PWS.docx

Performance Work Statement (PWS)

In Support of:

448 SCMW

B-2 Collaborative Forecasting

Integrator Support

3 April 2017 (V1)

Prepared By:

Mr. James Scott Wells

3001 Staff Drive, 1AD294B

424 SCMS/GUMB

Tinker AFB, OK. 73145

405-736-7608 / DSN: 336-7308

james.wells.3@us.af.mil

Revision History

Contract No: PR – FD2030-17-02545 ii

Table of Contents

ACRONYM LIST

1.0 INTRODUCTION

1.1 Purpose

The purpose of this Performance Work Statement (PWS) is to acquire B-2 OEM Collaborative Forecasting (Co-Forecasting) integrator contract support for 448 SCMW managed B-2 end items and support the development and implementation of the B-2 Co-Forecasting program. The integrator will be responsible for compiling, assembling, analyzing, and disseminating B-2 collaborative forecasting data and actions to Planning & Execution (P&E) Groups across the Wing, and coordinating semi-annual B-2 Co-Forecasting conferences with B-2 customer and supply chain stakeholders. The Co-Forecasting process will ensure that all user and supply chain stakeholder are made aware of future requirements and have the opportunity to add fidelity to the requirements and develop needed execution strategies lead time in advance of the requirement.

1.2 Scope

The scope of the tasks defined in Section 3.0 shall include B-2 end items managed within the 448 SCMW P&E groups.

1.3 Background

Supply chain performance of the B-2 enterprise continues to be impacted by the low density nature of the workload and the associated challenges of low density workload (supplier interest, repeatable processes, workload efficiencies, computation processes, etc.). The Co-Forecasting integrator function is designed to add an enterprise perspective to the supply function, by correlating and collaborating historical and future B-2 requirements with supply chain requirements and objectives. The integrator function is also designed to effectively collaborate repair spares requirements with respective stakeholders to ensure situational awareness and opportunity/commitment for the stakeholder to support future projected requirements.

2.0 REFERENCE DOCUMENTS

2.1 Government Documents

Not applicable

2.2 Other Documents

Not applicable

3.0 CONTRACTOR TASKING / REQUIREMENTS

The contractor shall support the development, implementation and ongoing execution of a B-2 collaborative forecasting process for 448 SCMW managed end items, involving B-2 users and supply chain functions and stakeholders. The Government will provide access to data and data systems necessary for the supply chain analysis and root cause analysis required herein.

3.1 Maintain B-2 Co-Forecasting Con Ops Document

The contractor shall update and maintain the B-2 Co-Forecasting Con Ops document (developed under previous contract) to reflect changes in Co-Forecasting processes, supply chain processes and lesson learned.

The co-forecasting CONOPS shall include the following topics, and shall address the processes detailed in Sections 3.2-3.4 herein

· Schedule, interrelationships, timing and integration of the co-forecasting processes

· Stakeholders roles and responsibilities

· Semi-annual time phased Co-Forecasting processes and events

· Identify all required data inputs, associated sources, validation methods and associated analyses

· Recurring products to be developed

· Recommended metrics to measure process effectiveness, support continuous process improvement, and methods to compute and track metrics

The contractor shall perform verification of co-forecasting CONOPS for the PWS 3.2-3.4 co-forecasting processes

The Con Ops documents shall be reviewed within 60 days following each Co-Forecasting conference, to include all recommended updates and processes changes, based on lessons learned from the preceding six month cycle.

Updated Co-Forecasting Con Ops shall be submitted in IAW CDRL A045.

3.2 Co-Forecasting Analysis and Requirements Collaboration

The Contractor shall collect and analyze data from PDM and Field repair and spares usage, B-2 mod schedules, along with D200, organic repair, and Buy/Repair contracts; to present projected future requirement to each respective stakeholder as part of the CoFo process. The contractor shall collect stakeholder CoFo inputs and incorporate revised requirements feedback into supply chain processes for action.

In advance of each semi-annual Co-Forecasting Conference, the contractor shall develop and disseminate the 448 SCMW B-2 end item future requirements to the respective stakeholders (P&E groups, MXWs, DLA, Field, PDM, B-2 OEM, end item OEMs, CDM, ICS, etc.). The Co-Forecasting document shall be structured to allow each stakeholder the opportunity to provide revised inputs to the projected future requirements for discussion at the CoFo conferences. End product shall also include actionable list of items to work to ensure requirements are correct and that mitigation actions are captured and resolved Contractor shall also monitor data from the various inputs to provide action items between Co-Forecasting conferences in order for the supply chain to be better aware of real-time anomalies. The contractor shall provide integrated and enterprise supportability support for multiple P&E Groups, MXW and DLA. The contractor shall support supportability evaluation, root cause and corrective action/collaboration for a large volume of 848 SCMG B-2 PDNs. Requirements Review and Depot Determination (R2D2) evaluation for the entire OC SOR workload is provided to enable supportability considerations to be utilized to meet budgetary constraints. This R2D2 evaluation is further utilized to prioritize supportability mitigation actions on both AF and DLA managed items to include supportability trending and metrics. This requirement also includes depot production logistics analysis support to improve supportability on organic repair workload in support of the PMXG, CMXG, B-2, and DSCM teams. Provides analysis on issues gathered across all the OC Co-Forecasting events with the intention of focusing on the root causes across the Supply Chain. The analysis will assist with identifying and correcting supportability gaps across the enterprise.

The contractor shall summarize status and working products developed under the PWS requirements within the Monthly Status Report, submitted IAW CDRL A039.

3.3 Semi-Annual Co-Forecasting Conference

The contractor shall organize and execute each semiannual Co-Forecasting conferences with the stakeholder community. The key stakeholders (P&E Groups, CMX, DLA PDM, SPO, Field, B-2 OEM) will meet in a single venue. Buy and repair suppliers conference participation may be electronic, virtual and/or incorporated into existing SRM and PMR formats with the suppliers. At a minimum the conference shall include a review of the designated NSNs with the stakeholders having the opportunity to provide inputs regarding the projected requirements and commitments to those requirements.

The Co-Forecasting Conference meeting agenda shall be submitted in IAW CDRL A001.

The Co-Forecasting Conference meeting minutes shall be submitted in IAW CDRL A002.

3.4 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 of the construction of schedules, financial performance tracking, 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.

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

3.4.2 Basic or Applied Research

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

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

3.4.4 Contractor’s Progress, Status, and Management Report

The Contractor shall deliver a Contractor’s Progress, Status, and Management Report (CDRL A039) in accordance with the schedule in paragraph 4.2. The Contractor shall ensure the report covers: Progress of the previous month Status of contract milestones, Resource expenditures for the project Issues/concerns and associated recommendations.

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

2.0 3.0 3.1 3.2 3.2.1 3.2.2 3.2.3 3.2.4

3.4.5 Meeting Agendas and Minutes

The Contractor shall develop and deliver meetings agendas and minutes for any meeting conducted on this EA. The Contractor shall deliver meetings agendas and minutes in accordance with the schedule in paragraph 4.2.

CDRL A001 – Conference Agenda (DI-MGMT-81249A) CDRL A002 – Conference Minutes (DI-ADMN-81250A)

3.4.6 Contract Closure Letter

The Contractor shall submit a Contract Closure Letter (CDRL A089) per DI-ADMN-80447A 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) five days after all deliverables have been accepted by the government. The Contractor shall facilitate their delivery of Contract Closure Letter.

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

4.0 PERIOD OF PERFORMANCE AND DELIVERY SCHEDULE

4.1 Period of Performance

The contract support shall include a one year basic period of performance, with four, one year options

4.2 Delivery Schedule for CDRLs

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. Deliverables due on the same date may be combined into one deliverable package as long as all CDRL requirements are met.

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

5.0 SPECIAL CONSIDERATIONS

5.1 Security

5.1.1 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 Scott Wells, 448 SCMW/LS.

5.1.2 Access to Confidential, Proprietary and/or Sensitive Information Contractor personnel may be required to access Confidential, Proprietary and/or Sensitive Information held by the USAF relating to the tasks to be performed under this Task Order. 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, Contracting Officer Representative (COR), and Contracting Officer 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 Task Order.

It should be noted that Confidential, Proprietary, and/or Sensitive Information shall not include information that the Contractor personnel or the Contractor can demonstrate:

1. was 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.

5.1.3 Security Clearance

The tasking performance requires access to classified data, a security clearance of SECRET will be required for all personnel having access to classified data. All Contractor employees shall possess appropriate security clearances to support the B-2 platform. Refer to the DD Form 254 attached to the contract for additional security instructions, guidance, policies, and restrictions.

5.1.4 Common Access Cards

For base and data system access, a Common Access Card (CAC) is required in support of this effort and the Security Clearance level is expected to be UNCLASSIFIED, 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.

In accordance with Hill AFB Instruction 36-812, Issue of Common Access Cards to Contractors (Contractor Verification System), paragraph 6.1.5. 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 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.

Refer to AFFARS clause 5352.242-9001, Common Access Cards (CAC) for Contractor Personnel, under the OASIS or stand alone basic ID/IQ contract(s) for additional instructions and procedures that apply to obtain and manage CACs under individual DESP3 task orders. One of the provisions of this clause is that the Contractor shall provide a listing of personnel who require a CAC to the Contracting Officer. For purposes of individual DESP3 task orders, in addition to the Contracting Officer the Contractor shall also submit the listing to the Program Manager and Contracting Officer Representative (COR). A sample template of the CAC listing for Contractor personnel is provided in PWS Attachment III.

5.1.5 Base or Area Badges and Access to Facilities

448SCMW/LS or the Government Program Manager will assist Contractor personnel in processing the necessary 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 448SCMW/LS at least fifteen working days prior to the need date. Control of the facilities shall remain with the Government.

5.1.6 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 or and Contractor personnel leave work on this project they will have 5 working days to terminate all their network user account and to return all access cards and base identification badges. 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.

5.2 Base Support - Government Provided Office Space

Base support is anticipated with this task order. Some work efforts shall be performed at the Contractor’s site.

5.3 Government Program and Contract Management

5.3.1 Government Program Management

448 SCMW/LS will provide the Government Program Manager for this Task Order. The Government Program Manager will provide the Contractor access to all technical data required to perform approved tasking. Only the Government Program Manager while functioning in his/her capacity as a COR has the authority to review and approve contract deliverables (see paragraph 4.3).

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

5.4 Safety Requirements

5.4.1 General Safety Requirements

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

5.5.1.2 Damage to Government Property and/or Base Support

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

5.5.1.2.1 Major Mishap

When a major mishap ($2,000 or more) involving Government property (GFE/M/P/S 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.

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

5.5 Contractor Manpower Reporting

The Contractor shall report ALL Contractor labor hours (including subcontractor labor hours) required for performance of the services provided under this contract, Reverse Engineer and Technical Data Package via a secure data collection site. The Contractor is required to completely fill in all required data fields at http://www.ecmra.mil.

Reporting inputs will be 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.

The Use 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 shall 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 CMRA link. However, user manuals for Government personnel and Contractors are available at the Army CMRA link at http://www.ecmra.mil.

6.0 TRAVEL REQUIREMENTS:

Travel may be required in support of the above requirements. The Contractor is responsible for estimating and proposing the projected travel require in support of the requirements defined in Section 3.0 herein. A summary of each trip shall be included in the applicable task Contractor’s Progress, Status, and Management 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.

6.1 Travel Anticipated

Contractor personnel may be required to travel on an “as needed basis” to support the objectives of this PWS. Travel will generally include visits to contract and/or organic suppliers to the 448 Supply Chain Management Group (SCMW).

6.2 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.)

6.3 Travel Expenses

Contractor travel policies and procedures must be best business practices IAW FAR 31.205-46. 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.205-46. The Government reserves the right to disallow unreasonable travel costs. Travel must be billed as a separate line item on all invoices.

6.4 Post-Trip Report

As part of the monthly Contractor’s Progress, Status, and Management Report (CDRL A039), upon completion of any travel, the Contractor representative shall submit a trip report. The Contractor shall facilitate their delivery of Contractor’s Progress, Status, and Management Report.

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

7.0 SERVICES SUMMARY (SS):

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

Services Summary

*Note: An error is defined as a rejected data submittal which is returned to the Contractor for rework due to non-compliance with contract requirements.

8.0 CONTRACTING OFFICER REPRESENTATIVE

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

3001 Staff Drive, 1AE1 93A

448 SCMW/LS

Tinker AFB, OK. 73145 405-736-5031 james.wells.3@us.af.mil The Contractor will be notified by letter at time of award of the Primary and Alternate CORs assigned to this task order.

9.0 CONTINUATION OF ESSENTIAL SERVICES DURING CRISIS: N/A

ATTACHMENT I -- CONTRACT DATA REQUIREMENTS LISTS (CDRLs)

DESIGN AND ENGINEERING SUPPORT PROGRAM (DESP) CONTRACTUAL ENGINEERING TASK (SOW)

Engineering Assignment

Prepared by:

3001 Staff Drive, 1AD294B

448 SCMW/LS

Tinker AFB, OK. 73145

For detailed CDRL instructions see DoD 5010.12-M See attachment 11 for DIDs Pick List

For all CDRLs use the following information

Block 3 Contractor/PR Number PR or MIPR Number

Don’t forget to include mailing address and if data is to be electronically delivered include email address.

Optional If a distribution statement is needed, enter an appropriate distribution statement; otherwise delete the following.

For distribution statement instructions see AFI-61-204

BLOCKS 9: DISTRIBUTION STATEMENT “D” Distribution authorized to Department of Defense (DoD) and DoD Contractors for administrative or operational use determined 23 July 1991. Other requests for a copy of this document shall be referred to the BLK 6 Requiring Office on the DD Form 1423 that governs this submittal.

WARNING: This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751 et seq.) or Executive Order 12470. Violations of these export laws are subject to severe criminal penalties.

The above Distribution Statement and Warning Notice shall be displayed or affixed to the data in a conspicuous position.

ATTACHMENT II – NONDISCLOSURE AGREEMENT

Engineering Assignment

3001 Staff Drive, 1AD294B

448 SCMW/LS

Tinker AFB, OK. 73145

CONTRACTOR NONDISCLOSURE AGREEMENT

DESP III Contract # __________________ DESP III Task Order # _______________________

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:

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

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

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

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

5. Any questions I have regarding this agreement that I desire to direct to the USAF shall be in writing to

[Insert name & address of USAF POC].

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

7. 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 III – COMMON ACCESS CARDS (CAC) LISTING FOR CONTRACTOR PERSONNEL

Dated: 7 April 16

3001 Staff Drive, 1AD294B

448 SMCW/LS

Tinker AFB, OK. 73145

DESP3

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:

(1) 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.

(2) 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)).

(3) 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.

(4) 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.

(5) 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.

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

image1.png