Audit of the Department of Justice Information Technology Studies, Plans, and Evaluations
Audit Report 07-39
August 2007
Office of the Inspector General
The system summaries in this appendix contain information from documents the components submitted that we did not verify. The purpose is to provide readers additional information on each system or project and the environment in which it operates or is expected to operate.
The lists of studies, plans, and evaluations include documents representing entire studies, plans, and evaluations we determined complied with one or more of the standards described in Finding 1. The lists do not include all other artifacts the components submitted that we determined contributed to compliance with the standards, such as spreadsheets and briefing slides.
The document titles in the lists may include additional acronyms that we have defined in the text preceding the document list for each system. Acronyms not found in the text of this appendix are located in Appendix II. Blank cells in the Date column indicate items for which no date was provided.
National Integrated Ballistics Information Network
Bureau of Alcohol, Tobacco, Firearms, and Explosives
The ATF’s National Integrated Ballistics Information Network (NIBIN) program supports criminal investigations in conjunction with the Integrated Ballistics Identification System (IBIS), a nationally distributed ballistic evidence-imaging database. This database assists state and local law enforcement officials in identification of firearms and bullets collected at crime locations and allows for comparison and correlation to other crime scene evidence or recovered crime guns. NIBIN allows for the ATF to provide ballistic imaging, comparison equipment, and the network over which it communicates to 182 state and local law enforcement partners at 239 data remote sites. State and local NIBIN partners enter bullet and cartridge casing evidence into the systems and conduct electronic comparisons to find potential matches. "Hits" or matches between crimes, not otherwise known to be related, assist law enforcement officials in locating repeat violent offenders. The program began spending funds in FY 1996, and the system is operational.
NIBIN Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Business Case Study | OMB Exhibit 300 for BY 2007 | May 2006 | 8 |
Privacy Impact Assessment | Privacy Threshold Analysis, IBIS | 9 | |
Risk Management Plan | Risk Assessment, NIBIN and IBIS | Jun 2005 | 13 |
Acquisition Plan | Request for Justification for Other Than Full and Open Competition | Jan 2002 | 12 |
Security Plan | Security Plan, NIBIN and IBIS | Jun 2005 | 14 |
Test Plan | Security Test and Evaluation, NIBIN | Dec 2005 | 15 |
Test Plan | Testing on Test Rig Test Plan – Phase 3, NIBIN | Mar 2006 | 1398 |
Test Plan | Testing on Test Rig Test Plan – Phases 1 & 2, NIBIN | Jan 2006 | 1397 |
Implementation Plan | Deployment of the NIBIN Enterprise – Set 9 | Jan 2006 | 1413 |
Implementation Plan | NIBIN Deployment Plan, IBIS 3.4.6 Upgrade | Mar 2006 | 1414 |
Training Plan | NIBIN Training Set 11, Version 1.2, Draft | 17 | |
Contingency/Continuity Plan | Contingency Plan – Appendix I, NIBIN | 2 | |
Contingency/Continuity Plan | Contingency Plan, DOJ, NIBIN and IBIS | Jun 2005 | 3 |
Test Report | Security Test and Evaluation, NIBIN | Dec 2005 | 15 |
Test Report | Security Testing and Evaluation, NIBIN | Dec 2005 | 16 |
Test Report | Test Rig Test Evaluation Summary – Phase 1 & 2 | Jan 2006 | 1395 |
Test Report | Test Rig Test Evaluation Summary – Phase 3 | Mar 2006 | 1396 |
Inmate Telephone System-II
Bureau of Prisons
The BOP’s Inmate Telephone System-II (ITS-II) project began spending funds in FY 1998. The project is a centralized inmate calling system intended to provide inmates with a secure, efficient, and cost effective means of maintaining contact with family, friends, and the community while at the same time preventing crime, fraud, and abuse by inmates. It provides the BOP with enhanced call monitoring, call recording, and reporting capabilities. ITS-II is funded and maintained using non-appropriated funds generated from the Commissary Trust Fund. Maintenance costs for the system are established and funded from the actual costs of service charges for telephone usage. Annual funding is based on the projected sales for that year which exceeds the outlays for the project. ITS-II is fully installed and is in a steady-state status. It consists of local networks at all BOP facilities and primary and secondary Central Office Facilities and is connected via a Wide Area Network.
ITS-II Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Market/Other Research | Request for Comment | 416 | |
Business Case Study | Analysis of Alternatives, Next Generation Inmate Telephone System | Jul 1996 | 18 |
Business Case Study | OMB Exhibit 300 BY 2006 | 1392 | |
Privacy Impact Assessment | Privacy Impact Assessment | Apr 2006 | 20 |
Acquisition Plan | Individual Acquisition Planning | Jan 1997 | 19 |
Project Plan | Program Plan | May 2005 | 412 |
Security Plan | Inmate Telephone System (ITS-II) Security Plan | Dec 2004 | 21 |
Systems Engineering Management Plan | Engineering Management Plan | Apr 2005 | 415 |
Conversion Plan | Site Network Integration Plan, ITS-II/TRUFACS | Nov 2001 | 22 |
Implementation Plan | Site Network Integration Plan, ITS-II/TRUFACS | Nov 2001 | 22 |
Contingency/Continuity Plan | Contingency Plan | Nov 2004 | 414 |
Concorde
Drug Enforcement Agency
The DEA is the federal entity charged with the enforcement of the controlled substance laws and regulations. It has approximately 300 locations throughout the world and utilizes various “stove-piped” applications in support of primary businesses – criminal data gathering, case status tracking, lab analysis, evidence and seized asset handling, licit drug manufacturing and distribution tracking (DEA’s diversion function), and administrative functions such as tracking agent property (weapons, fleet, badges), and agent tasking. The Concorde program is intended to eliminate these stove-piped systems by integrating business functions and allowing for information sharing across the main DEA business areas.
Concorde Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Privacy Impact Assessment | Initial Privacy Impact Assessment, Concorde | 35 | |
Risk Management Plan | Risk Management Plan, Concorde, Version 1.0 | Feb 2005 | 46 |
Acquisition Plan | Statement of Work/Acquisition Plan, Concorde, Version 1.0 | Nov 2002 | 49 |
Project Plan | Project Management (PMP), IMPACT Fiscal Year 2004, Version 2.1 | Sep 2004 | 42 |
Project Plan | OMB Exhibit 300 for BY 2007 | Sep 2005 | 39 |
Security Plan | System Security Authorization Agreement (SSAA), Appendix E, Web Architecture | Mar 2002 | 50 |
Configuration Management Plan | Configuration Management Plan, Concorde, Version 1.0 | Jul 2004 | 29 |
Quality Assurance Plan | Quality Management Plan (QMP), Office of Information Systems (SI), Version 4.1 | Sep 2005 | 83 |
Test Plan | Project Test Plan (PTP), IMPACT, Release 2.0, Version 1.0 | Feb 2005 | 44 |
Implementation Plan | Project Deployment Plan, Concorde, Version 1.0 | Sep 2004 | 41 |
Training Plan | Training Program, PMP Concorde, FY 2006, Version 1.0 | Oct 2005 | 51 |
Contingency/Continuity Plan | Contingency Plan, Web Architecture, Version 2.0 | Mar 2006 | 30 |
Test Report | Operational Test for Impact on Security (OTIS) Report of the Pilot Implementation, IMPACT | Jul 2002 | 40 |
Test Report | System Security Authorization Agreement (SSAA), Appendix E, Web Architecture | Mar 2002 | 50 |
Performance Evaluation | OCIO: Project Dashboard Project Managers Worksheet, Concorde | Aug 2005 | 38 |
In the 1990’s, DEA introduced the agency-wide Firebird client/server, which is the core local area network. Concorde is built on the Firebird infrastructure. The focus of Concorde is the investigative and case management process.
The Concorde project is composed of four major technology enhancements: Investigative Management Program and Case Tracking System (IMPACT), Plan Enforcement Tracking System (PlanETS), Statistical Management and Report Tracking System (SMARTS), and the Centralized Evidence Reporting and Tracking System (CERTS). Although the OMB exhibit 300 shows the project began spending funds in FY 2003, IMPACT’s pilot implementation was released in 1999. The scheduled completion for the entire project is the end of FY 2009.
E-Commerce
Drug Enforcement Agency
The DEA’s Office of Diversion Control (OD) regulates the manufacture and distribution of controlled substances in the United States. This regulatory control is designed to prevent the diversion of legitimate pharmaceutical drugs into illegal channels and to ensure that there is a sufficient supply for legitimate medical uses while preventing the introduction of contraband controlled substances into the legal distribution channels.
E-Commerce Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Business Case Study | Economic Impact Analysis of the Electronic Orders Rule | Mar 2005 | 58 |
Business Case Study | Initial Economic Impact Analysis of the Proposed Electronic Orders Rule | Mar 2003 | 61 |
Business Case Study | OMB Exhibit 300 for BY 2007, Final CSOS | Sep 2005 | 64 |
Privacy Impact Assessment | Detailed Privacy Impact Assessment, Attachment: DEA CSOS Privacy Policy, Section IV |
Sep 2005 | 56 |
Risk Management Plan | Facilitated Risk Assessment Process, DEA Diversion Control E-Commerce PKI, SSAA, Appendix G, Version 1.0 | Dec 2003 | 60 |
Risk Management Plan | Risk Management Plan, DEA Diversion Control, E-Commerce System, Version 1.0 | Oct 2005 | 72 |
Project Plan | Program Management Plan, DEA Diversion Control E-Commerce PKI, Version 3.1 | Nov 2004 | 68 |
Security Plan | System Security Plan, CSOS, Version 1.0 | Jun 2005 | 74 |
Systems Engineering Management Plan | Operational and Technical Architecture, Public Key Infrastructure Analysis, DEA Diversion Control E-Commerce PKI | Jun 2003 | 65 |
Configuration Management Plan | Configuration Management Plan, DEA Diversion Control E-Commerce System, Version 1.0 | Feb 2006 | 53 |
Quality Assurance Plan | Process and Product Quality Assurance, DEA Diversion Control E-Commerce System, Version 1.0 |
May 2005 | 67 |
Test Plan | Acceptance Test Plan, Public Key Infrastructure Analysis, Diversion PKI, CSOS | Jan 2005 | 52 |
Test Plan | Test Plan and Reporting Procedures, CSOS/ EPCS | Dec 2001 | 75 |
Training Plan | Training Plan, Public Key Infrastructure Analysis, DEA Electronic Commerce PKI | Aug 2002 | 76 |
Contingency/Continuity Plan | Contingency Plan, DEA Diversion Control E-Commerce PKI System (EPCS/CSOS), Version 1.0 | Nov 2003 | 54 |
Contingency/Continuity Plan | Contingency Plan, DEA Diversion E-Commerce System Security Plan, Appendix L, Version 1.1 | May 2005 | 55 |
Test Report | System Security Authorization Agreement (SSAA), Appendix F, CSOS and EPCS PKI | Mar 2004 | 73 |
Post-Implementation Evaluation | Diversion Metrics Implementation Report, DEA Diversion Control, E-Commerce System, Version 1.0 |
Jan 2006 | 57 |
The Government Paperwork Elimination Act (GPEA) of 1999 (Title XXII of Public Law 105-277) mandates that Federal agencies allow for the option of electronic submission of required records and for the use of electronic signatures when practicable.
In July 1999, DEA undertook the initiative to begin designing two e-commerce initiatives that would enable industry to conduct e-commerce. The first project was called the Manufacturers and Distributors (MADI) Public Key Infrastructure (PKI) Analysis and Design Program, which involved the designing of a PKI proof-of-concept to better oversee and manage the transfer of Schedule II controlled substances between DEA registrants, manufacturers, wholesalers, and pharmacies. The second project was called DEA – Department of Veterans Affairs (DEVA) PKI Pilot Program, which involved designing a public key infrastructure architecture suitable for use in transmitting prescriptions electronically and identifying aspects of the relationship between the physician and the pharmacy that can be enhanced through the implementation of a PKI.
The initial phases of both projects entailed requirements and design analysis. The next phases of the e-commerce projects introduced a change in the project titles: Controlled Substance Ordering System (CSOS) and Electronic Prescriptions for Controlled Substances (EPCS). The DEA and DVA pilot continues under the EPCS project.
The CSOS/EPCS project began spending funds in FY 1999 and is estimated to be complete in FY 2016. The DEA has begun the collection and analysis of CSOS orders.
El Paso Intelligence Center (EPIC) Information Systems
Drug Enforcement Agency
Other Components Involved: | Federal Bureau of Investigation U.S. Marshals Service Bureau of Prisons |
EIS Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Market/Other Research | National Drug Seizure System Discussion Paper, CDX | Feb 2004 | 432 |
Market/Other Research | NDSS Project, Background: NIBRS/UCR Data, CDX | May 2003 | 427 |
Business Case Study | OMB Exhibit 300 for BY 2007 | Sep 2005 | 77 |
Privacy Impact Assessment | Initial Privacy Impact Assessment for EID | 1411 | |
Risk Management Plan | EIS Risk Impacts, EPIC | 1408 | |
Risk Management Plan | Risk Assessment Report, EPIC | May 2005 | 417 |
Risk Management Plan | Risk Management Plan, Open Connectivity Project, DEA EPIC, Revised | Aug 2004 | 429 |
Risk Management Plan | Seizure System Risk Assessment Report, EPIC | May 2005 | 1404 |
Project Plan | Information Systems Project management Plan, EPIC | Sep 1991 | 1405 |
Security Plan | System Security Plan, ESS | Aug 2005 | 420 |
Systems Engineering Management Plan | System Engineering Management Plan, EPIC Open Connectivity Project | Jun 2004 | 424 |
Configuration Management Plan | Configuration Control Board (CCB) Charter and Request for Information Technology Services (RITS) Policy | Feb 2004 | 425 |
Quality Assurance Plan | Quality Management Plan (QMP), Office of Information Systems (SI), Version 4.1 | Sep 2005 | 83 |
Verification/Validation Plan | Verification and Validation Plan, EPIC Open Connectivity Project | Apr 2004 | 426 |
Test Plan | Development Inspection Logs, EPIC | 1412 | |
Test Plan | Year 2000 Test Plan, EPIC | 1409 | |
Training Plan | Training Plan, EPIC Open Connectivity Project | Jun 2004 | 423 |
Contingency/Continuity Plan | Contingency Plan, ESS | Mar 2006 | 422 |
Test Report | Development Inspection Logs, EPIC | 1412 | |
Test Report | Operational Test Report | Jan 1993 | 1410 |
EPIC accomplishes its mission in part by manually processing written or telephonic requests for information received from State, local and Federal law enforcement personnel, on persons, modes of transportation, organizations, or addresses that are suspected of being engaged in, or associated with some criminal activity. Watch Officers using a multiple database query process the requests for information.
The objective of the Open Connectivity Project is to enable EPIC to provide secure internet access to tactical intelligence information for Federal, State and Local law enforcement agencies. The system objective is to streamline access by providing to all EPIC customers a point of entry that permits direct and remote electronic access from the users’ existing IT and internet architecture and provides an automated response to queries. With the Open Connectivity Project, EPIC will provide this access for its customers in the form of a secure, Internet connection. Through an EPIC web site, law enforcement officers will access EPIC services, which will include the multiple source data repository, comprehensive query results, multiple formatted reports, and automated analytical support.
Firebird
Drug Enforcement Agency
Firebird is the DEA's global computing infrastructure, providing the foundation for the communications network, the client and server hardware and software, and the DEA's complete office automation system to all DEA personnel and contractors. A client-server based network, Firebird links DEA offices and components worldwide and supports the full spectrum of DEA operations. Firebird enables the DEA's investigative case management system, the financial management system, and all other Sensitive But Unclassified (SBU) information systems that DEA personnel use to support their daily job functions. Firebird also provides the interface for all new web-based applications and lays the foundation for improved information sharing with partner agencies.
Firebird Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Market/Other Research | Firebird Information Technology Support (FITS) Market Research Report | Mar 2004 | 1379 |
Business Case Study | OMB Exhibit 300 for BY 07 | Sep 2005 | 1378 |
Project Plan | Project Management Plan (PMP), Firebird Infrastructure Technology Services (FITS), Version 3.0 | Jan 2006 | 129 |
Security Plan | Security Operating Procedures Guide, Firebird (FSOPG), Version 4.0 | Mar 2004 | 1021 |
Configuration Management Plan | Configuration Management Plan (CMP), FITS, Version 1.3 | Jan 2006 | 116 |
Quality Assurance Plan | Quality Assurance Plan, FITS, Version 2.1 | Jan 2005 | 130 |
Test Plan | Security Test and Evaluation Plan and Procedures, Appendix E | Jul 2004 | 131 |
Implementation Plan | EOS Software Deployment Function Description, Version 2.5, not dated | 118 | |
Implementation Plan | Windows 2003 (W2K3) Implementation Plan, FITS MDE, Version 1.2 | Jun 2006 | 139 |
Contingency/Continuity Plan | Windows Server 2003 Infrastructure Disaster Recovery Document, FITS, Version 2.1 | Jun 2006 | 141 |
Test Report | Test Matrix, Desktop and Server Management Evaluation 2005 | 137 | |
Performance Evaluation | Enterprise Health and Performance Metrics Review | May 2006 | 117 |
Performance Evaluation | Firebird Dashboard | Apr 2006 | 121 |
Performance Evaluation | SIO Firebird project portfolio | Jul 2006 | 132 |
In 1994 the DEA began replacing its proprietary Wang Office Automation (OA) system with Firebird. The OA system provided personnel with basic office automation software and access to DOJ mainframe systems, but did not allow for electronic case management, or electronic communications and information sharing between DEA offices. The DEA designed Firebird based on forward looking enterprise-wide and Federal IT standards, the recognized advantages of a modular architecture, and the need for a flexible system that is maintainable and expandable.
The Firebird project began spending funds in FY 1994, and entered the Operational/Maintenance phase in FY 2003. In May 2003, the DEA completed its initial deployment of Firebird, which supports nearly 16,000 users, over 14,500 workstations, and over 500 servers in more than 370 locations worldwide.
Model 204 Corporate Systems
Drug Enforcement Agency
Other Components Involved: Federal Bureau of Investigation
The DEA performs mainframe data processing activities utilizing Computer Corporation of America (CCA) Model 204 database management system software for the development of applications for the corporate mission and administrative databases. These Model 204 Corporate Systems applications or subsystems provide the capability for DEA personnel to acquire information relating to drug related activities and cases. The applications also provide a method to track administrative information relating to DEA equipment and personnel.
M204 Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Business Case Study | OMB Exhibit 300 for BY 2007 | Jul 2005 | 80 |
Project Plan | Project Management Plan (PMP), Events Activity Subsystem (EVENTS), Calendar Year 2004, Version 1.0 | Jun 2004 | 82 |
Security Plan | Systems Security Authorization Agreement (SSAA), Model 204 Corporate Systems (M204) | Nov 2004 | 85 |
Configuration Management Plan | Project Level Configuration Management Plan, Events Activity Subsystem (EVENTS), Version 1.0 | Jun 2004 | 81 |
Quality Assurance Plan | Quality Management Plan (QMP), Office of Information Systems (SI), Version 4.1 | Sep 2005 | 83 |
Verification/Validation Plan | Independent Verification and Validation (IV&V) Software Testing Procedure for Mainframe Environment, Version 2.0 | Jun 2004 | 79 |
Test Plan | ST & E Plans and Procedures, Appendix E, Model 204 Corporate Systems | 1420 | |
Test Report | Certification Results, Appendix F, Model 204 Corporate Systems | 1421 |
The M204 system includes approximately 32 core investigative and administrative applications that support DEA's mission, strategic goals, and objectives as well as serving the specific needs of external DEA partners. Several of the legacy applications now running in the M204 environment are scheduled for replacement through a number of modernization initiatives. To enhance the usability and simplify access to M204 applications until the modernization initiatives deploy viable solutions, DEA has acquired and is implementing JANUS Web Server to provide browser based access to selected M204 applications. JANUS will replace the mainframe "green screen" with user friendly drop down menus, data entry validation and navigation features.
The M204 project began spending funds in FY 1980, and is in the operational/maintenance phase of the DEA SDLC.
Merlin
Drug Enforcement Agency
Merlin provides DEA offices with the capability to transmit, access, and share classified intelligence data over the existing classified telecommunications networks that service the DEA’s domestic and foreign offices.
The Merlin system provides the end-users workstations and the necessary enterprise and site-level servers to run Active Directory services, mail services, local file services, and a Merlin Web site. The Merlin system provides the end users with a complement of commercial applications such as Microsoft Office, i2’s Analyst’s Notebook, and ArcView. It also provides the users access to DEA custom applications that use a browser (Internet Explorer) interface.
Merlin Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Business Case Study | OMB Exhibit 300 for BY 2007 | 271 | |
Risk Management Plan | Risk Assessment Report, DEA Classified Infrastructure Support System | May 2005 | 261 |
Project Plan | Merlin Program Plan, Version 2 | Jun 2006 | 268 |
Security Plan | System Security Authorization Agreement (SSAA), DCISS | Aug 2003 | 272 |
Configuration Management Plan | Configuration Management Plan for the Merlin Project | Sep 2006 | 1431 |
Quality Assurance Plan | Quality Management Plan (QMP), Office of Information Systems (SI), Version 4.1 | Sep 2005 | 83 |
Quality Assurance Plan | Merlin Quality Assurance Plan | Feb 2005 | 1432 |
Test Plan | Security Test & Evaluation Plan and Procedures | Aug 2003 | 1384 |
Contingency/Continuity Plan | Contingency Plan for the DEA Merlin Program | Jun 2006 | 259 |
Test Report | Certification Results | Aug 2003 | 1385 |
Test Report | COOP Test Report using VERITAS Replication EXEC 3.1 | Mar 2006 | 260 |
Test Report | System Security Authorization Agreement (SSAA), DCISS | Aug 2003 | 272 |
Performance Evaluation | Earned Value Management (EVM) Merlin, Doc #12-35-41-55 | Jul 2006 | 262 |
Performance Evaluation | Merlin Dashboard - May | Jun 2006 | 264 |
Organized Crime Drug Enforcement Task Force Fusion Center System
Office of the Deputy Attorney General
Other Components Involved: | Executive Office for the U.S. Attorneys Bureau of Alcohol, Tobacco, Firearms, and Explosives U.S. Marshals Service Federal Bureau of Investigation Criminal Division Tax Division |
The mission of the OCDETF Fusion Center (OFC) is to fuse data from multiple disparate sources and extract previously unidentified relationships and knowledge from the fused data relating to persons and organizations. The OFC will support the OCDETF intelligence and investigative activities task force with a fused database comprised of information from its member agencies. The Fusion Center System is a web based application that will be used by the OFC analysts and agents to search on information contained within this fused database. OCDETF began spending funds on the Fusion center system in FY 2003.
OFC Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Market/Other Research | Comparative Analysis of the FBIs SCOPE and DEAs NEDRS Systems | Feb 2003 | 1377 |
Market/Other Research | Comparative Analysis of the FBI's SCOPE and FTTTF | Apr 2003 | 1372 |
Market/Other Research | Draft Comparative Analysis of OCDETF Requirements with Existing DOJ Data Warehousing Efforts | Apr 2003 | 1371 |
Market/Other Research | Third Party Tool Recommendations | Jun 2005 | 1369 |
Business Case Study | OMB Exhibit 300 for BY 2006 | Sep 2004 | 316 |
Privacy Impact Assessment | Privacy Impact Assessment, OFC (Draft) | Aug 2004 | 320 |
Risk Management Plan | Risk and Issue Management Master Plan | Jun 2005 | 328 |
Acquisition Plan | Justification for Other than Full and Open Competition | May 2004 | 306 |
Project Plan | Project Management Plan, OFC Deployment | Sep 2005 | 321 |
Project Plan | Project Plan, Software Version 1.0, OFC | May 2006 | 322 |
Security Plan | System Security Plan, OFC Compass | 334 | |
Quality Assurance Plan | Quality Management Plan (QMP), Office of Information Systems (SI), Version 4.1 | Sep 2005 | 83 |
Test Plan | System Test Plan, OFC, Version 1.2 | Jan 2006 | 335 |
Training Plan | Compass Training Plan, OFC, Version 1.0 | Sep 2005 | 289 |
Contingency/Continuity Plan | IT Contingency Plan, IRSS, Version 2.2 | Mar 2005 | 305 |
Test Report | System Test Plan, OFC, Version 1.2 | Jan 2006 | 335 |
eWorld
Executive Office for Immigration Review
The Executive Office for Immigration Review's (EOIR) eWorld project began spending funds in FY 2002 and is the agency's primary initiative in its capital planning and investment control process. In this multi-year, multi-phased, multi-disciplinary project, EOIR will make the transition from paper to electronic documents for its official adjudication records spanning from initial filing through final appellate decisions.
eWorld Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Market/Other Research | Market Survey, EOIR, Digital Audio Recording Project, Version 0.16 (Draft) | Apr 2006 | 854 |
Business Case Study | OMB Exhibit 300 for BY 2007 | Jan 2006 | 112 |
Privacy Impact Assessment | Privacy Impact Assessment, Executive Office for Immigration Review | Apr 2006 | 860 |
Project Plan | Project Management Plan, CASE Court Pilot | Apr 2006 | 851 |
Project Plan | Project Management Plan, Digital Audio Recording Project, Version 0.05 | May 2006 | 852 |
Security Plan | System Security Plan (SSP) for JCON-II/CASE, EOIR | Mar 2006 | 863 |
Configuration Management Plan | Configuration Management Plan, EOIR | Mar 2006 | 856 |
Configuration Management Plan | Configuration Management Plan, eWorld, Version 1.0 (Draft) | Feb 2006 | 857 |
Contingency/Continuity Plan | IT Contingency Plan, EOIR, JCON-II/CASE, Version 2.0 | Nov 2005 | 855 |
Biometric Reciprocal Identification Gateway
Federal Bureau of Investigation
The FBI's IAFIS is a 10-rolled fingerprint identification system that is used by federal, state, and local law enforcement and authorized non-criminal justice agencies to identify subjects with criminal histories. The DHS IDENT is a 2-flat fingerprint identification system originally deployed by the Immigration and Naturalization Service as a database of criminal and illegal aliens to assist Border Patrol in identifying aliens who repeatedly attempt illegal border crossings. The DHS utilizes IDENT for search and enrollment purposes when non-US citizens travel to the United States through an authorized port of entry. The Department of State (DOS) Consular Posts utilize IDENT for search and enrollment purposes when determining suitability for aliens traveling to the United States. Currently, IAFIS and IDENT are linked through limited automated and manual processes.
BRIDG Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Business Case Study | Full Business Case, IDENT-IAFIS Interoperability, iDSM Project | Jan 2006 | 455 |
Business Case Study | OMB Exhibit 300 for BY 2008 | Aug 2006 | 1036 |
Privacy Impact Assessment | Privacy Impact Assessment for the DOJ/FBI-DHS Interim Data Sharing Model (iDSM) | 459 | |
Risk Management Plan | Risk Management Plan, iDSM Project | Jan 2006 | 462 |
The FBI supports DHS and DOS through daily biographic-based extracts of wants and warrants that have an associated FBI number and Known and Suspected Terrorists. The extract process, however, does not provide real-time access to current information, includes only a subset of information, and does not allow international, federal, state, and local fingerprint contributors access to all immigration information. Various legislative acts demand that the FBI and DHS ensure that the biometric systems are able to seamlessly share data that is complete, accurate, current, and timely. Through this interoperability, the criminal and immigration information will be accessible to and shared among other federal, state, and local law enforcement agencies.
In order to realize interoperability, investment is needed to develop the Biometric Reciprocal Identification Gateway (BRIDG). BRIDG development is planned in three phases: interim Data Sharing Model (iDSM); Initial Operating Capacity (IOC); and the Full Operating Capacity (FOC). In FY 2008, investment is needed to support the operation and maintenance of the iDSM and development of both the IOC and FOC portions of the BRIDG. The BRIDG investment will allow the creation and maintenance of biometric-based links between the biographic information contained in the IAFIS and IDENT systems, in near real time, as well as provide the infrastructure necessary to exchange data between the systems to ensure that biometric-based immigration and travel history information and criminal history record information is available to authorized personnel.
Computer Analysis Response Team Storage Area Network
Federal Bureau of Investigation
In the aftermath of the September 11, 2001 terrorist attacks, the FBI collected digital evidence from businesses, personal computers and loose media from across the US. The FBI did not possess a storage/examination/review system that could efficiently and consistently process large quantities of digital evidence collected from multiple sources. The Computer Analysis Response Team Storage Area Network (CARTSAN) System is a unique state-of-the-art "Digital Forensic Network" that allows for the efficient forensic processing and review of computer evidence. This system was certified and accredited on August 15, 2005. It offers the Computer Analysis Response Team (CART) Examiner and FBI Case Agent a resource that ensures accurate and timely handling of computer evidence acquired in support of Criminal, Cyber, Counterintelligence and Counterterrorism matters in a forensically secure environment.
CARTSAN Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Business Case Study | OMB Exhibit 300 for BY 2008 | Dec 2006 | 1023 |
Privacy Impact Assessment | Privacy Impact Assessment, CARTSAN, (Draft) | 446 | |
Risk Management Plan | Risk Management Plan | Jul 2005 | 447 |
Security Plan | System Security Plan, CARTSAN | Aug 2005 | 449 |
Configuration Management Plan | Configuration Management Plan, Version 0.1 (Draft) | 438 | |
Quality Assurance Plan | Digital Evidence Laboratory Quality Assurance Manual Supplement, CART | Apr 2006 | 439 |
Test Plan | Certification Test Report, CARTSAN | Aug 2005 | 436 |
Implementation Plan | CARTSAN Review Network Installation Plan | Jun 2005 | 434 |
Test Report | Certification Test Report, CARTSAN | Aug 2005 | 436 |
Performance Evaluation | Earned Value Management Worksheet | Jul 2005 | 441 |
Performance Evaluation | Investment Management/Project Review Board | Aug 2005 | 443 |
Each CARTSAN System has the ability to temporarily store large quantities of digital computer evidence. This system establishes digital connectivity between the CART forensic examination and review processes, eliminating the need to store forensic examination data on multiple hard drives. The system greatly reduces the time required to process and disseminate computer related evidence.
In FY 2006, CART anticipates completing more than 10,000 examinations of computer media, equating to more than one Petabyte of digital evidence. One Petabyte of information is equivalent to 250 billion pages of text; enough to fill 20 million, four-drawer filing cabinets. As the amount of data average businesses collect and store is doubling each year, this amount of data will be what many businesses will be managing within the next 5 years. As this growth occurs, the FBI is required to expand its capability to process and temporarily store these increasing amounts of data.
Phase I of the CARTSAN project, initiated in FY 2002 and concluded in FY 2006, included the design, acquisition, and deployment of CARTSAN Systems to 25 major FBI Field Office and Regional Computer Forensic Laboratories (RCFL) locations. Phase II is scheduled to begin in BY 2007 with the allocation of personnel resources to begin planning for the next deployment of systems. Phase II includes the purchase and deployment of 20 new CARTSAN Systems as well as operation, maintenance and upgrade costs for the existing 25 systems.
Combined DNA Index System
Federal Bureau of Investigation
The Combined DNA Index System (CODIS) is an automated DNA information processing and telecommunications system that supports the National DNA Index System, State DNA Index System, and Local DNA Index System. The concept behind CODIS is to create a database of the States' convicted offender profiles to help solve violent crimes for which there are no suspects. CODIS enables Federal, State, and local forensic laboratories to exchange and compare DNA profiles electronically, thereby linking serial violent crimes to each other and to known offenders. CODIS uses two indexes to generate investigative leads in crimes where biological evidence is recovered from the crime scene. The Convicted Offender Index contains profiles of individuals convicted of felony offenses and other crimes. The Forensic Index contains DNA profiles developed from crime scene evidence, such as semen stains or blood.
This investment began in 1990 and is scheduled to be completed by January 2010.
CODIS Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Business Case Study | FY 2008 Full Business Case | Dec 2005 | 467 |
Privacy Impact Assessment | Privacy Impact Assessment, National DNA Index System (NDIS) Database | Oct 2004 | 471 |
Risk Management Plan | Risk Management Plan, CODIS, Draft Version 01 |
May 2006 | 473 |
Acquisition Plan | Single Acquisition Management Plan for the Combined DNA Index System | Feb 2006 | 475 |
Project Plan | Product Management Plan, CODIS Bridge Contract Extension | Sep 2005 | 472 |
Security Plan | System Security Plan, CODIS | Jan 2005 | 476 |
Contingency/Continuity Plan | Three Part Contingency Plan, CODIS Bridge Contract Extension | Oct 2005 | 477 |
Data Centers Unit
Federal Bureau of Investigation
The Data Centers project began spending funds in FY 2004. The project consists of: (1) operations and maintenance of installed computing platforms, data storage devices, and a channel extension network; (2) modernization of computing platforms, operating systems, data storage devices, and channel extension; (3) enhancement of existing hardware / software (for example, for storage expansion, greater processing capacity, process improvement, and systems integration); and (4) periodic development for new technology or projects such as robotic tape libraries and channel extension (past) and an enterprise backup solution (future). The mission of the Data Centers Unit is to provide an IT infrastructure and effective, efficient, and timely technical support that is the foundation for supporting the FBI's priorities. The major goal of the Data Center Unit is to provide continuous, effective automated production workload support and business continuity for all FBI investigative and administrative missions.
DCU Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Business Case Study | OMB Exhibit 300 for BY 2008 | Jul 2005 | 489 |
Project Plan | Contribution of the Mainframe to the Bureau's Mission, FBI | Feb 2006 | 481 |
Project Plan | Project Plan, Global Mirroring Project | Dec 2005 | 490 |
Security Plan | System Security Plan, FBI, Enterprise Servers, Version 1.2 | Oct 2004 | 492 |
Contingency/Continuity Plan | Continuity of Operations Plan, FBI, ITOD, Operations Section | Jan 2005 | 480 |
Performance Evaluation | Project Summary Report, ITOD Mainframe System Upgrade | 491 |
Digital Collection System
Federal Bureau of Investigation
The Digital Collection project began spending funds in FY 1997. Digital Collection consists of the DCS-3000, DCS-5000, and DCS-6000, which provide digital collection tools, foreign counterintelligence gathering, and law enforcement evidence collection, respectively.
DCS Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Business Case Study | OMB Exhibit 300 for BY 2008 | Aug 2006 | 1024 |
Privacy Impact Assessment | Privacy Impact Assessment, SPIDERNET and DIGITAL STORM | Aug 2001 | 510 |
Privacy Impact Assessment | Privacy Impact Assessment, Upgrade from SPIDERNET to Red Wolf | Dec 2005 | 511 |
Risk Management Plan | Risk Assessment and Management Plan (RAMP), DCS-6000, Systems Security Plan, Appendix L, Version 2.0 | May 2006 | 521 |
Project Plan | Project Plan, Digital Collection System, Digital Collection - 05 | Nov 2004 | 516 |
Project Plan | Project Plan, Digital Collection, Digital Collection - 03 | Aug 2003 | 517 |
Project Plan | Project Plan, Digital Collection, Digital Collection - 04 | Jan 2004 | 518 |
Project Plan | Project Plan, Digital Storm | Jun 1998 | 519 |
Security Plan | System Security Plan, DCS 3000, Version 2.0 | Apr 2006 | 524 |
Security Plan | System Security Plan, DCS-5000, Revision 3.5 | Dec 2005 | 525 |
Security Plan | System Security Plan, DCS6000 Voice Box III, Version 3.1 | May 2006 | 526 |
Test Plan | Test Plan, Digital Storm, Version 1.0 | Feb 1999 | 527 |
Performance Evaluation | Project Status Report, DCS-5000 | Jun 2006 | 520 |
Post-Implementation Evaluation | Phase Review Report, Phase 1/2, Project Digital Storm, | Aug 1998 | 509 |
Post-Implementation Evaluation | Project Closeout Report, Digital Collection - 04, Version 1.1 | Jul 2005 | 514 |
Today's information technology capabilities afford terrorists and criminals many avenues to coordinate and commit offenses against US citizens and interests. Traditional phones were the primary avenue criminals used to communicate information regarding unlawful acts. Today, more incidents are committed and facilitated by terrorists using high-tech, non traditional communications methods. Communications methods are dramatically increasing in number and complexities, resulting in the continual and evolving need for advanced methods of electronic surveillance of voice communications - methods of electronic surveillance have limited-life utility in intercepting newer, more secure types of publicly offered communications.
The expansion of electronic surveillance activity in frequency, sophistication, and linguistic needs continues to increase the level of support required. An important factor behind this expansion is the changing demographic of targets that must be monitored by investigators. The FBI must supply equipment and analytical tools to uniquely qualified language specialists to speed the translation and transcription process to meet the investigators' needs. Further, the life span of today's technology is often much shorter than older technologies, resulting in more frequent need for solution development. Terrorist and criminal activity has expanded across international boundaries. Current United States-based intercept technologies and collection capabilities are not always sufficient to meet global requirements. Increased coordination and cooperation with other government agencies and governments of other countries place are needed.
Digital collection must continue to clearly define electronic surveillance requirements and closely track manufacturers' approaches and solutions. Collection equipment manufacturers continue toward complying with technical standards as a result of the Communications Assistance to Law Enforcement Act (CALEA). One result of the CALEA standard is more information is available for collection. This increase in data coupled with the increased complexity of computer-based electronic surveillance information management systems will impose a requirement for efficient distribution to users and their respective collection systems.
Electronic Surveillance Data Management System
Federal Bureau of Investigation
The Electronic Surveillance (ELSUR) Data Management System (EDMS) project began spending funds in FY 2004. The system ensures the timely and proactive collaboration, analysis, and integration of Title III and Foreign Intelligence Surveillance Act (FISA) intelligence and evidence collected from lawfully authorized digital intercepts and seizures.
EDMS Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Business Case Study | OMB Exhibit 300 for BY 2007 | Sep 2005 | 540 |
Business Case Study | OMB Exhibit 300 for BY 2008 | Aug 2006 | 1025 |
Privacy Impact Assessment | Privacy Impact Assessment (PIA), Draft | Sep 2005 | 529 |
Risk Management Plan | Risk Management Plan, EDMS | Aug 2000 | 547 |
Risk Management Plan | Risk Management Plan, EDMS, Version 3.0 | 548 | |
Project Plan | Project Plan, Project EDMS (ELSUR Data Management System) | Feb 2004 | 544 |
Security Plan | System Security Plan, EDMS, version EDMS SSP Rev. 2.0 | Apr 2004 | 553 |
Configuration Management Plan | Configuration Management Plan, Revision b | Sep 2005 | 532 |
Test Plan | Certification Test Plan | Apr 2004 | 531 |
Test Plan | Test and Evaluation Master Plan, EDMS, Revision A | Aug 2005 | 555 |
Conversion Plan | Target EA and Transition, EDMS Enterprise Architecture, Executive Summary, Version 1.0 | Jan 2005 | 554 |
Contingency/Continuity Plan | Continuity of Operations Plan | Apr 2004 | 533 |
Performance Evaluation | EDMS Briefing for the FBI Science and Technology Advisory Board | Jul 2005 | 536 |
Performance Evaluation | Project Status Report, ELSUR EDMS | Apr 2006 | 546 |
Performance Evaluation | Department Investment Review Board | 535 | |
Performance Evaluation | Monthly Project Status Reporting | 543 |
EDMS integrates and consolidates ELSUR products, such as wiretaps, telephone, email, and seized media from multiple field collection systems. As ELSUR products are consolidated into EDMS, the system performs multiple functions, including indexing, data minimization (for legal compliance), language translation, data prioritization, and other functions. Most importantly, EDMS provides the capability for agents, translators, and analysts to have increased access to many types of ELSUR data extracted from multiple collection sources to view and analyze within a single system. This significantly increases the FBI's ability to manage, analyze, and share ELSUR products and greatly improves the efficiency with which investigators can develop leads and intelligence through integrating best-of-breed automated and interoperable data analysis capabilities.
While providing significant tactical value, EDMS cannot continue to support the FBI's counterintelligence and counterterrorism mission objectives as it currently exists due to the increase in data collection volume and user base. Since October 2004, EDMS experienced a 300 percent increase in average users per month. Over the past 3 years, the volume of ELSUR collections has grown over 62 percent for audio wire-taps and over 3,034 percent for digital collections such as email and seized media. The current system is unable to scale and meet these growing demands. Because of the increased burden, the ability to share ELSUR data and collaborate efficiently with other authorized federal, state, local law enforcement and federal intelligence agencies will no longer be feasible unless the proposed enhancements are implemented.
The budget year 2008 primary objectives are to: provide additional disk capacity to support current and anticipated storage needs; enhance current system security controls to adequately protect data; upgrade interfaces and data loaders to provide for increases in data volume inputs and more efficiently manage data; and acquire additional software licenses and processors to accommodate anticipated increase in users.
Foreign Terrorist Tracking Task Force
Federal Bureau of Investigation
In 2001, Homeland Security Presidential Directive-2 established the Foreign Terrorist Tracking Task Force (FTTTF) to provide actionable intelligence to law enforcement to assist in the location and detention and ultimate removal of terrorists and their supporters from the US.
In 2005, a White House Memorandum on Strengthening the Ability of the Department of Justice to Meet Challenges of the Security of the Nation directed the Attorney General to establish a "National Security Service" and to combine the missions, capabilities, and resources of the counterterrorism, counterintelligence, and intelligence elements of the FBI under the leadership of a senior FBI official. As a result, the FBI created the National Security Branch. This Branch will enable FBI to meet information sharing Presidential Guidelines and Initiatives such as the Intelligence Reform and Terrorism Prevention Act of 2004.
FTTTF Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Business Case Study | OMB Exhibit 300 for BY 2008 | Dec 2006 | 1026 |
Risk Management Plan | Risk Management Plan, Guardian, Version 1.0 | Apr 2006 | 565 |
Project Plan | Project Management Plan (Software Development Plan), Guardian 2.0, Version 9.0 | Mar 2006 | 564 |
Systems Engineering Management Plan | System Engineering Management Plan, Guardian, Draft Version 11.0 | Mar 2006 | 567 |
Test Plan | Test and Evaluation Master Plan, Guardian, Version 1.0 | Mar 2006 | 568 |
Implementation Plan | Installation Plan, Guardian 2, Draft Version 5.0 | Apr 2006 | 561 |
In FY 2006, an FBI assessment determined that existing HPSD-2 national security and counterterrorism operations would be enhanced by providing analysis and technology support by capitalizing on FTTTF's existing operations in line with FBI's Enterprise Architecture. This will enable multiple Divisions to consolidate technological and analytical resources to support the combined activities of the counterterrorism, counterintelligence, and intelligence elements of the FBI. As part of this mission, the National Security Branch must deliver new analytical capabilities and operational products (such as activity reports, records, and information), real-time to State, local law enforcement, Tribal, FTTTF, National Counterterrorism Center, and other agencies. This data warehousing for search and retrieval capability will leverage best information and querying practices for information sharing through FBI's architecture and electronic directory services across domains. These technological solutions will increase the efficiency in sharing information with State, local and Tribal law enforcement and make it easier for the FBI to access and analyze the information. This solution supports consolidation of resources to combine activities of the counterterrorism, counterintelligence, and intelligence elements of the FBI.
The FTTTF project began spending funds in FY 2005. This FY 2008 justification is designed to address the core IT strategy of the FTTTF and the National Security Analysis Center (NSAC) while providing the framework for integration into the National Security Branch’s Analytical Capabilities Program. This IT enhancement will support the core strategy of the NSB.
Integrated Automated Fingerprint Identification System
Federal Bureau of Investigation
The Integrated Automated Fingerprint Identification System (IAFIS) is a rapid, electronic fingerprint identification and criminal history system that responds to law enforcement agencies within two hours and to authorized civil agencies within 24 hours. Prior to the IAFIS, fingerprint identification was a manual, labor-intensive process which took weeks or months to complete. The IAFIS provides identification, image exchange, and criminal history services to more than 80,000 law enforcement agencies and qualified civil agencies. The IAFIS is internationally recognized as the biometric system leader and contains the largest fingerprint repository in the world.
IAFIS Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Business Case Study | OMB Exhibit 300 for BY 2008 | Aug 2006 | 1027 |
Security Plan | Operational System Security Plan, AFIS | Jan 1999 | 588 |
Security Plan | System Security Plan, IAFIS, Version 2.1 | Mar 2006 | 591 |
Systems Engineering Management Plan | Systems Engineering Management Plan, Criminal Justice Information Services Division | Jul 2005 | 592 |
Systems Engineering Management Plan | Systems Engineering Management Plan, SoSSS, Revision 2.2 Final | Nov 2005 | 593 |
Configuration Management Plan | Configuration Management Plan, Criminal Justice Information Services Division, Revision1.2 | Aug 2002 | 582 |
Quality Assurance Plan | Quality Assurance Plan, CJIS Division | Mar 2005 | 589 |
Verification/Validation Plan | Independent Verification, Validation & Testing (IVV&T) SOW, CJIS Division | Nov 1993 | 586 |
Test Plan | Build E System Integration and Test Plan (SITP), IAFIS | Jan 1998 | 577 |
Test Plan | IAFIS System Acceptance Test Plan, Volume 1 | Feb 1999 | 584 |
Conversion Plan | Transition Plan, IAFIS, Second Iteration | Apr 1998 | 596 |
Conversion Plan | Transition Plan, IAFIS, Third Iteration | Oct 1998 | 597 |
Implementation Plan | Build D Installation Plan | Nov 1997 | 574 |
Implementation Plan | Build E Installation Plan | Apr 1998 | 576 |
Implementation Plan | Build F Installation Plan | Mar 1998 | 579 |
Implementation Plan | Build F Installation Plan (CWV Draft 3, as Built) | Jun 2000 | 580 |
Implementation Plan | Early Build C Installation Plan | May 1997 | 583 |
Training Plan | ITN Training Plan | Jul 1999 | 587 |
Training Plan | Training Plan, AFIS | Nov 1998 | 595 |
Test Report | Build C Test Report, Volume 1 | Aug 1997 | 573 |
Test Report | Build D Test Report, Volume 1 | Dec 1997 | 575 |
Test Report | Build E Test Report, Volume 2 | May 1998 | 578 |
Test Report | Build F1 Test Report, Volume 1 | May 1999 | 581 |
Test Report | IAFIS System Acceptance Test Report | Aug 1999 | 585 |
The IAFIS was deployed in July 1999 based on 12-year old technology. The IAFIS is operating satisfactorily at this time; however, due to increased demand for new and existing services continual upgrades are necessary. Workload projections for FY 2008 are expected to exceed 168,000 fingerprint submissions per day. The current IAFIS design capacity is 170,000 per day. The following IAFIS enhancements are planned for FY 2008: (1) additional system capacity due to increased fingerprint submissions; (2) additional system capacity related to processing of flat fingerprint submissions in support of the Department of Homeland Security' need to expedite fingerprint processing at Ports of Entry; and (3) the automation manual processes related to update of criminal history records to streamline and improve existing services and offer new services. Additionally, four regularly scheduled IAFIS Builds occur each year for defect correction and system enhancements. Requests for change to the IAFIS baseline may be initiated internally or externally at the request of contributing agencies.
Congressional mandates, such as, the USA PATRIOT Act of 2001, the Enhanced Border Security and Visa Entry Reform Act of 2001, the DOJ Entry/Exit Border Security Proposal, propose new applications for the fingerprint-based identification services provided by the FBI's IAFIS. To achieve the goals outlined in these Acts and Proposals, enhancements to existing IAFIS functions and the development of new IAFIS related capabilities are required.
Information Assurance Technology Infusion
Federal Bureau of Investigation
IATI Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Business Case Study | Feasibility Study, IATI Program, CARA, Version 1.0 |
Mar 2005 | 605 |
Business Case Study | OMB Exhibit 300 for FY 2008 | Mar 2006 | 612 |
Privacy Impact Assessment | Privacy Impact Assessment, CARA | Apr 2006 | 613 |
Risk Management Plan | Risk Management Plan (RMP), Technology Infusion Program, Version .8 | Nov 2003 | 616 |
Project Plan | Program Management Plan, Technology Infusion Program, Volume I, Version .19 | Nov 2003 | 614 |
Security Plan | Security Attachment to the FBI System Security Plan (SSP), IATI Program, IODM, Version 2.0 | May 2006 | 619 |
Security Plan | System Security Plan (SSP), IATI Program, CARA, Version 6.0 | May 2006 | 623 |
Security Plan | System Security Plan (SSP), IATI, SSIAC, SAE, Version 7.0 | Mar 2006 | 624 |
Systems Engineering Management Plan | System Engineering Master Plan, IATI Program, Version 1.0 | May 2004 | 621 |
Configuration Management Plan | Configuration Management Plan (CMP), Technology Infusion Program (TI), Volume 1, Version 0.5 | Nov 2003 | 602 |
Quality Assurance Plan | Quality Assurance Plan (QAP), IATI, Volume 1, Version .9 | Nov 2003 | 615 |
Test Plan | System Test Plan, IATI Program, CARA, Version 3.0 | Jan 2006 | 625 |
Test Plan | Test and Evaluation Master Plan (TEMP), IATI, Draft | Apr 2004 | 626 |
Test Plan | Test Plan, IATI Program, IODM, Version 3.0 | May 2006 | 627 |
Conversion Plan | Transition Plan, IATI Program, CARA, Version 1.0 |
May 2006 | 629 |
Implementation Plan | Installation Plan, IATI Program, IODM, Version 2.0 |
May 2006 | 608 |
Implementation Plan | System Installation Plan, IATI Program, CARA, Version 3.0 | May 2006 | 622 |
Training Plan | Training Plan, IATI Program, CARA, Version 2.0 |
Apr 2006 | 628 |
The Information Assurance Technology Infusion (IATI) Program was initiated and began spending funds in FY 2005; the system implementation was completed in FY 2006. IATI is a Security Division initiative to design, develop, assess, and implement security technology safeguards in the FBI’s IT enterprise to mitigate risks to and reduce vulnerabilities of the Bureau’s most critical information assets. IATI provides resources for research, evaluation, design, development, implementation, and operations and maintenance of IT security solutions that enhance the security for the Federal Bureau of Investigation’s 340 plus information systems. Many of these systems directly enable the information sharing requirements for Intelligence, Counterterrorism, and operational missions.
Investigative Data Warehouse
Federal Bureau of Investigation
The FBI’s Investigative Data Warehouse (IDW) began spending funds in FY 2002, and system implementation was completed in FY 2005. The IDW system provides data storage, database management, search, information presentation, and security services allowing FBI investigative and analytical personnel to access aggregated data previously only available through individual applications. The IDW system is the successor to the Secure Collaboration Operational Prototype Environment (SCOPE), which originally was named the Secure Counter-terrorism Operational Prototype Environment.
The IDW receives, stores, processes data in a heterogeneous computing environment of UNIX and Windows Servers. Data processing is conducted by a combination of Commercial-Off-the-Shelf (COTS) applications, interpreted scripts, and open-source software applications. Data storage is provided by several Oracle Relational Database Management Systems (DBMS) and in proprietary data formats. Physical storage is contained in Network Attached Storage (NAS) devices and component hard disks. Ethernet switches provide connectivity between components and to FBI LAN/WAN. An integrated firewall appliance in the switch provides network filtering.
Users of the system are FBI investigative, analytical, and intelligence personnel. These personnel are both FBI employees and contractors. Administrators of the system are FBI IDW program contractors. Users are permitted to access the system from FBI accredited facilities in the United States of America. IDW is not available to FBI Legal Attaché offices.
IDW Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Risk Management Plan | Risk Management Plan, IDW, Version 1.0 | Feb 2005 | 631 |
Security Plan | System Security Plan, IDW, Version 2.0 | May 2006 | 633 |
Conversion Plan | Transition and Deployment Plan, IDW | Jun 2004 | 636 |
Training Plan | Training Management Plan, IDW | Jun 2004 | 635 |
Test Report | Test & Evaluation Test Analysis Report (TETAR) for IDW, Version 1.1 | Jul 2004 | 634 |
Law Enforcement Online
Federal Bureau of Investigation
LEO is a 24-hours-a-day, 7-days-a-week, on-line, controlled-access communications and information-sharing data repository. It provides an Internet-accessible focal point for electronic Sensitive But Unclassified (SBU) communications and information sharing for the federal, state, local and tribal law enforcement agencies. LEO also supports anti-terrorism, intelligence, law enforcement, criminal justice, and public safety communities nationwide. User anywhere in the world can communicate securely using LEO. LEO is accessed by vetted and authorized entities using industry-standard personal computers equipped with any standard Internet browser software. LEO currently supports a user base of over 40,000 individuals, who access LEO either via the Internet, dialup, or other dedicated connections. In addition to the current LEO user base, there are 17,000 potential Regional Information Sharing Systems (RISS) users who may have the ability to access LEO. LEO operates as SBU network under the Computer Security and Privacy Acts. In summary, LEO provides a mechanism for law enforcement entities to share data internally and externally.
LEO Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Business Case Study | OMB Exhibit 300 for BY 2008, CEI | 1017 | |
Project Plan | Implementation Plan for the LEO System Relocation of Primary Operations to the CJIS Division | May 2006 | 643 |
Project Plan | Project Management Plan, LEO, Relocation and Reengineering Project | Jun 2006 | 653 |
Security Plan | FBI LEO System Security Plan, dated 9 June 2006 |
Jun 2006 | 642 |
Configuration Management Plan | LEO Configuration Management (CM) Processes, dated 21 June 2004 | Jun 2004 | 647 |
Test Plan | System Test Plan, LEO System Relocation of Primary Operations to the CJIS Division (Final Draft) | Jun 2006 | 657 |
Conversion Plan | Transition Plan, LEO System Relocation of Primary Operations to the CJIS Division (Final Draft) | Jun 2006 | 659 |
Implementation Plan | Installation Plan, LEO System Relocation of Primary Operations to the CJIS Division (Final Draft) | Dec 2005 | 644 |
Contingency/Continuity Plan | IT Contingency Plan, LEO, Version 1.0 (Draft) | May 2006 | 645 |
National Crime Information Center
Federal Bureau of Investigation
The National Crime Information Center (NCIC) is a computerized criminal justice information system available 24 hours a day, 365 days a year. NCIC is accessed by over 6 million Federal, State, and Tribal entities, including the Department of Homeland Security and the Department of Defense. The NCIC database consists of 18 files, including seven property files and eleven person files.
NCIC Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Business Case Study | OMB Exhibit 300 for BY 2008 | Aug 2006 | 1028 |
Risk Management Plan | Risk Management Plan for NCIC 2000, \Revision 2 | Feb 1996 | 684 |
Project Plan | Plan for Early Delivery of the FMS Subsystem, NCIC 2000 Program | Apr 1997 | 682 |
Security Plan | System Security Plan (SSP), NCIC | Jul 2006 | 688 |
Systems Engineering Management Plan | System Engineering Management Plan for NCIC 2000 |
May 1996 | 687 |
Configuration Management Plan | Configuration and Data Management Plan for NCIC 2000 | Feb 1998 | 669 |
Test Plan | Maintainability Test Plan and Procedure for NCIC 2000 | May 1999 | 675 |
Test Plan | Maintainability Test Plan for NCIC 2000 | Feb 1994 | 676 |
Test Plan | Successive Level Integration Test Plan for NCIC 2000 |
Jul 1996 | 686 |
Test Plan | Test and Evaluation Master Plan for NCIC 2000 | Mar 1996 | 690 |
Conversion Plan | Preliminary Transition Plan for NCIC,Volume I of VII, Transition Overview | Apr 1997 | 693 |
Conversion Plan | Transition Plan for NCIC 2000 | Aug 1998 | 691 |
Implementation Plan | Facility Requirements and Installation Plan for NCIC 2000 | Jul 1998 | 670 |
Training Plan | Personnel Requirements and Training Plan for NCIC | Nov 1998 | 681 |
Test Report | External Interface Checkout Test Report for NCIC 2000 | May 1999 | 665 |
Test Report | Fingerprint Matching Subsystem Beta Test Report, NCIC 2000 | May 1999 | 672 |
Test Report | FMS Reintegration Test Report for NCIC 2000 | Mar 1999 | 673 |
Test Report | Maintainability Test Report for NCIC 2000 | Jun 1999 | 677 |
Test Report | NCIC 2000 Security Certification and Testing Analysis | Jul 1999 | 678 |
NCIC also contains the Originating Agency Identifier (ORI) file. The NCIC ORI File contains contact information, such as the agency's address and telephone number, for agencies that have an ORI. The NCIC may also be used to search and retrieve the criminal history records of 50 subjects.
The NCIC is considered a Sensitive But Unclassified system and is subject to all DOJ and FBI policy, standards and practices governing the collection and dissemination of SBU data. Access to the NCIC system is controlled at the agency level by ORI. Authorized users are authenticated by user ID and password. Users are also required to be trained and tested on NCIC policy and practices.
The NCIC is an invaluable tool that aids law enforcement and criminal justice agency officials in the successful completion of their day-to-day operations and protect the United States from terrorist attack. The Terrorist Screening Center enters terrorist information in the Violent Gang and Terrorist Organization File (VGTOF) and maintains the documentation to support the terrorist watch-list. Additionally, the National Counterterrorism Center, the Joint Terrorism Task Forces, and the Field Intelligence Groups have electronic access to NCIC through their respective CJIS System Agency. Federal, State, local and tribal entities may search and retrieve VGTOF, and other person records, electronically by name, and a unique numeric identifier such as date of birth. Records may also be obtained as a result of a query of the Wanted Person File and Stolen Vehicle File. Finally, NCIC will send a notification to the Terrorist Screening Center whenever a fingerprint search results in a hit on a VGTOF record.
NCIC is in the operations and maintenance phase of the Life Cycle Management Directive. In FY 2008, the FBI CJIS Division will continue to upgrade hardware that has reached the end of its life-cycle and add new services such as an enhanced ad hoc search capability.
Law Enforcement National Data Exchange
Federal Bureau of Investigation
Information sharing is mission critical to today's public safety mandate. Most law enforcement agencies (LEAs) utilize some type of computerized data base to collect incident and investigative information. Moving this data across jurisdictional boundaries into the hands of those who need to know is a significant challenge. The Law Enforcement National Data Exchange (N-DEx) concept is to take the data provided by LEAs and criminal justice agencies and convert it into valuable information to fight crime and terrorism. N-DEx services extract specific information on people, places, things, the relationship between them, as well as crime characteristics such as MO's and criminal signatures.
N-DEx will: (1) share complete, accurate, timely and useful criminal justice information across jurisdictional boundaries and provide new investigative tools that enhance the United States’ ability to fight crime and terrorism; (2) provide fusion centers, the National Counterterrorism Center, Field Intelligence Groups, Joint Terrorism Task Force, and other agencies with access to N-DEx capabilities and services; (3) check all new suspects entered into the system against terrorist watch lists or notify/alert users of addresses that are known to be associated with other suspected terrorists; (4) provide the capability to share sensitive investigative information while simultaneously protecting the investigative equities of proprietary information; (5) provide an electronic catalog of structured criminal justice information that provides a single point of discovery to assist in locating terrorism information and people with relevant knowledge about that information; (6) leverage its national connectivity environment to create a directory of LEAs and users to facilitate new methods of law enforcement collaboration relevant to cases, investigations, or discovered data describing terrorist activity; and (7) provide advance search capabilities to discover information when there is a lack of key information for conducting a typical query search. N-DEx will provide insights into previously unknown terrorist activity through automated discovery of patterns and linkages to detect and deter crime and terrorism.
N-DEx Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Business Case Study | OMB Exhibit 300 for BY 2008 | Dec 2006 | 1029 |
Privacy Impact Assessment | Privacy Impact Assessment, N-Dex | Mar 2006 | 1386 |
Risk Management Plan | Risk Management Plan, Law Enforcement N-DEx, Version 1.4 |
Aug 2006 | 700 |
Project Plan | Program Plan, Law Enforcement N-Dex | Jul 2006 | 699 |
Security Plan | System Security Plan Attachment H - Risk Assessment, N-Dex Prototype, Version 1.1 | Jun 2004 | 702 |
Test Plan | Certification Test Plan, N-DEx | Oct 2004 | 694 |
Next Generation Identification
Federal Bureau of Investigation
The Next Generation Identification (NGI) project began spending funds in FY 2005. The project will be a major upgrade to the current Integrated Automated Fingerprint Identification System (IAFIS) that will provide new functionality, as well as improve upon current functionality. The NGI was included in a previous IAFIS OMB 300 submission because it is a major upgrade to the existing IAFIS. In 2005, the NGI was separated from the IAFIS exhibit 300 for management control purposes based on guidance from the FBI's Office of the Chief Information Officer.
NGI Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Business Case Study | OMB Exhibit 300 for BY 2008 | Aug 2006 | 1030 |
Privacy Impact Assessment | PIA, Advanced Fingerprint Identification Technology (AFIT) | 719 | |
Privacy Impact Assessment | PIA, Enhanced IAFIS Repository | 720 | |
Privacy Impact Assessment | PIA, Interstate Photo System (IPS) | 721 | |
Privacy Impact Assessment | PIA, National Palm Print System (NPPS) | 722 | |
Risk Management Plan | Risk Management Plan, NGI | Nov 2005 | 729 |
Project Plan | Project Management Plan, NGI, Version 1.0 | Jan 2006 | 726 |
Configuration Management Plan | Configuration Management Plan, NGI | Apr 2006 | 709 |
Quality Assurance Plan | Quality Assurance Plan, NGI | May 2006 | 727 |
Performance Evaluation | Investment Management/Project Review Board | Feb 2006 | 713 |
Performance Evaluation | Program Management Review | May 2006 | 725 |
The NGI Program is a compilation of initiatives that will either improve or expand existing biometric identification services. The NGI Program will accommodate increased information processing and sharing demands in support of anti-terrorism. As a result of the NGI initiatives, the FBI will be able to provide services to enhance interoperability between stakeholders at all levels of government, including local, state, federal, and international partners. This will accommodate the increasing need for pre-employment background checks, licenses, and will support the increase in border patrol and entry/exit checks. The NGI will allow the FBI to: establish a terrorist fingerprint identification system that is compatible with other systems; increase the accessibility and number of the IAFIS terrorist fingerprint records; and provide latent palm print search capabilities.
The NGI Study Contract was awarded to Intellidyne, L.L.C. on July 1, 2005. Intellidyne, L.L.C. and CJIS NGI representatives jointly participated in User Requirements Canvasses which included onsite interviews, telephonic interviews and written surveys resulting in the identification of over 1,000 new requirements, including high-priority, specialized requirements in the Latent Services, Facial Recognition, and Multi-modal Biometrics areas.
National Instant Criminal Background Check System
Federal Bureau of Investigation
The National Instant Criminal Background Check System (NICS) prevents the transfer of a firearm to persons who are prohibited from possessing or receiving a firearm while allowing the timely transfer to those individuals that are not prohibited. Title 18, Section 922 of the United States Code defines who is prohibited from shipping, transporting, possessing, or receiving any firearm or ammunition in or affecting commerce. The NICS was created through the collaborative efforts of the FBI; the Bureau of Alcohol, Tobacco, Firearms and Explosives; the Department of Justice; local, state, and other federal law enforcement agencies; and private contractor support.
NICS Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Business Case Study | OMB Exhibit 300 for BY 2008 | Dec 2006 | 1031 |
Security Plan | System Security Plan, NICS/ FBI | May 1998 | 746 |
Configuration Management Plan | Configuration Management Plan, CJIS Division, Revision 1.2 | Aug 2002 | 732 |
Quality Assurance Plan | Quality Assurance Plan, CJIS Division | Mar 2005 | 743 |
Test Plan | Certification Test Plan, NICS/E-Checks/NICS Call Center | Sep 2005 | 730 |
Test Plan | Formal Qualification Test Plan, NICS | Jul 1998 | 737 |
Test Plan | System Test Plan, NICS Efficiency Upgrade Project, Draft | Jun 2003 | 747 |
Conversion Plan | NICS Rehost Transition Plan | May 2004 | 742 |
Conversion Plan | Transition Plan NICS Efficiency Upgrade Project | Oct 2003 | 749 |
Implementation Plan | Installation Plan, NICS | Jun 1998 | 740 |
Implementation Plan | NICS Efficiency Upgrade Installation Plan, Draft | Sep 2003 | 741 |
Implementation Plan | Superdome System Administration and Installation Cookbook, NICS [Rehost] | Jul 2005 | 745 |
Implementation Plan | Windows 2003 Server Installation Cookbook, NICS, Revision 3.0 [Efficiency Upgrade] | Mar 2006 | 750 |
Contingency/Continuity Plan | Contingency Plan, NICS | Dec 2001 | 733 |
Contingency/Continuity Plan | Contingency Plan, NICS and E-Check | Sep 2005 | 735 |
Test Report | Formal Qualification Test Report, NICS | Oct 1998 | 739 |
The NICS Regulation, Title 28, Code of Federal Regulations, Part 25, Subpart A requires the NICS to provide Federal Firearms Licensees (FFL) with an immediate response regarding the person for whom the receipt of a firearm would violate the Code. Additionally, if the initial response is a "delay," the NICS is required to provide the FFLs with a "proceed" or "deny" response within three business days. The NICS Regulation provides the states with the option to act as a point of contact (POC) for NICS transactions and allows the FBI to serve as the POC in those states that have chosen not to perform the checks. There are currently 13 full POC states/territories, eight partial POC state/territories, and 35 non-POC state/territories.
The NICS Regulation required development of other electronic means of contact as an alternative to the telephone. Therefore, the NICS E-Check was developed. This function enables the FFLs to initiate an unassisted NICS background check for firearm transfers via the Internet. When the FFLs conduct a NICS check, a name search is conducted for matching records in the following three databases: (1) the National Crime Information Center, which contains information on wanted persons; (2) the Interstate Identification Index, which contains criminal history records; and (3) the NICS Index, which contains the names of prohibited persons as outlined in the Brady Act.
During FYs 2006 and 2007, the NICS will undergo an extensive Business Process Re-design study to seek opportunities to improve the NICS services. FY 2008 funding will be used to finalize the results of the study, provide project management and business case support and conduct requirements development efforts.
Multi-Agency Information Sharing Initiative Regional Data Exchange
Federal Bureau of Investigation
The Multi-Agency Information Sharing Initiative (MISI) Regional Data Exchange (R-DEx) project began spending funds in FY 2005. The R-DEx is designed to provide the capability to share full text investigative information from federal, state, and local investigative agencies. R-DEx will provide searching, link analysis, and geo-spatial capabilities to aid investigators, analysts, and managers in analyzing criminal activity. It will facilitate the elimination of suspects, setting leads, and establishing linkages in cases that wouldn't otherwise occur. R-DEx is being developed in four phases. Phase I was the development of the concept of Operations, System Requirements Document, and Tool Suite that meets those requirements. Phase II was the implementation of the system as an operational prototype in St. Louis, San Diego, and Seattle. Phase III was the implementation of up to ten additional sites.
The DOJ Law Enforcement Information Sharing Program (LEISP) strategy facilities improved capabilities for law enforcement agencies to collaborate across agency, jurisdictional and geographic boundaries making that information available for use by all law enforcement agents. R-DEX fits into the LEISP data fusion category by co-mingling data on a regional level. R-DEX will provide for the collections and sharing of regional data between federal, state, local and tribal law enforcement agencies, regional FBI sites, and other federal law enforcement agencies. R-DEX development and deployment for Phase III will be coordinated with the DOJ/OCIO to ensure that development as a part of the FBI Information Sharing Initiative, designed to facilitate the sharing of information at the federal, state, and local levels, which provides an integrated approach to the development or upgrade of systems designed to share investigative information by providing powerful analytical tools for analyzing integrated datasets and making the information available to users at all levels of government. LEISP will: leverage existing system capabilities, architectural components, and business services where plausible; redirect the management and execution of projects where performance failures or weaknesses have been identified; and result in the development of a single enterprise wide information sharing architecture for the Department. LEISP is the critical DOJ-wide initiative to facilitate the sharing of what law enforcement knows about terrorism, criminal activity and threats to public safety.
R-DEx Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Business Case Study | OMB Exhibit 300 for BY 2008 | Dec 2006 | 1032 |
Risk Management Plan | Risk Assessment and Risk Management Matrix (RMM), RDEX, Version 1.0 | Jul 2005 | 662 |
Security Plan | System Security Plan, FBI Regional Data Exchange (R-DEx), Version 4.2 | May 2006 | 664 |
Test Plan | Certification Test Plan, R-DEx, Version 1.6 | Feb 2005 | 660 |
Test Report | Certification Test Report, R-DEx, Version 1.6 | Feb 2005 | 661 |
Sensitive Compartment Information Operational Network
Federal Bureau of Investigation
The Sensitive Compartment Information Operational Network (SCION) began spending funds in FY 2003. The FBI is working to strengthen its capabilities to detect, analyze, understand, expose, pre-empt, interdict, terminate, and prosecute terrorist activities before they can reach the stage of causing harm to the United States. SCION will enhance these capabilities by providing agents, counter-terrorism intelligence analysis, and their staffs with modern information processing/extraction tools and unified access to relevant and appropriate data sources at the TS/SCI level.
SCION is a common TS/SCI network providing FBI users with standard applications, data sharing, and through Joint Worldwide Intelligence Communication System (JWICS), access to other intelligence community information systems. SCION primarily supports the FBI Counter Intelligence (CI) and Counter-Terrorism (CT) divisions. SCION provides the means for the divisions to access raw intelligence and intelligence products, perform analysis, and to distribute intelligence product.
SCION Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Privacy Impact Assessment | Full Privacy Impact Assessment, TS/SCI LAN | Dec 2002 | 751 |
Security Plan | System Security Plan, SCION | Aug 2004 | 753 |
Configuration Management Plan | Configuration Management Plan, SCION | Dec 2003 | 752 |
Test Report | Certification Test Results, TS/SCI LAN | May 2003 | 754 |
Sentinel
Federal Bureau of Investigation
The Sentinel project began spending funds in FY 2005 with implementation projected for FY 2010 The FBI is implementing Sentinel to replace legacy systems and to provide improvements identified in the wake of the Oklahoma Bombing Case, the terrorist attacks of September 11, and the Hanssen Espionage Case.
The FBI’s investigative case management systems maintain more than 300,000 open and closed cases per year, which together contain more than 100 million text documents. However, only a subset of the information currently collected by the Bureau is being entered into the Automated Case Support (ACS) for FBI-wide access. ACS data entry processes are manually intensive, and a significant backlog for entering data into ACS exists in some locations. ACS has extremely limited capabilities for structuring the information collected by the FBI. Agents and analysts throughout the Bureau maintain case data and significant intelligence information off-line in their own internally developed or commercial-off-the shelf (COTS) applications that run on stand-alone desktops. The information residing in these systems is available only to those users that have direct system access.
SENTINEL Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Business Case Study | OMB Exhibit 300 for BY 2008 | Aug 2006 | 1033 |
Privacy Impact Assessment | Sentinel Phase 1 Privacy Impact Assessment | Feb 2006 | 1434 |
Risk Management Plan | Risk Management Plan, SENTINEL, Version 1.2 | Jul 2005 | 772 |
Acquisition Plan | Acquisition Plan (FD-911), SENTINEL, Version 2.0 |
Aug 2005 | 755 |
Acquisition Plan | Source Selection Plan, FBI Sentinel Program, Version 2.95 | Aug 2005 | 1037 |
Project Plan | Program Management Plan, SENTINEL, Version 1.2 |
Aug 2005 | 770 |
Systems Engineering Management Plan | Systems Engineering Management Plan (SEMP), SENTINEL | Jun 2005 | 776 |
Configuration Management Plan | Configuration Management Plan, SENTINEL PMO, Version 1.1 | Jul 2005 | 758 |
Quality Assurance Plan | Quality Management Plan, SENTINEL, Version 1.0 |
Jul 2005 | 771 |
Test Plan | Test and Evaluation Master Plan (TEMP), SENTINEL | Jul 2005 | 777 |
Performance Evaluation | Lessons Learned, Sentinel, Version 1.0 | Jul 2005 | 1039 |
Sentinel will put critical information in the hands of agents and analysts in the field. With few exceptions, Sentinel will provide its users with instantaneous access to all information entered into a case file. It will improve the collection and availability of information by allowing users to create electronic documents using web-based forms. Sentinel will include a multimedia capability that will rectify a longstanding information-sharing limitation with the FBI. Agents will be able to scan documents, photographs, and other electronic media into the case file, allowing evidence and other case-related information to be shared among agents working on a case without the need to exchange physical copies of the information
Security Management Information System
Federal Bureau of Investigation
The Security Management Information System (SMIS) project began spending funds in FY 2004. SMIS is a multi-year technology initiative employing knowledge management concepts hosted on an Enterprise Service Bus compliant with the FBI’s Service Oriented Enterprise Architecture to increase the ability of the FBI to develop, analyze, share, manage and store security related data in order to reduce risk to people, facilities, operations and information.
SMIS Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Business Case Study | OMB Exhibit 300 for BY 2007 | Jan 2006 | 797 |
Privacy Impact Assessment | Initial Privacy Impact Assessment, Polygraph Workflow Management Application | Aug 2005 | 791 |
Privacy Impact Assessment | Initial Privacy Impact Assessment, SMIS | Aug 2005 | 792 |
Privacy Impact Assessment | Privacy Impact Assessment, Security Division Implementation the Financial Disclosure Forms Analyzer | Feb 2006 | 798 |
Risk Management Plan | Risk Management Plan, SMIS, Final 1.1 | Dec 2005 | 817 |
Project Plan | Project Plan, SMIS Facilities Certification and Accreditation Component, Draft | Mar 2006 | 812 |
Project Plan | Project Plan, SMIS Financial Disclosure Forms Analyzer Component, Draft | Feb 2006 | 813 |
Project Plan | Project Plan, SMIS, Version 0.7, Draft | Jul 2005 | 814 |
Security Plan | System Security Plan, Financial Disclosure Forms Analyzer (FDF-A), Version 1.2 | Jan 2006 | 826 |
Security Plan | System Security Plan, Polygraph Workflow Management System | Apr 2006 | 827 |
Configuration Management Plan | Configuration Management Plan, SMIS, PMO, Version 1.0 | Jul 2005 | 785 |
Quality Assurance Plan | Quality Management Plan, SMIS, Version 1.0 | Jul 2005 | 815 |
Test Plan | Certification Test Plan, FDF-A | Jan 2006 | 782 |
Test Plan | Test and Evaluation Master Plan for the Polygraph Workflow Management Application | Aug 2005 | 829 |
Test Plan | Testing and Evaluation Master Plan Unit Testing and Traceability Matrix, SMIS FCA Application | Mar 2006 | 831 |
Training Plan | Training Plan for the Polygraph Workflow Management Application | Sep 2005 | 833 |
Test Report | Certification Test Report, FDF-A | Feb 2006 | 783 |
Test Report | Test Analysis Report for the Polygraph Workflow Management Application | Nov 2005 | 828 |
Performance Evaluation | Control Gate Review Exit Report, SMIS, FDF-A, Gate 6 - OAR | Mar 2006 | 786 |
Performance Evaluation | Investment Management/ Project Review Board (IMPRB), Summary Notes | Jan 2005 | 794 |
Performance Evaluation | Investment Management/ Project Review Board (IMPRB), Summary Notes | Aug 2005 | 793 |
The SMIS project will replace out-dated manual work processes and proliferating, stand-alone spreadsheets and databases with an efficient, cohesive, highly automated capability enabling authorized users to effectively and efficiently mine multiple security related applications, databases, and other electronically assimilated sources of relevant data to provide the Bureau with timely, actionable intelligence and security support information. Upon completion, SMIS will contain all security-related information for the entire professional life cycle of a person, facility or system. The enhanced capabilities will allow Security Division (SecD) to share selected information with other divisions, law enforcement entities, and the Intelligence Community (IC) in the most efficient manner.
Technical Refreshment Program
Federal Bureau of Investigation
The Technical Refreshment Program (TRP) project began spending funds in FY 2007. The program is an orderly and planned replacement of the FBI's technical assets associated with the FBI's FBINET and UNet enclaves, which are the primary backbones of the FBI's communications and operations. The TRP will follow the FBI's enterprise architecture technical reference model to support the technical framework. The standards, specifications, and technologies that support the delivery of service components and capabilities will be accomplished by replacing IT equipment at 20 percent per year.
The FBI has experienced information technology growth because of the new tasks forces, new data sharing initiatives, and new classified programs. The FBI currently has over 60,000 desktops, 27,000 laptops, 21,000 printers, and over 2,600 servers. The FBI requires funds to refresh and upgrade network components, enhance network functions, incorporate new network management software, and provide new features for monitoring and control. As mandated by OMB, the FBI will plan to upgrade all components to implement the FBI to IPv6 for network communications. Control and software tools will be constantly enhanced and integrated, and improve the ability of EOC personnel to manage the FBI's IT infrastructure. The improvements will enable the FBI to continue to improve the productivity and efficiency of the FBI's IT infrastructure. The program is chartered to replace aging and out of date IT Hardware to minimize obsolescence, in advance of loss of service or hardware failure. The impact, if not funded, will put the FBI at risk. This is due to the fact that the hardware cannot be serviced, as the IT industry will not support IT hardware beyond its 5th year of service.
TRP Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Business Case Study | OMB Exhibit 300 for BY 2008 | Dec 2006 | 1034 |
Performance Evaluation | Project Summary Report, TRP | 836 |
Terrorist Screening Center
Federal Bureau of Investigation
The Terrorist Screening Center (TSC) project began spending funds in FY 2004. The project was formed by the Department of Justice in response to Homeland Security Presidential Directive-6 (HSPD-6), dated 16 September 2003. The TSC originates and maintains the United States’ only consolidated terrorist identities database, participates in and explores ways to improve information sharing with all defense, national security, intelligence and law enforcement partners, as well as select foreign partners, and initiates and leads the Federal Search Working Group.
The TSC supports national security by providing information on both international and domestic terrorist identities on demand for agencies and/or Departments, including the Department of State, the Department of Homeland Security’s Customs and Border Protection and Transportation Security Administration, granting access on the basis of need-to-know to the limit prescribed by the originating agency of record. The TSC's links with many communities, including law enforcement at the state, local, tribal and territorial levels, are maintained around the clock.
TSC Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Business Case Study | OMB Exhibit 300 for BY 2008 | Dec 2006 | 1035 |
Risk Management Plan | Risk Management Plan, Terrorist Screening Center (TSC), Version 1.7 (Draft) | Apr 2006 | 845 |
Project Plan | TSDB Automated Ingest Project Plan | Apr 2006 | 849 |
Security Plan | System Security Plan, TSDB Phase 1B, Version 1.2 |
846 | |
Verification/Validation Plan | Independent Verification and Validation (IV &V) Plan, TSC | 848 | |
Test Plan | Independent Verification and Validation (IV &V) Plan, TSC | 848 | |
Test Plan | Test Management Plan, TSDB 1.7.1 | Mar 2006 | 847 |
Test Report | IV & V Test Report, TSDB 1.8.0.2, TSC | May 2006 | 843 |
The TSC's basic philosophy is of information sharing with all partner agencies, and participation in monthly information sharing sessions with partner agencies and foreign government representatives. The TSC hosts regular training for all employees, to include sensitive but unclassified classifications and privacy issues. Despite budget constraints, improvements in efficiency and functionality are ongoing and necessary to obtain the full scope of HSPD-6 and meet the mandate of the President's Management Agenda. The TSC uses the very latest search and retrieval technologies to meet these requirements, and is pioneering search technology in several areas, most notably search standards through development of a control database, search "cocktails" by the use of a combination of multiple search engines, and the federation of searches to search several databases at one time.
In budget year 2008, the TSC plans to develop an ability for external users to query the Terrorist Screening Database (TSDB), as well as a portal for external users to better reach and share and exchange information with the TSC call center, intelligence and nominations personnel. The query capability will be in production by early FY 2008, with the portal to follow. Future efforts will include improved data consumption of NCTC into the TSDB, deployment of biometric capability, planned hardware and software interface with DHS, Voiceprint and DNA data, and improved privacy and security features within EMA supporting TSDB.
Classified Information Technology Program
Justice Management Division
Components Involved: All components except FBI
CITP Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Market/Other Research | Enterprise Proof-of-Concept Functional Requirements, JSIT, Version 1.1 | Dec 2003 | 154 |
Business Case Study | Fiscal Year 2005 Information Technology Concept Paper | 158 | |
Business Case Study | OMB Exhibit 300 for BY 2006 | 173 | |
Privacy Impact Assessment | Initial Privacy Impact Assessment, JCON-S | 161 | |
Privacy Impact Assessment | Initial Privacy Impact Assessment, JCON-TS | 162 | |
Privacy Impact Assessment | Privacy Threshold Analysis, JCON-S | 175 | |
Privacy Impact Assessment | Privacy Threshold Analysis, JCON-TS | 176 | |
Risk Management Plan | Risk Assessment/Risk Matrix, JWICS | Dec 2003 | 180 |
Risk Management Plan | Risk Management Plan, Enterprise SIPRNET, Draft | Mar 2003 | 181 |
Risk Management Plan | Risk Management Plan, JIST, Version 1.0, Draft | Jul 2006 | 182 |
Acquisition Plan | Acquisition Plan, CITP, Version 1.0 | Jan 2006 | 142 |
Project Plan | MOA between JCON and DTO Regarding Operation and Support of the JCON Classified Infrastructure, Version 0.2, Draft | Dec 2003 | 171 |
Project Plan | Program Guide, JCON-S, Version 2.1 | May 2005 | 177 |
Security Plan | System Security Authorization Agreement (SSAA), JCON-S | Feb 2004 | 188 |
Security Plan | System Security Plan, JWICS Network, JCON-TS |
Dec 2003 | 189 |
Configuration Management Plan | Configuration Management Process, JCON-S, Appendix V, Version 1.1 | Dec 2003 | 147 |
Configuration Management Plan | Published Documents, Configuration Management Plan, JCON-S, Version 1.0 | May 2004 | 146 |
Verification/Validation Plan | Engagement Security Approach, JCON-S | 153 | |
Test Plan | Acceptance Test Plan and Report | Dec 2003 | 168 |
Test Plan | Security Test and Evaluation Plan, JCON-S, Appendix E | Feb 2004 | 186 |
Conversion Plan | Data Migration, ADNET to JCON-S | 150 | |
Implementation Plan | Sample JSIT Deployment Plan | 151 | |
Training Plan | Computer Security Awareness and Training (C/SAT) Plan, JCON-S Enterprise System, Version 2.1 | Dec 2003 | 145 |
Contingency/Continuity Plan | Contingency Plan, JCON-S, Appendix L | Feb 2004 | 149 |
Contingency/Continuity Plan | Contingency Plan, JWICS Network, Appendix M | 148 | |
Test Report | Acceptance Test Plan and Report | Dec 2003 | 168 |
Test Report | Security Test and Evaluation Plan, JCON-S, Appendix E | Feb 2004 | 186 |
The Classified Information Technology Program (CITP) project began spending funds in FY 2003. The mission is to develop a Department of Justice Classified Enterprise Architecture, an initial operational infrastructure, and an Operations and Maintenance Model for processing classified information. The scope of the project includes classified information technology for all Department of Justice components except the Federal Bureau of Investigation. The project’s objectives are to: (1) define requirements to support implementation of a Department Sensitive Compartmented Information and Collateral Classified Information Processing Capability; (2) implement initial capabilities for Top Secret/Sensitive Compartmented Information and Collateral Classified Information Processing Capability; and (3) define an ongoing program for Department of Justice Classified Information Technology.
Integrated Wireless Network
Justice Management Division
Components Involved: All Components
The Integrated Wireless Network (IWN) project began spending funds in FY 2001. The project is a collaborative effort by the Departments of Justice, Homeland Security, and the Treasury to provide a consolidated, nationwide federal wireless communications service that replaces stovepipe stand alone component systems, and supports law enforcement, first responder, and homeland security requirements with integrated communications services in a wireless environment.
IWN Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Market/Other Research | Market Research Summary | Apr 2004 | 1388 |
Business Case Study | High Level Design Report | 198 | |
Business Case Study | OMB Exhibit 300 for BY 2007 | Jan 2006 | 206 |
Risk Management Plan | Risk Management Plan, DOJ Wireless Management Office, Justice Wireless Network | Jun 2006 | 211 |
Acquisition Plan | Acquisition Plan, IWN JPO | Aug 2004 | 195 |
Project Plan | Program Plan FY 2006, Joint Program Office, Draft | Jun 2005 | 209 |
Project Plan | Strategic Plan 2005-2010, Integrated Wireless Network (IWN), (Draft) | Jun 2006 | 1004 |
Security Plan | System Security Plan, Beta Test System | Nov 2004 | 214 |
Configuration Management Plan | Configuration Management Plan, JPO IWN | Jun 2004 | 196 |
Quality Assurance Plan | Quality Assurance Plan, DOJ Wireless Network | 210 | |
Verification/Validation Plan | Data System Functional Tests, JPO-Pilot System | Oct 2004 | 192 |
Verification/Validation Plan | Network Management | Oct 2004 | 193 |
Verification/Validation Plan | Report Generation Tests | Oct 2004 | 194 |
Test Plan | Data System Functional Tests, JPO-IWN Pilot System | Oct 2004 | 192 |
Test Plan | Network Management | Oct 2004 | 193 |
Test Plan | Report Generation Tests | Oct 2004 | 194 |
Test Plan | Security Test and Evaluation Report: Beta Test System | Nov 2004 | 213 |
Implementation Plan | Organizational Readiness Transition Activities, IWN Seattle-Blaine Service Area | Sep 2004 | 203 |
Implementation Plan | Transition Plan | Oct 2004 | 215 |
Training Plan | Personnel Training for the Integrated Wireless Network | Nov 2004 | 208 |
Contingency/Continuity Plan | Contingency Plan, JPO IWN Northwest Zone | Jun 2005 | 197 |
Performance Evaluation | Beta Benchmark Assessment, IWN Seattle/Blaine | 202 | |
Post-Implementation Evaluation | Beta Benchmark Assessment, IWN Seattle/Blaine | 202 |
The IWN will implement solutions to provide federal agency interoperability with appropriate links to state, local, and tribal public safety, and homeland security entities. Justice, Treasury and DHS personnel represent the majority of law enforcement personnel within the Federal Government and are responsible for fulfilling numerous duties related to national law enforcement, protective missions, and homeland security missions. These operations are made more effective, efficient, and safe through the use of tactical communications. Unfortunately, current legacy wideband networks do not have sufficient communications capabilities to support the successful accomplishment of core activities. Many of the existing systems are 15 years old or older and are increasingly unreliable and expensive to maintain. Furthermore, varying tactical communications systems exist between field offices and organizations, preventing basic interoperability and presenting logistical issues during the course of routine enforcement activities. This incompatibility of systems makes communications interoperability difficult to achieve.
To meet these challenges, the IWN design is based on a very high frequency, Project 25 trunked system utilizing a packet switched Internet Protocol backbone. Additionally, the system design provides for encrypted communications. The network is presently based on land mobile radio services, and may be complemented by commercial wireless service solutions. The IWN will also be designed to facilitate interoperability with other federal, state and local public safety partners.
Justice Consolidated Office Network
Justice Management Division
Components Involved: Antitrust Division, Civil Division, Civil Rights Division, Community Relations Service, Criminal Division, Environment and Natural Resources Division, Executive Office for Immigration Review, Executive Office for United States Attorneys, Federal Bureau of Prisons, Justice Management Division, Office of Justice Programs, Tax Division, U. S. Marshals Service, U. S. Trustee Program, U. S. National Central Bureau of INTERPROL, U. S. Parole Commission
The JCON program began in FY 1996. The program provides a standard, consolidated DOJ Enterprise Office Solution, in partnership with DOJ components and the Office of Chief Information Officer’s staff, through the delivery of standing technology products and services. JCON is the critical infrastructure that provides a reliable and robust common office automation platform upon which 16 of the Department’s litigating, management, and law enforcement components operate their mission-critical applications. The cornerstone of the JCON is the JCON Standard Architecture, which defines the basic information technology computing framework, including networked workstations, servers, printers, a common set of core applications, such as email and word processing, and a basic set of system administration tools. JCON also provide the infrastructure for components to access case management and other mission-related databases, e-Gov applications, and the Department’s law enforcement, litigation, and administration systems. JCON provides the fundamental IT tools and services required by Department employees and contractors to perform their daily work functions.
JCON Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Market/Other Research | JCON Architecture Study, Final Report | Jan 1998 | 227 |
Market/Other Research | Request for Information (RFI), JCON PMO, Version 1.0 | Apr 2006 | 1012 |
Business Case Study | OMB Exhibit 300 for BY 2007 | Dec 2005 | 387 |
Privacy Impact Assessment | Initial Privacy Impact Assessment | 380 | |
Privacy Impact Assessment | Privacy Threshold Analysis | 390 | |
Risk Management Plan | Risk Management Plan, JCON PMO, Version 2 | Jul 2003 | 400 |
Acquisition Plan | Contract Administration, JCON | 374 | |
Project Plan | Project Management Plan Template, JCON PMO SDLC, Version 2.0 | May 2005 | 391 |
Project Plan | Project Management Plan, Civil Rights Division, JCON Implementation | Dec 2005 | 392 |
Project Plan | Project Management Plan, EOUSA JCON IIA Deployment | May 2005 | 393 |
Project Plan | Project Management Plan, JCON Modernization | Jun 2005 | 394 |
Project Plan | Strategic and Tactical Plan, JCON | Apr 2005 | 1005 |
Security Plan | System Security Plan, JCON-COAR | May 2006 | 404 |
Systems Engineering Management Plan | Systems Engineering Process, JCON PMO, Version 1.0 | Jun 2006 | 407 |
Configuration Management Plan | Configuration Management Plan, JCON PMO, Version 1.2 | Mar 2006 | 372 |
Test Plan | System Test Plan for DOJ EOIR, Version 1.0, Draft | Aug 2005 | 405 |
Test Plan | System Test Plan Template, JCON PMO SDLC, Version 1.0 | Mar 2005 | 406 |
Implementation Plan | Implementation Plan, EOIR, Final Version 2.7 | May 2006 | 379 |
Implementation Plan | JCON Implementation Plan Template and Guidance, JCON PMO SDLC, Version 2.0 | Mar 2005 | 382 |
Contingency/Continuity Plan | Contingency Plan, JCON COAR, Version 1.8 | Mar 2006 | 373 |
Test Report | Security Test and Evaluation, JCON COAR | May 2006 | 401 |
Test Report | System Analysis Report JCON Civil Rights Division Design, Version 1 - Final | Apr 2006 | 403 |
Performance Evaluation | Department Executive Review Board Presentation | Feb 2005 | 375 |
Post-Implementation Evaluation | Civil Rights Division Lessons Learned Report, JCON IIA Implementation Phase | May 2006 | 371 |
Post-Implementation Evaluation | Lessons Learned Report for the JCON Civil Deployment Implementation Phase | May 2006 | 385 |
Post-Implementation Evaluation | Lessons Learned Report Template and Guidance, JCON PMP SDLC, Version 1.0 | Jan 2005 | 386 |
Post-Implementation Evaluation | Summary of Findings, Email Users Survey | Dec 2005 | 402 |
Litigation Case Management System
Justice Management Division
Components Involved: | Executive Office for United States Attorneys Antitrust Division Civil Division Civil Rights Division Criminal Division Environment and Natural Resources Division Tax Division |
The Department’s major litigating components are highly decentralized, with information stored in numerous disconnected systems. The Litigation Case Management System (LCMS) initiative will develop and implement a common case management solution for the litigating components that will support efficient, automated information sharing and streamlined reporting capabilities. The project is part of the Department’s Case Management Common Solutions and OMB’s Lines of Business Programs to develop business-driven, common solutions across agencies. The LCMS will consist of a suite of solutions built on a common foundation, creating a case management architectural blueprint, data standards, and other products that should be reusable by other agencies. (The OMB-300 for budget year 20 07 indicates that several components were in various stages of pursing their own solutions, and are now participating in the LCMS program.)
The LCMS project began spending funds in FY 2003 and is planned to be phased in incrementally, beginning with Phase 1 in FY 2007 in U.S. Attorney’s Offices. Phase 1 is intended to incorporate case information management and reporting, workload management, and time reporting. Litigation support tools that can be used by attorneys to organize and manage individual cases are not part of Phase 1.
LCMS Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Market/Other Research | Final Market Research Report, LCMS | Jun 2005 | 250 |
Business Case Study | OMB Exhibit 300 for BY 2007 | Dec 2005 | 252 |
Business Case Study | Technical Evaluation Report, LCMS Phase 1, Version 0.9, Final | Apr 2006 | 256 |
Privacy Impact Assessment | Privacy Impact Assessment (Draft) | May 2005 | 1383 |
Project Plan | Project Management Plan, Version 1.2 | Aug 2005 | 254 |
Configuration Management Plan | Project Configuration Management Plan, Version 1.1 |
Apr 2005 | 253 |
Public Key Infrastructure
Justice Management Division
Components Involved: All Components
The Department of Justice has established a Public Key Infrastructure Program (PKI) to provide infrastructure-level trust services to enhance existing and planned business processes, applications, and services. The PKI will enhance security in order to foster communication between Department personnel across Components, other Federal, State, and Local Government agencies, commercial business partners, and transactions involving private citizens. The PKI is not in itself a security service, but instead is an underlying infrastructure-level service that enhances the offerings of existing security services within the DOJ enterprise. To augment these security services, the PKI Program will seek to establish an enterprise-wide public key capability and look to enable key business processes to leverage the services provided by the DOJ PKI.
PKI Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Market/Other Research | Planning and Design Support, DOJ PKI | Oct 2002 | 232 |
Business Case Study | Business Case, DOJ Enterprise PKI, Version 1.0 | Jul 2004 | 216 |
Business Case Study | OMB Exhibit 300 for BY 2008, CEI | 1017 | |
Privacy Impact Assessment | Privacy Threshold Analysis (questionnaire) | 235 | |
Project Plan | Project Management Plan, DOJ PKI | Aug 2004 | 236 |
Security Plan | System Security Plan, DOJ PKI, Revision 2 | Mar 2006 | 244 |
Configuration Management Plan | Configuration Management Plan, DOJ PKI Program and Technical Support, Version 1.1, Draft | Mar 2005 | 220 |
Test Plan | Test and Evaluation Master Plan, DOJ PKI, Revision 1 | Apr 2005 | 245 |
Implementation Plan | Deployment Implementation Plan, DOJ PKI, Final | Jun 2005 | 222 |
Training Plan | Training Plan, DOJ PKI, Final | Apr 2005 | 247 |
Disposition Plan | Chain of Custody Processes, DOJ PKI, Version 1.01 | Jun 2005 | 218 |
Contingency/Continuity Plan | IT Contingency Plan, DOJ PKI, Appendix L, Revision 3 | Mar 2006 | 226 |
Test Report | Security Test and Evaluation Plan (Final), DOJ PKI |
May 2005 | 242 |
Test Report | Test Report, DOJ PKI, Draft | Jun 2005 | 246 |
Performance Evaluation | Earned Value Management, DOJ Enterprise PKI Infrastructure Service Office | 223 |
Unified Financial Management System
Justice Management Division
Components Involved: All components
The Department of Justice has initiated an effort to implement a unified system that will improve the existing and future financial management and procurement operations across DOJ. The Department will address these needs via the implementation of the Unified Financial Management System (UFMS), which is planned to replace six core financial management systems and multiple procurement systems currently operating across DOJ with an integrated commercial off the shelf solution.
UFMS Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Market/Other Research | Financial Vendor Response Summary Draft | 1418 | |
Business Case Study | OMB Exhibit 300 for BY 2007 | Dec 2005 | 99 |
Privacy Impact Assessment | Privacy Impact Assessment, UFMS, Working Draft | Dec 2006 | 1399 |
Risk Management Plan | Risk and Issue Management Plan, Version 2.0 | Sep 2004 | 101 |
Acquisition Plan | Acquisition Plan UFMS Integration and Implementation Services | Jun 2005 | 86 |
Acquisition Plan | Acquisition Strategy Paper, DOJ UFMS | Jun 2002 | 87 |
Project Plan | DOJ Program Office Charter and Program Management Plan, Version 2.0 | Sep 2004 | 93 |
Project Plan | Implementation and Integration - Project Management Plan, Version 1.0 | Jun 2006 | 94 |
Security Plan | Security Management Plan (UFMS), Version 2.0 | Jan 2006 | 103 |
Security Plan | System Security Plan (SSP) for DOJ UFMS | Dec 2005 | 105 |
Systems Engineering Management Plan | Integration and Implementation - Systems Engineering Plan | Jul 2006 | 96 |
Configuration Management Plan | Configuration Management Plan, Version 1.0 | Aug 2005 | 88 |
Configuration Management Plan | Configuration Management Plan, Version 2.0 | Jun 2006 | 89 |
Quality Assurance Plan | Integration and Implementation - Quality Control Plan, Version 1.0 | Jul 2006 | 95 |
Test Plan | Integration and Implementation Test and Evaluation Master Plan | Jul 2006 | 97 |
Conversion Plan | Data Conversion Strategy, Version 1.0 | Jul 2006 | 92 |
Implementation Plan | System Implementation Plan, Version 1.0 | Jul 2006 | 106 |
Training Plan | Training Strategy, Version 1.0 | Jul 2006 | 109 |
The UFMS will allow the DOJ to streamline and standardize business processes and procedures across all components, providing accurate, timely, and useful financial data to financial and Program managers across the Department, and produce component- and Department-level financial statements. In addition, the system will assist the DOJ by improving financial management performance and aid Department components in addressing the material weaknesses and non-conformances in internal controls, accounting standards, and systems security identified by the OIG. Finally, the system will provide procurement functionality, consolidated management information, and the capability to meet all mandatory requirements of the Federal Acquisition Regulation and the Justice Acquisition Regulations.
Justice Grants Management System
Office of Justice Programs
Components Involved: | Office of Justice Programs Office of Community Oriented Policing Services |
The Justice Grants Management System (JGMS) is a web based, data driven application that provides end-to-end support for the application, approval, and management of grants for the proposed Justice Grants Management Consortium. JGMS is adaptable to accommodate the varying grants processes and grants types of its multiple users. JGMS supports the core missions and grants processes of DOJ's Office of Justice Programs and Office on Violence Against Women, and is targeted to incorporate the Community Oriented Policing Services (COPS) program. The Office of Grants and Training, Department of Homeland Security is also an established JGMS user and will continue to be supported by JGMS.
JGMS Studies, Plans, and Evaluations
Document Type | Title | Date | Item # |
---|---|---|---|
Business Case Study | OMB Exhibit 300 for BY 2007 | 364 | |
Project Plan | Grant Adjustment Notice (GAN) Module Project Management Plan, Draft | Sep 2005 | 360 |
Security Plan | System Security Plan for Grants Management System | Feb 2006 | 340 |
Configuration Management Plan | Configuration Management Plan, OJP | Nov 2004 | 341 |
Test Plan | GAN Module Test Plan, OJP | 347 | |
Test Plan | GMS Grant Adjustment Notice Module Test Cases | Oct 2005 | 346 |
Test Plan | Grant Adjustment Notice Module Test Plan, Phase 2 | 348 | |
Training Plan | GMS GAN Training Plan, (Draft) | May 2005 | 359 |
Contingency/Continuity Plan | Continuity of Operations Plan, OJP | Jul 2005 | 342 |
Test Report | Functional Requirements Document, Grant Adjustments, OJP, Version 1.1 | Nov 2005 | 345 |
Test Report | GAN Test Problem Report (Spreadsheet) | 357 | |
Test Report | Validation Test Script Forms, GMS | Feb 2006 | 1390 |
The Justice Grants Management Consortium formalizes the existing alliance of JGMS users, with the addition of new users with like interests such as COPS. JGMS has the capability to accommodate additional prospective agencies whose missions support first responder and disaster grants programs, should they elect to join the Consortium as members. JGMS provides an interface with the Grants.gov portal to allow potential applicants to conduct searches and apply for DOJ and Department of Homeland Security grant opportunities using the Grants.gov Find and Apply capabilities. JGMS will also build upon its interface with the financial management system which accounts for its DOJ users' grant funds and disburses funds to grantees, and its capability to export financial-related grants transaction data to external financial systems.
« Previous | Table of Contents | Next » |