Documents

ICE TECS Modernization Operational Requirements

Mar. 2 2017 — 5:49p.m.

/17
1/17

For Official Use Only ICE TECS Modernization Program Operational Requirements Document (ORD) February 28, 2014 Version 1.0 Office of the Chief Information Officer (OCIO) CI: {Obtain CI for the document from CM/DM process.} Date Revised: {Delete the Date revised line if this is the first issue of the process.} i

ICE OCIO TECS Modernization Operational Requirements Document Revision History No. Date Reviewer (s) Title Change Description 1. 1/29/14 Version 1 2. 2/20/14 Version 1 (Program Adjudicated per PARM Comments) 3. 2/28/14 Version 1 (Program Adjudicated per CAE Comments) TECS Mod ORD - 20140228 For Official Use Only i

ICE OCIO TECS Modernization Operational Requirements Document Table of Contents Executive Summary .........................................................................................................................1  1  Introduction ................................................................................................................................2  1.1  1.2  1.3  Purpose............................................................................................................................ 2  Background ..................................................................................................................... 2  Timeframe ....................................................................................................................... 3  2  Concept of Operations Scenarios ...............................................................................................4  3  Operational Effectiveness Requirements ...................................................................................4  3.1  3.2  Measures of Effectiveness .............................................................................................. 5  Measures of Performance ............................................................................................... 5  4  Suitability Requirements ............................................................................................................6  4.1  4.2  4.3  4.4  4.5  4.6  System Design ................................................................................................................ 6  Reliability, Availability, Maintainability (RAM) ........................................................... 6  Human Systems Integration ............................................................................................ 7  Integrated Logistics Support ........................................................................................... 7  Survivability.................................................................................................................... 8  Training Requirements.................................................................................................... 8  5  Key Performance Parameters .....................................................................................................9  6  Critical Operational Issues .......................................................................................................10  APPENDIX A: ACRONYM LIST ................................................................................................11  APPENDIX B: ICM SYSTEM INTERFACES LIST ...................................................................12  TECS Mod ORD - 20140228 For Official Use Only ii

ICE OCIO TECS Modernization Operational Requirements Document Executive Summary TECS is a mainframe based system and is the primary investigative tool used by Immigration and Customs Enforcement (ICE). It provides investigation, reporting, entry processing, and Watchlist mission support for ICE and Customs and Border Protection (CBP) and is the system of record for all activities related to both criminal and administrative investigations. ICE has identified deficiencies in the current legacy mainframe system and O&M cost impacts that will occur beginning in FY2016 in the event the system is not replaced. The ICE TECS Modernization Program will address both of these issues. The ICE TECS Modernization Program will provide a modernized Investigative Case Management (ICM) solution that meets ICE Homeland Security Investigations (HSI) mission needs in the areas of: Case Management Subject Records System Interfaces Reporting and Analytics The TECS Modernization Program has defined milestones for Initial Operating Capability (IOC) and Final Operating Capability (FOC). The program will deliver IOC by September 30, 2015, which will achieve mainframe independence. The program will deliver FOC by Q4 FY17, which will include additional functionality and integrations. This Operational Requirements Document (ORD) identifies the specific operational requirements necessary to support the HSI mission and to achieve the stated performance measures. The ORD includes Measures of Effectiveness (MOEs) and Measures of Performance (MOPs) that quantify the system’s ability to effectively support the HSI mission. The ORD also includes suitability requirements that guide the system design and support system operations and maintenance. This document further describes the roll up of MOEs and MOPs into three Key Performance Parameters (KPPs) and four Critical Operational Issues (COIs). KPPs represent the system capabilities that HSI considers essential to achieve its mission, and include Response Time, Concurrent Users, and Availability measures. COIs measure the operational effectiveness and suitability characteristics used to evaluate the system’s ability to achieve the HSI mission, and address Case Management, Interfaces, Access Control, and Reliability. TECS Mod ORD - 20140228 For Official Use Only 1

ICE OCIO TECS Modernization Operational Requirements Document 1 Introduction The ORD translates the capabilities defined in the Mission Needs Statement (MNS) into operational level performance requirements that complement the Concept of Operations (CONOPS). 1.1 Purpose The purpose of the ORD is to identify the operational and program-level requirements to achieve the performance goals and mission of the ICE TECS Modernization Program. This document will accomplish the following: Identify the operational requirements to build the capabilities necessary to achieve the goals and mission of the ICE TECS Modernization Program Provide the effectiveness requirements that must be part of, or met by, the ICE TECS Modernization Program in order to successfully complete its mission Address the suitability requirements necessary to meet supportability and sustainment, reliability, availability, maintainability, survivability, design and training requirements as well as personnel safety and environmental considerations Define Key Performance Parameters that measure system capabilities considered essential for the modernized TECS system 1.2 Background TECS was developed in 1987 by the U.S. Customs Service as an umbrella system to support the business activities of investigative case management. TECS is a mainframe based system utilizing 1980’s processing, application and information management technology, which administered by the Customs and Border Protection (CBP) Office of Information Technology (OIT). CBP and Immigration and Customs Enforcement (ICE) components are collaborating to modernize the system. Under this structure, ICE and CBP will build separate systems that provide the capabilities needed to support each component’s unique mission. Due to the requirement to share critical information between ICE and CBP, the ICE TECS Modernization Program and CBP TECS Modernization Program have been and will continue to closely coordinate development of their respective systems. This will occur through a governance process that includes executive oversight and participation at the program and working levels. The ICE TECS Modernization Program is being driven by the need to address deficiencies in the legacy mainframe system. Current functionality does not allow interfaces between systems, lacks modern interfaces for system users, and does not support required security measures. The program is also driven by the need to migrate the legacy system from the mainframe. If ICE is unable to achieve mainframe independence by FY2015, it will be required to assume responsibility for maintaining the legacy TECS system and incur significant O&M costs starting in FY2016. The program revised its acquisition and solution strategy in Q1 FY14 to clearly define the capabilities needed for ICE to discontinue the use of legacy TECS mainframe by September 2015. The program assessed its requirements, technology, and processes to reduce the overall program costs, schedule, and technical risks. The effort resulted in an issuance of an ADM requiring the ICE TECS Modernization Program to achieve an ADE-2B decision, which is currently planned for Q3 FY14. TECS Mod ORD - 20140228 For Official Use Only 2

ICE OCIO TECS Modernization Operational Requirements Document 1.3 Timeframe 1.3.1 Initial Operational Capability Date The Initial Operational Capability (IOC) for the ICE TECS Modernization system occurs once the investigative case management capabilities are deployed and the Program no longer relies on the legacy TECS system. Mainframe independence will be considered complete at IOC which is planned on or before September 30, 2015 to align with CBP’s schedule to transition off legacy TECS. IOC represents the minimum required functionality to achieve mainframe independence in the following five categories: Case: includes the primary work product for all ICM users to include management of investigative cases, investigative reports, administrative reports, and statistics Subject Records: capture and share information on subjects of interest (for example, people, vehicles, businesses), link subject records to cases and investigative reports, and establish connections between subject records and cases globally Interfaces: includes implementation of the required interfaces with which the investigative case management system will share data as identified in the ICM System Interfaces List (Appendix B) Universal: includes functionality that appears throughout the system in multiple screens and modules (for example, the ability to print or sort) Technical: includes implementation of all other technical requirements needed to support enduser functionality (for example, implementing existing DHS single sign-on capabilities) These collectively are considered core case management functionality. Those classified for FOC are both enhancements to the core case management functionality and new functionality. 1.3.2 Full Operational Capability Date FOC of the TECS Modernization system is achieved when there are no additional releases and all the capabilities have been developed and deployed. FOC includes major enhancements and other service integration. The scheduled baseline objective for FOC is Q4 FY17. FOC represents implementation of enhancements and additional functionality to provide more effective core case management. In addition, there will be integration of functionality required by the Office of Professional Responsibility. With regard to core case management, enhancements will include the following capabilities: Case: electronic distribution of investigative reports to administrative email inboxes to replace distribution via office printers, implementation of digital signatures for case documents, creation of repository for case document templates with version control, system mobility, voice recognition capabilities and comprehensive analytics Subject Records: creation of additional remarks to enhance communication with other law enforcement agencies, address validation for better data quality and consistency across subject records, and immediate access to record owner information by querying agent Interfaces: includes implementation of remaining interfaces as identified in the ICM System Interfaces List Universal: includes implementation of media tagging; capability to save search criteria for streamlined searching; ability to manage (save/delete) notifications; full utilization of audio, video and other multi-media information; and geospatial mapping Technical: includes implementation of all other technical requirements needed to support FOC functionality TECS Mod ORD - 20140228 For Official Use Only 3

ICE OCIO TECS Modernization Operational Requirements Document 2 Concept of Operations Scenarios Concept of Operations scenarios have been created that support the ORD development and are identified within the CONOPS document. Representative user scenarios presented in the CONOPS were developed by the HSI business users and depict operational functional capabilities. The HSI Investigative Case Management Operational View diagram shown in Figure 2-1 is a representation of a reactive case initiated by an event and concluded upon reaching judicial process. The diagram shows the following case management processes: Processing of an event Searching and retrieving the system and interfaced systems for subjects and related case documents Creating a case and supporting case documents Interfacing with analytical tools to create support work products Creating subjects and lookouts to CBP via the CBP lookout service Creating charging documents to facilitate prosecution of subjects A lookout is an ICM system subject record shared with CBP for enforcement action and/or in furtherance of investigations. Once shared, the record becomes searchable and viewable by CBP according to defined access control. Figure 2-1: HSI Investigative Case Management Operational View 3 Operational Effectiveness Requirements The system’s operational effective performance requirements and parameters are segmented into Measures of Effectiveness (MOE) and Measures of Performance (MOP). TECS Mod ORD - 20140228 For Official Use Only 4

ICE OCIO TECS Modernization Operational Requirements Document 3.1 Measures of Effectiveness The measures of effectiveness for the system identify performance requirements needed to meet operational level capability objectives and shall do the following: Provide the ability for all users with appropriate access to view cases and all associated documents, subject records and links within five seconds of being created when they are accessing the system from a device directly connected to an ICE network Ensure the system provides the ability to create a lookout record and have that record available for posting within five seconds to CBP TECS Portal Provide the ability for users to complete all work related to cases, case documents and subject records (i.e., opening/creating, approving, modifying, deleting) Provide the ability for a user to link cases to case documents and subject records/lookouts Provide the ability for a user to link subject records/lookouts to case documents Ensure the system provides the ability to receive and present search responses from all sources with which the system interfaces within five seconds of being made available Provide audit trails to facilitate reconstruction of events on demand Reduce data entry time by eliminating duplicative requests for input of data from users Interface with the systems listed in the ICM System Interfaces List (Appendix B) 3.2 Measures of Performance The measures of performance for the system are quantitative measures of system characteristics. Transaction Response Time: Transaction response time refers to the time required for completion of an individual transaction. Specifically, the transaction response time shall not be greater than five seconds from a workstation request to a workstation response. A transaction is defined as the ability to search, create, read, update and delete all data elements required to complete the business function. A business function may also include auto loading transactions (uploading/downloading) in which case a many-to-one scenario is considered to be a single transaction. A single search transaction includes responses from all data sources from which information is requested (user login is not to be considered a transaction). Response time excludes transaction processing time on systems external to the investigative case management application. Concurrent Users: The system shall meet performance thresholds with 6,000 concurrent users and objective with 10,000 concurrent users. Number of Transactions: The system shall provide the ability to process a threshold of 250,000 transactions per day and objective of 500,000 transactions per day. TECS Mod ORD - 20140228 For Official Use Only 5

ICE OCIO TECS Modernization Operational Requirements Document 4 Suitability Requirements 4.1 System Design The ICE TECS Modernization Program shall follow the ICE System Lifecycle Management (SLM) process, which is aligned with the DHS Systems Engineering Life Cycle (SELC), to ensure the system meets the required standards for implementation, operations and maintenance. The technical solution shall use a commercial off-the-shelf (COTS) investigative case management system with customization to include development of interfaces to systems via web services. The design shall include the use of Single Sign On (SSO) to leverage DHS infrastructure for authentication and authorization. It is not anticipated that the system will be deployed in any special operational environments. 4.2 Reliability, Availability, Maintainability (RAM) RAM refers to three related characteristics of a system and its operational support: reliability, availability, and maintainability. Reliability is the probability of an item to perform a required function under stated conditions for a specified period of time. Maintainability is the ability of a system and its parts to be retained in, or restored to, a specified condition. Availability is a measure of the degree to which an item is operable and can be committed at the start of a mission when the mission is called for at an unknown (random) point in time. Availability blends reliability and maintainability. 4.2.1 Availability The metric used to specify availability will be Operational Availability (Ao), which is the probability that an item will be operating or capable of operation when required when used in an actual or realistic operating and support environment. It includes logistics time, ready time, and waiting or administrative downtime, and both preventive and corrective maintenance downtime. This value is equal to the mean time between failure (MTBF) divided by the mean time between failure plus the mean downtime (MDT). This measure extends the definition of availability to elements controlled by the logisticians and mission planners such as quantity and proximity of spares, tools and manpower to the hardware item. The ICM system is mission essential and has been designed as a continuously operating system that is expected to be available 24 hours per day, 7 days per week. The ICE TECS Modernization Program shall implement the ICM solution using the DHS cloud-based Infrastructure as a Service (IaaS). This service is hosted in Tier II Data Centers (as defined by the Uptime Institute) that provide 99.75% availability. The program will also use other systems, networks, and services provided by DHS, to include the DHS wide area network (DHS OneNet). Equipment used locally includes workstations, laptops, printers, and local area networks that are supported by ICE OCIO. The management and oversight of the IaaS service and local equipment is outside the scope of the TECS Modernization Program. Therefore, availability shall be calculated for the ICM system components that provide the mission essential functions required to achieve mainframe independence in the Case, Subject Records, Interfaces, Universal, and Technical categories identified in Section 1.1.3. Availability shall be calculated for the ICM system components at the Data Centers using the perspective of the entire user community outside of the Data Centers; that is, all users must be unable to access the mission essential functions for an outage to exist or to be calculated as downtime/system failure. Sitespecific outages that do not impact the entire user population (i.e., individual site outages) are system reliability degradations and not system outages. Regardless of the reason for the outage, all failures must be recorded and resolved as soon as practicable. TECS Mod ORD - 20140228 For Official Use Only 6

ICE OCIO TECS Modernization Operational Requirements Document The Ao requirements for the ICM system components are: Threshold of 99.07% and Objective of 99.97%. 4.2.2 Reliability Reliability is the duration or probability that an item or system can perform its intended function for a specified interval under a stated condition without failure or negatively impacting mission accomplishment. The TECS Modernization program tracks reliability using two metrics. Mean Time Between Failure (MTBF) is a predicted or estimated value based on the system components. MTBF does not include actions resulting from scheduled preventive maintenance. Mean Down Time (MDT) is the average time that a system is non-operational. It includes all downtime associated with repair, corrective and preventive maintenance, self-imposed downtime, and any logistics or administrative delays (i.e., scheduled and unscheduled down time). To minimize the impact of routine system maintenance activities, redundancy will be built into the infrastructure used to run the ICM system. As stated in section 4.2.1, down time shall be calculated for the ICM system components at the Data Centers using the perspective of the entire user community outside of the Data Centers; that is, all users must be unable to access the mission essential functions provided by the ICM system to be calculated as down time. The ICM system components shall be at least as reliable as the legacy TECS system, and shall be calculated for the ICM system components at the Data Centers. Using TECS historical reliability data as the baseline, the required (threshold) MTBF for the ICM system shall be 117 hours and the desired (objective) MTBF shall be 3500 hours. The MDT for the ICM system shall be 1.1 hours (threshold and objective). 4.2.3 Maintainability Maintainability is a measure of the relative ease and economy of time and resources with which an item can be retained in, or restored to, a specified condition when corrective action or preventative maintenance is performed by personnel having specified skill levels, using prescribed procedures and resources, at each prescribed level of maintenance and repair. A basic measure of maintainability is determining the Mean Time To Repair (MTTR). This is the mean or average of the corrective maintenance (active repair) times for a system. The MTTR for ICM system components shall be 1 hour (threshold and objective). 4.3 Human Systems Integration There are no unique personnel, safety, human factors or environmental considerations for the ICE TECS Modernization Program. The ICE user population for the current TECS system is expected to stay the same for the modernization effort. Training of personnel will be developed as part of the ICE TECS Modernization Program training task, and will address any safety, human factor and environmental considerations as needed. The ICM system shall generally operate in an office environment with no special operating factors or considerations. The system will comply with all applicable Section 508 requirements. 4.4 Integrated Logistics Support The TECS Modernization system will be developed and maintained with no unusual or specific logistics support requirements. TECS Mod ORD - 20140228 For Official Use Only 7

ICE OCIO TECS Modernization Operational Requirements Document The DHS Data Center and ICE OCIO Operations Division will identify, acquire and manage the IT resources needed to sustain the products and support equipment. Any issues identified at the field level will be routed through the ICE Service Desk and escalated as required to Tier 2 and Tier 3 support. Further details regarding system support will be provided in the Integrated Logistics Support Plan (ILSP) developed for this program. 4.5 Survivability The ICM system is mission critical and is required to survive and continue to offer continuous availability in the event of a natural or man-made disaster. Accordingly, the ICM system shall be hosted in a DHS Data Center and maintain redundant components in each Data Center. Should either Data Center fail, the other Data Center shall assume the full workload. To guard against man-made threats, the system shall meet ICE standards for security and privacy, which comply with policies and direction as contained in the DHS 4300A Sensitive Systems Handbook. 4.6 Training Requirements All ICM system users must complete Privacy Awareness training prior to accessing the system. In addition, new agents will receive ICM training at the Federal Law Enforcement Training Centers (FLETC). Other users will receive role based training to include on-the-job training. Training courses will be available to ICM users via hyperlink, which will direct users to the appropriate training forum. ICM will maintain user profiles that reflect certification dates of required training and control access to applications and interfaces based on established training requirements. The TECS Modernization Program will deliver system training to those individuals supporting the system as well as current Legacy TECS users. In addition, ICE OCIO has contracted for support using an ICE Office of Training and Development (OTD) contract with OPM to design, develop and deliver the system training. Training and education solutions will consist of training methods including self-directed training and an electronic performance support system. The Program will determine the specific point of distribution as the training program is further developed and will follow OTD contract requirements at such point that ICE Virtual University may be used for training course access and/or distribution. TECS Mod ORD - 20140228 For Official Use Only 8

ICE OCIO TECS Modernization Operational Requirements Document 5 Key Performance Parameters The table below identifies the KPPs for the ICE TECS Modernization Program. No. 1 KPP Response Time: Transaction response time refers to the time required for completion of an individual transaction. Specifically, the time it takes from a workstation request to a workstation response, which is tested at the end user device level. Test time begins when the user hits enter after filling out the appropriate transaction criteria and ends when the intent of the transaction is accomplished, for example when search results appear on the results page. Threshold Objective Comments The system shall provide operationally acceptable transaction response time* for individual transactions across the system, not to exceed 5 seconds 95% of the time. The system shall provide a transaction response time* for individual transactions across the system, not to exceed 3 seconds 99% of the time. *Response time excludes transaction processing time on systems external to the investigative case management application. (For example, processing within the ICM application must not add more than 5 seconds to the time required for an external database to process a request with regard to Threshold or 3 seconds with regard to Objective.) Response time for search includes responses from all data sources queried. 2 Concurrent Users: The system shall be able to handle a high level of users, measured by the number of concurrent users accessing the system at the same time. Response time is calculated only for devices directly connected to an ICE network and does not include remote devices (i.e., connected through VPN, mobile device running over wireless network, etc.). No less than 6,000 users accessing the system at the same time with system capability allowing all users to conduct business transactions concurrently within the application. No less than 10,000 users accessing the system at the same time with system capability allowing all users to conduct business transactions concurrently within the application. TECS Mod ORD - 20140228 For Official Use Only 9

ICE OCIO TECS Modernization Operational Requirements Document No. KPP Threshold Ao > 99.07% Availability: 3 Objective . Ao > 99.97% The ICM system shall achieve the required level of Operational Availability (Ao). Comments Required level of monthly Operational Availability for the ICM system components. Figure 5-1: Key Performance Parameters 6 Critical Operational Issues The table below identifies the Critical Operational Issues (COIs) for the ICE TECS Modernization Program. No. COI Category COI 1 Case Management Does the modernized system provide users the capability to perform case management functions (whether criminal or administrative) required from case inception to final disposition as well as reporting and audit capabilities? 2 Interface with Critical Systems Does the modernized system allow HSI to exchange data with critical systems both internal and external to the agency? 3 Access Control Does the modernized system provide access control that will ensure proper handling of sensitive data within the ICM application in addition to data shared with systems both internal and external to the agency? 4 RAM Is the modernized system technically viable (supportable) in an operational environment providing a sufficient degree of reliability, availability and maintainability? Figure 6-1: Critical Operational Issues TECS Mod ORD - 20140228 For Official Use Only 10

ICE OCIO TECS Modernization Operational Requirements Document APPENDIX A: ACRONYM LIST Acronym Full Term Ao Operational Availability ADE Acquisition Decision Event ADM Acquisition Decision Memorandum CBP Customs and Border Protection COI Critical Operational Issue CONOPS Concept of Operations COTS Commercial Off-The-Shelf DHS Department of Homeland Security FLETC Federal Law Enforcement Training Centers FOC Full Operational Capability HSI Homeland Security Investigations IaaS Infrastructure as a Service ICE Immigration and Customs Enforcement ICM Investigative Case Management ILSP Integrated Logistics Support Plan IOC Initial Operational Capability KPP Key Performance Parameter MDT Mean Down Time MNS Mission Needs Statement MOE Measure of Effectiveness MOP Measure of Performance MTBF Mean Time Between Failure MTTR Mean Time To Repair O&M Operations and Maintenance OCIO Office of Chief Information Officer OIT Office of Information Technology OPM Office of Personnel Management ORD Operational Requirements Document OTD Office of Training and Development RAM Reliability, Availability, Maintainability SEACATS Seized Assets and Case Tracking System SLA Service Level Agreement SELC Systems Engineering Life Cycle SLM System Lifecycle Management SSO Single Sign On VPN Virtual Private Network TECS Mod ORD - 20140228 For Official Use Only 11

ICE OCIO TECS Modernization Operational Requirements Document APPENDIX B: ICM SYSTEM INTERFACES LIST # ICE Internal, DHS Internal, or DHS External System Description Owning Agency Inbound, Outbound, or Bi-directional Data Items To/From Interfacing System IOC or FOC 1 DHS Internal CBP Modernized TECS Provides inspection / border crossing data critical to HSI investigations CBP Real time, Bidirectional, system-tosystem interface and Single Sign-On integration Subject/Lookout Record: Create/Modify/ Query/Delete (all record types). Query to include: Primary, Secondary Air, Secondary Land, Crossing, Incident Logs, Query Notification, SEACATS, ATS, ACS, ADIS. Capability to ingest data into the ICM System. IOC 2 DHS Internal SEACATS (Seized Asset and Case Tracking System) Creation and tracking of arrest and seizure, and property CBP Bi-Directional Creation, maintenance, and query of statistical data related to arrests, seizures, and property management. (Note: The creation of incidents is a priority capability to be developed, as incident query is available via both Falcon and AFI). IOC 3 ICE Internal ACRIMe (Alien Criminal Response Information Management System) ICE enterprise service used to access numerous data systems ICE Inbound NCIC, Interstate Identification Index (III), NLETS, CIS, Claims 3, Claims 4,External Search Service (ESS) IOC 4 DHS Internal Virtual University Training and Certifications DHS Inbound Import of validated certifications (NCIC/NLETS, TPA, etc.) for ICM system access. IOC 5 ICE Internal Falcon Analytic tool with access to the ICE Enterprise Data Warehouse ICE Inbound ICM Data Warehouse, DARTTS, FinCEN, SEN (SIR, SPEAR, DRO Tav, LEARA), SEACATS, TLS, PCTS, CI, UC, Tip Line, ICE AD, ACE, AES, CLEAR, PEN LINK, CELLBRITE, Mbox, BLACK ASPHALT IOC TECS Mod ORD - 20140228 For Official Use Only 12

ICE OCIO TECS Modernization Operational Requirements Document # ICE Internal, DHS Internal, or DHS External System Description Owning Agency Inbound, Outbound, or Bi-directional Data Items To/From Interfacing System IOC or FOC 6 DHS Internal AFI (Analytic Framework for Intelligence) Analytical tool primarily focused on CBP warehoused data CBP Inbound CBP Primary, CBP Secondary and Incident Reports, APIS, CLEAR, CMIR, EID, LEXIS NEXIS, NSEERS, SEVIS, Travel and Entry Docs, CEE, AFI INTELVIEW, AFI PROJECTS, AFI REQUEST FOR INFO, SEACATS, ATS IOC 7 ICE Internal EID (Enforcement Integrated Database) Arrest / Booking System(s) ICE Bi-Directional EAGLE, IAFIS, IDENT, ABIS, ICE Active Directory, NCIC IOC 8 ICE Internal ICM Data ICE enterprise data management ICE Inbound The data repository for all ICM data for search and analytical purposes FOC 9 DHS Internal CTTP (Consolidated Trusted Travelers Program) Provides information regarding subjects approved as low-risk travelers CBP Inbound Verification of subject status as trusted traveler FOC 10 DHS External CLASS (Consular Lookout and Support System) Queries of DoS lookouts by name and DOB Department of State Inbound Verification of subject status on lookout with DoS FOC 11 DHS External EPIC (El Paso Intelligence Center) Narcotics / Alien Encounters DEA Inbound Event and subject Information related to narcotics or aliens FOC 12 DHS External NICB (National Insurance Crime Bureau) Provides vehicle related information by VIN or license tag number Privately Owned Inbound Information on vehicle related thefts, declarations, salvage and exports FOC Warehouse(s) TECS Mod ORD - 20140228 For Official Use Only 13

ICE OCIO TECS Modernization Operational Requirements Document # ICE Internal, DHS Internal, or DHS External System Description Owning Agency Inbound, Outbound, or Bi-directional Data Items To/From Interfacing System IOC or FOC 13 DHS External ATF (Alcohol Tobacco Firearms & Explosives) Provides information on lookouts by name/DOB and firearm purchase data by firearm serial number ATF Inbound Lookout records and data on firearm purchases FOC TECS Mod ORD - 20140228 For Official Use Only 14

Filters SVG