Attachment_1_-_PWS_Final.docx

FA701419PXXXX

PERFORMANCE WORK STATEMENT

FOR

Air Force District of Washington UH-1N Line Operations Safety Audit

AT

JOIN BASE ANDREWS, MARYLAND

24 July 2019 Final

Contents

SECTION I…………………………………………………………………………………….4

1.0 DESCRIPTION OF SERVICES……………………………………………………..4

1.1 General………………...……………………………………………………………..4

1.2 Background………...………………………………………………………………...4

SECTION II………………...………………………………………………………………….4

2.1 Task 1…………………………………………………………………………………...4

2.2 Task 2…………………………………………………………………………………...4

2.3 Task 3 …………………………………………………………………………………..5

2.4 Task 4…………………………………………………………………………………...5

2.5 Task 5…………………………………………………………………………………...5

2.6 Task 6…………………………………………………………………………………...6

2.7 Task 7…………………………………………………………………………………...6

2.8 Task 8…………………………………………………………………………………...6

2.9 Task 9

2.10 Task 10

2.11 Task 11

2.12 Task 12

SECTION III…………………………………………………………………………………...7

3.0 SERVICE SUMMARY…………………………………………………………………7

SECTION IV 11

4.0 DELIVERABLES……………………………………………………………………….……11

4.1 Deliverables Management……….……………………………………………...……...12

4.2 Schedule…………………………………….………………………………………………...12

4.3 Other Reporting Requirements………………………………….,.……………………13

4.4 Contractor Manpower Reporting……………………………………………………………………………..……….13

5.1 GFP

5.2 Data……………………………………………………………………….……………...14

6.1 Place of Performance………………………………………………………………………

6.2 Travel 14

6.3 Hours of Work…………………………………...………………………………….14

6.4 Core Duty Hours……………………………………………...……………………..15

6.9 Security Instructions………………………………………………………………...16

SECTION VII……………………………………………………………..…..……………….19

7.0 TRAVEL……..…………………………………………………………………………...19

7.1 Contractor Travel……………………………………………………………………..19

7.2 Non-Local Travel……………………………………………………………………..19

7.3 Local Travel…………………………………………………………………………..19

7.4 Trip Reports…………………………………………………………………………..20

SECTION VIII………………….……………...……………………………………………...20

8.0 EMPLOYEES………………………………………………………………………….…20

8.1 List of Employees………………………………………………………………….…20

8.2 Contractor Professionalism…………………………………………………………...20

SECTION IX…………………………………………………………………………………..20

9.0 MISCELLANEOUS……………………………………………………………………...20

9.1 Freedom of Information Act (FOIA)………………………...……………………

9.2 For Official Use Only (FOUO)…………………………………..…………………...21

9.3 Privacy Act……………………………………………………………………………21

9.4 Records………………………………………………………………………………..21

9.5 Safety Concerns……………………………………………………………………….21

9.6 Project Policy…………………………………………………………………...…….21

9.7 Inherently Governmental Functions…………………………………………………..21

9.8 Ethics………………………………………………………………………………….21

9.9 Professional Appearance of Work Space…………………...………………………...21

9.10 Non-Personal Service…………………………………………………………...…...21

SECTION I

1.0 DESCRIPTION OF SERVICES

1.1 General. The Air Force District Washington Directorate of Safety (AFDW/SE) mission is to preserve resources through mishap prevention. In support of this goal, AFDW/SE analyzes trends to establish mishap reduction objectives, develops mishap prevention policy, and identifies opportunities for improvement. Risk Management (RM) is part of the AFDW culture and is the basis for proactive mishap reduction.

1.1.1 Scope. AFDW/SE requires contractor support for threat and error identification during crew performance and flight operations. As outlined in the Federal Aviation Administration Advisory Circular Number 120-90 dated 27 April 2006, this process, commercially referred to as a Line Operations Safety Audit (LOSA), provides a rigorous and methodical assessment of the safety strengths and weaknesses in normal flight operations of aircraft, aircrews, and ground personnel. A LOSA is a formal process that requires highly trained experienced observers to ride the jump seat or observe operations during regularly scheduled UH-1N flights to collect safety-related data on environmental conditions, operational complexity, and crew/team performance. A LOSA provides a diagnostic snapshot of strengths and weaknesses that AFDW and other major Commands (MAJCOMs) can use to bolster the “health” of its safety margins and prevent degradation. Confidential data collection and non-jeopardy assurance for crew/team members are fundamental to the LOSA process.

1.2 Background. The objective of this acquisition is to provide LOSA services that supports HQ AFDW and other MAJCOMs operating the Bell UH-1N “Iroquois” helicopter.

SECTION II

2.0 Task Descriptions. The Contractor shall provide all services, materials, supplies, equipment, and project supervision, as required in connection with this Performance Work Statement (PWS). The contractor shall provide comprehensive technical, analytical, consulting, and program support to AFDW’s rotary-wing LOSA program that includes the following:

2.1 Task 1. The contractor shall provide a Program Lead to advise and assist the AFDW LOSA Program Manager and AFDW Senior Leadership on program methodology and processes, Threat and Error Management (TEM) as it applies to military flight operations, and in-depth explanation of LOSA results for an executive level briefing.

2.2 Task 2. The contractor shall develop a customized Threat and Error Matrix (TEM) for each flight crew position (Pilot and Special Mission Aviator on the UH-1N) within 60 days of contract award. The contractor shall coordinate a workshop with Government provided Subject Matter Experts (SMEs) to develop an accurate and comprehensive Threat and Error Matrix for use in LOSA execution. The TEM shall consist of a robust list/table of defined threats to the operations/mission/tasks and potential errors based on the documented threats. The TEM is a critical component to a successful LOSA and shall be created with enough fidelity to capture necessary operational data which shall be used for trend analysis, data comparison, and safety audit recommendations. Following TEM Matrix delivery to the government, the government will conduct a TEM audit for 15 days in advance of actual observer training.

2.3 Task 3. The contractor shall conduct in-residence classroom LOSA observer training, within 30 days of completion of the TEM audit for Pilot (P) and Special Mission Aviator (SMA) at a Government-identified location that provides instruction to LOSA observers (Government personnel) on the following topics:

a. TEM concepts

b. Methodology on observing and documenting threats and errors during operations

c. Contractor provided LOSA software program

d. Writing narratives documenting the threats, errors, undesired states, crew resource management, crew/team coordination, and subjective crew/team comments and surveys

2.4 Task 4. The contractor shall provide LOSA data collection software which is adaptive to military specific Threat and Error Matrix data inputs collected from LOSA observers during LOSA execution. Software shall efficiently and methodically collect, analyze, store, and allow future search capability of the LOSA data collected. The contractor shall also provide training to necessary Government personnel on the software use and installation. The software must be compatible with government computer systems. The contractor’s LOSA database shall have an existing and substantial repository to allow for comparison of aircrew and aircraft performance to established civil airline industry data, rotary wing operations data or joint service maintenance data. This database must be capable of deriving analysis for comparison with this requirement’s LOSA observations.

2.4.1 In accordance with AFI33-210, all software planned for use or in use on the AF-GIG must be certified for placement on the Air Force Evaluated/Approved Product List. This also includes hardware devices that contain embedded software. The contractor shall provide proof of certified software within 3 months of contract award. The Contracting Officer’s Representative (COR) and LOSA Program Manager will be the point of contact and provide direction for certification.

2.5 Task 5. The contractor shall provide HQ AFDW Safety Directorate (AFDW/SE) and the AFDW LOSA Program Manager an electronic copy of the data and software to access and sort/search data for each LOSA executed. This database shall provide interoperability with commercially available database software and previous LOSA databases from other major weapon systems. HQ AFDW/SE requires software tools to perform in-depth data search queries to determine root causes of errors and perform trend analysis. The contractor shall ensure security and confidentiality of all Government data from unauthorized users and will not release any data, analysis, or reports. The contractor shall provide an electronic copy of data and software at debriefing to USAF Senior Leadership at the conclusion of the LOSA. The government will maintain the rights to this data.

2.5.1 Provide AFDW LOSA Program Manager expert advice and support after conclusion of audit analysis process to produce actionable findings and recommendations for the AFDW staff. The contractor shall provide advice and concurrence to AFDW on the review, validation and acceptance of the military observer findings and recommendations as a result of the safety audit and the contractor’s analysis until the USAF Safety Investigation Board (which will immediately follow the senior leader outbrief) is complete.

2.6 Task 6. The contractor shall establish a robust and proven process to receive observer reports directly from worldwide locations via secure and confidential electronic means directly into a server and database developed and managed by contractor at contractor expense. Confidentiality and security of raw data from the observers is a critical Government requirement to maintain the integrity and fidelity of the LOSA program and data quality. The contractor shall ensure security and confidentiality of all Government data from unauthorized users and will not release any data, analysis, or reports.

2.7 Task 7. The contractor shall conduct real-time continual review, with 100% quality control check, of all incoming observations during execution to ensure data quality is sufficient with respect to TEM principles and data gathering principles necessary for future analysis. Every observation, without exception, will be reviewed within 2 business days by the contractor for quality and completeness. If incoming observations are not of adequate quality (as determined by the contractor) to be utilized in analytic efforts, contractor will correct the observer on-the-spot via electronic communication to ensure their data collection is of adequate quality for inclusion in the final data set.

2.8 Task 8. The contractor shall conduct robust data processing and analysis of the LOSA results that includes data and observer confidentiality/de-identification processes and data quality assurance processes. Contractor must be able to compare and contrast previous LOSA data to future data collection to allow comparison, analysis, and trending.

2.9 Task 9. The contractor shall provide a team of analysts to review and analyze raw LOSA data. The team shall document and highlight strengths and weaknesses in the AFDW operations and drill-down into problem areas to find the root cause or contributing factors.

2.10 Task 10. Within 30 days of the final LOSA Observation, the contractor shall conduct data “roundtable” verification sessions for the UH-1N LOSA data. Contractor may be required to travel for roundtable sessions to a location of Government’s direction. The Government will provide SMEs to facilitate validation and review of all threats, errors, and undesired states against current published guidance and procedures. These sessions will review every recorded threat, error, and undesired state and determine if they meet definitions and the intent of government policies and guidance (i.e., Technical Order guidance and command policies and procedures defined in AFGSC/AFDW directives)

2.11 Task 11. The contractor shall thoroughly review LOSA data and deliver a comprehensive written final report, no later than 30 days after the roundtable, as required and directed by the LOSA Program Manager that includes at a minimum: executive summary, data regarding operations, documented threats, errors, undesired states, crew/team resource management, crew/team coordination, and subjective aircrew/team comments and surveys. The contractor shall travel to Joint Base Andrews, MD or another government approved location to conduct a debriefing to AFDW Senior Leadership at the conclusion of the LOSA no earlier than one-week from submission of the final report.

SECTION III

3.0 SERVICE SUMMARY

3.1 Post Award Conference/Kick-off meeting. The contractor shall schedule and coordinate a kickoff meeting at the location approved by the contracting officer. The meeting will provide an introduction between contractor personnel and government personnel who will be involved with the contract. In coordination with the contracting officer and COR, the contractor shall provide a Kick-Off Meeting Agenda that will include, but not be limited to, the following:

· Introduction of personnel

· Overview of tasks

· Review of organization (complexity)

· Communication Plan/lines of communication overview (between both contractor and government)

· Security requirements (Building access, badges, Common Access Cards (CAC))

· Invoice procedures

· Monthly meeting dates

· Reporting Requirements, e.g. Monthly Activity Report (MAR)

· Overview of incoming Transition Plan to include process, timeframes, and status

· Initial deliverables

· Quality Control Plan (QCP)

· Sensitivity and protection of information

· Additional issues of concern

· The contractor shall provide the COR and LOSA Program Manager Post-Award Conference minutes within 15-days of the conference, which details a contract execution timeline, milestones, and a full summary of the conference with any action items

3.2 A monthly written report is due by the 10th business day of each month. The contractor shall communicate/coordinate with the AFDW LOSA Program Manager at least monthly regarding timetables, execution schedules, and program execution milestones. AFDW will provide a single Point of Contact (POC), the LOSA Program Manager, to the contractor to ensure continuity and historical reference to the overall project.

3.3 The contractor shall assist AFDW in developing recommended courses of action for a robust and comprehensive LOSA program. The contractor shall participate in program review groups, working groups, and other forums which provide avenues for promoting change and improvement.

Paragraph

-Technical writing and reports are delivered to the COR in accordance with the CDRL 90% of the time.

-Late deliverables are submitted not later than one working day.

-There are no more than 4 grammatical, punctuation, or spelling errors per page.-There is no more than 1 rewrite resulting from inaccurate, incomplete, or unsupported information per submitted document.

The COR and SME working group will review and approve final TEM prior to LOSA observer training.

-Performance reports are delivered to the COR of the CDRL 90% of the time.

-Late deliverables are submitted not later than one working day.

-There are no more than 4 grammatical, punctuation, or spelling errors per page.

-There is no more than 1 rewrite resulting from inaccurate, incomplete, or unsupported information per submitted document.

The COR will conduct a monthly review of the report regarding timetables, execution schedules, and program execution milestones.

-The contractor has fully trained all observers on data collection software at training events as specified by LOSA program manager.

-Data collection software has been successfully delivered to observers a minimum of one week prior to the beginning of the LOSA Observation period.

The COR will conduct an initial review of the first 10 LOSA Observations and contractor feedback to ensure quality of LOSA Observer training.

-The contractor has contacted observers to make corrections to incomplete observations within 48 hours of receipt 95% of the time.

-Late Observer contacts will be made no later than next business day.

The COR will conduct weekly reviews of all LOSA Observations and associated contractor feedback.

-The contractor has organized and executed the required SME roundtable 100% of the time.

-The contractor has ensured all data processes are IAW Government requirements 100% of the time The COR will conduct a one-time exit survey with all SMEs to ensure roundtable met government requirements.

-Written Performance reports are delivered to the COR in accordance with the terms of the CDRL 90% of the time.

-Late written performance reports are submitted not later than one working day.

-There are no more than 4 grammatical, punctuation, or spelling errors per page.

-There is no more than 1 rewrite resulting from inaccurate, incomplete, or unsupported information per submitted document.

The COR will perform a review of the written report and receive the formal briefing to validate prior to delivery to senior leadership.

Note: The government reserves the right to inspect or test services that have been tendered for acceptance. The government may require performance of any nonconforming services at no increase in contract price. If this does not correct the performance issue or is not possible, the government may seek an equitable price reduction or contractual processes will begin to terminate the contract. Past performance history will be reported in Contractor Performance Assessment Reporting System to reflect satisfactory or unsatisfactory performance.

SECTION IV

4.0 DELIVERABLES

The Contractor shall provide deliverable(s) in a format mutually agreed upon by the Government and the Contractor.

The following enumerated deliverables are not expected to change. Due Date intervals are not expected to change but actual dates may need to be revised depending on actual contract start date.

4.1 Deliverables Management. The Contractor shall provide deliverables as specified in the PWS and contract. The Government will be provided access to current and historical web-based contract deliverables and performance metric data.

4.1.1 Threat and Error Matrix Workshop. The contractor shall conduct a TEM Workshop within 45-days of contract award.

4.1.2 Threat and Error Matrix Workshop Summary The contractor shall provide a written summary of the workshop to the Government within 15 calendar days of workshop completion.

4.1.3 Final Aircraft/Aircrew Threat and Error Matrix The contractor shall develop a customized Threat and Error Matrix for each flight crew position (Pilot and Special Mission Aviator) to be audited in advance of actual observer training. Threat and Error Matrix is due within 15 calendar days of completion of the Threat and Error Matrix Workshop.

4.1.4 LOSA Observer Training The contractor will provide LOSA Observer training NLT 30-days after the government audit of the Final TEM.

4.1.5 LOSA Data Analysis Roundtable. The contractor will conduct a LOSA Data Analysis Roundtable NLT 30-days after the completion of the final LOSA Observation.

4.1.6 Comprehensive Written Final Report. After a thorough review of LOSA data, the contractor shall deliver a comprehensive written final report to the COR and government-identified Senior Leadership NLT 30-days following the Data Analysis Roundtable. The report shall include: executive summary; data regarding operations; documented threats, errors, undesired states, crew/team resource management, and crew/team coordination; and subjective aircrew/team comments and surveys.

4.1.7 Electronic Data / Software. The Contractor shall provide HQ AFDW/SE, AFDW LOSA Program Manager and AFDW LOSA SIB an electronic copy of the data and software to access and sort/search data for the LOSA. Training to sort/search this data will be included. Electronic data/software is due at one-week prior to the debriefing to government-identified Senior Leadership.

4.1.8 Senior Leader Briefing. The contractor shall conduct a briefing to government-identified senior leadership No Earlier Than one-week after the submission of the Comprehensive Written Final Report.

4.1.9 Monthly Written Performance Report. The contractor shall provide the LOSA Program Manager a monthly written report documenting performance and accomplishments in the preceding month, by the 10th business day of each month.

4.2 Schedule. All deliverables (or proof of deliverable completion) shall be submitted directly to the COR and LOSA Program Manager. The Government will provide the contractor with an e-mail address for electronic deliverables. Unless otherwise noted in the PWS, the Government will have five business days to review deliverables and make comments to the contractor. The contractor shall have five business days to address those comments and resubmit the deliverables to the Government.

4.3 Other Reporting Requirements. In addition to the deliverable requirements identified above, the contractor shall immediately notify the LOSA Program Manager, Contracting Officer (CO), and COR as soon as problems or potential problems arise. The contractor shall follow-up verbal reports with written reports within five business days to AFDW/SE, COR, and LOSA Program Manager.

4.4 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 AFDW/SE via a secure data collection site. The contractor is required to completely fill in all required data fields at https://www.ecmra.mil.

SECTION V

5.0 GOVERNMENT FURNISHED PROPERTY, ETC

5.1 The Government will provide required resources to each contractor employee assigned to this contract for contract performance. The following resources are agreed upon in advance:

5.1.1 The Government will provide escorted access to Joint Base Andrews, Building 1500 and Building 1910, and other facilities as deemed appropriate by the AFDW LOSA Program Manager to contractor personnel assigned to this contract. Arrangements for use of resources during other than normal business hours will be coordinated through the LOSA Program Manager when approval is granted to work those hours.

5.1.2 At the discretion of the AFDW LOSA Program Manager, the Government may provide the opportunity for the contractor to visit AFDW units and participate in aircraft/simulator familiarization flights IAW AFI 11-401 on the UH-1N. These flights are not required but offered to allow the contractor to gain familiarity with and research into the flight deck characteristics and crew coordination in advance of actual LOSA execution.

5.1.3 The Government will provide qualified flight crews to comprise the observer crew force with qualifications and experience required to capture quality observations. The SMEs for the Threat and Error Matrix development and data validation will also be provided by the Government at their discretion and at locations per the Government’s requirements.

5.1.4 Information Sources. The Government will provide technical guidance and clarification in support of this program. However, contractor personnel are expected to utilize available reference material and not rely solely on the technical point of contact. Unclassified aircraft technical orders and operational guidance directives will be provided to the contractor for their reference. The contractor shall return these documents to the Government upon conclusion of the audit and the contractor shall ensure they are not distributed to unauthorized personnel. Documents produced or owned by the Government, including systems documentation, standards, and specifications or guidelines governing development of deliverables, manuals, to the extent that they are available, will be provided to the contractor on request.

5.2 Data. The Government has unlimited rights to all deliverables of this contract to include intellectual property. All documents and materials produced under this contract shall be Government owned and are the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. These documents and materials may not be used or sold by the contractor without written permission from the Contracting Officer. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights.

5.2.1 As part of this contract, the contractor shall provide a lifetime software licensing agreement to fully utilize all contractor-provided LOSA software. The contractor is responsible for providing software updates and upgrades as required to ensure full functionality of the software for three years following end of the contract period of performance. The LOSA data shall become the property of the U.S. Government for future use with historical LOSA data sets. All data collected, analyzed and stored shall be provided to the Government without usage limitations.

SECTION VI

6.0 GENERAL INFORMATION

6.1. Place of Performance. The primary place of performance shall be the contractor’s corporate office or facility. The secondary place of performance shall be Government facilities, Building 1500 and Building 1910 at Joint Base Andrews, MD. Any alternate places of performance will be designated by the AFDW LOSA Program Manager.

6.2 Travel. As an integral part of performing some of the requirements of the PWS, the contractor shall perform temporary duty (TDY) to Joint Base Andrews, MD. The forecasted travel is displayed in the Table below.

6.3 Hours of Work. AFDW/SE normal operating hours are 0800-1600, Monday through Friday. The contractor shall be accessible via electronic means (i.e. email, telephone, text or facsimile) and be able to respond to the AFDW LOSA Program Manager in a timely manner when not at Joint Base Andrews. The contractor shall ensure continuity of operations during periods of personnel turnover and long-term absences. Long-term absences are considered those longer than two weeks duration.

6.4 Core Duty Hours and Base Shutdown/Inclement Weather. Core duty hours are 0800 - 1600, Monday through Friday (excluding federal holidays). The Contractor shall follow guidance of the installation containing their place of performance to determine reporting schedules whether due to a base closure or inclement weather. The website for guidance regarding status of performance for work to be performed in the National Capital Region (NCR) is http://www.opm.gov/status/.

6.5 Kickoff Meeting/Orientation Meeting: The Contractor shall schedule and coordinate a Project kick-off Meeting no later than (NLT) five (5) calendar days after contract award at the location approved by the Government. The meeting will provide an introduction between the Contractor personnel and Government personnel who will be involved with the contract. The meeting will provide the opportunity to discuss technical, management, and logistic issues; travel authorization; communication process between Government and Contractor; and reporting procedures. At a minimum, the attendees shall include key Contractor personnel, AFDW/SE, key Government representatives, and the COR.

6.6 Quality Control

6.6.1 Quality Assurance. The Government shall rely on the Contractor’s existing quality assurance system as the method to ensure that the requirements of the contract and performance thresholds are met; however, the Government reserves the right to monitor and evaluate the quality of services provided and compliance with the contract terms and conditions at any time.

6.6.2 Quality Control Plan (QCP). The Contractor shall develop and maintain an effective quality control program to ensure services are performed IAW this PWS, applicable laws and regulations, and best commercial practices. The Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services with special emphasis placed on those services listed in this PWS. The Contractor’s quality control program is the means by which it assures itself that the work complies with the requirement of the contract.

6.7 Emergency Operations/Mission Essential Personnel: Continuation of Essential Contractor Services During Crisis. All services in this PWS HAVE NOT been defined or designated as essential services for performance during crisis IAW DFARs 252.237-7023, “Continuation of Essential Contractor Services.”

6.8 Contractor Manpower Reporting Application (CMRA):

6.8.1 The Contractor shall report ALL labor hours (including subcontractor labor hours) required for performance of services provided under this contract via the secure Contractor Manpower Reporting Application (CMRA) data collection site. The Contractor is required to completely fill in all required data fields at: http://www.ecmra.mil. Reporting inputs shall be for the labor executed during the period of performance for the Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported anytime during the FY, all data shall be reported not later than 31 October 2020. The Contractor may direct questions to the CMRA help desk.

6.8.2 Subcontractor Input in CMRA: Prime Contractors are responsible to ensure all subcontractor data is reported. Subcontractors will not be able to enter any data into CMRA but will enter their information into a Bulk Loader spread sheet available from the AF CMRA helpdesk. Subcontractor shall fill in columns A-C then return it to the AF CMRA helpdesk after it's completed and a technician team will enter the information into CMRA.

6.9 Security Instructions

6.9.1 Access. For access to unclassified Air Force networks and unescorted access to Government installations and facilities, the contractor must, at minimum, have completed a verifiable National Agency Check with Written Inquiries (NACI) or higher level investigation. Once a minimum of a NACI investigation has been completed and the results are favorable, the contractor may be issued a Common Access Card (CAC) card. The contractor shall acquire all necessary base passes for contractor personnel.

6.9.2 Training. Required security training on local procedures and policies will be provided by the Government and shall be completed satisfactorily by contractor personnel before they can perform their tasks.

6.9.3 Contractor Consent to Background Checks. Contractor shall not employ persons to perform under this contract if such employee is deemed or identified by each Air Force installation as a potential threat to the health, safety, security, general well-being, or operational mission of the installation and its population, nor shall contractor or subcontractor employ persons under this contract who have an outstanding criminal warrant as identified by Law Enforcement Agency Data System (LEADS) through the National Crime Information Center. LEADS checks will verify if a person is wanted by local, state, and federal agencies. All contractor and subcontractor personnel must consent to LEADS background checks. Contractor and subcontractor personnel who do not consent to LEADS check will be denied access to the installation. Information required to conduct a LEADS check includes: full name, driver’s license number and/or social security number, date of birth of the person entering the installation, and completion of a background check questionnaire. Contractor must have this information ready to provide to the base Visitor Control Center, if requested.

6.9.4 Badges. Contractor is required to provide identification badges for their employees. All contractor personnel must wear these badges while on duty on the Government site. Badges are required to identify the individual, company name, and be clearly and distinctly marked as contractor. Size, color, style, etc. are to be mutually agreed to by contractor and the COR. Contractor’s identification badge will not be used as an entry requirement for installation entry or entry into any Government designated controlled or restricted area.

6.9.5 Access to Installation during Force Protection Conditions (FPCONs). Contractors will be assigned a mission essential designation IAW requirements contained in base Antiterrorism/Integrated Defense Plan(s). Only the installation commander or the unit commander requesting contract support will assign the mission essential designation.

6.9.6 Safeguarding Unclassified, Safety Privileged and/or For Official Use Only (FOUO) Information. Contractor must meet Air Force standards for storing, processing, and handling unclassified, safety privilege, and/or Controlled Unclassified Information (CUI) information and systems. Additionally, all resources (e.g. maps, publication/instructions, photos) provided by the Government to assist the contractor in the performance of their contract will be surrendered upon termination of employment or the end of the contract performance period.

6.9.7 Privacy Act. Work on this project may require that personnel have access to Privacy Information. Personnel must adhere to the Privacy Act, Title 5 of the U.S. Code, Section 552a and applicable agency rules and regulations.

6.9.8 Contractors Working in Controlled or Restricted Areas. When the contractor requires access to the controlled or restricted area and does not have the proper security investigation, the Government will ensure escort(s) are provided for contractor at all times when within a controlled or restricted area. Contractor must have an issued AF Form 1199 or be under escort. Contractor is only allowed to escort visitors from the same company for which he/she works and all visits must be for official business. In addition, contractors must fulfill, maintain, and comply with all security requirements IAW AFI 31-101, Integrated Defense and command/local directives.

6.9.9 Access to Government Facilities with Controlled or Restricted Areas. Contractor must comply with security regulations imposed by the installation commander and/or the agency responsible for the project location. Due to specific mission requirements inherent in the nature of controlled or restricted areas on Air Force installations, Government may direct contractor to leave the controlled or restricted areas at any given time.

6.9.10 For Official Use Only (FOUO) and Safety Privilege Information. Agency information marked “For Official Use Only” or “Safety Privileged” or bearing other sensitivity markings shall be handled in accordance with agency information security program regulations and AFI 91-204 and instructions provided on the DD Form 254. This information will not be divulged or disclosed without agency permission. Requests for disclosure will be addressed to the Government Program Manager. Contractor personnel shall ensure information that is considered sensitive or proprietary is not compromised.

6.9.11 Non-Disclosure Requirements. In performance of this contract, the contractor may obtain access to sensitive, nonpublic information. The contractor agrees (a) to use and protect such information from unauthorized disclosure in accordance with the FAR; (b) to use and disclose such information only for the purpose of performing this task order and to not use or disclose such information for any personal or commercial purpose; (c) to obtain permission of the government COR before disclosing/discussing such information with a third party; (d) to return, upon government request, any non-public, sensitive information no longer required for contractor performance; and (e) to advise the government COR of any unauthorized release of such information. Upon request, the contractor shall have its employees assigned to this contract execute a non-disclosure agreement for delivery to the government. The government will require contractor personnel both on and off-site to sign a non-disclosure statement to protect non-public information of the government. The contractor shall maintain the nondisclosure agreements and have these agreements available for government review during the life of the contract. At the end of the task order, the contractor shall turnover to the government its personnel non- disclosure agreements.

6.9.12 Physical Security. The Contractor shall safeguard all Government property, documents and controlled forms provided for Contractor use and adhere to the Government property requirements contained in this contract. At the end of each work day, all Government facilities, equipment, and materials shall be secured by a Government POC. Contractors are not allowed to secure Government facilities, equipment, and materials.

6.9.13 Access Control. The Contractor shall establish and implement methods of ensuring that no building access instruments issued by the Government are lost, misplaced or used by unauthorized persons. Access codes shall not be shared with any person(s) outside the organization. The Contractor shall control access to all Government provided lock combinations to preclude unauthorized entry. The Contractor is not authorized to record lock combinations without written approval by the Government COR. Records with written combinations to authorized secure storage containers, secure storage rooms, or certified vaults, shall be marked and safeguarded at the highest classification level as the classified material maintained inside the approved containers.

6.9.14 Pass and Identification Items. The Contractor shall ensure the pass and identification items required for contract performance are obtained for employees and non-government owned vehicles.

6.9.15 Retrieving Identification Media. The Contractor shall retrieve all identification media, including vehicle passes, from employees who depart for any reason before the contract expires.

6.9.16 Traffic Laws. The Contractor and its employees shall comply with base traffic regulations.

6.9.17 Weapons, Firearms, and Ammunition. Contractor employees are prohibited from possessing weapons, firearms, or ammunition, on themselves or within their Contractor- owned vehicle or privately-owned vehicle while on Joint Base Andrews or any other military facility.

6.9.18 Communications Security (COMSEC). Contractors may require access to COMSEC information on Air Force installations. The Contractor shall not require a COMSEC account. Access shall be controlled by the sponsoring agency. Access to COMSEC material by personnel is restricted to US citizens holding final US Government clearances. Such information is not releasable to personnel holding only reciprocal clearances. If it is determined the Contractor is required to access COMSEC information, the necessary training information and courses shall be provided by the COR. The DD Form 254 shall give further instructions on safeguarding and managing COMSEC material.

6.9.19 Contractor Identification. All Contractor personnel shall wear the Air Force issued Common Access Card at all times when away from their immediate work area so as to distinguish themselves from Government employees. When conversing with Government personnel during business meetings, over the telephone or via electronic mail, Contractor personnel shall identify themselves as a contractor to avoid situations arising where sensitive topics might be better discussed solely between Government employees. Contractors shall identify themselves on any attendance sheet or any coordination documents they may review. Electronic mail signature blocks shall identify their company affiliation. Where practicable, contractors occupying collocated space with their government program customer should identify their work space area with their name and company affiliation or as a minimum “Contractor” after name.

6.9.20 Drug, Tobacco, and Alcohol Use Policy. The consumption of alcoholic beverages or illegal drugs by contractor personnel, while on duty, is strictly forbidden. Contractor shall immediately remove any employee who is under the influence of alcohol or drugs. Tobacco use shall be restricted to government-designated areas.

SECTION VII

7 TRAVEL

7.1 Contractor Travel. Contractor will be required to travel CONUS and within the National Capital Region (NCR) during the performance of this contract to attend meetings. Contractor will be authorized travel expenses consistent with the substantive provisions of the Joint Travel Regulation (JTR) and the limitation of funds specified in this contract. All travel requires Government approval/authorization and notification to the COR.

7.2 Non-Local Travel. Contractor employees may be required to travel to various locations in performance of this contract. Travel costs shall be reimbursed utilizing the Federal Travel Regulation, Joint Travel Regulations and Standardized Regulations section 925 as applicable from Federal Acquisition Regulation 31.205-46 for locality per diem rates. Actual modes of transportation and costs shall be agreed to in advance and reimbursed on a cost basis upon receipt of the invoice in Wide Area Work Flow and all receipts turned in to the COR. No General & Administrative (G&A) charges will be paid on these actual costs. The Contractor shall present official business travel request for non-local travel. Upon COR approval, the contractor may take the business trip. All travel reimbursement claims must be submitted NLT five business days after travel.

7.3 Local Travel. The contractor may be required to attend meeting or events within the local city or base of assignment commuting vicinity may be required at no cost to the Government. Local travel within the National Capital Region (NCR) commuting vicinity shall be considered a cost of doing business and shall not be separately reimbursed. Reimbursement for parking is at the discretion of the COR and must be approved prior to local travel.

7.3.1 Further guidance for Contractor travel can be found at

https://www.defensetravel.dod.mil/site/faqctr.cfm.

7.4 Trip Reports. The Contractor shall prepare and deliver Trip Reports following each non-local trip to the COR within three workdays after trip completion. The Trip Reports are not required for local travel as defined in the Federal Travel Regulation. The trip Reports shall detail:

· Individual traveling

· Destination

· Dates

· Itemized Cost

· Purpose of trip

· Participation of traveler

· Result of the trip

· Problems/issues

SECTION VIII

8.0 EMPLOYEES

8.1 List of Employees. The Contractor shall maintain a current listing of employees assigned under this contract and define who key personnel are. The list shall include the employee's name, social security number and level of security clearance. The list shall be validated and signed by the company Facility Security Officer (FSO) and provided to the Contracting Officer, Program Manager, and Servicing Security Activity. An updated listing shall be provided upon request.

8.2 Contractor Professionalism. The contractor shall:

· Present a professional appearance and maintain professional demeanor and conduct at all times.

· Conduct their work assignments IAW project schedules.

· Function effectively and efficiently during extended periods of high pressure and stress.

· Function as an integral member of a team of highly trained professionals responsible for the safety and security of USAF personnel and resources.

SECTION IX

9.0 MISCELLANEOUS

9.1 Freedom of Information Act (FOIA). All official Government records affected by this contract are subject to the provisions of the FOIA (5 U.S.C. 552/DoD 5400.7-R/AF Supplement). Any request received by the Contractor for access/release of information from these records to the public (including Government/Contractor employees acting as private citizens), whether oral or in writing, shall be immediately brought to the attention of the CO for forwarding to the AFDW FOIA Manager to ensure proper processing and compliance with the Act.

9.2 For Official Use Only (FOUO). The Contractor shall comply with DoD 5400-7-R, Chapter 4, DoD Freedom of Information Act (FOIA) Program requirements. This regulation sets policy and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding FOUO material.

9.3 Privacy Act. Work on this contract may require that personnel have access to information protected by the Privacy Act. Contractor personnel shall adhere to the Privacy Act, Title 5 of the U.S. Code, Section 552a and applicable agency rules and regulations when handling such information.

9.4 Records. All records created and received by the Contractor in the performance of this contract shall be maintained and readily accessible. Records shall remain the property of the Government.

9.5 Safety Concerns. The Contractor is solely responsible for compliance with OSHA standards for the protection of their employees. The Government is not responsible for ensuring that Contractors comply with “personal” safety requirements that do not present the potential to damage Government resources.

9.6 Project Policy. The Contractor shall comply with all industry standards. All work shall be done in accordance with all federal, local, and state laws and regulations.

9.7 Inherently Governmental Functions. The Contractor shall not perform inherently governmental functions as defined in the Federal Acquisition Regulation (FAR) Subpart 7.5 in relation to this PWS.

9.8 Ethics. The Contractor shall not employ any person who is an employee of the US Government if employing that person would create a conflict of interest. Additionally, the Contractor shall not 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 DoDD 5500-7, Joint Ethics Regulation.

9.9 Professional Appearance of Work Space. The Contractor shall keep work space areas neat and orderly and avoid conditions leading to safety violations.

9.10 Non-Personal Services. The Government shall not supervise or task Contractor employees in any manner that generates actions of the nature of personal services, or that creates the perception of personal services. It is the responsibility of the Contractor to manage its employees directly and to guard against any actions that are of the nature of personal services, or give the perception of personal services to the Government or to Government personnel. If the Contractor feels that any actions constitute, or are perceived to constitute personal services, it is the Contractor’s responsibility to notify the CO immediately. Non-personal Contractor services shall not be used to perform work of a policy/decision making or management nature.

Page 11 | 21