The Joint Automated Booking System

Audit Report 05-22
May 2005
Office of the Inspector General

Appendix III

Implementation Milestones

  • February 1996 to July 1999 - The JABS Pilot Project in the Southern District of Florida is operational.

  • May 1999 - The program's System Boundary Document is approved by the JABS Board of Directors. Development of the Core JABS data repository and the DEA's Firebird Booking Service (FBS) begins.

  • November 1999 - The program's Concept of Operations and Version 1.0 Requirements Matrix is approved by the JABS Board of Directors.

  • March 2000 - The program's System Design Document is approved by the JABS Board of Directors. The JABS change control process and charters for the JABS Advisory Group and the Security Working Group are approved by the Board of Directors.

  • July 2000 - The JABS Program Management Office (PMO) receives certification and accreditation for the Core JABS and it becomes operational. The DEA begins deployment of the FBS. The JABS linkage with the DEA's FIREBIRD network is established.

  • February 2001 - The BOP to the JABS Interface System Concept Design is completed by the BOP.

  • March 2001 - The CONOPS and functional requirements for the ENFORCE/JABS interface are completed by the INS.

  • October 2001 - The Core JABS version 2.0 Requirements Document is completed by the PMO.

  • November 2001 - A study of the USMS's automated booking station and PTS systems is completed by the PMO.

  • August to October 2002 - The BOP, FBI, USMS, and INS booking stations are linked to the Core JABS and deployment of their booking stations begins.

  • November 2002 - The Core JABS Version 2.0 is placed into production with backup capability.

  • March 2003 - Functions of the INS are incorporated into the new Department of Homeland Security.

  • April 2003 - Internet capability, with a network connection, to the FBI's Law Enforcement Online (LEO) unit is established.30

  • September 2003 - The JABS PMO reports deployment to 202 DEA sites, 137 FBI sites, 125 USMS sites, and 113 DHS sites.

  • October 2003 - The JABS PMO completes deployment to one National Institutes of Health and one Department of Defense (Fort Monmouth) site.

  • December 2003 - The ATF connects one site to the Core JABS.

  • June 2004 - The Core JABS Version 3.0 is placed into production. The required certification and accreditation is also received during this month.

With the anticipated submission of the OMB's-300 Exhibit for 2006, the JABS PMO advertises the following projected milestones.

  • November 2004 - The ATF continues to deploy stations to remaining sites.

  • September 2005 - The USMS expects to convert their automated booking stations to the web-based architecture. The FBI and USMS should be completely deployed. The ATF expects to have stations deployed to about 130 sites.

  • December 2005 - The JABS PMO expects the U.S. Courts might have a JABS data interface.

  • December 2005 - The federal offender tracking system should be integrated with the automated booking stations.

  • September 2006 - Due to anticipated equipment loss, obsolescence, and breakage, the JABS PMO expects to refresh equipment for about 250 Department sites.


  1. LEO is a 24/7 “on-line” (real-time), controlled-access data repository, providing a focal point for electronic communication, education, and information sharing for the Law Enforcement, Criminal Justice, and Public Safety Communities nationwide. Users are vetted by the FBI prior to being given access to the network. LEO is accessed by using industry-standard personal computers equipped with any standard Internet browser software. Virtual private networking software provides authorized users secure access to LEO via the Internet through an Internet Service Provider such as America On-Line, Microsoft Service Network, a DSL/cable modem or Local Area Network.

Previous Page Back to Table of Contents Next Page