HQs_USAF_OASIS_Plus_PWS_DRAFT_20240724.docx

TASK ORDER

PERFORMANCE WORK STATEMENT (PWS)

FOR ACQUISITION, BUSINESS, SCIENTIFIC AND LOGISTICS SUPPORT SERVICES

Part 1 General Information

1. General:

This is a non-personal service(s) task order to provide the Joint Program Executive Office for Chemical, Biological, Radiological and Nuclear Defense (JPEO- CBRND) Headquarters (HQ), and the United States Air Force (USAF) with acquisition, business, scientific and logistics services. Personnel rendering the service(s) are not subject, either by the contract’s terms or by the manner of its administration, to the supervision and control usually prevailing in relationships between the Government and its employees.

Offerors shall use this PWS as a reference to develop proposals, which should be written in compliance with the Instructions, Conditions, and Notices to Bidders (i.e., Section L) provided in the Request for Proposal (RFP).

This Task Order (TO) PWS shall be used as a basis for conducting business.

Terms, conditions, and requirements from the parent contract vehicle apply to this TO.

1.1 Description of Services/Introduction: To provide non-personal acquisition, business, scientific and logistics services to the JPEO-CBRND HQ and the USAF.

1.2 Background:

1.2.1 The scope of this TO was previously competed and awarded under the Multiple Award Indefinite Delivery Indefinite Quantity contract called Joint Enterprise – Omnibus Program, Engineering and Technical Support (JE-OPETS) and is now being competed under the One Acquisition for Integrated Services Plus (OASIS+) Contract Vehicle. This TO will provide continuity of services in support of the CBRND mission for the requiring office(s) specified in Part 5, Specific Tasks.

1.2.1 Mission: The JPEO-CBRND manages our nation’s investments in chemical, biological, radiological, and nuclear defense equipment, and medical countermeasures. The JPEO-CBRND leads, manages, and directs the acquisition, fielding, and sustainment of CBRN sensors, protective equipment, medical countermeasures, specialized equipment for U.S. Special Forces, integration and information management systems, and defense-enabling biotechnologies. The organization also works closely with various Government agencies that need CBRN defense equipment.

1.2.2 Need: The JPEO-CBRND HQ and the USAF require acquisition, business, scientific and logistics services to oversee and manage the portfolio CBRND programs under the JPEO-CBRND purview and provide continuity of services when the existing JE-OPETS TOs expire.

1.3 Scope:

1.3.1 This TO provides acquisition, business, scientific and logistics services to the JPEO-CBRND HQ and the USAF. The technical performance requirements for this TO are provided in Part 5, Specific Task.

1.3.2 The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items necessary to perform services as described in the PWS and associated contract documents, except for those items specified in Part 3 incidental Government Furnished Property (GFP). The contractor shall perform to the standards and acceptable quality levels identified in this PWS and associated contract documents.

1.3.3 This TO is for non-personal services. The Government shall neither supervise contract support personnel nor control the method by which they perform required tasks. It shall be the responsibility of the awarded contractor to manage its employees, through the assignment of a Site Supervisor on-site at each requiring office, to guard against any actions that are of the nature of personal services or give the perception of personal services. If the awarded contractor believes that any actions constitute, or are perceived to constitute, personal services, it shall be the awarded contractor's responsibility to notify the Contracting Officer (KO) or Contracting Officer’s Representative (COR) immediately.

1.3.4 Contractor employees performing services under this TO shall be controlled, directed, and supervised at all times by management personnel of the contractor. The contractor's Site Supervisor shall ensure that employees properly comply with the performance standards outlined in this PWS and as required by the KO or the COR. Contractor employees shall perform independent of and without the supervision of any Government official. Actions of contractor employees may not be interpreted or implemented in any manner that results in any contractor employee creating or modifying Federal policy, obligating the appropriated funds of the U.S. Government, overseeing the work of Federal employees, providing direct personal services to any Federal employee, or otherwise violating the prohibitions set forth in Parts 7.5 and 37.1 of the FAR.

1.3.5 The contractor shall not perform any inherently Governmental functions as defined by Federal Acquisition Regulation (FAR) Subpart 7.5. All program decisions shall be the sole responsibility of the Government. The contractor shall not counsel, mentor, make judgments or discretionary decisions or perform any other activities related to supervision of Government personnel. If the contractor believes that any actions constitute or are perceived to constitute inherently Governmental functions, the contractor shall notify the KO immediately.

1.4 Objectives: The primary objective of this TO is to provide performance-based support and a seamless transition of existing with acquisition, business, scientific and logistics services for the JPEO-CBRND HQ and the USAF. The contractor shall be responsible for providing staff that have the technical skills, certifications, security clearance level and experience to support the requirements of this task order.

1.5 General Information: The awarded contractor shall be responsible for all PWS requirements to include the performance of requirements by a subcontractor or partner company.

1.5.1 Quality Control Plan (QCP): The contractor shall develop and maintain a QCP to ensure services are performed in accordance with (IAW) CDRL A005 and this PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The contractor's QCP is the means by which it assures that the work provided complies with the requirements of the contract. Comment by O'Brien, Brenda S CIV USARMY DOD JPEO CBRND (USA): Updated CDRL Number

1.5.1.1 The contractor’s proposed QCP shall be submitted to the KO through the COR for review within ten (10) days after date of contract award. Comment by Andrew: CDRL Reference? Comment by O'Brien, Brenda S CIV USARMY DOD JPEO CBRND (USA): The reference is stated in the first sentence.

1.5.1.2 The Government will review and either notify the contractor in writing of acceptance of the plan or return their comments to the contractor. If the Government has provided comments, the contractor shall then have three (3) days to submit a final QCP. After receipt of the final QCP, the contractor may receive the KO’s acceptance in writing. Any proposed changes to the accepted QCP are required to be resubmitted for acceptance by the KO no later than thirty (30) days prior to the anticipated change and before implementation by the Contractor. The timeline noted above will apply for review and acceptance for proposed changes. At a minimum, the QCP must include and answer the following to be acceptable:

(a) A chart showing the organizational structure and lines of authority, the names, qualifications, duties, responsibilities, and classification of each member of the contractor's Quality Control Team;

(b) How the contractor will monitor work to ensure performance complies with all deliverables (etc. timelines, deadlines, and goals);

(c) How the contractor will monitor work to ensure performance complies with all specifications and requirements of the contract, including the contract’s clauses;

(d) How the contractor will monitor and ensure staff qualifications remain current and valid including Department of Defense (DoD) Contractor Personnel Office processes/approvals throughout contract performance;

(e) How the contractor will ensure all keys issued will remain controlled items (Paragraph 1.7 Key Control), if applicable;

(f) How the contractor will inventory and track maintenance of all incidental GFP/ Materials;

(g) How the contractor will identify, investigate, and correct any non-conforming performance and prevent similar deficiencies in the future; and

(h) How the contractor will file and save all Quality Control related documents for the life of the contract plus five (5) years.

1.5.1.3 An Analysis of Quality Control and Timeliness of Submittals (i.e. deliverables) shall be provided to the COR within thirty (30) days upon completion of each TO. Comment by Andrew: CDRL reference? Comment by O'Brien, Brenda S CIV USARMY DOD JPEO CBRND (USA): This is still part of CDRL A006

1.5.1.4 The contractor shall inform the COR of issues or potential issues that might affect the performance within twenty-four (24) clock hours of identifying those issues. Verbal reports shall be followed up by written reports within two (2) days. Comment by Andrew: Will this go in the COR file? Comment by O'Brien, Brenda S CIV USARMY DOD JPEO CBRND (USA): Yes

1.5.2 Quality Assurance:

1.5.2.1 The Government shall evaluate the contractors’ performance in accordance with the Quality Assurance Surveillance Plan (QASP). The QASP is primarily focused on what the Government must do to ensure that the contractor has performed IAW the performance requirements/standards. It defines how the performance requirements/standards will be applied, the frequency of surveillance, and the acceptable defect rate(s). The Government reserves the right, at its sole discretion, to change or increase the methodology and/or frequency of surveillance at any time. In which case, the contractor shall provide all access requested by the Government.

1.5.2.2 Government Remedies: The contractor shall be responsible to address and correct performance and compliance issues.

1.5.2.3 Issue Resolution Steps: The intent is to resolve issues at the lowest possible level. If the Government experiences an issue (i.e. performance, non-compliance) with the contractor, the COR will work with the contractor Site Supervisor to achieve immediate resolution. If the issue persists greater than two (2) weeks, the COR will provide a Memo for Record (MFR) documenting the performance issue(s) to the KO who will formally submit the MFR to the contractor for review and resolution. The Contract Manager shall provide the Government a resolution plan within three (3) business days of receiving the MFR, detailing how the performance issue(s) will be resolved as quickly as possible. A status update meeting will be held two (2) weeks after the Government receives the contractor’s resolution plan. After thirty (30) days, the COR will document the success or failure of the resolution plan. In the case of failure, the issue is elevated to the KO for further resolution.

1.5.3 Recognized Holidays: The following provides information on recognized holidays for the purpose of the PWS. If submittal of any documentation (e.g. deliverables, submittals, etc.) deadlines fall on a holiday, the closest workday prior to the holiday will apply as the deadline for submittal.

1.5.3.1 U.S. Holidays:

1.5.3.1.1 Work shall not be performed on U.S. federally recognized holidays occurring during the normal workweek unless otherwise directed by the KO. When a U.S. holiday occurs on a Saturday or a Sunday, the holiday is observed on the preceding Friday or following Monday, respectively.

Juneteenth Independence Day Labor Day Columbus Day Veteran’s Day Thanksgiving Day Christmas Day

1.5.3.1.2 On-site technical work efforts shall be performed in Government office space as specified in Part 5, Specific Task. On-site contractor support personnel will reside in assigned Government facilities, except on Federal holidays or when the Government facility is closed due to local or national emergencies (e.g., weather, etc.), administrative closings, or similar Government-directed facility closings (e.g., Government shutdown, etc.). In such cases, including any Federal holiday(s) not recognized by the awarded contractor, alternate work procedures and locations shall be established by the contractor for on-site support personnel.

1.5.3.2 Host Nation Holidays: Work requirements for host nation holidays will be established when applicable to the TO.

1.5.4 Operating Hours: The Government facility office hours, facility operating hours, and the contractor support hour requirements often coincide, however, they may differ. Please refer to the following.

1.5.4.1 Government Facility Office Hours: RESERVED

1.5.4.2 Government Facility Operating Hours: The Government facility operating hours vary pending location and organization, but normally occur between the hours of 0600 to 1800 daily. The Government facility may close due to local or national emergencies, administrative closings, or similar Government directed facility closings and will be communicated by the KO to the contractor.

1.5.4.3 Contractor Support Hours:

1.5.4.3.1 The contractor shall provide support during normal/core work hours Monday through Friday, except Federal holidays identified in paragraph 1.5.3.1.1 above or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. Government workday core hours are between 0900 and 1500 daily. This may vary depending on organization and location and may be specified differently.

1.5.4.3.2 The contractor shall maintain an adequate, qualified workforce that meets the requirements of this TO at all times, for the uninterrupted and successful performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons. When hiring personnel, the contractor shall keep in mind that the stability and continuity of the workforce is essential. For other than Firm Fixed Price Contracts, the contractor will not be reimbursed when the Government facility is closed for the above reasons.

1.5.4.3.3 The contractor shall remove (permanent or temporary) personnel for security, safety, or health reasons, upon discovery of fraudulent credentials/qualifications, or when contractor personnel behave in an unprofessional manner that would be considered unacceptable by a reasonable person.

1.5.4.3.4 The contractor shall respond to Government requests for contractual actions within one (1) business day. The contractor shall adhere to all schedule timelines, milestones, delivery schedules and administrative requirements that contribute to, or effect schedule variance, to include scheduled on-time delivery of reports, data products, billing invoices, staffing of personnel, and action items.

1.5.4.3.5 The contractor shall successfully integrate and coordinate all activity needed to execute the TO. These activities include timeliness, completeness and quality of problem identification, corrective action plans, proposal submittals, timely identification of issues in controversy, effective/responsive management of subcontractors, customer satisfaction, and professional and ethical behavior of the contractor management personnel.

1.5.4.3.6 The contractor shall be responsible for any subcontract management necessary to integrate work performed on this TO and shall be responsible and accountable for subcontractor performance.

1.5.4.3.7 Under no circumstances will the contractor personnel providing support in CONUS exceed a forty (40) hour work week without prior written authorization from the KO. Deployed individuals (OCONUS) may be required to work other than core hours in support of mission requirements and are authorized to exceed a forty (40) hour work week; however, hostile fire and hardship pay differentials apply only to the forty (40) hour work week.

1.5.4.3.8 Surge Support: Surge support requirement is defined as short term work to support mission activities in order to meet urgent customer needs. Because of its nature, surge support needs cannot be forecasted far into the future. This type of support is typically needed because of schedule changes, system requirements updates, adverse test results, and other unforeseen or unplanned events. As such, surge support is usually needed "at the last minute." Often times, the need for surge support is satisfied by allowing contractor personnel to simply work more than the normal forty (40) hours per week (i.e., "overtime"). The contractor must ensure they can provide this type of flexibility and support without the need to modify the existing PWS or contract. In other words, surge support should not be considered a "new requirement" for a program that needs it.

1.5.4.3.9 A Compressed Work Schedule (CWS) may be used on a case-by-case basis as long as contract performance and the Government mission and requirements are not adversely impacted. Contract support personnel identified to support a CWS shall maintain performance at an effective level, accomplishing all assigned tasks. Prior to initiation of a CWS, the Site Supervisor shall coordinate a written CWS plan and work schedule with the COR. The COR and Government Lead may identify potential performance risks of the CWS plan and schedule to the contractor. The contractor shall ensure successful contract performance when CWS is used, and any performance issues must be addressed and corrected immediately.

1.5.4.4 Reserved

1.5.5 Training Holidays (if applicable): Reserved

1.5.6 Place of Performance:

1.5.6.1 The place of performance is specified in Part 5, Specific Tasks.

1.5.6.2 Work will be performed at on-site or off-site locations as designated in Part 5 of this PWS. The contractor will ensure its employees under this contract have access to workspaces, computers, Local Area Network (LAN) accounts, access to telephone service, operating supplies, and other items and tools of the trade required for daily operations. Access to Government buildings, network accounts, and Common Access Cards (CACs) will be approved by the Government as deemed necessary to support TO.

1.5.6.3 In instances where support is required off-site, a specific support location will not be identified by the Government. However, off-site personnel shall be available via TEAMS, telephone and e-mail, and must be able to travel to the customer when required. All equipment must be authorized by the Government for use. Comment by Andrew: Teams as well? Comment by O'Brien, Brenda S CIV USARMY DOD JPEO CBRND (USA): Added TEAMS

1.5.6.4 On-site work shall be performed at the designated place of performance specified in Part 5, Specific Tasks. On a case-by-case basis, situational/ad hoc or recurring telework may be used with on-site work as long as contract performance and the Government mission and requirements are not adversely impacted. Operating costs associated with the contractor using an alternative worksite for telework will not be assumed by the Government. All equipment must be authorized by the Government for use. The contractor shall maintain availability during core hours via email and phone (and other means as required, such as MS Teams) and must be available and able to travel to the on-site performance location when required at no additional cost to the Government. All expenses for Internet, telephone connectivity, and other equipment services shall be borne by the contractor. At least ten (10) business days in advance of the start of recurring telework the contractor shall coordinate a written telework plan with the COR. The COR and Government Lead may identify potential performance risks of the coverage plan to the contractor. A telework plan is not required for situational/ad hoc telework. During all telework situations, the contractor shall ensure successful contract performance and management of their personnel. After telework begins, any performance issues must be addressed and corrected immediately. Classified work is not authorized under telework or the alternate worksite. Authorized telework or alternate worksite locations do not abrogate the contractor’s requirement for complying with the protection of information IAW DoD regulations, Security and Protection of Information sections of the PWS, contract clauses, or DD Form 254.

1.5.6.5 The contractor shall ensure that contractor personnel make every effort to conserve utility costs during performance of the tasks herein.

1.6 Security Requirements: The following information is provided on security related matters. This contract requires the handling and access to classified information.

1.6.1 Security Program: Classification requirements for this TO are specified in Part 5, Specific Tasks. The security requirements are IAW with the DoD Contract Security Classification Specification (DD Form 254), which is currently accessible at the following link: http://www.dtic.mil/whs/directives/forms/eforms/dd0254.pdf.

1.6.2 Personnel Security Clearance Requirements: The contractor’s employees performing work in support of this TO shall have been granted the level of security clearance required by the TO from the Defense Industrial Security Clearance Office as required to perform their assigned duties in accordance with the start of the TO period of performance.

1.6.2.1 The security requirements are IAW the DoD Contract Security Classification Specification DD Form 254. The contractor shall ensure that contractor employees and subcontractor employees performing services under this contract comply with FAR 52.204-2 Security Requirements when the employee has access to information classified “Confidential,” “Secret,” or “Top Secret.” The contractor shall ensure the employee complies with the DoD Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (DoD 5220.22-M), and any revisions to DoD 5220.22-M, notice of which has been furnished to the contractor.

1.6.2.2 The contractor holding this TO, and its employee(s), shall be responsible for coordinating with the COR whom serves as the Mission Partner Identity, Credential and Access Management (MP ICAM) Sponsor to obtain the required Common Access Card(s) (CACs), security clearances, country clearances, visas, work permits, installation access, and other employee-specific security requirements as necessary to achieve the operational and support objectives specified in this TO. Access is provided on a need-to-know basis and with the appropriate clearance for access to a particular system or facility.

1.6.2.3 For this TO, the contractor is required to receive, handle, and generate sensitive and classified information up to and including the TOP SECRET/Sensitive Compartmented Information (SCI) classification level. Access to sensitive and classified information requires a favorable security investigation resulting in an adjudication at or above the level required for each position, as specified in Part 5, Specific Task.

1.6.2.4 At the start of work, contract support personnel shall possess either an active or interim clearance at the level stated in Part 5, Specific Task. Any contract support personnel who start work with an interim Secret clearance must complete the investigation and be granted the full clearance to continue support. For positions that require a Top-Secret clearance to accomplish assigned tasks, the contractor shall also be required to possess a Top-Secret facility clearance. Contract support personnel assigned to a position requiring a Top-Secret clearance shall possess a Top-Secret clearance at start of work.

1.6.2.5 All contract support personnel shall maintain the appropriate level of clearance throughout the period of performance. The contractor shall provide all information required to substantiate the clearance level of its contract support personnel, as well as any additional information requested.

1.6.2.6 For contractor access to secure buildings or facilities or if a contractor shall have access to, generate or store classified material, a DD Form 254 to specify the requirements will be provided. Contractors shall possess the facility clearance at the highest level of classification required in Part 5, Specific Task, before submitting a TO proposal. The contractor shall provide all information required to substantiate the clearance level of its contract support personnel, as well as any additional information requested by the JPEO-CBRND Security Office or other CBRND Enterprise Security Office.

1.6.2.7 PIV Compliance:

1.6.2.7.1 The contractor shall ensure its workforce complies with all PIV requirements. For individuals working for DoD, the PIV credential is the CAC. Contract personnel will be required to obtain a CAC prior to start of work as prescribed in accordance with the policies and procedures implementing the HSPD-12. As such, the investigative and adjudicative requirements that must be completed prior to issuing of a CAC will vary depending upon the level required by requirement and position specifications. The Government will provide CACs via the Defense Manpower Data Center (DMDC) Mission Partner Identity, Credential and Access Management (MP ICAM) application.

1.6.2.7.1.1 In order for the government to issue a CAC to contractor personnel, an FBI fingerprint check with favorable results and submission of National Agency Check with Inquiries (NACI) or Tier 1, 2, or 4 investigation must be completed in accordance with Army Directive 2014-05.

1.6.2.7.1.2 All contractors that require access to controlled facilities and/or federally controlled information systems shall adhere to HSPD-12 policy.

1.6.2.7.2 The contractor employee will be issued a CAC only if duties involve one of the following: (1) both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2) remote access, via logon, to a DoD network using DoD-approved remote access procedures; or (3) physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the Federal Bureau of Investigation (FBI) fingerprint check and a successfully scheduled NACI at the Office of Personnel Management.

1.6.2.7.3 Justification shall be included with each request for a CAC, and the requiring offices to which contract support personnel are assigned will sponsor all CAC registrations and renewals. CAC activation periods will coincide with the TO period of performance.

1.6.2.7.4 All personnel issued a CAC shall maintain possession of it at all times. CACs shall not be left unattended. The CAC shall not be used in temporary badge exchanges and CAC pin numbers shall not be shared with anyone. CACs are the property of the U.S. Government and shall be returned to the Government (i.e., security personnel) upon termination of employment, expiration or replacement of the CAC, or upon contract completion. The loss of a CAC shall be reported on the first business day following the discovery of the lost CAC, to the COR or local Security Office and to the issuing agency.

1.6.2.8 For contractors that do not require a CAC but require access to a DoD facility or installation. Contractor and all associated subcontractor employees shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification Index (NCIC-III) and Terrorist Screening Database (Army Directive 2014-05/AR 190-13); applicable installation, facility and area commander installation/ facility access and local security policies and procedures (provided by Government representative); or, at OCONUS locations, in accordance with status-of-forces agreements and other theater regulations.

1.6.2.9 Access and General Protection/Security Policy and Procedures: The \contractor and all associated sub-contractor employees shall comply with applicable installation, facility, and area commander installation and facility access and local security and safety policies and procedures.

1.6.2.10 The contractor and all associated subcontractor employees shall provide all information required for background checks to meet installation access requirements to be accomplished by the installation Provost Marshal Office, Director of Emergency Services, or Security Office. Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contract Personnel) as directed by DoD, HQDA and local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

1.6.2.11 For contractors Authorized to Accompany the Force: Defense Federal Acquisition Regulation (DFARS) Clause 252.225-7040, Contractor Personnel Authorized to Accompany U.S. Armed Forces Deployed Outside the United States, shall be used in solicitations and subsequent TOs that authorize contractor personnel to accompany U.S. Armed Forces deployed outside the U.S. in contingency operations; humanitarian or peacekeeping operations; or other military operations or exercises, when designated by the combatant commander. The clause discusses the following Antiterrorism and Operations Security (AT/OPSEC) related topics: required compliance with laws and regulations, pre-deployment requirements, required training (per combatant command guidance), and personnel data required.

1.6.2.12 For Contracts Requiring Performance or Delivery in a Foreign Country: DFARS Clause 252.225-7043, Antiterrorism/Force Protection for Defense Contractors Outside the US, shall be used in solicitations and subsequent TOs that require performance or delivery in a foreign country. This clause applies to both contingencies and non-contingency support. The key AT requirement is for non-local national contractor personnel to comply with theater clearance requirements and allows the combatant commander to exercise oversight to ensure the contractor’s compliance with combatant commander and subordinate task force commander policies and directives.

1.6.2.13 For Contracts That Require Handling or Access to Classified Information: Contractor shall comply with FAR 52.204-2, Security Requirements. This clause involves access to information classified “Confidential,” “Secret,” or “Top Secret” and requires contractors to comply with (1) the Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (DoDI 5220.22-M); (2) any revisions to DOD 5220.22‐M, notice of which has been furnished to the contractor.

1.6.2.13.1 If secure telecommunication requirements apply, clause 252.239-7016 and follow guidance at 239.74 apply.

1.6.2.13.2 If covered system support requirements apply, provision 252.239-7017 and clause 252.239-7018 apply to the contract, and follow guidance at 239.73.

1.6.3 Installation Access: Access to U.S. installations, buildings and controlled areas is limited to personnel who meet security criteria and are authorized by Host Nation law to work in that country. Failure to submit required information/data and obtain required documentation or clearances will be grounds for denying access to U.S. installations, buildings and controlled areas. The contractor shall ensure that any subcontractors used in performance of this contract complies with these requirements and that all employees, of both the contractor and any subcontractor utilized by the contractor, are made aware of and comply with these requirements.

The contractor shall be aware of and comply with the requirements associated with Installation Access Control. The Government is not liable for any costs associated with performance delays due solely to a firm’s failure to comply with Installation Access Control System (IACS) processing requirements.

The contractor shall return installation passes to the issuing IACS office when the contract is completed or when a contractor employee no longer requires access.

Specific requirements will be provided at the TO level.

1.6.3.1 Installation Pass Log: Reserved

1.6.3.2 Individual Termination or Expiration of Employment: Reserved

1.6.3.3 Contract Termination or Cancellation: Reserved

1.6.3.4 Common Access Cards (CAC) and CAC Log: Reserved

1.6.4 Background Checks: Reserved

1.6.4.1 U.S. Citizen: Reserved

1.6.4.2 Local Nationals and Third Country Nationals: Reserved

1.6.5 Physical Security: The contractor shall safeguard all Government equipment, information, and property provided for contractor use. At the close of each work period, Government facilities, equipment, and materials shall be secured IAW the Army Physical Security Program (AR 190-13.”) Passwords, access codes, and badges are sensitive items and shall be safeguarded at all times. Failure to safeguard sensitive items, using passwords or access codes without proper authorization, or disseminating passwords or access codes without proper authority, or without regard for established procedures, are causes for removal from this contract. At times, contractor personnel shall be provided keys to facilities. The loss or theft of keys, access cards, passcodes, passwords, and CACs shall be reported to the COR immediately.

1.6.6 Operations Security (OPSEC) Requirements:

1.6.6.1 Contractor personnel shall adhere to facility security policies and restrictions. The contractor shall immediately report suspicious activities to security personnel.

1.6.6.2 Government issued access badges shall not be worn outside designated facilities where visible to the general public.

1.6.6.3 For contracts that require a formal OPSEC program. The contractor shall develop an OPSEC Standing Operating Procedure (SOP)/Plan within 90 calendar days of contract award and within 30 days of any significant changes, to be reviewed and approved by the responsible Government OPSEC officer. This plan will include a process to identify critical information, where it is located, who is responsible for it, how to protect it, and why it needs to be protected. The contractor shall implement OPSEC measures as ordered by the commander. In addition, The contractor shall have an identified certified Level II OPSEC coordinator per AR 530-1. Comment by Andrew: CDRL reference. Comment by O'Brien, Brenda S CIV USARMY DOD JPEO CBRND (USA): Double checking with Security on if we require a formal OPSEC Program

1.6.7 Mandatory Cyber Reporting:

1.6.7.1 The contractor shall comply with the security requirements of the National Institute of Standards and Technology (NIST) SP 800-171, “Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations” and DFARS 252.204-7012, “Safeguarding Covered Defense Information and Cyber Reporting”.

1.6.7.2 Cyber Reporting. Upon the detection or discovery of any unauthorized access, denial of service, or compromise of a contractor's classified or unclassified network, information system or data contained thereon, The contractor shall report in writing within 24 hours to the CBRN Information Resource Center (24 hour hotline): Commercial (309) 782-7349, Toll Free: 1 (800) 831-4408, Email: CBRN.IRC@army.mil, SIPRNet Email: USARMY.CBRN.IRC@army.smil.mil

1.7 Key Control: Reserved

1.8 Post Award Conference/Periodic Progress Meetings/Data Calls: The contractor shall attend any post award conference convened by the contracting activity or contract administration office in accordance with FAR Subpart 42.5. The KO, COR, and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the Government.

1.8.1 The contractor shall attend, participate in, and furnish input to scheduled and unscheduled meetings, conferences, and briefings that relate to the functions and services herein as required by the Government to provide effective communication and impart necessary information. The Contract Manager or designated representative shall attend meetings as requested by the Government. Meeting attendees shall at times include contractor managerial, supervisory, and other personnel knowledgeable of the subject matter. Meetings may start or end outside of regular duty hours.

1.8.2 The contractor shall answer Government data calls and assist in responding to other Government requirements. Data calls include such things as preparing budget inputs, reporting the compliance with Government mandates, reporting on system and network performance, accomplishment of personal qualifications, and other topics.

1.8.3 A Start of Work meeting is required for all positions where the incumbent from the last period of performance (PoP) will not be continuing to provide support. This meeting will also be a requirement for any new position added after the start of a PoP. The COR will schedule the meeting with the Prime, Government Lead(s) and Senior Leadership prior to the start of work date. The purpose of this meeting is for the Government Lead to provide clarification to the Prime on the PWS tasks.

1.9 Contracting Officer’s Representative (COR): Refer to Part 2 of this PWS for the definition of a COR. As determined by the KO, a COR will be appointed and identified by letter of designation, a copy of which will be provided to the contractor by the KO. The designation letter states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates, or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order. The COR monitors all technical aspects of the TO contract and assists in TO contract administration. The COR is not authorized to obligate the Government. If the work is not written in the TO order contract, the COR is not authorized to request new work. The COR is authorized to perform the following functions: assure that the contractor performs the technical requirements of the TO contract, perform inspections necessary in connection with the TO contract performance, maintain written and oral communications with the contractor concerning technical aspects of the TO contract, issue written interpretations of technical requirements, including Government drawings, designs, specifications, monitor contractor's performance and notifies both the KO and contractor of any deficiencies, coordinate availability of Government property, and coordinate site entry of contractor personnel.

1.10 Key Personnel: The following personnel are considered key personnel by the Government:

1.10.1 Contract Manager, and Alternate Contract Manager: The contractor shall provide a Contract Manager and Alternate Contract Manager who shall be responsible for the performance of the work. The names of the Contract Manager and Alternate Contract Manager shall be designated in writing to the KO. The Contract Manager, or Alternate Contract Manager when the Contract Manager is absent, shall have full authority to act for the Contractor on all TO contract matters relating to daily operation of the TO contract. The Contractor Manager identified for each support location, will serve as the focal point to work with the assigned COR. The individual typically has a detailed knowledge of daily activities associated with the PWS and TO and is responsible for day-to-day communication with the COR. Comment by Andrew: CDRL reference Comment by O'Brien, Brenda S CIV USARMY DOD JPEO CBRND (USA): Comment by O'Brien, Brenda S CIV USARMY DOD JPEO CBRND (USA): These roles are not assigned or approved by the government. We just need the information in an email for situational awareness.

1.10.1.2 Other Key Personnel: Other personnel may be designated as Key Personnel as indicated in Part 5, Specific Task. These Key Personnel will have associated experience, education or qualification requirements as specified.

1.10.2 Quality Control Manager: Reserved

1.10.3 Systems Administrator: Reserved

1.10.4 Special Qualifications: Reserved

1.11 Identification of Contractor Employees: All contractor personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties must identify themselves, to include proper marking of signature blocks in correspondence, to avoid creating an impression in the minds of members of the public that they are Government officials. The contractor shall ensure that all documents or reports, produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed. Contractor personnel will be required to obtain and wear badges in the performance of this service. Contractor personnel shall wear badges or CACs at all times, identifying them as contractor personnel. Badges shall be worn above the waist and include a picture of the employee.

1.12.1 Reserved

1.12.2 Contractor Identification Badges: Reserved

1.13 Contractor Travel: To accomplish the work under this PWS, contractor personnel shall be required to represent or participate with Government personnel at meetings, conferences, and other activities within the Washington D.C. metropolitan area or at other sites in the Continental United States (CONUS) and Outside Continental United States (OCONUS) as directed by the Government. All travel requirements must be pre-authorized by a Government Lead or the COR based on contractor-prepared purpose, dates, and estimated costs in advance of travel dates. In case of mission urgencies, oral or verbal approval may be obtained from the COR. One exception is OCONUS travel, which can only be approved by the Contracting Officer. Any OCONUS travel requires submission of a Line of Accounting (LOA) into the Synchronized Pre-Deployment and Operational Tracker (SPOT). Other documentation may apply based on the OCONUS support location. Travel arrangements without Contracting Officer approval of the LOA are not authorized.

1.13.1 Travel costs that cannot be accurately forecasted will be reimbursed as travel occurs. Costs for travel shall be billed in accordance with the regulatory implementation of Public Law 99-234 and FAR 31.205-46 Travel Costs. Local travel (i.e., mileage from the assigned work location to the temporary duty location and from the temporary duty location back to the assigned work location) and costs associated with local travel, e.g., tolls, parking, and public transportation are reimbursable.

1.13.2 Travel trip and cost reports shall be completed in accordance with CDRL A002 . Comment by Andrew: Specify the CDRL Comment by O'Brien, Brenda S CIV USARMY DOD JPEO CBRND (USA): Updated

1.13.3 Costs for transportation may be based upon mileage rates, actual costs incurred, or a combination thereof, provided the method used results in a reasonable charge. Travel costs will be considered reasonable and allowable only to the extent that they do not exceed on a daily basis, the maximum per diem rates in effect at the time of the travel. The contractor may be authorized travel expenses at rates no higher than the substantive provisions of the Joint Travel Regulation (JTR), IAW FAR Part 31.205-46, and the limitation of funds specified in the TO. All travel requires Government approval and authorization prior to scheduled travel. The JTR, while not wholly applicable to contractors, shall provide the basis for the determination as to what is reasonable and allowable. Maximum use is to be made of the lowest available customary standard coach or equivalent airfare accommodations available during normal business hours. All necessary travel meeting the above criteria shall be approved in advance by the COR. Exceptions to these guidelines shall be approved in advance by the KO. Upon completion of travel, a trip report shall be submitted within five (5) business days of the TDY trip end date IAW CDRL A002 Travel Trip and Travel Cost Report. While General and Administrative (G&A) costs are allowable, overhead costs and fee (profit) are not allowable.

1.13.4 OCONUS Travel: OCONUS support may be required in Korea, Germany, Canada and or other locations as determined by enemy threats and mission and will be in accordance with supported command policies and procedures. With prior approval by the KO, deployed individuals may be required to work other than core hours in support of mission requirements and are authorized to exceed a forty (40) hour work week; however, hostile fire and hardship pay differentials apply only to the forty (40) hour work week.

1.13.5 The contractor shall be responsible for ensuring that employees assigned to the TO comply with the applicable laws and regulations of the host country and any international agreements (e.g., Status of Forces Agreement(s) (SOFA), Host Nation Support Agreements, etc.) and memoranda of agreements or understanding applicable to U.S. Armed Forces or U.S. citizens in the Area of Responsibility (AOR). The contractor is also responsible for ensuring that such employees comply with pertinent Service and DoD directives, policies, and procedures, military rules and regulations when employed in areas under the jurisdiction of the applicable military commander. In cases where contract support personnel are required to travel to locations OCONUS, including Theaters of Operation, they will be permitted use of various Government facilities, subject to the approval of the Theater or In-Country Commander and current SOFA or applicable international agreement for the specific location, as well as applicable Theater Business Clearance, Letters of Authorization, and the terms and conditions of the parent contract vehicle and TO. In the event that a contractor’s employee displays disruptive behavior, violates substance abuse laws, or regulations of host nations or host military commanders and is subsequently barred from continuing to perform under the contract for failure to comply with the laws, rules, and regulations, the costs incurred by the contractor because of the removal of the employee or the substitution of a replacement employee shall not be reimbursable.

1.13.6 RESERVED

1.13.7 Deployment/Re-Deployment to the Central Command AOR (If applicable). Unless deploying to the Central Command (CENTCOM) AOR for seventeen (17) days or less, The contractor shall complete individual pre-deployment training. Fort Bliss, Texas has been identified as the approved CONUS Replacement Center (CRC) for both Logistics Civil Augmentation Program (LOGCAP) and non-LOGCAP contractors. Please refer to Fort Bliss’ website listed below for instructions relating to deployment and re-deployment through their CRC.

https://home.army.mil/bliss/index.php/units-tenants/crc/contractor-deployer

1.13.8 The contractor shall not establish unique individual pre-deployment training operations for their employees. Non-LOGCAP firms may only utilize the LOGCAP facilities with an Army Sustainment Command (ASC) waiver and subject to the terms and conditions of their prime contracts with the Government.

1.14 Other Direct Costs (ODCs): All contractor purchases for Other Direct Costs (ODCs) must be approved by the KO in advance of any purchases. The contractor shall provide a monthly report showing all ODC’s, their purpose, and KO approval incurred during the previous month IAW CDRL A0003. Due NLT the tenth working day following the preceding month.

Comment by O'Brien, Brenda S CIV: Can this section be removed since there are no requirements for software/firmware in this Task Order? Comment by Andrew: We’ll run this by legal.

1.15 Intellectual Property:

(Note: Since this is a Model PWS, the following may need to be revised for future TOs based on the requirements of the specific TO. Therefore, it must be reviewed by the cognizant IP counsel for each contract, TO, DO, etc.)

1.15.1 The Government’s rights to all documents and materials, including technical data, software, firmware, software/firmware documentation, and source codes of software/firmware, produced under this Contract/Agreement, are as specified below. These documents and materials may not be used, disclosed, licensed, assigned or sold by the contractor without written permission from the KO. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights.

1.15.2 Data and Software Rights

1.15.2.1 Data and Software rights are covered under Defense Federal Acquisition Regulation Supplement (DFARS) clauses: 252.227-7013, Rights in Technical Data - Non-commercial Items; 252.227-7014, Rights in Noncommercial Software and Noncommercial Computer Software Documentation; 252.227-7015, Technical Data – Commercial Items; 252.227-7025, Limitations on the Use or Disclosure of Government-Furnished Information Marked with Restrictive Legends; and 252.227-7027, Deferred Ordering of Technical Data or Computer Software.

1.15.2.2 All non-commercial technical data and software deliverables shall be properly marked in accordance with the marking requirements set forth in DFARS 252.227-7013(f) and DFARS 252.227-7014(f), respectively. Technical data and software deliverables with non-conforming restrictive markings shall be rejected and corrected by the contractor at the contractor's expense, in accordance with DFARS 252.227-7013(h)(2) and DFARS 252.227-7014(h)(2), respectively.

1.15.3 Data/Software Rights Assertions

Pursuant to the content and formatting requirements for Data and Software Rights Assertions set forth in DFARS 252.227-7017, Offerors are required to specifically identify…