Potential Sites

The following States and cities are being considered as proposed ISE-SAR EE sites. The venues listed are being considered because of a number of factors, including involvement in the MCCA SAR Support and Implementation Project (which developed several recommendations regarding implementation of the SAR process), level of technology, maturity of the Fusion Centers, and existing data efforts in the area of SARs. This list does not preclude the consideration of other States or cities as possible ISE-SAR EE participants.

Boston (UASI)

Houston (UASI)

Las Vegas (UASI)

Chicago/Illinois (UASI/State)

Los Angeles/JRIC (UASI/State)

Miami-Dade (UASI)

Phoenix/Arizona (UASI/State)

Seattle/Washington (UASI/State)

Washington, DC (UASI) and Federal Shared EE Sites

Maryland (State)

Florida

New York State

Virginia

Architecture

A major challenge with identifying, implementing, and operating IT systems to support ISE mission processes, such as SAR, involves standardizing and rationalizing all the inherent differences and distinct separation of information resources9 across the Federal Government and with SLT organizations where appropriate. Achieving business-led standardization and architectural integration is absolutely essential for establishing an ISE-SAR EE-wide, federated capability for efficiently, effectively, and reliably sharing ISE-SAR information. This document constitutes one of two documents being created by the ISE-SAR EE integrated project team.

Segment Architectures are logically arranged documents that lay the foundation for building executable operational solutions (or systems) that meet or exceed mission performance goals for a particular line of business and are derived from a concept of operations. Segment Architectures achieve this by documenting the set of business and information requirements, outcomes, and constraints. This ISE-SAR EE Segment Architecture document is scoped to one particular line of business—terrorism-related suspicious activity reporting. It documents the business outcomes and will drive necessary decisions (both programmatic and solution) consistent with the logical business case for the ISE-SAR EE.

Solution Architectures are structured, technical documents, derived from Segment Architectures, that are scoped to describe the particular functions or processes that will be implemented (in this case the SAR services and operations capabilities), identify methods for achieving operational outcomes, and define specific IT assets, applications, and components for procurement and implementation. Solution Architectures do not specifically identify vendors or specific vendor items as these are generally identified in subsequent specification documents and/or procurement orders. As part of this ISE-SAR EE, partnering ISE-SAR EE organizations will follow guidance from both this Segment Architecture and the corresponding ISE-SAR EE Solution Architecture to define ISE-SAR EE project development, implementation, and operations activities.

http://www.ncirc.gov/sar/ISE-SAR_EE_Segment_Architecture_v1(Dec_2008_Final).pdf

GLTA in 2010, Opty