MIOES Phase-In Task Order PWS 14 June DRAFT RFP.pdf

Page i

MIOES

MDA Information Technology Operations & Engineering Solutions Task Order Number: TBD

MIOES Phase-In Performance Work Statement Period of Performance: TBD (Six Months) Contract Type: Firm Fixed Price

June 14, 2024

DRAFT

Page ii

Change History

Version Date Mod # Changes

Page iii

Table of Contents

1.0 Vision and Purpose Statement

1.1 Vision

2.0 Background

3.0 Scope

5.0 Contract Data Requirement List

6.0 Milestones (TBD-Will be populated with milestones proposed in Phase-In Plan)

7.0 Government Property and Facility Support

8.0 Facts

9.0 Applicable Directives / Regulations

10.0 Performance Requirements

10.1 Task Order Leadership and Management

10.2 Phase-In Requirements

1.0 Vision and Purpose Statement

1.1 Vision

Execute a streamlined, transparent and seamless transition from the current Integrated Research and Development for Enterprise Solutions (IRES) contract to the new MDA Information Technology Operations & Engineering Solutions (MIOES) contract while ensuring uninterrupted Concurrent, Test, Training, and Operations (CTTO).

2.0 Background

The IRES contract has approximately 10 – 12 active task orders that are expected to transition to the MIOES contract. These task orders will be negotiated and awarded during the transition period. Exhibit 2 provides a list of the task orders that will transition. A schedule will be provided for proposing and negotiating the task orders. The start date [effective date] of all task orders (other than the Transition TO) will be 8 February 2027.

Exhibit 1. Legacy IRES Task Orders that will transition in whole or in part to MIOES during the transition period.

This list of task orders may evolve, merge, or evaporate; the list provided here is current as of publishing of the document.

IRES TO # Title F8002 Integrated Research & Development for Enterprise Solutions F5900 C2BMC Infrastructure, Engineering, and Event Services F8003 Enterprise Information Technology Services (EITS) F8004 Facilities Engineering and Operations (FE&O) F8700 Information Technology (IT) Projects F8900 Supply Chain Product Support and Government Property Management F1500 Joint Functional Component Command for Integrated Missile Defense (JFCC IMD) Engineering and

Maintenance F3100 Ground-Based Midcourse Defense (GMD) Operations and Training Support F4100 Missile Defense Space Center (MDSC) Operations and Maintenance F7300 Engineering Web Services F8600 MDIOC Infrastructure Support Projects F8800

3.0 Scope

This PWS encompasses all phase-in activities necessary to transfer all capabilities, responsibilities, and services from the IRES contract to the MIOES contract. The incumbent contractor is responsible for mission accomplishment during the transition window with the MIOES contractor responsible to assume 100% of mission accomplishment the day immediately following the transition window with no interrupted execution of the MIOES mission.

5.0 Contract Data Requirement List

Task CDRL DID Title

10.1.2 001 DI-MGMT-80368A Status Report

10.2.3 002 DI-MISC-80508B/T Technical Report - Study/Services (Phase-In Plan)

6.0 Milestones (TBD-Will be populated with milestones proposed in Phase-In Plan)

Task Activity Days After Contract (DAC)

Note: DAC = Task Order Period of Performance Start Date

7.0 Government Property and Facility Support

The MIOES contractor will not assume property accountability responsibility until the completion of the contractor’s inventory of existing government property. The inventory will not be conducted under the transition task order; the inventory will be conducted under the Property Management and Accountability task order that will be awarded during the transition period. Upon accomplishment of the inventory under that task order, government property will be transferred to the contractor as Government Furnished Property (GFP). The contractor will assume property management and accountability of approximately 125,000 items under the Property Management and Accountability task order.

It is not anticipated that Government Acquired Property (GAP) is required under this task order.

A modification to the task order will be executed if GAP is required.

The Government will provide conference rooms and office space and equipment and Unclassified Local Area Network/Classified Local Area Network (ULAN/CLAN) access for approximately 15 people at the Missile Defense Integration & Operations Center (MDIOC) in Colorado Springs and the Von Braun Complex in Huntsville during the transition period. This space will be made available one week prior to the start of the task order. Additional facility space can be made available to support interviews, if required.

The MDIOC Presentation Center and the VBIII Auditorium will be available for scheduling gatherings that require a larger venue.

8.0 Facts

The following facts are applicable to this task order:

8.1 A Government van and driver can be made available to help transport bulk items inside the Restricted Area at Schriever Space Force Base.

8.2 The incumbent contractor has one Associated Contractor Agreement with Lockheed Martin that aligns with Information Technology (IT) Projects.

8.3 Existing software/hardware licensing agreements, plans, processes, or procedures from MDA and the IRES contractor will be provided to the contractor prior to day one of the task order start date.

8.4 An initial list of critical/high risk MDA activities, processes, and personnel that should be observed, understood, and coordinated to ensure a continuity of services upon contract award after contract award and before the transition task order begins is identified in Appendix A.

8.5 The contractor shall be given access to the Program Resource Internet Database Environment (PRIDE) Workforce Integration Tracking System (WITS) module, in accordance with MDA Instruction 1400.07-INS, in order to in-process new employees within the first 5 days of the task order start date.

8.6 The incumbent IRES contractor will make themselves available to meet with the MIOES team in executing transition activities. The incumbent Phase-Out Plan will be provided at time of award.

8.7 The contractor shall be offered a dedicated collaboration site for information management and communication requirements.

8.8 The incumbent contractor will provide policies, plans, manuals, procedures and standards that are critical to ongoing MIOES operations.

8.9 The contractor will be given an opportunity to meet with each MDA organization that owns a MIOES task order for a deep dive into their requirements within the first 14 calendar days of the task order start date.

8.10 The PCO will provide a list to the contractor of all IRES employees and their respective employer.

8.11 The IRES contractor will provide a complete list of ongoing projects, the status of each project, and identify those that will continue under MIOES within the first 5 days of the MIOES transition period.

8.12 Workload data required for the transition task order

• Approximately 900 – 1,400 personnel must maintain or obtain access to MDA facilities and MDA networks

• Approximately 500 personnel must maintain or obtain System administrators rights.

9.0 Applicable Directives / Regulations

In addition to the directives and regulations identified in Request for Proposal (RFP) Attachment TBD, the following are applicable to this task order:

• None

10.0 Performance Requirements

10.1 Task Order Leadership and Management

The contractor shall provide task order level leadership, management, administration, and integration activities required to execute task order requirements within the integrated enterprise framework of the contact. The contractor shall integrate and coordinate all activities needed to execute the requirements.

10.1.1 Provide a Program Manager as a single point of contact to manage cost, schedule, risk and technical performance

10.1.2 Provide situational awareness, report status and insight on cost, schedule, risk and technical performance, significant accomplishments; customer concerns or issues; risks and mitigation status; performance against the PWS objective measurements.

• CDRL 001: Status Report

10.1.3 Adjustments or refinements to the contractor’s business systems are made in advance and ready for deployment and integration during the transition window

10.1.4 Identify and measure risk and develop and implement risk mitigation strategies.

Include potential solutions; analyze overall risk; analyze their impact; track, update, and re-assess changing risks and mitigation actions; and ensure risk information is communicated to MDA/IS leadership on a weekly basis and documented in CDRL 002.

10.2 Phase-In Requirements

The contractor shall develop, plan, and execute all activities necessary to phase-in all capabilities, responsibilities, and services from the IRES contract to the MIOES contract.

10.2.1 Participate in a contract kick-off meeting with IS Program Office within two working days of the task order start date.

10.2.2 Participate in a post award conference 10 calendar days of task order start date.

10.2.2.1 Discuss the contractor’s standard Cost and Software Data Reporting (CSDR) process that satisfies the guidelines of DoD 5000.04-M-1 and the requirements in the Government-approved CSDR provided at RFP Attachment ????.

10.2.3 Deliver and execute an updated Phase-In Plan that was submitted with the RFP within 14 calendar days of the task order start date.

• CDRL 002: Technical Report - Study/Services (Phase-In Plan)

10.2.3.1 Identify critical/high risk MDA activities, processes, and personnel that should be observed during transition

10.2.3.2 Identify incumbent processes that must be incorporated by day one of the contract to ensure continuity of services

10.2.3.3 Identify tasks in which employees’ activities fall under the purview of the International Traffic in Arms Regulations (ITAR) (22 CFR 120-130) and manage the ITAR and Technical Assistance Agreement (TAA) processes

10.2.3.4 Include a detailed integrated transition schedule that identifies the milestones, activities, events, deliverables and associated dates

10.2.3.5 Include a staffing plan based on the staffing requirements of each task order

10.2.4 Provide the resources and expertise to engage with the IS Program Office in following the Task Order Award/Modification process (Reference Attachment L-??) to award all MIOES task orders identified in paragraph 2.0.

10.2.4.1 Complete task order negotiations within the established schedule

10.2.4.2 Provide Integrated Team Process (ITP) members that are knowledgeable of task order subject matter and are empowered to make real-time decisions

10.2.5 Conduct weekly Transition Readiness Reviews with the IS Program team covering topics such as:

10.2.5.1 Status of transition activities

10.2.5.2 Transition schedule updates and modifications

10.2.5.3 Review of risk management activities—identification, tracking, and mitigation of mission execution and performance risks that affect the achievement of continuity of services

10.2.6 Collaborate and provide timely, accurate, and comprehensive information to all MIOES stakeholders (e.g., MDA, IRES leadership and IRES employees).

10.2.7 Conduct a final transition progress review approximately 5 days prior to the end of the task order to verify with IS Program leadership that all transition tasks have been accepted.

10.2.8 Participate in IRES and MDIOC Risk Management Boards.

10.2.8.1 Gain familiarity with the Risk Management Board participants, process, and tools

10.2.8.2 Gain familiarity with the current risk management culture

10.2.8.3 Gain understanding into risks that must be addressed either during the transition period or accepted after the start of each task order

10.2.9 Establish a shadowing program on a noninterference basis to observe critical processes to enable continuity of services on day one of contract performance

10.2.10 Review and analyze the current Integrated Master Test Plan (IMTP), IT sustainment and modification plans, and test deployment resources and collaborate with the Government to identify key activities required to maintain continuity of operations. Key event activities include the following:

10.2.10.1 Test event meetings, phase reviews, and executive reviews for local primary, secondary, tertiary, and associated operations test participants as required for ongoing MDA supported events

10.2.10.2 Post-test executive reviews as required for ongoing MDA supported events

10.2.10.3 Continuous development, flight testing, ground testing, and cyber testing as required for ongoing MDA supported events

10.2.10.4 Test deployment as required for ongoing MDA supported events

10.2.10.5 Attend relevant mission planning, technical interchange meetings, etc.

during transition for ongoing MDA supported events

10.2.11 Achieve continuity of services by providing Software/Hardware licensing capabilities, transitioned System Administrator rights and in maintaining or obtaining access to MDA networks for all personnel migrating from IRES

10.2.12 Achieve continuity of services by identifying and selecting qualified personnel who hold appropriate security clearances required to execute assigned responsibilities and have the applicable training / certifications necessary to operate, maintain, and execute MIOES processes, operations, functions, and infrastructure

10.2.13 Develop an early procurement capability to acquire specific long-lead items to facilitate continuity of operations and to enable rapid initiation of projects upon the start of stakeholder task orders. A contract modification will be executed if procurements actions are required

10.2.14 Coordinate and collaborate with the appropriate government stakeholders in performing the following activities:

10.2.14.1 Issue employee badges

10.2.14.2 Submit and manage Top Secret/Sensitive Compartmented Information (TS/SCI), Special Access Program (SAP), and Special Access Required (SAR) billet requirements

10.2.14.3 Track personnel security requirements to include TS/SCI, SAP, and SAR indoctrination

10.2.14.4 Oversee, track, and schedule Common Access Card (CAC) issuance

10.2.14.5 Oversee subcontractor security requirements

10.2.14.6 Transition classified holdings

10.2.14.7 Ensure all security-related requirements are met (e.g., DD 254, Visitor Group Security Agreement [GSA])

10.2.14.8 Ensure System Administrator rights are transitioned

10.2.15 Deliver a Phase-In task order lessons learned briefing as an attachment to the Status Report CDRL.

10.2.15.1 Identify what went well and issues encountered during the transition window.

10.2.15.2 Capture processes and recommended process improvements for future MDA acquisitions.

10.2.15.3 Deliver a draft briefing 20 days prior to the end of the task order and the final briefing with the last status report.

APPENDIX A

Critical/high risk MDA activities, processes, and personnel to be observed, understood, and coordinated to ensure a continuity of services immediately upon the contract start date.

Appendix A will be populated with the release of the final Draft RFP.