2006 SEARCH Symposium. Justice Interoperability Across the Extended Enterprise: A Wisconsin Case Study. Jim Pingel - WIJIS Director Donna Lewein – Project Manager. Background: Interoperability in Wisconsin An Update on Current Projects Lessons Learned
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Justice Interoperability Across the Extended Enterprise:A Wisconsin Case Study
Jim Pingel - WIJIS DirectorDonna Lewein – Project Manager
Automated case processing; movement of documents electronically, from one system to another.
The ability to search for key investigative or case information across multiple individual systems.
THIS IS A STORY ABOUT TRYING TO COLLABORATIVELY ACHIEVE
Interoperability in Wisconsin
Promote and coordinate automated information systems that are interoperable among, and available to, local, tribal, county, and state justice agencies.
Coordinate Multiple Projects, Leverage Grant Resources
Accomplish both information sharing and exchange with a single infrastructureWIJIS Overview
The IEPD Process
Warrants & Protective Orders
Local Law Enforcement
Records Management Systems
Gaps Remain in Seamless, Secure Information Sharing.
The View from Local Law Government
Project Management in a Multi-Agency, Multi-Project Environment
Identified overarching issues for resolution beyond this group
Reset the expectation to focuson producing the Gateway toolInvoking a Project Reset
Conflicting priorities with other duties
Lack of traditional contracting leverage
Residual conflicts between team members
Politics and the motives created
Historic distrust between agenciesManaging an Interagency Team
Communicate often & widely though adds overhead (compared to total outsourcing) itself can cause risk
Value team members’ specific experience with locals on other state Justice projects: builds trust of locals and a tight team
Reinforce the reusability of infrastructures, code, processes, documentationManaging an Interagency Team
Provides secured Internet access fordispersed local and state users to:
Project documentation, schemas, specs
Topical, threaded discussions
Links to justice sharing articles
http://sourceforge.net/projects/geeklogplugins/Managing an Interagency Team
Include people of the appropriate levels
Be a trustworthy partner:
Make productive use of people’s time
Be focused on the product
Be inclusive in decision-making
Be inclusive in giving credit where it’s dueTake me to your leader!
Experienced pushback against agile methods from team members in other agencies:
…a “teach by example” opportunity
The local partners have liked the flexibility of the agile style;their feedback is quickly implemented.
Don’t interrupt ongoing projects
But ready use projects as case studies to propose standard solutions to recurring problemsJustice Interoperability Workgroup
De-values the information-sharing effort.
If the rules change, start over!
Write Restrictions Into Each Application.
Rigid system design.
If the rules change, re-write many lines of code.
Cascading Disclosure Control Language
Write rules once, reuse them in many situations.
A policy change means changing a config file – rather than a new software project.
Data providers have flexibility to write their own rules.A Potential Deal-Killer: Disclosure of Sensitive Info
For more information please visit:
Or contact us: