Achieving Information Interoperability and Business Agility

1. Achieving Information Interoperability and Business Agility The Justice Reference Architecture: A Global Project (update)

2. Its about Interoperability… • Solving interoperability challenges continues to be a significant problem and a high priority for the justice and public safety community. • There are approximately 100,000 justice agencies that have the critical need to share information across their various information systems. • The variety of systems creates multiple layers of interoperability problems involving different hardware, software, networks and business rules for data exchange. • GXDM/NIEM and IEPDS are good start, but not enough • The Global Justice Information Sharing Initiative (Global) Justice Reference Architecture (JRA) project seeks to solve the interoperability challenge.

3. Its about Agility… • Agility is the hallmark of successful modern enterprises • Citizens expect rapid response to changing requirements • In the public safety arena: • Clever opponents • New partners and requirements • Policy initiatives • The Global JRA project seeks to improve agency agility.

4. S O A Service Oriented Architecture Capabilities performed by one for another to achieve a desired outcome Aligning architecture to enable a collection of services to be linked together to solve a business problem The fundamental organization of a system by its capabilities, their interactions, and the enterprise environment SOA is an architecture approach for organizing and using services to support interoperability between enterprise data assets and applications Its about Services… Slide courtesy of Booz Allen Hamilton and OASIS SOA-RM TC.

5. The Global JRA • The Global JRA Specification is intended to be a technical implementation architecture that addresses the full range of information sharing use cases, and provides a comprehensive blueprint for implementing interoperable data sharing services and capabilities. • Global believes that this dynamic interoperability strategy will help to prevent incompatibilities, guide vendors and organizations on how to fit components together, and facilitate communication and interoperability between disparate communities.

6. Distinguishing Characteristics • Interactions between consumers and providers (of functionality, data) take place across a minimalist interface • Interface based on open (versus proprietary) standards • Interface defined in business event terms, not system or technology terms

7. Why do I need another Reference Architecture? FEAF NASCIO EA DOD/C4ISR Framework Treasury Enterprise Architecture Framework (TEAF) DOJ DHS ISEEA

8. A Reference Architecture… • A reference architecture provides a proven template solution for an architecture for a particular domain. It also provide a common vocabulary with which to discuss implementations, often with the aim to stress commonality. • Reference architectures can be defined at different levels of abstraction. • A highly abstract one might show different pieces of equipment on a communications network, or Lines of Business, each providing different functions. • A lower level one might demonstrate the interactions of procedures (or methods) within a computer program defined to perform a very specific task. • The JRA • Focuses on Justice Information Sharing within a multi-jurisdictional environment • Leverages SOA • Provides the “right” level of abstraction

9. Global JRA Mission/Vision/Target Audience • Mission: To enhance justice and public safety through a service-oriented approach to information sharing. We accomplish this mission by providing a reference architecture with guidance for identifying, defining, implementing, and governing services. • Vision: Global JRA and related documents will be the definitive source for justice and public safety agencies for guidance on implementing a service-oriented approach to information sharing. • Target Audience: The target audience for the reference architecture and guidance is any group or set of justice partners that want to share information and agree to implement common business rules and infrastructure requirements.

10. Key Global JRA Deliverables • The JRA itself (concepts, relationships, and high-level components) • Concept of Operations • Service Interaction Profiles (think “messaging standards”) • Service Modeling/Specification Guidelines • Service Design Principles • Service Identification and Design Methodology • Management/Policy guidelines • Guidance on necessary investments to support services and interactions

11. GISWG Committees and Leadership • Tom Clark, GISWG Chair/ Eric Sweden, GISWG Vice Chair • Executive Architecture Committee • Management and Policy Committee • Dale Good, Chair • Services Interaction Committee • Kael Goodman, Chair • Services Committee • Scott Fairholm, Chair

12. IJIS is Actively Involved • Kael Goodman • John Loverude • Zemin Luo • David Rader • Sharad Rao • Iveta Topalova • Joseph Wheeler • Richard Williams

13. So what have you done for me lately… • Global JRA Version 1.3 Released • Version 1.4 in process • http://it.ojp.gov/topic.jsp?topic_id=242 • Concept of Operations (in process) • Services Interaction Profile for Web Services (committee draft) • Service Specification Guideline (committee draft) • Service Design Principles (committee draft) • Service Identification and Design Methodology (committee draft) • Fingerprint Identification Service Specification (committee draft) • Liaison to other Global Working Groups

14. So what have you done for me lately… • Discussions underway to map the Global JRA to other architecture efforts • Department of Justice • Department of Homeland Security • Information Sharing Environment (DNI) • OASIS SOA Reference Model Technical Committee • Fusion Center Architecture Working Group (IJIS) • Representatives attend our committee meetings

15. Thank You… Scott D. Fairholm National Center for State Courts sfairholm@ncsc.dni.us 757 259-1863