RFP UCF Performance Work Statement ID04200022 amend003 July 1 2020.docx

General Services Administration Federal Acquisition Services Assisted Acquisition Services Division Southeast Sunbelt Region

Task ID: ID04200022 Solicitation PIID: 47QFSA20R0006 Requirements IDIQ Contract:

Date: April 13, 2020

GSA Contract Specialist:

Dorothy “Hae” Monroe Phone: (720) 468-8023 Email: dorothy.monroe@gsa.gov GSA Senior Contracting Officer:

Mary “Beth” Clark Phone: (478) 365-1167 Email: mary.clark@gsa.gov

Client Organization:

USSOCOM MISO

MacDill AFB, FL 33621-5323 Primary Client Representative:

Captain Whitney O’Connell Phone: (813) 826-1969 Email: whitney.e.o'connell.mil@socom.mil

Project Name:

MISO Evaluation and Transregional Analysis (META) Period of Performance:

Base Year: 07/31/2020 – 07/30/2021 Option Year 1: 07/31/2021 – 07/30/2022 Option Year 2: 07/31/2022 – 07/30/2023 Option Year 3: 07/31/2023 – 07/30/2024 Option Year 4: 07/31/2024 – 07/30/2025 Option to Extend Services: 07/31/2025 – 01/30/2026

Contract

Funding

PART I – THE SCHEDULE

A.

SOLICITATION/CONTRACT FORM

A.1 SOLICITATION/CONTRACT FORM

Reference SF1449 through GSA business systems portal, AASBS (https://portal.fas.gsa.gov).

END OF SECTION A

B. SERVICES AND PRICES

B.1 SCHEDULE OF SUPPLIES/SERVICES TO BE PROVIDED

The contractor shall provide their total proposed amounts in Blocks 20 through 24 of the SF1449 cover page through the GSA business systems portal, AASBS (https://portal.fas.gsa.gov) for all Task Items/Contract Line Item Numbers. Separate task items/CLINs are provided for a one year base period of performance, four each one year optional period of performance, and a six month extension period in accordance with FAR 52.217-8.

This will be a Requirements contract that fulfills mission support for USSOCOM J39 and its Military Information Support Operations (MISO). Orders may only be placed by GSA FAS through this contract for USSOCOM J39 and its MISO mission requirements.

The Contract Line Item Numbers (CLINs) are firm fixed price (FFP) for CLINs X001-X0014. CLIN X015 is cost reimbursable (CR).

The Contract Line Item Numbers are as follows for the Base Year, Option Years 1-4, and the Six-Month Extension Period:

Base Year

0001: Translations 0002: Quantitative Data Acquisition, permissive environment 0003: Quantitative Data Acquisition, semi-permissive environment 0004: Quantitative Data Acquisition, non-permissive environment 0005: Qualitative Data Acquisition, permissive environment 0006: Qualitative Data Acquisition, semi-permissive environment 0007: Qualitative Data Acquisition, non-permissive environment 0008: Automated Data Collection, permissive environment 0009: Automated Data Collection, semi-permissive environment 0010: Automated Data Collection, non-permissive environment 0011: Data Analysis 0012: User Support (includes survey development, reachback, platform, and training) 0013: Data Storage 0014: Data Vizualization (Data Mangement Add-On, User Accounts, and licenses) 0015: Travel

Option Year 1

1001: Translations 1002: Quantitative Data Acquisition, permissive environment 1003: Quantitative Data Acquisition, semi-permissive environment 1004: Quantitative Data Acquisition, non-permissive environment 1005: Qualitative Data Acquisition, permissive environment 1006: Qualitative Data Acquisition, semi-permissive environment 1007: Qualitative Data Acquisition, non-permissive environment 1008: Automated Data Collection, permissive environment 1009: Automated Data Collection, semi-permissive environment 1010: Automated Data Collection, non-permissive environment 1011: Data Analysis 1012: User Support (includes survey development, reachback, platform, and training) 1013: Data Storage 1014: Data Vizualization (Data Mangement Add-On, User Accounts, and licenses) 1015: Travel

Option Year 2

2001: Translations 2002: Quantitative Data Acquisition, permissive environment 2003: Quantitative Data Acquisition, semi-permissive environment 2004: Quantitative Data Acquisition, non-permissive environment 2005: Qualitative Data Acquisition, permissive environment 2006: Qualitative Data Acquisition, semi-permissive environment 2007: Qualitative Data Acquisition, non-permissive environment 2008: Automated Data Collection, permissive environment 2009: Automated Data Collection, semi-permissive environment 2010: Automated Data Collection, non-permissive environment 2011: Data Analysis 2012: User Support (includes survey development, reachback, platform, and training) 2013: Data Storage 2014: Data Vizualization (Data Mangement Add-On, User Accounts, and licenses) 2015: Travel

Option Year 3

3001: Translations 3002: Quantitative Data Acquisition, permissive environment 3003: Quantitative Data Acquisition, semi-permissive environment 3004: Quantitative Data Acquisition, non-permissive environment 3005: Qualitative Data Acquisition, permissive environment 3006: Qualitative Data Acquisition, semi-permissive environment 3007: Qualitative Data Acquisition, non-permissive environment 3008: Automated Data Collection, permissive environment 3009: Automated Data Collection, semi-permissive environment 3010: Automated Data Collection, non-permissive environment 3011: Data Analysis 3012: User Support (includes survey development, reachback, platform, and training) 3013: Data Storage 3014: Data Vizualization (Data Mangement Add-On, User Accounts, and licenses) 3015: Travel Option Year 4

4001: Translations 4002: Quantitative Data Acquisition, permissive environment 4003: Quantitative Data Acquisition, semi-permissive environment 4004: Quantitative Data Acquisition, non-permissive environment 4005: Qualitative Data Acquisition, permissive environment 4006: Qualitative Data Acquisition, semi-permissive environment 4007: Qualitative Data Acquisition, non-permissive environment 4008: Automated Data Collection, permissive environment 4009: Automated Data Collection, semi-permissive environment 4010: Automated Data Collection, non-permissive environment 4011: Data Analysis 4012: User Support (includes survey development, reachback, platform, and training) 4013: Data Storage 4014: Data Vizualization (Data Mangement Add-On, User Accounts, and licenses) 4015: Travel

Six-Month Extension (IAW 52.217-8 Option to Extend)

5001: Translations 5002: Quantitative Data Acquisition, permissive environment 5003: Quantitative Data Acquisition, semi-permissive environment 5004: Quantitative Data Acquisition, non-permissive environment 5005: Qualitative Data Acquisition, permissive environment 5006: Qualitative Data Acquisition, semi-permissive environment 5007: Qualitative Data Acquisition, non-permissive environment 5008: Automated Data Collection, permissive environment 5009: Automated Data Collection, semi-permissive environment 5010: Automated Data Collection, non-permissive environment 5011: Data Analysis 5012: User Support (includes survey development, reachback, platform, and training) 5013: Data Storage 5014: Data Vizualization (Data Mangement Add-On, User Accounts, and licenses) 5015: Travel

END OF SECTION B

C. DESCRIPTION/SPECIFICATION/STATEMENT OF WORK

C.1 BACKGROUND

The USSOCOM J39 Military Information Support Operations (MISO) Branch has the mission to plan, coordinate, integrate, and, when directed, execute MISO strategies to promote the goals and objectives of the Government of the United States and serve at the Joint Proponent Office for MISO. MISO Evaluation and Transregional Assessment (META) is a USSOCOM effort to create a centralized contract to collect, format, analyze, store, and present MISO data for both theater and transregional/strategic assessment.

C.2 SCOPE OF EFFORT

The contractor shall provide for survey development and the collection, formatting, analyzing, storage, and presentation of data to support USSOCOM META mission requirements. USSOCOM requires MISO units be able to task assessment activities in support of MISO series within their area of responsibility (AOR). The data collected from such assessment tasking(s) shall be shared with USSOCOM and subordinate units as necessary. In order to show effects of a MISO product or operation, measured changes in the attitudes, beliefs, and/or behavior of the Target Audience shall be tied to some effort executed by or coordinated through the MISO unit.

The contractor shall provide an interface that supports in identifying the vulnerabilities of a target population, evaluating and assessing influence operations, and using outcome or predictive analyses to dependably inform USSOCOM future operations. The contractor shall support in statistically analyzing the performance and effects influence operations have had on achieving MISO objectives. The contractor shall provide the necessary local language proficiency and access to collect the data required to inform measures of performance (MOP) and measures of effectiveness (MOE) for MISO capability enabling MISO operators to task out data collection, and also to rapidly and reliably receive, share, and visualize data.

C.3 PERFORMANCE REQUIREMENTS

The contractor shall address all performance issues and customer complaints to ensure the requirements defined in the PWS are met successfully 100% of the time. The contractor shall provide episodic support for known and emerging requirements to support USSOCOM META operations to include question development, collection, storage, formatting, analyzing, and presentation of information. The contractor’s emerging requirement support shall assist the USSOCOM J39 and its sub-units in achieving their MISO requirements. Contractor shall be capable of executing the task order starting no more than 14 businessdays from notification of the Contracting Officer (CO).

3.1 ASSESSMENT:

3.1.1. Access for Data Collection. The contractor shall conduct various types of data collection across the globe to empirically assess both the performance of MISO efforts as well as the effects of information operations on various target audiences (TA). In order to reliably track MOP, evidence of MISO product dissemination to specific target audiences across various platforms (e.g., television, radio, billboards, newspapers, magazines, hand bills, cell phones, internet, or any other relevant or emerging platform used for MISO) must be captured. Freedom of movement is required in sometimes very restricted, denied, or non-permissive environments to validate those measures. The contractor may be required to collect data from hidden or hard-to-access populations within the countries of operation. For example, some MISO units may require data from populations in countries where a U.S. footprint is restricted, or may need to survey populations with ties to terrorist activities.

3.1.2. Data Collection Methods. The contractor shall provide a broad array of both quantitative and qualitative research methods be utilized to support data collection, analysis, and evaluation. The contractor will develop an assessment plan and survey questions or other data gathering items which align with and support the interpretation of desired behaviors, MISO objectives, Lines of Effort (LOEs), and MISO programs. Potential quantitative methods needed are sample surveys (to include in person, online, phone, text, email, smart phone app, or any emerging surveying mechanism that could feasibly be used for these efforts), crowd sourcing, hierarchical, longitudinal statistical modeling, social network analysis, and demography. Necessary qualitative methods may include case studies, observations, interviews, focus groups, natural language processing and textual analysis, sentiment analysis, topic modeling, or any emerging method that could feasibly be used for these efforts. These data collection methods must be appropriate for the stated unit objective and able to be conducted either in person, telephonically (via phone call, text, smart phone app), or online, depending upon the requirements of the requesting MISO unit. Tasks will vary based on individual project requirements and the security situation of locations. Documentation may be required in the form of native language transcripts, translated transcripts, audio, and/or audio/visual documentation of focus groups. Report will be in Word format with graphs, as applicable.

3.1.2.1. Organizations conducting MISO require trend analysis in order to determine if operations in execution have had an impact on the attitudes, beliefs, and/or behaviors of their TA. To inform trend analysis, the contractor shall employ multiple iterations of the same survey or assessment to the same target audience in order to provide reliable data to successfully inform future operations.

3.1.2.2. The contractor shall collect and integrate publically available information (PAI) via online scraping to provide a more robust assessment of MISO efforts.

3.1.2.3. The contractor shall employ a network of contributors and visualize (e.g., via a map, location list, etc.) their locations in order to support planning considerations for mission, enemy, terrain and weather, troops, time available, and civil (METT-TC) considerations.

3.1.3. Reliability and Validity of Data. The contractor shall provide for the employment of empirically sound methodology for all assessments, per industry standards, in order to ensure the highest levels of reliability and validity of the data. While access to some locations and/or populations may limit the gold standard of empirical methodology, it is essential that limitations are clearly identified and alternative rationale presented to ensure results are valid and reliable. Confidence levels for any correlational or statistical analysis must be provided and any issues encountered during data collection impacting the validity or reliability of the data are clearly notated for transparency.

3.1.4. Standardization. A primary goal of META is to enable transregional analysis of MISO efforts. To support this transregional analysis requirement, the contractor shall ensure any research questions asked in one AOR that can be tied to the same or similar objectives in another AOR be asked in a similar manner (similar verbiage, sentence structure, and response options), within the context of local language and education level of the TA. The contractor shall ensure standardization of data coding across all AORs to support transregional analysis.

3.1.5. Language. The contractor shall ensure all survey, focus group, and interview questions be translated into the local language of the region in which it shall be conducted, and then back translated to ensure the translation is valid (minimum language capability includes: Arabic [MSA, Maghrebi, Levantine, Egyptian, Gulf, Yemini], Chinese, Dari, Farsi, French, Haitian, Hausa, Kazakh, Korean, Kurdish, Kyrgyz, Pashtu, Russian, Swahili, Somali, Spanish, Tajik, Turkman, Ukrainian, Uzbek). Translation shall be done by a native speaker. Once the data is collected and compiled, it must be translated back into English for consumption by the requesting MISO unit(s). All question development, data analysis, and evaluation products created shall be created in English. The contractor shall have the ability to translate analysis and evaluation products into host nation language, when needed.

3.1.6. Speed of Data Visualization and Reporting Results. The contractor shall provide near-real-time feedback to the teams conducting MISO in order to support the most time sensitive operations. As data is collected, it shall be populated in the data visualization dashboard for MISO units to access and manipulate. The contractor’s assessment report must be completed within 14 days of the conclusion of data collection.

3.1.7. Attribution. Attribution for the contractor’s data collection shall be in line with current OSD policy.

3.1.8. PAI Integration. The contractor’s data collected in support of operations being executed in-country shall be integrated with PAI in order to produce a robust and accurate assessment picture suited to inform operational decision making. To support this requirement, access to PAI data is required, as well as a means to ingest the associated information for analyses.

3.1.9. RESERVED

3.1.10. Flexible Execution. The contractor shall have the ability to rapidly shift assessment capability to new countries as the need arises and to meet the 14-day requirement for onset of data collection outlined in this PWS. Flexibility is essential to facilitate assessment of both repetitive operations and ad hoc requirements.

3.1.11. Quality Control. The contractor shall ensure quality checks both for the people conducting assessments and also on the data they submit. Techniques such as GPS tracking, geolocation, VPN verification, silent recordings, key stroke analysis, timestamps, and any other relevant techniques, shall be employed in order to verify the reliability of personnel and the validity of products being delivered. Quality control measures to be employed will be identified in the contract, and any quality control issues encountered in the field must be reported quarterly.

3.2. DATA ANALYSIS:

3.2.1. MOP and MOE. The contractor shall reliably assess MISO efforts (to include, but not limited to: the number of products disseminated to a specified target audience, verification of dissemination locations, level of penetration, reach of MISO products to target audience, verification of psychological acts), and the contractor shall correlate MOP with measured changes in attitudes, beliefs, or behaviors of the TA. The contractor shall integrate MOP or MOE documented/collected by the requesting unit as well as PAI data with any MOP or MOE collected by the contractor.

3.2.2. Statistical Analysis of Data. The contractor shall provide statistical analysis of collected data. Statistical analysis may be required for broad target audience analysis, to inform baseline analysis, pre- and/or post-test data to assess product effectiveness, and/or multiple iterations of sentiment analysis in order to assess changing attitudes and behaviors of a population over time and, ultimately, provide MOP and MOE to the MISO units. At a minimum, correlational analysis between MISO performance and effects will be provided for each standard and quarterly report (exception: analysis/reports including baseline data only). The contractor’s data shall be cleaned and weighted, when appropriate, in order to present the most accurate results to the MISO units interpreting it. Contractor data analysts shall be cleared up to the SECRET level to produce reports.

3.2.3. Data Visualization. Results of statistical analyses conducted shall be conveyed in an interpretable, easy-to-consume, executive format. The contractor’s visualization interface shall be user-friendly and well-maintained (e.g., identified database issues are promptly corrected). The interface shall be accessible by MISO units from anywhere around the globe; it shall enable units to search, sort, and manipulate data, and to easily produce interpretable visualizations (e.g. maps, trend graphs based on objectives, pie charts of demographic variables) of data. MISO units must be able to access and manipulate results from individual data collection iterations as well as access and manipulate results from trend data (if multiple iterations of data were collected in order to evaluate MOP and MOE). The contractor’s visualization products shall be easy to create and export within the interface. As data is collected, it shall populate in the data visualization dashboard so results can be seen near-real time prior to the conclusion of the entire data collection effort.

3.2.4. Data Aggregation. The contractor shall provide the ability to aggregate data collected in support of various MISO teams across the globe in order to provide one consolidated, overarching picture of the effects being created in the operational environment. Multilevel, longitudinal modeling shall be used to assess changes at various levels (i.e., individual, target audience, country, region, trans-regional area) over time. The contractor’s aggregated data shall be easily organized, interpreted, and visualized according to problem set, country/region, MISO Program, MISO Objectives, and/or by LOE.

3.2.5. Data Storage. The contractor shall provide and maintain a cloud-based storage solution for data collected. The cloud shall feed into a user-friendly interface, and shall be made available to everyone in the MISO community who requires access. MISO users must be able to easily retrieve data analysis for any measures on which data has been collected, when needed. Multi-level security solutions must be available in order to appropriately store data and analytic products. Data will be transferrable to future USSOCOM cloud services currently in development.

3.2.6. Raw Data. The contractor’s raw data collected shall be provided to USSOCOM. The raw data shall be provided in .csv, .json, and .xml formats. The raw data shall be easily exportable from a “cloud” storage configuration. Any weights used for the data shall be clearly relayed.

3.2.7. Data Rights. The Government has unlimited rights to all documents/material produced under this contract IAW DFARS 252.227-7015 Technical Data--Commercial Items (Feb 2014). All documents and materials, to include the source codes of any software, produced under this contract shall be Government owned and are the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. These documents and materials may not be used or sold by the contractor without written permission from the Contracting Officer. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights.

C.4 DELIVERABLES

4.1. REPORTS:

4.1.1. Per Data Collection. The contractor’s completed reports shall be provided to the requesting MISO unit(s) within 14 business days of data collection completion unless otherwise stated in the task order. For near-real-time data analysis requirements, the contractor’s iterative analysis shall be provided as soon as two days after the collection of a specified number of data is completed. All reports will be produced at the SECRET level.

USSOCOM requires reports created after each data collection to include, at a minimum:

4.1.1.1. Standard Report Content. USSOCOM requires reports provided to the requesting MISO unit(s) upon completion of the task order assessment to include:

4.1.1.2. Problem Formulation. The program and MOs under which data was collected shall be listed, and data collection location(s) shall be listed. There shall be a clear statement of the research question(s) addressed by the assessment, along with the objective(s) or measureable outcome variables or goals based on the requesting MISO unit’s guidance and intent for the data analysis.

4.1.1.3. Methods. An unambiguous description of study design(s) shall be given, as well as the sample size, sampling technique (including explanations for deviations from gold-standard practices), and confidence level. A description of data collection techniques shall also be included.

4.1.1.4. Analysis. A description of the demographic characteristics of the data sample(s) shall be provided, and any groups over- or underrepresented shall be identified. An appropriate analysis of the data as it relates to the measured objective shall be provided, to include both univariate and multivariate statistics, when able, and a detailed analysis of any statistically significant results. Correlation between MISO products/series and changing attitudes, beliefs, or behaviors of the TA shall be highlighted, as well as areas where MISO series were conducted, yet no effects were seen.

4.1.1.5. Conclusion/Discussion. This shall include a generalization of findings, with a closing note on any stand-out results. Limitations of conclusions based on sampling, design and measurement shall be reported, as well as recommendations for future MISO efforts. Any quality control issues encountered that quarter must be reported.

4.1.2. Quarterly Report. The contractor’s completed reports shall be provided to USSOCOM no later than 14 days after the end of the quarter on the fiscal year calendar.

USSOCOM requires quarterly reports to include, at a minimum:

4.1.2.1. Requesting Units. The number of MISO units supported that quarter, including the number of countries in which work was performed.

4.1.2.2. Research Question. All of the programs and MISO Objectives (MOs) under which data was collected shall be listed; data shall be outlined by country in which assessments were conducted, as well as by problem set. There shall be a clear statement of the research question(s) addressed that quarter, and those statements shall contain objective or measureable outcome variables or goals based on the MISO units’ guidance and intent for the data analysis.

4.12.3. Methods. An unambiguous description of study design(s) shall be given, as well as the sample size, sampling technique, confidence level. A description of data collection techniques shall also be included.

4.1.2.4. Analysis. A description of the demographic characteristics of the samples shall be provided, and any groups over- or underrepresented shall be identified. An appropriate analysis of the data as it relates to the problem set shall be provided, to include both univariate and multivariate statistics, when able, and a detailed analysis of any statistically significant results. Relationships between MISO products/series and target audience consumption (MOP) and changing (e.g. longitudinal trend data of) attitudes, beliefs, or behaviors of the TA shall be highlighted, as well as any areas where MISO series were conducted, yet no effects were seen.

4.1.2.5. Transregional Analysis. When the same or similar MOs and/or LOEs are used, transregional/strategic analysis will be provided to determine baseline status and/or change of transregional audiences over time.

4.1.2.5. Conclusion/Discussion. The quarterly report shall include a generalization of findings, with a closing note on any stand-out results. Limitations of conclusions based on sampling, design, and measurement shall be reported, as well as recommendations for future MISO efforts. Any quality control issues encountered that quarter shall be reported.

4.2. TRAINING:

The contractor shall provide training to users that clarifies data collection requests, data collection processes, and data analysis. Hands-on training shall be provided to ensure users can effectively navigate the data visualization interface.

4.3. USER SUPPORT:

The contractor shall provide a point of contact to each subordinate unit to USSOCOM J39 and/or other combatant commands who may utilize META. This point of contact shall develop an assessment plan for the MISO effort, and ensure that plan aligns with and supports the interpretation of desired behaviors, MISO objectives, Lines of Effort (LOEs), and MISO programs. This point of contact shall develop survey questions to support the assessment plan, and will work with the requesting unit to finalize surveys and assessment products. The vendor shall provide reach back support throughout the life of the task order, to include, but not limited to, assessment plan refinement, survey/question development and refinement, and data visualization support and troubleshooting.

END OF SECTION C

D. PACKAGING & MARKING

D.1 LISTING OF CLAUSES INCORPORATED BY REFERENCE (FAR 52.252-2) (FEB 1998)

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also the full text of a clause may be accessed electronically at the addresses below:

I. FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER 1)

CLAUSE NO. DATE TITLE

None included

II. DFAR SUPPLEMENT (48 CFR CHAPTER 2)

None Included

III. GSAM FAR SUPPLEMENT (48 CFR CHAPTER 18)

None Included

END OF SECTION D

E. INSPECTION & ACCEPTANCE

E.1. INSPECTION AND ACCEPTANCE

Inspection and acceptance will occur in accordance with FAR 52-212-4 Contract Terms and Conditions-Commercial Items. In the absence of other agreements negotiated with respect to time provided for Government review, deliverables will be inspected and the contractor notified of the findings within seven calendar days of normally scheduled review. If the deliverables are not acceptable, the COR will notify the contractor immediately. Acceptance of invoices shall constitute acceptance of performance.

Performance by the contractor to correct defects found by the Government as a result of quality assurance surveillance and/or by the contractor as a result of quality control shall be at the contractor’s own expense without additional reimbursement by the Government. Unless otherwise negotiated, the contractor shall correct or replace all non-conforming services or deliverables not later than seven calendar days after notification of non-conformance.

E.2 QUALITY CONTROL PROGRAM/QUALITY CONTROL PLAN

Management of the quality control program is the responsibility of the contractor. The contractor is responsible for the delivery of quality services/supplies to the Government. The contractor shall develop, implement, and maintain an effective Quality Control Program which includes a written Quality Control Plan (QCP). The QCP shall implement standardized procedure/methodology for monitoring and documenting contract performance to ensure all contract requirements are met. The contractors’ QCP must contain a systematic approach to monitor operations to ensure acceptable services/supplies are provided to the Government. The QCP, as a minimum, shall address continuous process improvement; procedures for scheduling, conducting, and documenting inspections; discrepancy identification and correction; corrective action procedures to include procedures for addressing Government discovered non-conformances; procedures for root cause analysis to identify the root cause and root cause corrective action to prevent re-occurrence of discrepancies; procedures for trend analysis; procedures for collecting and addressing customer feedback/complaints. The contractor shall provide to the Government their comprehensive QCP within thirty days after contract award. If the QCP requires updates/revisions over the course of contract performance they shall be provided within five business days after updates/revisions are deemed necessary to the Contracting Officer’s and COR’s approval. The plan may be in contractor provided format ensuring information contained therein completely covers the requirements of the deliverable.

The Government will have five business days to review the deliverable for content. If the deliverable is unacceptable, the Government will return it to the contractor within two business days and the contractor shall provide a revised QCP within two business days that is acceptable to the Government. Unless otherwise advised by the Contracting Officer, all deliverables shall be uploaded to AASBS (https://portal.fas.gsa.gov/) via a Post Award Collaboration.

E.3 GOVERNMENT SURVEILLANCE

The Government shall monitor the contractor’s performance under this contract using the quality assurance criteria specified in the Services Summary, herein, and the Quality Assurance Surveillance Plan (QASP).

The contractor shall cooperate with inspectors and auditors and provide any requested information relating to the operations covered by the contract. The contractor shall allow inspectors and auditors to periodically access work areas and provide access to any files required in relation to this contract. The contractor shall correct discrepancies and/or violations noted during safety/security/fire/performance inspections and prepare a written response providing information on actions taken to correct discrepancies and/or violations. The contractor shall provide this response to the COR within the time frame specified by the inspecting agency.

When an observation indicates defective performance, the COR will require the contractor’s representative at the site to initial the observation documentation. The contractor’s representative initialing the observation documentation does not constitute concurrence with the observation, only acknowledgment.

The contractor shall notify the COR, within one business day, of complaints in writing received by the contractor on services/supplies covered by or received under this contract. These complaints could include, but are not limited to, those received from customers receiving deliveries, commercial shippers, and discrepancies in Shipment Reports (Standard Form 361). The contractor is responsible for researching and submitting proposed answers to all deficiencies to the COR within five calendar days of the compliant notification. All complaints shall be resolved to COR’s satisfaction within seven calendar days of compliant notification.

The COR will document all defects using a “Task Discrepancy Report (TDR)”. The COR will verbally notify GSA of the defect and will submit a copy of the TDR as an Action Memo in AASBS to the GSA CO. The COR will ensure the TDR is completed in its entirety and coordinated through the CO. The contractor will also be furnished a copy of the TDR. The contractor shall furnish their response to the TDR. The contractor’s response will address the accuracy and validity of the defect, planned corrective action, and actions to prevent recurrence. The TDR information will be included when assessing the contractor’s overall performance (i.e., past performance assessments, exercise of options, etc.).

Government surveillance of tasks may occur at any time during the performance period.

E.3.1 QUALITY ASSURANCE SURVEILLANCE PLAN

A Quality Assurance Surveillance Plan (QASP) is developed to evaluate contractor actions while implementing this Performance Work Statement (PWS). It is designed to provide an effective surveillance method of monitoring contractor performance for each listed objective on the Services Summary. The QASP provides a systematic method to evaluate the services the contractor is required to furnish on a quarterly basis.

E.3.2 SERVICES SUMMARY

The contractor shall provide all required personnel to successfully perform the work detailed herein. The contractor shall address all performance issues and customer complaints to ensure the requirements defined in the PWS are met successfully 100% of the time.

Contractor met requirements in the PWS and received no more than two written customer complaints/notification of non-conforming services during a single one-year performance period AND complaints/non-conforming services were successfully corrected by the contractor within seven calendar days of notification.

Quarterly Inspections

Quarterly Inspections

E.4 PAST PERFORMANCE INFORMATION

The Government will provide and record Past Performance Information for acquisitions over $250,000 utilizing the Contractor Performance Assessment Reporting System (CPARS). The CPARS process allows contractors to view and comment on the Government’s evaluation of the contractor’s performance before it is finalized. Once the contractor’s past performance evaluation is finalized in CPARS, it will be transmitted into the Past Performance Information Retrieval System (PPIRS).

Contractors are required to register in CPARS, so they may review and comment on past performance reports submitted through CPARS. Go to the following website to register in CPARS: https://www.cpars.gov/.

END OF SECTION E

F. DELIVERIES OR PERFORMANCE

F.1 LISTING OF CLAUSES INCORPORATED BY REFERENCE (FAR 52.252-2) (FEB 1998)

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also the full text of a clause may be accessed electronically at the address below:

I. FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER 1)

CLAUSE NO. DATE TITLE

F.2 PERIOD OF PERFORMANCE

This contract shall be effective as of contract award. One (1) one-year base period and four (4) one-year option periods are included in addition to a six month extension period in accordance with FAR 52.217-8, Option to Extend Services. See cover page of this document for actual Periods of Performance dates.

F.3 PLACE OF PERFORMANCE

Work will be performed at various locations based on each task order, which include but are not limited to, locations CONUS/OCONUS based on data acquisition sites.

END OF SECTION F

G. CONTRACT ADMINISTRATION DATA

G.1 CONTRACTING OFFICER RESPONSIBILITIES

The Contracting Officer (KO) is the sole and exclusive Government official with actual authority to take actions that bind the Government under this contract.

The right to issue contract modifications, change terms and conditions, and terminate the contract is reserved solely for the Contracting Officer.

G.2 CONTRACTING OFFICER’S REPRESENTATIVE RESPONSIBILITIES

The Contracting Officer’s Representative (COR) is responsible for monitoring the contractor’s progress in fulfilling the technical requirements in the contract. The COR ensures that all required documentation and data are submitted in accordance with the PWS requirements. Should the contractor fail to fulfill the contractual requirements, the COR must inform the contractor of such failure. The COR will inform the Contracting Officer of any technical or contractual problems or delays. The COR maintains administration records, approves invoices, and performs final inspection and acceptance of work performed under this contract.

The COR has no actual, apparent or implied authority to bind the Government. The COR may not grant the contractor permission to deviate from the requirements stated in the contract, nor direct the contractor to perform any work outside the scope of the contract. Changes in the contract requirements, price, or terms and conditions will only be made by the CO via properly executed modifications to the contract. The Contracting Officer will appoint a COR and issue a COR Designation Letter stating the authority of the COR. The contractor will receive a copy of the COR designation Letter.

The services to be performed by the contractor during the period of this contract shall at all times and in all places be subject to review by the Contracting Officer or authorized representative(s).

G.3. CONTRACT ADMINISTRATION

The contractor shall establish processes and assign appropriate resources to effectively administer the contract. The contractor shall respond to Government requests for contractual actions within two business day. The contractor shall designate and maintain a single point of contact between the Government and contractor personnel assigned to support the contract.

G.4 INVOICE REQUIREMENTS

The invoice shall include charges authorized by the COR and Contracting Officer which are within scope of this contract (e.g., travel, materials) and reflect the details specified below.

G.4.1 PAYMENT INFORMATION

Invoices shall be submitted to GSA ASSIST (AASBS) and the Central Invoice System (CIS) web-based Order Processing System (https://portal.fas.gsa.gov/). The COR and the GSA Customer Account Manager or Contract Specialist must approve each invoice in CIS prior to payment. Failure to enter an invoice into the GSA AASBS web-based system may result in a rejection.

An invoice for completion of each deliverable shall be electronically delivered to the COR via the GSA electronic contract management system (AASBS) by the twentieth calendar day of the month following delivery for client and GSA acceptance. A copy of the invoice shall be attached to the associated deliverable “Acceptance Report” posted in GSA AASBS located on the web at https://portal.fas.gsa.gov/web/guest. The invoice shall be submitted on official company letterhead.

For reimbursable expenses, the invoiced charges shall not exceed the limit specified in the contract. No charges shall be paid by the Government, which are not specifically identified in the task and approved in advance by the Government. Copies of receipts, travel vouchers, etc., completed in accordance with Government Joint Travel Regulations and FAR 31.205-46 shall be attached to the invoice to support the charges. Original receipts shall be maintained by the contractor and made available to Government auditors upon request.

The contractor shall submit Requests for Payments in accordance with the format contained in General Services Administration Acquisition Manual (GSAM) 552.232-25, PROMPT PAYMENT (NOV 2009), to be considered proper for payment.

The contractor shall provide the following payment information for GSA use. It must be an exact match with the information under the contract number in the AAS Business Systems Portal, AASBS Contract Registration (not the contractor’s company or individual representative’s registration) as well as with the information under the contractor’s Data Universal Numbering System (DUNS) number in the System for Award Management (SAM), https://www.sam.gov/SAM/. Mismatched information will result in rejected payments.

G.4.2 INVOICE INFORMATION

The contractor shall provide the following information on each invoice submitted:

a. Invoice Number – must not include any special characters; AASBS and the invoice must match

b. ACT Number from GSA Form 300, Block 4

c. GSA Task Order Number – must match AASBS

d. Contract Number from GSA Form 300, Block 3

e. Point of Contact and Phone Number

f. Remittance Address

g. Delivery date or Period of Performance for the billing period

h. Charges, identified by deliverable or line item(s), with a narrative description of the service performed. Labor, reimbursable costs, and other charges (e.g., G&A) must be broken out.

i. Prompt Payment Discount, if offered

j. Total Invoice Amount – must match the acceptance information posted in AASBS; cannot exceed the current task order ceiling

k. Total cumulative task order amount and burn rate

G.4.3 INVOICING PROCESSING GUIDELINES

To ensure invoices are valid and processed timely, the contractor shall follow the guidelines listed herein when submitting invoices and include the required details per the terms and conditions of the contract.

a. Invoice Numbers – Invoice numbers can be up to 14 characters, alpha numeric text only, and no special characters or spaces. AASBS will automatically append to the end of each invoice number the Act#, which is not included in the 14 character limitation. Invoice numbers must be unique, no duplicates allowed.

b. Invoices Crossing Option Periods – Contractors may combine charges for multiple task items over two separate option periods on a monthly invoice for services completed and/or materials delivered or task items with mismatched performance periods completed during the monthly billing period invoiced.

c. Supplemental Invoices – Services must be billed to the month they are incurred. If trailing costs are invoiced, the contractor shall submit a supplemental invoice. If using the same invoice number previously used for the month, the contractor shall add an S following the original invoice number. If more than one supplemental invoice, then the contractor shall add a numeric indicator such as S1, S2, etc.

d. Resubmission of an Invoice – If an invoice has been rejected and the contractor is resubmitting, if using the same invoice number previously used for the month, the contractor shall add an R following the original invoice number. If more than one resubmission is required, then add a numeric indicator such as R1, R2, etc. Resubmissions of invoices shall always include all applicable supporting documentation regardless of whether it was attached to previously rejected invoices.

e. The contractor shall ensure submitted invoices and supporting documentation are submitted in accordance with contract terms and conditions. Invoiced costs posted in AASBS invoices must match the task item and costs on the attached invoice and be within the funded limits.

f. The contractor shall ensure the invoice prices/rates, labor hours, and labor categories conform to the terms and conditions of the contract.

g. The contractor shall ensure Labor Hours for each billed contract line item do not exceed the contract ceiling limit. (If applicable)

h. The contractor shall ensure reimbursable costs are approved, funded, valid, and in the case of time and materials, labor-hour, or cost contracts, costs associated with such other direct costs are allowable and have been determined to be reasonable and directly associated with contract and billed to the correct task item and period they were approved in. For reimbursable line items invoiced, the contractor shall have received prior approval and supporting documentation shall be supplied to support the costs and dates and invoiced amounts do not exceed the line items and total amounts authorized.

i. The contractor shall ensure travel costs are supported having supporting records of Government approval, are approved, funded, and valid by the contract, and billed to the correct task item and period they were approved in.

j. The contractor shall ensure the period of performance invoiced is within the period of performance of the contract and invoiced task items.

k. The contractor shall ensure all subcontractor rates are valid and have been properly reviewed and substantiated by the prime contractor.

G.4.4 FINAL INVOICE/CONTRACT CLOSEOUT

The invoice for final payment must be so identified and submitted within 60 calendar days from task order completion. No further charges are to be billed. The contractor may request an extension of 60 days from the GSA CO to submit the final invoice. Mark with the word FINAL (even if it is a zero amount). Reimbursable travel costs shall be billed at a predetermined rate and are not subject to final rate approval. After the final invoice has been paid, the contractor shall furnish a completed and signed Release of Claims (GSA Form 1142, or equivalent) to the CO. This Release of Claims is due within fifteen calendar days of final payment.

G.5 MEETINGS

The contractor shall organize, attend and/or host, and/or facilitate program meetings as directed by the Government.

The contractor shall provide meeting agendas/presentation material as requested by the COR within two business days of the meeting date. Subsequently as requested by the COR, the contractor shall provide meeting minutes/action items within five business days after meeting.

G.5.1 KICK OFF MEETING

A kickoff meeting provides an opportunity for the Government to provide details of the contract and for the contractor to demonstrate an understanding of the work to be performed and completed under this PWS. Within ten business days of the contract award, the contractor shall attend a kick off meeting in order to review the intent and details of the contract. The meeting will include an orientation and overview of the contact scope and terms and conditions. The location will be a mutually agreed upon after award and may be facilitated by the Contracting Officer. The meeting may be accomplished through telecom or other alternative means.

G.5.2 PERIODIC PROGRESS MEETINGS

The Contracting Officer, COR, and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor’s performance or progress of outstanding task orders. These meetings shall be at no additional cost to the Government.

END OF SECTION G

H. SPECIAL CONTRACT REQUIREMENTS

H.1 TRAVEL REQUIREMENTS

Travel is required to various CONUS and OCONUS non-hazardous locations. The Contractor shall travel as initiated by written tasking. The contractor shall ensure that travel expenses are incurred in accordance with the Limitations set forth in FAR 31.205-46. Personnel may be deployed to OCONUS locations; therefore, the government COR must approve all travel in advance.

The Government cannot establish the locations and the duration of travel at the…