PWS.pdf

Performance Work Statement (PWS)

For

448 Supply Chain Management Wing

(448 SCMW)

420 Supply Chain Management Squadron

Supply Chain Risk Management (420 SCMS / SCRM)

PR # FD2030-20-00460

ID/IQ: FA4452-19-D-A00X

Task Order ####

Original Date: Mar 20

Revision Date #1:

SUPPLY CHAIN RISK MANAGEMENT GEOSPATIAL SERVICES

Procuring Office: Air Force Sustainment Center Strategic Contracting Squadron

AFSC/PZAAC

3001 Staff Drive Tinker AFB, OK 73145

Requiring Office: 448 Supply Chain Management Wing Air Force Sustainment Center 3001 Staff Drive Tinker AFB, OK 73145

SCRM GEOSPATIAL SUPPORT SERVICES

PWS for PR FD2030-20-00460

PWS, FD2030-20-00460

TABLE OF CONTENTS

SECTION 1.0 DESCRIPTION OF SERVICES ________

1.1 Background

1.1.1 Purpose…………………………………………………………………………... 3

1.1.2 Scope…………………………………………………………………

1.2 Task Requirements

1.2.1 Task 2 –Requirements Elicitation…………………………………………..………3

1.2.2 Task 5 - Geospatial Data Support…………………………………………….…

1.2.3 Task 10 – Application Development, Modernization, and Sustainment…………...4

1.2.3.1 – Application Development/Modernization Planning Activities………...…4

1.2.3.2 - Application Development/Modernization Programming…………………4

1.2.3.3 - Application Sustainment………………………………………………….5

1.3 Services Summary…………………………………………….…………………………….5

1.4 Data Deliverables…………………………………………….…………

1.5 Security Requirements………………………………………………………………………………………………7

1.6 Supplemental Task Order Contractual Requirements

1.6.1 Place of Performance…………………………………………………

1.6.2 Hours of Operation………………………………………………

1.6.3 Replacement Personnel………………………………………………

1.6.4 Information Assurance Certification Requirements……………………

1.6.5 Information Assurance Workforce Training………………………………………...9

1.6.6 Cybersecurity………………………………………………………………………..9

1.6.7 Contractor Identification...…………………………………………………………..9

1.6.8 Non-Disclosure Agreements…………………………………………………….…..9

1.6.9 Travel……………………………………….……………………………………….10

1.6.9.1 Travel Reimbursement………………………..……………………………………

1.6.10 Data Rights and Non-Commercial Computer Software…………………………..…10

1.6.11 COTS Manuals and Supplemental Data………………………………………..……10

1.6.12 Accident Report Procedures…………………………………………………….….10

1.6.13 Organizational Conflict of Interest (OCI)……………………………………….…10

1.6.14 Identification and Mitigation Plan……………………………………………….…10

1.6.15 Violation Reporting………………………………………………………………...10

1.6.16 Quality Assurance………………………………………………………………… ..10

1.6.17 Transition Plan……………………………………………………………………...11

1.6.18 Kickoff Meeting…………………………………………………………………….11

1.6.19 Uses and Safeguarding of Information…………………………………………

1.6.20 For Official Use Only (FOUO)……………………………………………………...11

1.6.21 Contractor Manpower Reporting…………………………………………………

1.6.22 Antiterrorism Training……………………………………………………………

1.6.23 Government Furnished Property & Services………………………………………..12

1.6.24 Government-Furnished Supplies/Property………………………………….……….12

1.6.25 Government-Furnished Property…………………………………………………….12

2.0 Mission Essential Services …………………………………………………………………..12

1.0 DESCRIPTION OF SERVICES

1.1 BACKGROUND:

The mission of the 448 Supply Chain Management Wing, Air Force Sustainment Center, Supply Chain Risk Management (SCRM) Cell provides integrated geospatial solutions that enhance the visibility of supply chain to identify any vulnerabilities that may delay delivery to supply chain customers. SCRM provides situational awareness and other Supply Chain Risk Management information and services by synchronizing geospatial requirements and identifying potential vulnerabilities for Air Force Materiel Command risk owners, 448 SCMW organizations, AFLCMC lifecycle partners and the greater SCRM community. The 448 SCRM shares geospatial data or digital maps created by SCRM SMEs with stakeholders and provides guidance to other SCRM and supply chain offices. The location-based-risk geospatial vision results in geospatially shared situational awareness across the 448 Supply Chain Management Wing. This effort is also aimed at optimizing 448 SCMW investments in geospatial data, technologies, services, and capabilities. This PWS involves support at Headquarters (HQ) 448 SCMW and/or its affiliated installations and units.

1.1.1 Purpose.

This PWS identifies and defines the requirements for support to the 448 SCMW and the associated Supply Chain Risk Management program under the Air Force Sustainment Center (AFSC) Strategic Contracting Division (PZAA) decentralized implementation of the Air Force (AF)-Wide Geospatial Support Contract.

1.1.2 Scope.

The objective of this PWS is to provide Geospatial Program Support for the 420 SCMS / SCRM under the management of the 448 SCMW. The 420 SCMS is responsible for organizing and executing the 448 SCMW geospatial program and capabilities. The AFSC geospatial system infrastructure involved in this task order currently includes National Geospatial Agency (NGA) geospatial system infrastructure, AFIMSC (Air Force Installation Mission Support Center) installation-level geospatial infrastructure, Homeland infrastructure from the Department of Homeland Security, the Federal Emergency Management Agency (FEMA), National Aeronautical & Science Administration (NASA), the National Oceanic and Atmospheric Administration (NOAA), the United States Geological Society (USGS), and other Department of Defense and US Government sources-as part of the USAF Logistics Geospatial Information & Systems capability (also known as LGI&S). SCRM requires a forward looking capability that provides alerts and visual indications when hazards occur, or will occur, in close proximity to the Air Force Supply Chain and its sub-tier structure. The sustainable geospatial solution should provide a programmed alert capability that identifies hazards for vulnerabilities in close proximity to, those increasing in severity, and those presenting immediate risk to the 448 SCMW and its stakeholders. Support will require contractor to operate within Non-secure Internet Protocol Router Network (NIPRNET) and the Secure Internet Protocol Network (SIPRNet).

Contractor must have the ability to work within Air Force Geospatial Information Management System (AFGIMS), ability to create custom products within the ARC GIS GeoEvent Server / Processor and the ability to quickly locate and access national Event based Alert systems such as the Integrated Public Awareness Warning System, National Response Framework, National Incident Management System, National Disaster Medical System, etc. Also, when applicable must have ability to incorporate secure sources for developing more effective awareness; including but not limited to targeted industrial commodity indices, academic and commercial risk models and external alerts on global events. And, must be able to maintain backup capability within NGA platform.

The contractor must have the ability to expand the advanced analytics capability, to connect supply chain tiered structure network visualization, and to add/modify existing supply chain network visualization, monitoring and alert system. The following requirements exemplify focus areas, but are not all inclusive: supervised or unsupervised 24 hour monitoring of supply chain networks and suppliers, to align supply chain sub-tier location data, industry data, assistance with information gathering for supplier studies, advanced time series and proximity analysis, ability to conflate and measure global, country, local and academic data to conduct activities such as highlighting suppliers most at risk for emerging risk events; to identify suppliers’ time to survive.

1.2 TASK REQUIREMENTS:

1.2.1 Task 2 –Requirements Elicitation.

Contractor shall discover requirements and convert them to mission-driven and value-based execution plans for establishing an advanced geospatial Supply Chain Risk Management program, beginning with a rapid development design for future (3) years; focused on blending disciplines and combing emerging technology within the 448 SCMW SCRM geospatial platform. This may include, geospatial systems, geospatial applications, system integrations (interoperability) with other systems (geospatial and non-geospatial, artificial intelligence and cryptographic), hardware, software, and manpower. The contractor shall perform activities necessary to gain detailed understanding of 448 SCMW requirements such as stakeholder interviews, questionnaires, user observations, workshops, brainstorming, use cases, role playing, and prototyping.

1.2.1.1 Requirements Analysis and Synthesis.

Contractor shall analyze and synthesize collected requirements into coherent documents for planning, programming, budgeting, design, development or other purposes. This may include the development of conceptual capability designs (i.e., “mockups”), system integration schematics, prototypes, technical reports, etc. (CDRL 0001, CRDL 0002, CDRL 0003, and CDRL 0004)

1.2.2 Task 5 – Geospatial Data Support. Contractor shall provide data manipulation support involving both tabular data and geospatial vector data. This support is primarily focused on geospatial data, however, this task order does require some interaction with non-geospatial data to facilitate integration, interoperability, and geospatial-enablement.

1.2.2.1 The Contractor shall provide geospatial data manipulation support for the 420 SCMS/SCRM.

When applicable, contractor shall perform data manipulation support in preparation for, or response to, risk events (e.g., hurricanes, Floods, terrorism, cyber-attacks, geopolitical turmoil, etc.). During these periods of enhanced risk, the contractor may be asked to provide expedited geospatial data manipulation support in response to the crisis. The contractor should estimate 1-2 risk occurrences, 1-2 calendar days each, during the performance period.

1.2.2.2 Data Standards Compliance.

Contractor shall process data requests and adhere to data standards as required. All related contractor actions shall be reviewed and approved by the Government Program Manager/COR. Data standards compliance shall involve, for example, standards governed by the SCRM geospatial focal point at AFIMSC and higher headquarters, including but not limited to the Spatial Data Standards for Facilities, Infrastructure, and Environment (SDSFIE). In some instances, the coordination of multiple Government standards requires resolution and alignment between standards, for example, cross-walking SDSFIE with the National Emergency Number Association (NENA) standards.

1.2.2 Editing and Maintaining Vector Data.

1.2.3.1 The contractor shall ensure geospatial vector data is delivered in GIS format (e.g., ESRI format) unless otherwise stipulated in writing by Government Program Manager/COR. Geospatial vector data shall be created or manipulated using industry standard techniques, for example, Coordinate Geometry (COGO) techniques.

1.2.3.2 The contractor shall also perform geospatial data loading or transfer activities. Data manipulation and processing shall occasionally be required for geo-enabling or system integration purposes. Examples shall include, but are not limited to, geo-referencing business system data via geocoding street addresses.

Digital Model Creation. Contractor shall manipulate data and/or otherwise geospatially reference non-geospatial data using industry-leading tools and techniques such as geocoding protocols.

1.2.3 Task 10 – Application Development, Modernization, and Sustainment.

Contractor shall support geospatial capability implementation, modernization, and sustainment. Contractor shall provide remote technical support regarding web-based capability development and sustainment issues consistent with USAF and SCRM policy. Existing SCRM geospatial capabilities leverage ESRI software products, and JavaScript technologies and, therefore, contractor personnel must, at a minimum, have extensive experience applying these technologies to sustain existing SCRM geospatial capabilities. Contractor shall develop and demonstrate a documented strategy for limiting outages to ensure the SCRM geospatial system(s) operate during standard business hours, 5 days a week, and 52 weeks a year (discounting federal holidays). Personnel accessing

SCRM geospatial system servers on Task 10 MUST possess an IAT Level II, Security+ Certification IAW DoD 8570.01-M and AFMAN 33-285 prior to full contract performance start. Contractors shall obtain and retain Functional System Administrator (FSA) accounts in alignment with AFI 33-115.

1.2.3.1 Application Development/Modernization Planning Activities. Contractor shall perform activities associated with planning for mission-enhancing geospatial capabilities, for example, locating existing ArcGIS Server and/or Portal for ArcGIS website widgets and adapting them for SCRM mission exploitation. Planning associated with such capability adoption shall require stakeholder interviews, user observations, brainstorming, use cases, role playing, prototyping, and continuous identification of SCRM-related authoritative data sources.

1.2.3.2 Application Development/Modernization Programming. Contractor shall perform activities associated with creating or editing code for mission-enhancing geospatial capabilities. In these instances, the contractor shall create, modify, implement, and maintain web-based geospatial capabilities, for example, ArcGIS Server and/or Portal for ArcGIS website widgets and adapting them for SCRM mission exploitation. The contractor shall be forthcoming with suggestions of existing knowledge of industry best practices and professional services to maximize development and modernization potential.

1.2.3.3 Application Sustainment. Contractor shall perform sustainment activities for SCRM geospatial applications and capabilities. Contractor shall sustain or otherwise modify existing applications as necessary to address functional owner requirements, to meet interoperability requirements, to comply with new security policies, to ensure compatibility with a sustainment technical refresh, or to respond to changes to the AF Network. Contractor shall modify existing or create new web tools to fit necessary mission needs. Contractor shall manage all “presentation tier” aspects of the SCRM geospatial system(s) including the SCRM Provisional Map. Contractor shall manage and monitor the availability of all SCRM-related web sites, web services, and web tools while minimizing geospatial capability downtime. Contractor shall frequently be required to publish map services for new or updated map/data requests. Contractor shall manipulate geospatial data using ESRI’s ArcMap and/or ArcCatalog and/or SQL Developer, for example, to provide the clearest and most relevant map services. Application Sustainment shall also include “geospatially-enabling” data from existing business and/or mission systems. Geospatially enabling existing systems shall include, but is not limited to, interacting with legacy system data and the system itself allowing the geospatial presentation and analysis of the legacy system’s data within, or outside of, the legacy, data-sourcing IT system. Contractor shall create coherent documentation of workflows, processes, and other technical details associated with geospatial capability operations and sustainment. Contractor shall provide resolution to include Government approved corrective action for customer complaints within 72 hours of initial receipt of customer complaint When applicable, contractor shall perform the activities associated with this task in support risk events (e.g., hurricanes, Floods, terrorism, cyber-attacks, geopolitical turmoil, etc.) as well as during these periods of enhanced risk. No less than one contractor representative with the required technical expertise assigned on this task shall be available to attend via telecon short-notice (i.e., 30 minutes or less).

1.3 Services Summary (SS).

The Services Summary table summarizes the most important performance objectives and performance thresholds (specific standards) as identified within the body of the PWS. The absence of any performance objective and threshold from this SS shall not detract from its enforceability nor limit the rights or remedies of the Government under any provision of the contract/task order. The Government Program Manager/COR shall evaluate the Contractor on each SS performance objective on a monthly basis and provide a copy of the evaluation to the Contracting Officer.

Table 1: Services Summary Performance Objective PWS Para Performance Threshold (Standard) Contractor shall provide all data 1.2, 1.4 & Performance is acceptable when there are no deliverables IAW the timeframes within the PWS

Table 2 typographical or content errors and no more than two late data deliverables per quarter.

Contractor shall develop and demonstrate a documented strategy for limiting outages to ensure the SCRM geospatial system(s) operate during standard business hours, 5 days a week, and 52 weeks a year (discounting federal holidays).

1.2.3

No more than four system outages should occur per period of performance year. Outages must be reported to the Government Program Manager/COR within 15 minutes of contractor-confirmed outage.

Each outage shall be less than 4 hours in duration.

Contractor shall provide resolution to include Government approved corrective action for customer complaints within 72 hours of initial receipt of customer complaint.

1.2.3.3

Performance is acceptable when there are no more than one late resolution and/or corrective action submission to a customer complaint per period of performance and there are no recurrence of recognized process problems.

Note: The government reserves the right to inspect or test services that have been tendered for acceptance. The government shall require performance of any nonconforming services at no increase in contract price. If performance shall not correct the performance issue or correction is not possible, the government shall seek an equitable price reduction or be forced to commence the termination process. Past performance history shall be reported in Contractor Performance Assessment Reporting System to reflect satisfactory or unsatisfactory performance.

1.4 Data Deliverables.

The following items are outputs which fall within the scope of this task order and are illustrative of the type of work the Government requires. Deliverables required by the Government IAW this PWS shall have a Data Item Description (DID) and shall be provided in a commercially acceptable format. All deliverables shall be reviewed for timeliness, accuracy and format. If a deliverable due date falls on a weekend or holiday, the Contractor shall submit the deliverable on the last work day prior to the due date. One electronic copy of each output shall be delivered to the Government Program Manager/COR on date specified. In addition, unscheduled project updates shall be provided by government/COR. Table 2, Data Deliverables, provides a list of the required PWS deliverables;

however, Table 2 shall NOT be construed as an all-inclusive list of required PWS deliverables; reference PWS Tasks for all required deliverables. If not otherwise stated below, all required deliverables shall be provided to the Government within a mutually agreed timeframe upon request by the Government Program Manager/COR or, if not requested by the Government Program Manager/COR, no later than the end of the Task Order Period of Performance.

Deliverables are to be transmitted electronically with a cover letter, on the prime Contractor’s letterhead, describing the contents. The Contractor shall provide hard copy deliverables as required per Government Program Manager/COR request. All deliverables shall be produced using recommended software tools/versions as approved by the Government. All reports shall be accomplished utilizing a commercially acceptable format. Products and documentation delivered under this PWS become the property of the Government.

Table 2: Data Deliverables

The following deliverables shall be provided IAW CRDLs:

Title PWS Para. CDRL Requirements Elicitation Documents 1.2.1.1 & 1.4.1 CDRL 0001

Strategic Program Support Documents 1.2.1 & 1.4.2 CDRL 0002

SCRM Geospatial Application 1.4.3 CDRL 0003

SCRM Geospatial Capability Sustainment Continuity Handbook 1.4.4 CDRL 0004

Trip Reports 1.4.5 CDRL 0005

1.4.1 Requirements Elicitation Documents.

Requirements documentation shall include records of stakeholder interviews and/or questionnaires, workshop discussions, role playing sessions, brainstorming sessions, and authoritative data sources. Requirements documentation must capture critical information (e.g., use-case scenarios, mockups, etc.) to be used by technical solution developers for creation of solutions that meet stakeholder requirements (CDRL 0001).

1.4.2 Strategic Program Support Documents.

Strategic Program Support documentation involves a variety of program support documents to help advance the SCRM Geospatial Integration program. Documents shall include, but not be limited to, one-to-two page white papers (e.g., USAF Point Papers) outlining program situations and/or challenges and concluding with program advancement recommendations as well as more lengthy, detailed strategy documents (e.g. program or capability CONOPS documents, business case analyses, DoDAF-aligned architecture documents, etc.). Contractor can estimate creating between two and four Strategic Program Support documents during the performance period

(CDRL 0002).

1.4.3 SCRM Geospatial Application.

SCRM Geospatial Application shall provide situational awareness and leadership awareness of supplier locations, subtier locations; subsequent ambient and imminent risk based on internal and external authoritative data.

Application may require re-hosting of APIs, development of integrated solutions, migration to and from host locations. Contractor must be able to work in classified and unclassified environment. Contractor can estimate sustainment and modernization of the SCRM geospatial application to occur throughout the performance period

(CDRL 0003).

1.4.4 Geospatial Capability Administration Continuity Handbook.

Contractor personnel performing geospatial analysis activities (e.g., logistics capability analysis, development, sustainment, etc) shall document analysis tactics, techniques, and procedures in a Continuity Handbook and include software, data sources, tools, and step-by-step procedures so that other geospatial analysts can replicate the processes in a time of need (CDRL 0004).

1.4.5 Trip Reports.

Within five workdays after completion of travel, contractor shall provide a trip report to the Government Program Manager/COR for approval. The trip report shall include, but not be limited to the purpose of the trip, name(s) of traveler(s), dates of travel, location of travel, key personnel contacted, discussion, and conclusions/recommendations

(CDRL 0005).

1.5 Security. Contractor to comply with all of the Geospatial basic IDIQ Security Section 1.10.

1.5.1 Security Requirements. The contractor shall comply with the Defense Department (DD) Form 254.

Contract Security Classification Form and add attachments, Department of Defense Contract Security Classification Specification, and DoD 522.22-M, National Security Program Operating Manual (NISPOM), DoD Directive 8500.1, DoD 5200.2, AFI 31-501, and AFI 33-202.

1.5.2 Contract personnel must have a SECRET clearance at the time of the proposal submission, and must maintain the security required for the life of the contract.

1.5.3 Safeguarding Classified or Unclassified Information. Contractor shall meet Air Force standards for storing, processing, and handling classified information. The contractor shall be responsible for safeguarding all government equipment, information, and property for contractor use. At the close of each work period, government facilities, equipment, and materials shall be secured.

1.5.4 Computers used for transmitting classified information must not be connected to unclassified networks or peripherals (copiers, printers, etc). Additionally, computers, network devices, and equipment associated with the transmission of classified information (confidential or secret) will be secured in an approved security container, secure room or vault, or facility approved for the level of classification transmitted. For example, if collateral classified information (confidential or secret) is transmitted via SIPRNet, the SIPRNet computer terminal, nodes, and other associated equipment will be secure in a secure room or vault meeting the requirements of DoDM 5200.01, Volume 3, Enclosure 3.

1.5.5 The contractor will be required to attend meetings designated as classified. The contractor shall ensure all contract personnel, five business days prior to on site arrival have the required security clearances. The Contractor shall bear all costs associated with obtaining the required security clearance and/or required background investigations. All personnel employed by the contractor in the performance of this contract, or any representative of the contractor, shall abide by all security regulations.

1.5.6 The contractor shall implement and administer a security program to ensure that classified information and document are protected.

1.6 SUPPLEMENTAL TASK ORDER CONTRACTUAL REQUIREMENTS

This Task Order PWS provides contractual requirements for enhanced guidance respective to the AF geospatial IDIQ. The Contractor shall cross-reference this Task Order PWS’s respective paragraphs with the respective initial contract’s PWS paragraphs by title to ensure all contractual requirements are met. Paragraph numbers within this Task Order PWS and the initial contract’s PWS are different; therefore, the Contractor shall not cross-reference PWSs by paragraph number. In the event that there is a conflicting statement between this PWS and the initial contract PWS, this PWS shall take precedence.

1.6.1 Place of Performance.

Contractor performance of most tasks at a contractor-owned facility is appropriate and permissible other than those identified as requiring travel in this PWS. The 420/SCMS SCRM Tinker AFB, OK is responsible for supporting various echelons of the SCRM hierarchy to include units, installations, and headquarters levels (e.g., AFMC/SCRM, 448 SCMW and the 448 geo-agnostic sub-organizations) resulting in travel and/or remote support. The contractor shall be responsible for, and shall comply with, all rules and regulations applicable to contractor performance in foreign countries.

1.6.2 Hours of Operation.

In accordance with Section 1.7.6 of the Air Force Geospatial Support ID/IQ PWS, core duty hours are 0800-1700, Monday through Friday. Some activities for this task may need to be performed outside of normal business hours (e.g., information system maintenance to mitigate downtime during peak usage hours). Contractor leadership shall coordinate with the Government Program Manager/COR, in advance, when performance of activities outside of normal business hours is required. Contractor personnel can be called in for an emergency; this is a rare event, which may or may not occur during the term of the task order. The contractor must remain within the negotiated task order hours. Contractor leadership shall coordinate with the Government Program Manager/COR regarding planned absences (e.g., vacation leave) of key contractor personnel at least two weeks prior to the absence to ensure no mission impact.

1.6.3 Replacement Personnel.

The contractor shall ensure any vacancies are filled with qualified personnel within 10 calendar days of vacancy, unless approved in writing by the Contracting Officer and there is no AF mission impact.

1.6.4 Information Assurance Certification Requirements.

IAW DoD 8570.01-M Information Assurance Workforce Improvement Program, and AFMAN 33-285, Cybersecurity Workforce Improvement Program, the contractor shall provide IAT Level II and/or IAM Level II certifications for contractor personnel as required for PWS task requirements. Positions responsible for performing any of these functions, regardless of the contractor’s occupational title shall be identified as part of the IA workforce and must comply with DoD 8570.01-M Information Assurance Workforce Improvement Program and AFMAN 33- 285 Cybersecurity Workforce Improvement Program mandatory procedures to meet certification levels in prior to contract performance start.

1.6.5 Information Assurance Workforce Training.

IAW DFARS clause 252.239-7001, Contractor personnel shall comply with all respective MAJCOM security requirements pursuant to DODI 5200.2, DOD Personnel Security Program (PSP), which requires DoD military, and civilian personnel, as well as DoD consultant and Contractor personnel who perform work on sensitive automated information systems (AIS) to be assigned to positions which are designated sensitive. All personnel shall complete Annual Information Assurance training by on line computer based training (CBT).

1.6.5.1 All personnel shall comply with DoD 8570.01-M, Information Assurance Workforce Improvement Program and AFMAN 33-285, Cybersecurity Workforce Improvement Program, as required in this PWS, and shall provide appropriate certification(s) at least 10 calendar days before task orders’ period of performance start date and start date for new and/or replacement individuals.

1.6.5.2 Contractor personnel who do not have proper and current certifications shall be denied access to DoD information systems for the purpose of performing IA functions.

1.6.6 Cybersecurity.

The Contractor shall ensure that personnel accessing information systems have the proper and current IA certification to perform IA functions in accordance with DoD 8570.01-M, Information Assurance Workforce Improvement Program and AFMAN33-285 Cybersecurity Workforce Improvement Program.

1.6.7 Antiterrorism Training.

Within 30 calendar days after task order start, all contractor personnel shall complete Antiterrorism Level I training, as required by DODI 2000.16. Newly hired personnel shall complete the Antiterrorism Level I Training within the first 30 calendar days of their employment. Refresher Antiterrorism Level I Training shall be completed and documented annually thereafter. The training is provide at https://atlevel1.dtic.mil/at/ and also available through Advanced Distributed Learning Services (ADLS), Force Protection Course (ZZ133079) at https://golearn.csd.disa.mil/kc/main/kc_frame.asp for AF Portal access or https://golearn.csd.disa.mil/kc/login/login.asp for non-portal login.

1.6.8 Contractor Identification.

Each Contractor employee shall, while on base, wear in plain view on the upper portion of the outer garment a metal or plastic identification badge to be furnished by the Contractor, containing the company name, employee name, and the section where the employee works. Each contractor personnel shall also, while on base, be required to wear AF-approved or provided picture identification badges so as to distinguish themselves from government employees.

Contractor employees shall clearly identify themselves as "Contractors" at all times, in all communications and representations, including in the workplace, at meetings, in conversations, telecommunications, mail, electronic mail (e-mail), and faxes, whether with Government personnel, other Contractor personnel, or with the public.

Contractors with access to the base Local Area Network (LAN) or with an official Government e-mail address shall clearly identify themselves as “Contractor” in the email signature block and the designation "CTR" in the global address. The Contractor shall notify the Government if the "CTR" designation is not included in the global address.

1.6.9 Non-Disclosure Agreements.

Due to the sensitive nature of the data and information being worked with on a daily basis, of this requirement the contractor shall require on-site personnel and others as mutually agreed to by the contractor and government program manager/COR to sign a non-disclosure statement to protect non-public information of the Government.

The Contractor shall complete and return the Government-provided non-disclosure statement within 15 calendar days after award, or prior to new hires reporting for duty, to protect unauthorized disclosure of sensitive or proprietary information. Copies of signed non-disclosure statements shall be provided to the COR.

As required, all contractor personnel assigned shall be required to complete additional non-disclosure statements prior to technical interchanges to ensure information that is considered sensitive or proprietary by other companies, corporations, or businesses is not compromised. Signed non-disclosure statements shall be provided to the COR within 15 calendar days after task order award.

1.6.10 Travel.

The contractor shall travel for performance of this PWS. All travel arrangements shall be the responsibility of the contractor, to include airline, hotel, and rental car reservation and all other travel arrangements associated with the trip (e.g., conference reservation). At least five working days prior to the travel start date, the contractor shall submit a travel itinerary to the COR. The COR shall confirm the need for travel. No later than five workdays after conclusion of travel, a trip report shall be submitted to the COR for approval. Table 3 below lists the forecasted travel, which is consistent for each period of performance.

Table 3: Forecasted Travel Number of

Trips Per Year Number of

Persons Number of Days Trip Purpose

2 4 3-5 Consulting Visits to SCRM, Tinker AFB, OK 1 4 5 Annual SCRM Partnership Review, Tinker AFB, OK 1 3 3-5 Misc. TDYs (visits/conference)

1.6.10.1 Travel Reimbursement.

All travel shall be included in the firm fixed price portion of this contact and will not be reimbursed separately. The Government estimates the following required travel in Table 3 above.

1.6.11 Data Rights and Non-Commercial Computer Software.

The Government reserves unlimited rights to all documents/material produced under this Contract. All documents and materials, to include interfaces and source code written under this Contract shall be Government-owned and are the property of the Government with unlimited rights and privileges of the ownership and intellectual property rights belonging exclusively to the Government. All materials produced for the Government shall be the sole property of the Government and may not be used for any other purpose without written permission from the PCO. These rights do not abrogate any other Government rights under the applicable Data Rights clause(s). Data rights for noncommercial software will be pursuant to the applicable DFARS clauses contained in the contract.

1.6.12 COTS Manuals and Supplemental Data.

The contractor shall provide documentation for all systems services delivered under this Task Order. The contractor shall provide commercially available off-the-shelf (COTS) manuals, supplemental data for COTS manuals, and documentation IAW best commercial practices (i.e. CD-ROM, etc.). This documentation shall include users’ manuals, operators’ manuals, maintenance manuals, and network and application interfaces if specified in this task order.

1.6.13 Accident Report Procedures.

In the event of an accident on government property, or involving government personnel or property, the contractor shall submit a report within 72 hours to the COR in letter form that shall include the following: (1) the time and date of occurrence, (2) the place of occurrence, (3) a list of personnel directly involved, (4) a narrative or description of the accident to include chronological order of the accident and circumstances.

1.6.14 Organizational Conflict of Interest (OCI).

For general information on the handling of OCI, reference FAR 9.5.

1.6.15 Identification and Mitigation Plan.

The contractor must maintain an OCI Identification and Mitigation Plan (OIMP) acceptable to the Contracting Officer. The OIMP shall include, among other information, processes and internal controls necessary to identify, capture, and mitigate OCI activities at the subcontractor level.

1.6.16 Violation Reporting.

When the contractor discovers an OCI, potential OCI, or violation of the OIMP with respect to this task order, either by its own employee or that of one of its subcontractors, the contractor shall in writing report to the COR with prompt and full disclosure of the incident or incidents. The report shall include a description of the OCI violation and proposed contractor actions to avoid, neutralize, or mitigate and/or preclude repetition of the violation. After conducting necessary inquiries and discussions, the Contracting Officer and the contractor shall agree on appropriate action, or the Contracting Officer shall take such action afforded under the terms of the contact and statute, to include updating the OIMP.

1.6.17 Quality Assurance.

The Government shall perform periodic reviews of the contractor’s performance in accordance with the Contractor’s Commercial Quality Control Plan (QCP), along with the Government’s Quality Assurance Surveillance Plan (QASP) and the SS. The Government reserves the right to review services to be provided, including those developed or performed at the Contractor's facilities, to determine conformance with performance and technical requirements. Government quality assurance shall be conducted on behalf of the Contracting Officer. The COR shall be appointed to coordinate the overall quality assurance of technical compliance. The contractor shall bring problems or potential problems affecting performance to the attention of the COR as soon as possible.

1.6.18 Transition Plan.

1.6.18.1 Transition-In.

To minimize any decreases in productivity and to prevent possible negative impacts on additional services there will be a transition period for tasks 5 and 10, in accordance with this task order. This allows time for the Contractor key personnel to in-process and obtain required ID/CAC cards, computer system access requests, Security+ Certification (if/where required), and receive workplace and task orientation to ensure the entire team is in-place for period of performance start of this Task Order. During the transition-in period, the Contractor shall become familiar with performance requirements in order to commence full performance of services on the contract start date. The Contractor shall jointly work with and assume all responsibility from the incumbent work-force to ensure continuity of operations. There is no incumbent contractor to retain responsibility during the transition period The expectation is that the 420 SCMS work-force shall work closely with the new contractor to identify and explain any unique aspects of the requirement.

1.6.18.2 Transition-Out.

When there is a change in contractor upon award of a new contract there shall be a transition-out period associated with the transfer of responsibility, records, and data by the incumbent. The incumbent Contractor retains responsibility for work performed in each requirement until the end of the transition period. At no time shall employees from one Contractor act in a supervisory capacity over the other Contractor’s employees. The expectation is that the incumbent Contractor transition-out work-force shall work closely with the new Contractor to identify and explain any unique aspects of the requirement.

1.6.19 Kickoff Meeting.

Contractor shall attend a kickoff meeting specific to the TO requirement with the Government Program Manager/COR and the Contracting Officer at Tinker AFB and/or via telecom within seven working days of contract award. The Contractor shall provide concurrence with the date, time and location for the meeting via email notification to the Contracting Officer, at least three business days prior to the scheduled meeting.

1.6.20 Uses and Safeguarding of Information.

Information from the secure web site is considered to be proprietary in nature when the contractor number and the Contractor identity are associated with the direct labor hours and direct labor dollars. At no time shall any data be released to the public with the Contractor name and contract number associated with the data.

1.6.21 For Official Use Only (FOUO).

The contractor shall comply with DoD 5400.7-R, Chapter 4, DoD Freedom of Information Act (FOIA) Program, requirements. This regulation sets policy and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding FOUO material.

1.6.22 Contractor Manpower Reporting.

The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under each task order via a secure data collection site. The contractor is required to completely fill in all required data fields at http://www.ecmra.mil.

Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October* of each calendar year. Contractors may direct questions to the CMRA help desk.

1.6.23 Government-Furnished Property and Services

The contractor shall conform to the provisions of AFI 31-101, Integrated Defense (FOUO), for safeguarding the government-furnished buildings and all classifications of government property contained therein. All records, files, documents and work papers provided by the government or generated by the contractor in support of the contract are government property and shall be maintained and disposed of per AFI 23-111, Management of government Property in Possession of the Air Force.

1.6.24 Government-Furnished Supplies/Property

Contractor personnel shall be required to complete a DD Form 2875, System Authorization Access Request, prior to accessing certain government systems, which will be identified by the 420 SCMS PM after award. The contractor shall make prudent use of all government-furnished supplies, equipment, software and intangible property. At the conclusion of the order period of performance, or in the event of order termination, the contractor shall return to the COR all unused supplies, equipment, software and intangible property in the same condition as received, fair wear and tear acceptable. All products and materials procured or developed at government expense during the course of this order, whether tangible or intangible, are the property of the government and shall have no license encumbrances.

The contractor shall ensure all such procured or developed products are in the English language, readable and in a readily retrievable format that requires no additional software or tools beyond those already installed on government systems. The contractor shall ensure all intangible property is secured at the close of each business day. The contractor shall protect government property to prevent damage during the period of time the property is in the possession of the contractor. Contractor personnel shall use only government computers to access government systems and not for any activities not directly related to the requirements of this contract. Contractor personnel shall not load on or add to government computers any software not provided or approved by the government. Contractor personnel shall not connect any external storage devices to any government computers. The contractor shall have all government work-related compact discs or digital video discs scanned by AF information technology personnel before inserting into any government computer. Contractor personnel shall not use any personal compact discs or digital video discs in any government computer. The contractor shall utilize the Defense Switched Network (DSN) for long-distance calling when it is available.

1.6.25 Government-Furnished Property

The contractor shall be responsible for the protection of all Government property, if required, in its possession. The Contractor shall maintain the systems, records, and methodologies necessary for effective control of Government property. The Contractor shall confirm and approve the final inventory from Contract ---------------, Order ------------- --- with the COR. The Contractor shall conduct a joint inventory and turn in this property to the COR upon request or completion of the Contract. See GFP list attached to contract.

2.0 Mission Essential Services

N/A http://www.ecmra.mil/

ACRONYMS

Air Force (AF) Air Force Base (AFB) Air Force Installation Contracting Agency (AFICA) Air Force Manual (AFMAN) Air Mobility Command (SCRM) Authority to Connect (ATC) Authorization to Operate (ATO) Automated Information Systems (AIS) Business Enterprise Architecture (BEA) Business Mission Area (BMA) Business Process Re-engineering (BPR) Chief Information Officer (CIO) Clinger-Cohen Act (CCA) Command Cyber Readiness Inspection (CCRI) Computer Based Training (CBT) Concept of Operations (CONOPS) Content Standard for Digital Geospatial Metadata (CSDGM) Continental United States (CONUS) Continuity of Operations Plan (COOP) Contracting Officer Representative (COR) Coordinate Geometry (COGO) Courses of Action (COA) Data Item Description (DID) Defense Information Systems Agency (DISA) Department of Defense (DoD) Department of Defense Architecture Framework (DoDAF) Enterprise Information Technology Data Repository (EITDR) Enterprise Mission Assurance Support Services (eMASS) Environmental Systems Research Institute (ESRI) Federal Aviation Administration (FAA) Federal Data Center Consolidation Initiative (FDCCI) Federal Information Security Management Act (FISMA) Financial Improvement and Audit Readiness (FIAR) Freedom of Information Act (FOIA) Functional System Administrator (FSA) Geo Integration Office (GIO) Geospatial Information and Services (GI&S) Geospatial Information Systems (GIS) Global Positioning System (GPS) Headquarters (HQ) In Accordance With (IAW) Information Assurance (IA) Information Assurance Management (IAM) Information Resource Management (IRM) Information Technology Management Reform Act (ITMRA) Installation Geospatial Information and Services (IGI&S) Integrated Activities List (IAL) Joint Capabilities Areas (JCA) Joint Capabilities Integration Development System (JCIDS) Joint Common System Functional List (JCSFL) Joint Information Environment (JIE) Joint Strategic Capabilities Plan (JSCP) Local Area Network (LAN)

Major Command (MAJCOM)

ACRONYMS CONTINUED

Maximum-on-Ground (MOG) Mission Essential Function (MEF) Mobility Air Force (MAF) National Defense Authorization Act (NDAA) National Emergency Number Association (NENA) National Geospatial-Intelligence Agency (NGA) No Later Than (NLT) No Security Impact (NSI) Non-secure Internet Protocol Router Network (NIPRNet) Organizational Execution Plan (OEP) Other Direct Costs (ODC) Outside Continental United States (OCONUS) Performance Work Statement (PWS) Production Line Tool Set (PLTS) Public Affairs (PA) Quality Assurance Surveillance Plan (QASP) Quality Control Plan (QCP) Rapid Global Mobility (RGM) Risk Management Framework (RMF) Security Technical Implementation Guide (STIG) Services Summary (SS) Spatial Data Standards for Facilities, Infrastructure, and Environment (SDSFIE) Specialized Contracting Squadron (SCONS) Supply Chain Risk Management (SCRM) Supply Chain Risk Management Body of Knowledge (SCRMBOK) Supply Chain Management (SCM) Time Compliance Network Orders (TCNO) United States Air Force (USAF) United States Transportation Command (USTRANSCOM) Universal Joint Task List (UJTL) Unmanned Aerial Vehicle (UAV) Warfighter Mission Area (WMA) Wide Area Workflow (WAWF)