Draft PWS TDSSe3 FD2060-22-32378 v4.pdf

PR: FD2060-22-32378 PWS REVISION: 0 1

Performance Work Statement for

Technical Data Support Services

Enterprise Program (TDSSe3)

Purchase Request: FD2060-22-32378

Date /Month/ Year

Date QAPC signs QASP.

PR: FD2060-22-32378 PWS REVISION: 0 2

1.0 Description of Services

This Performance Work Statement (PWS) defines the requirements for the Technical Data

Support Services enterprise (TDSSe3) program, which will be henceforth referred as T3. T3 encompasses the sustainment of Technical Orders (TO) and engineering data for AF organizations such as Air Force Sustainment Center (AFSC), Air Force Nuclear Weapons Center

(AFNWC), Air Force Research Laboratory (AFRL), Air Force Test Center (AFTC), Air Force

Installation and Mission Support Center (AFIMSC), Air Force Life Cycle Management Center

(AFLCMC) and Space Force, and their Foreign Military Sales (FMS) customers.

For clarification:

a. Contractor - denotes the prime Contractor, joint venture team and/or sub-Contractor.

b. Technical Data - refers to both TOs and Engineering Data.

c. References to Air Force Instructions, Military Specifications, Preferences, Details, TOs and regulations refer to the most current release.

d. TO is equivalent to the DoD term Technical Manual as defined in TO 00-5-3.

e. This PWS defines the general scope of the contract. A new PWS defining program specific requirements will be developed for each task order.

f. TOMA denotes the Technical Order Management Agency as well the Technical Order

Management Agent as identified in TO 00-5-3.

g. Sustainment of TO and Engineering Data refers to the Contractor updating and/or formatting existing approved technical data per the program specifications. This does not require the Contractor to create/develop engineering and technical data.

1.1 Objective(s): This Performance Work Statement (PWS) describes the services required to support the TDSSe3 programs. These services include performance standards and thresholds required to meet Air Force objectives. Standard and threshold deviations will be identified within each task order. This Indefinite Delivery Indefinite Quantity (IDIQ) contract will support

Air Force, Space Force, and FMS sustainment of technical data.

1.2 Benefit to United States Air Force (USAF): This acquisition will benefit the United States

Air Force (USAF) by providing an enterprise wide, single award, Technical Data Support

Contract Vehicle that will increase program flexibility and lower program cost, by providing an efficient and reliable technical data sustainment contract avenue to award technical data sustainment services.

1.3 Background: This contract consolidates the aforementioned requirements into a single, long-term contract, that will provide improved responsiveness to the warfighter’s demands and requirements, with the goal of optimizing overall availability.

PR: FD2060-22-32378 PWS REVISION: 0 3

2.0 Services Summary Contractor shall be responsible for meeting performance objectives and performance standards outlined in the basic contract and awarded task orders.

Note: In the event of a joint venture prime Contractor, the Services Summary applies to all joint venture members.

2.1 Basic Contract Services Summary:

Performance Objective PWS

Reference

Performance Threshold

Sub-Contractor

Participation and Utilize

AbilityOne in performance of CDRL

A003 deliveries

4.11.1

4.11.2

4.2.1

4.2.2

The Contractor shall deliver a Sub-Contractor

Participation Report annually on all task orders no later than 30 days after basic contract anniversary date.

Contractor shall deliver an AbilityOne

Participation Report annually on all task orders within 30 days after basic contract anniversary date.

There shall be no more than two total rejection(s) of deliverables per contract year for the basic contract. The Government will reject a deliverable if one (1) or more technical errors or five (5) or more minor errors are found within the deliverable. There shall be no more than one rejection of any single deliverable.

There shall be no more than one (1) late submission(s) of deliverables per contract year for the basic contract.

Monthly Cost/Employee

Status Report CDRL

A002 deliverable

4.11.3

4.2.1

4.2.2

The Contractor shall provide an initial report within ten business days of contract start date.

The Contractor shall thereafter provide a monthly status report no later than the tenth of each month.

There shall be no more than two total rejection(s) of deliverables per contract year. The Government will reject a deliverable if one (1) or more technical errors or five (5) or more minor errors are found within the deliverable. There shall be no more than one rejection of any single deliverable.

There shall be no more than one (1) late submission(s) of deliverables per.

PR: FD2060-22-32378 PWS REVISION: 0 4

2.2 Task Order Services Summary: Task Orders will each have a tailored services summary addressing delivery schedule(s), performance threshold(s) and any additional performance metrics applicable for that task order. Task Orders may have multiple performance thresholds for each performance objective.

Performance Objective

PWS

Reference Performance Threshold

Provide editorial support 4.3.1 Required cycle times and quality measurements will be defined within program task orders.

Provide Technical Order

Management Agent

Support

4.3.2 Required cycle times and quality measurements will

be defined within program task orders.

Provide Technical Data

Distribution

4.3.3 Required cycle times and quality measurements

will be defined within program task orders.

Provide Technical Content Management

4.3.4 Required cycle times and quality measurements will

be defined within program task orders.

Provide TO Library Management

4.3.5 Required cycle times and quality measurements will

be defined within program task orders.

Provide Engineering Data Sustainment

4.3.6 Required cycle times and quality measurements

will be defined within program task orders.

Provide Interactive

Electronic Technical

Manual Support

4.3.7 Required cycle times and quality measurements

will be defined within program task orders.

Provide Technical Data

Functional/Customer

Support

4.3.8 Required cycle times and quality measurements

will be defined within program task orders.

Request for emergency assistance

4.5 The Contractor shall initially respond to a

request for emergency assistance within four (4) business hours. Follow-up assistance, if required, shall be provided by the suspense date acceptable to the Government.

3.0 Government Property

PR: FD2060-22-32378 PWS REVISION: 0 5

3.1 Contractor Responsibility: The Contractor shall be responsible for Government property in accordance with the Federal Acquisition Regulation (FAR) and as specified in the contract/order.

3.2 Government Property to be provided: Government Furnished Material (GFM), Government

Furnished Equipment (GFE), Government Furnished Property (GFP), Government Furnished

Software (GFS), and Government Furnished Information (GFI) may be provided to support individual task orders. In such cases, the GFP/GFE/GFM/GFS and GFI clauses of the contract will be supplemented by specific delivery and disposition instructions provided in individual task order.

a. All data provided by the Government to the Contractor for the Contractor to input and process will remain at all times the property of the Government. Technical data input and processed during the performance of task orders must at all times be maintained in a readable and readily retrievable format. Technical data received, created or edited shall be made available to the government upon request during the contract period of performance.

The Contractor shall transition the storage of all technical data to government managed system(s) prior to the end of task orders or as required in meeting transition requirements.

b. All software developed under this contract shall become the property of the government.

Therefore, source code for all systems, scripts, tools, etc., developed as part of this contract must be provided at contract completion or upon request from the government at any time during the period of performance.

c. The Contractor shall not use or disclose data provided by the Government for any purpose or in any manner not specifically authorized or required by the task order.

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.

3.3.1 On-Base Support: When on-base support is required, the Government may provide a workstation with associated equipment such as chairs, storage cabinets, telephone, and access to postal services. Computer hardware, with the minimum capabilities as defined by the Base

Network and Information Assurance Organization, may also be provided. Any local requirements and procedures for access to Government facilities and property will be specified by the

Government requirements POC for each task order.

3.3.2 Off-Base Support: When off-base support is needed; Contractor performance may be restricted to a maximum distance from the supported AF location. Performance distance restrictions will be identified within program specific task orders.

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

PR: FD2060-22-32378 PWS REVISION: 0 6

Environment (PIEE), https://piee.eb.mil, as stipulated by DFARS 252.245-7002. 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/.

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.

3.7 Material Purchases: Material purchase requirements will be specified in individual task orders. Material purchases will be reviewed by individual task order Contracting Officer

Representatives to determine validity and funding availability prior to PCO approval. This information will be reviewed to determine if material costs are allocable and acceptable.

Contractor will not incur profit/fee on material costs. Material purchases needed after Task Order issuance will be reviewed by the Administrative Contracting Officer for approval prior to purchase. No item shall be purchased which is outside the scope of this contract. The PCO is the only person with the authority to make a final determination regarding the scope of this contract.

If there is any question regarding the appropriateness of an item to be purchased, the issue shall be directed to the PCO for prompt resolution.

4.0 Technical Requirements

4.1 Period and Place of Performance

https://piee.eb.mil/ https://dodprocurementtoolbox.com/ https://piee.eb.mil/piee-landing/

PR: FD2060-22-32378 PWS REVISION: 0 7

4.1.1 Contract/Order Period of Performance: The ordering period for the basic TDSSe3 contract will encompass a single five year task ordering period with a three-year optional task ordering period. Performance of work will extend no longer than twelve months past the last awarded task order.

4.1.2 Place of Performance: Task Orders can be issued for any combination of on-base and off-base support. Contractor will support several locations across the United States. Locations will include but not be limited to: Hanscom AFB, MA; Hill AFB, UT; Kirtland AFB, NM; Peterson

AFB, CO; Robins AFB, GA; Tinker AFB, OK. Support at additional locations may be required as additional requirements are identified. Services may also require performance at the

Contractor’s Facility. Any restrictions, terms, and/or conditions of service location will be outlined in the issued Task Order PWS.

4.2 Contract Data Requirements List(s) (CDRL)

Document

Identifier

DID Title PWS

Reference(s)

A001 DI-ENVR-81840 Programmatic Environmental Safety and Health Evaluation (PESHE) Plan

5.9.2

A002 DI-MGMT-80368A Status Report 4.11.3, 4.12.1

A003 DI-MGMT-80004A Management Plan 4.11.1, 4.11.2

A004 DI-MGMT-81117 Technical/Management Work Plan 4.12.2

A005 DI-MGMT-81861A Integrated Program Management

Report

4.12.3

A006 DI-MGMT-81797 Program Management Plan 4.12.4

A007 DI-ADMN-81505 Report, Record of Meeting/Minutes 4.13

A008 DI- ADMN-81373 Presentation Materials 4.13.3

A009 DI-ADMN-81250B Conference Minutes 4.13.3

A010 Data Deliverable 4.3.7.3

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 contract year.

The Government will reject a deliverable if one or more technical errors or five 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.

PR: FD2060-22-32378 PWS REVISION: 0 8

4.2.2 Receipt of CDRL Deliverable: CDRL deliverables shall be submitted via Wide Area Work

Flow (WAWF) and submitted directly to the MFT member identified on the CDRL. There shall be no more than one late submission(s) of deliverables per quarter. 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.

4.3 Technical Data Categories: This PWS’s technical requirements are divided into eight interrelated technical data categories. Each task order award may require one, all or a combination of these technical data categories. These technical data categories are:

a. Editorial

b. TO Management Agency (TOMA) Support

c. Technical Data Distribution

d. Technical Content Management

e. TO Library Management

f. Engineering Data Sustainment

g. Interactive Electronic Technical Manual

h. Technical Data Functional/Customer

NOTE: Some categories can be independent or a sub-function of other categories. For example, Editorial and Interactive Electrical Technical Manual support can support a single set of data.

4.3.1 Editorial: Editorial support consists of developing, editing, composing, illustrating, converting, authoring and performing quality assurance of Air Force, Country Standard TOs

(CSTO) and Flight Manuals (FMs) in accordance with Department of Defense (DoD) and Air

Force Technical Manual Specifications and Standards (TMSS).

NOTE: TMSS deviations may be required by some programs. Specific TMSS deviations will be identified in program task order.

a. Developing encompasses the creation of a TO and/or Time Compliance Technical Order

(TCTO) from government approved source data for initial publication.

b. Editing encompasses the update of published TOs from government approved source data.

These updates consist of changes, supplements, and revisions.

c. Composing consists of the input of government approved source data into content management systems, such as TOAP and the creation of output files such as Indexed

Portable Document Format (IPDF) and IETMs from source files.

d. Illustrating consists of the update or creation of artwork from items such as sketches, photographs, engineering drawings and/or halftone graphics.

e. Authoring is the process of creating a document for publishing from government approved source data.

PR: FD2060-22-32378 PWS REVISION: 0 9

f. Quality Assurance is the review of a developed, converted or changed illustration, TO, supplement, revision or TCTO in order to provide adequate confidence the product optimally fulfills the requirement.

4.3.1.1 Contractor is expected to be proficient in all legacy editorial formats as well as current content management systems and desktop publishing software.

a. Contractor shall be proficient in sustainment of S1000D and utilization of associated business rules.

b. Contractor shall be proficient with various types of markup languages such as Standard

Generalized Markup Language (SGML), Generalized Markup Language (GML), eXtensible Markup Language (XML) and Air Force Document Type Definitions (DTDs).

c. Contractor shall be proficient with desktop publishing software such as but not limited to

PageMaker©, and FrameMaker©. The Contractor shall be capable of sustaining documents in desktop publishing environments.

d. Contractor shall be proficient in their ability to author and publish TOs within Air Force and commercial content management systems such as Technical Order Authoring and

Publishing (TOAP), and associated editorial tools such as Content@, EPIC Editor, Adobe

Acrobat, and Digital Change Management Software (DiTO).

4.3.1.2 The Contractor shall be proficient in their ability to update, convert, and create new illustrations utilizing commercial software such as Solidworks, AutoCAD©, Photoshop©, Illustrator©, CATIA©, Unigraphics©, CorelDraw© and ISODraw.

4.3.1.3 The Contractor shall be proficient in their ability to perform quality assurance inspections to ensure content and format accuracy of all products IAW established AF business rules and specifications. One hundred percent (100%) content accuracy of delivered documents is required.

Packages not meeting 100% content accuracy or task order format requirements will be returned to the Contractor for correction.

4.3.1.4 The Contractor shall be capable of providing subject matter expert training services for technical data software and systems used in the editorial process. Training may be for initial users as well as refresher training. Contractor shall utilize train the trainer concepts when applicable to maximize user independence.

4.3.1.4 Contractor may be required to independently conduct end-to-end editorial processes or support an integrated government/contractor editorial process.

4.3.1.5 Editorial Clarifications: Task orders awarded under TDSSe3 will inherently require adherence to the below clarifications. Any deviations will be identified in the task order.

a. The Contractor shall demonstrate a proficiency in American English, and a working knowledge of general style and grammar for technical documents, including an ability to edit technical content in accordance with a complex set of specific instructions and standardized best practices for multiple document formats.

b. A page is defined as one of the printed sizes in MIL-STD-38784.

PR: FD2060-22-32378 PWS REVISION: 0 10

c. EXAMPLE: 8 1/2 x 11 inch, 4 x 6 inch, and 5 x 8 inch page sizes are considered basic page sizes.

d. Pages shall be counted in equivalents of the basic page size for a foldout page.

e. EXAMPLE: If a TO has a page size of 8 1/2 x 11 inches and has foldout pages with a printed size of 25.5 X 11 inches, the foldout page count for contract purposes would be three pages. Foldout pages with a printed size of 8 x 8 inches in a TO with 4 x 8 inch page size would constitute two pages.

f. Changes to page numbers only, a reflowing of text, blank pages and backup pages not undergoing content editing shall not constitute as a countable change page.

g. Deviations from source data, such as rephrasing, rearranging or recomposing technical information, are not permitted without written approval from Technical Content Manager.

h. Editorial products developed under this contract will be the property of the government.

The Contractor shall transition the storage of all editorial products to government managed system(s) prior to the end of the program task order or as required in meeting transition requirements.

i. The Contractor shall provide electronic editorial review copies of changes, revisions, TCTOs, supplements, data modules, illustrations, or other documentation when requested by COR.

j. Delivered illustrations shall be in native format, in a representative neutral format, and in an output format. The native format is the commercial software format such as Illustrator© uses (.ai). The neutral format is the file format through which one native format may be converted to a different native format such as Computer Graphics Metafile (CGM) and

Drawing Interchange File (DXF™). The output format is the file format that is utilized within the TO.

4.3.2 TOMA: TOMA support includes the acquisition support, sustainment, format approval, publication review, storage and distribution of TOs and related technical data in accordance with

TOMA duties as outlined in AFPD 63-1/AFPD 20-1, AFI63-101/20-101, AFI 63-138, AFMCI 63-

10, and 00-5-series TOs.

a. Acquisition support includes TO program requirements coordination with equipment management activity representatives. TO program specific requirements will be identified and coordinated using Technical Manual Contract Requirements (TMCR), TMSS, and

Data Item Descriptions (DID) as outlined in TO 00-5-3.

b. Sustainment includes day-to-day functional support required for all other TOMA activities.

Support of this type includes functions such as TO system updates, answering customer questions, coordinating documentation, and participating in meetings as required to support program identified mission needs.

c. Format approval entails review and acceptance of editorial packages supporting electronic and paper media types, resulting from changes/revisions/supplements, modifications, acquisitions, and data conversions for compliance with appropriate specifications.

PR: FD2060-22-32378 PWS REVISION: 0 11

d. Publication reviews include reviewing and accepting source data packages, resulting from changes/revisions/supplements, modifications and acquisitions, for compliance with appropriate specification and business rules.

e. Storage entails management of paper and digital repositories required to meet user needs.

f. Distribution encompasses deployment of approved technical data for specific military systems or commodities.

4.3.2.1 The Contractor shall be knowledgeable of Air Force TO processes and systems required to update and publish TOs from approved Publication Change Request (PCR) and other source documents provided by the Technical Content Managers (TCM).

4.3.2.2 The Contractor shall be knowledgeable of the review and recommend approval of TOs and

TCTOs as prepared and/or delivered by contractors or other sources for proper writing techniques, specifications compliance, and safety applications. Additionally, contractor will be capable of ensuring that TOs and TCTOs are accurate, thoroughly detailed, and illustrated. The type of TO or TCTO review will be dependent on program needs and may include various types of reviews such as tabletop reviews, in process reviews and verification review formats. Both local and remote reviews may be required.

NOTE: Changes/revisions/supplements/new TOs may originate from Original Equipment

Manufacturer (OEM), government organic or from other Contractor maintained technical data.

4.3.2.4 The Contractor shall be responsible for maintaining configuration control of data residing in TO management systems of records, such as Enhanced Technical Information Management

System (ETIMS) and Central Technical Order Repository (CTOR) and/or other systems utilized by the government for the configuration management and sustainment of TOs.

4.3.2.5 Contractor shall populate and update TO management systems/metadata on a timely and accurate basis. Error levels should be kept to a minimum at all times and identified errors should be corrected in a timely manner.

4.3.2.6 The Contractor shall provide customer support for TO related questions and provide accurate answers/acknowledgment on TO issues surrounding customer concerns on TCTOs, TOs, editorial requirements, distribution requirements, ETIMS and any other TO related systems.

4.3.2.7 Contractor shall be responsible for creating and coordinating TO management documentation such to Technical Manual Contract Requirements (TMCR), TMSS Data Item

Descriptions (DID), Technical Order Life Cycle Management Plan (TOLCMP), Technical Order

Life Cycle Verification Plan (TOLCVP), and Comprehensive Air Force Technical Order Plan

(CAFTOP) based on mission needs.

4.3.2.8 Contractor shall be proficient in their ability to manage technical data TOMA processes and responsibilities as outlined in Unit Compliance Inspections/Unit Self Inspection (UCI/USI) checklist and other applicable Air Force standards.

PR: FD2060-22-32378 PWS REVISION: 0 12

4.3.3 Technical Data Distribution Support: Technical data distribution is the processing of One

Time Requisitions (OTRs) and Initial Distribution (ID) of changes, revisions, supplements and

TCTOs from final TOMA approval to Technical Order Distribution Office (TODO) delivery.

a. One Time Requisitions (OTRs) are one time requests for paper TOs. OTRs are processed by an interface between ETIMS and TODPS and filled by printing or shipping from warehouse stock.

b. Initial Distribution (ID) is the first time distribution of a TO or TO increment. Prior to distribution TO management system updates will be required. The Contractor shall update

TO management systems, process DD Form 843s, shipping labels and related documentation.

4.3.3.1 Contractor may be required to independently manage end-to-end distribution processes or support an integrated Government/Contractor distribution process. Processes may include items such as; reviewing and uploading TOs into TO management systems; interfiling and interlinking of TO updates; indexing of metadata; printing of mailing labels; and the coordination of print and mailing requirements with Defense Logistics Agency Document Services (DLADS).

4.3.3.2 The Contractor may be expected to perform distribution of CSTOs from their facilities.

This function requires ordering labels through SATODS, packaging and mailing to FMS TODOs.

4.3.3.3 The Contractor may be expected to perform mailing processes once documents are printed.

4.3.4 Technical Content Management Support: TCM support includes sustainment support for the verification, acquisition and modification of technical data as outlined in AFMCI 63-101, TO

00-5-1, TO 00-5-3, TO 00-5-15, and TO 00-5-19. The TCM shall provide support for the accuracy, adequacy, and classification of TO procedures, engineering data and related technical content.

a. Acquisition support includes the technical content review and coordination of technical data submitted by OEMs for new and legacy equipment. Reviews may require the coordination with responsible Operational Safety Suitability and Effectiveness (OSS&E) engineer and Subject Matter Experts (SME).

b. Modification support includes the reviewing and development of technical data content updates associated with equipment modification programs. System modifications, which drive technical data updates, commonly require In Process Reviews (IPRs) as well as verification prior to acceptance.

c. Verification includes the technical content review of preliminary technical data via tabletop reviews or hands on equipment verifications.

d. Sustainment includes day-to-day content management processes and reviews required to develop, manage and update TOs in accordance with appropriate 00-5 series TO.

4.3.4.1 Contractor shall be capable of developing and coordinating urgent and emergency technical data updates to include Interim Time Compliance Technical Orders (ITCTOs), Interim Technical

Orders (ITOs), and Rapid Action Changes (RACs) using associated electronic distribution system.

PR: FD2060-22-32378 PWS REVISION: 0 13

Cycle times in TO 00-5-3, must be adhered to; however, processes for accomplishing this requirement may vary by program.

4.3.4.2 Contractor shall be capable of reviewing technical sources, such as Change Management

(Formerly AFTO Form 22s, AFMC Form 202s, DRs, AFTO Form 252s) and Engineering Change

Orders (ECOs), ensuring changes incorporated into TOs and drawings are 100% technically accurate.

4.3.4.3 Contractor shall be capable of developing and processing Recommended Changes (RCs) and Publication Change Request (PCRs), Engineering Change Orders (ECOs), and TCTOs for review and acceptance by the responsible engineering office or assigned equipment managers.

One-hundred percent (100%) technical accuracy is required for all technical content.

4.3.4.4 Contractor shall be proficient in their ability to manage technical data TCM processes and responsibilities as it applies to, modifying and interpreting TOs, validating and verifying

TOs/TCTOs, and incorporating TCTO data into applicable TOs and drawings.

4.3.4.5 Contractor will be required to provide efficient and timely review and determination of disposition for sponsor approvals.

4.3.5 Technical Order Library Support: Technical order library support includes establishing and/or sustainment of AF TO libraries in accordance with TO 00-5-1, TO 00-5-16, AFI 21-101, and other related TO policies. This support includes the management of physical TO library inventories for digital and paper TO and non-TO technical documents. Services include but are not limited to support for Paper and non-paper TOs, Computer Program Identification Numbers

(CPINs), Commercial Off-The-Shelf (COTS) technical data, Test Requirement Documents

(TRDs), and Interactive Electronic Technical Manuals (IETMs).

a. TO library establishing includes the set-up of Technical Order Distribution Offices

(TODO) and if necessary Technical Order Distribution Accounts (TODA). Library set-up also includes populating and updating associated system accounts required to manage library. Contractor may be required to identify physical storage requirements and digital storage requirements needed to support AF mission outlined within program task orders.

b. TO library sustainment includes TODO services, charge out system management, paper posting and digital update of TO and non-TO documents. Also, if necessary, TODA administrative services.

4.3.5.1 The Contractor shall research, support, coordinate, and update content stored in multiple

Electronic Tool (eTool) applications and tech data management systems, such as ETIMS, during the establishment and sustainment of TO libraries. Contractor shall perform and document CPIN inventories to ensure reconciliation effort is accomplished in accordance with TO 00-5-1 and TO

00-5-16 timelines.

4.3.5.2 Contractor will be required to maintain both electronic and paper TOs simultaneously. The

Contractor shall post all digital and physical media changes, revisions and supplements within timelines identified in TO 00-5-1.

PR: FD2060-22-32378 PWS REVISION: 0 14

4.3.5.3 Contractor shall ensure TODO personnel as well as TO library custodians and if necessary

TODA personnel are trained in accordance with TO 00-5-1. Local training requirements will be defined within program task order. Contractor shall ensure TODO training requirements are satisfied as defined in TO 00-5-1.

4.3.6 Engineering Data Support: Engineering data support is for sustainment of engineering data to include engineering data management, drafting, 3D model development, Bill of Material

(BOM) development, CAD data processing, quality assurance, and repository services.

a. Engineering data management includes engineering data acquisition, review, change control, and sustainment support for assigned weapon system programs.

b. Engineering drafting includes generating and modifying drawings, processing Engineering

Orders (EOs), and creating and updating appropriate repository metadata.

c. 3D model development includes conversion of 2D drawings to 3D models, interpretation of loft data and updating 3D models. BOM development includes creation of product structure information for assemblies.

d. Engineering data quality assurance and repository services include final QA of digital documents and their associated index information. Repository services include capture, upload, download and output of data into both electronic and physical media.

4.3.6.1 Contractor shall be familiar with requirements for acquisition of complete, accurate, properly formatted, packaged, and delivered engineering data and Technical Data Packages

(TDPs) in support of competitive lifecycle sustainment efforts. This includes items such as providing guidance to programs regarding engineering data, participating in data calls, writing engineering data Contract Delivery Requirements Lists (CDRLs), processing DLA Form 339s, and performing engineering data In Process Reviews (IPRs) in support of competitive lifecycle sustainment efforts.

4.3.6.2 Contractor shall have a thorough knowledge of ASME Standards, AF requirements, and policies for the drafting support of EOs and ECOs. Contractor shall be capable of updating EOs, ECOs, and uploading final drawings to engineering repository to include the input of metadata.

4.3.6.3 Contractor shall be proficient in software required for 2D drawings, 3D models and dimensioned drawings. 2D CAD software, including such as AutoCAD expertise be required. 3D

CAD software such as Siemens NX, CATIA, and Solidworks, expertise may be required.

4.3.6.4 Contractor shall provide capability to create 3D models from existing 2D drawings, undimensioned drawings, actual parts, etc. Quality assurance and repository services support may include the sustainment, improvement and distribution support for engineering drawings and all associated documents such as blueprints, undimensioned drawings, Engineering Orders/Change

Orders (EOs/ECOs), standards, and specifications stored in AF engineering data repositories.

4.3.6.5 Contractor shall be capable of reviewing, performing quality assurance procedures, conversion of legacy formats to digital, upload and correcting inaccurate and missing metadata.

Contractor shall be familiar with the policies/instructions that provide guidance in the sustainment, improvement, and distribution of engineering data.

PR: FD2060-22-32378 PWS REVISION: 0 15

4.3.6.6 Contractor shall be capable of supporting FMS and weapon system Requirements Data

Sets (RDS) request.

4.3.7 Technical Data Conversion: Technical Data Conversion is the transition of legacy source data formats such as scanning of paper to PDF, transitioning FrameMaker to SGML or converting non-standard SGML to the latest TMSS formats such as those outlined in MIL-STD-3048, MIL-

STD-1808 and associated MIL-DTLs.

4.3.7.1 The Contractor shall provide TO conversion support, as identified within individual task orders. The Contractor shall utilize industry best business practices and procedures for conversions, to include automated conversion processes and tools whenever applicable.

Conversion processes shall ensure that final deliverables have no degradation to quality, and are compliant with Air Force TMSS templates, Document Type Definitions (DTDs), schemas and applicable military specifications and standards. The Government reserves the right to deviate from TMSS standards on program specific task orders, if deemed in the best interest of the Air

Force.

4.3.7.2 The Contractor shall have capability to perform scanning activities to capture bulk paper documents or as needed in support of conversion.

4.3.7.3 The Contractor shall be proficient in their ability to author technical data procedures during conversion, such as the modularization of removal and replacement procedures, operation checks, fault isolations, individual parts breakdowns and wiring schematic updates. Data reuse concepts to author data once and reference it as many times as required should be implemented to the maximum extent practical. Data shall be converted with maximum intelligence, unless defined otherwise within program specific business rules. Contractor may be required to retain traceability and accountability of converted, authored and/or replaced data.

4.3.7.4 Conversion services may include end-to-end or assigned portions of the conversion process. Contractor shall be capable of serving as conversion integrator by mentoring programs through the conversion process, developing key documents such as program management plans, quality assurance plans, Data Module Requirements List (DMRL) and Business Rules Exchange

(BREX).

4.3.7.5 The Contractor shall be capable of providing functional subject matter expertise in support of program deployment and sustainment of data. Services shall include functions such as help desk services, creation/update of training videos and user guides, coordinating information to users, tracking lessons learned as well as identifying requirements on Technical Manual Contract

Requirements (TMCRs).

4.3.7.6 All deliverables shall be non-proprietary and of an open architecture. CDRL A010, Data

Deliverable (CDRL requirement to be determined at Order level).

4.3.7.6.1 Art resulting from any conversion shall be of the same clarity or better than the original art. Art which is not clear and usable shall be redrawn.

PR: FD2060-22-32378 PWS REVISION: 0 16

4.3.7.6.2 Contractor shall utilize common symbology libraries for standard Air Force symbols verses commercial symbols and verify that all tagging structures are in compliance with applicable business rules, prior to initial deliver.

4.3.8 Technical Data Sustainment Support: Technical data sustainment support includes the management of AF wide technical data systems and processes that are integrated in the technical data categories of this contract. Contractor may be required to provide services to one or multiple programs across the AF from a single location.

4.3.8.1 Contractor shall have an understanding of the Comprehensive Air Force Technical Order

Plan (CAFTOP). Support may include the gathering and analysis of database information and the development of draft Weapon Systems Management Support (WSMS) brochures. The Contractor shall have a complete understanding of TO 00-5-3, the CAFTOP Handbook, AFI 63-101, and the

Logistics Requirements Development Process as outlined in AFMAN 63-143.

4.3.8.2 Contractor shall have a complete understanding of UCI/USI program, checklist, associated policies, and requirements for functions within this contract. Contractor may be required to conduct Staff Assistant Visits (SAVs) to ensure UCI/USI requirements are being obtained.

4.3.8.3 The Contractor shall have the ability to provide non-technical functional support services as subject matter experts for technical data management systems. Contractor may operate as a help desk, assisting customers with indexing and distribution of technical data, workflow management, as well as notifying users of system issues, and assisting users as required. The

Contractor shall also create, provide, and/or assist with training associated with functional system.

The Contractor shall also support resolution of TO process deficiencies as identified by TO program metrics and policy evaluations such as those generated by DDRs.

4.3.8.4 Other technical data functional customer support services and acceptable variations to support program mission requirements will be identified within program task orders.

4.4 Technical Data Systems: In providing technical data services, the Contractor shall utilize/interface with existing technical data systems to provide services. The Contractor shall have knowledge of system functionality and system operations to accomplish technical data task.

The following is list of systems the Contractor shall be familiar with. Additional systems may be identified within program task orders.

a. ETIMS: Enhanced Technical Information Management Systems is an automated TO management application used to establish and manage information about AF TOs, disseminate current information on available TOs, manage TO Distribution Office

(TODO) accounts for the ordering of TOs and the maintenance of TO records, and enable the viewing of electronic TOs (eTOs) online in the ETIMS connected mode and on electronic Tools (eTool) in the ETIMS disconnected mode.

b. JEDMICS: The Joint Engineering Data Management Information and Control System is a system for electronically storing DOD technical data. The primary function of JEDMICS is to maintain, and provide access to approved data required for the operation, maintenance, PR: FD2060-22-32378 PWS REVISION: 0 17 and support of AF systems.

c. Konfig-CM: is a commercial-off-the shelf Product Data Management (PDM) system.

This product provides both Electronic Document Management (EDM) and PDM functionality. Konfig-CM supports system data management, storage and retrieval within

CTOR, Computer-Aided Design (CAD), Computer-Aided Manufacturing (CAM) data management system.

d. TDM Gateway: Technical Data Management Gateway is an electronic repository of TO documents. This repository supports view-on demand requirements for authorized users worldwide. The repository also support the print-on-demand requirements, wherein TO documents are uploaded to ETIMS. In addition, CTOR provides interface between other systems such as CITOMS as a reference library application. This interface allows users to access electronic documents stored within the CTOR.

e. IPDSC: Integrated Product Data Support Center provides infrastructure and software to support product data conversion and development processes.

f. SATODS: Security Assistance Technical Order Data System is a logistics management system for security assistance TO requirements. It is used by the Security Assistance

Technical Order Program Office in accomplishing case line manager actions for a standard

USAF TO case. SATODS is used for distribution control. After making distribution, the

TO Manager enters shipping and billing information into SATODS.

g. IDM/TOAP: Integrated Data for Maintenance is a suite of publishing tools for the creation and maintenance of TOs using Standard Generalized Markup Language (SGML), Commercial off the shelf (COTS) desktop publishing, and associate graphics files. IDM is primarily an integrated set of COTS tools for the authoring, storage, management, workflow, composition, typesetting and content management. The content management capability allows an individual TO to be broken up into subcomponents which can be independently manipulated and stored in a relational database. IDM also has the capability to render both SGML and desktop published documents into eXtensible Markup Language

(XML) formats for distribution on the internet.

h. @:CONTENTA: The Contenta Content Management Repository is a Common Source

Data Base (CSDB) that supports content authored to XML standards and DTDs. Contenta provides the automation and efficiency needed to deliver content reliably, repeatedly and effectively. Contenta contains an automated workflow that can clearly distinguish work-in-process and approved or published content, and provide status throughout the editorial and publishing process. It controls access to data modules based on user roles and project status.

i. IDET: IETM Data Entry Tool is a web based database/tool that allows data development outside of an IETM database, allowing multiple vendors’ to simultaneously update. This tool capitalizes on data reuse capabilities by exporting individual task requiring update and then managing review and acceptance processes for reinsertion into the IETM database.

4.5 Request for Assistance: The Contractor shall initially respond to a request for assistance within 4 business hours. Follow-up assistance, if required, shall be provided by the suspense date acceptable to the Government.

PR: FD2060-22-32378 PWS REVISION: 0 18

4.6 Personnel Qualifications

4.6.1 The Contractor shall not employ persons on this contract if such employee is identified to the Contractor as a potential threat to the health, safety, security, and/or general wellbeing or operational mission of the installation and its population. The Contractor shall not employ any person who is an employee of the United States Government if the employment of that person would create a conflict of interest, nor shall the Contractor employ any person who is an employee of the Department of the Air Force, either military or civilian, unless such person seeks and receives approval according to the DoD 5500.7-R Joint Ethics Regulations (JER). In addition, the

Contractor shall not employ any person who is an employee of the Department of the Air Force if such employment would be contrary to the policies contained in AFI 64-106, Air Force Industrial

Labor Relations Activities. The Contractor shall be prohibited from employing off-duty CORs who are assigned any contracts/subcontracts awarded to the Contractor. All contract employees depending on particular condition, occasion or place, or job assignment shall require professional, suitable attire. All Contractor employees shall conduct themselves in a professional, courteous manner. Contractor shall supervise and control all contractor employees during performance of task orders. Contractor employees are expected to meet requirements as outlined in this PWS and the requirements of basic contract provisions and individual task order. PCO will retain capability to restrict contractor access to base when those employees fail to meet Federal Civil Service employment standards.

4.6.2 The selection, assignment, reassignment, transfer, supervision, management, and control of

Contractor employees in performance of this PWS shall be the responsibility and prerogative of the Contractor; however, the Contractor shall comply with the requirements set forth in this PWS.

The Contractor shall employ and maintain a technically trained and experienced work force compatible with the scope of work defined within this contract and any task orders.

4.7 Key Personnel: The Contractor shall make a maximum effort to retain Key personnel. Key personnel are identified as Location POCs, one overall General Manager, and one overall CO.

4.7.1 General Manager/Contracting Officer:

a. The Contractor shall establish a general manager POC for program management and one

POC for contracting, having authority and responsibility for the overall effort for all task orders. The intent of each general manager is to give the Government agencies one POC to avoid possible duplication of effort from multiple task orders.

b. The Contractor shall provide the name of any alternates who shall act for the Contractor when the single manager and/or Contracting Officer is absent and they shall be designated in writing to the Contracting Officer within five working days after contract award. The

Contractor shall provide telephone numbers of the general manager and Contracting

Officer POCs and alternate(s) where these persons may be contacted at any time. The general manager, Contracting Officer, and their alternates shall have full authority to act for the Contractor on all matters relating to operation of this contract. The Contractor shall provide a general manager who can read, write, speak, and understand English fluently.

PR: FD2060-22-32378 PWS REVISION: 0 19

4.8 Program Management: The Contractor shall be responsible for managing all aspects of the contract and awarded task orders, to include cost, schedule, performance and contract management. The Contractor shall act as the task integrator, assuring that all technical and program elements of a task order provide a fully integrated approach.

4.9 Contractor Phase-in Requirements: During the phase-in period, the new Contractor shall hire a workforce to assure satisfactory performance beginning on the contract start date. The incumbent Contractor, after coordination with COR, shall allow the new Contractor to conduct on-site interviews with employees. The new Contractor shall obtain security clearance(s) needed for

Common Access Card(s) (CAC) or Contractor badge(s) for the newly hired employee(s). The

Contractor shall ensure that all training requirements for the newly hired employee(s) are completed before the contract start date.

4.10 Contractor Phase-out Requirements: During the phase-out period, the incumbent

Contr…