PWS Testek.pdf

MAINTENANCE SERVICES OF AVTRON - TESTEK TEST STANDS

i

PERFORMANCE-BASED WORK STATEMENT (PWS)

U.S AIR FORCE

309TH Maintenance Support Group (MXSG)

Created By 309 MXSG

4/20/2023 Version 1.0 ii

TABLE OF CONTENTS

1 DESCRIPTION OF SERVICES

2 BASIC SERVICES

3 SERVICE SUMMARY

4 CDRL SUMMARY

5 ADDITIONAL REQUIREMENTS

6 SECURITY:

7 GENERAL INFORMATION

8 ENVIRONMENTAL CONTROLS

9 GOVERNMENT OBSERVATIONS

10 FOREIGN OBJECT DAMAGE (FOD) AND TOOL CONTROL

11 ENVIRONMENTAL:

Appendix A – ACRONYMS AND ABBREVIATIONS appendix B – EQUIPMENT LISTING

531 CMMXS, HILL AFB

309 MMXG, HILL AFB

Appendix C – SAFETY

1 DESCRIPTION OF SERVICES

1.1 The Contractor shall be responsible to support the AVTRON/Testek Test Stands for the OO-ALC located at Hill Air Force Base (AFB) and the 525th Electronics Maintenance Squadron (EMXS) at Kadena Air Base (AB), Japan. The Contractor shall provide quality repair, maintenance services, engineering and software services, system integration, reconfiguration, modification, and component upgrade of the test stands identified in Appendix B. The Contractor shall be responsible to repair test stands to a fully functional state capable of successfully testing aircraft, missiles, and related commodities and electronics components in accordance with (IAW) Original Equipment Manufacturer (OEM) and AF technical data. The Contractor shall provide all equipment, software, updated technical and operational data, adapters, tools, supplies, labor, and management for required services.

1.2 The current software and some hardware components are proprietary. The Government cannot provide access to proprietary data and components. Proprietary restrictions are the sole responsibility of the Contractor.

2 BASIC SERVICES

2.1 Repair Services for Hill AFB and Kadena AB

2.1.1 The contractor shall be required to gain and maintain access to the Facility Equipment Maintenance System (FEMS) to be used as the system of record for capturing all sustainment and maintenance actions, for required deficiency and corrective action reporting and workload communication.

2.1.2 The Contractor shall provide a list of Contractor's Point of Contact (POCs) to the Contracting Officer Representative (COR), to include engineering support and maintenance support, at time of award. (CDRL A/B/C/D/E001) Within 14 business days after contract award, or after a POC changes.

2.1.3 The Contractor shall conduct all repairs IAW the applicable technical orders (TOs), technical data, specifications, OEM manuals and applicable codes (i.e. National Electrical Code (NEC), National Fire Protection Act (NFPA-70), etc.) with all final components and repairs being permanent.

2.1.4 The Contractor shall keep the Government shop supervisor/responsible Process Engineer abreast of the test stand’s progress daily which includes short term fix, parts required, parts cost, the date the parts are estimated to arrive, and estimated date of repair completion.

2.1.5 The Contractor shall record all deficiencies found during repair/visits in FEMS under the log tab via communication tab within 24 hours of identifying the deficiency.

2.1.5.1 The contractor shall only accept workload in the form of a Work Authorization Document (WAD) submitted through the FEMS only by 309 MXSS or COR.

2.1.5.2 After completion of repairs, the contractor shall document all deficiency resolution information in FEMS. The contractor shall input status updates for each open work order entered in FEMS on a weekly basis or as requested by the COR or 309 MXSS Supervisor.

2.1.6 After completion of repairs or component upgrades, the Government will perform tests of parts specified for the test stand in accordance with (IAW) applicable AF technical data. The test(s) will be used to validate the functionality of the test stands in actual production situations. In order for test stands to be considered fully repaired, they must be able to run tested components acceptably. If compliant, the test stand’s responsible 309 MXSS supervisor will validate acceptance and close the work order or equivalent document in the FEMS system.

2.1.7 The Contractor shall perform system/equipment familiarization with operator and maintenance personnel on any system updates, including programming and operational configuration changes to ensure safe operation. See paragraph 2.8.

2.1.8 The Contractor shall update existing Test Program Sets (TPS) and fixtures for assets (aircraft and missile components) tested on the test stands.

2.1.9 The contractor shall submit a copy of all program files or applicable data after completion of any TPS or software changes to include program logins and passwords. (CDRL A/B/C/D/E002)

2.1.10 The Contractor shall provide recommendations for the most cost-effective test stand upgrade, when requested by the COR. The Contractor shall provide the COR with detailed cost data used to make the recommendation. (CDRL A/B/C/D/E003)

2.1.11 The Contractor shall provide calibration assistance of the test stands, when requested by the 309 MXSS Shop Supervisor.

2.1.12 Contractor personnel shall be experienced in high pressure hydraulic systems, pneumatic controls systems, electrical and electronic control systems with a solid background in computer software programming and controls. Experience in LabVIEW® and Visual Basic programming may be required.

2.2 Hill AFB - Specific Requirements

2.2.1 The Contractor shall provide on-site technicians/engineers to adequately support the response times listed in table 2.1 and test stands listed in appendix B. Work performed shall be done at Hill AFB and at Kadena AB, Japan, when requested. Government will provide on-site office space at Hill AFB for three Contractor employees.

2.2.2 The Contractor shall be at the test stand’s location in need of repair within the time frame specified in the table below once notified by the COR. The Contractor shall have the test stand operational within the time frame depicted in the table, IAW the prioritized list below and contingent upon receipt of parts. The Contractor shall meet on-site arrival and completion times 85% of the time.

Table 2.1 Test stand Priority Hill AFB

Test Stand Priority On-Site Arrival Time

Completion Time

4 – critical equipment inoperable, work stoppage 4 business hours 6 business days

3 – non-critical equipment inoperable, work stoppage

8 business hours 9 business days

2 – critical equipment requires service, no risk of work stoppage

2 business days 15 business days

1 – non-critical equipment requires service 3 business days 21 business days

2.2.3 The Contractor shall continue to provide support if the repair action modified the operational condition or changed the parameters of the test stand after repairs have been completed until each test stand passes Precision Measurement Equipment Laboratory (PMEL) certification IAW TO 00-20-14 and 33K-1-100.

2.3 Kadena AB – Specific Requirements

2.3.1 The Contractor shall have two (2) business days in which to respond to the Government’s request for on-site support. At this time, the Contractor shall set up a date and time that is acceptable to the COR and Contractor to be on-site to perform repairs needed.

2.3.2 It is understood that due to the time difference and specific travel requirements, a minimum of fifteen (15) business days is required for any travel to Kadena AB from the date of the Government request, unless the Contractor agrees to the COR’s request for an earlier travel date.

2.3.3 The Contractor shall have one (1) business day in which to respond to the Government’s request for on-call technical support. The Contractor shall provide technical support via telephone or e-mail to assist Government personnel in diagnosing and repairing the test stands.

2.4 Engineering Services

2.4.1 The Contractor shall provide engineering services support for software maintenance, hardware maintenance, system integration, Air Force Engineering Data (AFED) development/revision, TPS and prepare engineering studies and reports related to test stand operation and repairs.

2.4.2 The Contractor shall assist engineering personnel in identifying and recording component changes that affect the form, fit or function of the test stand being repaired or upgraded.

2.4.3 The Contractor shall provide procedural changes as a result of component upgrades or modifications to the equipment as required. The contractor shall provide procedural changes to the 309 MXSS shop supervisor and COR who requested the service for the particular affected test stand within five (5) business days after completion unless an extension is approved by the COR.

(CDRL A/B/C/D/E004)

2.5 Software Services

2.5.1 The contractor shall provide Government Purpose Access Rights (GPAR) to all system files to include passwords and full system access on all test stands listed in appendix B.

2.5.2 The Contractor shall provide software support for minor configuration and programming changes required for component changes/replacement, TPS modifications, file system maintenance, system backup, restoration and generation, used to sustain the operational condition of the test stands and to provide enhanced user capabilities to resolve minor malfunctions and diagnostic analysis.

2.5.2.1 The contractor shall provide the government a back-up of the program file on approved media (CDRL A/B/C/D/E005) for all equipment listed in appendix B, by the end of the first year’s period of performance (PoP) of this contract.

2.5.2.2 Upon completion of any repairs that result in software changes the contractor shall provide the responsible 309 MXSS shop supervisor with a back-up of the program file on media approved by the requesting 309 MXSS Supervisor and/or COR. (CDRL A/B/B/D/E005)

2.5.3 The Contractor shall provide all necessary support to Government technicians for the calibration of the test stand after installation of the software. The 309 MXSS or 809 MXSS Supervisor will make the final determination as to what measurement accuracies will be used for calibration.

2.5.4 When new calibration standards are required, the Government may request the assistance of the Contractor in developing/installing the new standards on the affected equipment.

2.5.5 The Contractor shall comply with Air Force Automated Computer Program Identification Numbering System (ACPINS) as described in TO 00-5-16 when implementing, revising, or altering in any manner software code or programming. Any such changes shall be accompanied with properly labeled media identified by a new or revised Computer Program Identification Number (CPIN) visible in the software program itself for submission through AF systems.

2.6 Over and Above

2.6.1 In the event local personnel are not able to complete the services required in paragraphs 2.1, through 2.5, the Contractor shall assign additional subject matter expert(s) capable of completing the needed repairs within four (4) business days of being notified. Details of how the requirement will be met will be coordinated with the COR.

2.6.2 The Contractor shall obtain approval from the COR prior to engaging additional personnel.

2.7 Parts

2.7.1 The Contractor shall provide all repair parts for test stand support except as noted in paragraph

2.7.3. The Contractor shall coordinate parts for COR and/or 309 MXSS approval. The Contractor shall use technical data specified parts. If technical data specified parts are not available, the Contractor shall request prior approval from the COR on proposed replacement parts from other sources. The Contractor shall reference the test stand’s Identification (ID) number and work order number on the purchase order and ship parts to the address provided by the COR at the beginning of the contract and when changes occur.

2.7.2 The contractor shall provide a service report to include an itemized list of parts and materials to the COR NLT the 5th business day of each month. (CDRL A/B/C/D/E006). The Contractor shall also upload the itemized invoice of parts and materials to WAWF when billing.

2.7.3 The Government reserves the right to provide the Contractor with Commercial-off-the-shelf (COTS) parts meeting technical data or equivalent specifications when it is in the Government’s best interest.

2.8 Equipment Familiarization

2.8.1 The contractor shall notify 309 MXSS supervisor as diagnosis and repairs are being made on each test stand listed in Appendix B, to allow for hands on familiarization to further develop organic capabilities.

2.8.2 The Contractor shall provide on-the-job-training (OJT) to Government operators, maintainers, and engineers in conjunction with maintenance and repair functions as requested by the COR.

2.8.3 The Contractor shall be responsible for the functionality and sustainment of test stands while conducting training.

2.8.4 In months when training takes place, the Contractor shall report training accomplished to include Government employee name, test stand ID number, and type of training conducted in a service report to the COR and 309 MXSS Supervisor NLT the 5th business day of following month.

(CDRL A/B/C/D/E006)

2.9 Other Requirements

2.9.1 The contractor shall be responsible for updating the equipment listed on Appendix B when new test stands are added, removed, or become obsolete.

2.9.1.1 The Contractor shall update the Appendix B equipment list to include all asset identification numbers assigned to them in FEMS.

2.9.2 The contractor shall make available upon request by the COR, 309 MXSS Supervisor, or 309 MXSG EN, a copy of all existing tech data, OEM manuals, schematics/drawings, or passwords, (CDRL A/B/C/D/E005) necessary for the maintenance or repair of all equipment listed in Appendix B, within seven (7) business days of the request.

2.10 Warranty

2.10.1 The Contractor shall be responsible for the cost of any repairs or parts as a result of rework from poor workmanship.

2.10.2 The terms and conditions offered to the Government will be the same terms and conditions offered to commercial customers.

2.10.3 Standard commercial terms and conditions will be enforced in the performance of this contract.

3 SERVICE SUMMARY

PWS

Paragraph Performance Objective

Performance Threshold

2.1.5 In order for a test stand to be considered

fully repaired, it must be able to run tested components acceptably

(Satisfactory) when the Contractor has met the asset run test with one (1) customer complaint per quarter

2.2.1 The Contractor shall be on-site of the test stand

in need of repair within the time frame once notified by the COR (Hill AFB)

(Satisfactory) when the Contractor meets the time frame 85% of the time

2.2.2 The Contractor shall have the test stand

operational within the time frame starting the date of notification (Hill AFB)

(Satisfactory) when the Contractor meets the time frame 85% of the time

2.4.3 The Contractor shall provide written procedural

changes as a result of component upgrades or modifications to the equipment to the responsible shop supervisor. (CDRL AXXX)

(Satisfactory) when the Contractor meets the five (5) business days requirement 85% of the time

2.5.2 2.5.2.1 2.5.2.2

The Contractor shall provide the respective Process Engineer for the test stand repaired/upgraded with a back-up of the program file on media approved by the requesting 309 MXSS Supervisor

(Satisfactory) when the Contractor provides back-up on approved media by the end of the first years PoP and upon completion of any repairs that result in software changes

2.7.2 2.8.3

The Contractor shall provide a service report to the COR. (CDRL AXXX)

(Satisfactory) when the Contractor meets the 5th business day of each month and meets the time frame 85% of the time

2.3.1 The Contractor shall respond to requests for

on-site support. (Kadena AB)

(Satisfactory) when the Contractor meets the two (2) business day requirement 85% of the time

2.3.3 The Contractor shall respond to request for on-

call technical support. (Kadena AB) (Satisfactory) when the contractor meets the one (1) business day requirement 85% of the time

Definitions:

** Validated customer complaint – A customer complaint that is reviewed, documented, and confirmed via a Corrective Action Report (CAR).

4 CDRL SUMMARY

Contract information data shall be delivered electronically in accordance to the corresponding requirement for each Data Item listed in Table 4-1 (below). The contractor shall have no more than one error per quarter for all CDRL submittals. The contractor shall submit CDRLs according to the due date indicated and have no more than one CDRL per quarter submitted after the identified due date. Grammatical errors do not count as an error. Substantive mistakes shall be corrected within two working days and corrective action taken to prevent recurrence of inaccurate late CDRLs.

Table 4-1

Exhibit Title PWS Paragraph

Delivery

A001 Contractor POC List

2.1.2 Within 14 business days after

contract award, or after a POC changes A002 Program Files 2.1.8.1 After completion of any TPS or software changes

A003 Cost-effective test stand upgrade recommendations

2.1.9 As requested

A004 Procedural changes 2.4.3 Within five (5) business days after completion unless an extension is approved by the

COR

A005 Back-up of the program file on approved media

2.5.2.1, 2.5.2.2, 2.9.2 Initially by the end of the first year’s period of performance, upon completion of any repairs that result in software changes, or within seven (7) business days of the request.

A006 Service report 2.7.2, 2.8.4 NLT the 5th business day of each month or within seven

(7) business days of the request

A007 Incident/Mishap report 6.3.8.3 No later than one business day after the incident occurs

A008 Safety Program Appendix C Prior to commencement of any work described in this contract

5 ADDITIONAL REQUIREMENTS

5.1 Government Furnished Property (GFP)

5.1.1 Government furnished property will be issued to the contractor for repair when repairs are needed. The contractor shall safeguard all GFP placed into the contractor’s care. GFP shall be shipped to the OEM facility and returned to the appropriate 309 MXSS/MXDV office by the contractor, at the contractor’s expense.

5.1.2 The Contractor shall ship parts FOB destination with an agreeable shipping method approved by the Government and be responsible for all costs. Expedited shipping fees must be approved by the COR or 309 MXSG/MASO personnel prior to shipment.

5.2 Government Provided Support

The Government will provide necessary working space, including heat, light, ventilation, and electrical powered outlets for the use of contractors’ maintenance personnel. The Government shall provide access to the necessary facilities where the equipment resides. The place of performance shall be Hill Air Force Base (AFB), UT.

Government telephones shall be used for official business only.

The contractor shall be responsible for safeguarding all Government property provided for contractor use.

5.3 Quality Control Plan

The contractor shall establish a complete Quality Control Plan (QCP) to ensure the requirements of this contract are provided as specified upon proposal. The contractor's quality management program shall comply with the minimum quality management systems elements specified in the American National Standards Institute (ANSI), American Standards Organization (ASO), and International Standard Organization (ISO) family of standards. The report shall be submitted to the COR, NLT 30 days post contract award.

5.4 Quality Assurance

5.4.1 The COR will perform assessments of the contractor’s performance. Subsequent to contract award, specific name and contact information of the COR with a letter defining duties and authority will be furnished to the contractor.

5.4.2 The COR will inform the task manager in person when discrepancies occur and will request corrective action. The COR will make a notation of the discrepancy on the assessment checklist with the date and time the discrepancy was noted and will request the task manager (or authorized representative) to initial the entry on the checklist.

5.4.3 The government may inspect each task as completed or increase the number of quality control inspections if deemed appropriate because of repeated failures discovered during quality control inspections or because of repeated customer complaints.

5.4.4 Any matter concerning a change to the scope, prices, terms or conditions of this contract shall be referred to the CO.

5.5 Safety and Health Standards

5.5.1 The contractor shall follow and adhere to the Air Force as part of the Occupational Safety and Health Administration (OSHA).

5.5.2 Voluntary Protection Program (VPP). The contractor is required to attain familiarization with the requirements of VPP. Information on the VPP can be accessed at http://www.osha.gov/dcsp/vpp/index.html. VPP requirements apply to contractors whose employees work more than 1,000 hours per quarter. The contractor shall flow down these requirements to all sub-contractors who qualify as applicable contractors under this contract.

5.5.3 The contractor shall provide from its OSHA 300 information the Total Case Incident Rate/Days Away Restricted or Transferred (TCIR/DART) rate by 15 January of each year to the CO for submission as part of the installation's annual OSHA VPP self-evaluation report.

5.5.4 System Safety Program Plan. The contractor shall implement a safety program that ensures protection of Government personnel and property. As part of the Safety Program the contractor shall establish a Safety Plan IAW Appendix B of this PWS. The contractor shall submit the Safety Plan within fifteen (15) days after contract award.

5.6 Manpower Reporting:

5.6.1 The Contractor shall report ALL Contractor labor hours (including sub-contractor labor hours) required for performance of services provided under this contract via a secure data collection site.

The Contractor is required to completely fill in all required data fields at http://www.SAM.gov

5.6.2 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 Contractor Manpower Reporting Application (CMRA) help desk.

5.6.3 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 ECMRA link. User manuals for Government personnel and Contractors are available at the ECMRA link at http://www.SAM.gov

6 SECURITY:

Security Review Control Number:

Security Review Date:

Reviewed By:

6.1 Conflicts of Interest

6.1.1 The contractor shall not assign to contract or task order performance any person, including any employee of the U.S. Government, if employing that person would create a conflict of interest under any law, regulation or policy of the United States Government. Additionally, the contractor shall not assign to contract or task order performance, 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 DoD Directive 5500.7-R, Standards of Conduct, and any other applicable regulation or policy of the Department of the Air Force or its subordinate commands, as applicable, including but not limited to Air Force Materiel Command.

6.1.2 Contractors will not use any other form of identification to access any government installation or facility while working on a government contract except the issued credentials associated with the awarded contract or task order. Example: using a military retiree card to access an installation to work on a contract.

6.2 Security Requirements

6.2.1 Foreign nationals (FN) will not be escorted, or sponsored, onto the installation without being properly vetted. Any request must follow 309 MXSG OI 16-102, Security Requirements section

7. FNs must be approved for access via the Foreign Disclosure Office and Air Force Office of Special Investigations (AFOSI).

6.2.2 The contractor shall comply with all security, force protection, operation security and antiterrorism requirements at each installation.

6.2.3 The contractor shall comply with 309 MXSG in and out-processing procedures for all contractor personnel to ensure required security-related briefings and debriefings are accomplished.

Specific in and out-processing checklists may be included at the task order level.

6.2.4 The contractor will use the Contracting Officer Representative (COR) or 309 MXSS Supervisor.

as the primary means of reviewing and approving forms and for communicating with necessary government representatives.

6.2.5 For classified contracts the contractors with a current T3, T3R, T5 or T5R security clearance with “secret” eligibility must adhere to the Security Executive Agent Directive (SEAD) 3, reporting requirements for cleared personnel. Cleared contractors will complete, initially and annually, cleared personnel training to include any additional training.

6.2.6 Government issued Common Access Cards (CAC)s, badges, identification shall be removed and/or concealed from plain sight when outside the installation and shall not be left in vehicles or unprotected. Badges and passes will not be duplicated, photographed, or copied. Lost or stolen identification badges, vehicle passes etc. will be immediately reported to the COR and Security Forces Office.

6.2.7 Communications Security

6.2.7.1 All communications with DoD organizations are subject to Communications Security (COMSEC) review.

6.2.7.2 The DoD authorizes the military departments to conduct COMSEC monitoring and recording of telephone calls originating from, or terminating at, DoD organizations.

6.2.7.3 The Government advises the contractor that at any time they place a call to, or receive a call from, a DoD organization, they are subject to COMSEC procedures.

6.2.7.4 The contractor assumes the responsibility for ensuring wide and frequent dissemination of the above information to all employees dealing with official DoD information.

6.2.8 Operations Security (OPSEC) Requirements

6.2.8.1 During the course of this contract, in addition to those restrictions, instructions and guidelines delineated in the PWS and/or other references provided, the contractor will adhere to the following minimum requirements.

6.2.8.2 Introduction of personnel electronic devices into government spaces, laptops, tablet Personal Computers (PC)s, cellular phones, cameras, recording devices, and data recording/storage devices is strictly controlled and forbidden in most cases. Company issued equipment required for the performance of work must be approved by the government 309 MXSG security specialist. Photography and recording is not allowed in restricted areas and controlled areas except for official use and by approved photography letter only. NOTE: Unless otherwise stipulated in the contract, contact the Installation Public Affairs or SM for approval.

6.2.8.3 Contractor personnel shall not discuss government operations in public or over unprotected or unencrypted communications. Official Business controlled unclassified information (CUI) may only be transmitted as directed in the PWS as it adheres to CUI Guidelines.

6.2.8.4 The Contractor shall not post to company websites, publications, newsletters, or other media any images, data or information that reveal sensitive government operations, personnel, equipment, and/or classified or CUI. When in doubt, company press releases, related to this contract, will be coordinated through the Public Affairs Office prior to release.

6.2.8.5 Contractor personnel shall not disclose to unauthorized third parties, post to unofficial sites (including all Social Networking sites) any images, data or information that reveals sensitive government operations, personnel, equipment, including, but not limited to: Tactics, techniques and procedures, production or work schedules, any visible or concealed modifications, upgrades, additions to Air Force installations, property or weapons or equipment; increases, change, or decreases in work/deployment frequency or government personnel, project schedules, logistics or material delivery schedules; specialized equipment orders, deliveries, shipments, etc.

(Unauthorized disclosure and transfer of National Security Information is punishable under 18 USC § 793.); Unauthorized disclosures and attempts to solicit this type of information by unauthorized third parties or others not affiliated with this contract shall be reported to the SM and/or installation SFS, COR, and, if applicable, the company FSO and/or the Defense Security Service.

6.2.8.6 Practice OPSEC and implement countermeasures to protect Critical Information (CI) and other sensitive unclassified information and activities vigilance or degrade the planning and execution of military operations performed or supported by the contractor in support of the mission. Protection of CI will include the adherence to and execution of countermeasures which the contractor initiates or as provided by OPSEC manager or installation OPSEC Program Manager, for CI on or related to the

PWS.

6.2.8.7 The contractor must mark and protect any information IAW CUI, to include E-mail, and adhere to all CUI standards and policies.

6.2.8.8 Contractors who have access to the Ogden Air Logistics Complex (OO-ALC) and Government Servicing Units (GSU)s facilities or critical information shall have OPSEC training IAW AFI 10-701, Operations Security (OPSEC). Initial training will be approximately one (1) hour and follow-on recurring annual training will be approximately 1/2 (0.5) hour. OPSEC training will be conducted within 30 days of assignment.

6.3 Contractor Identification & Badges

6.3.1 All contractor management, staff and contractor personnel shall be clearly identified as such at ALL times. Contractor identification shall include visible badges, conversations, mail, email, teleconferences, video teleconferences, faxes, and/or other electronic communication whether with government personnel, other contractor personnel, or with the public when supporting this contract where their status as contractor employees might not otherwise be apparent or where they might be mistaken for civil service employees. At a minimum, contractor management staff or contractor personnel shall clearly identify themselves using the label “contractor” in email addresses in accordance with Federal Acquisition Regulation (FAR) 37.114(c), Special Acquisition Requirements; opening ALL phone conversations with a statement materially the same as, “[office name], I am [employee name], a [prime contractor’s company name] employee,” including the employing contractor’s name in the letterhead and/or signature block of any written correspondence; and any other means necessary.

6.3.2 The Contractor shall utilize the Defense Biometric Identification System (DBIDS) Badge/Common Access Card (CAC) /Controlled/Restricted Authorization Badge (CAB/RAB) In Accordance With (IAW) Hill Air Force Base (AFB) Instruction 36-812, Issue of Common Access Cards to Contractors (Contractor Verification System) and Air Force Instruction (AFI)_Air Force Material Command (AFMC)_Hill Air Force Base (AFB) Supplement 31-101-0, Hill Installation Defense Plan (IDP) Interim Change (IC) 1. The contractor must meet the same security requirements as government employees for access to the installations Automated Information Systems (AIS) or Information Technology (IT) Systems.

6.3.3 Defense Biometric Identification System (DBIDS) Cards

6.3.3.1 DBIDS Cards may be issued after contractor submits a completed AFMC Form 496, Application for AFMC Identification Card, to their assigned COR. The COR ensures the Form 496 is complete, to include: all requestor personal information, company name and address, current and valid driver license information, valid contract number and expiration date, requestor Social Security Number, requestor E-mail, what credentials needed, days and times for access and a digital signature from the COR.

The COR forwards Form 496 to the SM for signature and processing. The SM will notify COR after Form 496 is approved/disapproved with instructions for obtaining a DBIDS. Contractors will return completed Form 496 to issuing SM to begin in-processing. Incomplete Form 496s will not be processed. NOTE: Escort authority is not authorized, and Force Protection Condition “Bravo” is the minimum established by Security Forces Squadron (SFS). Contractors with a current DBIDS have authority to sponsor (not escort) onto the installation and must follow installation procedures for doing so. Contractors who do not require access to DoD IT systems will be issued a DBIDS annually unless contract end date is sooner.

6.3.3.2 New contractor employees approved for DBIDS will require an escort to Building 430 to receive a DBIDS. Employees going to Security Forces Squadron (SFS) without a sponsor are considered to be on the installation illegally and may be detained and removed. COR can escort the employee/s, or the employee/s may be sponsored onto the installation by a current CAC holder, and are required to meet all access requirements by SFS. A temporary visit request can be made for 1-60 days on the Visitor Control Website and requires the contractor employee name, driver’s license number and state of issue:

https://usaf.dps.mil/sites/HillAFB/vcc/SitePages/Home.aspx

6.3.3.3 Contractors with reported issues associated with background information on the Form 496 will be disapproved for DBIDS and will not be granted access to the installation.

Contractors that are denied access will have all issued credentials, keys, key cards or vindicator cards taken away and the employee removed from the installation immediately. Denied contractor/s are required to adhere to the appeal process established by SFS and 75 ABW Director. If employee is approved for access, they must obtain the approval letter and keep it on file for initial and future renewal of any credentials. Security forces will be notified if the employee, or anyone affiliated with the contractor, is uncooperative.

6.3.4 Common Access Cards (CAC)s

6.3.4.1 CAC eligibility is determined if access to Government Information Technology (IT) systems and access to Department of Defense (DoD) controlled installations or facilities on a recurring basis (for a period of six months or more) is required to perform the job, IAW HillAFBI 16-1405, Trusted Associate Sponsorship System (TASS). CACs will not be issued for training purposes only, IAW AFBI 36-812, Issue of Common Access Cards (CAC)s to Contractors. CACs will not be issued to foreign nationals unless they meet the requirements defined in AFI 31-113, Installation Perimeter Access Control. Contractor employees are required to provide two valid forms of identification prior to having a TASS account created. The list of valid forms of identification can be found on the Real-time Automated Personnel Identification System (RAPIDS) website: https://idco.dmdc.osd.mil/idco/

6.3.4.2 Eligible contractor employees requiring access to Government computer systems are required to pass a U.S. Government background check, favorable fingerprint results, and a minimum of a Tier (T) 1 investigation initiated by the Group Security Office.

When all steps are complete, with no issues, and the T1 investigation is opened with Office of Personnel Management (OPM) an interim CAC may be issued by the respective Group SM or Trusted Agent (TA). If the T1 is returned with less than favorable results the contractor employee will have their CAC revoked, issued credentials, key cards, keys, vindicator cards and any access to Government IT systems revoked. Without credentials the employee is no longer eligible to remain on the installation or have in their possession any other issued credentials.

6.3.4.3 Ineligible contractors are employees of a Defense contractor who is not eligible for a CAC but requires access to an AF installation or facility. Non-CAC eligible contractors are not allowed access to AF IT, IAW AF Memorandum, AFMC Guidance for the Credentialing of Uncleared Contractors. Contractors may be found ineligible if after a local determination is made by a certified Homeland Security Presidential Directive (HSPD)-12 adjudicator for derogatory fingerprints.

6.3.4.4 Contractor employees will be given two (2) weeks to complete the on-line Standard Form (SF) 85 investigation questionnaire and complete fingerprinting, prior to being submitted for a T1 and receiving an interim CAC. Employees that don’t complete the questionnaire and fail to meet the suspense dates may request an extension, otherwise they will be removed from the installation. On-line questionnaire and fingerprint scheduling will be initiated by the Group SM.

6.3.4.5 Prior closed investigations, with favorable results, must be within last two years from previous government employment, appointment, or affiliation to be used in lieu of submitting a new T1. A reciprocity check will be done to determine eligibility of prior investigations. If an investigation is out of scope, or none is found to exist, a minimum of a T1 investigation and fingerprints will be initiated by the 309 MXSG SM.

6.3.4.6 Contractor employees requiring a CAC, in performance of the contract or task order, that do not meet the minimum requirements for a CAC will be removed from the

Installation immediately. All Government credentials will be recovered and returned to the issuing 309 MXSG SM the same day. Only issued credentials, related to the contract, will be used to access the installation, receive CAB/RABs, vindicator cards and any approved AIS or IT. Contractor employees found not completing training with their CAC and only using the CAC to access a facility or installation will have the CAC revoked and a DBIDS issued.

6.3.4.7 The CAC shall not be amended, modified, or overprinted by any means. No stickers or other adhesive materials are to be placed on either side of the CAC. Holes shall not be punched into the CAC. The chip or laminate shall not be removed from the CAC.

6.3.4.8 Reverification of a CAC is required every six months by the TA IAW HillAFBI 16- 1405. As prescribed in AFFARS 5342.490-2, para (b)(1), contractors shall provide a listing of personnel who require a CAC to the contracting officer. Contractor supervisor/s and COR will notify the TA when a contractor employee no longer requires a CAC or has been removed from service and will return all issued credentials.

6.3.4.9 Contractors issued a CAC must complete initial Cyber Awareness Challenge Training once CAC is issued and complete annual training on or before the annual training date.

Contractors not completing training before required date will have their CACs revoked. When a contractor is found not using a CAC to access government networks and facilities on a regular basis the contractor will have the CAC revoked and a DBIDS issued.

6.3.5 Higher Level Clearance and Access

6.3.5.1 Contractor employees requiring classified access must be submitted for a Tier 3 (T3) or a Tier 3R for (Reinvestigations) if over 10 years. A Single Scope Background Investigation (SSBI) for Top Secret, must be submitted IAW DoDM 5200.02_AFMAN 16-1405, Air Force Personnel Security Program. The Field Security Officer (FSO), for the contractor, is responsible for initiating the required level of investigation above a T1 background investigation, and ensuring all investigations are current. The contractor shall meet the same security requirements as Government employees for access to the site AIS network and connections to an office printer, office supplies and any other items necessary to complete the assigned tasks.

The contractor will only have access and use of the office equipment as mentioned with the award of the task order. The Government supervisor or equipment custodian for the organization will monitor the accountability of the Government Furnished Equipment (GFE) provided for the contractor employee’s use. NOTE: Contractors, requiring classified access will have a current, approved, facility clearance and an approved form 254, Contract Security Classification Specification, before initiating a T3, or higher, investigation.

6.3.6 Controlled/Restricted Area Badge

6.3.6.1 The contractor shall provide written justification as to why controlled/restricted area access is needed and must include for each person: employee’s First, MI, Last name, current CAC or DBIDS ID number, Height, Weight, Eye Color, Hair Color, contract number with expiration date, date of last completed training and areas needing access to the issuing 309 MXSG SM to complete an AF Form 2586.

https://lms-jets.cce.af.mil/moodle/enrol/index.php?id=12980

6.3.6.2 Controlled/Restricted area badge (CAB/RAB) requests shall be requested through the COR and completed by the group 309 MXSG SM, who completes an AF Form 2586, Unescorted Entry Authorization Certificate, for each employee requiring entry into controlled/restricted areas. The contractor employee shall hand carry the AF Form 2586 to Security Forces (Hill AFB, building 430). The AF Form 2586 will be returned to the issuing 309 MXSG SM for accountability and before receiving a vindicator access card. NOTE: CAB/RABs will not be issued for the inconvenience of having to be escorted. Expiring cards will need to be reissued prior to expiration date and require at least a two-week notification from the contractor employee to allow for time to prepare a new Form 2586.

6.3.6.3 Contractor employees must meet the minimum background requirements prior to submitting for a CAB/RAB: Favorable Local File Check (LFC) located on a current Form 496, within the last cycle year, or a Form 2583, Request for Personal Security Action, within the last 30 days; have a current background investigation; or current security clearance verifiable through the Defense Information Security System (DISS) or subsequent system.

6.3.6.4 While in any Controlled/Restricted Areas, contractor employees shall display the CAB/RAB, in a company issued lanyard or badge holder, between the shoulders and above the waist in front of the body whenever inside an identified restricted or controlled area. NOTE: When outside any restricted/controlled area the CAB will be placed out of sight.

6.3.6.5 Contractor employees requesting unescorted access into a controlled area will have a valid DBIDS or CAC card prior to receiving a Form 1199, Controlled/Restricted Area Badge.

6.3.6.6 The contractor shall complete, initially and annually, Security Education and Motivation Phases I and II training prior to submitting an AF Form 2586 and any additional required training, based on access requirements. If the contractor has a CAC and access to AIS they will be loaded into the group training system for the initial and annual training. Those issued a DBIDS will schedule a time with the Group SM to complete the training and testing requirements initially and annually thereafter and should expect at least two (2) hours for completion.

6.3.7 Building ID. Keys and Vindicator Access Card Control

6.3.7.1 As required, the contractor employee shall also obtain a Building ID and/or vindicator access card from the appropriate Building Facility Manager or 309 MXSG SM.

Access to controlled/restricted areas will not be granted without a CAB/RAB badge and proper authorization for required areas. Some organizations require additional security measures and employees must meet those prior to gaining access.

6.3.7.2 The contractor shall establish and implement methods of making sure that all keys, vindicator cards, and building badges issued by the Government are not lost, misplaced, or used by unauthorized persons.

6.3.7.3 The contractor shall not duplicate any keys, vindicator cards or credentials issued by the Government.

6.3.7.4 The contractor shall immediately report the occurrence of a lost key to the appropriate building Facility Manager, and vindicator cards and building badges to the appropriate

309 MXSG SM.

6.3.7.5 The contractor shall prohibit the opening of locked areas by contractor employees to permit entrance of persons other than contractor’s employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the SM. Contractors will not share a vindicator and pin number to gain accesses.

6.3.8 Lost Credential/s or Access Card/s

6.3.8.1 Lost/stolen badges shall be reported to the issuing Group SM within one working day of loss. After receiving a Lost Identification Letter from the issuing security office, the contractor is required to fill out an AF Form 1168, Statement of Suspect Witness Complaint, through the SFS Office located in the West side of Building 408. The contractor must then bring a lost letter report and/or AF Form 2586 to the SF Offices to be issued a new badge then return all forms to the Group SM.

6.3.8.2 The CAC Issuing Official will verify the cardholder’s identity against the biometric information stored in DEERS and confirm the expiration date of the missing CAC.

The applicant is required to provide two valid forms of identification. The list of valid forms of identification can be found on the Real-time Automated Personnel Identification System (RAPIDS) website. The replacement CAC will have the same expiration date as the lost or stolen CAC. Contractor will follow HillAFBI 16-1405 lost CAC procedures prior to obtaining a replacement CAC.

6.3.8.3 The contractor shall create an Incident/Mishap report when a contract employee loses a CAC, DBIDS or CAB/RAB. The Incident/Mishap report must be submitted no later than one business day. (CDRL A/B/C/D/E007).

6.4 In/Out-Processing

6.4.1 All contractors are required to in/out-process from each respective organization regardless of if they are issued a DBIDS or CAC.

6.4.2 Contractor employees transferring between contracts, groups or companies will return DBIDS or CAC, CAB/RAB and vindicator card. New credentials will be issued by the receiving organization. The contractor shall have three days to return DBIDS or CAC, CAB/RAB, and vindicator card to issuing organization. NOTE: Contractor employee are required to be escorted while on the installation until new credentials are issued.

6.4.3 Contractor employees will complete the same in/out processing checklist from the assigned organization. Employees removed from the contract will be required to return all government issued credentials and vindicator key to the issuing office within the same day of separation. If employee is unable to return the credentials and vindicator key, then 309 MXSS supervisor or COR will ensure that all credentials are returned to the issuing SM the same day.

6.4.4 Contractors working on a form 254 for classified access will complete an AF Form 2587, Security Termination Statement, prior to being out-processed. This can be done by the COR or SM and if employee refuses to complete a form 2587, a witness will be required to show a debrief was conducted and the witness will annotate on the bottom of the form their name, signature, date and write on the form “employee refused to sign”.

6.4.5 Returning of Credentials

6.4.5.1 During performance of the contract and at the completion or termination of the contract, the contractor shall be responsible for prompt return of all credentials to the appropriate 309 MXSG SM for any employee who no longer requires access to the work site, and for obtaining required identification of newly assigned personnel.

6.4.5.2 When the Period of Performance (POP) has ended or the requirement is considered complete, contractors shall have two working days to terminate all their network user accounts and to return all access cards and base identification badges to the COR or

309 MXSG SM.

6.4.5.3 The CAC is the property of the U.S. Government and as such the contract employee (cardholder) has no rights to retain the CAC when not required to perform on a government contract or the U.S. Government requests its return. Hence once the U.S.

Government requests the CAC be returned (through the 309 MXSG MASO Office /Contracting Officer (CO)/COR, or other appropriate agent) the CAC can be seized by military or civilian police, the employer, 309 MXSG MASO Office or/CO/COR.

However, these entities must fully understand the limitations of their legal authority in cases where the cardholder refuses or resists verbal instructions during attempts to seize the CAC. Such cases will normally be turned over to Security Forces and/or other law enforcement agencies to be resolved. Contractors’ must notify the 309 MXSG MASO Office or/CO/COR if a cardholder fails to comply with these requirements. In cases where the 309 MXSG MASO Office or/CO/COR is not immediately available or situations involving misuse, refusal to return the CAC, violence, or criminal behavior, the company must also notify the TA directly. In extreme cases the company must also notify Security Forces. NOTE: Unauthorized possession of a CAC can be prosecuted criminally under section 701 of Title 18, United States Code, which prohibits photographing or otherwise reproducing or possessing DoD identification cards in an unauthorized manner, under penalty of fine, imprisonment, or both. Invalid, inaccurate, inoperative, terminated, or expired CACs shall be returned to the CAC Issuer for disposition. The CAC is the property of the U.S. Government and shall not be retained by the cardholder upon expiration, replacement, or when the DoD affiliation of the employee has been terminated.

6.5 Security Incident

6.5.1 Should a security incident occur, the contractor shall: immediately report to the site location 309 MXSG SM all available facts related to each instance, take such precautions as the SM may reasonably require for security purposes, take reasonable and prudent…