DRAFT PWS.pdf

Performance Work Statement (PWS) for Air Force PLM Software IDIQ Effort

1. Introduction

1.1 Organization

The Air Force Life Cycle Management Center, Business and Enterprise Systems Directorate (AFLCMC/HI), located at 4225 Logistics Avenue, Building 266, Room N101, Wright- Patterson AFB, OH 45433, is responsible for this effort.

1.2 Goal

The Siemens Teamcenter software provides the core functionality and architecture to meet the Air Force's Product Lifecycle Management (PLM) system requirements. Currently, the Air Force operates multiple, disparate, and sub-optimized implementations of the Teamcenter solution, leading to inefficiencies and redundancies. This contract aims to reactivate and maintain licenses for Siemens Teamcenter commercial software to streamline operations, reduce redundancy, and enable timely and informed decision-making.

1.3 Scope

This effort encompasses the reactivation and maintenance of Teamcenter licenses, upgrading inactive software licenses to the current version, and providing ongoing support for reactivated licenses. The Air Force reserves the right to renew maintenance for existing active Siemens licenses (6,000+) at negotiated rates under this IDIQ. Additional services may include original equipment manufacturer (OEM) technical support and training for the Capability Support Office (CSO). Formalized training for the broader Air Force user community is not anticipated.

1.4 Acquisition Strategy

This contract supports the reactivation and upgrade of Air Force-owned Teamcenter licenses, with provisions for ongoing maintenance. The Air Force reserves the right to exchange existing licenses for current or future Siemens software that better meets operational needs. OEM support requirements will be defined and negotiated at the task order level.

1.5 Air Force PLM Challenge

The PLM effort differs from traditional software efforts as it focuses on standardizing existing capabilities across the enterprise rather than developing a new software base.

Current Teamcenter configurations at various Air Force bases (e.g., Robins, Hill, Tinker) vary in version and module stack, leading to inconsistencies in functionality. This effort aims to create a standardized enterprise instance that incorporates best practices and addresses these challenges.

1.6 Solution

The PLM Software IDIQ contract will support the Air Force's IT lifecycle by consolidating disparate Teamcenter implementations, sustaining legacy systems, and enabling future service-oriented capabilities. The contract provides flexibility and responsiveness to accommodate varying quantities and timelines for products and services.

2. Requirements

2.1 General Product Requirements

All products provided under this contract shall comply with the following guidelines:

2.1.1 Information Assurance (IA) Technical Considerations

The Contractor shall ensure all Commercial-Off-The-Shelf (COTS) IA and IA-enabled products comply with AFI 33-117, Information Assurance (IA) Management. Products must meet CNSSP-11 compliance and be validated by accredited labs under the NIAP Common Criteria Evaluation and Validation Scheme or NIST FIPS Cryptographic Module Validation Program (CMVP).

2.1.2 Technical Refresh

The Contractor shall provide commercially available software updates and enhancements to the Government at no additional charge if such updates are provided to other customers without charge. Updates must include "state-of-the-art" technology and be delivered to the Capability Support Office (CSO) as specified in CDRL A001.

2.1.3 Products

The Contractor shall provide commercial items as defined by FAR 2.101, including all documentation, software, and user guides. All products must comply with the Trade Agreements Act of 1979 (TAA) and other applicable standards, including those in the AF Standards Center of Excellence Repository.

2.2 Software

This contract includes the reactivation of Air Force-owned Teamcenter licenses, with options for additional licenses, maintenance, and OEM support. The Air Force reserves the right to exchange existing licenses for other Siemens software solutions to better meet operational needs. Reactivation of licenses will occur on a staggered timeline.

2.3 Product Support Requirements

2.3.1 OEM Support

The Contractor shall provide OEM technical support, including:

• Configuration, integration, deployment, and support guidance.

• Technical and functional analysis of COTS products and modules.

• Participation in PLM working groups and Technical Interchange Meetings (TIMs).

• Priority problem investigation and resolution.

• Technical guidance on system architecture, performance, and scalability.

• Support for integration with new or existing Air Force applications.

• Assistance in classified or highly secure computing environments, as required.

2.3.2 Product Delivery Capability

The Contractor shall ensure timely delivery of PLM products to meet both routine and fluctuating Government requirements as specified in individual task orders. Any anticipated delivery delays must be reported to the Contracting Officer within two business days.

2.3.3 Installation

When required, the Contractor shall provide installation support as specified in individual task orders. Security requirements will be addressed in the IDIQ and task orders as necessary.

2.3.4 Customer Support

The Contractor shall provide telephone support to the CSO from 0800 to 2000 EST, Monday through Friday, to address questions and resolve issues. This support should be addressed 24 hours, 7 days a week, 365 days a year in accordance with the severity levels defined in Section 2.6.4 of this PWS.

2.8. Secret and Top-Secret Environments – ECP Task

Upon Government issuance of an approved Engineering Change Proposal (ECP) task order, the Contractor shall plan, design, configure, test, and deploy the AF-PLM Enterprise platform (Siemens Teamcenter) within designated Secret (SIPRNET / Cloud One IL6) and/or Top-Secret (JWICS) cloud-hosted operating environments.

The Contractor shall provide security-cleared personnel possessing active Secret and/or Top-Secret/SCI clearances in accordance with the contract's DD Form 254. The Contractor shall apply RMF controls, perform system vulnerability scanning, and generate Cybersecurity Test Reports (CSTR) tailored for classified domains. The Contractor shall coordinate with the AF-PLM CSO ISSM to obtain and maintain an Authorization to Operate (ATO) for all classified deployments.

3. Contract Requirements

3.1 Performance Reporting

The Contractor's performance will be monitored and assessed at both the task order and IDIQ levels, with results documented in the Contractor Performance Assessment Report

(CPAR).

3.2 Task Order Management

The Contractor shall provide a qualified workforce, including a project/task order manager, to oversee all aspects of task orders. The Contractor shall monitor performance, manage risks, resolve issues, and ensure timely and high-quality delivery of contracted deliverables.

3.9 Security Safeguarding and Technical Data Rights

3.9.1. Safeguarding Covered Defense Information (DFARS 252.204-7012)

The Contractor shall protect all Controlled Unclassified Information (CUI) and Covered Defense Information (CDI) hosted within Cloud One or processed on contractor development systems in strict compliance with DFARS 252.204-7012 and NIST SP 800-171.

3.9.2. Rights in Technical Data and Computer Software (DFARS 252.227-7013 & 252.227-7014)

The Government shall retain Unlimited Rights in all custom software configurations, database schema adaptations, automated workflows, scripts, and systems engineering documentation developed at Government expense under this contract. The Contractor shall deliver all source code, configuration files, and build pipelines to the Government's Bitbucket repository without proprietary markings or licensing restrictions.

3.10 Mandatory Service Delivery Summary (SDS) / Quality Assurance Surveillance Plan (QASP) Matrix

Performance Objective

PWS

Reference

Performance Standard

Acceptable Quality Level

(AQL)

Method of Surveillance

Sprint Backlog Execution

2.3.1 / 2.3.6

Sprint deliverables meet the agreed-upon "Definition of Done" (DoD).

≥ 90% of committed sprint user stories completed within the 2-week cycle.

Bi-weekly Sprint Review reports & Jira tracking.

System Testing Quality

2.3.13 / 2.3.16

Software releases delivered to UAT must be free of critical defects.

100% of Priority 1 and 2 Deficiency Reports resolved prior to TRR.

Zephyr Test Reports & TRR documentation.

Help Desk Responsiveness

2.6.3 / 2.6.4

Response to support tickets during business hours (M-F, 0800-

1800 ET).

95% of tickets acknowledged within 2 hours of receipt.

Jira Service Desk automated monthly reports.

Critical Incident Resolution

2.6.3 / 2.6.4

Critical/Emergency (P0/P1) outages resolved or bypassed.

Resolution or workaround established within 4 hours of notification.

Help Desk logs & system status reports.

Key Personnel Continuity

4.0 Substitution

notifications and overlap transition management.

100% compliance with 14-day written notification and 5-day overlap.

PMR reviews and staffing reports.