PWS DRAFT for SSS - API Data Cleanse 15Apr2024a.docx

One Acquisition Solution for Integrated Services (OASIS) Performance Work Statement

(PWS)

For 424 SCMS Technical Order Maintenance Parts List Validation & Applications/Programs/Indentures (API) Data Cleanse

Preparation date: 15 Apr 2024

PR: FD2030-24-01710

PREPARING ORGANIZATION: AFSC/448 SCMW/848 SCMG/424 SCMS

Tinker AFB OK 73145

Table of Contents

iii

INTRODUCTION

Purpose The purpose of this Performance Work Statement (PWS) is to define the requirements for technical analysis and problem resolution services associated with Technical Order (TO) Maintenance Parts Lists (MPL) and D200F Applications/Programs/Indentures (API) data. The services under this PWS include data verification/correction, gap analysis, API data cleansing, and actions associated with discrepancy identification and suggested corrections to applicable Illustrated Parts Breakdown (IPB) MPLs.

Scope This effort is designed to provide analysis and corrective actions for data inconsistencies between D200F (API), TOs, and source drawings. Reach-back to B-2 Original Equipment Manufacturer (OEM) data will be necessary to facilitate review and correction of deficiencies associated with D200F and the IPB MPLs. This data review is designed to provide technical support of B-2 end items originally managed by the B-2 System Program Office (SPO) that have transitioned to the 424 SCMS. The overall objective of this effort is to provide the Government with updated API data facilitating accurate indenture records within D200F system and corrected part numbers and configurations within the respective IPB MPLs.

Background The 424 SCMS maintains technical responsibly for a range of commodity end-items managed within the 848th Supply Chain Management Group. Technical responsibility, as it pertains to this PWS, includes the accuracy of transitioned IPB MPLs and D200F (API) data. Items covered under this PWS include those transferred from the B-2 SPO to the 424 SCMS as part of the end item management responsibility transfer. D200F data was created from data originally sourced from the D220 provisioning database and was designed to establish an indenturing database repository. Unfortunately, updates to the D200F database have been sporadic and as such the data has not been kept current or accurate. End item support services are now required to identify and correct errors in D200F data and IPB MPLs to ensure weapon system operational safety, suitability, and effectiveness (OSS&E).

Reference Documents

Contractor Tasking / Requirements The Contractor shall provide all management and labor necessary to provide the specific 424 SCMS engineering support functions as defined by this PWS. All documentation developed or updated by contractor personnel shall become the sole property of the Government. The Contractor shall maintain access, or obtain access and the rights to access, to OEM internal data systems to retrieve relevant weapon system design data. Support shall include but not be limited to technical analysis and problem resolution reports for each of the Government end-items associated with the API data cleanse and TO IPB MPL deficiency identification for the duration of the Period of Performance. Unless otherwise specified, all time spans given are in calendar days. When a required delivery date falls on a Weekend or Holiday, the Contractor shall deliver the subject Deliverable on the next Business Day following the Weekend or Holiday.

Kickoff Meeting The Contractor shall conduct a Kickoff meeting at the Contractor’s facility in accordance with the schedule in paragraph 4.2 herein. The Contractor shall ensure the meeting shows adequate planning and preparation, to include, but not limited to a review of the following: Overall program approach and objectives (e.g., data capture, cleansing, IPB recommendations, and data deliverables); schedule and Risks; and Government and Contractor points of contact (POCs). Kickoff meeting participants shall include Government Program Management, Engineers, Equipment Specialists, and relevant Contractor team members.

CDRL A001 - Conference Agenda (DI-ADMN-81249B) CDRL A002 - Conference Minutes (DI-ADMN-81250B)

Maintenance Parts List and API Data Error Identification and Correction The contractor shall review and identify discrepancies in D200F and IPB MPL data with the workload prioritized on 424 SCMS-managed items. The Contractor shall conduct reviews/data cleansing actions on End Items as follows:

The Contractor shall continue to request/receive associated electronic files from the D200F Office at Wright-Patterson AFB, OH and capture associated drawing sets and Technical Orders to support the review/data cleansing effort. The Government reserves the right to direct changes to the end-items and/or priority of items and will work with the Contractor to ensure any directed changes are manageable within the scope and schedule of the contract.

Monthly End Item List Review Requirements The Contractor shall perform services to review an average of 3,000 424 SCMS-managed D200F line items per month (an average of 3000 per month over the PoP). At a minimum, analysis shall consist of reviewing and providing corrective actions to resolve D200F data discrepancies associated with, but not limited to, indenture level and part number errors. The analysis process shall include a comparison between Government-provided D200F data, source drawings (CITIS, OEM Reach-back, etc.), and the associated IPB MPL. Disparities (identified as a disconnect) between the three sources of data shall be resolved through corrected API data, IPB MPL change requests, and/or Engineering Change Order recommendations as appropriate. If source drawings are identified as being incorrect, the disparities/resolutions between the D200F and the source drawings shall be confirmed with government engineering via electronic file. D200F disparities shall be corrected by the Contractor’s delivery of an electronic upload file. This file will allow the COR to provide the D200F Office of Primary Responsibility (OPR) with a means to batch upload corrected API data. For applicable technical orders, IPB MPL’s shall be compared against updated D200F data and source drawings. IPB MPL discrepancy correction shall be facilitated by the delivery of AFTO Forms 22 data (delivered in a Portable Document Format (pdf) file).

Subject AFTO Forms 22 shall be delivered with “Initiator” Blocks 6-7, 10-20, and 28 (if needed) filled in and Block 8 shall be digitally signed. TO 00-5-1, Air Force Technical Order System (ATOS) can provide additional guidance as necessary.

Show source drawing disparities/resolution (other than obsolescence notes annotated in the Technical Order Change Request via electronic file / TOCR) will be confirmed with the government by thorough explanation and request for validation through initiation of AFMC Form 202 "Nonconforming Technical Assistance Request and Reply".

The contractor shall indicate those component piece parts that are HCI on each end item. The Government will maintain responsibility for all re-cataloging actions. The Contractor shall leverage reach-back capabilities to OEM resources as necessary to identify drawings that facilitate correction of API data errors and provide corrective action recommendations for IPB MPL’s.

Task assignments under this requirement shall address gaps in Government data associated with inaccurate API indentures and IPB MPLs.

Subject Matter Expertise (SME) shall be provided by the Contractor to conduct comparison/validation of D200F API data and IPB MPLs.

The contractor shall deliver each API data set in electronic files compatible with D200F database upload formatting. The contractor shall support the D200F OPR as needed to ensure accurate and effective upload of each API file set.

CDRL A011, IPB MPL Configuration Audit Summary Report (DI-SESS-81022D) CDRL A011, D200F Configuration Audit Summary Report (DI-SESS-81022D)

Monthly Status Report The Contractor shall develop and deliver a Monthly Status Report (MSR) that provides the following summaries:

· The number of D200F line items review for the month and a cumulative total to date.

· Line items reviewed to date showing the following data elements for each:

· Priority (Based on paragraph 3.2 above)

· Status (Complete or On Hold)

· End Item Part Number (the “Parent” part number from which line items are indented)

· Description (the name or Nomenclature of the end item)

· National Stock Number (NSN)

· Date D200F Data received from Government (the date the data was received by the Contractor)

· Date of TO Change (the date show in the bottom right corner of the title page)

· Total Parts (total number of line items under the End Item (“Parent”) part number)

· Parts Reviewed (of the Total Parts)

· Parts Added (Total number of parts added under the End Item)

· TO Change Request (Number of associated TO Changes requested for the End Item)

· Number of Disconnects Identified (the number of disconnects between pulled D200F data and the source control data)

· Tasking’s Created (Gaps in Government data associated with API and IPB MPL errors)

· End Item part number list of AFTO Forms 22 data submitted for the month.

· End Item list (by National Item Identification Number (NIIN)) of parts requiring a change in the D200F system.

· Significant changes to the Contractor’s organization

· Significant activities delivered during the month.

· An updated schedule with projected deliveries during the Period of Performance

· Risk Management data.

· Issues/Problems/Recommended Solutions

CDRL A039 - Contractor’s Progress, Status, and Management Report (DI-MGMT-80227)

Program Management The Contractor shall provide program management to ensure planning, scheduling, control, and performance of requirements. Program management may include conducting management reviews with the Government for the construction of schedules, audits, spend plans, and periodic project status reviews to assure all products and services are accomplished and delivered per the specific requirements. The Contractor shall track and evaluate for compliance with cost, schedule, and performance requirements utilizing the Contractor hosted SharePoint site (Government accessible), or equivalent. The Contractor shall provide for, via SharePoint or secure website, the integration, integrity, and availability of data to facilitate information sharing between the Contractor and the Government. The Contractor shall make the information available for reviews to assist in managing schedule, cost and performance.

Information Assurance Training and Workforce Management The Contractor shall comply with all computer and network access requirements and instructions including DoD Directive 8570.1. Information Assurance Training, Certification and Workforce Management.

Basic or Applied Research This requirement includes basic or applied research that will result in new or original works, concepts, or applications.

Professional Certifications and/or Licenses Required for Contractor Personnel It is not anticipated that Contractor personnel may be required to possess Professional Certifications and/or Licenses in support of this task.

Program Status Reviews/Technical Interchange Meetings The Contractor shall attend regular (semi-annually) program status reviews, as approved by the Government Program Manager. The purpose of these meetings shall be to brief the progress of each assigned task, and to solicit input and concurrence of work performed. The Contractor shall generate presentation materials as required to aid in the discussion of technical issues.

Meeting’s Agenda and Minutes In accordance with the schedule in paragraph 4.2 herein, the Contractor shall develop and deliver a Meeting Agenda and Minutes for any meeting held regarding this EA.

CDRL A001 - Conference Agenda (DI-ADMN-81249B) CDRL A002 - Conference Minutes (DI-ADMN-81250B)

PERIOD OF PERFORMANCE AND SCHEDULE

Period of Performance The Period of Performance (POP) for this task shall be One (1) Year basic plus three (3) option years following award.

Schedule for CDRL Deliveries and Events The following table summarizes the deliverables and their respective due dates.

No later than the 15th day of each Month (the next working day if the 15th falls on a weekend or holiday)

As each End Item is completed

Government Inspection and Acceptance of Deliverables Documentation deliverables shall be delivered in accordance with this PWS, unless otherwise specified by the Government Program Manager and Contracting Officer through a contract modification or PCO letter. The Government Program Manager while functioning in his/her capacity as a Contracting Officer Representative (COR) will have the right to reject or require correction of any deficiencies found in deliverables. In the event of rejection of any deliverable, the Government Program Manager will notify the Contractor in writing of the specific reasons why the deliverable was rejected. The Contractor shall have 30 calendar days, or as outlined in the table in section 7.0 (whichever is shorter), to correct the rejected deliverable and resubmit to the Government Program Manager for re-inspection. If no comments are provided within 30 calendar days of deliverable receipt, the deliverable will be deemed to have been accepted by the Government.

Timely Upload of Accepted D200F Data Relevant to acceptance of deliverables is ensuring a timely upload of accepted D200F data. Ideally, the shorter the timespan between when D200F data is provided to the Contractor and when it is cleansed and uploaded the better. Because the D200F system is actively used by the Government, entries and other actions in the system may be made that impact the same part number(s) being worked during any given month by the Contractor. Data that is accepted then not immediately uploaded, begins to lose value at an undefined, yet tangible rate. For this reason, accepted CDRL A011, D200F Configuration Audit Summary Report and Certification (with attached electronic file, D200F database upload) should be uploaded into the D200F System within 10 business days of acceptance by the COR.

SPECIAL CONSIDERATIONS

Security The Contractor shall provide program security in accordance with the current B-2 program security guide (SCG, SJS 30 April 2018) and complete all documentation for B-2 security clearances.

Release or Removal of Information Contractor personnel shall not release or remove system documentation, data, or reports generated by or through use of Government systems. All requests for information shall be forwarded to the Flight Chief – Supply Chain Management (424 SCMS/GUME).

Access to Confidential, Proprietary, and/or Sensitive Information Contractor personnel may be required to access Proprietary and/or Sensitive Information held by the USAF relating to the tasks to be performed under this PWS. This information may belong to other Contractors, other third parties, or the USAF. Contractor personnel shall provide a completed copy of the Nondisclosure Agreement (reference PWS Attachment II) to the Government Program Manager, COR, and CO prior to performing work that involves Confidential, Proprietary and/or Sensitive Information held by the USAF relating to the tasks to be performed under this PWS.

Proprietary and/or Sensitive Information shall not include information that the Contractor personnel or the Contractor can demonstrate:

1. as known by the Contractor personnel or the Contractor without restriction as to further disclosure when received or was developed independently by the Contractor by individuals who had no direct or indirect access to such information,

2. was obtained from a source other than the USAF, its employees, agents, or Contractors through no breach of confidence,

3. was in the public domain when received or thereafter enters the public domain through no breach of confidence by Contractor or Contractor personnel, or

4. was used or disclosed with the prior written approval of the USAF

Security Clearance

The tasking performance requires access to classified data, a security clearance of SECRET will be required for all personnel having access.to the classified data. All contractor employees shall possess the appropriate security clearances to support the B-2 platform.

Common Access Cards (CACs) For base and data system access, a CAC is required in support of this effort and the Security Clearance level of some data systems is expected to be CLASSIFIED, the following instructions shall apply. It should be noted that this process may take a minimum of four (4) weeks to complete; so, it is critical that Contractors consider these instructions before award (i.e. when preparing a proposal in response to a RFOP) and prior to changing Contractor personnel after award.

For issue of Common Access Cards to Contractors (Contractor Verification System), the Contractor must have favorable or higher adjudication based on a National Agency Check with Inquiries (NACI) or higher investigation."

Also, AFSSI 8522, Communications and Information, Chapter 3, Access to Information Systems and Networks, states:

Favorable Background Investigation. CSAs, in coordination with the security manager, will verify proper security clearance and background investigation checks (National Agency Check with written Inquiries (NACI), Single Scope Background Investigation) are submitted prior to granting a network user access to the AF-GIG.

Upon successful completion of initial Information Assurance (IA) awareness training and verification of favorable background check, the user is authorized use of the network and is granted access to authorized network resources.

Contractors shall ensure Common Access Cards (CACs) are obtained by all contract or subcontract personnel who meet one or both of the following criteria:

(1) Require logical access to Department of Defense computer networks and systems in either:

(i) the unclassified environment; or

(ii) the classified environment were authorized by governing security directives.

(2) Perform work, which requires the use of a CAC for installation entry control or physical access to facilities and buildings.

Contractor shall provide a listing of personnel who require a CAC to the Program Manager, COR, and CO. A sample template of the CAC listing for Contractor personnel is provided in PWS Attachment III. Refer to AFFARS clause 5352.242-9001, CACs for Contractor Personnel for additional information.

Base or Area Badges and Access to Facilities 424 SCMS/GUME or the Government Program Manager will assist Contractor personnel in processing the necessary Department of Defense (DoD) forms to obtain base or area badges for access to Government facilities and property. Access to Government facilities is limited. Therefore, the Contractor shall coordinate required access/usage times and dates through 424 SCMS/GUME at least fifteen working days prior to the need date. Control of the facilities shall remain with the Government.

Standards of Conduct The Contractor shall not divulge any information regarding files, data, processing activities/functions, user ID's, passwords, or other knowledge that may be gained, to anyone who is not authorized to have access to such information. Contractor personnel shall abide by all Government rules, procedures, and standard of conduct. Contractors requiring access to Government Automated Information Systems (AIS) shall have background investigations and security awareness training completed, after task order award but prior to AIS access. When the period of performance is complete and/or contractor personnel leave work on this EA, the Contractor shall ensure they terminate all network user accounts and return all access cards and base identification badges within 5 working days.

Government Furnished Property/Equipment/Material (GFP/GFE/GFM) The contractor shall identify all Government Furnished Equipment (GFE), Government Furnished Material (GFM), Government Furnished Property (GFP) and/or Government Furnished Software (GFS) in support of this task order. These items will be provided to the contractor in “as in” condition. Upon receipt/acceptance of these items, the contractor shall perform a physical inspection of the items and submit formal documentation to the Government Program Manager detailing the date items were accepted, item descriptions, quantity, model, serial number and condition.

Upon completion of the contract, all items shall be returned to the Government. If these items are not returned in their original state, a report of survey (ROS) will be completed by the Government and contractor to determine the cause for the deterioration from the good working order and/or condition of the items. At that time, Contractor Liability for Government Property shall be determined in accordance with FAR clause 52.245-1, Government Property.

Any Government furnished equipment/materials/property/software must be coordinated through the cognizant contracting officer via a properly executed loan-lease agreement between the Government and the Contractor.

Base Support – Government Provided Office Space

N/A, all work will be performed at the contractor facility for this task order.

Government Program Management 424 SCMS/GUME will provide the Government Program Manager for this PWS. The Government Program Manager will provide the Contractor access to all technical data required to perform the PWS effort. Only the Government Program Manager while functioning in his/her capacity as a Contracting Officer Representative (COR) has the authority to review and approve contract deliverables.

Government Contract Management Responsibility for contracting activities rests solely with the Government Contracting Officer. No conversation, recommendations, or direction, whether given directly by, or implied by Government personnel, that will affect the scope, schedule, or price of the program covered by this PWS, shall be acted upon by the Contractor unless specifically approved by the Government Contracting Officer.

Safety Standards The Contractor shall comply with all safety provisions, e.g., technical specifications, technical publications, Federal Occupational Safety and Health Standards (Title 29 CFR. Part 1910). If there is no applicable Occupational Safety and Health Administration (OSHA) standard, use other applicable nationally recognized sources of safety, health, and fire prevention standards referenced in the work requirements of this contract. If there is any uncertainty regarding a particular safety standard, the Contractor shall seek guidance from the Government Program Manager.

Damage to Government Property and/or Base Support The Contractor shall protect Government property (e.g., GFP) to prevent damage during the period of time the property is in the possession of the Contractor and/or being used at a Government facility (i.e. Base Support). The Contractor shall report promptly to the Government Program Manager, COR, CO and Administrative Contracting Officer (ACO) and all available facts relating to each instance of damage to Government property.

Major Mishap When a major mishap ($2,000 or more) involving Government property (GFP and/or Base Support) occurs, the Contractor shall immediately secure the accident scene and the damaged item until released by the accident investigative authority as designated by the Government Safety Office. Such release shall be accomplished by the ACO with coordination from the Government Program Manager.

Investigation If the Government elects to conduct an investigation of the accident, the Contractor shall cooperate fully and assist Government personnel until the investigation is completed. The Contractor shall include a clause in each of its subcontracts requiring subcontractor cooperation and assistance in accident reporting and investigation.

Emergency Procedures

N/A

Contractor Identification 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.

Contractor Manpower Reporting The Contractor shall report ALL Contractor labor hours (including Subcontractor labor hours) required for performance of services provided under this contract for the USAF via a secure data collection site, Service Contract Report (SCR) located at www.SAM.gov. The Contractor is required to completely fill in all required data fields at www.SAM.gov. The Contractor shall provide reporting inputs for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October* of each calendar year. Contractors may direct questions to the CMRA help desk.

*Reporting Period: Contractors are required to input data by 31 October of each year.

Uses and Safeguarding of Information: Information from the secure web site is considered to be proprietary in nature when the contract number and Contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the Contractor name and contract number associated with the data.

User Manuals: Data for Air Force service requirements must be input at the Air Force Service Contract Report (SCR) located at www.SAM.gov.

Travel

Travel is not anticipated in support of the above requirements. If travel is required, the contractor is responsible for estimating and proposing the projected travel requirements. A summary of each trip shall be included in the applicable task Monthly Status Report, within the month the travel was accomplished. Airfare for travel and per diem shall be billed IAW FAR 31.205-46. The contractor is responsible for making all necessary travel arrangements.

The Contractor shall be required to travel in support of the above requirements. The Contractor shall provide estimated/proposed/projected travel requirements in support of each of the requirements defined in Section 3 herein. A summary of each trip shall be included in the applicable CDRL A039, Contractor’s Progress, Status, and Management Report within the month the travel was accomplished. Should travel occur on or about the delivery date of the current month’s CDRL A039, Contractor’s Progress, Status, and Management Report, the contractor shall ensure the travel is captured in the next month’s report. The Contractor shall ensure Airfare for travel and per diem is billed in accordance with FAR 31.205-46. The Contractor shall be responsible for making all necessary travel arrangements.

CDRL A039, Contractor’s Progress, Status, and Management Report (DI-MGMT-80227)

Travel Anticipated

N/A

Travel Pre-Approval The Contractor is responsible for making all necessary travel arrangements. The Contractor shall obtain written approval to travel from the Government Program Manager at least five (5) working days in advance before traveling. Request for approval shall include the following:

· Date of Travel

· Event (Purpose of Travel)

· Number of Travelers

· Name and Title (Labor Category) of Travelers

· Goals and Desired Outcomes of Trip

· Why Alternate Methods are not Viable Options

· (i.e. VTC, Telecom, etc. are not options to accomplish purpose and goals of trip)

· Total Estimated Cost of Trip

· Anticipated Itinerary with Associated Estimated Costs (i.e. airfare, hotel, rental car, etc.)

Travel Expenses Contractor travel policies and procedures must be best business practices in accordance with FAR 31.20546. Contractor must use FAR 31.205-46 and the DoD Joint Travel Regulation (JTR) as a guide regarding air fares, per diem, allowances, and reimbursement of travel expenses. First class air travel is not authorized. Costs incurred must be in accordance with FAR 31.20546. The Government reserves the right to disallow unreasonable travel costs. Travel must be billed as a separate line item on all invoices.

Contract Closure Letter The Contractor shall submit a Contract Closure Letter after all deliverables have been accepted by the Government. This letter shall be submitted on vendor’s letterhead and shall be delivered to the Procurement Contracting Officer (PCO) fifteen (15) days after all deliverables have been accepted by the Government.

CDRL A089 - Contract Closure Letter (DI-ADMN-80447A) Services Summary)

The contractor shall ensure the performance objectives, performance thresholds, and support for surveillance methods are achieved as follows:

In accordance with PWS Para 4.3, the COR will provide feedback on minutes. Revised minutes shall be resubmitted within 5 business days of notice. Final minutes will be defect free at time of delivery.

Contracting Officer Representative (COR)

The overall Program Management (PM) responsibilities for this task order reside with the following office:

424 SCMS/GUME

3001 Staff Drive, 1AE1 93A Tinker AFB, OK. 73145

The Contractor will be notified by letter at time of award of the Primary and Alternate CORs assigned to this task order.

Continuation of Essential Services During Crisis:

N/A

ATTACHMENT I – CONTRACTOR NONDISCLOSURE AGREEMENT

Performance Work Statement (PWS)

15 Apr 2024

CONTRACTOR NONDISCLOSURE AGREEMENT

OASIS Contract # TBD/OASIS Task Order # TBD

I, , an employee of , (Contractor) in order to support the United States Air Force (USAF) and in consideration of the USAF granting me access to Confidential, Proprietary and/or Sensitive Information held by the USAF relating to the tasks to be performed under the Task Order, intending to be legally bound, hereby agree to the following terms and conditions:

I understand that my assignment to support the Contractor in its contractual duties under the Task Order (the “Effort”) will involve access to Confidential, Proprietary and/or Sensitive Information belonging to other Contractors, other third parties, or the USAF. The sharing of Confidential, Proprietary and/or Sensitive Information is necessary to effectively perform the mission of the USAF.

Except as expressly authorized in writing by the USAF, I agree to hold Confidential, Proprietary and/or Sensitive Information in trust and confidence and agree that it shall be used only for my performance of duties in support of the Contractor’s performance of the Effort, shall not be used for any other purpose, or disclosed to any third party outside the USAF. I agree that I shall not, except as expressly authorized in writing by the USAF, at any time during or after my performance of duties in support of the Contractor’s performance of the Effort, directly or indirectly, disclose, publish or disseminate, to any other person or entity, any Confidential, Proprietary and/or Sensitive Information I have access to by reason of my performance of duties in support of the Contractor’s performance of the Effort, nor shall I use any such Confidential, Proprietary and/or Sensitive Information for my personal use or advantage, or make it available to others not cleared for access to Confidential, Proprietary and/or Sensitive Information by the USAF or lacking a need-to-know for performance of the Effort. I will hold all Confidential, Proprietary and/or Sensitive Information I have access to by reason of my performance of duties in support of the Contractor’s performance of the Effort in confidence and use it solely for the benefit of the USAF and the performance of Effort. I shall not retain any Confidential, Proprietary and/or Sensitive Information, including written notes, photographs, sketches, models, memoranda or any tangible representation of the Confidential, Proprietary and/or Sensitive Information except as required in my performance of duties in support of the Contractor’s performance of the Effort. Without limiting the generality of the foregoing statements, I agree that Confidential, Proprietary and/or Sensitive Information shall not be released to the media, press, competing firms, individuals, or Government officials outside the USAF for any purpose. I further understand and agree that all Confidential, Proprietary and/or Sensitive Information shall be retained, disseminated, released, and destroyed in accordance with the requirements of law and applicable Department of Defense or USAF directives, regulations, instructions, policies and guidance.

All information that I receive or obtain in performance of my duties in support of the Contractor’s performance of the Effort shall be deemed to be Confidential, Proprietary and/or Sensitive Information, including, without limitation, visual, verbal and written information, in whatever form or medium, including, but not limited to, personal, business or financial information, or intellectual property, or technical information in the form of discussions, communications, designs, concepts, requirements, specifications, software, interfaces, components, processes, or similar things. I understand and agree that any work product related to the Effort, including, but not limited to, final documents and products, drafts, feeder documents, briefings, notes, and any other related oral or written communication shall constitute Confidential, Proprietary and/or Sensitive Information for purposes of this Agreement. Confidential, Proprietary and/or Sensitive Information shall not include information that I or the Contractor can demonstrate (A) was known by me or the Contractor without restriction as to further disclosure when received or was developed independently by the Contractor by individuals who had no direct or indirect access to such information, (B) was obtained from a source other than the USAF, its employees, agents, or Contractors through no breach of confidence, (C) was in the public domain when received or thereafter enters the public domain through no breach of confidence by Contractor or myself, or (D) was used or disclosed with the prior written approval of the USAF.

I have been advised and understand that my violation of this agreement could cause irreparable injury to the United States. I understand that the United States Government may seek any remedy available to it to enforce this Agreement, including, but not limited to, application for a court order prohibiting disclosure of information in breach of this Agreement. I have been advised that the action can be brought against me in any of the several appropriate United States District Courts where the United States Government may elect to file the action. Court costs and reasonable attorneys’ fees incurred by the United States Government may be assessed against me if I lose such action. I understand that my violation of this Agreement may result in criminal action. I recognize that nothing in this Agreement constitutes a waiver by the United States of the right to prosecute me for any statutory violation.

Any questions I have regarding this agreement that I desire to direct to the USAF shall be in writing to 424SCMS/GUME, Tinker AFB, OK 73145.

I hereby assign to the USAF all royalties, remunerations, and emoluments that have resulted, will result or may result from any disclosure, publication, or revelation of Confidential, Proprietary and/or Sensitive Information not consistent with the terms of this Agreement.

Unless and until I am released in writing by an authorized representative of the USAF, I understand that all conditions and obligations imposed upon me by this Agreement apply during the time that I am granted access to the Confidential, Proprietary and/or Sensitive Information, and at all times thereafter. Each provision of this Agreement is severable. If a court should find any provision of this Agreement to be unenforceable, all other provisions of this Agreement shall remain in full force and effect. This Agreement shall be interpreted under and in conformance with the laws of the United States.

By:______________________________Print Name:

Date:___________________

ATTACHMENT II – COMMON ACCESS CARDS (CAC) LISTING FOR CONTRACTOR PERSONNEL

Performance Work Statement (PWS)

15 Apr 2024

OASIS

COMMON ACCESS CARDS (CAC) LISTING FOR CONTRACTOR PERSONNEL

PRIME CONTRACTOR NAME: TASK ORDER (T/O) NUMBER: EST. T/O COMPLETION DATE: AS OF DATE FOR LISTING:

NOTE / INSTRUCTIONS:

Contractors shall provide a listing of personnel who require a CAC to the Government Contracting Officer, Program M anger and Contracting Officer Representative (COR). The Government will provide the Contractor instruction on how to complete the Contractor Verification System (CVS) application and then notify the Contractor when approved.

Contractor personnel shall obtain a CAC from the nearest Real Time Automated Personnel Identification Documentation System (RAPIDS) Issuing Facility (typically the local M military Personnel Flight (M PF)).

While visiting or performing work on installation(s)/location(s), Contractor personnel shall wear or prominently display the CAC as required by the governing local policy.

During the performance period of the contract, the Contractor shall:

Within 7 working days of any changes to the listing of the contract personnel authorized a CAC, provide an updated listing to the contracting officer who will provide the updated listing to the authorizing Government official.

Return CACs in accordance with local policy/directives within 7 working days of a change in status for Contractor personnel who no longer require logical or physical access.

Return CACs in accordance with local policy/directives within 7 working days following a CACs expiration date.

Report lost or stolen CACs in accordance with local policy/directives.

Within 7 working days following completion/termination of the contract, the Contractor shall return all CACs issued to their personnel to the issuing office or the location specified by local policy/directives.

Failure to comply with these requirements may result in withholding of final payment.

APPENDIX – ACRONYM/BREVITY CODE LIST

image1.emf