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.
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.
No comments:
Post a Comment