Ground-based Midcourse Defense Future Request for Information

DESCRIPTION: The Missile Defense Agency (MDA) is conducting market research to determine potential strategies and industry capabilities to execute the Ground-Based Midcourse Defense (GMD) Systems Engineering and Integration, Development, System-Level Test, Production, Fielding, Operations, and Sustainment. This Request for Information (RFI) is part of the overall market research activity to collect, organize, maintain, analyze and present data in accordance with Federal Acquisition Regulation (FAR) Part 10. This is a market research announcement for informational planning purposes only and does not constitute a Request for Proposal (RFP), nor is it to be construed as a commitment by MDA. Information submitted will be considered as an exchange of information and may be used as part of future RFP(s). No RFP/solicitation will be issued at this time. Participation in this effort is strictly voluntary with no costs incurred or obligations made on behalf of MDA. RFI responses will not be construed as an offer and will not be accepted by MDA to form a binding contract. This RFI will assist MDA in making informed acquisition decisions related to: a) Potential and logical scope/prime contractor alignments across multiple acquisition approaches ranging from: - One single prime contract with overall program scope responsibility, or; - A model with strategic separation of program scope logically divided into multiple prime contracts to include a Weapon System Integrator (WSI). b) Determining Roles, Responsibilities, Authorities, and Opportunities between the Government Program Office, Independent Technical Assessment Agent, and industry partners. c) Defining of work roles for Systems Engineering, Test, Homeland Defense System-Level Integration, Weapon System Development and Deliveries, and Operations & Sustainment. d) Improvement areas for executing the GMD Program including organizational structure, weapon system component OEM insight/oversight, schedule, management and administrative overhead. e) Mitigation strategies for potential OCI issues associated with the approach of multiple prime contractors to include a weapon system integrator. f) Approaches and risks associated with transitioning incumbent contractor along with program content from current construct to follow-on contract(s). g) Identification of existing lessons learned that can be applied to the GMD Program from similar federal acquisitions based on program size, mission, and / or complexities. PROGRAM BACKGROUND: The GMD Program Element of the Ballistic Missile Defense System (BMDS) provides Combatant Commanders the capability to engage and destroy intermediate- and long-range ballistic missile threats in space to protect the U.S. The GMD Program Element integrates multiple sensors, communications systems, fire control capabilities, and Ground-Based Interceptors (GBIs) to detect, track, and destroy intermediate and long-range ballistic missile threats during the midcourse phase of flight. The GMD Program Element is composed of two main components: GBIs and Ground Systems (GS), along with required communications, support equipment, training equipment, and facilities. The GMD Program Element is a distributed capability with operational mission locations in Alaska, California, Colorado, and New York. The GMD architecture provides for a defensive operations capability as well as the simultaneous conduct of operations, flight tests, ground tests, cybersecurity tests, and training. The MDA implements an evolutionary acquisition strategy to design, build, integrate, test, and field capabilities for missile defense in an incremental capability delivery approach. Therefore, the GMD Program Element is involved simultaneously in multiple life cycle phases ranging from Product Development (Limited Fielding) to Operations and Support. Today, a single prime contractor manages the GMD Program Element, the GMD Development and Sustainment Contract (DSC) HQ014719C0004. The DSC is a single contract that provides for the full end-to-end development and sustainment of the current GMD weapon system. GMD PROGRAM ELEMENT SCOPE: MDA will assess respondent's strategies and capabilities to either perform or to integrate the following key requirements to develop, integrate, test, deliver, and sustain a major weapon system element. Based on the level of interest and the apparent capability of industry to perform in these areas, MDA reserves the right to request follow-up information and/or presentations from RFI respondents as needed. Information received from follow-up questions and presentations will be considered part of the overall market research activity and will be addressed in accordance with FAR Part 15.201. The scope listed below is intended to provide a high-level view of program's scope as currently structured. 1. Systems Engineering and Integration Component - Execute GMD Program Element-Level concept definitions, development and traceability of requirements, requirements definition support, requirements verification and design compliance, models & simulation (M&S) execution, configuration management (CM) and change management execution, conducting and understanding risk management analysis of alternatives, concept of model-based systems engineering (MBSE), conducting and executing trade studies, preparation and execution of informal and formal milestone technical reviews, architecture definition and modification, definition and traceability of internal and external interfaces, algorithm and software development including verification and validation, system level physical and logical integration, component/product level integration, analysis of system effectiveness, analysis of system performance and effectiveness, long range planning and studies, and weapon system data and lab infrastructure/management. - Execute GMD system integration of the BMDS integration for vertical and horizontal interoperability with the BMDS and GMD system, components, and products. Support the integration of the component and product hardware and software into the GMD and BMDS Government laboratories. Execute GMD system integration planning including interoperability of components and products in test and operational environments. In addition, execute development and integration of new functionality and capabilities using hardware and software technology insertion and obsolescence (form, fit, and function) replacements to keep the weapon system capable of countering an evolving threat. - Execute both non-real time and real-time M&S capabilities at multiple levels of fidelity are required to support architecture definition and system performance assessment, with verification, validation, and accreditation to support specific intended uses. - Define requirements for component and system-level ground, flight, and cybersecurity test and verification. Designs are to be reliable, producible and affordable when ready for production. Incorporate rigorous systems engineering processes and core standards. 2. System and Component Level Test (Flight, Ground, and Cybersecurity Test and Laboratory Support) Component - Manage and support planning, integration, and execution and analysis for the integrated BMDS as well as conduct internal testing and system level testing and verification and validation. GMD Test consists of four focus areas: Flight Test Execution, Ground Test Execution, Cybersecurity Test Execution and Resource Management. - Demonstrate and verify GMD Program Element performance requirements through detailed laboratory, ground, flight, and cybersecurity test events. Collect data that anchors modeling and simulation and builds confidence in system program performance. Provide support associated with day-to-day operations of the flight, ground, and cybersecurity test programs to include engineering support for test planning, execution, and analysis. - In accordance with the Integrated Master Test Plan (IMTP), execute BMDS level flight test (approximately one per year) ground test, and cybersecurity test events with GMD participation. Additional test events include sensor characterization flight tests, and post-flight simulation reconstruction for development of program risk reduction. -Execute GMD System Ground Test activities to include Integrated and Distributed testing. - Execute knowledge of test resources, test range support, test assets, processes, knowledge of system test and System Test Labs, and facilitation/integration of cross-functional organizations to bring testing to successful completion. - Manage system test lab resources that are scarce, high demand assets fundamental to the successful development, integration, verification, and assessment of present and future GMD capability. 3. Operations & Sustainment Component - Maintain readiness of the GMD Weapon System to include reporting, analyzing, and assisting with issues and assets associated with operations, training, test and exercise events, scheduled system and site transitions, development activities, including necessary privileged user/system administrator (SA) functions. - Perform maintenance (preventative and corrective) of the GMD Element and associated infrastructure. Plan and execute product support to meet or exceed system availability rates. Schedule and support coordination and synchronization of maintenance activities as required by the asset Management. - Execute hardware and software upgrades IAW Government provided installation kits/packages. Establish Contractor depot/original equipment manufacturer (OEM) and developer relationships to plan and execute both on-site and depot maintenance efforts required to support the GMD Element. - Execute replenishing of required spares, repair parts, and consumables necessary to maintain the components of the GMD Element. - Operate and maintain provided GMD Element support and training equipment. Manage and perform GMD system transitions between three Simultaneous Test and Operations (STO) environments: (1) Operations, (2) Maintenance, and (3) Test/Development. 4. Ground Based Interceptor (GBI) Component - Execute design, development, integration, test, delivery and emplacement of GBIs including boost vehicle (BV) development and production, kill vehicle (KV) development and production and all up round integration. Execute booster and kill vehicle upgrades, integrate, test, and maintain/repair interceptors. - Execute GBI-Level traceability of requirements through concept definitions, , requirements definition support, models & simulation (M&S), configuration management (CM), analysis of alternatives, MBSE, trade studies, architecture definition and modifications, and long range planning studies. - Establish metrics-based analytics to address definition and traceability of internal and external interfaces, algorithm and software development including verification and validation, system level physical & logical integration, component/product level integration, analysis of system effectiveness, program management, and weapon system data and lab management. - Execute engineering releases, maintenance on current operational software, GMD allocated capability requirements, specifications, enhancements and defect repairs, designate a major or incremental software build, testing activities and fielding methods. Execute software and hardware to implement enhancements and defect correction in support of installed and test assets. Deploy software, hardware and firmware to each affected component at each test, training, and operational site and conduct a configuration controlled, quality witnessed checkout. - Support the assessment and dispositioning of various forms of software and hardware trouble reports (e.g., Test Incident Reports (TIRs), Test Problem Reports, discrepancy reports, nonconformance reports, and BMDS Discrepancy Reports (BDRs)) arising from operations; flight, ground, and cybersecurity test events; training installations; labs; and other installed locations. Execute the integration and test all products to ensure interoperability. Support the MA's conduct of in-phase Software Independent Verification and Validation (SW IV&V) of software throughout the software development cycle. 5. Ground System (GS) Component - Execute design, development, integration, test, delivery and deployment of GS components including the GMD Fire Control (GFC), In-Flight Interceptor Communications System (IFICS) Data Terminals (IDT), GMD Communications Network (GCN) and related communications components, Launch Support Systems including Silos and Silo Interface Vaults or Launch Equipment Rooms, and other GS related components essential to the GMD Program Element of the BMDS. - Execute GS-Level traceability of requirements through concept definitions, , requirements definition support, models & simulation (M&S), configuration management (CM), analysis of alternatives, MBSE, trade studies, architecture definition and modifications, and long range planning studies. - Establish metrics-based analytics to address definition and traceability of internal and external interfaces, algorithm and software development including verification and validation, system level physical & logical integration, component/product level integration, analysis of system effectiveness, program management, and weapon system data and lab management. -Execute the design, development, delivery and deployment of upgrades to the baseline via GS builds utilizing existing GS design specifications. - Execute engineering releases, maintenance on current operational software, GMD allocated capability requirements, specifications, enhancements and defect repairs, designate a major or incremental software build, testing activities and fielding methods. Execute software and hardware to implement enhancements and defect correction in support of installed and test assets. Deploy software, hardware and firmware to each affected GS component at each test, training, and operational site and conduct a configuration controlled, quality witnessed checkout. - Support the assessment and dispositioning of various forms of software and hardware trouble reports (e.g., Test Incident Reports (TIRs), Test Problem Reports, discrepancy reports, nonconformance reports, and BMDS Discrepancy Reports (BDRs)) arising from operations, Ground and Flight Test events, training installations, labs, and other installed locations. - Execute the integration and test all products to ensure interoperability. Support the MDA's conduct of in-phase Software Independent Verification and Validation (SW IV&V) of software throughout the software development cycle. ACQUISITION CONCEPTS The MDA is exploring different approaches for fulfilling the GMD Program Element requirements. Acquisition approaches under consideration range from an award of a single contract to execute the entirety of the program scope to multiple contracts to execute segments / missions of the program scope. Essential to all of the acquisition approaches under consideration is the establishment of an enduring arrangement strategy for the execution of the WSI functions across the program lifecycle, either under a single prime contract, or as one of the multiple contracts. Research indicates the use of an enduring WSI model is advantageous for programs with: - Appropriate scope, complexity, and urgency - Integration and interoperability of multiple products, hardware, and software - Complexity and risk of new development efforts - Importance of maintaining ongoing and continued operations while developing and fielding new capabilities - Nature of partnership relationship between multiple Government stakeholders and industry Notionally, the expectations for the WSI Function includes: - Responsibility for, in partnership with the Government team, conceptual, integration, and architectural design IAW requirements definition (operational, functional, physical, interface, qualification) - Responsibility for execution of developmental and operational test of the GMD element - Accountability for the systems integration, deployment, and operational performance of the GMD element - Overall GMD performance as an integrated element of the BMDS INSTRUCTIONS: Address all questions concerning this RFI in writing via e-mail to GMD-Future@mda.mil. Additional information on the GMD weapon system can be found at www.mda.mil. In accordance with the Paperwork Reduction Act, RFI submissions will only be accepted electronically. Responses to this RFI are due no later than 15 October 2019, 2:00 PM, CT. All submitted information will be handled accordingly as marked. Respondent's information/documents submitted in response to this RFI will not be returned. The Respondent's information/documents should be complete, informative, clearly demonstrate competencies and expertise in executing and delivering robust systems engineering, systems integration, and test activities. MDA will not accept any responses submitted as classified information. Industry is encouraged to respond with information that is not constrained by proprietary data rights. If proprietary data is included in the reply, the respondent is responsible for appropriate markings on a paragraph-by-paragraph basis. MDA intends to use third party, non-Government (Contractor) support as subject matter experts to review RFI responses. Appropriate non-disclosure agreements have been executed to protect and safeguard industry information. The resultant knowledge will enable MDA to achieve the best value acquisition of systems, commodities, components, technologies, capabilities, or services to fulfill its complex mission. SUBMISSION REQUIREMENTS: Interested parties are requested to provide an information package consisting of the following: 1) Respondents and/or Prospective Offerors (if a solicitation is issued) and its subcontractors/ suppliers which must be U.S. firms/businesses and not foreign owned, controlled, or influenced. 2) Responses limited to a maximum page count of 25 pages. The response shall be single-spaced, minimum 12-point Times New Roman font, and describe corporate experience and/or relevancy in the areas described in the requirements scope. Do not submit generic corporate marketing materials for this RFI. Include a company profile which should entail: Company Name, Point of Contact, Address, Telephone and Fax Numbers, Email Address, DUNS Number, CAGE Code and/or Tax ID Number, Facility Clearance Level, and all applicable socio-economic business/company profile (e.g., Large/Small Business (SB), Small Disadvantaged, 8(a), 8(m) (both Woman Owned SB and Economically Disadvantaged Woman Owned SB), Tribally Owned entity, Alaskan Native Corporation, Hawaiian Owned Organization, Service Disabled Veteran Owned SB, Historically Underutilized Business Zone (HUBZone) SB, other, etc.). 3) Responses should address the following enabler-related questions: a) What are the benefits, lessons learned, barriers to implementation, and risks for a single prime contract structure to include all program scope (Option A) and a multiple prime contract structure with strategic separation of scope (Option B)? b) Given the GMD program scope described above, what is the recommended alignment of GMD work scope if a multiple contract construct (Option B) is utilized? c) Given the GMD program scope described above, what scope area(s) would you most likely bid on if a multiple contract construct (Option B) is utilized? d) Given the GMD program scope described above, how would you recommend the MDA structure an acquisition approach to fulfill the requirement for an enduring WSI Function for multiple component contracts? e) If the MDA was to pursue multiple prime contracts (Option B), what are your recommendations for the roles, responsibilities, and organizational structure between the Government Program Office, WSI, and Weapon System Developers? f) What are your recommended areas of improvement including organizational structure, weapon system component OEM insight/oversight, schedule, management / administrative overhead, and current and approval processes boards (e.g., Risk and Engineering)? g) What integration approach could solve / alleviate integration issues if the MDA selected an acquisition approach with multiple prime contracts for development with a single prime contractor to perform the WSI Function (Option B)? How would you address any OCI issue if the MDA allowed multiple awards to single companies? h) What issues (authority, data rights, property, labs, etc.) would there be in executing WSI Functions with Component Primes if the MDA pursued multiple prime contracts (Option B)? How could these issues be mitigated? i) How has your approach been successfully implemented in other like-sized programs? j) As part of either a single or multiple component acquisition approach, the MDA is considering providing key products or equipment to the prime contractor. What are your thoughts on impacts to executing design, development, test, and deployment activities, which rely on government furnished equipment or services? k) What is your transition strategy or recommendations to the MDA to transition the GMD Program from the current construct to the DSC Follow-on Contract? Please address both the acquisition approach of a single prime contract and multiple component contracts. Approved for Public Release 19-MDA-10209 (11 Sep 19) DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.