Program executive officers and direct-reporting product managers

PEOs and direct-reporting product managers will—

a.    Develop AEA architectures for assigned systems in coordination with CIO/G–6 and consistent with DOD guidance.

b.    Develop and coordinate architecture data as input to architectures under their purview Enterprise Email.

c.    Develop and submit information support plans in accordance with DOD guidance at http://jitc.fhu.disa.mil/ jitc_dri/jitc.html/. (See DA Pam 25–1–1.)

d.    Ensure that all fielded systems are logistically supportable during the life cycle of the system and follow integrated logistics support (ILS) responsibilities in accordance with AR 700–127.

e.   Submit all defense business systems with a total cost in excess of $1 million (over the period of the current future-years defense program submitted to Congress) for review by the appropriate Investment Review Board and certification approval by the Defense Business System Management Committee (DBSMC) (see 10 USC 2222).

f.     Ensure records management requirements are included in office operations and systems throughout their life cycle.

g.    Design, build, test, and field IP-enabled IT and NSSs to efficiently use IP address space. Coordinate materiel solution IP address space requirements with TRADOC and NETCOM as required. Request IP addresses to support materiel solutions in accordance with procedures published by NETCOM.

h.  Ensure compliance with IA C&A requirements, the Army Networthiness Program, and AEA for all PM-developed IT systems.
i.    Ensure that compliance with DOD policy regarding accelerated use of COTS IT and NSS by establishing a baseline and documenting progress in this effort.

j.     Comply with AIC policy (chap 6), configuration-management procedures, and resource adequately for systems to undergo AIC testing (see DA Pam 25–1–1).

k.   Support the Army’s configuration control process for the Joint messaging standards that are implemented in the systems for which they are responsible. Provide support, as required, to the Army’s representative to the Joint-configuration control boards that manage the configurations for these same Joint-messaging standards.

l.       Ensure that all installation-level IT infrastructure requirements (outside cable plant connectivity, campus area switching upgrades, and so forth) needed to support a specific product, program, or system fielding on Army posts, camps, and stations are validated and prioritized by NETCOM and approved by Army CIO/G–6 prior to implementa-tion (SAIS–AOI). (See DA Pam 25–1–1 for complete process.)

m.   Provide IT functional specifications, requirements, and relevant development systems and programs with ATEC to establish & maintain RDT&E capabilities.

Adhere to the platform requirements as specified in the COE architecture and information sharing requirements specified in the AIA.

Program, project, and product managers and information technology materiel developers

Program, project, and product managers and IT materiel developers (MATDEVs) will—

a. Implement applicable AEA guidance as related to their assigned program. The PM will—

(1)    Develop architecture views and products for the systems being acquired to comply with CJCSI 6212.01.

(2)    Develop and acquire technical support solutions and ensure that they are within the constraints of the AEA.

(3)    Coordinate AEA architectures for their systems with the program executive office (PEO) and the management official of gaining commands and installations (not applicable to weapons platforms).

(4)    Use the DISR online tool at https://disronline.csd.disa.mil/ to build standards views.

(5)    Coordinate their systems architecture with Army Architecture Integration Center prior to fielding systems. For more information Enterprise Email, see DA Pam 25–1–1.

(6)    Program for resources required to develop architectures and architecture products for assigned systems.

(7)    Program for resources required to perform accreditation and interoperability testing for integration with existing systems.
(8)    Identify bandwidth requirements to support program and collaborate with NETCOM for bandwidth support. b. Coordinate fielding plans for their systems with senior IM officials of gaining commands and installation NECs to ensure compatibility with existing systems and IT support structure.

c.    Develop and submit information support plans in accordance with DOD guidance at http://jitc.fhu.disa.mil/ jitc_dri/jitc.html/. For more information, see DA Pam 25–1–1.

d.    Ensure that all fielded systems are logistically supportable during the life cycle of the system and follow ILS responsibilities in accordance with AR 700–127.

e.    Ensure that records management requirements are included in systems throughout their life cycle in accordance with AR 25–400–2.

f.    Develop and prepare Exhibit 300 business case(s) for systems as applicable for submission with the IT budget in accordance with OMB Circular A–11 (not applicable to weapons platforms).

g.    Submit all defense business systems with a total cost in excess of $1 million (over the period of the current future year defense program submitted to Congress) for review by the appropriate Investment Review Board and certification approval by the DBSMC (see 10 USC 2222). This requirement does not apply to tactical systems.

Design, build, test, and field IP-enabled IT and NSSs to efficiently use IP address space. Coordinate materiel solution IP address space requirements with TRADOC and NETCOM as required. Request IP addresses to support materiel solution in accordance with procedures published by NETCOM.

Information management organizations below Headquarters, Department of the Army level

a. Subordinate organizations below HQDA, except as indicated below, may at their discretion designate a senior IM

official and establish supporting offices within their organization. Regardless of designation, all IM organizations will comply with governing legislation; Federal, DOD, and Secretary of the Army guidance; and the appropriate responsi-bilities delineated in chapter 2 and elsewhere in this regulation (see also DA Pam 25–1–1). The ARNG will comply with Defense Appropriations Bill 1997, Senate Report 104–286. Command senior IM officials will directly supervise the IM staff Enterprise Email, related programs, and activities; and execute LandWarNet global enterprise network activities as prescribed by NETCOM. Every ACOM and ASCC will appoint a senior IM official as a principal staff officer. DRUs may appoint a senior IM official as a principal staff officer if required and designated in writing by the respective HQDA official. MSCs may appoint an equivalent IM official with similar staff responsibilities as an ACOM’s or ASCC’s senior IM official. Senior IM officials will—

(1)    Perform voice and data network-management functions for the installation or assigned geographical boundary, including installation, operations and maintenance, and configuration management of common user component devices.

(2)    Determine procedures for enforcing standards view architecture compliance on a single installation or assigned geographical area.

(3)    Design or acquire systems within constraints of the AEA.

(4)    Appoint a frequency manager, if required, to coordinate, plan, program, manage, and supervise frequency management responsibilities.

(5)    Provide oversight and management for the installation’s participation in the Army’s IT Metrics Program.

 (6)    Perform IA functions in accordance with AR 25–2.

(7)    Perform functions as the single authority to validate the purchase of IT items on the installation, in accordance with IM and IT policies as prescribed by the Army CIO.

b. The Army Cyber Command operates, maintains, and secures Army global network operations via their theater signal commands. Subordinate brigades, battalions, and NECs comprise the IM and IT command, control, and operational structure across all theaters and on all Army installations. Their responsibilities include the following:

(1)    Provide quality common-user IM and IT baseline services to Army organizations at the highest possible level, commensurate with resourcing as defined in the approved-services list.

(2)    Provide quality mission level and enhanced IM and IT services to installation customers on a reimbursable basis as documented in the approved service level agreements (SLAs).

(3)    Oversee shared and common-user IT systems within their assigned area of responsibility and provide technical oversight for the IT services provided.

(4)    Develop MOAs and SLAs to document the above-baseline, customer-and-service-provider expectations, and to ensure successful conduct of the full spectrum of the theater IM and IT mission.

Implement and enforce Army-level IM and IT policies, standards, architectures, programs, plans, and portfolio management and budgets for common-user concerns within their assigned regions.

Army enterprise portals, Web sites and email

The transition to enterprise services will reduce the number of servers, the cost of hardware and software, and will improve the user experience. This section addresses how technology can be used to: support standardized, collaborative tool sets; share information to the maximum extent possible; and, provide portals with single sign-on capability. a. Enterprise portal. The Army enterprise portal improves information sharing and saves resources currently expended on traditional means of Web and email communication. The Enterprise Collaboration Services Program will replace the current Enterprise Email for collaboration and coordination of Army’s nonpublic information.

(1)    Enterprise Web portals. AKO (at https://www.us.army.mil), and Army Knowledge Online SIPRNET (AKO-S) are the current enterprise Web portals supporting unclassified and classified Army Web sites that activities will use to develop knowledge networks and portals.

(2)    Identity and access management. All Army email and Web servers that host sensitive information will be configured to use certificate-based client authentication using only DOD public key infrastructure (PKI)-approved certificates. The Enterprise Identity Management Service will populate the Global Address List, and will provision and maintain user account data and access management to enterprise applications. Issuance of the common access card (CAC) will serve as the authoritative source for account provisioning. Once a CAC is provisioned from the Defense Manpower Data Center, the user will have access to Army and DOD enterprise services from any Army system.

(3)    Logon. In accordance with AR 530–1, all account users are responsible for the security of their credentials and the content they create on the enterprise portal. Users who fail to properly secure their credentials and content via any Army IT resource may be subject to punitive and/or adverse administrative action.

(4)    Posting. Users will conform to posting procedures and policy on the use of official and authorized telecommuni-cations. See AR 25–13 for the unified capabilities (UC) policy.

(5)    Enterprise portal records. Email and other files on the enterprise portal that are determined to be records will be managed in accordance with AR 25–400–2.

b. Web sites and services.

(1)    Management of Web domains. NETCOM will manage the “army.mil” Web site assignment of subdomains and the Web domain registration process. The Web domain registry will include all of the Web domain information for “army.mil” Web sites at the third-level domain, as well as any commercial Web sites being used.

Army Data Management Program

a.    General. The ADMP is prescribed in Army Directive 2009–03. For more information on the ADMP, see DA Pam 25–1–1.

b.    Army data standards management.

(1)    Data standards. Data standards (specified in the DISR and other guidance documents and their associated authoritative data sources (ADSs), IESS, unique identifiers (UIDs), eXtensible markup language (XML), resource description framework (RDF), RDF vocabulary description language, RDF schema, and RDF schema derivatives) will be used to guide all data exchanges ENTERPRISE-EMAIL, including those needed to support legacy systems. DM requirements will be included in IT planning documents.

(2)    Army organizations. All Army organizations producing or using data standards (such as ADS, IESS, UID, and XML) will ensure that—

(a)    Only Army-approved data standards are used in systems.

(b)    New data standards are registered in the appropriate part of the Data Performance Plan System (DPPS) as needed.

(c)    Input is provided to Army data standards reviews.

(d)    Data standards used for information exchanges are identified during Army and Joint interoperability certification processes.

(e)    Only organizations identified by the data stewards as data standards producers will create or update DPPS content exchanged with or disseminated to any other organization.

(f)    Valid implementation of data standards Armywide. Functional data managers will manage ADSs, IESS, UIDs, and XML.

(g)    Their data is categorized as public, public restricted, or private. DOD requires protection requirements and accessibility requirements based upon the type of data. Public data that must be accessible from outside the .mil domain must reside in a DOD-approved shared space. Public data cannot be mixed or stored with public restricted or private data. Public restricted data must use some access-control method to restrict access to the data. Examples are CAC or user ID and password. Private data cannot be accessed outside the .mil domain. Private data must be separate from public and public restricted data in accordance with DOD policy, directives, and Chief Technology Offices.

(3) Army data quality management. All Army organizations producing or maintaining enterprise data must incorpo-rate a comprehensive data quality management process (DQMP) as part of their data production and maintenance activities. For more information on DQMP, see https://www.milsuite.mil/wiki/Data_Product_Catalog. The DQMP comprises the policies and procedures for selecting and implementing data-quality standards. These ensure that Army information products achieve and maintain the necessary level of data quality necessary to support all Army enterprise-wide operations and processes. All organizations producing or maintaining enterprise data will—

(a)    Create an environment and support the infrastructure needs to facilitate the exchange of lessons learned and best practices, so that all information products are brought to specified data-quality levels, regardless of operational environment.

(b)    Ensure that data-quality management procedures are adopted and applied to the Army data assets under their control.

(c)    Ensure that information products are objectively assessed by the DQMP for conformance to the necessary quality levels.

The U.S. Army Network Enterprise Technology Command

NETCOM will provide enterprise management and services, including to—

a.    Serve as the DAA for the Army enterprise, as directed by the CIO/G6.

b.    Serve as the Army IT integrator to achieve a single, virtual, Enterprise Network by advising the end-to-end management of the Army’s enterprise service area (service delivery ENTERPRISE-EMAIL, service operations, and infrastructure management) using the AEA and IEA. Provide Army network enterprise services and capabilities, including the mandated core enterprise services of the DOD Information Enterprise Architecture, installation IT services, and network connectivity. Prescribe the Army’s IT Service Management Program—

(1)    Prescribe all service delivery activities, policies, processes, procedures, and protocols for configuration manage-ment, availability management, capacity management, change management, and release management for the Army’s networks, systems, and functional processing centers. This includes technical and operational authority for any system architecture design or device that impacts the Army global-enterprise network and enabling technologies.

(2)    Prescribe all service operations activities, policies, processes, procedures, and protocols for incident manage-ment, event management, problem management, spectrum management, and database and Internet Web management for the Army’s networks, systems, and functional processing centers. This includes technical and operational authority over capabilities that impact the Army global-enterprise network and enabling technologies.

(3)    Prescribe all infrastructure management activities, policies, processes, procedures, and protocols for network and telecommunications management, facilities management, data storage management, IT services continuity management, and mid- and mainframe management for the Army’s networks, systems, and functional processing centers. This includes technical and operational authority over capabilities that impact the global-enterprise network and enabling technologies.

c.    Prescribe security of assigned fixed-station communications facilities and Army contractor telecommunications.

d.    Prescribe requirements for mobile or transportable communications assets to support assigned missions and functions.

e.    Organize and chair the LandWarNet technical configuration control board, and direct the Army enterprise configuration control and release management.

f.    Advocate for transformation, and engineer the enterprise network to efficiently and effectively serve the needs of the Army.

g.    Oversee Army leases of telecommunications services, and ensure that such services conform to DOD and National Communications Systems guidance.

h.    Oversee the Army Military Affiliate Radio System program, including amateur radio operators licensed to operate as a Military Affiliate Radio System member (see AR 25–6).

Support CIO/G6 to prescribe resources (people, projects, technology, and infrastructure) for service delivery, service operations, infrastructure management, IA, and network defense.

Principal officials, Headquarters, Department of the Army

Within their respective areas of functional and process proponency, principal officials, HQDA will—

 a.    Serve as the HQDA proponent for information requirements and associated capabilities within assigned functional areas of responsibility.

b.    Oversee functional processes within respective functional portfolio areas to maximize end-to-end enterprise processes and reduce redundancy in systems and local processes.

c.    Analyze their missions and revise their mission-related and administrative work processes ENTERPRISE-EMAIL, as appropriate, before making significant IT investments in support of those processes.

d.    Request and defend the capabilities and supporting resources needed for the development, deployment, operation, security, logistics support, and modification of ISs through the PPBE process.

e.    In coordination with their mission area architect, develop rules-based architectures for their respective functional segments; act as the integrator for any “system of systems” under their purview; and coordinate with CIO/G–6, as needed, on AEA documentation.

f.    Use E-Gov technologies to the maximum extent practicable to promote the goal of a paper-free (or nearly paper-free) business environment within the Army.

g.    Manage and oversee the records of respective functional areas to appropriately secure, maintain, and preserve them throughout their life cycle (see DA Pam 25–1–1, AR 25–400–2, DA Memo 25–51, and DA Pam 25–403 for additional responsibilities and information on the life cycle of records).

h.    Identify functional requirements for Army enterprise ISs and, as required, participate in related governance and advisory board activities.

i.    Establish IT PfM processes for assigned mission areas in order to define and justify planned IT expenditures that are consistent with DOD and Army guidance.

j.    Administer a telework program for their respective organizations and subordinate elements as prescribed in DOD and HQDA policy and guidance (see DA Memo 690–8 for more information).

k.    Provide a subject matter expert who will serve as a data steward under the direction of the Chief Data Officer; and who will also be responsible to develop, implement, and enforce Federal, Army, and organizational data standards, processes, and procedures.

Under Secretary of the Army

In addition to the duties listed in paragraph 2–4, the Under Secretary of the Army, or a designated representative, will—

a. Serve as the Army’s lead for generating force enterprise activities (GFEAs).
b.    Serve as the Chief Management Officer (CMO) for the management, coordination, oversight, and synchronization of the generating force’s business operations, processes, and decisionmaking procedures. This includes assisting with the integration and management of IT capabilities and services within the Generating Force through the Office of Business Transformation’s (OBT) Directorate of Business Operations.

c.    Preside over the BSIT-ESG.

Ensure that a single, integrated architecture for GFEA exists to support the Business Enterprise Architecture (BEA) and provide architecture products for integration into the AEA.