Appendix B, Figure 1: When Should Technology be
Shows a continuum of the five technology strategy choices ranging from a technology driver to a technology follower, or in some cases, a technology laggard.
Appendix C, Figure 1:
The technical features and capabilities necessary to implement business functions are displayed in four layers with the bottom layer providing the needed foundation for the layer immediately above it. The layers, from top to bottom are:
Application Layer - the custom-developed or commercial off the shelf (COTS) applications that implement and automate business functions
Service Layer - the intermediate, and often general purpose, services necessary to building applications. Examples of intermediate services include programming languages, user authentication services, and electronic mail transport services necessary to build the Application Layer.
Physical Layer - The physical layer is comprised of cables, computers, and other products assembled to build the Service Layer.
Telecommunications Layer - The connectivity between the upper layers including wide and local area networks, wireless networks, and even telephones.
Appendix D: Figure 1
The DOJ network comprises a number of independent, national networks developed and operated by each of the major DOJ components. These individual networks are generally hierarchically organized, reflecting the organization structure of a DOJ component and communicate through wide-area network connections.
Appendix D, Figure 2: DOJ Networks and Their Relationships
Figure 2 represents the details of individual DOJ component networks as a communications "cloud". Each of the component networks (as well as some of the classified networks and CJIS) is national in scope and has an implementation similar to the network shown in Figure 1 above. It suppresses many important details such as firewalls, gateways or specific hosts in order to label the types of existing networks and show a simplified view of the connectivity among them. The types of networks include
component classified networks, component unclassified networks, the FBI CJIS network, the MAN, the Internet, and "other U.S. Government networks."
Appendix D, Figure 3: Vision
The strategic vision for network connectivity is a single, secure Department wide network providing any-to-any communications among components. This DOJ wide area network would carry classified and unclassified data and define the perimeter for defense against external threats.
Appendix D, Figure 4: Concepts to Outsource
The local area networks within a building are shown to be the demarcation point between component run facilities and the outsourced DOJ data network.
Appendix E, Figure 1: Departmentwide PKI Concept
The PKI architecture shown at a conceptual level places PKI as the center connection for information exchange between components, state and local law enforcement, other state and local organizations, and other federal agencies.
Appendix F, Figure 1: JABS: A Conduit for Law Enforcement
The Department has developed JABS, a system for electronic information sharing to automate the booking processes of DOJ law enforcement components across the country. This segment architecture analysis examines how two of the Department's law enforcement components, the Drug Enforcement Administration (DEA) and the Immigration and Naturalization Service (INS), use their own internal booking processes in relationship to JABS and interface with the Federal Bureau of Investigation's (FBI) Integrated Automated Fingerprint Identification System (IAFIS).
Appendix F, Figure 2: Components of a Segment Architecture
Figure 2 depicts the process of developing and maintaining the segment architecture for JABS.
Block 1 = Baseline Characterization = The "As Is" Model
Block 2 = Gap Analysis = Transition Plan
Block 3 = Target Architecture = The "To Be" Model
Appendix F, Figure 3: Nationwide JABS Implementation
The graphic shows the high-level roles and responsibilities of the Project Management Office, the FBI IAFIS staff, and the component staff from the DEA and the INS in the implementation of nationwide JABS. Components provide the Booking Station, the FBI provides the 10-print criminal check, and the PMO provides direction and administration support.
Appendix F, Figure 5: Data Flow for the DEA Booking
The DEA collects booking and arrest data through its FBS. Once a booking package has been automatically constructed in FBS, the package is sent electronically to JABS, which repackages the information and submits it electronically to IAFIS. IAFIS responds with an e-mail message to JABS, which in turn, transmits the response with the data to the DEA
Appendix F, Figure 6: Data Flow for the INS Booking
INS bookings conducted through JABS bypass the IAFIS 10-print electronic matching process.
Appendix F, Figure 8: Department of Justice Value
Shows how the booking process within the Arrest Suspects function in the Enterprise Business Architecture contributes value to the in achieving the rapid identification of suspects; the sharing of common information among all law enforcement components; and the tracking of Federal offenders.
Appendix F, Figure 9: The Business Structure of the Department of Justice
This graphic shows how the "booking process" fits into the DOJ Enterprise Architecture. It is a component of the function " Arrest Suspects" within the Business Area "Enforcement Operations" and there are six activities that support the "booking process". These activities are:
Create booking record
Update booking record
Query JABS and IAFIS
Manage component station
Appendix F, Figure 12: Booking Process CRUD Matrix
The left column of this chart defines the rows within the matrix and is titled "Business Activity Names". The rows are broken out by component and Department level business activities. The columns are labeled "Data Entities" and include the following data entities:
Arrest (booking) officer
FBI ID record "rap sheet"
The blocks within the matrix where the business activities rows intersect with the data entity columns are filled in with one of the appropriate CRUD coding to show how the activity processes the data as shown below:
C- Creates data
R - Reads data
U - Updates data
D - Deletes data
Appendix F, Figure 14: Logical Relationship of
Target Booking Process Applications
This graphic shows the scope of the applications within the segment architecture highlighting that DEA, FBI, and BOP Booking Stations are outside the scope of the analysis.
Appendix F, Figure 15: Automated Booking Workflow
The diagram displayed in Figure 15 shows how JABS will enable the Department to design and implement a booking process to share booking data; facilitate the rapid identification of suspects through IAFIS; and track Federal offenders. When complete, all of the Department's law enforcement components will have an automated booking station, riding a robust infrastructure, to create the booking data repository.
Appendix F, Figure 17: Summary Transition Plan
The summary transition plan outlines the individual milestones that would allow the Department to transition from the current or "As Is" architecture to the target or "To Be" architecture over a two year period. The Transition Plan tasks are:
Develop component automated system
Deploy component booking stations
Offender tracking system
Latent fingerprint processing system
Update transaction system
Security system upgrade