policies and procedures for the acquisition of medical materiel

MIL STD–785(Reliability Program for Systems and Equipment Development and Production).MIL STD–881(Work Breakdown Structure for Defense Materiel Items).MIL STD–882(System Safety Program for Systems and Associated Subsystems and Equipment: Requirements for).MIL STD–1388–1(Logistic Support Analysis).MIL STD–1388–2(Logistic Support Analysis Data Element Definitions).MIL STD–1472(Human Engineering Design Criteria for Military Systems, Equipment, and Facilities).MIL STD 1474B(Noise Limits For Army Materiel).MIL–HDBK–472(Maintainability Prediction).MIL–M–73035(Front-End Analysis).MIL–M–36036(New-Look Operator’s Manuals).MIL–M–63037(Organizational DSIGS Logic Tree Style).MIL–M–63038(Organizational, DSIGS Maintenance).MIL–M–63040(Extension Training Materiels).Appendix BNONDEVELOPMENT ITEM (NDI) ACQUISITION MODELNote: See the NDI acquisition flow chart (fig 3-1) a fold-in page, located at the end of the regular size pages.B–1. Event 1: Coordinated Materiel Proposal.a. References.(1) AR 70-1.(2) AR 71-9.b. Description. Materiel proposals may originate from any user or staff source identifying a need for a new item ormodification or improvement of existing item. The primary action office is the logistician who will assign a projectnumber and forward to the combat developer for coordination with MEDMAP participants. The purpose of clearingthrough the logistician is to establish a central control point to monitor and track actions through the MEDMAP.B–2. Event 2: Review and Analysis.a. References.(1) AR 7D-1.(2) AR 71-9.b. Description. The combat developer will staff the proposal with the Joint Working Group (JWG) members forpreliminary review. This may be done either telephonically or by document review. If the consensus is that theproposal is valid. it will be scheduled for final review and decision by the JWG. The JWG will normally meet32 AR 40–60 • 15 March 1983