Technical Briefs

tech-brief-whyimportant Technical Brief-Enterprise Strategic Planning for Justice Information Sharing: Why It’s Important
When developing technology solutions to obtain and share justice information, it is important for organizations to plan their efforts carefully. This is particularly true when the information is shared within a justice and public safety enterprise that spans agency and jurisdictional boundaries. The justice enterprise is complex and can involve multiple participants, differing governing processes and rules, distinct business needs, and competing resources. Effective strategic planning is essential to achieve success in this environment—and it must focus on building a shared vision among all stakeholders in the greater information sharing enterprise.

This brief explores the benefits of following an Enterprise Strategic Planning (ESP) methodology when initiating an information sharing program with local, regional, state, and/or federal partners. SEARCH developed this ESP methodology based on the principles of Enterprise Architecture (EA). This is a companion document to the Technical Brief, Enterprise Strategic Planning: A Methodology to Build a Shared Vision for Justice Information Sharing

tech-brief-methodology Technical Brief-Enterprise Strategic Planning: A Methodology to Build a Shared Vision for Justice Information Sharing
Enterprise Strategic Planning (ESP) is a methodology SEARCH developed that focuses on building a shared vision among stakeholders of an information sharing enterprise. The intent is to provide a process that jurisdictions can use to develop a comprehensive, enterprise-wide plan to share justice information among local, regional, state, and/or federal partners. This guide introduces the ESP methodology and discusses the key components of this approach.

In conjunction, download and use this modifiable Enterprise Strategic Plan template:
Enterprise Strategic Plan

TB-UsingOSItoImplementGRA Technical Brief-Using Open Source Infrastructure to Implement the Global Reference Architecture
The Global Reference Architecture (GRA) is an information exchange solution designed to cut 80% of implementation time and costs for state and local justice agencies through reuse of established promising practices in IT architecture and design. Organizations that implement the GRA must choose a technology infrastructure. This Technical Brief discusses one approach to developing a GRA-conformant information sharing infrastructure using open source components. These require no licensing costs, and provide a viable and cost-effective strategy for implementing the GRA.
TB-JavaToolsNDEx_IEPD Technical Brief-Using Java Tools to Implement the National Data Exchange Information Exchange Package Documentation
The Law Enforcement National Data Exchange (N-DEx) is the FBI’s national repository of law enforcement incident and offender data; it has the ability to detect relationships between people, vehicles/property, location, and/or crime characteristics contained in these data. It supports investigative activities across jurisdictional boundaries—enhancing information sharing at all levels of government. But justice agencies must first develop an N-DEx Information Exchange Package Documentation (IEPD), which uses national models and standards to simplify the process to implement connectivity to N-DEx and enable cross-agency information sharing. This Technical Brief outlines three common approaches justice agencies can use to work with XML in Java in order to implement the N-DEX IEPD, and addresses the advantages and drawbacks of each.
TB-GRA_SSDWorkshopPrimer Technical Brief-Global Reference Architecture Service Specification Development Workshops: A Primer for Facilitators
This Technical Brief provides meeting facilitators a best practice approach to service specification package (SSP) development using the GRA based on the experience, expertise, and lessons learned from the Global Services Task Team (STT). It focuses on the steps within the SSP development methodology that involve interactions with subject matter experts (SMEs), and provides a step-by-step guide to working with SMEs to gather the business information needed to develop a service specification. It also includes suggestions to facilitate an SSP development workshop.
TB-ServiceManJusticeIT Technical Brief-Using Principles of Service Management to Manage Justice Information Technology Services
IT services are the delivery of expertise and products by an IT provider that support the customer’s business processes—often including a combination of resources, people, processes, and technology to maintain an adequate level of service. This Technical Brief describes how principles of IT Service Management (ITSM) can benefit IT operations in the justice environment. It also provides a set of 10 service catalog templates that agencies can use to start developing a Configuration Management Database (CMDB), a tool that IT managers and staff use to define and track changes to the services they manage.

Download and use these modifiable service catalog templates:
Service Description-Email
Service Description-File, Print, and Document Management
Service Description-Local Area Network
Service Description-Database Hosting
Service Description-Internet
Service Description-Criminal Justice Information System Interface
Service Description-Telephony
Service Description-Web Hosting
Service Description-Help Desk
Service Description-Application Development

Technical Brief-Model-driven Development of NIEM Information Exchange Package Documentation
This brief focuses on another benefit of a UML Profile for IEPDs: the ability to support model-driven development of IEPDs, and development of IEPDs that fit within a model-driven architecture.
Technical Brief-Web Services and NIEM: Realizing the Value of Available Tools
This brief focuses on the value of Web Services Description Language (WSDL) to software developers, who can use WSDL definitions to produce software code for the intersystem sharing of information; demonstrates the ability of several available tools to create programming code based on NIEM schemas; and demonstrates that the web services tool space has matured to the point that there are no longer significant barriers to the use of NIEM with web services and WSDL.
Technical Brief-A Service-Oriented Architecture Primer for Executives: Why You Should Care
This brief outlines the business case for using SOA, and better prepares executives to make key decisions and facilitate a successful integration strategy.
Technical Brief-Using NIEM With Web Services
This brief explains the crucial relationship between NIEM IEPD and WSDL to support cross-domain information sharing.
Technical Brief–How to Display Suspicious Activity Reports in Google Earth
The graphical display of geographic information can provide law enforcement officers and intelligence analysts with a powerful tool to understand, interrupt, and prosecute criminal activity. For instance, displaying a related set of suspicious activity reports (SARs) on a map can illuminate relationships between activities and the environment in which they occur, leading to valuable insights and new intelligence. This brief outlines how to use Google Earth and associated NIEM IEPD standards to display geospatial information.
Technical Brief–The Benefits of Using JIEM® to Capture Privacy Requirements
This brief identifies the benefits of using the Justice Information Exchange Model framework and tool to capture privacy requirements. Identifying protected information and documenting privacy policy rules is a key step to protecting privacy while meeting the growing need to share information.
Technical Brief–Transforming Hierarchical Structures Into Associations
This brief addresses the problem of transforming XML documents (also called “instances” or “messages”) between differing information exchange models.
Technical Brief–Modeling Exchange Requirements: Justice Information Exchange Model and Business Process Modeling Notation
This brief articulates the complementary relationship between JIEM® and BPMN, which can be used to model exchange requirements.