Sec. 1624. Department of Defense Ontology Governance Working Group
793 words·~4 min read·
/bill/119/s/2296/es/section-1624·A research copy — for the controlling text, always check the official state or federal source. Not legal advice.
The Secretary of Defense shall establish a working group to develop and implement a common data ontology and governance structure across the Department of Defense. The working group established pursuant to paragraph
(1)shall be known as the Department of Defense Ontology Governance Working Group (in this section the Working Group ). The purpose of the Working Group is to develop and implement a common data ontology and governance structure across the Department of Defense to improve data interoperability, enhance information sharing, and enable more effective decision making throughout the Department. The Working Group shall consist of— the Chief Digital and Artificial Intelligence Officer; the Chief Information Officer of the Department of Defense; the Chief Data Officers of the Department of Defense; the Chief Information Officers of the military departments and the combatant commands; such representatives from defense intelligence entities as the Secretary considers appropriate; and such other officers or employees of the Department as the Secretary considers appropriate. The Working Group shall— shall coordinate with and build upon any existing data ontology development efforts within the Department of Defense and intelligence community (as defined in section 3 of the National Security Act of 1947 ( 50 U.S.C. 3003 )) to ensure complementary and nonduplicative efforts; incorporate Department-wide data as well as data from defense intelligence entities; develop and maintain domain-specific data ontologies that address specialized knowledge areas within the Department of Defense, including warfighting, logistics, personnel, intelligence, and cybersecurity domains; establish a process to identify and designate functional domain leads responsible for leading the development, review, approval, and respective guidance of data ontologies for their particular domains; evaluate what security risks are introduced with common and domain-specific data ontologies and how these risks should be mitigated; and establish a governance framework that includes— a centralized repository to store the common and domain-specific data ontologies in a manner accessible to all authorized stakeholders; robust version control mechanisms to track changes, manage different versions, and ensure a stable and authoritative source; clear ownership designations and role definitions for data ontology management, including modification and access authorities for both enterprise-wide and domain-specific ontologies; standardized governance procedures for updating, reviewing, and maintaining the data ontologies to ensure relevance and accuracy; adherence to established data ontology engineering principles that promote interoperability and reusability across domains; and integration with existing Department data management practices and systems. In designating functional domain leads under subsection (d)(4), the Working Group shall select individuals who possess extensive subject matter expertise in their respective domains and maintain substantial equities or responsibilities within the domain. Functional domain leads selected under subsection (d)(4) shall be selected to ensure appropriate representation across the Department, including the military departments, combatant commands, defense agencies, and field activities. Functional domain leads selected under subsection (d)(4) shall be responsible for— leading the development and maintenance of data ontologies within their domains; reviewing and approving domain-specific data ontology elements; ensuring alignment between domain-specific data ontologies and the enterprise-wide data ontology framework; developing domain-specific guidance for data ontology implementation; and serving as the authoritative source for domain knowledge within the data ontology governance structure. The Secretary shall ensure that the Working Group is established pursuant to subsection
(a)not later than June 1, 2026, and the Working Group shall remain in effect for a period of not less than 5 years beginning on the date of the establishment of the Working Group, unless the Secretary determines that it is necessary to transition the Working Group into a permanent organization. Not later than August 1, 2026, the Working Group shall identify and designate functional domain leads in accordance with subsections (d)(4) and (e). Not later than June 1, 2027, the Working Group shall develop and distribute Department-level policy on the data ontology governance structure, including guidelines for the development, maintenance, and integration of domain-specific ontologies. The Working Group shall oversee the implementation of the governance structure by June 1, 2028. Not later than July 1, 2027, the Working Group shall provide to the congressional defense committees a briefing on progress of the Working Group. Not later than June 30, 2028, the Secretary shall submit to the congressional defense committees a report on the implementation of the ontology governance structure, including the status of implementation for both enterprise-wide and domain-specific ontologies, and recommendations for sustainment and further development. In this section: The term data domain ontology means a data ontology that is specific to a particular functional, operational, or subject-matter area within the Department, including warfighting, logistics, personnel, intelligence, or cybersecurity domains. The term data ontology means a formal, structured representation and categorization of data elements, their properties, and the relationships between them within an information system or knowledge domain that enables consistent interpretation, integration, and analysis of data across different systems and users.
Connectionstraces to 1
Traces to 1 document
U.S. Code
Citation graph
cites case law
Sec. 1624
Department of Defense Ontology Governance Working Group
Cites 1Cited by 0 across 0 sources