Presentation on theme: "MARINE AVIATION Marine Aviation Logistics Expeditionary Delivery System (EDS) Status Update Presented by: MGySgt Ron Barton, HQMC ASL 15 JUN 2010."— Presentation transcript:
MARINE AVIATION Marine Aviation Logistics Expeditionary Delivery System (EDS) Status Update Presented by: MGySgt Ron Barton, HQMC ASL 15 JUN 2010
Agenda EDS Need Summary of Actions Way Forward Questions
3 EDS Need An Expeditionary Delivery System (EDS) is needed that integrates with and augments existing supply Mobile Facility (MF) capability. Scalability and flexibility are needed in order to store and transport parts in a building block fashion consisting of a single drawer, stacks of drawers, cabinets with drawers installed, and a bulk storage cabinet that can be configured as a set of cabinets or an entire MF or multiple MFs worth of drawer/cabinet combinations.
Summary of Actions 4 Early 2008: MARFORPAC Universal Needs Statement (UNS) submitted in 2008 for Remote Expeditionary Support Package (RESP) Expeditionary Container solution (RESP Expeditionary Container initiative became EDS). Summer 2008: MALS FWD (OIF) multi-million dollar purchase of BOH containers to support deployed supply operational requirements. July 2008: Aviation Logistics Transformation Task Force (AVLOG TTF) Working Group conducted DOTMLPF analysis, identified container capability gaps (Advocate Gap List), and defined EDS requirements. Summer Spring 2009: HQMC ASL leverages POM-12 Expeditionary Force Development Process (EFDS) process o EDS/RESP Expeditionary container #87 of 264 on MAGTF Gap List (MGL) o MAGTF Solution Planning Directive (SPD) and SPD Task List directs ASL as lead activity to develop required JCIDS/acquisition documentation o EDS/RESP Expeditionary container #186 of 220 on MAGTF Requirements List (MRL)
5 July 2009: Marine Aviation Logistics Support Program II (MALSP II) Summit Working Group to further refine EDS requirements o ASL-1 directs Fleet to cease procurement of all container solutions so that EDS requirement can be formalized and a proper acquisition strategy can be developed for a common Fleet-wide solution December 2009: HQMC ASL, MALSP II Project Office, and MF Program Office draft EDS requirements document o Requirements development not completed in time for POM-12 submission 2 February 2010: ASL-2 signs EDS Capability and Requirements Description document w/ draft Request for Information (RFI) 29 March 2010: NAVAIR 2.0 releases RFI solicitation number: N RFI0001 – responses due NLT 14 May June 2010: HQMC ASL, MALSP II Project Office, and MF Program Office evaluate 7 RFI responses, rack and stack potential solution providers, and begin development of Procurement Strategy and Request for Proposal (RFP). Summary of Actions (Cont.)
Way Forward 6 June – July 2010: HQMC ASL, MALSP II Project Office, and MF Program Office finalize Procurement Strategy and draft/release Sources Sought/Request for Proposal (RFP). o Determination of Small Business or Full and Open competition o Develop proposed Funding Strategy (baseline + Indefinite delivery/Indefinite Quantity (IDIQ) o Define quantities, sites, FY schedule Targeting early FY-11 contract award and beginning of incremental Mobile Facility modifications (mounting plates) and configurations of EDS Cabinet/Drawer/Bulk Storage Racks.