Downloaded from https://www.everyspec.com (e) Notify the applicable command whenever get-well plans are revised. (f) Provide required documentation for all MRs. (This includes obtaining an acceptance of conditions and urgency- of-need statement from the gaining command (GC) for all conditional materiel release (CMR) actions.) (g) Prior to pursuing CMR for a system, obtain concurrence from the Army acquisition executive (AAE). (h) Request approval from the MRA to release materiel. (i) Execute the development and fielding of corresponding TADSS as part of the acquisition weapon/tactical system MR strategy.
(j) Ensure coordination of release actions with LCMCs responsible for support and ancillary equipment and document their MR support statements. (k) Obtain MRA approval (or designated representative) for any changes to get-well dates. When approval is obtained, notify the GC of the approved changes. (l) Ensure conventional ammunition has a demilitarization and disposal plan. (2) For MR safety— (a) Ensure the materiel system and associated logistics support products meets applicable ESOH requirements, and that acceptance of associated risks for residual hazards is properly documented in accordance with AR 25–2, AR 40–10, and AR 385–10.
(b) Coordinate with the supporting safety office and ATEC to determine whether software changes are likely to affect the safety of the total system and whether an amended safety confirmation is required. (c) Obtain Nuclear Regulatory Commission (NRC) and Army licenses for systems containing radioactive material. (d) Provide the EOD Technology Directorate Armament Research Development and Engineering Center all techni- cal data on all systems that use or transport energetic materials. All technical data must be supplied to the Armament Research Development and Engineering Center EOD Technology Directorate a minimum 180 days prior to the MR date.
(e) Ensure system has a final transportation classification in accordance with 49 CFR 173. (f) Ensure safety suitability statement (safety and health data sheet) is included within the MR or deployment package. (g) Request a safety confirmation from ATEC (Developmental Test Command (DTC)) as part of required MR documentation. (h) When materiel is reprocured, ensure that safety and health evaluations are performed to verify that the safety characteristics of the original configuration are not compromised and that no new hazards are introduced. These evaluations will be conducted during the initial production tests or other testing. These evaluations are required when— 1.
Specifications have changed significantly over the currently fielded version. 2. There is a change in configuration under a performance specification. 3. A mission change has occurred. (3) To ensure suitability— (a) Assure that the total system is tested in accordance with AR 73–1 in the configuration in which it will be fielded and that the evaluation process is complete. (b) Ensure that all critical and major test incidents disclosed during Government or contractor testing have been resolved or provisions made for resolution.
(c) Obtain Operational Test Agency (OTA) Milestone Assessment Report (OMAR) or OTA Evaluation Report (OER) from the Operational Evaluator of Record; if needed, obtain a safety confirmation. Note. SER and SA terms have changed to OTA Milestone Assessment Report and OTA Evaluation Report. (d) Coordinate with the combat developers (CBTDEVs) and ATEC to ensure that the materiel system adequately meets system requirements outlined in approved JCIDS capabilities documents. (e) Notify storage activities to reclassify materiel to the appropriate condition code and ownership purpose code when MR actions are complete.
(f) Program and budget for NET and displaced equipment training (DET) in accordance with AR 350–1. (g) Ensure training devices for initial fielding and sustainment are type classified, safe, suitable, and supportable. (h) Obtain the transportability approval from Military Surface Deployment and Distribution Command (SDDC) Transportation Engineering Agency.
(i) Ensure that interoperability and all the IA controls assigned to the system, consistent with the policy in AR 25–2, are properly implemented before the system is materially released or that a plan of action and milestones are approved by an Army certification authority and designated approving authority is in place before the system is materially released; manage each system to achieve the appropriate level of protection for the applicable functional security requirements; and ensure that corrective actions for IAVM vulnerabilities are addressed as part of the MR process.
(j) Ensure that systems are developed and fielded in accordance with the requirements of USF, Army Enterprise Architecture, software blocking, interoperability certification, IA C&A, and networthiness, if applicable. 7 AR 700–142 • 26 March 2008