Downloaded from https://www.everyspec.com Table 4–2 Full materiel release determination guidelines—Continued Criteria Request for FMR Notes: 1 ATEC should provide a Capability and Limitation Report for CCEP device being used in tactical environment. This will be used by gaining unit commander to determine acceptance and appropriate usage. 2 In some cases such as missiles, the functional authority shall waive the requirement because of limited test assets (normally due to cost) to establish the necessary statistical proof. In these cases, the PM shall establish a plan to validate RAM is achieved through the expenditure of assets over the life cycle.
3 Systems supported by planned ICS and that have planned and budgeted for a longer term support strategy such as organic support may be fully released. 4 DA authentication of technical manuals has been accomplished in accordance with AR 25–30 prior to fielding and handoff to units. 4–7. Software materiel release and software release A software MR (SMR) or a software release (SR) action is required for changes in software and/or firmware, including programs, routines and symbolic languages that controls the functioning of the hardware and direct its operation (even when it is not part of a materiel modification). a.
When the materiel is fielded through the MR process, the software associated with that materiel is simultaneously certified. (1) When the materiel (system) and software both require MR, the software is released as part of the materiel (system). (2) When the materiel (system) does not require a MR, but the software does, the software will undergo the SMR process on its own. b. Depending on the scope of the software change, software fixes sometimes called patches may be addressed using a SR. c. Software materiel release is the upgrade of software that— (1) Requires all software changes meet the requirements defined in paragraph 4–5.
(2) Will be processed by the MR coordinator’s office and be approved by the MRA. (3) Will be classified as full, conditional, or urgent, as defined in paragraph 4–4. (4) Will be approved by the DCS, G–3/5/7 in accordance with HQDA software blocking policy if it impacts battle command (BC) systems, or major releases of tactical network software. d. When one or more of the criteria listed in table 4–3 have been met, a SMR will be conducted. 19 AR 700–142 • 26 March 2008 Key SS performance aspects have been achieved as deter- mined by the functional authorities.3 —Maintenance planning accomplished and coordinated. Army preference is in accordance with AR 750–1.
—Manpower and personnel requirements to operate and maintain the system have been identified and documented. —Adequate supply support for fielding and sustainment of units (interim contract support (ICS), per- formance-based logistics, organic) has been established. —Support equipment is identified and documented at the appropriate organization; TMDE suppor- tability has been addressed; footprint is minimized. —Technical data rights of use are established; TMs have been verified by the Government.4 —Training and training support (to include TADDS and ammunition requirements for training) have been identified, developed and documented; training is available for all GCs and maintainers.
—Maintenance of software is addressed in the SS (software development plan) and life cycle cost esti- mate and hardware for mission-critical systems are available at the appropriate organization. —Facilities requirements are developed and documented (maintenance, training storage, covered, hu- midity controlled, and so on); facilities are available. —Package, Handling, Storage And Transportation System is transportable by all modes as specified in the capability document. Transportability has been evaluated by SDDC and documented according- ly. —The PM has programmed funding for the support strategy within POM. (Coordinate with the office of the DCS, G–3/5/7 (DAMO–TR).
—Ammunition Stockpile Reliability Program and ammunition surveillance procedures are in place. —All environmental impacts have been identified, mitigated if possible, and documented in accordance with the National Environmental Protection Act and 32 CFR 651.