Performance Work Statement for

Product Data Systems

Air Force Life Cycle Management Center Technical Services Division

AFLCMC/LZP-Robins

05 JANUARY 2026

PDSS IV 05 JAN 2026

PWS REVISION: 0 2

TABLE OF CONTENTS

1. DESCRIPTION OF SERVICES

1.1. Objectives

1.2. Benefit to United States Air Force

1.3. Background

2. SERVICES SUMMARY

3. GOVERNMENT FURNISHED PROPERTY (GFP) / GOVERNMENT FURNISHED MATERIAL

(GFM) AND SERVICES

3.1. Government Inventory

3.1.1. Government Inventory Reports

3.1.2. Government Furnished Property (Material/Equipment)

3.1.3. Contractor Responsibility

3.2. Government Property to be Provided

3.3. Base Support

3.4. Reporting of Government Property

3.5. Loss of Government Property

3.5.1. Definition of Loss of Government Property

3.5.2. Reporting Loss of Government Property

3.6. Return or Retention of Government Property

4. TECHNICAL REQUIREMENTS

4.1. Period and Place of Performance

4.1.1. Contract/Order Period of Performance

4.1.2. Hours of Operation

4.1.3. Accommodation

4.1.4. Location

4.1.5. Travel

4.1.6. Remote Work

4.2. Contract Data Requirements List(s) (CDRL)

4.2.1. Quality of CDRL Deliverable

4.2.2. Receipt of CDRL Deliverable

4.3. Antiterrorism (AT)

5. TECHNICAL SUPPORT

5.1. Technology Support

5.2. System Support Services

5.3. System Sustainment

5.3.1. Help Desk Sustainment

PWS REVISION: 0 3

5.3.2. Operations Sustainment

5.3.3. Cybersecurity Sustainment

5.3.4. Development sustainment

5.4. Software Licensing/Testing

5.5. ‘Warm’ Site and System Backup Capabilities

5.6. System User Training

5.7. Production Publishing Support

5.8. Content Management System Implementation/Support

5.9. S1000D Specification Data Capabilities

5.10. Subject Matter Expert Support

5.10.1. Transformation and Migration Support Services

5.10.2. Enterprise Level Capabilities/Data Support

5.10.3. Documentation

5.10.4. Project Management/Reports

5.10.5. Data Rights

5.10.6. Support Meetings/Conferences

5.10.7. Reserved

5.10.8. Reserved

5.10.9. Reserved

5.10.10. Required Skills

6. GENERAL INFORMATION: PRODUCT DATA SYSTEMS SUPPORT

6.1. Security Requirements

6.1.1. Security Regulations

6.1.2. Operations Security (OPSEC)

6.1.3. Communications Security (COMSEC)

6.1.4. Security Clearance

6.1.5. Security Incident or Violation

6.1.6. Access to Government Systems

6.1.7. Access to Robins AFB

6.1.8. Contractor Identification

6.1.9. Common Access Card (CAC)

6.2. Environmental Management (EMS)

6.3. Agency Affirmative Procurement Programs

6.4. Safety Requirements

6.4.1. Mishap Notification/Investigation

PWS REVISION: 0 4

6.4.2. Safety and Health Plan/Program

6.5. Inspection of Services

6.6. Service Contract Reporting (SCR)

6.7. Invoicing/Payment and Receipt/Acceptance

6.8. Quality Control Plan/Quality Management (QMS)

6.8.1. Self-Assessment Program (SAP)

6.8.2. Quality Control and Continuous Process Improvement (CPI)

6.9. Trafficking in Person

6.10. Continuation of Mission Essential Services During a Crisis

6.10.1. Designation of Services as Mission Essential

6.10.2. Mission Essential Contractor Services

6.11. Nondisclosure Requirements

6.12. Personnel Reporting

6.13. Uses and Safeguarding of Information

6.14. User Manuals

6.15. Non-Personal Services

6.16. Transition/Phase Out

6.17. Government Points of Contact

7. APPENDICES

7.1. Appendix A. Reference(s)

7.2. Appendix B. Product Data Systems Hardware and Application Descriptions

8. EXHIBITS

8.1. Exhibit Reference(s):

PWS REVISION: 0 5

DESCRIPTION OF SERVICES

1.1. Objectives

This Performance Work Statement (PWS) describes the services required to support Department of the Air Force (DAF) Product Data Systems Support (PDSS). These services include systems management, data management, and enterprise migration and sustainment support required for continued performance of highly specialized technical services at Robins Air Force Base (AFB) supporting product data systems and infrastructure, data management, conversion and migration processes, and transformation initiatives.

1.2. Benefit to United States Air Force

This acquisition will benefit the DAF by providing processes and tools to enable the enterprise division and its customers to acquire, develop, manage, transform, inspect, store, distribute, and maintain technical data.

1.3. Background

The contractor shall provide all labor, supplies, and technical support services necessary to operate and maintain Robins AFB product data hardware and software; to aid Government customers in managing and executing technical data generation, acceptance and sustainment activities, processes, and products within the product data environment; and to support data improvement, cleansing, and migration efforts necessary to prepare data for transition into modernized and/or DAF enterprise-level systems, such as the Enhanced Technical Information Management System (ETIMS), the Technical Order Authoring and Publishing (TOAP) enterprise, Air Force Product Lifecycle Management (AF-PLM), solutions resulting from DAF Logistics Capability Initiatives (CI), solutions resulting from DAF AFMC/A4 Logistic Information Technology (LogIT) initiatives, solutions resulting from AF-PLM Enterprise solution initiatives, and other system solutions which may result from system and data center consolidation activities.

ETIMS provides the capability for DAF system maintainers to manage their Technical Order (TO) and Electronic TO (eTO) subscriptions and libraries. Much of the data processed and/or managed within the Robins AFB Product Data Systems environments must also reside within the ETIMS in order to satisfy end-user requirements. Portions of the requirements outlined within this PWS are specific to the TO document structure and data loading requirements driven by ETIMS.

TOAP is designated as the organic TO authoring and publishing component of the DAF Standard TO Management System. TOAP provides the DAF enterprise capability to manage, author, and publish TO publication source content data and enforces authoring and publishing compliance outline in DAF policy documents.

AF-PLM is a major initiative designed to establish and implement an Air Force enterprise system which will subsume the majority of the existing Robins Technical Data-Product Data Management (TD-PDM) system and the data contained within those systems. Since the AF-PLM solution will provide capabilities/functionality similar to those currently supplied by the Robins AFB technical data systems, the level of technical systems and data support required is expected to increase in preparation for AF- PLM implementation, and then decrease as capabilities and data incrementally transition to that implementation and/or other enterprise-level systems.

PWS REVISION: 0 6

At present, the TD-PDM system contains approximately 70,000 active TO documents/increments, comprising an estimated 50,000,000 pages of various sizes; over 800,000 Computer Aided Design/Computer Aided Manufacturing (CAD/CAM) models and files; over 175,000 part indenture configurations consisting of over 18,300,000 part records; and more than 84,000,000 drawing related datasets in A-TEAM are managed at Robins AFB. Additionally, data owned and managed by DAF organizations at locations other than Robins is actively being migrated for sustainment within the PDSS environment at Robins AFB. Services to support product data (TO, engineering, and other product data) systems infrastructure and data management, sustainment, and transformation activities include:

Technical services to manage, maintain, and administer all computing hardware and software utilized to support the management, creation, sustainment, storage, and distribution of technical and engineering data.

Technical support to assist the Government in development and execution of digital data support, sustainment, and transformation strategies and processes.

Technical support necessary to facilitate evaluation and implementation of hardware and software necessary to support transition of technical data systems functionality and data to recently adopted DAF data standards, to newly implemented local system/data environments, and to DAF enterprise-level systems currently in various conceptual, planning, development, and/or implementation stages.

Technical support to establish, enhance, and execute processes necessary to discover, establish, and maintain relationships/links between various types of product data (i.e., parts, drawings, TOs).

2. SERVICES SUMMARY

Performance Objectives

PWS

Paragraph Performance Threshold

Maintain tech data system availability to all users

5.3

Maintain system uptime rate of 98.5% or higher monthly per system (TD-PDM, TOAP, STOR).

(Based on a 30-day month, 100% system uptime would equate to 720 hours.)

Cybersecurity and Authority- To-Operate (ATO) support

5.3

Submit required RMF documentation updates within specified timeframes: SSPs - within 15 days of system changes Hardware/software inventories - within 15 days of changes.

Review and implement release Secure Technical Implementation Guidelines

(STIGS)

5.3 Submit all applicable STIG checklist files with comments for each check and zero Not Reviewed checks within 30 days of release.

Maintain software licensing compliance

5.4 Provide notification of illegal software products within 30 days of identification.

Maintain viable system/data backup

5.5 Ensure execution and validity of backup routines at 100%. Full backups shall be accomplished weekly with daily incremental backups accomplished.

PWS REVISION: 0 7

Performance Objectives

PWS

Paragraph Performance Threshold

Maintain contingency capabilities

5.5 Monthly certify 100% synchronization and availability of critical data transferred to the COOP.

Complete delivery of PDF quality assurance data

5.10.1.3

Submitted documents priority load:

Routine: within seven (7) working days of receipt Urgent and Emergency: within three (3) working days of receipt Ensure accuracy of processed IPB part data

5.10.1.4 Ensure required data accuracy rate of 98% based on MPL achieved from source IPB content.

Development/sustainment of system, system security, and process documentation

5.10.3

Correct identified deficiencies or required updates within 15 working days. Provide a report of which documents were validated, and which ones were updated. Versioning and change summary shall be captured in a change log on each document.

Government Furnished Equipment (GFE) Hardware Inventory

3.4, 3.6 Maintain accurate hand receipts and update within 5 days of equipment assignment or changes.

3. GOVERNMENT FURNISHED PROPERTY (GFP) / GOVERNMENT FURNISHED

MATERIAL (GFM) AND SERVICES

Contractor will track, secure, and account for all GFP/GFM IAW FAR 45 and DFARs 245: The property shall be listed as an attachment of the request for proposal package. The fillable form is located at https://dodprocurementtoolbox.com/site-pages/gfp-attachments.

3.1. Government Inventory

3.1.1. Government Inventory Reports

The contractor shall perform an inventory of all Government property to include material and equipment not later than thirty (30) calendar days after contract start. After the initial inventory, the contractor shall inventory quarterly thereafter. Inventories may be required intermittently and shall be submitted as requested by the COR or PM. Quarterly physical inventory reports shall be submitted to the Government Property Administrator (AFSC/PZIE and the PMO). The report shall detail the results of the inventory, any items not accounted for and items that are lost, damaged or destroyed beyond use.

(Exhibit A: CDRL A001, Technical Report-Study/Services, DI-MISC-80508B)

3.1.2. Government Furnished Property (Material/Equipment)

The contractor shall maintain records evidencing receipt, accountability, preventative maintenance, and disposal as defined within the Government property clauses. All furnished Government property shall be included in the attached GFP inventory list spreadsheet.

The contractor shall maintain a record of accountably and allocation for all GFP (Material/Equipment) by PDSS major program including software license allocation and hardware allocation by system down to the application level where possible. The contractor shall be able to supply a detailed report of license allocation, and a report of hardware required to support each PDSS major program.

PWS REVISION: 0 8

3.1.3. Contractor Responsibility

The contractor shall make recommendations for purchases, as necessary, whenever existing hardware and/or software serviceability must be maintained, expanded or replaced to meet the requirements.

(Exhibit A: CDRL A001, Technical Report-Study/Services, DI-MISC-80508B)

The contractor will be responsible for gathering requirements (maintenance, support level, versioning, etc.), obtaining quotes and executing purchases, and for physical acceptance of procured items.

The contractor shall also recommend for lease or purchase any equipment, furniture, supplies, office space, and any/all other items or services deemed necessary to fulfill the requirements outlined in this PWS. Recommended items are to be acquired through means deemed most advantageous to and approved by the Government. All software developed under this contract shall be provided with unlimited rights. All equipment acquired, or software acquired, developed or licensed to facilitate processes or meet production requirements shall transfer to the Government at contract completion.

The Government shall have unlimited rights to all non-commercial software developed under this contract. Non-commercial source code for all systems, scripts, software tools, etc., developed under this contract must be thoroughly documented and shall be delivered unencumbered by restrictive markings to the Government at contract completion or within 30 days after receipt of a request from the Government Program Manager.

(Exhibit A: CDRL A003, Software Transition Plan, DI-IPSC-81429A /A004, Computer Program End Item Documentation, DI-IPSC-80590B)

Commercial software licenses shall also transfer to the Government at contract completion, or within 30 days after receipt of a request from the Government Program Manager.

(Exhibit A: CDRL A003, Software Transition Plan, DI-IPSC-81429A)

The Government Program Manager shall approve all development efforts prior to start of development.

All custom-developed noncommercial software shall be properly documented using industry or DAF standard techniques.

(Exhibit A: CDRL A004, Computer Program End Item Documentation, DI-IPSC-80590B)

3.2. Government Property to be Provided

The Government will provide the contractor access to facilities and the PDSS hardware and software necessary to support the tasks. With the exception of COTS software and standard office/supply items, all required technical data support materials currently utilized shall be provided by the Government.

Therefore, the contractor shall utilize Government property to fulfill the requirements of this contract whenever possible.

3.3. Base Support

The Government will furnish property incidental to the place of performance including office space and equipment, i.e., computer equipment, software, output device(s), phone/phone line, facsimile equipment, reproduction equipment and office supplies.

PWS REVISION: 0 9

3.4. Reporting of Government Property

The contractor shall have a system of internal controls to manage (control, use, preserve, protect, repair, and maintain) Government property in its possession in accordance with FAR 52.245-1, and its property management system shall be adequate to satisfy the requirements of this clause. The contractor shall record receipt and return of all Government Furnished Property (GFP), as well as the reporting of shipment, consumption, disposal, or transfer to another contract, in the GFP Module in Procurement Integrated Enterprise Environment (PIEE), https://piee.eb.mil, as stipulated by DFARS 252.245-7005.

This reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract. GFP training and guidance is located at the DoD Procurement Toolbox at https://dodprocurementtoolbox.com/site-pages/gfp-training.

3.5. Loss of Government Property

3.5.1. Definition of Loss of Government Property

“Loss of Government property” means unintended loss of or damage to Government property including property that cannot be found after a reasonable search, loss due to inadequate storage, loss due to lack of security, theft, damage requiring repair to restore the item to usable condition, or damage that renders the property useless for its intended purpose or Beyond Economical Repair (BER). Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing. Unless otherwise stated in the contract/order, loss of Government property does not include normal and reasonable inventory adjustments, i.e., losses of low priority consumable material, such as common hardware, as agreed to by the contractor and the Government Property Administrator.

3.5.2. Reporting Loss of Government Property

The contractor shall report loss of Government property in the GFP Module located in PIEE, https://piee.eb.mil/piee-landing/.

3.6. Return or Retention of Government Property

All property provided by the Government remains the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the Procuring Contracting Officer (PCO) directs the contractor to retain the property for continued use under a successor contract. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO. All material generated under the contract/order becomes the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the PCO directs the contractor to retain the material for continued use under a successor contract.

4. TECHNICAL REQUIREMENTS

4.1. Period and Place of Performance

4.1.1. Contract/Order Period of Performance

The period of performance for the contract/order will extend 14 JAN 2026 through 13 JUL 2027.

PWS REVISION: 0 10

4.1.2. Hours of Operation

Contractor personnel shall perform work during normal business hours Monday - Friday, 0700 - 1700 local time, excluding 11 Government-observed holidays, which currently include:

New Year’s Day Labor Day Martin Luther King Day Columbus Day President’s Day Veteran’s Day Memorial Day Thanksgiving Day Independence Day Christmas Day Juneteenth Day

In addition to the days designated as holidays, the Government may observe the following days as Government closure days:

Any other day designated by Federal Statute

Any other day designated by Executive Order

Any other day designated by Presidential Proclamation

Any other day designated as closure day with regard to Robins AFB facilities

On Government observed holidays and days designated by Federal Statute, Executive Order, Presidential Proclamation, or as closure days, when a Government staff representative is not present onsite, contractor personnel will not be permitted to work within the Robins AFB facilities, unless approved by the Government PM or COR. For regular Government observed holidays telework shall not be permitted. For ad-hoc designated holidays or other closures, the Government intends to allow telework but will need to approve on a case-by-case basis depending on the circumstances of the closure and workload.

In the event that an urgent situation arises that requires contractor personnel to rapidly respond and perform during periods of facility closures, access to facilities will be provided by the Government to allow appropriate contract staff members to respond and take necessary preventative, corrective, and/or recovery actions. Situations typically requiring rapid response during facility closure are those associated with critical system failures, with environmental issues carrying the potential to damage essential systems or equipment or to render equipment warranties and/or maintenance invalid, and/or those that that could result in data loss. While Government technical program staff and CORs associated with the program will be responsible for providing the contractor with access to Robins AFB facilities, the Government contracting officer will be responsible for providing direction to the contractor regarding any temporary suspension of performance.

The contractor may be required to perform work under this contract in excess of eight (8) hours per day.

Therefore, normal business hours or alternate business hours may be altered for a specified or indefinite period by the appropriate contract program management staff.

4.1.3. Accommodation

The contractor is required to submit all requests for accommodation for review and final approval by the Government. Accommodation requests that impact the contractor’s ability to perform work onsite will be reviewed by the PMO and a decision (approval or denial) issued within 10 business days. Work

PWS REVISION: 0 11

approved to be performed at an alternative location will be subject to remote work conditions outlined in

4.1.6 of this document. The contractor shall provide a written request with appropriate rationale and justification for the Government Program Manager/COR approval prior to any accommodation agreement.

4.1.4. Location

These services will be performed at Robins Air Force Base.

4.1.5. Travel

Contractor travel may be required. Contractor travel will be billed as a cost reimbursable item and is subject to the guidelines outlined in the Joint Travel Regulation (JTR). Reimbursement of travel expenses may be subject to submission of expense receipts prior to invoicing for reimbursement. The contractor shall be responsible for making their own travel and lodging arrangements as necessary to support the requirements outlined. All requests for travel shall be approved by the Government Program Manager or COR prior to expending funds. A detailed trip report will be provided to the Government Program Manager/COR not later than five (5) business days after completion of travel. Receipts must be presented with the invoice for reimbursement of actual travel costs.

(Exhibit A: Exhibit A: CDRL A006, Report, Record of Meeting/Minutes, DI-ADMN-81505).

4.1.6. Remote Work

All contractor staff are required to work on-site at Robins AFB daily (per section 4.1.5) and must be geographically located nearby. Remote work may be considered on a case-by-case basis by the Program Management Office (PMO) for positions with difficult-to-fill skillsets. The contractor is required to submit all remote work requests to the PMO for review. Each request must clearly identify the specialized skillsets considered difficult-to-recruit and outline the plan for fulfilling all contractual obligations while working remotely. The PMO will review each request and issue a decision (approval or denial) within 10 business days. Work approved to be performed at an alternative location will require use of Government Furnished Equipment (GFE) which will be provided and authorized for use by the Government. All GFE used for remote work will be configured per requirements outlined within Air Force Manual (AFMAN) 17-1301, Computer Security (COMPUSEC) and National Institute of Standards and Technology (NIST) Special Publication (SP) 800-46, Guide to Enterprise Telework and Remote Access Security. Operating costs associated with the contractor using an alternative worksite will not be assumed by the Government and will be the responsibility of the contractor. The contractor shall maintain availability during core hours (per section 4.1.1) via email and phone. All expenses for internet, telephone connectivity, and other equipment/facility services shall be borne by the contractor.

The contractor shall provide a written request with appropriate rationale and justification for the Government Program Manager/COR approval prior to any remote work agreement.

Classified work may be authorized at an alternate worksite with the approval of Government Program Manager or the COR and the security office only with an approved and assigned deviceONE SecureView (ADSV) machine. If approved, all users are required to follow all Security Guidance for Classified Portable Electronic Devices guidelines to include the ‘Acceptance of Risk to Operate United States Air Force (USAF) SecureView (SV)’ memorandum published by the Defense Information System Agency (DISA).

PWS REVISION: 0 12

4.2. Contract Data Requirements List(s) (CDRL)

CDRL Title Authority PWS Reference Date of First Submission

A001 Technical Report- Study/Services

DI-MISC-

80508B

5.3, 5.4, 5.6, 5.10.1.10.1.3, 5.10.1.4, 5.10.2.1, 5.10.3, 3.1.1, 3.1.2, 3.1.3

As required

A002 Status Report

DI-MGMT-

80368A

5.3, 5.5, 5.10.1.4, 5.10.4

40 days after contract award

A003 Software Transition Plan (STrP)

DI-IPSC-

81429A NOT 2

5.10.3, 5.10.5, 3.1.3 As required

A004 Computer Program End Item Documentation

DI-IPSC-

80590B

5.10.3, 5.10.5, 3.1.3 As required

A005 Conference Agenda

DI-ADMN-

81249C

5.10.6 As required

A006 Report, Record of Meeting/Minutes

DI-ADMN-

81505 NOT 1

4.1.5, 5.10.6 As required

A007 Program Management Plan

DI-MGMT-

81797 NOT 3

5.10.4 As required

A008 Environmental, Safety, and Occupational Health (ESOH) Plan

DI-SAFT-

82313

6.4.2 40 days after contract award

A009 Accident/Incident Report

DI-SAFT-

81563 NOT 2

6.4.1 As required (within 24 hours of incident)

4.2.1. Quality of CDRL Deliverable

There shall be no more than one rejection of any deliverable. There shall be no more than two total rejection(s) of deliverables per month. The Government will reject a deliverable if one or more technical errors or three or more minor errors are found within the deliverable. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS, or contract. A minor error is exemplified by a typographical error, a grammatical error, etc. The rejected deliverable shall be corrected and resubmitted within 10 business days of notification of Government rejection.

4.2.2. Receipt of CDRL Deliverable

CDRL deliverables shall be submitted via email to the COR and PCO and submitted directly to the MFT member identified on the CDRL. There shall be no more than one (1) late submission(s) of deliverables per contract year. The contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.Training Requirements

The contractor must participate in unit security training, initial and annual) in accordance with 32 CFR Part 117, National Industrial Security Program Operating Manual (NISPOM), § 117.7(a). Contractors shall complete and maintain records of all required annual training as directed by the Government.

PWS REVISION: 0 13

4.3. Antiterrorism (AT)

Contracts must comply with the AT provisions of the Defense Federal Acquisitions Regulation Supplement, DFARS: 252.204-7004 Antiterrorism Awareness Training for contractors.

5. TECHNICAL SUPPORT

5.1. Technology Support

The current PDSS support environment is described in Appendix B. The contractor shall operate, maintain, and facilitate expanded usage through implementation of new data sets, expansion of the user base, and incorporation of new solutions within the Robins AFB product data environments. While the current hardware infrastructure has been designed to support expanded use and increased storage requirements, the infrastructure components are subject to change to ensure continued viability of the infrastructure to support mission requirements. The contractor shall ensure the product data infrastructure and processes remain viable tools for development, management, storage, sustainment, publication, and distribution of DAF product and technical data. These activities include development of new, or enhancement, or improvement of existing system implementations, and establishment and management of processes to extract, transform, and load data to ensure requirements associated with DAF enterprise-level system implementations are satisfied. The contractor shall provide services necessary to research hardware and software solutions, to provide purchase recommendations to the Government Program Manager, and to implement hardware and software changes within the environment as required. The contractor shall also be responsible for configuration, testing, and implementation of new hardware and/or software applications as necessary and shall routinely be required to implement changes in the environment as necessary to ensure compliance with mandatory security directives/updates, and to ensure performance parameter requirements are achieved. The contractor shall provide personnel capable of working independently and who possess demonstrated working knowledge of the hardware and software components within the PDSS environments to support DAF processes. The contractor shall be responsible for ensuring all training and certifications prerequisite to gaining access to, and performing system support functions requiring elevated access privileges on systems attached to unclassified and classified DAF and stand-alone networks and the supported PDSS infrastructure are obtained and maintained by contractor personnel performing duties requiring such certifications.

5.2. System Support Services

Technical support services include system architect, system administration, and database management services necessary to manage and sustain hardware infrastructure and software components utilized in the capture, storage, maintenance, electronic distribution, transformation, and editorial processes associated with product data, and to ensure system and data contingency infrastructure and operations are implemented, viable, and documented. The following is a list of major software products currently utilized for product data management and supporting processes:

Technical Data-Product Data Management (TD-PDM) - TD-PDM is a collection of subsystems with Commercial-Off-The-Shelf (COTS) and Government-Off-The-Shelf (GOTS) components based on Product Lifecycle Management (PLM) technology. These subsystems provide users worldwide with single-source access to multiple linked data sources which also support View- On-Demand (VOD) and Print-On-Demand (POD) processes. The system provides storage, management, version control, and configuration management capabilities for electronic product

PWS REVISION: 0 14

data (TOs, engineering data, et al). TD-PDM is supports over 10,200 users from the .mil and .com network. These are primarily personnel throughout the DAF community, but the user base also includes users from other Department of Defense (DoD) Services and contractor community. TD-PDM serves as the repository for digital engineering drawings and related technical data. These capabilities support DoD logistics business functions, such as maintenance, repair, procurement, and re-engineering by providing worldwide, on-demand access to digital engineering drawings and associated data. See Appendix B for a list of tools and applications used within TD-PDM.

Technical Order Authoring and Publishing (TOAP) - TOAP is a collection of COTS and GOTS components providing a complete TO content management, sustainment, and publishing environment. TOAP is the designated DAF organic TO authoring and publishing component which employs workflow-controlled process solutions for TO management and editorial workgroups. TOAP stores and manages document and content components of TOs within a dynamic database repository, tracking changes against baseline TO documents and allowing users to reuse information objects. TOAP enforces authoring and publishing compliance outlined within DAF policy. See Appendix B for a list of tools and applications used within TOAP.

Secure Technical Order Repository (STOR) - STOR is a classified system and is the overarching system title assigned to the various COTS and GOTS products utilized to provide document content management, process and management workflows, and complex data publishing capabilities for classified TOs. The STOR system also functions as the DAF repository for archive and retention of electronic copies of classified DAF TO and Time Compliance Technical Order (TCTO) documents and associated increments (e.g., changes, supplements). As such, this system is utilized to support weapon system programs throughout the DAF. See Appendix B for a list of tools and applications used within STOR.

5.3. System Sustainment

The contractor shall manage and sustain the Robins AFB product data infrastructure. This includes the identification, recording, tracking, and resolution of all problems/issues, to include documentation and cause of system downtime (whether hours or unscheduled), and maintenance of a historical database to facilitate rapid identification of common system problems and trend analysis activities. The contractor shall ensure configuration control of COTS and GOTS products, and customized tools/scripts, is maintained, employing tracking and versioning techniques necessary to allow traceability of details associated with modifications/upgrades. The contractor shall document and employ disciplined testing and implementation processes to ensure modifications are implemented with minimal impact to the user community and to prevent degradation of performance and processes.

(Exhibit A: CDRL A001, Technical Report-Study/Services, DI-MISC-80508B)

The contractor shall perform actions necessary to facilitate compliance with DoD-mandated data center consolidation and cloud computing efforts. The contractor shall perform actions necessary to foster the adoption of safe, secure cloud computing options, to include the implementation of organizational cloud computing environments, steps to achieve data center consolidation objectives, and delivery of cloud services.

(Exhibit A: CDRL A001, Technical Report-Study/Services, DI-MISC-80508B)

PWS REVISION: 0 15

The contractor shall provide for the operation and maintenance of the PDSS infrastructure, supporting development, conversion, storage, improvement, and use of product data to facilitate business and operations, and maintenance activities until capabilities and data reside in the AF-PLM solution or other enterprise level system(s), and the systems supporting those capabilities are no longer operational at Robins AFB. The contractor shall monitor and manage assigned systems to ensure a 98.5 percent monthly system availability rate (based on a 30-day month, 100 percent system uptime would equate to 720 hours) to all users. Scheduled downtime and downtime caused by external factors (such as power and network outages) shall be documented and tracked but will not be used to calculate system availability for the purposes of this performance objective. The contractor shall provide support to users from 0700 to 1700 local time.

(Exhibit A: CDRL A002, Status Report, DI-MGMT-80368A)

5.3.1. Help Desk Sustainment

Types of Help Desk services to be performed include, but are not limited to:

Configuring/managing workstations, printers, scanners, and other peripheral devices.

Tracking GFE hardware and software inventory, ensuring utilization of software licenses does not exceed the availability of valid software licenses.

Coordinating with Government personnel when Help Desk problems occur.

Documenting user requirements for reports and queries.

Reviewing user issues/requests, determining system/software impact, and ensuring timely resolution of user problems

Developing and sustaining documentation associated with PDSS implementations, programs, scripts, and other automation tools.

Providing user training. Support training development of external efforts, not just applications managed within PDSS portfolio, including but not limited to areas within LZP-managed workload and AF-PLM CloudOne solution development.

Establishing and managing user privileges and profiles.

Providing support to system users, resolving user trouble calls, and satisfying requests for assistance or information.

Management and operation of multi-tiered technical help desk environment to support systems and applications within the PDSS environment.

Providing day-to-day user and help desk support for receipt, analysis, corrective action, and tracking of trouble and/or assistance calls received from customers on systems supported.

5.3.2. Operations Sustainment

Types of Operations sustainment services to be performed include:

Installing and configuring operating system and application software packages and updates and managing system configurations.

PWS REVISION: 0 16

Defining hardware, software, and cloud computing requirements, researching potential solutions, and providing recommendations for purchases and/or upgrades to the Government Program Manager.

Tracking requirements associated with, and providing cost estimates for, maintenance of systems hardware, software, and sustainment of system support services (such as cloud computing).

Coordinating and/or executing acquisition of required maintenance agreements in a manner preventing lapse/gaps in maintenance coverage required for systems/processes.

Tracking server hardware and software inventory, ensuring utilization of software licenses does not exceed the availability of valid software licenses.

Reviewing all Air Force Network Operations (AFNETOPs) task orders (e.g., Time Compliance Network Orders (TCNOs), Information Assurance Vulnerability management (IAVMs), Maintenance Task Orders (MTOs), etc.), determining applicability to the Robins AFB PDSS, and implementing those found to be applicable.

Ensuring Government-mandated security measures are installed and operational on all systems to include contingency environments (e.g., virus protection, firewall, authorization policies, account management, etc.).

Coordinating with Government personnel when Operations problems occur.

Managing system security.

Performing system backups and restores.

Monitoring and tuning the operating system.

Performing system troubleshooting and point of failure isolation and determining solutions for system problems.

Minimizing system downtime, notifying and obtaining approval from the appropriate Government representative in advance of scheduled downtime, and notifying the appropriate Government representative immediately upon discovery of other restrictions to processing or system availability.

Creating, monitoring, and tuning databases utilized to support storage, product data transformation, configuration management, sustainment, and distribution.

Supporting the PDSS applications, contingency environment services, and repositories.

Identifying system problems to appropriate system points of contact and participating in actions necessary for problem resolution.

Reviewing/updating/documenting actions associated with DAF enterprise-level systems, legacy system deconstruction, and data center consolidation/migration.

Generating system and/or data reports.

5.3.3. Cybersecurity Sustainment

Coordinating with Government personnel when cybersecurity problems occur.

Verifying system security.

PWS REVISION: 0 17

Maintaining continuous monitoring capabilities including: updating system documentation and artifacts; maintaining comprehensive hardware and software asset inventories; analyzing vulnerability scan reports; managing Plans of Action and Milestones (POA&Ms); completing Security Technical Implementation Guide (STIG) checklists in accordance with applicable standards and requirements; conducting audit log reviews and analysis; and performing audits of security-related tasks and controls to ensure compliance with established security policies and procedures.

Gathering and input of data and development of documentation necessary to ensure satisfaction of requirements driven by Configuration Control Board (CCB), portfolio management (via Information Technology Investment Portfolio (ITIPS), certification/authorization and accreditation (via Enterprise Mission Assurance Support Services (eMASS) and/or other designated systems), and National Defense Authorization Act requirements and mandates.

5.3.4. Development sustainment

Configuring, documenting, testing, and implementing new or updated software applications utilized to support technical data processes

Conducting compatibility testing to ensure continued operation of required product data applications on DAF standard desktop configuration releases.

Performing software application testing and completing required documentation for submission of required PDSS applications to the DAF Evaluated Products List (EPL) program office for subsequent evaluation/approval.

Coordinating with Government personnel when development problems occur.

Developing and sustaining documentation associated with PDSS implementations, programs, scripts, and other automation tools.

Performing system integration support.

Web design and delivery of electronic data.

Developing processes supporting product data transformation, management, sustainment, and distribution.

Developing and sustaining of tracking applications and other electronic inventory and auditing systems.

Assisting the Government in data input/integrity, quality assurance, and data migration processes.

Participating in testing, scanning and implementation of new software releases.

Developing and executing plans and actions necessary to facilitate DAF enterprise-level system (e.g., ETIMS, TOAP, and solutions resulting from the DAF Logistics Capability Initiatives) implementation/data migration.

Providing support services necessary for sustainment of hardware and software utilized in product data capture, conversion, and clean-up, and scanning operations.

Providing support services for hardware and software utilized in product data quality assurance operations.

PWS REVISION: 0 18

Providing technical system and database support services necessary for successful system operation.

Providing the skills necessary to establish and maintain web-based access to, and for execution of queries and retrieval of product data from within supported systems and integrated third party commercial repositories. Supporting system implementations in both unclassified and classified environments.

5.4. Software Licensing/Testing

The contractor shall maintain and track all Government-owned software license documentation and media for non-standard software utilized within the PDSS environments, shall ensure that all software installed is utilized in accordance with appropriate license agreements, and that software managed is processed for approval and placement on the DAF EPL or within the appropriate certification/authorization and accreditation package. The contractor shall maintain and utilize a software test and evaluation enclave compliant with DAF requirements for performance of software testing. The contractor shall conduct client/server testing in accordance with the most current HQ CCC/Software and Application Certification Assessments (SACA) (or other governing authority) software certification processes and governing Air Force Instructions (e.g., AFI 17-101). The contractor shall utilize automated tools to perform software usage audits and shall provide quarterly reports to the Government outlining software utilization metrics, and status of EPL approval for COTS and GOTS software not reflected, or approaching expiration on the DAF EPL.

(Exhibit A: CDRL A001, Technical Report-Study/Services, DI-MISC-80508B)

The contractor shall be responsible for identifying, resolving, and reporting instances of usage of illegal software on assigned systems. Instances of illegal software installation shall be resolved or a waiver submitted for Government approval within 30 days of identification. The contractor shall promptly identify requirements for additional software and/or licenses to the Government Program Manager as required for new capabilities, to resolve licensing issues, and/or to ensure continued support of products under projected configurations of DAF standard desktop and server configurations.

(Exhibit A: CDRL A001, Technical Report-Study/Services, DI-MISC-80508B)

5.5. ‘Warm’ Site and System Backup Capabilities

The contractor shall be responsible for backup and restoration, as required, of both system and data files for all systems within the PDSS environment. The contractor shall develop and execute all backup-related processes necessary to ensure restoration of systems and data can be accomplished as required.

Backup processes shall include the execution of both incremental and full back up routines, with incremental routines executed daily and full back up routines executed weekly, at a minimum. Backup routines shall produce multiple copies of backup media, to allow one (1) copy of backup media to be stored on-site within provided fire-proof containers in the Building 301 classified vault and one (1) copy to be stored within a General Services Administration (GSA) approved container in a Government Program Manager designated building on Robins AFB. The Government Program Manager/COR will certify on a monthly basis 100 percent synchronization and availability of data transferred to the continuity of operations (COOP).

The contractor shall execute processes necessary for storage and retrieval of both unclassified and classified (up to and including SECRET) PDSS backup media according to the Government-approved

PWS REVISION: 0 19

rotation plan. The contractor must provide personnel appropriately authorized by the Government security manager to courier classified data in order to transport all classified backup media to/from the storage locations.

The hardware and software comprising the current COOP infrastructure is depicted in Appendix B. The contractor shall perform efforts to manage and sustain infrastructure and processes associated with support of the hardware and software required for backup of critical product data at the contingency location. These efforts shall include all actions necessary to ensure continued viability and support of hardware, software, and network connectivity; and those actions necessary for development, sustainment, and execution of plans and processes to perform data replication and periodic data synchronization processes. The contractor shall ensure critical data from the production systems at Robins AFB are replicated within the ‘warm’ site backup systems location daily such that all data for critical systems is available at the ‘warm’ site location. The contractor shall certify successful replication of data (within ‘warm’ site systems and/or on media located at the ‘warm’ site location) on a monthly basis.

(Exhibit A: CDRL A002, Status Report, DI-MGMT-80368A)

Routine administration of the system at the ‘warm’ site should typically be accomplished by contract personnel located at Robins AFB utilizing remote administration methods with synchronization of data routinely accomplished via an automated update process. Contractor personnel will be required to perform system support activities in the event of hardware failure or if network connectivity is unavailable and shall be responsible for backup of the ‘warm’ site equipment. In the event a catastrophe occurs, which results in destruction of the primary systems at Robins, contingency plans to utilize the system at the ‘warm’ site must be in place to allow the ‘warm’ site systems to be utilized for access to critical data. The contractor shall identify to the Government Program Manager the key personnel required to deploy limited system and user support activities for critical technical data systems at the ‘warm’ site location. Key personnel will be considered mission essential (reference paragraph 6.10) and shall be required to travel to and perform system and user support efforts at the ‘warm’ site location, if able, after catastrophic events.

5.6. System User Training

The contractor shall provide user training for Government and contractor employees as required by the Government Program Manager. The training shall cover general system functionality and operation, in-depth functional training based on specific user roles/responsibilities, and data maintenance/improvement operations training for those individuals responsible for data configuration, cleansing, and accuracy both internal and external to the PDSS portfolio. ‘Train the Trainer’ type training will be utilized to the extent possible to support a select group of Government and/or contract employees who may provide system support and/or initial and recurring training to system users.

(Exhibit A: CDRL A001, Technical Report-Study/Services, DI-MISC-80508B)

5.7. Production Publishing Support

The contractor shall support the production publishing tools and support processes implemented within the TOAP environment and shall facilitate automation of additional business and sustainment processes within those tools. This includes customization and configuration of systems to support the unique functions of various programs, and to insert and distribute technology improvements. Prior to

PWS REVISION: 0 20

development or insertion of new or improved processes or capabilities, the contractor shall gain approval from the Government Program Manager and shall ensure developed capabilities are fully tested and documented (to include installation and operation procedures), and that impacts to the system’s Authority to Operate (ATO) are assessed and addressed via the appropriate processes.

The contractor shall also provide support for the publication toolsets and content management system by resolving issues identified by customers via help desk ticket submission, by executing content management system schema and workflow planning and design, and by scheduling and providing toolset training for customers, to include training on utilization of Government-owned and maintained FrameMaker templates and on proper methods of tagging technical data in Standard Generalized Markup Language (SGML) in order…