B-2 Nuclear Armament PWS.pdf

B-2 NUCLEAR ARMAMENT TECHNICAL ORDER SUPPORT PWS

Prepared By:

Douglas Wiggins

AFLCMC/WBZ

20 Sep 2022

Contents

1.0 Description of Services & Scope

1.1 SERVICES

1.1.1 Editorial Support

1.1.2 Editorial Clarifications

1.1.3 Editorial Management Formats

1.1.4 Technical Data Functions / Customer Support

2.0 Service Summary

2.1 Quality Assurance Surveillance Plan (QASP)

3.0 Government Furnished Property (GFP)

3.1 Government Furnished Information (GFI)

4.0 General Information

4.1 Security

4.1.1 Facility Clearance, Personnel Security Clearances, and Background Investigations

4.1.2 Security (Unclassified Task)

4.2 Quality

4.3 Procedure for Invoicing/Payment/Acceptance

4.4 Contractor Requirements

4.4.1 Personnel Qualifications

4.4.2 Program Management

4.4.3 Team Management

4.5 Transition Management Plan

4.6 Contractor Furnished Materials and Equipment

4.7 Non-Disclosure Requirements

4.8 Commercial Processes and Technologies

4.9 Meetings and Reviews

4.9.1 Program Management Reviews (PMR)

4.9.2 Technical Interchange Meetings (TIM)

4.9.3 Post-Award Conference

4.10 Place of Performance

4.11 Risk Management

4.12 Performance of Service During a Crisis

4.13 Inspection of Service Clause

4.14 Green Procurement Program (GPP)

4.15 Deliverables

4.15.1 Subcontractor Participation

4.15.2 Status Reports

4.15.3 Standardized Reporting

4.15.4 Contractor Manpower Reporting Requirements

4.15.5 Uses and Safeguarding of Information

4.15.6 Contract Data Requirements Lists

5.0 Appendices

1.0 Description of Services & Scope

The PWS is specific in nature and defines the requirements for the B-2 Nuclear Armament Technical Order Support.

This PWS encompasses the sustainment of Technical Orders (TO) and engineering data support services in support of Air Force Life Cycle Management Center (AFLCMC), B-2 Division (AFLCMC/WWZ). The primary location requiring support will be Tinker Air Force Base (Tinker AFB). The contractor shall provide support in the following areas: Editorial Support, Technical Data History/Record Management, TO Conference Support and Data Research (ex. Source Maintenance & Recoverability (SMR) Code, Commercial & Government Entity (Cage) Code, etc.).

Technical data services for B-2 Nuclear Armament supports the management of approximately 27 basic TOs comprising an estimated 11,000 pages and over 2,000 engineering data images total.

There will be a minimum of 2,000 text or illustration changes (which will also include a pre-publication review copy, reprint & update to tech manual indexed portable disk file (IPDF), 200 technical page development from source data (which includes reprints), 5 drawings per year & history package of technical manuals. These are the amount of changes required on an annual basis.

Special care shall be taken in regards to the security and protection of these TOs. These TOs are controlled items and designated as Air Force (AF) Nuclear Enterprise (NE) Controlled Unclassified Information (CUI) and Technical Information (TI). The contractor shall implement the specific security and handling requirements of Nuclear Enterprise (NE) Controlled Unclassified Information (CUI), as defined in Section 4.1 of this PWS.

Scope:

The contractor shall provide support for the following:

a. Text or Illustration change:

I. Text: All words, numeric’s, callouts on figures, titles, tables and other text on illustrations are text.

II. Illustration: Change to existing photographic (half-tone or color) or line drawing artwork.

III. Both text and illustration changes are based on a per-page change.

b. Pre-Publication Review Copy: Complete copy of change, TCTO, revision for review and or merged copies of changes when directed.

c. Reprint: A print of basic page size for additional or replacement copies. Consider reprints as an exception to the basic page size. In the case of reprints, all fold-ups count as one page regardless of size. For example, 3 foldouts plus 3 fold-ups equal six (6) total pages regardless of size.

d. Update Tech Manual Indexed Portable Doc File (IPDF): Indexing so user can move quickly between TO chapters, sections, figures, and tables, or move to specified words or character strings.

e. Technical Page Development from Source Data: Create TO format pages, figures, chapters, tables, IPBs, EBOMs, data supplied may be in very rough form, such as engineering notes, engineering drawings, minutes, or an AFTO Form 252. The Contractor shall draw, re-word, re-phrase, reformat or rearrange the data as required by the TO format. Contractor shall ensure they do not release any source data to include secondary release of information without written consent from PCO and controlling data official.

f. Drawings: Create 3D model drawings from source data when directed utilizing commercially available software such as, but not limited to AutoCAD, Illustrator©, CATIA©, and ISODraw.

g. History Package Development: Contractor will manage the B-2 11N T.O. basic copies and all historical change packages in digital format for the duration of contract. Contractor shall deliver historical T.O. changes within one workday when directed.

h. Provided services shall include the following requirements:

I. Text or Illustration Change, Pre-publication Review Copy, Reprints and Update Tech Manual Indexed Portable Doc File (IPDF).

II. Technical Page Development from Source Data and Reprints

III. Drawings

IV. History Package Development of technical manuals

1.1 SERVICES

1.1.1 Editorial Support

1.1.1.1 Editorial support consists of developing, editing, composing, illustrating, converting and performing quality assurance of Air Force Technical Orders, Illustrated Parts Breakdown (IPB), Supplements, Job Guides, and Work Cards in accordance with Department of Defense (DoD) and Air Force Technical Manual Specifications and Standards (TMSS).

a. Development support encompasses creation of a Technical Order from government approved source data for initial publication.

b. Editorial sustainment support encompasses updates of published TOs from government approved source data. These updates consist of changes, supplements, and revisions.

c. Composition consists of the input of government approved source data into content management systems and the creation of output files such as Indexed Portable Document Format (IPDF) or Hyper Text Markup Language (HTML) and Standard Generalized Markup Language (SGML) format from source files.

d. Illustration support consists of the update or creation of artwork from sketches, photographs, engineering drawings and/or halftone graphics.

e. Conversions involves the transition of data form a compliant or non-compliant data format to another Air Force compliant data format.

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

1.1.1.2 Contractors shall be currently proficient in their ability to author and publish TOs within Air Force and commercial content management systems and desktop publishing software’s.

Examples of such software include: FrameMaker, Interleaf, Command Publishing Suite (CPS), Content@, EPIC Editor, Adobe Acrobat, and Digital Change Management Software (DiTO).

1.1.1.3 Authoring services may include end-to-end or assigned portion of the editorial process such as supplements, changes, and revision. Required cycle times to support mission activities will be measure from contractor receipt to delivery. Required cycle times may vary and are dependent on the quantity of pages, and mission needs of individual programs.

a. 50 pages or less – within 20 calendar days from date of receipt.

b. 51 - 100 pages – within 30 calendar days from date of receipt.

c. 101 - 350 pages – within 45 calendar days from date of receipt.

d. 351 – 750 pages – within 55 calendar days from date of receipt.

e. 751 pages – As approved by the Technical Order Management Agent (TOMA), Sustainment Contracting Officer Representative (COR) or Program Manager.

1.1.1.4 The contractor shall be required to support compressed delivery cycle times as needed to support program mission requirements. Compressed cycle times will be for urgent/emergency TO changes, revisions, TCTOs and operational/safety supplements. The compressed delivery cycle times shall be directed by AFLCMC/WWZ COR or Program Manager.

Compressed cycle time shall require paper & CD T.O. delivery. Compressed cycle times are during standard business hours, Monday through Friday.

a. Urgent (changes) – ten (10) business days from date of receipt.

b. Emergency (changes) – one (1) business day from date of receipt.

1.1.1.5 The contractor shall be proficient in their ability to update, convert, and create new illustrations utilizing commercial software such as but not limited to AutoCAD©, Photoshop©, Illustrator©, CATIA©, and ISODraw. All illustrations shall be delivered and stored 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™). All CGM shall be drawn in Vector Art.

1.1.1.6 Graphics Conversion

1.1.1.6.1 The contractor shall provide support as required per Program System to develop change pages or revisions related to creation, editing, conversion and configuration management of graphics, including raster and vector, relating to technical publications. The contractor shall provide all black and white graphics output and delivered in both native and representative neutral formats. Color graphics shall use the CMYK (cyan, magenta, yellow and black) color standard. Graphics shall be de-speckled and de-skewed. Photographic reproductions shall be allowed in TOs as specified. Graphics shall be reviewed and quality checked against the original artwork, ensuring converted data accurately depicts the original artwork content.

a. When a neutral format is utilized to convert between native formats, the contractor shall ensure content and format accuracy is maintained in accordance with the original native format.

b. If illustration is degraded in any way, it shall be redrawn.

c. Broken lines shall always be redrawn and text that is filled in (bleeding) shall be retyped.

d. The art resulting from conversion processes shall have the same clarity as if it were redrawn (look as clean as original artwork).

e. All illustrations shall be developed in CGM or Web CGM native formats.

1.1.1.7 The contractor shall perform quality assurance inspections to ensure content and format accuracy of all products prior to delivery. One hundred percent (100%) content accuracy of delivered documents is required. Packages not meeting 100% content accuracy will be returned to the contractor for correction.

1.1.1.8 The contractor shall provide five (5) business day turn-around on corrections to assigned work and correct errors attributable to Contractor in any Technical Manual within sixty (60) calendar days of final delivery.

1.1.1.9 The IPDF file shall provide: Bookmark IAW MIL-STD-38784A, Search function, internal linking (paragraph, figure, and table).

1.1.1.10 Digitized TOs: The Contractor shall prepare digital TOs in graphic formats in accordance with TMSS standards as directed by the TOMA.

a. Raster Graphics - Black and White (one bit) – Tagged Information File Format (TIFF) data. The Contractor shall be permitted to compress using Comite Consultatif International Telephonique et Telegraphique (CCITT) Group 4 data.

b. Raster Graphics – Gray Scale or Color – Tagged Information File Format (TIFF) or Joint Photographic Experts Group (JPEG). The Contractor shall minimize losses from JPEG compression.

c. Vector Graphics - Computer Graphics Metafiles (CGM) – The Contractor shall deliver TOs in CGM Level 4. The Contractor shall use either the WebCGM or Air Transport Association (ATA) profiles.

1.1.1.11 The contractor shall provide Digitized TO data for all applicable digital TO programs.

The contractor shall provide TOs in accordance with (IAW) the Technical Manual Specifications and Standards (TMSS) requirements. TMSS requirements are described, in detail at:

https://techdata.wpafb.af.mil/tmss/index.html; or https://afkm.wpafb.af.mil/community/views/home.aspx?Filter=OO-LG-MC-38 The contractor shall keep up to date on the digitizing procedures and changes to the digitizing software due to specification changes or to the implementation of new Enhanced Technical Information and Management System (ETIMS) procedures. The contractor shall maintain the digitized data until the responsible TO manager requests delivery.

1.1.2 Editorial Clarifications

The following are editorial clarifications that are applicable to all sites. Due to the diversity in the Air Force, deviations may be required to support some program mission needs.

a. The contractor shall demonstrate a proficiency in American English, and a working knowledge of general style and grammar for technical documents, including an https://techdata.wpafb.af.mil/tmss/index.html https://afkm.wpafb.af.mil/community/views/home.aspx?Filter=OO-LG-MC-38 ability to edit technical content in accordance with a complex set of specific instructions and standardized best practices for multiple document formats.

b. Operational, Safety, and Routine Supplements shall be prepared in accordance with TO 00-5-3 and formatted in accordance with MIL-STD-38784.

c. Time Compliance Technical Orders (TCTOs) and TCTO Supplements shall be prepared in accordance with TO 00-5-15 and formatted in accordance with MIL-DTL- 38804.

d. Contractor shall ensure TCTOs do not conflict with any information provided on the

AFTO 873.

e. Technical order revisions require each page of the TO be captured in a content management systems native format, with the exception of blank pages.

f. Changes to page numbers only, blank pages and backup pages not undergoing content editing shall not constitute a countable or chargeable change page.

g. For the purposes of this PWS, ‘a page’ is defined as one of the printed sizes in MIL- STD-38784, Table II.

h. 8 1/2 X 11 inch, 4 x 6 inch, and 5 x 8 inch page sizes are considered basic page sizes.

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

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.

j. Deviations from source data, such as rephrasing, rearranging or recomposing technical information, are not permitted without written approval from technical content manager.

k. Editorial source data includes material supplied to the contractor for performance of editorial services. Editorial source data will be supplied for editorial services in various formats. Format examples may be electronic (including but not limited to Raster, PDF, IPDF, SGML, XML, GML, PageMaker©, FrameMaker©, AutoCAD©, CGM), Paper (Reproducible Copy, Printed Copy, Engineering Drawings, Engineering Notes), and supporting documentation (Publication Change Requests, Reference TOs, Minutes/Notes).

l. Contractor shall convert source data and IPBs to Electronic Bill of Materials (EBOM) when requested by AFLCMC/WWZ.

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

n. Concurrent source data deliveries, as well as incremental source data deliveries, along with composed files may be required.

o. The Contractor shall provide electronic editorial review copies of changes, revisions, TCTOs, supplements, data modules, illustrations or other documentation.

p. The Contractor shall ensure TCTOs do not conflict with any information provided on the AFTO Form 873.

1.1.3 Editorial Management Formats

1.1.3.1 The Air Force utilizes multiple content management systems to acquire and maintain TOs. Both Commercial Off-The-Shelf (COTS) and Air Force maintained content management systems may be used to manage and update TOs within a single program.

Conversion of TOs from a legacy format to a more desired format during editorial activity is considered common practice. Contractor shall be proficient in all legacy formats as well as current content management systems and desktop publishing software. Contractor shall be proficient in legacy data editing and composing of final change. Final change shall be provided to the program office TOMA within the specified timeframes set forth in PWS paragraph 1.1.1.3.

(NOTE: Legacy data is defined as a commercial manual with an Air Force title page and LEP. Tech order follows TMSS standards to a certain degree. Style and format are to remain consistent with original development of TO.)

a. Contractor shall be proficient working in S1000D and associated Air Force XML

Business Rules. S1000D is an international specification for technical publications utilizing a common source database

b. Contractor shall be proficient working with Standard Generalized Markup Language (SGML), Generalized Markup Language (GML) and Extensible Markup Language (XML) and Air Force Document Type Definitions (DTSs)/Format Output Specifications Instances (FOSIs) or equivalent style bundles.

c. The Contractor shall be capable of reviewing technical sources, such as AFTO Form

252s, ensuring changes incorporated into TOs and drawings are technically accurate and error free.

d. Contractor shall provide access to a system at their facility that allows the government to check electronic TO format (ex. SGML)

1.1.4 Technical Data Functions / Customer Support

Technical data functional and customer support includes services for the sustainment of technical data systems to include technical data history/record management, technical order conference support, and delivery requirements.

1.1.4.1 Technical Data History/Record Management

1.1.4.1.1 The Contractor shall maintain local servers, back up hard drives, CDs/DVDs store tapes, history folders, paper copies of each TO and or disks generated as a result of the preparation of TOs in traceable locations within Contractor facilities. The Contractor may not store any of the TOs on a server, hard drive, CD/DVD, or store tape that has other non-nuclear TOs or nuclear FMS TOs stored on it. The Contractor may not upload or store any TO copies or pages on a cloud server. All digital copies shall be maintained on local computers or servers. The contractor shall provide the following protections for AF NE CUI TI:

a. No digital distribution, digital copies or images of AF NE CUI TOs beyond the approved paper and CD versions is authorized.

b. Distribution of temporary modification technical information shall be accomplished via Public Key Infrastructure (PKI) encrypted e-mail IAW

TO 00-5-1.

c. AF NE CUI TI shall not be loaded into new or existing electronic automated information systems of record not currently in use, without the written consent of AFLCMC/WWZ (B-2 Program Office).

d. The Contractor shall not conduct technical reviews or otherwise discuss NE CUI over unclassified VTC (video teleconferencing capability) or Web conferencing (e.g. WebEx etc.). All reviews shall be conducted face-to-face.

e. Contractor will ensure that only authorized individuals have access to the data. Refer to section 4.1.

1.1.4.1.2 The Contractor shall provide moisture proof/temperature controlled facility for the storage of tapes & disks with dust and humidity control to avoid any damages to digital data, reproducible copies, positives and negatives.

a. Provide one (1) workday response for return of history folders upon request from the Government. If the history folder is not available, the Government shall be contacted with that information within one (1) work day.

b. Maintain a current electronic inventory of all history packages, digitized data, reproducible copies, Computer Generated Laser Copies, Duplicate Laser Copy, positives and negatives at all times. This inventory is constantly changing due to new data entering the inventory and old data being rescinded and deleted. The inventory shall be provided to the Government upon request.

c. At the Government’s request, the Contractor shall destroy all digital copies of all TO pages, books and files and provide proof of destruction.

1.1.4.2 Technical Order Conference Support

1.1.4.2.1 The Contractor shall provide a room (similar to a conference room) within contractor facility to support a minimum of five (5) government people & necessary contractor personnel to be available from 0800 to 1600 hours upon notification by the TO Manager, for the purpose(s) of reviewing TO changes (Approximately one (1) time per month).

1.1.4.2.2 The Contractor shall attend prepublication conferences for the development of new TOs when requested by the responsible TO Manager. Attend conferences to provide support on all technical aspects of changing, updating, reviewing, and developing data for applicable TOs. Attend conferences to provide status, issues, or progress of all changing, updating, reviewing and developing data for applicable TOs.

1.1.4.2.3 The Contractor shall provide conference minutes for the record, and distribute minutes. (DI-ADMN-81250B, CDRL A001).

1.1.4.2.4 In Process Review (IPRs): Contractor may be required to support IPR’s at

Whiteman AFB or Edwards AFB as directed by the government.

1.1.4.3 Delivery Requirements

1.1.4.3.1 The Contractor shall prepare and deliver black and white or color prepublication review copies in the quantity ordered, and/or in a digitized format, in a comparable product to a Computer Generated Laser Copy /CD/DVD-ROM. The Contractor shall provide prepublications to the responsible TO Manager by the due date specified by the timelines in this PWS. The Contractor shall return AFTO Form 252, TCTO (Interim Message or draft) with prepublication.

1.1.4.3.2 The Contractor shall provide an assembly sheet.

1.1.4.3.3 When requested by Responsible TO Manager, contractor shall provide CD and printed, fully merged, prepublication copy (color/back & white).

1.1.4.3.4 The Contractor shall provide a Portable Document Format (PDF) of the technical order on a CD.

1.1.4.3.5 The Contractor shall provide an exact listing of the files and file structured with each delivery.

1.1.4.3.6 The Contractor shall assemble the print package in the following manner from bottom to top:

a. Computer Generated Laser Copy in sequential page order (include blank pages as applicable).

b. Reproduction Assembly Sheet (original and two (2) copies).

1.1.4.3.7 The Contractor shall include the order number, AFTO Form 252 and the Contract order Package in the history package. The Contractor shall assemble the history package in the following manner:

a. Final reproducible copy.

b. One (1) copy of each AFTO Form 252.

c. Edited prepublication copy.

d. One (1) copy of Reproduction Assembly Sheet.

2.0 Service Summary

Contractor shall be responsible for meeting performance objectives and performance standards outlined below.

Government surveillance is to ensure contractor performance is effectively monitored and documented. Surveillance will measure and evaluate whether the contractor exceeds, meets, or does not meet performance standards outlined in the PWS.

a. SS Performance Objectives: Defines the desired outcomes

b. PWS Paragraph: Provides applicable reference paragraph

c. Performance Thresholds: Defines the level of service required under the contract to successfully meet the SS

Performance Objective

SS Performance Objective PWS Paragraph

Performance Threshold

The Contractor shall provide editorial support which consists of developing, editing, composing, illustrating, converting and performing quality assurance of Air Force Technical Orders (TOs) and Supplements in accordance with Department of Defense (DoD) and Air Force Technical Manual Specifications and Standards

1.1.1.1 For each respective Technical Orders (TOs) and

Supplements, not more than two (2) errors per report, with no more than 2 rewrites per package.

Upon notification. Contractor shall immediately correct within two (2) working days. An error is defined as a rejected data submittal which is returned to the contractor for rework due to non-compliance with contract requirements.

Contractor shall follow required cycle times which may vary with quantity of pages and mission needs of individual programs.

1.1.1.3 Contractor may submit up to two (2) later than

cited calendar days per each category. Required cycle times to support mission activities will be measured from contractor receipt to delivery.

Contractor shall be required to support compressed delivery cycle times as needed to support program mission requirements. Final documents shall be delivered to program specific TOMA within stated timeframes.

1.1.1.4 Required cycle times to support mission activities

will be measured from contractor receipt to delivery.

The contractor shall perform quality assurance inspections to ensure content and format accuracy of all products prior to finalized delivery. The contractor shall provide error free documents for finalized delivery.

1.1.1.7 1.1.3.1, c

Provides one hundred percent (100%) content accuracy of delivered pages. An error is defined as a rejected data submittal which is returned to the contractor for rework due to non-compliance with contract requirements.

Contractor shall submit a monthly status report 4.15.2 96% reporting accuracy. 100% on time receipt of deliverables.

The contractor shall provide electronic pdf editorial review copies (Pre-pub) of changes, revisions, supplements, data modules, illustrations or other documentation.

1.1.2, m No more than 2 rewrites per package. Upon notification, contractor shall immediately correct errors within two (2) working days.

Contractor shall be proficient in editing of all legacy formats as well as current content management systems and desktop publishing software.

Contractor shall be proficient in legacy data editing and composing of final change. Final change shall be provided to program office within specified timeframes set forth in 1.1.1.3

1.1.1.1 No more than 2 rewrites per package. Upon

notification, contractor shall immediately correct errors within two (2) working days. Final change shall be 100% accurate and error free.

Contractor shall be proficient in editing of Standard Generalized Markup Language (SGML) files and composing of final change. Final change will be provided to program office within specified timeframes set forth in 1.1.1.3

1.1.1.1 No more than 2 rewrites per package. Upon

notification, contractor shall immediately correct errors within two (2) working days. Final change shall be 100% accurate and error free.

2.1 Quality Assurance Surveillance Plan (QASP)

A QASP has been established for the surveillance of this contract.

3.0 Government Furnished Property (GFP)

All work is to be performed at the contractor’s facility. No Government furnished equipment, facilities, workstations and/or software will be provided.

3.1 Government Furnished Information (GFI)

a. All data provided by the Government to the contractor for the contractor to input and process shall remain at all times the property of the Government. Technical data incorporated and developed during the performance of this contract shall 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 the contract. The contractor shall transition the storage of all editorial products to primary and backup government managed system(s) prior to the end of the program contract or as required in meeting transition requirements.

b. The contractor may not use or disclose data provided by the Government for any purpose or in any manner not specifically authorized or required by the contract.

4.0 General Information

The Contractor shall comply with all security policies and regulatory requirements. Contractor employees shall be US Citizens and able to obtain a security clearance.

4.1 Security

The Contractor shall comply with all security policies and regulatory requirements. Contractor employees shall be US Citizens and able to obtain a security clearance.

a. The Contractor shall not divulge any information regarding files, data processing activities/functions, user identifications, passwords, or other knowledge that may be gained, to anyone who is not authorized to have access to and does not have a need to know such information. Contractor personnel shall abide by all Government rules, procedures, and standards of conduct.

b. For the purpose of these instructions, the Servicing Security Activity (SSA) is the local security organization that provides security support for all Government and contractor personnel.

c. The Contractor and subcontractors shall maintain a current and completed DD Form 2345, Military Critical Technical Data Agreement to the US Joint Certification Office (JCO) in accordance with AFI 61-

204. The DD Form 2345 shall be specific to the location the contractor plans to do the work, and if they intend to do the work at more than one location, they shall have a DD Form 2345 for each location. The contractor shall be required to show proof of a valid DD Form 2345 for the specific working location within 30 days after contract award.

d. The Contractor shall have a security plan in place for NE CUI that complies with the requirements contained in NIST Special Publication 800-171 (December 2016) Revision 1 (June 7, 2018), Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations. The contractor shall also ensure compliance with DODI 5210.83, DoD Unclassified Controlled Nuclear Information (UCNI), and with DODM 5200.01, Volume 4, DoD Information Security Program: Controlled Unclassified Information (CUI).

e. No digital distribution, digital copies or images of AF NE CUI TOs beyond the approved paper and CD versions are authorized.

f. Distribution of temporary modification technical information shall be accomplished via Public Key Infrastructure (PKI) encrypted e-mail IAW TO 00-5-1.

g. AF NE CUI TI shall not be loaded into new or existing electronic automated information systems of record not currently in use, without the written consent of AFLCMC/WWZ (B-2 Program Office).

h. The Contractor shall not conduct technical reviews or otherwise discuss NE CUI over unclassified VTC (video teleconferencing capability). All reviews shall be conducted face-to-face.

i. The Contractor shall not host data on systems that are co-located and or stored with foreign military sales.

4.1.1 Facility Clearance, Personnel Security Clearances, and Background Investigations

The contractor shall possess a facility clearance at the classification level indicated on the associated DD Form 254, Department of Defense (DoD) Contract Security Classification Specification. Each contractor requiring access to unclassified Government automated information systems will require a National Agency Check with Law and Credit (NACLC), as a minimum, in accordance with DoDM 5200.02, Procedures for the DoD Personnel Security Program. The SSA will process the necessary documentation for the contractor to obtain the necessary background investigation as specified by DoDM 5200.02 for the level of access required. Each employee requiring a background investigation for this purpose will comply with instructions furnished by the cognizant security manager and the SSA.

4.1.1.1 Contractor Identification

All contractor management staff and personnel shall clearly be identified as such at all times and from a distance. Contractor identification shall include conversations, mail, email, teleconferences, video teleconferences, faxes, and/or other electronic communication whether with government personnel, other contractor personnel, or with the public when supporting this contract where their status as contractor employees might not otherwise be apparent or where they might be mistaken for civil service employees in accordance with Federal Acquisition Regulation (FAR) 37.114 and

AFI 33-119.

4.1.1.2 Listing of Contractor Employees

The contractor shall provide an initial listing of contractor employees’ names, position titles and security clearance level to the Program Manager and the COR within thirty 30 days after contract award. The contractor shall also provide an updated listing of personnel to the Program Manager and the COR when employees affecting the work of this contract, statuses change, or position changes within ten (10) workdays.

4.1.2 Security (Unclassified Task)

4.1.2.1 General: Actual knowledge of, generation, or production of classified information is not required for performance of this contract.

4.1.2.2 Operations Security (OPSEC): The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. The Contractor shall ensure compliance with DoDD 5205.02E, DoD Manual 5205.02-M, and other applicable Government security regulations including procedures to protect classified and/or controlled unclassified information, Government projects and/or programs.

4.1.2.3 Employee Clearances: Contractor employees who need access to Government owned Automated Information Systems (AIS) will require, at minimum, a Favorable National Agency Check (NAC). Contractor personnel shall submit a Standard Form 85P, Questionnaire for Public Trust Positions, (fingerprint cards if available) to the cognizant Security Office for processing. Point of contacts for this effort will be platform designated CORs as well as Security Manager.

4.1.2.4 Security Incidents and Violations: The contractor shall immediately notify the Security Office of any actual security violation, security incident, or of any indication of a potential unauthorized disclosure or compromise of classified or sensitive but unclassified information.

4.1.2.5 Communications Security (COMSEC): The Contractor shall use only secure communications methods and/or equipment to transmit or otherwise transfer controlled unclassified information in accordance with DoD 5220.22-M and other applicable Government security regulations. Applicable Government property, including equipment, shall be safeguarded, maintained, and operated in accordance with DoD 5220.22-M and other applicable Government security regulations.

4.2 Quality

a. Quality Requirements: The Contractor shall develop and implement procedures to identify and prevent defective services. The Contractor shall develop quality control procedures addressing the areas identified in Section II of this PWS. The Contractor shall be responsible for complete quality control. The Contractor shall correct errors made by the Contractor at no expense to the Government.

The Contractor shall process requests for quality corrective actions, quality assistance and quality assurance assessment, no later than five (5) workdays after Contractor receives necessary materials

4.3 Procedure for Invoicing/Payment/Acceptance

The COR can request that data items be attached to acceptance forms through Wide Area Work Flow (WAWF) or submitted to Government personnel as spelled out in the data CDRL. To allow for payment of separately priced data items, the COR shall use WAWF for acceptance. Data CDRL will determine submittal requirements; however, both separately priced and non-separately priced items shall be accepted in WAWF in order for the line item to be closed out in the contract. Information regarding WAWF-Receipt and Acceptance is available at https://wawf.ef.mil.

4.4 Contractor Requirements

The contractor shall provide the services and supplies specified herein in accordance with the PWS.

NOTE: Contractor employees shall identify themselves as contractor personnel by introducing themselves or being introduced as contractor personnel and displaying distinguishing badges or other visible Identification for meetings with Government personnel. In addition, contractor personnel shall appropriately identify themselves as contractor employees in telephone conversations and in formal and informal written correspondence.

4.4.1 Personnel Qualifications

4.4.1.1 Upon contract award, the contractors’ priced labor categories will be incorporated as an attachment. Only those priced labor categories listed in the attachment may be used unless a waiver has been granted by the PCO.

4.4.1.2 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. 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. 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 the basic contract and this PWS. The contractor shall employ and maintain a technically trained and experienced work force.

https://wawf.ef.mil/

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

4.4.2 Program Management

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

The contractor shall also participate in Program Management Reviews (PMRs) where performance requirements and metrics will be discussed and areas for process improvement identified.

4.4.3 Team Management

a. The contractor may subcontract with other companies to establish capability to meet diverse requirements. The prime contractor shall be held fully responsible for all aspects of this contract’s performance and oversight, regardless of any arrangement between its subcontractors and vendors. Any subcontractors shall comply with all security requirements contained in section 4.1 of this PWS.

b. The Contractor shall submit a Team Management Plan in accordance with the CDRL A011, DI-MGMT-81797.

4.5 Transition Management Plan

a. To ensure a smooth changeover from an incumbent contractor to a new contractor, a transition plan is required. The contractor shall develop and provide a Transition Plan to ensure a seamless phase-in and phase-out transition. The Transition Plan shall be submitted ten (10) business days after contract award and shall be in accordance with CDRL A011, DI-MGMT-81797 and shall include at minimum the proposed approach, schedule, and validation. The contractor shall ensure services can be supported with minimal impact to cost, schedule and performance during phase-in and phase-out transition.

Contractor shall provide all equipment or software acquired, developed, or licensed to facilitate processes or meet production requirements to the Government at contract termination or completion.

The contractor shall be cooperative to ensure a smooth changeover is accomplished during the phase-in and phase-out periods.

b. Contractor Phase-In Requirements: Contractor shall begin a 30 calendar day phase-in period at award. The purpose of this phase-in period is for the Contractor to prepare to assume responsibility for all functions identified in the PWS on the full performance date. The tasks during the transition period shall include:

I. Coordination with Government Representatives

II. Conduct 100% inventory of technical data, equipment, Government property and account for classified document and materials, sensitive and or critical information.

III. Review, evaluate and transition of current support services.

IV. Transition of historic data to new contractor system.

V. Government-approved training and certification process.

VI. Complete Background investigation of personnel IAW Security requirements.

VII. Transfer of hardware warranties and software licenses (if applicable).

VIII. Transfer of all necessary technical documentation.

IX. Transfer of compiled and un-compiled Technical Order source data, (if applicable.).

X. Orientation phase and program to introduce Government personnel, programs, and users to the Contractor's team, tools, methodologies, and business processes.

XI. Transfer of Government Furnished Information (GFI).

XII. Applicable briefing and personnel in-processing procedures.

XIII. Provide plan to maintain personnel qualifications and minimize possible work delays.

c. The Contractor Shall submit applications to obtain security clearance(s) for Common Access Card(s) (CAC) for the newly hired employee(s), ensuring that all employee training requirements are completed, and finalizing quality control plans and procedures. To avoid delays in starting work, it is imperative that the contractor, at the earliest possible time after contract award, be proactive in submitting applications for personnel security clearances. At the completion of the phase-in period, Contractor shall be fully capable of providing all services outlined in the PWS.

d. Phase-in Joint Property Inventory: The Contractor shall complete the phase-in joint inventory prior to the start of the first performance period. The Contractor and a Government Representative (identified by the PCO) shall conduct a joint inventory of all GFP (if applicable).

During the joint inventory, the Contractor and the Government Representative shall jointly determine the condition of all equipment. The Contractor shall document the condition of all equipment listed. The Contractor shall notify the PCO in writing upon completion of the joint inventory of all missing or unsuitable GFP. Joint inventory shall include the incumbent and follow on Contractor plus Government Representatives.

e. Contractor Phase-out Requirements: The Contractor shall provide a plan for 45-days of outgoing transition for transitioning work from an active contract to a follow-on contract/order or Government entity. This transition may be to a Government entity, another Contractor or to the incumbent contractor under a new contract/order. In accordance with the Government-approved plan, the Contractor shall assist the Government in planning and implementing a complete transition from this Contract to a successful provider. The Contractor shall collaborate with the Government to develop and deliver an Outgoing Transition Plan within thirty (30) days after contract award to PCO for approval. The Contractor shall ensure the following phase-out requirements are accomplished within forty-five (45) calendar days prior to contract end date.

I. The Government designates a 45-day transition period for the incoming Contractor to coordinate and work with the incumbent Contractor. This transition plan shall include formal coordination with Government staff and successor staff and management. It shall include delivery of copies of existing policies and procedures, and delivery of required metrics and statistics. This Outgoing Transition Plan shall include, but is not limited to:

i. Coordination with Government Representatives.

ii. Conduct 100% inventory of technical data, equipment, and account for classified documents and materials, sensitive and or critical information.

iii. Review, evaluation and transition of current support services.

iv. Transition of historic data to new contractor system.

v. Government-approved training and certification process.

vi. Transfer of hardware warranties and software licenses (if applicable).

vii. Transfer of all necessary technical documentation to approved government storage facility or contractor facility IAW Government Representative Guidelines.

viii. Transfer of compiled and un-compiled source data, to include all versions, maintenance updates and patches (if applicable).

ix. Orientation phase and program to introduce Government personnel, programs, and users to the Contractor's team, tools, methodologies, and business processes.

x. Transfer GFI.

xi. Applicable debriefing and personnel out-processing procedures.

xii. Coordinate with the Government to account for government passes, ID and access cards.

II. The Contractor shall cooperate fully to permit an orderly changeover of the workload.

III. Allow all follow-on Contractor and Government personnel access on a non-interference basis, to observe workflow to include work in-progress, reporting, priorities, forms, documents, scheduling, storage, safety, security, and quality control procedures.

f. Phase-out Joint Inventory: The Contractor shall repair or maintain all property in a serviceable condition before the final joint inventory is made. All repairs or maintenance not performed by the Contractor shall be done at the Government’s option and at the Contractor’s expense. The Contractor shall participate and complete the phase-out joint inventory prior to the end of the last performance period (if applicable). The Contractor and the Government Representative (identified by the PCO) shall conduct a joint inventory of all Government property. During the joint inventory, the Contractor and the Government Representative shall jointly determine the condition of all property and complete the final inventory of classified & unclassified documents and materials. The Contractor shall document the condition of all Government property and notify the PCO in writing within five (5) working days of completion of the joint inventory. Joint inventory shall include the incumbent, follow-on Contractor, plus Government Representatives.

4.6 Contractor Furnished Materials and Equipment

The Contractor shall acquire/procure at contractor’s expense, any additional hardware and software not provided by the Government as required to accomplish the tasks listed in the PWS.

4.7 Non-Disclosure Requirements

a. Contractor personnel will be exposed to sensitive information and shall comply with all applicable safeguarding and handling requirements.

b. During the performance of this contract, contractor personnel may be required to access or come into contact with proprietary information or source sensitive Government information. Contractor personnel shall not use such information for any purpose other than for the performance of this contract. The contractor shall not release or remove system documentation, data, or reports generated by or through use of any Government systems. All requests for information shall be forwarded to the PCO.

c. Contract personnel shall act as trusted agents during the performance of this contract; therefore:

I. The performance chain for contract personnel assigned to support requirements of this PWS will not fall under their company’s Business Development or Proposal Management organizational structures.

II. Contractor personnel assigned to support requirements of this PWS will not divulge any competition sensitive Government information.

4.8 Commercial Processes and Technologies

The contractor shall apply commercially acceptable processes and technologies, as appropriate, in accordance with the following paragraphs: 1.1.1 and 1.1.2

4.9 Meetings and Reviews

4.9.1 Program Management Reviews (PMR)

The Contractor shall participate in PMR’s on a quarterly basis. PMR’s will be conducted by either telecom or Video Teleconference if available.

4.9.2 Technical Interchange Meetings (TIM)

The Contractor shall participate in TIMs on an as needed basis. TIM’s will be conducted by telecom or Video Teleconference if available.

4.9.3 Post-Award Conference

The Contractor shall host a Post-Award Orientation Conference for contract awardees at a contractor designated facility within 60 calendar days of contract award. All key contract participants (Government and each contractor) shall attend. The contractor will notify government of the specific date, location, and agenda within 30 calendar days after contract award.

4.10 Place of Performance

The Contractor shall provide off-site hosting/storage services for TOs belonging to AFLCMC/WWZ to facilitate Technical Information Exchange meetings requiring access to the contractor’s editors, illustrators, quality assurance specialists with source data and historical files being readily available. In addition, Face-to-Face conferences not to exceed 12 per year, to discuss acquisition and sustainment requirements for technical order projects.

4.11 Risk Management

The PCO or Program Manager reserve the right to request a risk mitigation plan for mitigating major risks identified in this contract. The plan shall outline the major risks to executing the proposed program concept and the contract’s proposed mitigation strategy.

4.12 Performance of Service During a Crisis

The Functional Commander/Director has determined, by placing in writing their decision, that this requirement is not Mission Essential (M-E) in accordance with Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.237-7023, Continuation of Essential Contractor Services.

4.13 Inspection…