23F8600_PWS.pdf

i

PERFORMANCE WORK STATEMENT

Missile Defense Agency (MDA) Integrated Research & Development for Enterprise Solutions (IRES)

Contract Number: HQ079617D0001

Task Order Title: Infrastructure Support Projects

Task Order Number: HQ085723F8600

Period of Performance: 9 January 2023 – 8 August 2025 ii

Performance Work Statement Revision History Version Date Mod # Change Description iii

TABLE OF CONTENTS

1. PURPOSE

2. BACKGROUND

3. SCOPE

4. SERVICE SUMMARY ITEMS

5. CONTRACT DATA REQUIREMENTS LIST

5.1 CDRL Identification

5.2 CDRL Tailoring

6. MILESTONES

7. GOVERNMENT PROPERTY

8. SPECIAL REQUIREMENTS

9. APPLICABLE DOCUMENTS

10. STATEMENT OF OBJECTIVES AND OUTCOMES

10.1 Task Order Administration

10.1.1 Task Order Management

10.1.2 Objective: Enterprise Task Order Support

10.1.3 Task Order Award and Modification

10.2 Task/Project Planning and Exploration

10.3 Immediate Response Task

10.4 Quick Response Task

10.5 Discrete Projects

11. DISCRETE PROJECTS

1. PURPOSE

The purpose of this Performance Work Statement (PWS) is to enable facility modifications and sustainment projects that are required to support MDA mission activities at the Missile Defense Integration and Operations Center (MDIOC) on Schriever Space Force Base (SFB) in Colorado Springs, Colorado (COS), and its Area of Responsibility (AOR).

2. BACKGROUND

The MDIOC provides the necessary infrastructure and support services through a mission execution platform for MDA elements/components and designated Combatant Commanders' (CCMDs’) Missile Defense System (MDS) operations executing missions at the MDIOC (24/7/365).

The MDIOC was built in 1989 and was designed to a 67-year life cycle. Building 720 is the MDIOC research and operations complex. It encompasses approximately 536,000 square feet and consists of 3 floors with 4 quadrants (quads) on each floor and a basement sector. It includes numerous element-level laboratories (labs), Special Access Programs (SAPs), test centers, conferencing facilities, and operational capabilities supported by highly reliable facility, communications, and IT infrastructure.

The complex has an 8,575-square-foot presentation center, a 19,880-square-foot data center, and an 11,060-square-foot Main Communications Hub (MCH). The open-span architecture of Building 720 allows for rapid reconfiguration of work areas, IT, and communications resources via an accessible between-floor central cable chase and modular workspace configurations.

Building 730 is the MDIOC Consolidated Support Facility (CSF), which encompasses approximately 110,500 square feet and consists of 3 floors, including the main lobby, administrative office areas, and the basement sector. It provides administrative office space, conferencing facilities, an international events center, and food service (i.e., a dining facility). Building 730 connects to Building 720 via the main entrance lobby and the basement.

3. SCOPE

The scope of this PWS is to enable facility sustainment, restoration, repair, modification, and modernization tasks required to support MDA mission activities at the MDIOC on Schriever SFB and its AOR.

4. SERVICE SUMMARY ITEMS

IAW the IRES Performance Evaluation and Incentive Plan, Service Summary Items (SSIs) 1–4 are common (i.e., required) on all Task Orders (TOs) and will be assessed at the contract level (i.e., all TOs will receive the same rating). SSIs 1–4 are documented in the Performance Evaluation and Incentive Plan.

SSIs 5–9 (Technical Performance) capture the specific TO SSIs deemed essential to successful execution of the TO.

SSI Definition Name Detailed Design Review CDRL 003 Delivery Identifier SSI #5 Definition The contractor delivers all detailed design documents required for the DDR briefing NLT two BDs before the DDR briefing. The contractor will gain Government approval of the timeline to complete any open action items from the DDR briefing. The contractor will hold a DDR Action Item briefing with the Government to gain their approval of the open action items from the DDR briefing.

Once Government approves of the Action Item closure, the contractor will submit the CDRL within five BDs of the Action Item closure briefing.

Measurable Concept Final Design Complete

Questions Addressed

Were the supporting artifacts required for the DDR delivered IAW Attachment 1 of the PWS?

Baseline Measure

Detailed design is complete and at the 100% level in all disciplines. All required artifacts will be delivered 2 business days in advance of the scheduled milestone brief IAW Attachment 1 of the PWS.

Technical Performance Measures

Definition: QPI:

DDR artifacts required for the DDR brief are delivered on time IAW the schedule milestone documented in the Project Description. 20

DDR artifacts were delivered 1–5 business days late. 15 DDR artifacts were delivered 6–10 business days late. 10 DDR artifacts were delivered 11–15 business days late. 5 DDR artifacts were delivered more than 15 business days late. 0

Notes The SSI score at the end of each Performance Review Board (PRB) review period will be the average SSI score of all DDR packages delivered from the beginning of the TO to the end of that respective PRB review period.

Name Joint Final Inspection Milestone Identifier SSI #6 Definition The contractor conducts the JFI within the defined schedule milestone. The required artifacts are delivered 2 business days prior to the JFI brief, as defined in Attachment 1 of the PWS.

Measurable Concept Completion of Implementation Activities

Questions Addressed

Were the supporting artifacts delivered and work completed IAW the PWS and Task/Project Description?

Baseline Measure Implementation activities are complete per the PWS.

Technical

JFI conducted on time IAW the PWS. 20 JFI conducted but occurred 1–3 business days late. 15 JFI conducted but occurred more than 4–7 business days late. 10 JFI conducted but occurred more than 8–10 business days late. 5 JFI conducted but occurred more than 10 business days late. 0

Notes Each JFI package will receive one SSI score at original submission; all resubmissions will not receive a separate score. The SSI score at the end of each PRB review period will be the average SSI score of all JFI packages delivered from the beginning of the TO to the end of that respective PRB review period.

Name Closeout Milestone CDRL 004 Delivery Identifier SSI #7 Definition CDRL C004 is delivered on or before the designated milestone.

Measurable Concept Task/Project Closeout Complete

Questions Addressed Were the supporting artifacts delivered IAW CDRL C004?

Baseline Measure Task/Project Closeout documentation complete and delivered IAW CDRL C004 requirements.

Technical

CDRL C004 delivered on time. 20 CDRL C004 delivered 1–5 business days late. 15 CDRL C004 delivered 6–10 business days late 10 CDRL C004 delivered 11–15 business days late. 5 CDRL C004 delivered more than 15 business days late. 0

Notes

Each CDRL C004 package will receive one SSI score at original submission; all resubmissions will not receive a separate score. The SSI score at the end of each PRB review period will be the average SSI score of all CDRL C004 packages delivered from the beginning of the TO to the end of that respective PRB review period.

Name CDRL Quality Identifier SSI #8 Definition Delivery of CDRLs that are compliant with the DD Form 1423, Contract Data

Requirements List (CDRL) Measurable Concept Quality

Questions Addressed

Was the CDRL delivered IAW the DD Form 1423, Contract Data Requirements List (CDRL)?

Baseline Measure CDRL documentation complete and delivered IAW the DD Form 1423, Contract Data Requirements List.

Technical

CDRL delivered IAW the DD Form 1423, Contract Data Requirements List (CDRL). Approved with no comment. 15

CDRL delivered IAW the DD Form 1423, Contract Data Requirements List (CDRL). Approved with comment; resubmission not required. 15

CDRL delivered IAW the DD Form 1423, Contract Data Requirements List (CDRL). Approved with comment; resubmission required. 7

CDRL has been delivered and is not approved with comments. 0

Notes Each CDRL will receive one SSI score at original submission; all resubmissions will not receive a separate score. The final score for each six-month evaluation period will be the average of the SSI score of each delivered CDRL during that period. The SSI score at the end of each PRB review period will be the average SSI score of all CDRLs delivered from the beginning of the TO to the end of that respective PRB review period.

Name Test Event/Mission Operations Interruption Identifier SSI #9 Definition Contractor caused an unplanned interruption to a test, wargame, or exercise event or critical operational mission associated with the following operational organizations located at the MDIOC:

• 100th Missile Defense Brigade (BDE) (MDB)

• Joint Functional Component Command for Integrated Missile Defense (JFCC

IMD)

• BMDS Network Operation Security Center

• Command and Control (C2), Battle Management, and Communications

(C2BMC) System Support Center

• Missile Defense Space Center (MDSC)

• Warfighter Support Integration

Contractor caused an unplanned interruption to a critical mission associated with the following 24/7/365 operations centers:

• Security Operations Center (SOC) (Room B33-1)

• Operations Support Center (OSC) (Room 1120)

• Intelligence Watch Center (Room 1305)

• BNOSC (Room 1117)

• MDA Cybersecurity Emergency Response Team (CERT) (Room B-78)

• JFCC IMD (Room 1408)

• 100th BDE (Room 1207)

• MDIOC Network Operations Center (NOC) (Room 1107)

• GM Readiness Desk (Room 1120)

• Global Network Operations and Security Center (GNOSC) (Room 2409)

Measurable Concept

Contractor caused an unplanned interruption to a test, wargame, or exercise event or critical operational mission.

Questions Addressed

Did any contractor action performed under this TO lead to an unplanned interruption to a test, wargame, or exercise event or critical operational mission?

Baseline Measure Any contractor action occurring under this TO does not cause an unplanned interruption to a test, wargame, or exercise event or critical operational mission.

Technical Performance Measure

Each contractor action that causes an unplanned interruption to a test, wargame, or exercise event or a critical operational mission during each PRB review period will result in a 10-point reduction to the QPI score for that 6-month assessment period.

Notes An interruption is defined as an unplanned break in a test, wargame, or exercise event or critical operational mission due to contractor action of an activity performed under this TO.

5. CONTRACT DATA REQUIREMENTS LIST

The point of delivery for all Contract Data Requirements List (CDRL) products, except as noted in Exhibit C, is the MDA Electronic Content and Records Tool (ECaRT) system. The contractor shall deliver all such products by saving and profiling them in ECaRT, with the appropriate notification of delivery letter transmitted electronically to the Government’s Data Management Office (DMO). Reference Exhibit C for specific CDRL delivery instructions.

5.1 CDRL Identification

Task CDRL Data Item

Description (DID) Title Description

10.1.2.2 C001 DI-MGMT-81861/T HQ085723F8600:

Integrated Program Management Report

Contains data for measuring cost and schedule performance. The IPMR is structured around seven formats that contain the content and relationships required for the electronic submissions.

10.1.2.2 C002 DI-MISC-80508B/T HQ085723F8600:

Task Order Status Report, [month ending]

Provides significant accomplishments, issues, concerns, LL, and risks associated with the TO.

10.4.1.5 C003 DI-MISC-80508B/T HQ085723F8600:

Engineering Documentation, Detailed Design

Detailed design documentation as defined in Attachment 1 of the PWS.

10.4.1.7, 10.5.1.6

C004 DI-MISC-80508B/T HQ085723F8600:

Engineering Documentation, Closeout

Closeout documentation as defined in Attachment 1 of the PWS.

5.2 CDRL Tailoring

The Department of Defense (DD) Form 1423, Contract Data Requirements List (CDRL), associated with each CDRL is attached to the TO.

6. MILESTONES

• Initial Integrated Baseline Review (BR) (IBR)—90 days after TO award

• Annual IBR—annually from the initial IBR The milestones associated with Sections 10.3, 10.4, and 10.5 will be identified in the Technical Direction Letter (TDL), Mission Support Task (MST) description, or Project Description, respectively.

The Task Change Requirement (TCR) process shall be followed by the contractor to document and communicate cost, schedule, performance, and requirements changes, and their associated impacts for all efforts performed under Sections 10.3, 10.4, and

10.5. The TCR form is completed by the contractor. When there is an impact to the schedule and/or performance, the contractor shall submit a TCR to the Contracting Officer’s Technical Representative (COTR)/Alternate COTR (ACOTR) as soon as the impact becomes known but No Later Than (NLT) one week after a potential impact that affects a contractual schedule milestone is identified. When there is an impact to the cost, the contractor shall submit a TCR to the COTR/ACOTR and the Procurement Contracting Officer (PCO) within two weeks of when the cost impact became known to Jacobs.

7. GOVERNMENT PROPERTY

• 7.1 In addition to the Government Property (GP) associated with the TO 8900 series, the following GP is applicable to this TO: None

• 7.2 In addition to the Government-Furnished Property (GFP) identified in Attachment 5 of the Integrated Research & Development for Enterprise Solutions (IRES) Contract, the following GFP is applicable to this TO: None

• 7.3 The following Government-Furnished Information (GFI) is applicable to this TO:

None

• 7.4 All Contractor-Acquired Property (CAP) shall be managed under the terms and conditions associated with the TO 8900 series.

8. SPECIAL REQUIREMENTS

In addition to the special requirements identified in the Integrated Research & Development for Enterprise Solutions (IRES) Contract Statement of Objectives (SOO), the following are applicable to this TO: None.

9. APPLICABLE DOCUMENTS

In addition to the directives and regulations identified in Paragraph 8.0 of the Integrated Research & Development for Enterprise Solutions (IRES) Contract Statement of Objectives (SOO), the following are applicable to this TO and will be further defined for each project or task:

Title Document ID Originator Date Facility Management MDA 6015.01-

INS

MDA 18-Apr-17

Real Property Acquisition and Sustainment Restoration, Modernization and Accountability

MDA 4165.01-

DIR

MDA 26-May-17

USD (AT&L) Memo, Department of Defense Unified Facilities Criteria

None Under Secretary of Defense

(USD)

29-May-02

Unified Facility Criteria (UFC) DoD Minimum Antiterrorism Standards for Buildings

UFC 4-010-01 National Institute of Building Sciences

(NIBS)

12-Dec-18

Unified Facilities Guide Specifications (UFGS) None Various U.S. Army Corps of Engineers Design Submission Requirements Manual

NANP-1110-1-1 U.S. Army Corps of Engineers

(USACE)

Current

Planning and Programming Appropriated Fund Maintenance, Repair, and Construction Projects

Air Force (AF) Instruction (AFI) 32-1032

AF 24-Nov-15

Real Property Accountability and Reporting AFI 32-9005 AF 04-Mar-15 Standard Facility Requirements AFI 32-1024 AF 14-Jul-11 Electrical Safe Practices AFI 31-1064 AF 29-Dec-16

Title Document ID Originator Date Grounding Systems AFI 32-1065 AF 12-Jan-15 MDIOC Engineering Review Board Charter None MDA/MDIOC 06-Jul-21 MDIOC Facility Systems Engineering Plan TO 8002, CDRL

C041 MDA 05-Oct-21

MDIOC Facility Quality Assurance Plan TO 8002, CDRL

C043, DI-MISC-

80508B/T

MDA 30-Nov-21

MDIOC Facility Configuration Management Plan TO 8002, CDRL C022

MDA 01-Oct-21

Information Technology Infrastructure Installation Guide

MDA 8350.01 MDA 08-Jul-22

Contract Data Requirements List (CDRL) DD Form 1423 DoD 01-Aug-96 Risk Management Framework DoDI 8510.01 DoD 29-Jul-17 Critical Program Information (CPI) Identification and Protection Within Research, Development, Test, and Evaluation (RDT&E)

DoD Instruction (DoDI) 5200.39

DoD 17-Nov-17

IRES Risk Management Program Plan TO 8002, CDRL

C021, PL-IRES-

12-0024-C

IRES 22-Jul-22

MDIOC Facility Environmental Program Plan C037-18F8002- 2846-A

IRES 30-Mar-22

MDIOC Facility Mishap Prevention and Safety Plan C036-18F8002- 2845-A

IRES 30-Mar-22

IRES Program Management Plan TO 8002, CDRL C008

IRES 16-May-22

IRES Program Systems Engineering Management Plan

TO 8002, CDRL

C005

IRES 10-Aug-22

International Traffic in Arms Regulations 22 CFR 120-130 National Archives and Records Administration

(NARA)

N/A

10. STATEMENT OF OBJECTIVES AND OUTCOMES

10.1 Task Order Administration

This PWS section contains the scope, objectives, and outcomes to provide TO administration and management within the integrated framework of the IRES contract.

This PWS element includes both the TO-specific and IRES contract scope required to manage and administer TOs.

10.1.1 Task Order Management

This PWS element represents the Stakeholder Technical Integration Management and IRES Integration Management activities required to support the management of requirements of the overall TO, which includes all reporting, briefings, awards, modifications, SSIs, etc.

Objective #1: The contractor shall manage TO execution, resources, and information to conduct, deliver, and communicate TO requirements delivery.

Outcomes:

• Manage the cost, schedule, risk, and technical performance IAW the PWS.

• Provide status and insight on performance, including the metrics outlined in the Quality Assurance Surveillance Plan.

• Manage activities IAW the processes defined in the IRES Program Management Plan (TO 8002, CDRL C008).

• Ensure all requirements are identified, managed, validated, and verified IAW the contractor’s IRES Program Systems Engineering Management Plan (TO 8002, CDRL C005).

• Ensure a common Enterprise Architecture (EA) vision is implemented to support MDA to-be architectures, including the identification of gaps and Lessons Learned

(LL).

• Manage the TO workforce efficiently, mitigating workforce surge and drawdown impacts, analyzing workforce trends, and forecasting workforce needs and hiring to those requirements.

• Document, revise, improve, and train to the processes required by the TO.

• Report status (e.g., technical, cost, schedule). Status includes cost and schedule performance by Work Breakdown Structure (WBS) and IRES organization structure;

significant accomplishments; customer concerns or issues; TO risks and mitigation status; and performance against the IRES contract, Systems Engineering (SE) and Program Integration (SEPI), and TO SSIs.

• Identify, track, and share performance trends with the COTR, the ACOTR, and applicable Government stakeholders.

10.1.2 Objective: Enterprise Task Order Support

This PWS element scope represents the processes and toolsets of contract-wide enterprise support required for delivery of the IRES contract. This support provides the back office functions that enable the TO’s work and resources.

10.1.2.1 Enterprise Management

Objective #1: The contractor shall provide the resources and data to enable enterprise management of this TO for contracting, Human Resources (HR), business/finance, and Jacobs Enterprise Management System (JEMS)/Commercial Off-the-Shelf (COTS) Based Real-time Architecture (COBRA) integration.

Outcomes:

• Contracting office provides subcontracting and limitation of funds oversight, and processes TO modifications and awards IAW contractual requirements.

• Provide on-demand access to program data for MDA customers and stakeholders.

• Manage export control requirements to comply with DoD and MDA requirements, including International Traffic in Arms Regulations (ITAR) (i.e., 22 CFR 120-130, International Traffic in Arms Regulations) and technical assistance agreements processes, as required.

• Provide HR staff and functions to support needs for recruiting, hiring, and training a qualified workforce.

• Provide business office functions to enable the execution of payroll, timekeeping, accounts receivable/payable, and travel services.

• Administer small business and teammate agreements in order to achieve MDA and IRES small business goals.

• Manage the workforce in a way that will mitigate workforce surge and drawdown impacts, analyze workforce trends, and forecast workforce needs to ensure the required staffing is available to meet the requirements of the TO.

• Maintain a trained and qualified workforce that is able to perform the functions necessary to operate, support, and sustain MDIOC facilities and systems required under this TO.

• Develop and document processes that will enable the requirements of the TO to be met.

• Deliver quality and innovative work IAW the policy and direction provided in the IRES Management System set of processes and tools.

Objective #2: The contractor shall administer an IRES TO Portfolio delivery system that delivers financial, Earned Value (EV), and SSI performance across TOs. The contractor shall utilize TO dashboards and automated workflows in order to manage the portfolio.

Outcome:

• Utilize an IRES Information Management System (IIMS) portal to host and communicate TO EV/performance data/metrics and trends, and continuously evaluate and improve performance through the use of objective performance measures.

Objective #3: The contractor shall provide information security, physical security, export control, and cybersecurity training and processes IAW federal, DoD, and agency requirements to safeguard the conduct of the MDA mission through the IRES contract.

Outcomes:

• Protect MDA-identified Critical Program Information (CPI) and Critical Technology

(CT) to the standards required in DoD Instruction (DoDI) 5200.39, Critical Program Information (CPI) Identification and Protection Within Research, Development, Test, and Evaluation (RDT&E).

• Protect Controlled Unclassified Information (CUI) from unauthorized access, disclosure, incident, or compromise.

• Maintain system authorization for contractor-managed systems IAW DoDI 8510.01, Risk Management Framework.

• Integrate cybersecurity requirements and considerations into SE, design, and risk management processes.

• Operate contractor-managed systems IAW cybersecurity requirements.

• Provide security administration IAW applicable DoD, MDA, and local security directives, policies, procedures, and instructions for physical security and for the safeguarding of Ballistic Missile Defense System (BMDS)-controlled and classified information, including proper document marking, classification, storage, accountability, transmittal, and destruction.

• Manage and report the status of personnel requiring privileged access and the required DoD-approved 8570 certifications for the operating system(s) and/or security-related tools/devices they support or operate.

10.1.2.2 Performance Management

Objective #1: The contractor shall perform program control to provide an EV Management (EVM) System (EVMS); associated Control Account (CA) Management and Scheduling common tools, training, standards, and resources; and contract-wide Portfolio and Project Management common tools, training, standards, and resources.

Outcomes:

• Develop and manage an EVMS that provides required Integrated Program

Management Report (IPMR) formats and IBR/BR artifacts.

• Perform an IBR (or BR) within 90 days or as otherwise specified in the TO.

• Support and conduct an IBR at least annually or as needed for major modifications or awards.

• Perform financial management activities in a way that ensures EVM reporting accurately reflects the current state of financial performance and status.

• Structure the TO Integrated Master Schedule (IMS) for integration into the contractor’s IRES Integrated Schedule (IIS).

• Manage Portfolio/Project practices in a way that enables technical consistency and cost effectiveness while providing an adaptable framework for planning, managing, and completing projects for a broad range of tasks and missions.

Milestone: IBR

• CDRL C001: Integrated Program Management Report

• CDRL C002: Task Order Status Report Objective #2: The contractor shall perform Mission Assurance (MA), Configuration Management (CM), risk management, and Quality Assurance (QA) and Safety that promote and enforce safe and sustainable work practices to prevent personnel injury, damage to property, or harm to the environment.

Outcomes:

• Manage risks IAW the IRES Risk and Opportunity Management Plan (TO 8002, CDRL C021).

• Manage the quality of TO activities IAW the MDIOC Facility Quality Assurance Plan

(TO 8002, CDRL C043).

• Manage asset configurations IAW the MDIOC Facility Configuration Management Plan (TO 8002, CDRL C022).

• Perform activities IAW the MDIOC Facility Mishap Prevention and Safety Plan (TO 8002, CDRL C036) to prevent personnel injury and property damage.

• Perform activities IAW the MDIOC Facility Environmental Program Plan (TO 8002, CDRL C037) to prevent harm to the environment and maximize sustainable practices.

Objective #3: The contractor shall produce and deliver program data to ensure the products and services provided under this TO utilize established integrated processes and practices that are standardized across the IRES contract.

Outcomes:

• Integrate systems integration requirements, capability gaps, and a common architecture vision across the enterprise.

• Manage critical assets, including conflict forecasting and de-confliction, across the enterprise.

• Track and deliver CDRLs on time and with accurate information.

• Solicit and track customer satisfaction with the services and products delivered.

• Collect and share LL, best practices, and accomplishments with the COTR, the ACOTR, other Government stakeholders, and the IRES workforce.

• Provide systems integration and a common MDIOC system vision and oversight that are integrated enterprise-wide IAW the IRES Program Management Plan (TO 8002, CDRL C008).

• Provide AS9100-compliant core IRES processes and tailored processes.

Objective #4: The contractor shall submit compliant TO CDRLs and reports and monitor status of all TOs’ CDRL delivery performance IAW CDRL and milestone requirements. The contractor shall document approved processes as part of an IRES-wide management system in compliance with the IRES Program Management Plan (TO

8002, CDRL C008).

Outcomes:

• Track upcoming CDRL deliveries for all TOs, the requirements for technical editing support, and the schedule to meet on-time deliveries in support of IRES SSI #4.

• Coordinate technical editing, process engineering, stakeholder review, and posting of approved MDA and IRES process documents in the IRES Process Asset Library

(PAL).

• Provide contractual deliverables within the agreed-to schedule, in the correct formats and to a high level of quality. Post all deliverables to ECaRT and/or the IRES PAL.

10.1.2.3 Functional Organizational Support

Note: This area is for functional organization support. Not all TOs will require this support.

Objective #1: The contractor shall provide a functional management oversight structure to lead, manage, and assign resources within their organization.

Outcomes:

• Perform leadership, management, and administrative functions. Ensure personnel are trained and equipped to accomplish objectives.

• Functional Director leads and manages the department to meet requirements.

• Functional Director delivers products and services—including the correct people, processes, and tools—to meet mission requirements.

• Functional Director tactically allocates and strategically forecasts resources to ensure the sustainment, renewal, and growth of the technical expertise within the department that meets current and future requirements.

• Functional Department provides training, certifications, and career growth of employees.

• Functional Director mentors and oversees the execution of event engineering; asset operations and sustainment; systems integration; and analysis to ensure technical success.

Objective #2: The contractor shall provide functional administrative and management support to communicate and deliver enterprise integration.

Outcomes:

• Develop and manage coordination, collaboration, communication, and integration activities and processes between IRES senior managers and Government leaders to support and ensure accomplishment of objectives.

• Develop, standardize, and deploy thorough processes for event engineering; asset operations and sustainment; systems integration; and analysis.

• Coordinate, integrate, and deliver innovations to the TO mission areas, and IRES as a whole, to optimize efficiencies and mission effectiveness.

10.1.2.4 Procurement Services Support

Objective #1: The contractor shall provide accurate and timely procurement service functions that meet the needs of the TO.

• Maintain a procurement capability and system that support the procurement needs and provide status of procurements to stakeholders.

• Purchase supplies and equipment IAW the IRES Supply Chain Risk Management (SCRM) Plan (TO 8002, CDRL C044), including an authorized suppliers list for critical systems.

10.1.3 Task Order Award and Modification

Objective #1: The contractor shall provide the resources and data to provide timely and accurate proposals to Government requirements for proposal and other contract modification actions, including providing support to the Integrated Product Team (IPT) and proposal development for the follow-on TO requested by the Contracting Officer (CO) or the Contract Specialist.

10.2 Task/Project Planning and Exploration

The purpose of this task is to assist the Government in the initial planning and exploration of those efforts that may be tasked to execute under Sections 10.3, 10.4, and 10.5. Each activity shall be defined through an electronic message that can be issued by the COTR/ACOTR/CO Representative (COR).

Objective #1: The contractor shall perform planning; requirements gathering and identification; and analysis of alternatives for tasks that may be further defined and performed under Sections 10.3, 10.4, and 10.5.

Outcomes:

• 10.2.1.1 Schedule and lead Technical Interchange Meetings (TIMs) and perform site surveys with required stakeholders to identify the requirements.

• 10.2.1.2 Define, document, and provide draft requirements, Plans of Action and Milestones (POA&Ms), conceptual single line drawings, and Rough Order of Magnitude (ROM) estimates (e.g., parametric estimates, analogies).

• 10.2.1.3 Perform reviews of the existing infrastructure to validate the requirements.

• 10.2.1.4 Provide analysis of alternatives and Courses of Action (COAs).

10.3 Immediate Response Task

The purpose of the Immediate Response Task (IRT) is to execute facility-related services and tasks that require little-to-no design or planning (e.g., installing wall monitors, minor infrastructure installation/reconfiguration, minor assessments, minor designs, minor architecture installation/reconfiguration, Install-Move-Add-Change [IMAC] services). Each project shall be defined through a Technical Direction Letter (TDL) which can be issued by the COTR/ACOTR/COR. The TCR process shall be followed to document and communicate to the government a potential cost, schedule, or requirement change to the IRT.

Objective #1: The contractor shall perform all required planning/coordination, requirements definition, design, implementation, and closeout activities as defined in the

TDL.

• 10.3.1.1 Perform task oversight—including customer coordination, collaboration, and communications—and respond to Requests for Information (RFIs) and problem resolution. Establish and lead IPTs throughout the life cycle of the task as a forum to exchange ideas; discuss schedules; identify risks and risk mitigation strategies;

review requirements; and prepare for upcoming milestones. Provide meeting minutes and recorded action items to all IPT members within five business days of the IPT meeting.

• 10.3.1.2 Provide timely and accurate POA&M and reporting, if applicable. Include the plan to execute task milestones, mission impacts, space use impacts, any foreseeable risks that may affect the occupant of the space, and any foreseeable risks that may affect the contractor’s ability to execute within cost, schedule, and performance thresholds.

• 10.3.1.3 Complete closeout activities. Conduct a Joint Final Inspection (JFI) with MDA/MSF, end users, and other required stakeholders as identified in the TDL.

Prepare and submit the closeout documentation identified in the TDL (e.g., requirements analysis, as-built drawings, test reports, LL). Obtain final acceptance by signing and submitting the completed Requirements Traceability Matrix (RTM) to

MDA/MSF.

• 10.3.1.4 Execute an additional group of 10 IRTs through a single Priced Prospective Work Package (PPWP). This PPWP can be executed up to 10 times.

Objective #2: Ensure compliance with the published instructions and standards IAW the MDA/DM Directive Type Memorandum (Memo) (001-2022) dated 24 June 2022 that governs the MDIOC Engineering Review Board (ERB). Ensure completion of the SE gate reviews required in order to validate requests, align with facility standards, and integrate solutions across the MDIOC facility.

Outcomes:

• 10.3.1.5 Present to the ERB all projects impacting the MDIOC facility that meet the entry criteria defined in the MDIOC Engineering Review Board Charter.

• 10.3.1.6 Submit briefings and supporting documentation to the MDIOC ERB as outlined in the MDIOC Engineering Review Board Charter.

• 10.3.1.7 Reconcile any re-work actions and technical conflicts that come from the ERB and receive approval from the ERB before project performance begins.

10.4 Quick Response Task

The purpose of a Quick Response Task (QRT) is to execute tasks that entail revisions to architectural, infrastructure, and facility systems to support new and changing missions and requirements that would be considered moderate in complexity. Minimal-to-moderate design and implementation planning are required for full life cycle efforts (e.g., wall installation/modification, door relocation/installation, cable conveyance extensions, electrical power relocation/installation, carpet/tile installation, mechanical system relocation/installation, furniture procurement/installation, system controls installation). A QRT will also allow for complete design efforts from Systems Requirements Review (SSR) through Detailed Design Review (DDR) required for design-only efforts (e.g., the development and delivery of a Detailed Design Package [DDP] that may be implemented within the MDIOC). Each QRT shall be defined through a Mission Support Task (MST) that will be issued by the CO. It is expected that most MSTs between Implementation Readiness Review (IRR) and JFI (i.e., the Implementation phase) will be completed within a 2–4-month period. Any changes to these expectations will be identified in the MST. Any required tailoring of the outcomes and Attachment 1 of the PWS will occur in the MST. An EVM work package shall be established for each MST, as defined in the DD Form 1423, Contract Data Requirements List (CDRL). The TCR process shall be followed to document and communicate to the Government a potential cost, schedule, or requirement change to the MST. A PPWP will be executed to meet surge requirements.

When the Government obtains a different contractor than IRES to perform work in the MDIOC, MDA/MSF will need coordination support (e.g., scheduling outages, following MDIOC procedures, submitting artifacts to the ERB) to help that project succeed.

The contractor shall provide support activities for projects that are being implemented under a separate Government contract. The support contractor shall support the Government but cannot take on active management of the Government’s implementation contractors, including approving/rejecting their work. While the support contractor shall keep the Government abreast of the work in this support function, the support contractor cannot represent the project in approval boards/meetings or direct the implementation contractors during the course of their work. The required tasks of the support contractor shall be outlined within the QRT.

PPWP: Execute an additional group of 10 QRTs through a single PPWP. This PPWP can be executed up to 10 times.

Objective #1:

10.4.1 The contractor shall perform all required planning/coordination, requirements definition, design, implementation, and closeout activities as defined in the MST.

Outcomes:

• 10.4.1.1 Attachment 1 to the PWS defines the detailed requirements associated with the outcomes. The MST description that is coordinated for each project will identify the milestones and provide any required tailoring of the outcomes.

• 10.4.1.2 Perform project management—including customer coordination, collaboration, and communications—and respond to RFIs and problem resolution.

Establish and lead IPTs throughout the life cycle of the task. Provide IPT read-ahead documents NLT two business day prior to IPT meetings. Provide meeting minutes to all IPT members within five business days of the IPT meeting.

• 10.4.1.3 Systems Requirement Review (SRR) phase—coordinate stakeholder schedules and conduct an SRR brief with all applicable stakeholders per the schedule milestones table as entry criteria are met. Provide meeting minutes, including captured actions items, within five business days after the SRR. Complete the SRR phase exit criteria listed in Attachment 1.

• 10.4.1.4 Preliminary Design Review (PDR) phase—develop a component-level architecture and preliminary design (i.e., 65 percent) solution. Perform a validation walkthrough of the work area with MDA/MSF and stakeholders prior to the PDR brief. Coordinate schedules and conduct a PDR with all applicable stakeholders per the schedule milestones table as entry criteria are met. Deliver the required PDR artifacts to MDA/MSF. Provide meeting minutes, including captured actions items, within five business days after the PDR. Complete the PDR phase exit criteria listed in Attachment 1.

• 10.4.1.5 DDR phase—develop a detailed design (i.e., 100 percent) solution that captures specific architectures (e.g., architectural, electrical, mechanical, security, IT) necessary to support project implementation. Perform a validation walkthrough of the work area with MDA/MSF and the stakeholder prior to the DDR. Coordinate schedules and conduct a DDR brief with all applicable stakeholders per the schedule milestones table as entry criteria are met. Provide meeting minutes, including captured actions items, within five business days after the DDR. Complete the DDR phase exit criteria listed in Attachment 1.

CDRL C003: Engineering Documentation, Detailed Design

• 10.4.1.6 Implementation phase—coordinate schedules and conduct an IRR brief with all applicable stakeholders per the schedule milestone table. Provide meeting minutes, including captured actions items, within five business days after the IRR.

Execute the approved IRR schedule. Complete the Implementation phase exit criteria listed in Attachment 1. Sign and submit a contractor-verified RTM to MDA/MSF NLT two business days prior to the JFI date for final acceptance.

• 10.4.1.7 Closeout phase—conduct a validation walkthrough of the work area with MDA/MSF. Conduct a JFI with MDA/MSF, the end user, and required external stakeholders (e.g., Fire Marshal, 50th Space Wing [50th SW] Civil Engineer Squadron [CES]) per the schedule milestones table as entry criteria are met. Provide meeting minutes, including captured actions items, within five business days after the JFI brief. Prepare and submit closeout documentation. Complete the Closeout phase exit criteria listed in Attachment 1.

CDRL C004: Engineering Documentation, Closeout

• 10.4.1.8 Submit a TCR to the COTR/ACOTR as soon as a schedule and/or performance impact becomes known but NLT one week before the negotiated schedule is impacted. When there is a cost impact, submit the TCR to the COTR/ACOTR and PCO within two weeks of when the cost impact became known.

Objective #2:

Ensure compliance with the published instructions and standards IAW the MDA/DM Directive Type Memo (001-2021) dated 6 July 2021 that governs the MDIOC ERB.

Ensure completion of the SE gate reviews required in order to validate requests, align with facility standards, and integrate solutions across the MDIOC facility.

• 10.4.2.1 Present to the ERB all projects impacting the MDIOC facility that meet the entry criteria defined in the MDIOC Engineering Review Board Charter.

• 10.4.2.2 Submit briefings and supporting documentation to the MDIOC ERB, as outlined in the MDIOC Engineering Review Board Charter.

• 10.4.2.3 Reconcile any re-work actions and technical conflicts that come from the ERB and receive approval from the ERB before project performance begins.

10.5 Discrete Projects

The purpose of this task is to perform requirements definition, preliminary design, detailed design, implementation, and closeout/transition activities for discrete projects.

All discrete projects will be negotiated individually. A separate Project Description will be defined and negotiated for each discrete project and will be contained in the SharePoint location identified in section 11.0. Any required tailoring of the outcomes and of Attachment 1 of the PWS will occur in the Project Description. The TCR process shall be followed to document and communicate to the Government a potential cost, schedule, or requirement change.

Objective #1:

10.5.1 The contractor shall perform all required planning/coordination, requirements definition, design, implementation, and closeout activities for each individual project as defined in the Project Description. Attachment 1 to the PWS defines the detailed requirements associated with the outcomes. The Project Description that is negotiated with each project will identify the milestones and provide any required tailoring of the outcomes.

Outcomes:

• Attachment 1 to the PWS defines the detailed requirements associated with the outcomes. The Project Description that is negotiated with each project will identify the milestones and provide any required tailoring of the outcomes.

• 10.5.1.1 Perform project management—including customer coordination, collaboration, and communications—and respond to RFIs and problem resolution.

Establish and lead IPTs throughout the life cycle of the task. Provide a slide deck for the IPT meetings no later than two business days prior to the IPT meeting. Provide meeting minutes, including captured action items, to all IPT members within five business days of the IPT meeting.

• 10.5.1.2 SRR phase—coordinate schedules and conduct an SRR brief with all applicable stakeholders per the schedule milestones table as entry criteria are met.

Provide meeting minutes to include captured actions items within five business days after the SRR. Complete the SRR phase exit criteria listed in Attachment 1.

• 10.5.1.3 PDR phase—develop a component-level architecture and preliminary design (i.e., 65 percent) solution. Perform a validation walkthrough of the work area with MDA/MSF and stakeholders prior to the PDR brief. Coordinate schedules and conduct a PDR with all applicable stakeholders per the schedule milestones table as entry criteria are met. Provide meeting minutes, including captured actions items, within five business days after the PDR. Complete the PDR phase exit criteria listed in Attachment 1.

• 10.5.1.4 DDR phase—develop a detailed design (i.e., 100 percent) solution that captures specific architectures (e.g., architectural, electrical, mechanical, security, IT) necessary to support project implementation. Perform a validation walkthrough of the work area with MDA/MSF and the stakeholder prior to the DDR. Coordinate schedules and conduct a DDR brief with all applicable stakeholders per the schedule milestones table as entry criteria are met. Provide meeting minutes, including captured actions items, within five business days after the DDR. Complete the DDR phase exit criteria listed in Attachment 1.

CDRL C003: Engineering Documentation, Detailed Design

• 10.5.1.5 Implementation phase—coordinate schedules and conduct an IRR brief with all applicable stakeholders per the schedule milestones table as entry criteria are met. Provide meeting minutes, including captured actions items, within five business days after the IRR. Execute the approved IRR schedule. Complete the Implementation phase exit criteria listed in Attachment 1. Sign and submit the implementation completion checklist to MDA/MSF for final acceptance.

• 10.5.1.6 Closeout phase—conduct a validation walkthrough of the work area with MDA/MSF. Conduct a JFI brief with MDA/MSF, the end user, and required external stakeholders (e.g., Fire Marshal, 50th SW CES) per the schedule milestones table as entry criteria are met. Provide meeting minutes, including captured actions items, within five business days after the JFI. Prepare and submit closeout documentation.

Complete the Closeout phase exit criteria listed in Attachment 1.

CDRL C004: Engineering Documentation, Closeout

• 10.5.1.7 Submit a TCR to the COTR/ACOTR and PCO as soon as a schedule and/or performance impact becomes known but NLT one week before the negotiated schedule is impacted. When there is a cost impact, submit the TCR to the COTR/ACOTR and PCO within two weeks of when the cost impact became known.

Objective #2:

Ensure compliance with the published instructions and standards IAW the MDA/DM Directive Type Memo (001-2022) dated 24 June 2022 that governs the MDIOC ERB.

Ensure completion of the SE gate reviews required in order to validate requests, align with facility standards, and integrate solutions across the MDIOC facility

• 10.5.1.8 Present to the ERB all projects impacting the MDIOC facility that meet the entry criteria defined in the MDIOC Engineering Review Board Charter.

• 10.5.1.9 Submit briefings and supporting documentation to the MDIOC ERB as outlined in the MDIOC Engineering Review Board Charter.

• 10.5.1.10 Reconcile any re-work actions and technical conflicts that come from the ERB and receive approval from the ERB before project performance begins.

11. DISCRETE PROJECT LIST

The following discrete projects have been negotiated and put on contract. The requirements for each discrete project are located in the project description subfolder in the 23F8600 Contracts Award Documents folder, located on SharePoint (https://mko.mda.mil/4cd2213c). The contractor shall follow the project description and the above applicable PWS paragraphs.

1-1

ATTACHMENT 1

1-2

Outcomes 10.4.1.1 and 10.5.1.1: Integrated Product Team Requirements IPTs include Government stakeholders, contractor personnel, and non-MDA stakeholders. With MDA/MSF concurrence, the contractor establishes routine schedules for IPTs to meet in order to complete the requirements of the effort. IPTs are utilized as a forum to exchange ideas; discuss schedules; present RS Means estimates; identify risks and risk mitigation strategies; review requirements; prepare for upcoming milestones; and provide any other information pertinent to the task’s position on its life cycle.

Outcomes 10.4.1.3, 10.4.2.2, and 10.5.1.2: System Requirement Review Requirements During the SRR phase, the contractor conducts the SRR brief to all stakeholders in order to review requirements, planning processes, and major risks and constraints, and evaluate the preparedness and readiness to enter the Procurement, Planning, and Design phase. A validation walkthrough of the work area with MDA/MSF is considered part of the SRR brief. The SRR milestone includes the following:

1. Requirement Overview

2. Risk Assessments and Mitigation Strategies

3. Milestones

4. Conceptual Diagram

5. RTM (Reference Note 2 below) System Requirements Review Phase Entry Criterion The following criterion is met prior to entering the SRR milestone:

1. The SRR brief is delivered and conducted per the scheduled milestone;

stakeholders are coordinated in advance to ensure maximum participation.

Systems Requirements Review Phase Exit Criteria The following criteria are met prior to exiting the SRR milestone:

2. Meeting minutes are provided to and coordinated with MDA/MSF.

3. An action item list is provided to and coordinated with MDA/MSF. Each action identifies an Office of Primary Responsibility (OPR) and an Estimated Completion Date (ECD).

4. All artifacts have been accepted by MDA/MSF and notification has been provided during the SRR brief (i.e., captured in meeting minutes) and/or via email by the

COTR/ACOTR.

Outcomes 10.4.1.4 and 10.5.1.3: Preliminary Design Drawings Specifications are documented IAW the Whole Building Design Guide (WBDG) and the Unified Facilities Guide Specifications (UFGS), as follows:

1. Columns are designated with alpha-numeric gridlines for referencing purposes

(current practice).

1-3

2. Drawings are scalable to standard American National Standards Institute (ANSI) sheet sizes. Individual sheets will contain a scale (current practice).

3. The title block is supplemented with or contains numbers that are unique to the project.

4. The cover sheet includes the following:

a. TO number

b. Task number

c. Project title

d. Submittal type (e.g., preliminary design, detailed design)

e. Drawing Table of Contents (TOC)

5. The border includes an alpha-numeric drawing coordinate system (current practice).

6. Existing drafting standards are followed, including, but not limited to, the following:

a. Levels

b. Reference schemes

c. Colors

d. Line weights

7. For drawing areas, typical quad sheets are used to communicate change and are supplemented with standard sector drawings, as required, for scalability and readability purposes.

8. Designs comply with current codes, the UFGS, the Unified Facility Criteria (UFC), and the MDIOC UFGS (MUFGS). Details are included and dimensioned or scaled as required.

9. Drawing package are arranged in the following order:

a. Civil—"C" drawings

b. Architectural—"A" drawings

c. Structural—"S" drawings

d. Mechanical—"M" drawings

e. Plumbing—"P" drawings

f. Electrical—"E" drawings

g. Each section is in the following order (when required):

i. Demolition

ii. New

iii. Details/Sections

iv. Schedules

1-4

10. Drawings are 65-percent complete and include those addressing the Implementation phase.

11. Redlined specifications are provided to allow reviewers…