Downloaded from https://www.everyspec.com (2) Ensure all conditions in the get-well plan are listed within the MRTS. Categorize conditions according to DA Pam 700–142. Normal MR procedures will be used to expedite fielding of systems/materiel to meet MTOE authoriza- tions unless the unit is imminently deploying; in this case, UMR policy and procedures will apply. (3) Restrict CMR to specific quantity, location, and application. (4) Notify the gaining GC of the issues precluding full release as reported by the functional authority and update the GC whenever the get-well plans are revised.
(a) A GC acceptance statement issued by the GC and signed by or for a general officer or civilian equivalent will accompany a concurrence of a conditional release. (A system scheduled for a conditional release without an urgency of need statement, signed by or for a general officer or civilian equivalent, will not be approved for MR.) (b) Correction of faults and subsequent FMR of systems does not relieve the PM of the requirement to correct deficiencies in systems previously conditionally released. Consequently, there may be similar systems in the field simultaneously, some under a conditional release and some under a FMR.
(c) Identify and establish mitigating controls in the get-well plan for identified safety hazards not meeting the requirements for FMR. (5) For systems containing explosives— (a) Certify all safety requirements have been met or mitigated, as determined by the supporting Safety Office. (b) Do not preposition, move, or ship the explosive component to a GC until all safety requirements have been met. This includes EOD supportability statement, safety confirmation, and a DOD final hazard classification (FHC).
If the FHC is not complete, an IHC can be assigned provided the IHC authority is satisfied that the sponsoring organization is actively pursuing the FHC (see TB 700–2 for additional considerations). (6) Obtain approval by the MRA or the MRA’s designated representative for any changes to get-well dates of conditions in the MRTS. The designated representative will be no lower than the grade of colonel or civilian equivalent. Once approval is obtained, the GC will be notified of the approval and change in the get-well date. A refusal by the GC to accept the change or failure to convince the MRA to approve the extension may result in revocation of release approval.
This would require an immediate suspension of the materiel and preclude further release actions until the condition is corrected. (7) To close a condition— (a) Obtain concurrence from the proponent for closure. (b) Provide the MR coordinator with a copy of the concurrence. (c) Request the MR coordinator close the condition and update MRTS to reflect the condition closure. 4–9. Conversion of conditional materiel release to full materiel release a. Take the following actions when MR conditions prohibiting FMR have been corrected:
(1) The PM will ensure a MSR is submitted using SLAMIS to reclassify the item TC STD when an item was previously type classified as LP and now meets TC STD requirements. (2) The MR coordinator will— (a) Upgrade MRTS to reflect a status change from CMR to FMR. (b) Supply a memorandum to the PM, the MRA, and agencies/organizations identified in paragraph 4–13 e (1) through 4–13 e (9) documenting that the system is now recommended for an FMR. (c) The MRA may approve the conversion. b. The PM may convert a CMR to FMR when the MR conditions are determined to be acceptable after attempts to follow get-well plans have failed or are no longer applicable.
Convert a CMR to FMR when— (1) The materiel meets applicable safety requirements and has acceptance of associated risks for residual hazards properly documented in accordance with AR 385–10. (2) All members of the MRRB will— (a) Reach agreement that the limiting condition cannot be eliminated. (b) Recommend to the MRA that the system be given a FMR as currently fielded. (3) The PM will attain written agreement from the using command. (4) The MRA may approve the conversion. c. Upon approval by the MRA, the— (1) MR coordinator will— (a) Convert the CMR to FMR. (b) Make appropriate changes in the MRTS, accordingly. (2) PM will notify the supporting and using commands. 4–10.
Urgent materiel release—operational need The UMR of materiel (including software) is intended solely to meet an operational need of a deployed or imminently deploying force in support of approved operational contingencies. a. Urgent materiel release procedures may be used for type-classified and non type-classified systems/materiel, to 21 AR 700–142 • 26 March 2008