OCS Tutors PWS Revised.pdf

PERFORMANCE WORK STATEMENT

FOR

OPERATIONAL CONTRACT SUPPORT (OCS) TRAINING INITIATIVE

“OCS TUTORS”

AT

BOLLING AFB, DISTRICT OF COLUMBIA

AFDW/PK

26 January 2024

Contents

SECTION I

1.0 DESCRIPTION OF SERVICES

1.1 General

1.2 Scope

1.3 Background

SECTION II

2.1 Task 1

2.2 Task 2

2.3 Task 3

2.4 Task 4

2.5 Task 5

SECTION III

3.0 SERVICE SUMMARY

SECTION IV

4.0 DELIVERABLES

SECTION V

5.0 GOVERNMENT FURNISHED PROPERTY OR SERVICES

SECTION VI

6.0 GENERAL INFORMATION

6.1 Scheduling Concerns

6.2 Kickoff/Orientation Meeting

6.3 Transition-In/Out Plan

6.4 Quality Control

6.5 Contractor Manpower Reporting Application (CMRA)

6.6 Security Instructions

6.7 Personnel, Employee Accountability and Turnover. ...... Error! Bookmark not defined.

6.8 Travel

6.9 Miscellaneous Paragraphs

SECTION VII

APPENDIX 1

1.0 DEFINITIONS, ABBREVIATIONS, AND ACRONYMS

2.0 ACRONYMS............................................................... Error! Bookmark not defined.

SECTION I

1.0 DESCRIPTION OF SERVICES

1.1 General. Headquarters, Air Force Contracting (SAF/AQC) and the Air Force District of Washington (AFDW) Contracting Office (AFDW/PK) is responsible for overseeing the execution and performance of Air Force Contracting Expeditionary Operations, which encompasses Operation Contract Support (OCS) functions, training, guidance and implementation, in accordance with this Performance Work Statement (PWS).

1.2 Scope. The requirement is for non-personal services for OCS tutor/trainers that will provide technical expertise and deliver tailored instruction and tutoring to Geographic Combatant Commands (GCC), Functional Combatant Commands (FCC), and Service Headquarters and component members to implement OCS capability.

This requirement will provide the training and curriculum materials to integrate OCS in the present force and propose a full spectrum doctrine, organization, training, material, leadership and education, personnel, and facilities (DOTMLPF) and capability solution framework to deliver more responsive and accountable OCS for the warfighter. The contractor shall provide all personnel, equipment, tools, materials, supervision, and quality control necessary, except as specified in Paragraph 5.0 as government-furnished, to perform OCS tutoring and instruction services as defined in this PWS.

The government requires tutoring/instruction services to guide, mentor, and train-the-trainer GCC/FCC and Service staff as applicable to address capability gaps related to the planning and integration of OCS into current and future operations.

Current OCS Capability Gaps for all DoD Components to be addressed by Tutors/Trainers:

1. Insufficient awareness of the significance and complexity of OCS.

2. Limited integration of OCS into task planning, assessments, training, and reporting.

3. Lack of strategy for total force manpower requirements for OCS-enabling functions.

4. Lack of personnel, manpower, rules, tools, and/or processes to integrate OCS into theater plans.

5. Insufficient ability to visualize, track, and monitor OCS capabilities in theater.

6. Lack of sufficient leadership oversight of OCS.

7. Lack of ability to identify contract vehicles and capabilities by region.

8. Inadequate capability to oversee contractor performance.

9. No common capability to generate acquisition-ready contract support requirements packages.

10. Lack of capability to identify contractors and control base access.

In accordance with Joint Publication 4-10 “OCS,” Boards, Bureaus, Centers, Cells, and Working Groups (B2C2WGs) are the forums for synchronizing and integrating OCS. There are three key boards critical for synchronizing and integrating contract support and contractor management.

OCS Tutor/Trainers will ensure designated staff/students have the knowledge, skills and abilities to integrate their efforts into the following:

1. Commanders Logistics and Procurement Support Board (CLPSB): Establishes contracting and contractor management guidance and procedures.

a. Identify contracting issues that may require guidance from GCC/FCC or Service components

b. Recommend theater-wide and/or Service component OCS guidance and procedures

c. Establish theater-wide and/or Service component contracting and contractor management procedures (theater business clearance, government furnished life support validation, Reception, Staging and Onward Integration (RSOI), contractor accountability)

d. Determine appropriate support capabilities (e.g., strategic contracts, Rapid Deployment Teams, expeditionary contracting officers) for employment and activation

2. Requirements Review Board (RRB): Vet, validate and prioritize requirements.

a. Review, validate, and prioritize requirements

b. Recommend acquisition methodology (e.g., existing capabilities, long-term contracting)

c. Provide visibility of planned or unplanned requirements for funding prioritization

d. Provide guidance for acquisitions related to use of US contractors, third country nationals, local nationals for force protection considerations, vendor vetting, vendor threat mitigation, cyber security

3. Contracting Support Board (CSB): Coordinate and de-conflict sourcing of requirements and key contracting efforts

a. Synchronize theater-wide and/or Service component contracting capabilities and activities to eliminate duplication of efforts

b. Determine appropriate contracting vehicles and sourcing solutions to include theater support and external support contracting, Economy Act, Interagency Agreements, FMS

c. Provide theater-wide and/or Service component forum for information exchange related to contracting capabilities/activities, sourcing solutions, contractor performance, impact to warfighters vendor threat mitigation, cyber security impact

d. Provide guidance on contracting efforts impacting warfighters’ global operations and analysis of the operational environment (i.e. market research, commercial business intelligence)

e. Review common operating picture of approved requirements, sourcing solutions, contracts, contracting capabilities/activities and force laydown, COR compliance, contractor management

The OCS tutors will focus their training on the acquisition and logistics workforce, and functional communities who contribute significantly to OCS by their assigned duties.

The contractor shall furnish the necessary services and provide qualified personnel to address current OCS capability gaps, identified above, to plan and integrate OCS into operations and training. The contractor will provide personnel whose collective experience includes in-depth expertise and knowledge in acquisition, logistics, planning, operations, and program management.

1.3 Background. Operational Contract Support (OCS) is an emerging Department of Defense (DoD) capability that recognizes that we have been, and will be, heavily reliant on contracted support for a wide variety of capabilities that span the strategic-operational-tactical continuum.

OCS is how we plan for, procure, and manage contracted support in a coordinated and synchronized manner. OCS is generally executed by Combat Support Agencies (CSA) and Combatant Command (CCMD) staffs, subordinate unit staffs, Service (Army, Navy, Air Force, Marine) staffs and theater special operations commands (TSOC). The DoD recognizes OCS is a critical operational enabler and has directed these organizations to develop an enduring capability and training to ensure OCS viability in planning and operations. Planned and executed correctly, OCS provides increased operational reach and flexibility for Joint Force Commanders. The Defense Logistics Agency (DLA) provided some OCS capabilities to these organizations to mitigate shortfalls. However, DLA support is being discontinued. This PWS provides a measure for organizations to contract subject matter expertise to assist in their OCS functions, principally in a training and mentoring capacity.

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 following section specifies the train-the-trainer Mission Essential Tasks for GCC/FCC and Service requirements (as applicable).

2.1 Task 1 - Tutor, train, mentor, and advise GCC/FCC, Service component and TSOC staffs on OCS tasks as identified below. (See APPENDIX 1 for references)

2.1.1 - General OCS Competencies

• Conducting OCS Crisis Action Planning (CAP)

• Conducting OCS deliberate planning

• Operating an OCS Integration Cell (OCSIC)

• Conducting OCS Analysis of the Operational Environment

• Establishing OCS B2C2WGs and Integrating into other B2C2WGs

• Performing OCS Knowledge Management

• Advising on Managing Critical Contract Risk

• Advising on evolving Vendor Threat Mitigation (VTM) processes

• Coordinating OCS with Lead Service for Contract Coordination/Lead Service for

Contracting (LSC/LSCC/LSC)

• Advising on and applying OCS doctrine and policy

• Performing Contractor Management

2.1.2 - OCS Tasks: For all Military Service tutor/trainers, train on factors of OCS:

• Establish OCSIC after receipt of WARNORD that initiates Crisis Action Planning and/or after the receipt of EXORD/DEPORD

• Identify core members of the OCSIC; establish initial roles/responsibilities for the core OCSIC members

• OCSIC support to CAP/OPT and the Joint Operations Planning Process

• Developing the Contractor Management Plan (CMP) (Annex W) and preparing to publish

• Ensuring the CMP contains all appropriate elements IAW CJCSM 3130.03A formats

• Collecting OCS operational environment data/info as part of the CAP and deliberate plans

• Coordinate contract support requirements from the CSOR with designated Base

Operating Support (BOS), and the /LSC/LSCC in accordance with LSC/LSCC’s established business rules and reporting requirements

• Utilize LSC/LSCC during CAP to provide OCS operational environment information and data

• Advise on how to establish risk mitigation plan for all critical contracts

• Establish/use OCS Knowledge Management Plan (OCSKM)

• Identify and assigned roles and responsibilities ISO OCSKM tasks

• Prepare OCSIC 7 minute drill on Foreign Vendor Vetting (FVV)/Intelligence-based

Vendor Threat Mitigation (IVTM) for mission command consideration in its battle rhythm/B2C2WG.

• Analyzing the battle rhythm/establishing appropriate B2C2WG with business rules/operations procedures that integrate with other higher-level B2C2WG

• Identifying theater-specific OCS concerns/issues so that they understand how to insert OCS aspects of the Operational Environment and capabilities seamlessly into the Warfighters’ standard operating procedures and battle-rhythm events.

2.2 Task 2 - Implement a framework (i.e. strategy) for the planning, integration, management, and execution of contract support no later than 180 days from contract start.

(See APPENDIX 1 for references)

2.3 Task 3 - Develop curriculum that enable GCC/FCC and Services to train-the-trainer to develop Logistics Supportability Analysis (LSA) for OPLANS and CONPLANS, guidebooks, handbooks, and SOPs relating to OCS no later than 180 days from contract start. (See APPENDIX 1 for references)

2.4 Task 4 - Attend GCC/FCC and Service component exercises; and tutor, train, mentor, and advise personnel at the exercises. A monthly report of each exercise participation will be submitted to the COR.

2.5 Task 5 - Provide a detailed monthly report on the 5th of each month, explaining the training activities and completed tasks, to include training curriculum. The monthly status report shall include, at a minimum the following information:

• The collection and analysis of data pertaining to the various components of OCS (e.g.

requirements determination, contract support integration, contracting support, and contractor management, etc.)

• Identification of project development and efforts with GCC/FCC and Service component stakeholders to identify problems or opportunities that may lend themselves to process improvements for greater effectiveness and efficiency

• Analytics/metrics on data from the RRBs, CLPSBs, CSBs), or other OCS B2C2WGs and other OCS-related data when provided by the government to assess the effectiveness of OCS doctrine, existing processes, and best practices.

• Any best practices, observations, insights, and lessons learned (BPOILS) within the training curriculum (refer to TECHNICAL EXHIBIT 1, “Performance Requirements Services Summary” and TECHNICAL EXHIBIT 3, “Deliverables Schedule.”

SECTION III

3.0 SERVICE SUMMARY

The Contractor service requirements are summarized into performance objectives that relate directly to mission essential items The performance threshold briefly describes the minimum acceptable levels of service required for each requirement and will be assessed on an “Acceptable” or “Unacceptable” basis. These thresholds are critical to mission success.

SECTION IV

4.0 DELIVERABLES (Technical Exhibit 3)

FAR clause 27.403, Deliverables shall be submitted to the COR designated in the COR appointment letter. The Government shall have unlimited rights to all deliverables, including training materials, reports and evaluation data. All deliverables shall be submitted using Microsoft Office suite of tools (for example, MS Word, MS Excel, MS PowerPoint), or Adobe PDF format, unless otherwise specified by the COR. Electronic submission shall be made via email, unless otherwise agreed to by the COR.

The COR has the right to reject or require correction of any deficiencies found in the deliverables. In the event of a rejected deliverable, the contractor will be notified in writing by the COR of the specific reasons for rejection.

SECTION V

5.0 GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, MATERIAL,

INFORMATION, OR SERVICES

5.1 Government Furnished Property, Equipment, Material, Information, or Services. The contractor shall be furnished current task working papers, project descriptions, program-briefing material, and other pertinent information, and other documentation or material required to carry out the tasks described hereunder. The government will provide the contractor with all of the information needed for performance including desired formats and, where existent, samples, as requested. Electronic information will be provided by and returned to the government wherever possible. The government will furnish subject matter experts as needed and available. The government shall provide the following property for contract operations. The property shall be used only in direct performance of contract requirements.

5.2 Property Accountability. FAR Clause 52.245-2, Government Property, is incorporated by reference. That clause and Part 45.5 of the FAR shall govern the use and accountability of government furnished property, subject to the following:

The government reserves the right of access to the government-furnished property. Contractor liability for joint use property will be restricted to validated damage, theft, or negligence resulting from contractor performance.

Contractor shall prepare inventory listings within 15 days from start of period of performance.

Throughout the performance period, the contractor shall ensure that the property inventory listing is current, complete, and accurate.

5.3 Government Furnished Property (On-Site/Off-Site Contractor Personnel)

The requirements of this PWS will be performed at a mix of locations between the contractor’s site, DoD component locations both domestic and overseas and other worldwide government facilities. This mix of locations will change over time as the program matures. Government furnished property or facilities are needed:

• Office space and related utilities appropriate for the number of positions, information to be stored, and equipment to be used in performance of the contract (on-site only).

• Office furniture appropriate for performance of the contract (on-site only).

• Computer hardware, software, networks, systems, and related technology, as necessary, to perform the requirements of the contract.

• Information, manuals, instructions, folders, and other data required to perform the requirements of the contract.

• Telephones and communications systems (on-site only).

Requests for additional Government furnished property shall be submitted in writing to the COR for consideration. The government will approve or disapprove within five business days of receipt.

5.4 Contractor Acquired Property. The contractor will not be required to acquire any property.

5.5 Government Furnished Services. The government shall provide the following services necessary for contract operations: Access and logon IDs as required for networks and other applications. (Note: The government's provision of these services shall not, however confer government civilian personnel status on contractor recipients.)

SECTION VI

6.0 GENERAL INFORMATION

6.1 Scheduling Concerns.

6.1.1 Duty Hours. The Contractor shall have access to Government facility five days per week, Monday through Friday, eight hours a day, except when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings, unless otherwise approved. Contractor personnel are expected to conform to customer agency normal operating hours; however the Contractor may be required access to Government facility outside of duty hours based on the customer agency’s needs. As a baseline, Contractor personnel shall work 8 hours per day, 40 hours per week. Compensatory time arrangements are permissible for temporary spikes in worktime; but overtime pay is prohibited without COR and CO approval. Federal Holidays shall be observed in accordance with Office of Personnel Management policy.

6.1.2 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.1.3 Performance Location. Performance shall be at the locations specified in TE 2. The contractor shall at all times maintain an adequate work force for the uninterrupted performance of all tasks defined within this PWS when the government facility/installation is not closed for the above reasons. When hiring personnel, the contractor shall keep in mind that the stability and continuity of the work force are essential. There will be some travel to different locations as part of this requirement. OCS tutor performance at a GCC/FCC, Service Headquarters or component shall be limited to OCS-related functions and tasks.

6.1.4 Telework. The government may permit telework by contractor employees when determined to be in the best interest of the government in meeting work requirements. The contractor shall have an established telework program subject to review by the government. All telework agreements will be authorized and approved by the COR and include the date, time, and description of the tasks to be performed. In furtherance of Continuity of Operations Planning (COOP), a telework program may be enacted to ensure the government's mission-critical operations stay operational during times of national emergency or incidents of national significance. The COR must identify to the contracting officer any tasks that are required to ensure continuity of critical supplies and services, and at what level those supplies and services must be delivered. Telework shall be at no additional cost to the government.

6.2 Kickoff/Orientation Meeting

At the direction from the Contracting Officer, 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 http://www.opm.gov/status/ procedures. At a minimum, the attendees shall include key Contractor personnel, AFDW/PK, SAF/AQC, HAF/A4L, key Government representatives, and the COR. The Contractor shall provide a Kick-Off Meeting Agenda that may include up to, but not be limited to, the following:

• Introduction of personnel, primary POCs

• Overview of project tasks

• Review of organization (complexity)

• Schedule (shows major tasks, milestones, and deliverables; planned and actual start and completion dates for each)

• Communication Plan/lines of communication overview (between both

Contractor and Government)

• Discussion of draft Program Management Plan (PMP)

• Travel notification and processes

• Government-furnished information (GFI)

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

• Analytical Support Status Accreditation (ASSA) Documentation

• Invoice procedures

• Monthly meeting dates

• Reporting Requirements, (e.g. Monthly Status Report (MSR))

• Roles and Responsibilities

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

• Prioritization of Contractor activities

• Any initial deliverables

• Other logistic issues

• Quality Control Plan (QCP)

• Sensitivity and protection of information

• Additional issues of concern (Leave/back-up support)

The Contractor shall provide a draft copy of the agenda NLT 3 days after contract award for review and approval by the COR prior to finalizing. The Government will provide the Contractor with the number of participants for the kick-off meeting and the Contractor shall provide sufficient copies of the presentation for all present.

The Kickoff Meeting location will be determined at the time of award and facilitated by the Government, either at a physical location or through virtual means; the date and time will be mutually agreed upon by both parties.

6.3 Transition-Out Plan.

The Contractor shall provide a Transition-Out Plan NLT than 60 calendar days prior to expiration of the contract. The plan shall facilitate the accomplishment of a seamless transition from the incumbent to and incoming Contractor (if applicable). In addition, the Contractor will continue to accomplish all tasks as outlined in the contract during this period.

6.3.1 Phase-out. The contractor shall maintain complete documentation that is totally assessable to the designated government representatives via a web portal or some other portal as the government directs. The contractor shall overlap with incoming contractor during transition for a nominal period of 30 days and will work with government personnel and the incoming contractor to transfer knowledge, information, and documentation for all projects and tasks related to this contract.

The Contractor shall identify how it will coordinate with the incoming Contractor and Government personnel to transfer knowledge regarding the following:

• Project management processes

• Points of contact

• Location of technical and project management documentation

• Status of ongoing technical initiatives

• Transition of key personnel

• Schedules and milestones

• Actions required of the Government

• Coordination of IT related programs, issues

All automated data files in the possession of the contractor are the property of the government and shall be turned over to the contracting officer or the COR at the completion or termination of the contract. Additionally, all records related to the execution of the current contract shall be returned to the government as electronic copies that are readable and accessible by the government.

The Contractor shall also establish and maintain effective communication with the incoming Contractor and Government personnel for the period of the transition via weekly status meetings.

Current employees under this contract may be interviewed for possible employment by a succeeding Contractor; however, the Contractor will have the first right of refusal. The current Contractor will release any employee who chooses to be employed by a succeeding Contractor.

The current Contract will assist by orienting assigned employees of the succeeding Contractor during the last 30 days of the period of this contract, if so directed by the CO. The Government shall make available to such employees existing Government Furnished Property listed under Section V of this PWS. Items that are not accountable, such as desks, chairs, telephones, and other normal office equipment and office supplies during the orientation period, will only be transferred to the incoming Contractor if items were solely purchased by the current Contractor’s company.

6.3.2 Transition-In Plan. The Contractor shall provide a Transition-In Plan at the Kickoff Meeting, the plan shall facilitate the accomplishment of a seamless transition from the incumbent Contractor (if applicable) and incoming Contractor. The contractor shall follow its transition plan submitted as part of their proposal and keep the government fully informed of status throughout the transition period. Throughout the phase-in/phase-out periods, it is essential that attention be given to minimize interruptions or delays to work in progress that would impact the mission. The contractor must plan for the transfer of work control, delineating the method for processing and assigning tasks during the phase-in/phase-out periods. If there is a change in contractor or if the operation reverts to the DoD, the contractor shall provide transition services and a phase in/out orientation. The phase in/out orientation shall begin as soon as possible after new contract award or changeover is directed to ensure continuity of operations. During the phase-in/out orientation period, the incumbent contractor shall be fully responsible for performance requirements and cooperate to the extent required to permit an orderly changeover to the successor.

The Contractor shall identify how it will coordinate with the incumbent Contractor and Government personnel to transfer knowledge regarding the following:

• Include a timetable on when all transition events will occur

• How all procedures and operating processes will be communicated to the personnel taking over those duties

• How knowledge transfer will occur to personnel taking over duties

• Points of contact

• Descriptions and locations of all applicable documentation

• Status of ongoing technical initiatives

• Transition of key personnel

• Schedules and milestones

• Actions required of the Government

• Coordination of IT related programs, issues

Specific transition details and additional information would be provided in the appropriate Task Order.

6.3.3 Phase-in. The contractor shall submit a detailed phase-in plan to include start-up activities that may be required to transition to full operational capability upon conclusion of the transition period.

The contractor shall:

• Provide a detailed transition methodology in logical sequence to ensure a smooth transition of all tasks/subtasks of the contract without interruption or degradation of service levels;

• Provide a timeline for completion; and

• Identify associated risks and issues and risk mitigation strategies.

The Contractor shall also establish and maintain effective communication with the incumbent Contractor and Government personnel for the period of the transition via weekly status meetings per the COR’s direction.

6.3.4 Post-Award Conference/Periodic Progress Meetings. The contractor agrees to attend any post award conference convened by the contracting officer in accordance with Federal Acquisition Regulations Subpart 42.5. The contracting officer, COR, and other government personnel, as appropriate, may meet periodically with the contractor to review the contractor’s performance. At these meetings, the contacting officer will apprise the contractor of how the government views the contractor’s performance, and the contractor shall apprise the government of problems, if any, being experienced. The contractor shall resolve outstanding issues raised by the government. Contractor attendance at these meetings shall be at no additional cost to the government.

6.4 Quality Control.

6.4.1 Quality Assurance. The government will evaluate the contractor’s performance under this contract in accordance with the QASP. This plan is primarily focused on what the government must do to ensure that the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and acceptable quality level(s) (defect rate(s)).

6.4.2 Quality Control Plan (QCP). The contractor shall prepare and submit a DRAFT Quality Control Plan as part of their proposal. This plan shall describe the contractor’s methodology for quality assurance and compliance with the Deliverables and Performance Requirements Summary above. After award, the COR will notify the contractor of concurrence or required modifications to the QCP within 10 business days. The contractor shall make appropriate modifications within five business days of the COR’s notification and provide a revised QCP within five business days.

Once approved by the contracting officer, the contractor shall adhere to their Quality Control Plan (QCP).

The QCP shall document how the contractor will meet and comply with the quality standards specified in the PWS and Quality Assurance Surveillance Plan (QASP). At a minimum, the QCP must include a self-inspection plan, an internal staffing plan, and an outline of the procedures that the contractor will use to maintain quality, timeliness, responsiveness, customer satisfaction, and any other requirements set forth in this PWS.

6.4.3 Performance Requirements Services Summary. (See Technical Exhibit 1)

6.4.4 QUALITY ASSURANCE SURVEILLANCE PLAN (QASP).

A QASP will accompany the contract in a separate document and applies to all deliverables specified in the deliverables table for this task order.

6.5 Contractor Manpower Reporting Application (CMRA)

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 each 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 of each calendar year. The Contractor may direct questions to the CMRA help desk.

6.5.1 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.5.2 Subcontractor Management: The contractor shall be responsible for any subcontract management necessary to integrate work performed on this requirement and shall be responsible and accountable for subcontractor performance on this requirement. The prime contractor will manage work distribution to ensure there are no organizational conflicts of interest (OCI) considerations. Any plans for the contractor to utilize subcontractors must be presented to the contracting officer at the time of proposal submission.

6.5.3 Identification of Organizational Conflicts of Interest (OCI). If the contractor is currently providing support or anticipates support to a federal agency that creates or represents an actual or potential OCI, the contractor shall immediately disclose the actual or potential OCI in accordance with FAR Part 9.502. Disclosure may be made via memo on company letterhead and included under a separate tab in Volume I of the contractor’s proposal. The contractor is also required to complete and sign an OCI Statement in which the contractor (and any subcontractors) agrees to disclose information concerning the actual or potential conflict with any proposal for any solicitation relating to any work in the contract. All actual or potential OCI situations shall be handled in accordance with FAR Subpart 9.5.

6.5.3.1 To avoid any potential conflicts of interest, the contractor agrees that it may not restrict the conception, design, or configuration of its analyses, recommendations or findings in a manner that will favor any endeavors that are its separate marketing efforts or those of its affiliates, subordinates, or other commercial ventures.

6.5.3.2 The contractor company will not ask their employee for information regarding the location nor types of services, commodities, and construction that the employee is proposing or advising to the air component staff. The contractor employee will not divulge to the contractor company the location nor services, commodities, and construction efforts being planned for the operation.

6.6 Security Instructions. A DD Form 254, Contract Security Classification Specification, applies to this IDIQ. All task orders on this IDIQ support Top Secret (SCI/) tasks. Contractor personnel shall possess a Top Secret clearance with SCI eligibility prior to being issued a Common Access Card (CAC). There is one exception that pertains to Contractor personnel with an interim security clearance. Fingerprints must be complete, favorable and on file for validation by 11th Wing Information Protection office (this is only applicable for contractors providing supporting in the NCR, all other locations shall follow local procedures). All Contractor personnel must maintain the level of security required for their contracted duties for the life of the contract.

The security requirements are in accordance with the attached DD Form 254. Any extracts or use of such data shall require the Contractor to apply derivative classifications and markings consistent with the source from which the extracts were made in accordance with DoDM 5200.1

Volumes 1-4, Information Security Program, a manual for safeguarding classified information;

and Executive order 12356, Classified National Security Information. Pursuant to DoD 5220.22M; Chapter 6, Visits and Meetings; the contractor shall submit visit requests to applicable security managers (see task order CORs for security manager POCs). Contractor shall complete necessary documentation for sub-contractor(s) associated with each IDIQ holder.

DoD requires that all contractor personnel assigned to task orders must have attained a favorable outcome to the designated IT (aka Automated Data Processing (ADP)) investigative requirement, generally an ADP-III (IT-III). If personnel will need access to sensitive data, restricted system data (e.g., table data), an ADP-II (IT-II) will be required. IT-II access is required for personnel assigned to Technical Infrastructure and Architecture (TIA). The appropriate ADP access approval is required for their work assignment and to initiate work without undue delay upon task order award. Personnel on task orders must also have an active and current ADP-II (IT-II) prior to starting work on such task order.

The government will ensure prompt access to key government personnel and data required by the contractor in the conduct of this project. Delays in gaining access to data may require amending the delivery schedule.

6.6.1 OPSEC/SOP/Plan. The contractor shall develop an OPSEC Standing Operating Procedure (SOP)/Plan and provide it to the COR within 90 calendar days of contract award, as a deliverable under TE 3 to be reviewed and approved by the responsible government OPSEC officer, per AR 530-1, Operations Security. This SOP/Plan shall include the government's critical information, why it needs to be protected, where it is located, who is responsible for it, and how to protect it. In addition, the contractor shall identify an individual who will be an OPSEC Coordinator. The contractor shall ensure this individual becomes OPSEC Level II certified in accordance with AR 530-1.

6.6.2 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.6.3 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. The contractor is allowed unescorted access.

6.6.3.1 Access to Pentagon. Access to the Pentagon is covered by provisions of Administrative Instruction 30 (AI 30). Permanent Pentagon access is only authorized based on the individual’s employment in the Pentagon. Contractors are not given escort privileges, and are only permitted business hours only UNLESS their specific contract they work on requests escort privileges and or 24 hour access. In these cases, the task order COR/Security Manager would send in the PWS/Contract documents to prove justification. Contractors are only given permanent access aligned with their contract end date issued for a minimum of one month and for a maximum of three years, based on length of the contract. NOTE: All contractor applications must be validated by the Security Assistant’s using applicable documentation i.e. 254, VGSA, SOO/PWS, etc. All contractors must be serviced in JPAS by requesting organization. The current requirement for both permanent and temporary of requests is that 75 percent of an individual’s duties require access to the Pentagon or delegated facility. All requests must be processed by the Badging office within 10 business days of Authorizing Official’s signature. It is the Security Assistant’s and Authorizing Official’s responsibility to confirm/validate that an applicant has a legitimate requirement for access to buildings on the Pentagon Reservation and that they meet the 75% requirement.

6.6.4 Classified Material. The contractor shall comply with FAR Clause 52.204-2, Security Requirements. This clause involves access to information classified “Confidential,” “Secret,” or “Top Secret” and requires contractors to comply with The Security Agreement (DD Form 441) including the National Industrial Security Program Operating Manual (DoD 5220.22-M) and applicable updates/changes. The level of classification required for this requirement is TOP

SECRET.

6.6.4.1 Access to Classified and Sensitive Information. Elements of this project are categorized as classified at the Top Secret level and requires the contractor maintain a favorable Facility Clearance at the same or higher level of classification. This contract does not require the contractor to store, handle, process classified information at their facility.

The following security access/performance requirements are required in performance of this contract:

Requirement Supported Contract Task National Intelligence Information, Sensitive Compartmented Information (SCI) and Non-SCI

Task 4 requires Contractor to access Classified OPLANS and CONPLANS

Special Access Program (SAP) Information

Task 4 requires Contractor to access Classified OPLANS and CONPLANS

Alternative Compensatory Control Measures (ACCM) Information

Task 4 requires Contractor to access Classified OPLANS and CONPLANS

Have Operations Security (OPSEC) Requirements

Task 5 and 6.6.1 requires the Contractor complete OPSEC Training and develop OCSEC SOP

Receive, Store, or Generate Controlled Unclassified Information (CUI)

Task 5 requires Contractor to create an online collaborative environment between the CSA/Service Components.

6.6.5 Communications Security (COMSEC). Contractors may require access to COMSEC information on Air Force, Army or other DoD 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.6.5.1 Use of Government Information Systems (IS). Use of government Information Systems (IS) and access to government networks is a revocable privilege, not a right. Users are the foundation of the DoD strategy, and their actions affect the most vulnerable portion of the AEI. Contractor employees shall have a favorable background investigation or hold a security clearance and access approvals commensurate with the level of information processed or available on the system. Contractor employees shall:

a. Comply with the command's Acceptable Use Policy (AUP) for government-owned IS and sign an AUP prior to or upon account activation.

b. Complete initial and/or annual IA training as defined in the IA Best Business Practices (BBP) training (https://informationassurance.us.army.mil).

c. Mark and safeguard files, output products, and storage media per classification level and disseminate them only to individuals authorized to receive them with a valid need to know.

d. Protect IS and IS peripherals located in their respective areas in accordance with physical security and data protection requirements.

e. Practice safe network and internet operating principles and take no actions that threaten the integrity of the system or network.

6.6.5.2 Protection of Personally Identifiable Information (PII). The contractor shall protect all Personally Identifiable Information (PII) encountered in the performance of services in accordance with DFARS 224.103 and DoDD 5400.11, Department of Defense Privacy Program, and DoD 5400.11-R. If a PII breach results from the contractor’s violation of the aforementioned policies, the contractor shall bear all notification costs, call-center support costs, and credit monitoring service costs for all individuals whose PII has been compromised.

6.6.6 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. All contractor personnel will be required to obtain and wear badges in the performance of this contract. Contractor personnel shall wear identification badges distinguishing themselves as such. The badges shall have the company name, employee name, and the word “contractor” displayed. The contractor shall retrieve all identification media (including vehicle passes) from their employees who depart employment for any reason. All identification media (i.e., badges and vehicles passes) shall be returned to the COR within 14 days of an employee’s departure. A control mechanism for all badges issued will be a deliverable under TE 3. The contractor shall ensure that all documents or reports produced by contractor personnel are suitably marked as contractor products or that contractor participation is appropriately disclosed. The contractor’s status as a “contractor” shall be predominantly displayed in all correspondence types

(to include signature blocks on e-mail) and dealings with government or non-government entities.

6.6.6.1 Key Control/Key Cards. The contractor shall establish and implement methods of ensuring all keys/key cards issued by the government are not lost or misplaced and are not used by unauthorized persons. NOTE: All references to keys include key cards. No keys issued by the government shall be duplicated. The contractor shall include procedures covering key control in the QC Plan. Such procedures shall include turn-in of any issued keys by personnel who no longer require access to locked areas. The contractor shall immediately report any occurrences of lost or duplicated keys/key cards to the COR.

In the event keys, other than master keys, are lost or duplicated the contractor shall, upon direction by the contracting officer, re-key or replace the affected lock or locks; however, the government, at its option, may replace the affected lock or locks or perform re-keying. When the replacement of locks or re-keying is performed by the government, the total cost of re-keying or the replacement of the lock or locks shall be deducted from the monthly payment due the contractor. In the event a master key is lost or duplicated, all locks and keys for that system shall be replaced by the government, and the total cost deducted from the monthly payment due the contractor.

The contractor shall prohibit the use of the government issued keys/key cards by any persons other than the contractor’s employees. The contractor shall prohibit the opening of locked areas by contractor employees to permit entrance of persons other than contractor employees engaged in the performance of services in those areas, or personnel authorized entrance by the contracting officer.

6.6.7 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.6.8 Traffic Laws. The Contractor and its employees shall comply with base traffic regulations.

6.6.9 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 working on or visiting any military facility.

6.6.10 Contractor Identification. All Contractor personnel shall wear the appropriate Air Force or other Government issued Common Access Card (ref 6.6.10.1) 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.6.10.1 Common Access Card (CAC). The CAC is the DoD Federal Personal Identity Verification (PIV) credential. In accordance with Directive Type Memorandum (DTM) 08-003, December 1, 2008, incorporating Change 5, October 8, 2013, initial issuance of a CAC requires at a minimum, the completion of FBI fingerprint check with favorable results reflecting "No Record" and submission of a National Agency Check with Inquiries (NACI) to the Office of Personnel Management (OPM), or a DoD-determined equivalent investigation. The issuance of a CAC will be based on four criteria; (a) eligibility for a CAC; (b) verification of DoD affiliation from an authoritative data source; (c) completion of background vetting requirements according to the Federal Information Processing Standards Publication 201-1, Personal Identity Verification of Federal Employees and Contractors, March 2006, and DoD Regulation 5200.2-R, Department of Defense Personnel Security Program, January 1987, and (d) verification of a claimed identity. CAC eligible personnel must be registered in the Defense Enrollment Eligibility Reporting System (DEERS) through either an authoritative personnel data feed from the appropriate Service or Agency or Trusted Associate Sponsorship System (TASS).

6.6.11 HSPD-12 Background Investigation Requirements. All contract or subcontract personnel assigned to work on the government site and by personnel requiring access to a DoD network who require CACs (and other eligible populations as specified in DTM-08-003 Attachment 3, paragraph 3a.) are required to, at a minimum, have received a favorable FBI fingerprint check and must have submitted to the OPM a NACI or equivalent/higher investigation. It is the responsibility of the contractor to ensure that all employees requiring an initial background investigation complete a Personnel Security Investigation Portal (PSIP) form at the earliest possible date and that this form is forwarded to the COR immediately. The COR will review the form for completeness and accuracy, and forward to the NGB Personnel Security manager who will initiate the investigation process via the PSIP. Contractor personnel will then receive two e-mail messages; the first will confirm that the request has been received by the OPM, and the second will provide instructions for the completion of the appropriate form via the Electronic Questionnaires for Investigations Processing (e-QIP) system.