13.07.2015 Views

policies and procedures for the acquisition of medical materiel

policies and procedures for the acquisition of medical materiel

policies and procedures for the acquisition of medical materiel

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

concept <strong>and</strong> mission pr<strong>of</strong>ile <strong>of</strong> using units will fur<strong>the</strong>r define <strong>the</strong> basic need <strong>for</strong> developing a new MES or revising anexisting MES.C–2. Event 2: Requirements Document.The combat developer (AHS) will prepare a requirements document (AR 71-9) <strong>for</strong> a new MES. This document will bebased on a mission pr<strong>of</strong>ile <strong>and</strong> <strong>the</strong> operational concept <strong>for</strong> <strong>the</strong> particular MES in relation to its supported TOE. Themission pr<strong>of</strong>ile will be based upon current or proposed clinical, tactical, <strong>and</strong> field <strong>medical</strong> support doctrine. Therequirements document <strong>for</strong> <strong>the</strong> MES will also include an assessment <strong>of</strong> training <strong>and</strong> testing requirements <strong>and</strong>recommendations <strong>for</strong> alternate means <strong>of</strong> testing <strong>the</strong> MES. The purpose <strong>of</strong> <strong>the</strong> MES requirements document is to plan<strong>the</strong> resources <strong>for</strong> <strong>the</strong> PPBES <strong>and</strong> will not be used <strong>for</strong> any new <strong>materiel</strong> <strong>acquisition</strong>s. A separate requirements documentwill be initiated <strong>for</strong> all new <strong>materiel</strong> <strong>acquisition</strong>s.C–3. Event 3: Approval <strong>of</strong> Requirements Document.The combat developer <strong>and</strong> <strong>the</strong> mission assignee agency will au<strong>the</strong>nticate Letter Requirements (LRs) in coordinationwith <strong>the</strong> <strong>medical</strong> <strong>materiel</strong> developer. The LRs will be submitted to <strong>the</strong> OTSG <strong>for</strong> approval be<strong>for</strong>e initiation <strong>of</strong>developmental actions fur <strong>the</strong> MES. Directorate, Heath Care Operations, OTSG, will coordinate <strong>the</strong> staffing <strong>of</strong> <strong>the</strong>documents within OTSG. The approved requirements documents establish <strong>the</strong> doctrinal base upon which <strong>the</strong> AHS willdevelop <strong>the</strong> MES. All o<strong>the</strong>r requirements documents (ROCs) <strong>for</strong> major programs, designated <strong>acquisition</strong> programs, <strong>and</strong>DA IPR programs will be submitted to HQDA (DAMO-RQR) <strong>for</strong> approval.C–4. Event 4: Select MES Development Panel.At <strong>the</strong> same time as <strong>the</strong> action in event 3, above, <strong>the</strong> AHS will, in coordination with HSC <strong>and</strong> <strong>the</strong> combatdevelopments advisory council, initiate actions to designate <strong>the</strong> chiefs <strong>and</strong> o<strong>the</strong>r pr<strong>of</strong>essional members <strong>of</strong> <strong>the</strong> MESDevelopment Panels.C–5. Event 5: Outline Test Plans/Resume Sheets (OTRs/RSs).The designated test organization will prepare OTPs/RSs when testing is anticipated as documented in <strong>the</strong> requirementsdocument.C–6. Event 6: Program Management Plan (PMP).The PMP is a tailored document prepared by <strong>the</strong> combat developer to support <strong>the</strong> development, training, testing,assembling, <strong>and</strong> fielding <strong>of</strong> <strong>the</strong> MES. In <strong>the</strong> PMP technical analysis, program decisions, <strong>and</strong> development milestonesare documented. O<strong>the</strong>r participating activities provide input.C–7. Event 7: Submission <strong>of</strong> BOIP Feeder Data <strong>and</strong> QQPRI.The mission assignee agency in coordination with <strong>the</strong> combat or training developer will initiate BOIP feeder data <strong>and</strong>QQPRI according to AR 71-2 <strong>for</strong> <strong>for</strong>warding to HQ, TRADOC.C–8. Event 8: Development <strong>of</strong> MES Component Listing.a. The development panel will develop <strong>the</strong> MES according to <strong>the</strong> requirements document <strong>and</strong> <strong>the</strong> guidance providedin chapter 3.b. The panel will weigh <strong>the</strong> factors below to determine <strong>the</strong> type <strong>and</strong> quantities <strong>of</strong> items required <strong>for</strong> <strong>the</strong> MES:(1) Item <strong>of</strong> choice <strong>for</strong> a specific need.(2) Potential <strong>of</strong> <strong>the</strong> item <strong>for</strong> multiple uses.(3) Skill level <strong>of</strong> personnel using <strong>the</strong> item.(4) Availability <strong>of</strong> <strong>the</strong> item within DOD.(5) Current state-<strong>of</strong>-<strong>the</strong>-art.(6) Current st<strong>and</strong>ardized <strong>medical</strong> equipment <strong>and</strong> supplies.(7) Stockage criteria.(8) Commonality <strong>of</strong> items.(9) Redundancy.(10) Training requirements.(11) Item characteristics (potency, shelf life, maintainability, durability, special storage requirements, simplicity,reliability, weight, cube, transportability, etc.).(12) DOD Tri-Service D-day significant items list.C–9. Event 9: MACOM Staffing <strong>of</strong> Proposed MES.a. AHS will staff <strong>the</strong> proposed MES (Draft) with selected using units, major Army comm<strong>and</strong>s (MACOMs), <strong>and</strong>panel team chiefs <strong>for</strong> review, comment, <strong>and</strong> recommendations.b. The combat developer (AHS), <strong>medical</strong> <strong>materiel</strong> developer, <strong>and</strong> mission assignee agency (USAMMA) will review38 AR 40–60 • 15 March 1983

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!