MIOES Acquisition Strategy Summary - 14 June DRAFT RFP.pdf

This white paper summarizes the scope and highlights key acquisition points for the anticipated MIOES acquisition strategy. This is for informational and planning purposes only and the MDA reserves the right to revise details of the acquisition strategy contained herein.

NOTE: There has been a name change to this acquisition

Previous: MDA Integration & Operations for Enterprise Solutions (MIOES) New: MDA IT Operations & Engineering Solutions (MIOES)

1. Background

1.1 The Missile Defense Agency (MDA) has a continuing need for the research, development, test, evaluation, and integration of Missile Defense System components. These activities rely heavily on MDA Information Management (IM) systems, underlying Information Technology (IT), and facility infrastructure that support rigorous Missile Defense System capability development and business operations for MDA. A Research Development Test and Evaluation (RDT&E) IT ecosystem is required to provide MDA with a secure development, test, digital engineering and modeling environment, and continuous access to unclassified and classified networks and collaboration services.

1.2 Information Management and underlying IT infrastructure is also critical to the daily operations of MDA personnel to collaborate across all classification domains with each other, Senior Department of Defense (DoD) and other United States (US) Government agency personnel, Combatant Commanders, North Atlantic Treaty Organization (NATO) partners, allies, and industry partners. It requires advanced and persistent cybersecurity vigilance that ensures daily operations and communications are protected and safeguarded.

1.3 These activities are conducted across MDA’s worldwide enterprise and within the Missile Defense Integration & Operations Center (MDIOC) mission execution platform.

1.4 MDA requires a contract that can operate within the complexities of this dynamic environment to enable MDA to simultaneously conduct Missile Defense System development, testing, warfighter training, and operations support for multiple MDA directorates and Combatant Command requirement owners while executing the MDA enterprise communications and IT mission. This contract must be able to develop a capability for government and contractor stakeholders to operate within this environment that requires a continual real-time, compliant, cyber secure IT and facility infrastructure capable of conducting concurrent event execution and continual, real world, 24x7x365 mission operations.

2. MIOES Technical Areas

Technical Area (TA)

Name % of Effort

Description

Enterprise/RDT&E

IM

Global Communications & RDT&E/Enterprise Information Management (IM) Solutions & Integrated Architectures

63%

1. Communications Services & Solutions. Operational planning and logistics for the provisioning, development, integration, operations, management, sustainment, and interoperability of reliable communication networks.

2. Enterprise Services & Solutions. Services, solutions, and end-user support required to manage MDA’s globally dispersed enterprise network that simultaneously supports Missile Defense System RDT&E systems and operations.

3. System Architecture Solutions. Development of technical baselines and reference architectures for standard designs and solutions.

4. Mission Assurance and Configuration Management. Governance to establish and sustain effective operations, architectures

. 5. Cybersecurity. Provide Defensive Cyberspace Operations and robust cybersecurity solutions to protect and defend the Missile Defense System

Mission IM

Missile Defense System Mission & Event Operations:

IM Architectures & Solutions

26%

1. Design, develop, integrate, operate, and sustain secure and reliable IM architectures and IT infrastructure, for mission systems enabling a continuous operational readiness posture.

• C2BMC mission laboratories and enclaves

• Ground-Based Midcourse Defense Operations and Training

Center

• Ballistic Missile Defense System Network Operations and

Security Center

• Operations Support Center

• Missile Defense Space Enterprise Architecture

• MDA Enterprise Ground Services

• Space Test and Integration Laboratory

• Missile Defense Space Operations Center

• Modeling and Simulation infrastructure and enclaves

• JFCC-IMD Operations Center

2. Conduct Missile Defense technology maturation, design, development, prototyping, demonstration and testing.

MDIOC Facility Operations

MDIOC Operations, Sustainment, Restoration & Modernization

(SRM)

9%

1. Operate and maintain the MDIOC facility infrastructure.

• Sustainment: maintenance/ repair activities

• Restoration: restoring real property to its designated purpose

• Modernization: alteration/replacement of facilities solely to implement new or higher standards, to accommodate new functions, or replace building components

2. Minor construction activities not within scope

MDIOC

Integration

MDIOC Planning and Integration

2%

1. Planning and integration to ensure MIOES activities do not interfere with real-world Missile Defense System mission and exercise/test events performed within or supported by the MDIOC range.

2. Develop and execute mission assurance and configuration management practices and alignment to ensure MIOES activities are validated, aligned and integrated with MDIOC standards and processes.

3. Develop, implement, and deliver a MDIOC Range Integrated Schedule

• MDIOC activities, facility infrastructure and maintenance projects, network modifications/projects

4. Develop and maintain the MDIOC facility infrastructure technical baseline.

5. Establish event configuration protections for mission and test assets to prevent unapproved access/changes through physical and logical seals & access restrictions.

3. Acquisition History MIOES is a follow-on acquisition to the Integrated Research and Development for Enterprise Solutions (IRES) contract, HQ0796-17-D-0001.

Although MIOES is a follow-on to IRES, the MIOES scope is different due to the following:

• Application of DoD IT optimization initiatives

• Application of category management principles

The following table identifies the original IRES scope and how that has changed since 2017.

Original IRES Scope Current Contract Scenario MIOES Applicability

MDS Mission Operations IRES (TO1500, TO3100, TO4100, TO

5900, TO7300

TA2

MDS Testing 1. IRES (TO8003) (IT Infrastructure)

2. MDA TEAMS-Next (Test Execution)

1. TA1

2. Test execution not in MIOES scope

Wargames and Exercises 1. IRES (TO8003) (IT Infrastructure)

2. MDA TEAMS-Next (Event Execution)

1. TA1

2. Event execution not in MIOES scope

Modeling and Simulation 1. SWDC

2. IRES (TO 6100)

1. SWDC requirements not in scope

2. IRES (TO 6100) migrates to MDA’s Agency Information Management & Software Services (AIMSS) contract

Enterprise Communications & IT IRES (TO 8003, TO8700) TA1

• Unified Communications migrating to the

R&D Enterprise Collaboration Services (RECS) follow-on contract

• Data Analytics migrating to AIMSS Operation of Facility Infrastructure IRES (TO 8004, TO8600, TO8900) TA3

Systems Engineering and Program Integration (SEPI)

IRES (TO 8002) 1. MIOES program integration requirements currently performed under IRES task order 8002 will be identified in each individual task order.

2. TA4. MDIOC Planning and Integration will occur under a severable MIOES task order.

3. The following requirements, currently performed under IRES task order 8002 will migrate to the MAPSS contract (Follow-on to TEAMS Next)

• Defining, drafting, coordination of plans enabling integration of activities affecting MDIOC infrastructure.

• Monitoring of MDIOC range activities to ensure compliance with MDIOC facility technical baseline

4. Delivery or Performance-Period Requirements Based on the nature of the requirements and as a result of the market research, the contract construct is a single-award IDIQ with a maximum ordering period of eight years (five-year base with three one-year option periods).

A four-six month transition/phase-in window will minimize the potential for Missile Defense Systems event degradation and maximize the ability to provide effective, efficient, secure, and reliable services for critical DoD and MDA requirements as services are transitioned between contracts, contractor teams, and respective workforces. This will also allow sufficient time to negotiate the remaining task orders that will not be part of the contract award process.

5. Risks

5.1 The services, systems, processes, and products associated with the MIOES contract support Missile Defense System development and testing which is rapidly evolving. This leads to technical and scheduling challenges that will strain the contractor’s adaptability and ability to meet performance and schedule requirements. The contractor will also manage enterprise networks/systems in locations throughout the world in this dynamic Missile Defense environment.

In addition, the contractor must be able to:

• Execute a broad set of evolving mission, RDT&E, and enterprise requirements in a high mission operations tempo with agility and speed

• Seamlessly maneuver a workforce to execute the breadth and depth of requirements

• Foster an environment that will enable an agile and lean delivery schedule for projects

• Deliver optimized solutions that are coordinated with all applicable stakeholders

5.2 To achieve the objectives of the MDA in developing, testing, and fielding the Missile Defense System, the contractor must perform the integration of multiple disparate capabilities while simultaneously synchronizing unrelated requirements across a broad spectrum of stakeholders all vying for the same shared resources. The contractor must effectively integrate, manage, and communicate within and between all technical areas. In addition, the contractor must be able to:

• Effectively develop a single integrated master schedule across all MIOES technical areas

• Ensure mission, RDT&E, and enterprise objectives are effectively coordinated and met during

Event Protection Periods (EPPs)

• De-conflict critical assets and systems within a multi-mission environment

• De-conflict and synchronizes diverse schedules

• Rapidly react and reprioritize in order to respond to real-world events;

5.3 Requirements within and between all TAs are so integrally related that continuous coordination, integration, and management is required

5.4 The scheduling of MIOES activities is highly dependent on concurrent test, training and operations (CTTO) occurring across the enterprise and often outside the control of the contractor

5.5 DoD IT reform and optimization initiatives spanning cyber security, enterprise services, network services, and operations are continually evolving

6.0 Competition

A full and open competition will be utilized. All announcements will be released through SAM.gov to seek, promote, and sustain competition.

7.0 Contract type selection

7.1 A single-award IDIQ structure was determined appropriate. Because of the nature of the RDT&E and event-driven MDA environment the MIOES contract operates under, MDA is precluded from predetermining, above a specified minimum, the precise quantities of supplies or services that it will require during the contract period.

7.2 Based on the comprehensive integration requirements supporting a dynamic Missile Defense landscape and in accordance with FAR 16.504(c)(1)(ii)(D)(1), it was determined that the MIOES task orders are so integrally related that only a single source can reasonably perform the work.

7.3 The MIOES contract will offer multiple contract types and incentive structures at the task order level. This allows for the task order contract type and incentives to be tailored to stakeholder requirements at the task order level.

• Firm Fixed Price (FFP)

• Fixed Price Incentive Firm (FPIF)

• Cost Plus Incentive Fee (CPIF)

• Cost Plus Fixed Fee (CPFF)

• Cost Plus Award Fee (CPAF)

• Time and Materials (T&M) with a Not-To-Exceed ceiling

• Cost Reimbursement (CR)

- Will be utilized for MIOES Non-prime contract labor/ODC type requirements like travel, equipment, SW licenses, materials, vendor support

8.0 Incentive structures

Incentive structures will be tailored by task order. Potential examples of incentives:

• Information assurance workforce training & certifications

• First call resolution

• Hardware performance

• Service Level Agreement compliance

• Automation

• Mean Time To Repair

• Accuracy of software records

• Accuracy of property records

• Operations availability of network systems

• Restoration incidents

• Unplanned outages

• Malware instances

• Enclave accreditation

• Cybersecurity compliance

• Approved/Unapproved event seals

• Schedule

• Quality

9.0 Source-selection procedures

Source selection will be conducted using the best value tradeoff process described in FAR 15.101-1 and the source selection procedures identified in FAR Subpart 15.3, as supplemented by DFARS Subpart 215.3, and MDA Instruction 5013.06, Source Selection Procedures, (June 5, 2023), based upon an integrated assessment of the factor and subfactors. To be eligible for award, the Offeror must be deemed responsible in accordance with FAR subpart 9.1, to include FAR 9.104-1; have an accounting system adequate for determining costs applicable to the contract are in accordance with FAR 16.301-3(a)(3) and FAR 9.104-1(e); conform to all required terms and conditions established in the RFP; and include all applicable certifications that are required.

10.0 Acquisition considerations

10.1 Pursuant to FAR 15, this acquisition will be negotiated because award will not be based on only cost/price and cost-related factors; it will be necessary to conduct discussions with offerors.

10.2 The MIOES contract is predominantly for services, although material and IT items will be required in order to execute the service requirements and develop required solutions.

10.3 This will be a performance-based acquisition as defined by FAR subpart 37.6. Measurable performance standards can be defined.

11.0 Product or service descriptions

11.1 The primary focus of the MIOES contract is to:

• Develop and maintain MDA’s IM system and underlying IT infrastructure that enables rigorous RDT&E of missile defense capabilities to support the assessment and evaluation for future fielding decisions and to provide MDA with a secure development, test, digital engineering and modeling environment and continuous global network connectivity to enable agency RDT&E and Enterprise operations.

• Design, develop, integrate, operate, and sustain a secure and reliable IM architectures and infrastructure for mission systems, enabling a continuous operational readiness posture.

• Develop and execute mission assurance and configuration management practices and alignment to ensure MIOES activities are validated, aligned, and integrated with MDIOC standards and processes.

• Planning and integration to ensure MIOES activities do not interfere with real-world Missile Defense System mission and exercise/test events performed within or supported by the MDIOC range.

• Operate and maintain the MDIOC facility infrastructure.

11.2 The proposed NAICS is 541715—Research and Development in the Physical, Engineering, and Life Sciences (except Nanotechnology and Biotechnology)

11.3 The predominate Federal Procurement Data System Product and Service Code (PSC) is AC13

- National Defense R&D Services; DoD – Military; Experimental Development. The following PSCs also apply:

• M1BG – Electronic and Communications Facilities

• 7A21 – Business Application Off-The-Shelf Software

• 7K20 – Information Technology Input/Output and Storage Devices

• 4940 – Miscellaneous Maintenance and Repair Shop Specialized Equipment

11.4 Based on the nature of the requirements and as a result of the market research conducted, the MIOES acquisition does not meet the commercial item definition in FAR 2.101; FAR Part 15 procedures will be used for the MIOES acquisition.

12.0 Cost Reporting

MIOES will implement Earned Value Management System (EVMS) requirements on the prime contract and any subcontract that meets EVMS application requirements. All TOs will require an Integrated Program Management Data and Analysis Report (IPMDAR) which will be tailored to meet the needs of the program. For TOs that do not meet the EVMS application requirements, the EVMS DFARS clause will not be applied, however, a tailored IPMDAR will still be required.

For FFP TOs and CLINs cost reporting will not be required, yet a tailored IPMDAR containing only an Integrated Master Schedule may be applied as necessary. In addition, a tailored MIOES summary IPMDAR will be required that will provide summary data for contract wide program management.

13.0 Government-furnished property

The contractor will be provided GFP. Contractor Acquired Property (CAP) from the IRES contract will be accepted by MDA at the end of that contract, and issued back to the MIOES contractor as GFP. The contract will contain all required GFP clauses, to include FAR clause 52.245-1, Government Property. Any GFP identified as required in the resultant contract, will be captured as an attachment in Section J of the contract and appropriately tracked. All GFP will be managed within the Defense Property Accountability System (DPAS) and marked IAW Item Unique Identification (IUID) procedures. The contractor will utilize/maintain the MDA provided Remedy system for the management of GFP and CAP.

14.0 Government-furnished information

The Government will provide a bidder’s library for the RFP. To obtain access to the bidder's library the contractor must email the PCO to request access. The PCO will determine whether access will be granted. Access to the library will be granted through the Procurement Integrated Enterprise Environment, known as PIEE, which has the capability to control access to Unclassified (but not appropriate for public release) and Controlled Unclassified Information (CUI). An Access Agreement form will also be completed by the requestor.

Each requestor will agree to the following, “In submitting this request, I, on behalf of my company, agree to the following document handling procedures: Only US persons with need to know will have access to the MDA Missile Defense System CUI provided to support the MIOES acquisition. My company will comply with the DFARS clause 252.204-7012 for protection of Missile Defense System CUI on the company’s unclassified information systems.” A DD 254 will be provided to all companies approved for participation in this acquisition.

15.0 Security considerations

15.1 The contract will require access to classified information up to the Top Secret level, to include access to Sensitive Compartmented Information (SCI) and involve Special Access Programs. The contract will incorporate a DD254 requirement and FAR 52.204-2 “Security Requirements” that will prescribe all appropriate security requirements and considerations. All classified processing/storage will be at MDA site and not contractor site.

15.2 The contract will require contractors to have routine physical access to a Federally-controlled facility and/or routine access to a Federally-controlled information system. FAR clause 52.204-9, “Personal Identity Verification of Contractor Personnel,” will be incorporated in the contract to implement requirements from Federal Information Processing Standard (FIPS) PUB 201 as amended, and Office of Management and Budget guidance M-05-24.

15.3 The contract operates in accordance with all applicable Security Classification Guides (SCG). MIOES personnel will ensure classified or unclassified sensitive data collected, generated by, and/or delivered to the MDA is adequately protected at all times. MIOES personnel will receive and document annual training to facilitate the implementation of required security processes and expectations.

15.4 The MIOES contract also operates IAW the DoDI 8500.01, Cybersecurity,” MDA Instruction 8540.01 Network Connection Approval Process, and DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT), for the implementation of RMF on MDA systems and in the governance structure of DoD information systems. The MIOES contract will utilize the definitions for the assigned cyber workforce and outline roles and responsibilities for the management of the DoD cyber workforce IAW DoD Directive 8140 series. Information Assurance Workforce Improvement Program (DoDM 8140.03) provides guidance and procedures for the training, certification, and management of the DoD workforce conducting Information Assurance (IA) functions in assigned duty positions. These DoD policies describe how cybersecurity of systems and personnel requirements for DoD information systems.

15.5 The MIOES contract will adopt National Institute of Standards and Technology (NIST) Cybersecurity Framework 2.0 standards.

15.6 The contract will require registration in MDA’s Cyber Workforce Management Program.

MDA will enforce NIST SP 800-171 Rev 2 Protecting CUI in Nonfederal Systems and Organizations. The contract will contain the following clauses and provisions:

• FAR 52.204-21, “Basic Safeguarding of Covered Contractor Information Systems”

• DFARS 252.239-7001, “Information Assurance Contracting Training and Certification”

• DFARS 252.204-7009, “Limitations on the Use or Disclosure of Third-Party Contractor

Reported Cyber Incident Information.”

• DFARS 252.204-7012 “Safeguarding Covered Defense Information and Cyber Incident

Reporting”

• DFARS 252.204-7019, “Notice of NIST SP 800-171 DoD Assessment Requirements”

• DFARS 252.204-7020, “NIST SP 800-171 DoD Assessment Requirements”

• DFARS 252.239-7017, “Notice of Supply Chain Risk”

• DFARS 252.239-7018, “Supply Chain Risk”

• MDA Information Management and Control Plan (IMCP)

• DoDI 5200.48, Controlled Unclassified Information

16.0 Constraints

16.1 MDA missions executed from the MDIOC require a 24x7x365, compliant, cyber secure IT and facility infrastructure capable of supporting concurrent event execution and mission operations. IT and facility infrastructure heavily dependent on each other through the MDIOC platform require agility and robust integration.

16.2 Schedules and requirements are driven and dictated by enterprise, RDT&E, Missile Defense System test events, and operational mission activities.

16.3 Unique mission and RDT&E hardware, software, interface, configuration control, cybersecurity challenges and limitations, rapid resource reprioritization and dynamic scheduling constraints must be met, managed, de-conflicted to ensure mission success.

16.4 The MDIOC operates within Space Base Delta 1 – restricted area on Schriever Space Force Base.