23F3100_PWS.pdf

PERFORMANCE WORK STATEMENT

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

Contract Number: HQ079617D0001

Task Order Title: Ground-Based Midcourse Defense (GMD) Operations and Training Support

Task Order Number: HQ085723F3100

Period of Performance: 5 March–8 August 2025

Dated: 6 January 2023

Performance Work Statement Revision History

Version Date Mod # Change Description Basic TBD Award N/A

TABLE OF CONTENTS

1. PURPOSE

2. BACKGROUND

3. SCOPE

4. SERVICE SUMMARY ITEMS

5. CONTRACT DELIVERABLE REQUIREMENTS LIST

5.1 CDRL Identification

5.2 CDRL Tailoring

6. MILESTONES

7. GOVERNMENT PROPERTY/GOVERNMENT-FURNISHED

PROPERTY/GOVERNMENT-FURNISHED INFORMATION/CONTRACTOR-

ACQUIRED PROPERTY

8. SPECIAL REQUIREMENTS

8.1 Technical Change Request Task Order-Specific Language

9. APPLICABLE DIRECTIVES/REGULATIONS

10. PERFORMANCE WORK STATEMENT

10.1 10.1 Task Order Administration

10.1.1 10.1.1 Task Order Management

10.1.2 Objective: Enterprise Task Order Support

10.1.3 Task Order Award and Modification

10.2 GMD Operations Sustainment

10.2.1 Activity Assistance

10.2.2 Capability Sustainment

10.2.3 Customer Support Services

10.3 GMD Training and Exercise Sustainment

10.3.1 Activity Assistance

10.3.2 Capability Sustainment

10.3.3 Customer Support Services

10.4 General GMD Support and Sustainment

10.4.1 Activity Assistance

10.4.2 Capability Sustainment

10.4.3 Customer Support Services

10.5 Events and Engineering Projects

10.5.1 Objective— IRT (Minor) Projects

LIST OF TABLES

Table 4–1 Service Summary Items and Weights Applicable to this Task Order Table 10–1 Performance Standard Summary

1. PURPOSE

The purpose of the Ground-Based Midcourse Defense (GMD) Operations and Training Task Order (TO) is to provide the resources (i.e., personnel, information systems, software applications, infrastructure, and communication networks) to support operations, sustainment, and development of fielded GMD sites, contributing to the MDA’s mission to develop and deploy an integrated, global Missile Defense System.

2. BACKGROUND

GMD is an MDA organization with several operational, training, and development areas (approximately 32,000 square feet total) within the MDIOC, Building 720 at Schriever Space Force Base (SFB) (SSFB). As such, the MDA provides basic tenant support services—including Missile Defense System baseline integrity and overall Mission Assurance (MA)—within the MDIOC facility. This TO provides for GMD mission-unique support requirements and services above MDA standard IT services. This TO is funded from an Operations and Maintenance (O&M) appropriation; however, special one-time requirements may be funded from Research, Development, Test, and Evaluation (RDT&E) sources.

3. SCOPE

This TO provides the contract vehicle to obtain all necessary labor, services, equipment, and materials required to operate, sustain, and upgrade MDA equipment and infrastructure systems supporting the GMD program. IRES services determined to be outside of the baseline IT service coverage of the IT Service Delivery (ITSD) TO or above standard MDA IT services will be executed through this TO. This TO also provides a mechanism to execute facility modification requests, engineering projects, and major event support.

TO requirements are typically limited to GMD activities at the MDIOC; however, similar requirements at other GMD fielded sites may be executed under this TO—including, but not limited to, Cheyenne Mountain Space Force Station (SFS) (CMSFS); Peterson SFB (PSFB); Fort Greely, AK (FGA); Fort Drum, NY (FDN); and Vandenberg SFB, CA (VSFB)—on an as-required basis.

4. SERVICE SUMMARY ITEMS

Exhibit 1 provides the Service Summary Items (SSIs) that are applicable to this TO.

Table 4–1 Service Summary Items and Weights Applicable to this Task Order SSI # Title Description

SSI 1 Integration Refer to Attachment J-06, IRES Performance Evaluation and Incentive Plan (PEIP).

SSI 2 Small Business Utilization Refer to Attachment J-06, IRES Performance Evaluation and Incentive Plan (PEIP).

SSI 3 Customer Satisfaction Refer to Attachment J-06, IRES Performance Evaluation and Incentive Plan (PEIP).

SSI 4 CDRL, Proposal, and Milestone Timeliness

Refer to Attachment J-06, IRES Performance Evaluation and Incentive Plan (PEIP).

SSI

# Title Description

Performance Threshold—

Unacceptable

Performance Threshold—

Poor Performance

Performance Threshold—

Meeting Needs

Performance Threshold— Exceptional

Performance Threshold—

Perfect Weight Assessment

Method

SSI

Critical GMD Operations Sustainment Incident Requests

Mission-critical incident requests during core or non-core hours are accomplished IAW the times identified in paragraph 10.2.3.2.

4 or more mission-critical incident requests did not meet established times for incident response and completion.

3 mission-critical incident requests did not meet established times for incident response and completion.

2 mission-critical incident requests did not meet established times for incident response and completion.

1 mission-critical incident request did not meet established times for incident response and completion.

No mission-critical incident requests are identified or 100% of mission-critical incident requests meet established times for incident response and completion.

35% COR: Review of TO 3100, CDRL C002, 21F3100: Task Order Status Report

Quality Performance Index (QPI) score = 0

QPI score =

QPI score =

QPI score =

QPI score =

35 QPI

SSI

Events and Engineering Projects

Events and engineering projects are accomplished IAW the procedures and times identified under paragraph 10.5.

4 or more events and/or engineering projects are not completed by the negotiated completion date.

3 events and/or engineering projects are not completed by the negotiated completion date.

2 events and/or engineering projects are not completed by the negotiated completion date.

1 event and/or engineering project are not completed by the negotiated completion date.

All events and engineering projects are completed by the negotiated completion date.

25% 100% review of RTM items prior to event or project completion.

QPI score = 0 QPI score = 15.25

QPI score = 18.5

QPI score =

QPI score =

25 QPI

SSI

Management Measurement Ratings

Expectations for management review are met based on the QASP monthly performance report.

6-month review results in an average of 0–2 across all performance metrics.

6-month review results in an average of 2–3 across all performance metrics.

6-month review results in an average of 3–4 across all performance metrics.

6-month review results in an average of 4–4.5 across all performance metrics.

6-month review results in an average of 4.5 and above across all performance metrics.

15% 100% review of requirements under QASP guidelines for management/ business relations environment. QPI Score = 0 QPI Score = 9 QPI Score =

QPI Score =

QPI Score =

15 QPI

5. CONTRACT DELIVERABLE REQUIREMENTS LIST

The point of delivery for all Contract Deliverable 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). Refer to Exhibit C for specific CDRL delivery instructions.

5.1 CDRL Identification

PWS

Task(s)

CDRL

Number

Data Item Description

(DID)

Title CDRL Description

10.1 C001 DI-MGMT-

81861A/T

23F3100:

Integrated Program Management Report (IMPR)

[MMM-YYYY],

DFARS EVMS

NA

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. (Note: WBS structure and Format 1 should identify PWS paragraph 10.x breakdown and CLIN summaries; Format 5 analysis only required at TO [i.e., Fiscal Year (FY) funding] level; Format 6 [i.e., schedule] not required.)

10.1 C002 DI-MISC-

80508B/T

23F3100: Task Order Status Report (TOSR), [month ending]

Provides significant accomplishments, issues, concerns, LL, and risks associated with the TO. The report shall include:

• A summary of all completed and open procurement actions with associated request and delivery dates

• A summary of all maintenance actions scheduled during the period and completion status

• A summary of all incident requests, associated response times, and root cause analysis

• A summary of all work requests and associated response times

• A summary of all active projects, including project identifier, work description, submission date, need date, planned/actual turnover date, CRQ number(s), and estimated/actual cost of the project

• Project closeout summaries that contain the final resource-loaded schedule and an element of cost summary for each project

10.2.2.1 10.3.2.1 10.4.2.1

C003 DI-MISC-

80508B/T

23F3100:

Maintenance and Spare Report

Identifies all recurring maintenance/sustainment tasks planned during the current Period of Performance (POP). The report should identify specific actions by room, system, or rack, and include task description and frequency. The report should also identify recommended spare

PWS

Task(s)

CDRL

Number

Data Item Description

(DID)

Title CDRL Description equipment inventory levels based on mission criticality, frequency of use, or long-lead time/obsolescence criteria. Includes inventory of all spares and the identification of licensing, maintenance agreements, and renewal documentation of hardware and software assets.

10.2.2.2 10.3.2.2 10.4.2.2

C004 DI-MISC-

80508B/T

23F3100:

Technology Refresh Plan

Provides a summary report of all equipment items maintained by the contractor; the report shall include, at a minimum: make, model number, quantity, age of item(s), recommended replacement date, replacement criticality, and an estimated cost for replacement item(s).

10.2.2.4 10.3.2.4 10.4.2.4

C005 DI-MISC-

80508B/T

23F3100: Facility Configuration Report

Provides a report on the “as built” configuration of all facilities the contractor maintains, including requirements, functional layouts, Automated Data Processing Equipment (ADPE) configuration, and network connectivity. The report should include an appendix with a summary of all projects completed or in progress during the previous POP. The report should also include an appendix of all drawings and other configuration control documents maintained under the TO.

10.2.2.4 10.3.2.4 10.4.2.4 10.5.1.7 10.5.2.7

C006 DI-MISC-

80508B/T

23F3100, [Event or Project Title]:

Engineering Documentation

Provides detailed project and engineering documentation, including the following components, as applicable: project request and change orders, RTM, version description documents, slide packages, DoDAF artifacts, rack elevation drawings, facility construction drawings, and floor plans.

5.2 CDRL Tailoring

The Department of Defense (DD) Form 1423, Contract Data Requirements List, associated with each CDRL is attached in Exhibit C:

23F3100-Exhibit-C_(B ase).pdf

6. MILESTONES

PWS Task Activity Date/Days After Contract (DAC)

10.1.2.2 Baseline Review 120 DAC

PWS Task Activity Date/Days After Contract (DAC) TO Status Review Monthly

Note: DAC = days after TO POP start date.

7. GOVERNMENT PROPERTY/GOVERNMENT-FURNISHED

PROPERTY/GOVERNMENT-FURNISHED INFORMATION/CONTRACTOR-

ACQUIRED PROPERTY

7.1 In addition to the Government Property (GP) associated with paragraph 6.0 of the Integrated Research & Development for Enterprise Solutions (IRES) Contract Statement of Objectives (SOO), the following GP is applicable to this TO:

• None

7.2 In addition to the Government-Furnished Property (GFP) identified on 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 TO 22F8900, Government Property Management.

8. SPECIAL REQUIREMENTS

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

• The TO shall be executed IAW MDA security classification guidance with day-to-day activities conducted in areas designated at the SECRET level.

• The contractor shall have emergency response capability to the Missile Defense Element (MDE) Sensitive Compartmented Information Facility (SCIF) at Top Secret (TS) level. Note: Most TO requirements in the MDE SCIF can be conducted at the SECRET level with an authorized escort (TS/Sensitive Compartmented Information [SCI] required).

• Certain GMD areas are designated System Security Level A (SSL-A) for physical protection; access to these areas will be granted to a limited number of personnel with a permanent SECRET security clearance.

• The contractor must follow current risk management framework requirements IAW DoD Instruction (DoDI) 8510.01, Risk Management Framework (RMF) for DoD Information Technology.

8.1 Technical Change Request Task Order-Specific Language

The TO will follow 18F8002 Technical Direction Letter (TDL) 012 for directions to comply with the submission of Technical Change Requests (CRQs) (TCRs):

• Project/events over 480 hours that incur cost or schedule change

• Immediate Response Task (IRT) projects/events with a cost or duration variance of 25 percent or greater. The Government or the contractor reserves the right to submit a TCR for select requested IRT projects The Procurement Contracting Officer (PCO) or the Contracting Officer’s

Technical Representative (COTR) has the ability to waive the submission of a TCR for IRT projects/events on selected projects

9. APPLICABLE DIRECTIVES/REGULATIONS

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:

Title Originator Date None

10. PERFORMANCE WORK STATEMENT

The contractor shall perform the following requirements under this TO. Exhibit 2 provides the performance standards (i.e., initial response time, estimated time to repair, time to provide a situation report, and time to complete actions).

Table 10–1 Performance Standard Summary

Objective Area Applicable Paragraph

Initial Response

Estimated Time to Repair

Situation Report

Action Completed

10.2 GMD Operations Sustainment

Recurring maintenance 10.2 As scheduled N/A N/A As scheduled Incident request 10.2.3.2

• Mission critical, core hours 30 minutes 1 hour** 6 hours** 24 hours**

• Mission critical, non-core hours 2 hours 4 hours** 6 hours** 24 hours**

• Non-critical 8 hours 24 hours** N/A 72 hours** IMAC services 10.2.3.3

• Urgent N/A N/A N/A 3 days*

• Routine N/A N/A N/A 14 days* Documentation/drawing updates 10.2.2.4 Redline N/A N/A 30 days

10.3 GMD Training and Exercise Sustainment

Recurring maintenance 10.3 As scheduled N/A N/A As scheduled

Objective Area Applicable Paragraph

Initial Response

Estimated Time to Repair

Situation Report

Action Completed

Incident request 10.3.3.2

• Mission critical, core hours 1 hour 2 hours** Daily** 72 hours**

• Mission critical, non-core hours 2 hours 4 hours** Daily** 72 hours**

• Non-critical 24 hours 48 hours** N/A 14 days** IMAC services 10.3.3.3

• Urgent N/A N/A N/A 7 days*

• Routine N/A N/A N/A 30 days* Documentation/drawing updates 10.3.2.4 Redline N/A N/A 60 days

10.4 General GMD Support and Sustainment

Recurring maintenance 10.4 As scheduled N/A N/A As scheduled Incident request 10.4.3.2

• Non-critical 48 hours 72 hours** N/A 14 days** IMAC services 10.4.3.3

• Urgent N/A N/A N/A 7 days*

• Routine N/A N/A N/A 30 days* Documentation/drawing updates 10.4.2.4 Redline N/A N/A 90 days

10.5 Events and Engineering Projects

(IRT) Minor project 10.5.1 N/A N/A N/A 90 days Documentation/drawing updates 10.5.1.7

10.5.2.7 Redline N/A N/A 60 days

* Number of days to complete action excludes procurement delivery time.

** Response times to complete action excludes A/V support by associate contractor.

10.1 10.1 Task Order Administration This Performance Work Statement (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 TO specific and IRES contract scope required to manage and administer TOs.

10.1.1 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 (QASP).

• 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 Master Plan (SEMP) (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 Assistant COTR (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)/Cobra integration.

Outcomes:

• The 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 22 Code of Federal Regulations (CFR) 120-130, International Traffic in Arms Regulations, and technical assistance agreement 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 Information Management System (IIMS) set of processes and tools.

Objective #2: The contractor administers 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.

Outcomes:

• Utilize an 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 to the standards required in DoD Directive (DoDD) 5200.39, Critical Program Information (CPI) Identification and Protection Within Research, Development, Test, and Evaluation (RDT&E).

• Protect 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 Missile Defense System-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 Integrated Baseline Review (BR) (IBR)/BR artifacts.

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

• 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 MA, Configuration Management (CM), risk management, 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 Cybersecurity Risk Management Plan (TO 8002, CDRL

C016).

• 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 C042).

• 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, as well as 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, requirements for technical editing support, and a 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.

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

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

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

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

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

• The 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, 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: The contractor shall provide accurate and timely procurement service functions that meet the needs of the TO.

Outcomes:

• Maintain a procurement capability and system that supports the procurement needs and provides 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: 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 GMD Operations Sustainment

GMD operations sustainment encompasses planning, maintenance, and execution of all operations and sustainment requirements as they affect GMD operational systems and work areas. Principal work areas include GMD operations in Sector 1207, GMD Fire Control (GFC) in Server Room 2209, associated areas in Quad 1100 (e.g., GMD Element Coordination Information Center [GECIC], BMDS Network Operations and Security Center [BNOSC]), and the classified storage space in Room 114.

10.2.1 Activity Assistance

The contractor shall facilitate the identification and scheduling of facility maintenance, inspection, project-related visits, and inventory requirements that are performed in these areas under other IRES TOs. In addition, the contractor shall monitor and report other MDA/IRES TO activities that could potentially have an operational impact on GMD areas.

• 10.2.1.1 Maintain awareness of GMD activities and events through attendance at GMD staff meetings, participation in project/event meetings, and direct interface with GMD staff.

• 10.2.1.2 Coordinate, facilitate, and provide escort for personnel not permanently authorized access to GMD-controlled areas for facility maintenance, inspection, project-related visits, and inventory activities. This includes the 1207 SCIF area.

• 10.2.1.3 Identify and mitigate/de-conflict MDA and IRES activities that could potentially have an operational impact on GMD equipment or mission space.

• 10.2.1.4 Coordinate MDIOC-level freeze waivers, as necessary, to minimize and/or eliminate any risk to GMD activities and events.

10.2.2 Capability Sustainment

The contractor shall provide services necessary for the sustainment of MDA equipment and infrastructure supporting the GMD program. Sustainment activities include proactive/corrective maintenance, hardware/software refresh planning, Information Assurance (IA), network administration services, and CM. Supported equipment includes networked and non-networked desktop/laptop computers, data communications systems, voice communications systems, large display monitors connected to computers only, and common area signage.

The contractor shall maintain the MDA enterprise technical standards for teleconferencing, large computer system displays (i.e., monitors), the Internet Protocol (IP) TV (IPTV)/EZ-TV distribution system, and the Public Address (PA) system. This does not include display devices that are connected to Video Teleconference (VTC) systems, A/V distribution systems, and video walls. All other A/V product standards will be defined by the associate contractor. IRES will coordinate with the associate contractor to ensure equipment standards, VTC, and A/V distribution systems are compatible and integrate with the enterprise network, with the Government resolving any discrepancies.

The contractor shall act as liaison between GMD and the associate contractor to facilitate A/V O&M break/fix activities, as needed. The contractor shall meet designated response time requirements but shall not be held accountable for completion of actions by the associate contractor.

• 10.2.2.1 Maintain and refresh hardware, software, and current capabilities IAW industry best maintenance practices, ensuring an appropriate mix between inspection, proactive, and corrective maintenance, repair, and replacement to maintain availability of systems, equipment, and networks. Document and execute maintenance plans, schedules, and performance expectations. Utilize system performance and maintenance trending analysis to manage the maintenance program. Develop sparing methodology based on mission criticality, frequency of use, acquisition lead-time, and vendor support criteria. Monitor approved spare levels and recommend procurement action to replenish stock.

• 10.2.2.2 Develop criteria for technology refresh of hardware, software, and current capabilities IAW industry best practices to ensure availability. Leverage MDA IT support policy to minimize GMD investments for IT hardware and software above MDA standards. Manage and provide the Government with real-time access to a database that conforms to Defense Property Accountability System (DPAS) requirements identifying the location and acquisition details for all GMD-acquired assets. Implement an integrated approach to operate and manage all GMD hardware and software investments that provides for the continuous identification, selection, control, Life Cycle Management (LCM), and evaluation of the investments in a structured process, resulting in a systematic method to maximize investment return and allow predictable budgeting. Manage and maintain currency on all licensing and update services for third-party software, software drivers, and diagnostic software.

• 10.2.2.3 Maintain protection from intrusion and exploitation of Information systems as required by MDA and DoD standards. Manage applicable networks and network components, including supporting documentation, to ensure RMF accreditation is maintained. Provide network administration services, including cable plant management and network distribution in all Local Area Network (LAN) environment locations, as well as the distribution of precision timing and video cable circuits.

• 10.2.2.4 Maintain conformance to a CM/SE process to ensure standards are established to control and manage system capabilities in optimum condition. Track and maintain the currency of documentation for facility, equipment, cabling configuration, and operating procedures to perform the GMD mission. Develop baselined systems artifacts (e.g., Interface Control Documents [ICDs], network ICDs, schematic, functional system overlay, architectural drawings compliant with DoD Architecture Framework [DoDAF] v2.0) that clearly diagram and articulate the system or components performance, function, and physical attributes and functional relation between parts, subsystems, and systems. Manage and provide the

Government access to drawing repositories and other applicable configuration control documentation IAW Exhibit 2.

10.2.3 Customer Support Services

The contractor shall provide customer support services inclusive of ISD operations, touch-labor client services, conference room system support, Install-Move-Add-Change (IMAC) services, VIP support, major event activities, and engineering project services.

• 10.2.3.1 Provide Tier II ISD support during core business hours. Ensure knowledge base maintenance and development enabling first call resolution of ISD calls.

• 10.2.3.2 Provide an incident request process/system that allows effective identification, tracking, and resolution of all recurring maintenance findings, troubleshooting, and break/fix service restoration requests. Identify actions as urgent or routine based on actual/potential impact on mission system availability. Create the capability for all GMD users and service providers to submit, identify mission impact, and inquire as to the status of subject requests. Performance standards (i.e., initial response time, estimated time to repair, time to provide a situation report, and time to complete actions) are provided in Exhibit 2.

• 10.2.3.3 All requests for engineering or IMAC services requires GMD review and approval. Provide a work request process/system that allows GMD-appointed personnel to submit, assess, validate, vet, prioritize, approve, track, and evaluate subject work requests. The content of contractor response for each request shall include scope, need date, POC(s), solution, breakout of activities, schedule, cost, and materials. Implement a CRQ process for schedule changes. Create a categorical binning system for approval and vetting for projects, with respect to urgency and project size. Implement a streamlined/Agile process for work requests.

The performance standards (i.e., time to complete actions) for urgent/ routine IMAC requirements are provided in Exhibit 2.

10.3 GMD Training and Exercise Sustainment

GMD training and exercise sustainment encompasses planning, maintenance, and execution of all operations and sustainment requirements as they affect the GMD training and exercise systems and work areas. Principal work areas include the Joint GMD Training and Exercise Center (J-GTEC) and other sustainment training areas in Quad 3400, and training systems in Data Center Rooms 2201/2209.

10.3.1 Activity Assistance

The contractor shall facilitate the identification and scheduling of facility maintenance, inspection, project-related visits, and inventory requirements that are performed in these areas under other IRES TOs. In addition, the contractor shall monitor and report other MDA/IRES TO activities that could potentially have an operational impact on GMD areas.

• 10.3.1.1 Maintain awareness of GMD activities and events through attendance at GMD staff meetings, participation in project/event meetings, and direct interface with GMD staff.

• 10.3.1.2 Coordinate, facilitate, and provide access to personnel not permanently authorized access to GMD-controlled areas for facility maintenance, inspection, project-related visits, and inventory activities.

• 10.3.1.3 Identify and mitigate/de-conflict MDA and IRES activities that could potentially have an operational impact on GMD equipment or mission space.

• 10.3.1.4 Coordinate MDIOC-level freeze waivers, as necessary, to minimize and/or eliminate any risk to GMD activities and events.

10.3.2 Capability Sustainment

The contractor shall provide services necessary for the sustainment of MDA equipment and infrastructure supporting the GMD program. Sustainment activities include proactive/corrective maintenance, hardware/software refresh planning, IA, network administration services, and CM. Supported equipment includes networked and non-networked desktop/laptop computers, data communications systems, voice communications systems, large display monitors connected to computers only, and common area signage.

The contractor shall maintain the MDA enterprise technical standards for teleconferencing, large computer system displays (i.e., monitors), the IPTV/EZ-TV distribution system, and the PA system. This does not include display devices that are connected to VTC systems, A/V distribution systems, and video walls. All other A/V product standards will be defined by the associate contractor. IRES will coordinate with the associate contractor to ensure equipment standards, VTC, and A/V distribution systems are compatible and integrate with the enterprise network, with the Government resolving any discrepancies.

The contractor shall act as liaison between GMD and the associate contractor to facilitate A/V O&M break/fix activities, as needed. The contractor shall meet designated response time requirements but shall not be held accountable for completion of actions by the associate contractor.

• 10.3.2.1 Maintain hardware, software, and current capabilities IAW industry best maintenance practices, ensuring the proper mix between inspection, proactive, and corrective maintenance to maximize availability. Document and execute maintenance plans, schedules, and performance expectations. Utilize system performance and maintenance trending analysis to manage the maintenance program. Develop sparing methodology based on mission criticality, frequency of use, acquisition lead-time, and vendor support criteria. Monitor approved spare levels and recommend procurement action to replenish stock.

• 10.3.2.2 Develop criteria for technology refresh of hardware, software, and current capabilities IAW industry best practices to ensure availability. Leverage MDA IT support policy to minimize GMD investments for IT hardware and software above MDA standards. Manage and provide the Government with real-time access to a database that conforms to DPAS requirements identifying the location and acquisition details for all GMD-acquired assets. Implement an integrated approach to operate and manage all GMD hardware and software investments that provides for the continuous identification, selection, control, LCM, and evaluation of the investments in a structured process, resulting in a systematic method to maximize investment return and allow predictable budgeting. Manage and maintain currency on all licensing and update services for third-party software, software drivers, and diagnostic software.

• 10.3.2.3 Maintain protection from intrusion and exploitation of Information systems as required by MDA and DoD standards. Manage applicable networks and network components, including supporting documentation, to ensure RMF accreditation is maintained. Provide network administration services, including cable plant management and network distribution in all LAN environment locations, as well as the distribution of precision timing and video cable circuits.

• 10.3.2.4 Maintain conformance to a CM/SE process to ensure standards are established to control and manage system capabilities in optimum condition. Track and maintain the currency of documentation for facility, equipment, cabling configuration, and operating procedures to perform the GMD mission. Develop baselined systems artifacts (e.g., ICDs, network ICDs, schematic, functional system overlay, and architectural drawings compliant with DoDAF v2.0) that clearly diagram and articulate the system or components performance, function, and physical attributes and functional relation between parts, subsystems, and systems. Manage and provide the Government access to drawing repositories and other applicable configuration control documentation IAW Exhibit 2

10.3.3 Customer Support Services

The contractor shall provide customer support services inclusive of ISD operations, touch-labor client services, conference room system support, IMAC services, VIP support, major event activities, and engineering project services.

• 10.3.3.1 Provide Tier II ISD support during core business hours. Ensure knowledge base maintenance and development enabling first call resolution of ISD calls.

• 10.3.3.2 Provide an incident request process/system that allows effective identification, tracking, and resolution of all recurring maintenance findings, troubleshooting, and break/fix service restoration requests. Actions shall be identified as urgent or routine based on actual/potential impact on mission system availability. All GMD users and service providers should be able to submit, identify mission impact, and inquire as to the status of subject requests. Performance standards (i.e., initial response time, estimated time to repair, time to provide a situation report, and time to complete actions) are provided in Exhibit 2.

• 10.3.3.3 All requests for new work or involving IMAC services will require GMD review and approval. Provide a work request process/system that allows GMD-appointed personnel to submit, assess, validate, vet, prioritize, approve, track, and evaluate subject work requests. The content of contractor response for each request should include scope, need date, POC(s), solution, breakout of activities, schedule, cost, and materials. Implement a CRQ process for schedule changes. Create a categorical binning system for approval and vetting for projects, with respect to urgency and project size. Implement a streamlined/Agile process for work requests.

The performance standards (i.e., time to complete actions) for urgent/ routine IMAC requirements are provided in Exhibit 2.

10.4 General GMD Support and Sustainment

General GMD support and sustainment encompasses support for common areas, conference rooms, general administrative work areas, and implementation of GMD security, work approval, and other administrative policies. This task includes support to other GMD element requirements and areas not specifically identified under operations and training support tasks above, including the following:

• Information Systems Security Officer ISSO Room (Room 3404-B)

• Denver Execution Room (Room 3401-05)

• Mission Control Center (MCC)-A (Room 3404-02) and MCC-B (Room 3401-02)

• Engineering Support Center (ESC) (Room 3401-03)

• Test Mission Control Enclave (TMCE) Room (Room 3401-08)

• Range Interface Test and Evaluation (RITE) Room (Room 3401-09)

• MDA/GM Data Analysis and Review Team (GDART) (Room 3309)

• Room 3308

10.4.1 Activity Assistance

The contractor shall facilitate the identification and scheduling of facility maintenance, inspection, project-related visits, and inventory requirements that are performed in these areas under other IRES TOs. In addition, the contractor shall perform on-site facility technical services and security management functions for designated areas (currently, MDIOC Building 720, third floor areas) to ensure compliance with MDIOC, MDA, and DoD standards.

• 10.4.1.1 Maintain awareness of GMD activities and events through attendance at GMD staff meetings, participation in project/event meetings, and direct interface with GMD staff.

• 10.4.1.2 Coordinate, facilitate, and provide access to personnel not permanently authorized access to GMD-controlled areas for facility maintenance, inspection, project-related visits, and inventory activities.

• 10.4.1.3 Identify and mitigate/de-conflict MDA and IRES activities that could potentially have an operational impact on GMD equipment or mission space.

• 10.4.1.4 Coordinate MDIOC-level freeze waivers, as necessary, to minimize and/or eliminate any risk to GMD activities and events.

• 10.4.1.5 Perform duties as the Security Assistant as defined in the Standard Operating Procedure (SOP) of the subject area. Coordinate for the Security Manager with MDA Security personnel on all physical and information security issues and tasks. Develop and maintain SOP documentation IAW standard MDA procedures.

• 10.4.1.7 Manage access control to controlled areas.

• 10.4.1.8 Perform block captain activities IAW the latest Government directives.

• 10.4.1.9 Manage and process incoming and outgoing Visit Authorization Requests (VARs).

• 10.4.1.10 Maintain and manage open storage certification requirements. Provide guidance to occupants on security classification requirements. Receive, generate, and reproduce classified material up to the SECRET classification.

• 10.4.1.11 Perform conference and VTC room scheduling and publish the reservation results.

• 10.4.1.12 Report to the MDA ISD when classified and unclassified printers are not operational and facilitate paper and toner replacements.

• 10.4.1.13 Ensure the "Unclassified Sensitive/CUI/Proprietary Information" recycle bins are serviced through the MDA ISD.

10.4.2 Capability Sustainment

The contractor shall provide services necessary for the sustainment of MDA equipment and infrastructure supporting the GMD program. Sustainment activities include proactive/corrective maintenance, hardware/software refresh planning, IA, network administration services, and CM. Supported equipment includes networked and non-networked desktop/laptop computers, data communications systems, voice communications systems, large display monitors connected to computers only, and common area signage.

The contractor shall maintain the MDA enterprise technical standards for teleconferencing, large computer system displays (i.e., monitors), the IPTV/EZ-TV distribution system, and the PA system. This does not include display devices that are connected to VTC systems, A/V distribution systems, and video walls. All other A/V product standards will be defined by the associate contractor. IRES will coordinate with the associate contractor to ensure equipment standards, VTC, and A/V distribution systems are compatible and integrate with the enterprise network, with the Government resolving any discrepancies.

The contractor shall act as liaison between GMD and the associate contractor to facilitate A/V O&M break/fix activities, as needed. The contractor shall meet designated response time requirements but shall not be held accountable for completion of actions by the associate contractor.

• 10.4.2.1 Maintain hardware, software, and current capabilities IAW industry best maintenance practices, ensuring the proper mix between inspection, proactive, and corrective maintenance to maximize availability. Document and execute maintenance plans, schedules, and performance expectations. Utilize system performance and maintenance trending analysis to manage the maintenance program. Develop sparing methodology based on mission criticality, frequency of use, acquisition lead-time, and vendor support criteria. Monitor approved spare levels and recommend procurement action to replenish stock.

• 10.4.2.2 Develop criteria for technology refresh of hardware, software, and current capabilities IA industry best practices to ensure availability. Leverage MDA IT support policy to minimize GMD investments for IT hardware and software above MDA standards. Manage and provide the Government with real-time access to a database that conforms to DPAS requirements identifying the location and acquisition details for all GMD-acquired assets. Implement an integrated approach to operate and manage all GMD hardware and software investments that provides for the continuous identification, selection, control, LCM, and evaluation of the investments in a structured process, resulting in a systematic method to maximize investment return and allow predictable budgeting.