23F1500_PWS.pdf

PERFORMANCE WORK STATEMENT

Contract Number:

HQ0796-17-D-0001

Task Order Title:

Joint Functional Component Command for Integrated Missile Defense

(JFCC IMD) Engineering and Maintenance

Task Order Number:

HQ0857-23-F-1500

Period of Performance:

1 March 2023–8 August 2025

Task Order Type:

Cost Plus Incentive Fee

Performance Work Statement Revision History

Version Date Mod # Change Description

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 TO-Specific Language

9. APPLICABLE DIRECTIVES/REGULATIONS

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 JFCC IMD Operations and Sustainment

10.2.1 Scheduling

10.2.2 Information Security

10.2.3 Operations Sustainment Engineering

10.2.4 Customer Support Services

10.2.5 Configuration Management and Asset Control

10.3 Events and Engineering Projects

10.3.1 Objective—IRT Project

10.3.2 Objective—QRT Projects

LIST OF TABLES

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

1. PURPOSE

Maintain and sustain the Joint Functional Component Command for Integrated Missile Defense (JFCC IMD) mission/administrative systems, capabilities, and facilities.

2. BACKGROUND

JFCC IMD is a tenant command under U.S. Strategic Command (USSTRATCOM) that operates out of Schriever Space Force Base (SFB) (SSFB), Colorado Springs, CO (COS). Presently, JFCC IMD resides in the MDIOC, Building 730 (Room 222), Building 720 (Rooms 1404–1409 B28), Building 400 (Mod 7, Room 12), Building 442 (first floor), the Joint BMD Training and Education Center (JBTEC) facility (COS), and one other location in COS. JFCC IMD synchronizes global missile defense planning, conducts BMD operations support, advocates for missile defense capabilities, recommends allocation of missile defense forces, and executes joint BMD training and education as directed by Commands, USSTRATCOM (CDRUSSTRATCOM). These actions are performed by JFCC IMD in support of the Combatant Commands (CCMDs), the services, and appropriate U.S. Government agencies to deter adversaries, assure allies, and defend the U.S., deployed forces, allies, and partners against missile attacks.

Predecessor Task Orders (TOs): 20F1500, 18F1500, 19F1500, 9906, 8906, 7906, 6906.

3. SCOPE

The scope is as follows:

• Provide facility, IT services, and information security operations assistance for JFCC

IMD

• Sustain mission operations and mission/administrative systems and capabilities

• Upgrade equipment and infrastructure systems supporting JFCC IMD

• Provide customer support for daily activities, including network management, project management and engineering, design/implementation, MDA ISD, and Install-Move- Add-Change (IMAC) activities

• Perform training and exercise/event support for all Integrated Missile Defense (IMD) spaces

JFCC IMD locations include the following:

• SSFB: Building 720 (Rooms 1404–1409, B28), Building 730 (Consolidated Support Facility [CSF] Room 222), Building 442 (Rooms 100–104), Building 400 (Mod 7, Room 12)

• The Metropolitan Area Network (MAN) site (except for assets or services provided by the 21st Communications Squadron)

• JBTEC: Atrium II facility, 1150 Academy Park Loop, COS (JFCC IMD-owned assets only)

4. SERVICE SUMMARY ITEMS

Exhibit 1 provides the Service Summary Items (SSIs) 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 JFCC

IMD

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 1500, CDRL C003

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.

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

QPI score = 0 QPI score = 9 QPI score =

QPI score =

QPI score =

15 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.

25% 100% review of requirements under QASP guidelines for management/ business relations environment

QPI score = 0 QPI score = 15.25

QPI score = 18.5

QPI score =

QPI score =

25 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-

81861/T

23F1500:

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 C002 DI-MISC-

80508B/T

23F1500: Task Order Status Report, [month ending]

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

• A summary of degradations/failures, including the response times and a root-cause analysis

• Any lapses in hardware service agreements or software licenses

• A summary of workload data on a quarterly basis

• All project closeout documentation, including a project summary, the final resource-loaded schedule, and an element of cost summary for each project

10.2.3.1 C003 DI-MISC

80508B

23F1500:

Maintenance and Spare Report

Identifies type, location, and frequency of recurring sustainment activities and the sparing methodology used in establishing a recommended spares requirement list.

Includes inventory of all spares and the identification of licensing, maintenance agreements, and renewal documentation of hardware and software assets.

10.2.3.2 C004 DI-MISC

80508B

23F1500:

Operational Support Documents:

Technology Refresh Plan

Takes into account the formally documented current state of the hardware necessary to execute business functions, deliver services, and maintain the logical relationships between customers, partners, and suppliers. Primarily, this superset will contain the system architecture, the storage architecture, and the network architecture across the enterprise.

5.2 CDRL Tailoring

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

6. MILESTONES

PWS Task Activity Date/Days After Contract (DAC)

10.1.1 Baseline Review 120 DAC

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 any 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 Contract-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:

• All positions requiring network/system administrator rights/privileges and or conducting information security (i.e., Information Assurance [IA]) duties must meet DoD certification requirements as outlined in DoDI 8570.01-M, Information Assurance Workforce Improvement Program (dated November 10, 2015), including certification on/for specific Operating Systems (OSs) and applications

• Top Secret (TS)/Sensitive Compartmented Information (SCI) clearances and a courier badge (for transportation of hardware to all JFCC IMD facilities)

• Maintain adequate personnel with access to the Metropolitan Area Network (MAN) site

• Core MDA Integrated Service Desk (ISD) business/duty hours are 0730–1600, Monday–Friday (federal holidays not included)

8.1 Technical Change Request TO-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 MDA/SSM Directive Memo (001-2021) N/A 6 July 2021

10. STATEMENT OF OBJECTIVES AND OUTCOMES

The contractor shall perform the following requirements under this TO. Exhibit 1 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 JFCC IMD Performance Standard Summary JFCC IMD Operations and Training Support (TO 1500)—Response Time Objectives

Objective Area Initial Response

Estimated Time to Repair

Situation Report

Action Completed

Building 720, Rooms 1404-1408; Directors in Building 720, Room 1409; CoS and DCO in Building 730, CSF Room 222; MAN Site when occupied***

Recurring maintenance As scheduled

N/A N/A As scheduled

Incident request

• Core hours 30 minutes** 1 hour** 6 hours** 24 hours**

• Non-core hours 2 hours** 4 hours** 6 hours** 24 hours** IMAC services

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

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

JFCC IMD Operations and Training Support (TO 1500)—Response Time Objectives

Objective Area Initial Response

Estimated Time to Repair

Situation Report

Action Completed

JBTEC when class or conference is in session Recurring maintenance As scheduled N/A N/A As scheduled

Incident request

• Core hours 1 hour** 2 hours** Daily** 72 hours**

• Non-core hours 2 hours** 4 hours** Daily** 72 hours** IMAC services

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

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

Building 720, Room 1409; JBTEC when no class or conference is in session; MAN site when unoccupied; Building 442, Rooms 100–104; Building 730, CSF Room 222; Building 720, Room

B28 Recurring maintenance As scheduled N/A N/A As scheduled

Incident request

• Core hours 48 hours** 72 hours** N/A 14 days** IMAC services

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

• Routine N/A N/A N/A 30 days* Documentation/drawing updates Redline N/A N/A As scheduled

Events and Engineering Projects IRT projects (10.3.1) N/A N/A N/A As scheduled QRT projects (10.3.2) N/A N/A N/A As scheduled Documentation/drawing updates Redline N/A N/A As scheduled Note:

* Required completion date is based on calendar days following receipt of required materials/equipment ** Response times to complete action excludes A/V and VTC support by associate contractor ***Personnel exceptions approved by JFCC IMD will meet the Building 720, Room 1409 response time objectives

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 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; 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 (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, 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 DoDI 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: Integrated Baseline Review

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

• 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 through 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.

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 #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 JFCC IMD Operations and Sustainment

10.2.1 Scheduling

The contractor shall facilitate the reporting and scheduling of facility maintenance, inspection, and cleaning requirements that are performed under other IRES TOs and other contracts.

• 10.2.1.1 Coordinate, facilitate, and provide access to the JFCC IMD footprint for personnel not permanently authorized within the JFCC IMD footprint, for facility inspections, cleaning crews, VIP visits, project-related visits, and inventory activities.

• 10.2.1.2 Coordinate freeze waivers, as necessary, to minimize and/or eliminate any risk to JFCC IMD.

10.2.2 Information Security

The contractor shall perform security scans for the Global Command and Control System (GCCS)–Joint (GCCS-J), the Processing and Display System (PDS)–Migration (PDS-M), and periodic system audits for GCCS-J.

• 10.2.2.1 Perform periodic scans and update/maintain GCCS-J and PDS-M workstations, as necessary.

• 10.2.2.2 Perform MDA/ICT incident reporting and Classified Message Spill (CMS) activities on MDA Unclassified Local Area Network (LAN) (ULAN) and Classified LAN (CLAN) systems and equipment.

• Determine CMS instances have been properly researched and contained.

• Determine the required level and scope of the cleanup effort.

• Implement each of the detailed steps for containment and sanitation.

• Manage the generation and proper handling of all classified reports to stakeholders and ultimately determine to close the CMS ticket.

The contractor will perform required activities associated with CMS instances as defined in the JFCC IMD Classified Message Spill Procedure, as referenced in PWS paragraph 9.0.

10.2.3 Operations Sustainment Engineering

The contractor shall provide the services necessary for the sustainment of mission systems and capabilities. Sustainment activities include network management, CM, proactive/corrective maintenance, hardware and software refresh, break/fix service restoration, and engineering services for JFCC IMD IT and existing mission capabilities.

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, and with JFCC IMD to resolve any discrepancies. The contractor shall act as liaison between JFCC IMD and the associate contractor to facilitate A/V Operations and Maintenance (O&M) break/fix activities, as needed. The contractor shall maintain IA infrastructure to MDA and DoD standards. The contractor shall maintain all sustainment engineering documentation.

• 10.2.3.1 Maintain and refresh hardware, software, and current capabilities IAW industry best maintenance practices, ensuring an appropriate mix between 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. The contractor shall act as liaison between JFCC IMD and the associate contractor for A/V upgrade requests and shall oversee A/V implementation of solutions, upgrades, enhancements, and reconfigurations completed by the associate contractor.

• 10.2.3.2 Develop and implement an integrated approach to operate, manage, and plan IT investments that provide for the continuous identification, selection, control, Life Cycle Management (LCM), and evaluation of the IT investments in a structured process, resulting in a systematic method maximizing the return of IT investments, both in the present and in the future.

• 10.2.3.3 Critical functional areas (as defined under Exhibit 1)—maintain continuous situational awareness to anticipate problems and react in order to prevent or minimize mission degradation to ensure availability of all mission equipment within critical functional areas. Exhibit agility in response to urgent operational needs and affect management of IT infrastructure and capabilities.

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 1. As the customer, JFCC IMD reserves the right to set and/or change the priority/urgency of all tickets opened in areas identified as critical functional areas in Exhibit 1. The contractor shall not be held accountable for completion of A/V and VTC actions by the associate contractor.

10.2.3.4 Other functional area—during core hours, respond to degradations/ failures within one hour and provide an estimated timeline associated with service restoral IAW contractor-developed ticket escalation procedures. Demonstrate minimal impact to mission while repair activities are initiated, conducted, and completed. Incidents occurring outside of core hours shall be worked the following business day.

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 1.

The contractor shall not be held accountable for completion of A/V and VTC actions by the associate contractor.

• 10.2.3.5 Maintain currency on software licensing and hardware warranties. Track life cycle information in relation to vendor End-of-Life (EOL)/End-of-Service (EOS) and MDA network owner end-of-net-worthiness and support.

10.2.4 Customer Support Services

The contractor shall provide customer support services, including MDA ISD operations, touch-labor client services, conference room AV support, conference and event activities, daily maintenance checks of equipment (including VTCs), IMAC services, and engineering services above those service levels provided under other IRES TOs.

• 10.2.4.1 Provide Tier II MDA ISD support during core business hours. Ensure knowledge base maintenance and development enabling first call resolution of help desk calls. Ensure 24/7 2-hour response time for help desk support calls coming from the critical functional areas.

• 10.2.4.2 Provide an online work request process/system that allows assigned Government personnel to submit, assess, validate, vet, prioritize, approve, track, and evaluate work requests for non-MDA ISD support-related activities. The content of the contractor response for each request is as follows: scope, need date, identification of POCs, 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 that require eight man-hours or fewer to complete.

• 10.2.4.3 Provide IT technician support for JFCC IMDs standalone (i.e., non-networked) systems and devices. Install and configure computer hardware, peripherals, operating systems, and applications. Support the roll-out of new hardware, applications, or updates. Monitor and proactively maintain computer systems, replace parts as required, perform troubleshooting to diagnose and resolve problems, check computer hardware to ensure functionality, and help in identifying computer equipment needs/shortages for procurement. Maintain documentation and hardware/software registers.

10.2.5 Configuration Management and Asset Control

The contractor shall provide facility and equipment configuration control and provide compliant asset management services of assets (i.e., equipment and cell phones) from initial receipt to final disposition, and maintain an auditable inventory. The contractor shall implement a mechanism for recording, tracking, and reporting the status of Configuration Items (CIs). The contractor shall examine, evaluate, and monitor baseline hardware/software to maintain version control integrity.

• 10.2.5.1 Maintain positive CM control for all facilities, cabling, systems, operating procedures, and assets.

• 10.2.5.2 Develop and provide 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.

10.3 Events and Engineering Projects

The contractor shall provide technical oversight for all phases of project planning, design, scheduling, execution, and reporting to ensure technical solutions for projects meet their mission, goals, and objectives. The contractor shall implement solutions, upgrades, enhancements, and reconfigurations completing planning, design, procurement, implementation, documentation, and CM activities.

Projects are categorized as IRT (minor) and QRT (small). These projects will be approved and documented in the Aspen database through the Requirements Review Board (RRB) by the COTR or provided approval privileges by the COTR for the JFCC IMD Program Office.

The Government requests an emailed list of approved projects for the current month to be emailed to the COTR, the PCO, and the Contracting Officer Representative (COR) by the 10th calendar day of the following month. The Government also requests that a reporting feature is created in Aspen in which Aspen users can access approved projects for a selected time period by categories of routine, IRT, and QRT.

This process will be reflective of anticipated, future routine Aspen projects that are neither critical nor require significant procurement. These noted exceptions will continue to be discretely planned.

Ensure compliance with the published instructions and standards IAW the MDA/DM Directive Memo (001-2021) dated 6 July 2021 that governs the MDIOC Engineering Review Board (ERB). Ensure completion of SE gate reviews required in order to validate requests, align with facility standards, and integrate solutions across the MDIOC facility.

• Present to the ERB all projects impacting the MDIOC facility that meet the entry criteria defined in the charter.

• Submit briefings and supporting documentation to the MDIOC ERB as outlined in the charter.

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

Priced Prospective Work Packages (WPs) (PPWPs) will be executed to meet surge requirements. Material and software required for these projects will be executed as PPWPs.

The source and timing of available funds may also require that new Contract Line Item Numbers (CLINs) be established in conjunction with PPWP execution.

• Material package (PPWP)—material (Software, Hardware and Miscellaneous Equipment) to implement upgrades, enhancements, reconfigurations, and projects.

• Generic labor (PPWP)—labor to surge if additional project requirements are identified.

10.3.1 Objective—IRT Project

The contractor shall plan, design, schedule, and execute IRT projects. The COTR will approve projects in Aspen prior to execution for all work associated with this task.

Outcomes:

• Operate in the context of the IRES Program Systems Engineering Master Plan

(SEMP) (TO 8002, CDRL C005) and established governance processes reflected through standardized engineering artifacts and an integrated SE approach to design efforts to meet technical requirements.

• Collaborate with the Government to obtain required Chief Information Officer (CIO) and MDA/DX approvals, as required.

• Perform project oversight—including customer coordination and communications— and respond to Requests for Information (RFIs) and problem resolution.

• Plan and develop sequenced, resource-loaded schedules. Identify resources needed to accomplish the project and ensure all resources have the proper work authorizations. Identify risks, work sequencing, critical paths, and procurement lead-times.

• Initiate requirements management activities. Document and track requirements in a Requirements Traceability Matrix (RTM) that identifies specific and derived requirements.

• Develop design solutions and conduct design reviews (preliminary and final) for Government approval. Participate in required MDIOC review boards (e.g., Project Steering Committee [PSC], Design Review Board [DRB], Engineering and Architecture Board [EAB]).

• Develop, maintain, and coordinate technical documentation—including Technical Data Packages (TDPs), engineering drawings, and interface control specifications— for existing systems that require documentation or because of newly developed and/or modified systems. Ensure fully coordinated, redlined change documents are available for the Government user and service technicians at customer turnover date; formal configuration control documentation and drawings shall be updated and posted as scheduled.

Baseline engineering documentation (due date will be identified in each project):

• Execute a project change management process.

• Complete project close-out activities.

10.3.2 Objective—QRT Projects

The contractor shall plan, design, schedule, and execute QRT projects. The COTR will approve projects in Aspen prior to execution for all work associated with this task.

Outcomes:

• Operate in the context of the IRES Program Systems Engineering Master Plan

(SEMP) (TO 8002, CDRL C005) and established governance processes reflected through standardized engineering artifacts and an integrated SE approach to design efforts to meet technical requirements.

• Collaborate with the Government to obtain required CIO and MDA/DX approvals, as required

• Perform project oversight—including customer coordination and communications— and respond to RFIs and problem resolution.

• Plan and develop sequenced, resource-loaded schedules. Identify resources needed to accomplish the project and ensure all resources have the proper work authorizations. Identify risks, work sequencing, critical paths, and procurement lead-times.

• Initiate requirements management activities. Document and track requirements in an RTM that identifies specific and derived requirements.

• Develop design solutions and conduct design reviews (preliminary and final) for Government approval. Participate in required MDIOC review boards (e.g., PSC, DRB, EAB).

• Develop, maintain, and coordinate technical documentation—including TDPs, engineering drawings, and interface control specifications—for existing systems that require documentation or because of newly developed and/or modified systems.

Ensure fully coordinated, redlined change documents are available for the Government user and service technicians at customer turnover date; formal configuration control documentation and drawings shall be updated and posted as scheduled.

Baseline engineering documentation (due date will be identified in each project):

• Execute a project change management process.

• Complete project close-out activities.

• Provide all close-out documentation—including a project summary, the final resource-loaded schedule, and an element of cost summary for each project—in the monthly TOSR (CDRL C002).

10.1.3 Task Order Award and Modification