IC ITE - Bryant McGill

# IC ITE **Domain:** Austin Research / Programs **Doc Type:** Research entity **Source basis:** Supplied research cluster with linked references; see the [[wiki/Austin Research Evidence Map|evidence map]] for verification scope. The **Intelligence Community Information Technology Enterprise (IC ITE)** is the shared-services architecture initiated in the early 2010s to make intelligence data, compute, applications, identity, and security services interoperable across agencies. Its 2012–2017 strategy supplies the central historical reference; later data and cloud strategies extend its principles. ## What becomes executable Common identities establish who or what requests access. Metadata identifies an information object’s origin, meaning, and handling requirements. Authorization services evaluate requests; catalogs and interfaces make resources discoverable; cloud services supply compute; audit records preserve what happened. These functions move repeated information-handling decisions into software while participating institutions retain their respective authorities. The 2017–2021 data strategy explicitly develops machine-interpretable governance for data that had been coupled to applications and bilateral sharing arrangements. The 2019 cloud strategy extends service availability toward remote and disconnected mission environments. The 2024 information-environment roadmap develops data-centricity, multi-cloud infrastructure, Zero Trust, and AI services. ## Austin comparison and succession relevance The Austin master uses IC ITE as the enterprise-scale comparison for a distributed executable loop: a sensor, model, analytic service, and authorized decision-maker can occupy separate institutions and locations. The specific execution path from [[wiki/PECOS|PECOS]] to an IC cloud or an ODIN aircraft remains unresolved. Documented Oden research interfaces and documented IC architecture are separate evidence layers. Its succession significance is **portable organized process**: data, identities, policy, and interfaces can survive replacement of a cloud provider or application. Human and non-person identities are both represented in the [[wiki/Unified Identity Attribute Set|Unified Identity Attribute Set]]. Such operational machine identity supports authenticated execution; it is distinct from legal personhood or consciousness. ## Connected entries [[wiki/Office of the Director of National Intelligence|Office of the Director of National Intelligence]] · [[wiki/Unified Identity Attribute Set|Unified Identity Attribute Set]] · [[wiki/Attribute-Based Access Control|Attribute-Based Access Control]] · [[wiki/Trusted Data Format|Trusted Data Format]] · [[wiki/Intelligence Community Cloud Architecture|Intelligence Community Cloud Architecture]] · [[wiki/Machine-Executable Policy|Machine-Executable Policy]] · [[wiki/Task Force ODIN|Task Force ODIN]] · [[wiki/Saturn Arch|Saturn Arch]] · [[wiki/Digital Twin Interoperability|Digital Twin Interoperability]] · [[wiki/Computational Process|Computational Process]] · [[wiki/Austin Executable Loop|Austin Executable Loop]] · [[wiki/Austin Regional Intelligence Center|Austin Regional Intelligence Center]] · [[wiki/Intelligence Advanced Research Projects Activity|Intelligence Advanced Research Projects Activity]] · [[wiki/National Geospatial-Intelligence Agency|National Geospatial-Intelligence Agency]] · [[wiki/North Central Texas Council of Governments|North Central Texas Council of Governments]] · [[wiki/Sensor-to-Action Loop|Sensor-to-Action Loop]] · [[wiki/Texas Fusion Center|Texas Fusion Center]] · [[wiki/Xpress and Xtend|Xpress and Xtend]] ## Sources and corpus context - [[research/The Austin Executable Loop|The Austin Executable Loop — master document]] - [[research/IC ITE - Intelligence Community Information Technology Enterprise|IC ITE - Intelligence Community Information Technology Enterprise]] - [[research/ODIN - Observe, Detect, Identify, Neutralize|ODIN - Observe, Detect, Identify, Neutralize]] - [Intelligence Community Information Technology Enterprise Strategy 2012–2017](https://www.odni.gov/files/documents/IC_ITE_Strategy.pdf) - [Cloud Computing in the Intelligence Community — Strategic Plan](https://www.odni.gov/files/documents/CIO/Cloud_Computing_Strategy.pdf) - [Intelligence Community Data Strategy 2017–2021](https://www.odni.gov/files/documents/CIO/Data-Strategy_2017-2021_Final.pdf) - [IC Technical Specification — Unified Identity Attribute Set](https://www.odni.gov/files/documents/CIO/ICEA/IC_Tech_Spec_Attributes_V2_Final_PUBLIC.pdf) - [Vision for the IC Information Environment — May 2024](https://www.odni.gov/files/documents/CIO/IC-IT-Roadmap-Vision-For-the-IC-Info-Environment-May2024.pdf) **Cluster:** [[wiki/Austin Executable Loop|Austin Executable Loop]] · [[wiki/Austin Research Evidence Map|Austin Research Evidence Map]]  ## The regional counterpart to enterprise integration [[wiki/Interlocal Information Sharing|Austin’s LEAP route]] demonstrates integration constituted at several institutional layers: city participation, regional administration, and a reported federal MOU. The comparison with IC ITE concerns portable access and rules implemented through interfaces. The LEIS briefing identifies its own web-service and message standards; IC ITE’s data strategy identifies enterprise data and machine-executable handling rules. [[wiki/LEAP Provider Transition|Provider transition]] makes continuity a concrete question: do records, permissions, and correction obligations survive a change of operator? The documented NCTCOG handoff and the commercial CrimeTracer history motivate that inquiry without establishing a LEAP deployment inside IC ITE. **Follow:** [[wiki/DHS Law Enforcement Information Sharing Service|DHS Law Enforcement Information Sharing Service]] · [[wiki/LEAP Provider Transition|LEAP Provider Transition]] · [[wiki/Machine-Executable Policy|Machine-Executable Policy]] **Source:** [[research/The Austin Surveillance Field|The Austin Surveillance Field]]; [DHS — Law Enforcement Information Sharing Service briefing, slides 4–16; existing MOUs on slide 15](https://info.publicintelligence.net/DHS-LEISS.pdf); [ODNI — IC Information Environment Data Strategy 2017–2021](https://www.odni.gov/files/documents/CIO/Data-Strategy_2017-2021_Final.pdf); [NCTCOG — FY2014 comprehensive annual financial report, PDF p. 10, provider transition](https://www.nctcog.org/getmedia/cb64f213-b8d5-4332-aae2-8cabe5354be1/CAFR2014.pdf?ext=.pdf).