Atch 3 PWS PAI Template v2.docx

Attachment 1

FA5000‐XX-X-XXXX

FA701426R0008

PERFORMANCE WORK STATEMENT

FOR

PUBLICLY AVAILABLE INFORMATION (PAI) ALERTING

AT

HEADQUARTERS UNITED STATES AIR FORCE, PENTAGON

Date

Contents

SECTION I

1.0 DESCRIPTION OF SERVICES

1.1 General. The Headquarters United States Air Force (HAF), A2 Intelligence requires contractor support to enhance the Department of the Air Force’s ability to assess, web-based, mobile, e-mail, and application programming interface (API) alerting news to the Department of Defense (DoD) for force protection and first response for the entirety of the license agreement.

1.2 Scope. The commercially available license subscription should leverage a variety of publicly available information sources, evaluate content to detect emerging events as they are developing, and push alerts to users based on user-defined areas and topics of interest. The solution must be capable of distributing alerts in near real-time via email, application programming interface (API), web-based application, and mobile platforms. The solution must be available commercially in the marketplace, and able to scale to a DoD enterprise capability, and keep pace with developments and standards within the commercial industry sector.

1.3 Background. The DoD is seeking a commercially available solution to evaluate publicly available information (PAI) in near real time, to provide the DoD with situational awareness, force protection, indications and warnings, and support for emergency and contingency operations concerning global events.

SECTION II

2.0 Task Descriptions – Please add your task information as needed, the number of tasks is just for demonstration, add or subtract as your solution requires

2.1 TASK 1: As appropriate example – Enterprise License

2.2 TASK 2: As appropriate example – Delivery Method

2.3 TASK 3: As appropriate example – Support and Help Desk

2.4 TASK 4: As appropriate example – Training methodology

SECTION III

3.0 SERVICE SUMMARY

The following table outlines the key performance objectives, associated tasks, acceptable performance thresholds, and the surveillance methods the Government will use to evaluate contractor performance. These thresholds reflect mission-essential functions and provide a concrete basis for accountability, while allowing for iterative improvement in a dynamic environment.

TABLE 1: SERVICES SUMMARY

Threshold Method of Surveillance

SS – 1

Provide comprehensive training support

Quarterly Report. Annotated in the QSR

SS – 2

Comply with Privacy Act & IC CAI Policy Framework, and DoDD 3115.18 DoD Access to and Use of Publicly Available Info.

Quarterly

SS – 3

Maintain Enterprise License Subscription Support and user database

SS – 4

Help Desk: Provide accurate resolutions to customer needs and agency requirements 24/7

Helpdesk support 24/7; acknowledge receipt of issues within 12 hrs., resolve issues within 5 days & receive no more than 5 valid complaints about service during the month

Periodic Surveillance Quarterly. Annotated in the QSR

SS-5

Timely & accurate deliverables by due date

Surveillance Quarterly. Annotated in QSR

SS-6

Contractor performance meets requirements of the PWS

Periodic Surveillance Annotated in QSR

SECTION IV

4.0 DELIVERABLES

The Contractor shall provide the following deliverables in support of tasks outlined in this Performance Work Statement. All deliverables shall be submitted electronically to Microsoft Office, Adobe PDF, or other formats as required by the Government. Unless otherwise specified, deliverables will be submitted to the A2/OR Contracting Officer’s Representative (COR).

TABLE 2: DELIVERABLES

Program Management Review

Technical Exchange Meetings

Quarterly Status Report

(QSR)

Subcontract Management Plan

Problem Notification Reports

Kickoff Meeting Agenda

Quality Control Plan

4.1 Deliverables Management.

The Contractor shall provide deliverables as specified in the contract. If a deliverable due date falls on a weekend or holiday, the Contractor shall submit the deliverable on the last workday prior to the due date.

The contractor shall provide technical specific reports, informal analyses, papers, opinions, databases, briefings, etc. generated on an as-required (ad-hoc) basis during the performance of this contract in conjunction with the request for an ad-hoc technical meeting. Additionally, the contractor shall provide briefings, minutes, schedules, and metrics, etc., as required

4.2 Project Management Plan (PMP).

The Contractor shall host a semi-annual review with the DoD to highlight program successes, address program shortfalls and corrective actions to be taken, as well as other items and topics of interest or concern. For the purposes of this agreement, Contractor shall host PMRs every January and July of each year unless specified otherwise at a to be determined (TBD) location

4.3 Technical Exchange Meeting

The contractor shall provide technical specific reports, informal analyses, papers, opinions, databases, briefings, etc. generated in conjunction with the request for an ad-hoc technical meeting during the performance of this contract. Additionally, the contractor shall provide briefings, minutes, schedules, and metrics, etc., as required

4.4 Quarterly Status Report.

The contractor shall provide a Quarterly Status Report (QSR) no later than 10 calendar day preceding the end of the Government Fiscal Calendar Quarter: January 10, April 10, June 10, October 10. The report will be presented in an electronic format agreed upon by the Government COR and Contractor and should include a status of the enterprise license to enable at-scale alerts across services and user databases with updates each quarter

4.5 Subcontract Management Plan.

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.

4.6 User Training Support.

Provide training on product onboarding for up to 4 Web Conference User sessions per week and no less than 4 sessions per month. Account for training by reporting on each training session in the Quarterly Status Report (QSR).

4.6.1 The Contractor will provide up to four (4) remote Web Conference User sessions per week, but no less than four (4) per month, during the License Period at the request of the Government, virtual or in-person (use virtual to the most extent practicable);

4.6.2 Provide comprehensive training support report, to include:

· Training dates

· Training units

· Number of trainees, if unit is listed also list number of trainees in attendance

· Training subjects

4.7 Problem Notification Reports (PNR). At the discretion of the DoD, and with five (5) business days’ notice, ad-hoc meetings may be called to address issues that unexpectedly arise.

4.8 Help Desk. Helpdesk support will be 24/7; acknowledge receipt of issues within 12 hrs., resolve issues within 5 days & receive no more than 5 valid complaints about service during the month

SECTION V

5.0 GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, MATERIAL, INFORMATION, OR SERVICES

5.1 Government Furnished Property, Equipment, Material, Information, or Services. The Government will not furnish property or services for this requirement. The Government does not intend on providing any property, equipment, material, information, or Services, in conjunction with this contract

5.2 Contractor Acquired Property. The contractor will not be required to acquire any property. The Government does not anticipate or expect the contractor to acquire any property in conjunction with this contract

SECTION VI

6.0 GENERAL INFORMATION

6.1 Kickoff Meeting/Orientation Meeting

6.1.1 The Contractor shall schedule and coordinate a Project kick-off Meeting no later than (NLT) five (5) calendar days after contract award at the location approved by the Government. The meeting will provide an introduction between the Contractor personnel and Government personnel who will be involved with the contract. The meeting will provide the opportunity to discuss technical, management, and logistic issues; travel authorization; communication process between Government and Contractor; and reporting procedures. At a minimum, the attendees shall include key Contractor personnel, HAF AF/A2, key Government representatives, and the COR. The Contractor shall provide a Kick-Off Meeting Agenda that will include, but not be limited to, the following.

6.1.2 The Contractor shall provide a draft copy of the agenda NLT 5 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.

6.1.3 The Kickoff Meeting location will be held at the (Government's or Contractor’s) facility or another designated location and the date and time will be mutually agreed upon by both parties.

6.2 Transition-In Plan

6.2.1 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 identify how it will coordinate with the incumbent Contractor and Government personnel to transfer knowledge regarding the following:

6.2.2 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 Transition-Out Plan

6.3.1 The Contractor shall provide a Transition-Out Plan NLT than 10 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. The Contractor shall identify how it will coordinate with the incoming Contractor and Government personnel to transfer knowledge regarding the following:

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

6.4 Quality Control.

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

6.4.2. Quality Control Plan (QCP). The Contractor shall develop and maintain an effective quality control program to ensure services are performed IAW this PWS, applicable laws and regulations, and best commercial practices. The Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services with special emphasis placed on those services listed in this PWS. The Contractor’s quality control program is the means by which it assures itself that the work complies with the requirement of the contract. The Contractor shall submit a QCP at the contract kick-off meeting. The QCP demonstrates how the Contractor shall maintain an inspection system acceptable to the Government covering the services under this contract. The QCP shall demonstrate the Contractor’s documented processes and procedures to monitor and control:

a. Objectives in Services Summary (Table 1)

b. Subcontractor relationships

c. Contractor and subcontractor invoicing

d. Non-conformances

7.0 Security Instructions

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

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

7.3 Contractor Identification. Contractors shall identify themselves on any attendance sheet or any coordination documents they may review. Electronic mail signature blocks shall identify their company affiliation.

7.4 Drug, Tobacco, and Alcohol Use Policy. The consumption of alcoholic beverages or illegal drugs by contractor personnel, while on duty, is strictly forbidden. Contractor shall immediately remove any employee who is under the influence of alcohol or drugs.

7.5 Travel

Contractors may provide DoD senior leadership support online, via telephone, or in person, as reasonably required and as mutually agreed upon. Travel and any associated costs as a result of in-person sessions are at the contractor’s expense. DoD senior leadership is defined as general/flag officers, executive-level civilians, and select individuals as identified by the DoD. Contractor personnel supporting these sessions should be familiar with the product and responsibilities of senior DoD leadership. All travel for training shall be approved by the COR within a reasonable amount of time, to allow travel to occur.

8.0 Miscellaneous Paragraphs.

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

8.2 Controlled Unclassified Information (CUI). All DoD CUI must be controlled until authorized for public release in accordance with DoD Instruction (DoDI) 5200.01. This regulation set policy and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding of CUI material.

8.3 Privacy Act. Work on this contract may require that personnel have access to information protected by the Privacy Act. Contractor must ensure safeguards are in place to protect user information, in compliance with National Institute of Standards and Technology (NIST) SP 800-171 and FAR 52.239-1, DFARS 252.204-7009, DFARS 252.2047015, and DFARS 252.239-7010 and Contractor personnel shall adhere to the Privacy Act, Title 5 of the U.S. Code, Section 552a and applicable agency rules and regulations when handling such information, including IC CAI Policy Framework, and DoDD 3115.18 DoD Access to and Use of Publicly Available Info and

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

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

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

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

8.8 Ethics. The Contractor shall not employ any person who is an employee of the US Government if employing that person would create a conflict of interest. Additionally, the Contractor shall not employ any person who is an employee of the Department of the Air Force, either military or civilian, unless such person seeks and receives approval according to DoDD 5500.07, Joint Ethics Regulation.

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

SECTION VII

APPENDIX 1

1.0 DEFINITION AND ACRONYMS

1.1 Definitions

Contracting Officer (CO). The duly appointed Government agent authorized to award or administer contracts. The contracting officer is the only person authorized to contractually obligate the Government.

Contracting Officer’s Representative (COR) means an individual, including a contracting officer’s technical representative (COTR), designated and authorized in writing by the contracting officer to perform specific technical or administrative functions.

Defective Service. A service output that does not meet the standard of performance specified in the contract for that service.

Performance Threshold. The minimum performance level of a performance objective required by the Government.

1.2 Acronyms

AFRICOM Africa Command

CENTCOM Central Command