Statement of Work (SOW) DRAFT - 02232023.pdf

PR #: TBD

STATEMENT OF WORK

Revised as of: 23 February 2023

LAST UPDATED: 02/23/2023 PAGE 1/12

STATEMENT OF WORK (SOW)

FOR

CONTRACTOR SUPPORT SERVICES FOR THE U.S. COAST GUARD (USCG)

ACQUISITION DIRECTORATE BUSINESS INTELLIGENCE (BI) APPLICATION

1.0 GENERAL

The purpose of this Statement of Work (SOW) is to obtain Contractor services to further develop a Business Intelligence (BI) material solution utilizing the U.S. Coast Guard (USCG) Acquisition Directorate’s (CG-9) existing BI System.

1.1 BACKGROUND

CG-9 is responsible for providing data-driven metrics to ensure that the USCG is promoting projects with the requisite technical, contracting, and program management skills to deliver best-value systems and assets to USCG operating forces. The USCG currently has an existing system in place that can be utilized to integrate this requirement. The Acquisition Directorate has deployed and is operating a comprehensive acquisition performance management system using commercial off-the-shelf (COTS) BI software. The performance management system known as the Financial Management Procurement Data Repository (FMPDR) is a SAS-based BI system consisting of enterprise business intelligence, data integration, and performance management components. FMPDR receives data from multiple sources both internal and external to the USCG and displays the information for executives and managers through a portal, web reports and metrics.

1.2 SCOPE

The USCG has a requirement for Contractor services to develop and implement performance management data sets and measures in support of the Acquisition Directorate’s Strategic Plan and Action Plan goals and objectives utilizing CG-9’s existing BI system known as FMPDR.

Specifically, the Acquisition Directorate requires an organic capability to provide a holistic view of the CG-9 performance management data in a single dashboard/portal. The performance management data should be capable of searching and displaying relevant, holistic, and predictive information that will support strategic decisions, which will enable CG-9 to address critical business decisions and align resources with organizational plans.

In addition to supporting the goals and objectives of the Acquisition Directorate’s Strategic Plan and Action Plan, CG-9 requires an organic BI capability to implement performance management functions by integrating data from various sources into one portal that displays all measures, metrics and reports.

1.3 OBJECTIVE

The purpose of this Statement of Work (SOW) is to obtain contractor support services to assist the USCG CG-9, Office of Resource Management (CG-928) in the development and ongoing implementation of existing and new automated performance measures, system reporting, ../SCOPE%20PARAGRAPHS.doc

LAST UPDATED: 02/23/2023 PAGE 2/12

documentation, training, and program management in support of the programs and projects within CG-9.

2.0 SPECIFIC REQUIREMENTS/TASKS

2.1 TASK ONE. PERFORMANCE MEASURES SUPPORT

The Contractor shall support the USCG during the review and ongoing implementation of existing and new automated performance measures that pertain to various projects and programs within the Acquisition Directorate in support of the Strategic Plan and Annual Action Plan.

1. The Contractor shall develop, review, and modify all existing automated performance measures developed from current data marts to ensure they are running correctly and include the most recent fiscal year data.

2. The Contractor shall verify that these measures continue to run with minimal interruption of the current financial data mart from the Coast Guard Enterprise Data Warehouse.

3. The Contractor shall create new performance measures, such as dashboards, reports and data warehouses in SAS Visual Analytics (Viya), that support CG-9 projects and programs within the Acquisitions Directorate as required.

4. The Contractor shall integrate data from the financial management application into data sets useable in the BI system to include integration with actual accounting data from the data mart by various financial variables such as object class, appropriation, transaction date, etc.

5. The Contractor shall review and develop any potential new data or data sources and integrate it with currently available data. This includes testing, validating and developing the business logic for any new data sources, datamarts or reports required.

6. The Contractor shall review industry best practices, make recommendations, and develop new measures based on currently available data.

7. The Contractor shall review the current FMPDR dashboards, reports and portal pages, make recommendations, and create additional pages and portlet types for use by FMPDR offices.

8. The Contractor shall provide support and update data via coding in FMPDR in support of USCG Treasury reporting and audit compliance.

2.2 TASK TWO. REPORTS AND DOCUMENTATION

1. The Contractor shall provide updated documentation for each process, process modified, or developed in support of Section 2.1.

2. The Contractor shall update all information technology documentation to account for the systems latest Security Authorization and process changes that occur during the period of performance.

3. The Contractor shall update or assist in the creation of any new documentation requirements that pertain to the system.

2.3 TASK THREE. AD-HOC TRAINING

The Contractor shall provide ad-hoc training, as needed, for any measures or reports developed in support of Section 2.1.

LAST UPDATED: 02/23/2023 PAGE 3/12

2.4 TASK FOUR. PROGRAM MANAGEMENT

The Contractor shall monitor the performance of all work executed under this SOW and ensure all work completed on the system is tested on the development servers and coordinated for deployment on the production system with the FMPDR Project Manager and System Administrator. The Contractor shall hold peer reviews of all processes developed to support data sets in FMPDR to ensure the code is efficient and sustainable and that it does not duplicate or override any other code or processes in existence within the system.

2.5 TASK FIVE. STATUS REPORTS

The Contractor shall provide a monthly status report to the Contracting Officer’s Representative (COR) and Contracting Officer (KO) via electronic mail. This report shall include a summary of all Contractor work performed under this SOW, an assessment of technical progress, schedule status, and any Contractor concerns or recommendations for the previous month.

2.6 TASK SIX. STATUS MEETINGS

The Contractor shall be responsible for keeping the COR informed about Contractor progress under this SOW, and ensure Contractor activities are aligned with USCG requirements. The Contractor shall be available for a meeting within 24 hours of request by the COR.

3.0 CONTRACTOR PERSONNEL

3.1 QUALIFIED PERSONNEL

The Contractor must provide qualified personnel to perform all requirements specified in this SOW. The Contractor personnel shall have at a minimum eight years of experience using SAS and a minimum of five years expertise in the following: SAS BI version 9.4, SAS Portal Version 4.4; SAS Web Report Studio Version 4.4; Base SAS Version 9.4; Information Map Studio Version 4.4; SAS Financial Management Studio Version 5.5 and SAS Management Console Version 9.4. The Contractor shall have at a minimum one year of experience using SAS Visual Analytics (Viya). The Contractor shall have experience in extracting data from SAS Financial Management version 5.5 to include extraction of data from supplemental schedules and shall have experience in configuring data for use in automatic metric loading using SAS Strategy Management 5.6. The Contractor Personnel shall have experience in moving data between versions of SAS software. In addition, the Contractor Personnel must have experience in creating, developing, and maintaining large-scale data warehouses, and programming via SAS Studio. The Contractor Personnel shall have experience in ORACLE database management and code.

3.2 CONTINUITY OF SUPPORT

The Contractor must ensure that the contractually required level of support for this requirement is maintained at all times. The Contractor must ensure that all contract support personnel are present for all hours of the workday. If for any reason the Contractor staffing levels are not maintained due to vacation, leave, appointments, etc., and replacement personnel will not be

LAST UPDATED: 02/23/2023 PAGE 4/12

provided, the Contractor must provide e-mail notification to the COR prior to employee’s absence. Otherwise, the Contractor must provide a fully qualified replacement.

3.3 KEY PERSONNEL

All personnel supporting the requirements under this SOW are considered Key personnel.

Before replacing any individual designated as Key by the Government, the Contractor must notify the Contracting Officer no less than 15 business days in advance, submit written justification for replacement, and provide the name and qualifications of any proposed substitute(s). All proposed substitutes must possess qualifications equal to or superior to those of the Key person being replaced, unless otherwise approved by the Contracting Officer (KO).

The Contractor must not replace Key Contractor personnel without approval from the KO. The following Contractor personnel are designated as Key for this requirement. Note: The Government may designate additional Contractor personnel as Key at the time of award. A meeting with the COR and the Contractor is required after any change in Key Personnel.

3.5 EMPLOYEE IDENTIFICATION

3.5.1 Contractor employees visiting Government facilities must wear an identification badge that, at a minimum, displays the Contractor name, the employee’s photo, name, clearance-level and badge expiration date. Visiting Contractor employees must comply with all Government escort rules and requirements. All Contractor employees must identify themselves as Contractors when their status is not readily apparent and display all identification and visitor badges in plain view above the waist at all times.

3.5.2 Contractor employees working on-site at Government facilities must wear a Government issued identification badge. All Contractor employees must identify themselves as Contractors when their status is not readily apparent (in meetings, when answering Government telephones, in e-mail messages, etc.) and display the Government issued badge in plain view above the waist at all times.

3.6 EMPLOYEE CONDUCT

Contractor employees must comply with all applicable Government regulations, policies and procedures (e.g., fire, safety, sanitation, environmental protection, security, “off limits” areas, wearing of parts of DHS uniforms, and possession of weapons) when visiting or working at Government facilities. The Contractor must ensure Contractor employees present a professional appearance at all times and that their conduct must not reflect discredit on the United States or the Department of Homeland Security. The Project Manager must ensure Contractor employees understand and abide by Department of Homeland Security established rules, regulations and policies concerning safety and security.

3.7 REMOVING EMPLOYEES FOR MISCONDUCT OR SECURITY REASONS

The Government may, at its sole discretion (via the KO), direct the Contractor to remove any Contractor employee from DHS facilities for misconduct or security reasons. Removal does not relieve the Contractor of the responsibility to continue providing the services required under the contract. The KO will provide the Contractor with a written explanation to support any request to remove an employee.

LAST UPDATED: 02/23/2023 PAGE 5/12

4.0 OTHER APPLICABLE CONDITIONS

4.1 SECURITY

The requirements office anticipates the following:

Check Applicable

Box

Tier Investigation

Risk Form

1 Low Risk, Non-Sensitive, Physical/Logical Access (HSPD-12 Credentialing)

SF85

X 2 Moderate Risk, Public Trust SF85P

3 Non-Critical Sensitive, L, Confidential and Secret Information

SF86

4 High Risk, Public Trust SF85P

5 Q, Top Secret, Compartmented Information, Critical Sensitive, Special

Sensitive

SF86

Contractor access to classified information is not currently required under this SOW. However, the Government at a later date may require all Contractor personnel to have Secret clearances.

Accordingly, all Contractor employees provided for this requirement must be eligible for a Secret Clearance. The details will be provided in a future Department of Defense Form 254 if this policy goes into effect.

4.1.1 Contractor access to unclassified, but Security Sensitive Information may be required under this SOW. Contractor employees shall safeguard this information against unauthorized disclosure or dissemination.

4.1.2 Contractor employees that require access to classified information must have proper security clearances in place at the time of award.

4.1.3 All hardware, software, and services provided must be compliant in accordance with 140- 01 Information Technology Systems Security and the DHS Sensitive Systems Handbooks 4300A or 4300B for Classified Systems.

4.1.4 Access to Unclassified Facilities, Information Technology Resources, and Sensitive Information The assurance of the security of unclassified facilities, Information Technology (IT) resources, and sensitive information during the acquisition process and contract performance are essential to the DHS mission. DHS Management Directive (MD)

11042.1 Safeguarding Sensitive But Unclassified (For Official Use Only) Information, describes how Contractors must handle sensitive but unclassified information. DHS MD 140.01 Information Technology Systems Security and the DHS Sensitive Systems Handbook prescribe policies and procedures on security for IT resources. Contractors shall comply with these policies and procedures, any replacement publications, or any other current or future DHS policies and procedures covering Contractors specifically for all Task Orders that require access to DHS facilities, IT resources or sensitive information. Contractors shall not use or redistribute

LAST UPDATED: 02/23/2023 PAGE 6/12

any DHS information processed, stored, or transmitted by the Contractor except as specified in this SOW.

4.1.5 Security Review The Government may elect to conduct periodic reviews to ensure that the security requirements contained in this SOW are being implemented and enforced. The Contractor shall afford DHS, including the organization of the DHS Office of the Chief Information Officer, the Office of the Inspector General, authorized COR, and other government oversight organizations, access to the Contractor’s facilities, installations, operations, documentation, databases and personnel used in the performance of this SOW. The Contractor will contact the DHS Chief Information Security Officer to coordinate and participate in the review and inspection activity of government oversight organizations external to the DHS.

Access shall be provided to the extent necessary for the government to carry out a program of inspection, investigation, and audit to safeguard against threats and hazards to the integrity, availability and confidentiality of DHS data or the function of computer systems operated on behalf of DHS, and to preserve evidence of computer crime.

4.1.6 Interconnection Security Agreements Interconnections between DHS and non-DHS IT systems shall be established only through controlled interfaces and via approved service providers. The controlled interfaces shall be accredited at the highest security level of information on the network. Connections with other Federal agencies shall be documented based on interagency agreements; Memoranda of Understanding, service level agreements or interconnect service agreements. COMDTINST 5500.13 requires an ISA for all interconnections. All hardware and software interfaces shall meet FIPS 140-2 and FIPS 197 Advanced Encryption Standard (AES) 256 encryption compliance. All hardware and software shall be Federal Desktop Core Configuration (FDCC) compatible.

4.1.7 Security Certification/Accreditation: Information Assurance (IA) professionals in significant information security roles are required by COMDTINST 5200.3 to have a professional certification. USCG shall provide personnel with the appropriate clearance levels to support the security certification/accreditation processes under this Agreement in accordance with DHS MD 4300A, DHS Sensitive Systems Policy and Handbook. During all SDLC phases of USCG systems, USCG personnel shall develop documentation and provide any required information for all levels of classification in support of the certification/accreditation process. In addition, all security certification/accreditation will be performed using the DHS certification/accreditation process, methodology and tools.

4.1.8 DHS Sensitive Systems Policy Directive 4300 A, Section 4.1.4 requires the "Separation of duties to prevent a single individual from being able to disrupt or corrupt a critical security process." The Policy requires the following: "Components shall divide and separate duties and responsibilities of critical IT system functions among different individuals to minimize the possibility that any one individual would have the necessary authority or system access to be able to engage in fraudulent or criminal activity." Security testing is but one critical systems function that needs to be performed by a provider (either Government or Contractor) other than the system designer/developer/operator.

This requirement is based, in part, on NIST 800-53 Rev 3, Security Control CA-2 Security Assessments - enhancement 1 which requires "The organization employs an independent assessor or assessment team to conduct an assessment of the security controls in the

LAST UPDATED: 02/23/2023 PAGE 7/12

information system." Consequently, the vendor that provides C&A services may not perform the security controls testing.

4.2 FACILITY AND COMPUTER ACCESS

The following applies when the Contractor(s) are required to access a Coast Guard, Department of Defense (DoD), or other federally-controlled computer information system(s), or needs public key infrastructure (PKI) authentication to perform their contractual duties, or requires physical access to multiple Coast Guard facilities on a recurring basis.

Trusted Associate Sponsorship System (TASS)

(a) "Contractor employee" means an employee of a firm, or an individual, under contract or subcontract to the Coast Guard to provide services who also requires one or more of the following:

• Physical access to multiple Coast Guard facilities or multiple federally controlled facilities on behalf of the Coast Guard on a recurring basis (a minimum of two (2) times per week and/or eight (8) times per month) for a period of six (6) months or more.

• Remote access, via logon, to Coast Guard network using Coast Guard-approved remote access procedures.

• Both physical access to Coast Guard facility and logical access, via logon, to Coast Guard networks on-site or remotely. Access to the Coast Guard network must require the use of a computer with Government-controlled configuration or use of Coast Guard-approved remote access procedure in accordance with the Defense Information Systems Agency (DISA) Security Technical Implementation Guide.

(b) Homeland Security Presidential Directive (HSPD)-12 mandates a Federal standard for secure and reliable forms of identification for Federal employees and contractor employees. The Common Access Card (CAC) is a personal identification card for the Department of Defense/Uniformed Services and complies with HSPD-12. The Coast Guard has instituted the CAC as its HSPD-12 compliant personal identification card for contractor and subcontractor employees who are required to access a Coast Guard, Department of Defense (DOD), or other federally-controlled computer information system and/or facility, or need public key infrastructure (PKI) authentication to perform their contractual duties. The Trusted Associate Sponsorship System (TASS) is the automated application process for obtaining a CAC.

(c) Contractor and subcontractor employees working pursuant to this contract who are required to access a Coast Guard, DOD, or other federally-controlled computer information system and/or facility, or need PKI authentication to perform their contractual duties must use TASS to obtain a CAC.

(d) The Contracting Officer Representative (COR) or Assisting Contracting Officer Representative (ACOR) is the TASS Trusted Agent (TA) and initiates contractor accounts in the TASS, approving, returning, or rejecting CAC applications (as applicable); re-verifying assigned contractors every six months; revoking contractor and employee eligibility for a CAC.

(e) The TA ensures that contractor personnel satisfy the security requirements for CAC issuance prior to creating the CAC application in TASS. Current investigative requirements must https://www.dhs.gov/homeland-security-presidential-directive-12

LAST UPDATED: 02/23/2023 PAGE 8/12

be verified according to Commandant Instruction COMDTINST 5500.18, Coast Guard Trusted Associate Sponsorship System. The initial CAC issuance requires a favorably adjudicated Tier 1 investigation (equivalent or higher) or a Tier 1 background investigation (BI) (equivalent or higher) package that has been successfully scheduled with the investigative service provider (ISP) and a FBI fingerprint check with favorable results. The TA and Sponsor or other appropriate Federal Government representative must coordinate with the unit BI Verifier (Command Security Officer/Trusted Agent Security Manager) or the U.S. Coast Guard Security (SECCEN) to confirm the appropriate investigation has been favorably adjudicated or scheduled at the ISP with favorable FBI fingerprint results.

(f) The COR or KO provides such forms to, or requests such information from, contractor employees that may be necessary for obtaining a CAC via the TASS. The Contractor submits completed forms and information as directed by the COR or KO. Contractors are responsible for the accuracy and completeness of the information submitted and for any liability resulting from the Government's reliance on inaccurate or incomplete information.

(g) Contractor employees who are declined via the TASS are ineligible to perform work under this contract.

(h) When an employee with a CAC is no longer performing work under this contract, the employee must return the CAC to the COR/TA or KO on the same day the employee stops working.

(i) The contractor must insert this clause in all subcontracts when a subcontractor's employee is required to access a Coast Guard, DoD, or other federally-controlled computer information system and/or facility, or need PKI authentication to perform contractual duties.

(End of Clause)

4.3 PERIOD OF PERFORMANCE

The period of performance for this contract is a six-month base period with four one-year option periods as follows:

Base Period September 20, 2023 through March 19, 2024 Option Period One March 20, 2024 through March 19, 2025 Option Period Two March 20, 2025 through March 19, 2026 Option Period Three March 20, 2026 through March 19, 2027 Option Period Four March 20, 2027 through March 19, 2028

4.4 PLACE OF PERFORMANCE

The primary place of performance is the U.S. Coast Guard Headquarters Building at 2703 Martin Luther King Jr Ave, SE, Washington, DC 20593.

4.5 OFF-SITE CAPABILITY

Contractors may be allowed to complete all or part of select functions off-site. To request, the Contractor must submit a written request describing the function(s) to be completed off-site, LAST UPDATED: 02/23/2023 PAGE 9/12 validating that schedule, minimum on-site support fulfillment, and USCG off-site capability and security requirements are properly addressed. The COR will approve or deny all off-site capability requests.

4.6 HOURS OF OPERATION

Contractor employees must generally perform all work between the hours of 0800 and 1600 EST, Monday through Friday (except Federal holidays). However, there may be occasions when Contractor employees must be required to work other than normal business hours, including weekends and holidays, to fulfill requirements under this SOW.

4.7 TRAVEL

No Contractor travel is anticipated under this SOW in support of the requirements.

4.8 POST AWARD CONFERENCE

The Contractor must attend a Post Award Conference with the KO and the COR no later than five (5) business days after the date of award. The purpose of the Post Award Conference, which will be chaired by the KO, is to discuss technical and contracting objectives of this contract. The Post Award Conference will be held at the Government’s facility, located at 2703 Martin Luther King Jr Ave, SE, Washington, DC 20593, or via teleconference.

4.9 PROGRESS REPORTS

The Contractor must provide a monthly progress report to the KO and COR via electronic mail.

This report must include a summary of all Contractor work performed, including a breakdown of labor hours by labor category, all direct costs by line item, an assessment of technical progress, schedule status, any travel conducted and any Contractor concerns or recommendations for the previous reporting period.

4.10 PROGRESS MEETINGS

The Contractor shall be responsible for keeping the COR informed of Contractor progress under this SOW, and ensure Contractor activities are aligned with USCG requirements. The Contractor shall be available for a meeting within 24 hours of request by the COR to discuss progress, exchange information, and resolve emergent technical problems and issues. These meetings must take place either at the Government’s facility, or via teleconference (i.e., Microsoft Teams).

4.11 GENERAL REPORT REQUIREMENTS

The Contractor must provide all written reports in electronic format with read/write capability using applications that are compatible with DHS workstations (Microsoft Office Applications) within 48 hours of request by the COR.

4.12 INTELLECTUAL PROPERTY

LAST UPDATED: 02/23/2023 PAGE 10/12

All Contractor developed processes and procedures and other forms of intellectual property first developed under this SOW, shall be considered Government property, unless specifically stated. The Contractor shall provide—upon five (5) business days’ notice—electronic copies of all materials developed in this SOW in a format with read and write capability using applications that are compatible with USCG work stations. Additional intellectual property requirements may be specified under this SOW.

4.13 PROTECTION OF INFORMATION

Contractor access to proprietary information shall be required under this SOW. Contractor employees shall safeguard this information against unauthorized disclosure or dissemination in accordance with DHS MD 11042.1, Safeguarding Sensitive but Unclassified (SBU) Information.

SBU includes information categorized by DHS or other government agencies as: For Official Use Only (FOUO); Official Use Only (OUO); Sensitive Homeland Security Information (SHSI);

Limited Official Use (LOU); Law Enforcement Sensitive (LES); Safeguarding Information (SGI);

Unclassified Controlled Nuclear Information (UCNI); and any other identifier used by other government agencies to categorize information as sensitive but unclassified. The Contractor shall ensure that all Contractor personnel having access to business or procurement sensitive information sign a Non-Disclosure Agreement (NDA) (DHS Form 11000-6).

4.13.1 The Contractor shall continue to ensure employees safeguard this information when the new Controlled Unclassified Information (CUI) framework replaces the sensitive but unclassified (SBU) categorization.

4.13.2 Contractor personnel will have access to CGOne/CG Portal, where For Official Use Only (FOUO) information may be accessible. Access to PersonalIy Identifiable Information (PII) is not required. In accordance with DHS MD 11042.1, Safeguarding Sensitive but Unclassified (FOUO) information, all Contractor personnel with access to sensitive information shall execute DHS Form 11000-6, Department of Homeland Security Non-Disclosure Agreement (NDA), as a condition of access to such information. Further, Contractor personnel shall be personally liable and responsible for adhering to DHS Class Deviation 15-01 for proper handling and safeguarding of the security of all such USCG information. The following clauses apply:

• Safeguarding of Sensitive Information (MAR 2015)

• HSAR Clause 3052.204-71, Contractor Employee Access (SEP 2012)

• Information Technology Security and Privacy Training (MAR 2015)

4.14 SECTION 508 COMPLIANCE

Based on the results of the Department of Homeland Security (DHS) Accessibility Requirements Tool (DART) 2.1., Section 508 does not apply to the deliverables listed.

4.15 DHS ENTERPRISE ARCHITECTURE COMPLIANCE

All solutions and services shall meet DHS Enterprise Architecture policies, standards, and procedures. Specifically, the contractor shall comply with the following Homeland Security (HLS) Enterprise Architecture (EA) requirements:

• All developed solutions and requirements shall be compliant with the HLS EA.

• All IT hardware and software shall be compliant with the HLS EA Technical Reference

Model (TRM) Standards and Products Profile.

LAST UPDATED: 02/23/2023 PAGE 11/12

• Description information for all data assets, information exchanges and data standards, whether adopted or developed, shall be submitted to the Enterprise Data Management Office (EDMO) for review, approval and insertion into the DHS Data Reference Model and Enterprise Architecture Information Repository.

• Development of data assets, information exchanges and data standards will comply with the DHS Data Management Policy MD 103-01 and all data-related artifacts will be developed and validated according to DHS data management architectural guidelines.

• Applicability of Internet Protocol Version 6 (IPv6) to DHS-related components (networks, infrastructure, and applications) specific to individual acquisitions shall be in accordance with the DHS Enterprise Architecture (per OMB Memorandum M-05-22, August 2, 2005) regardless of whether the acquisition is for modification, upgrade, or replacement. All EA-related component acquisitions shall be IPv6 compliant as defined in the U.S.

Government Version 6 (USGv6) Profile National Institute of Standards and Technology (NIST) Special Publication 500-267) and the corresponding declarations of conformance defined in the USGv6 Test Program.

5.0 GOVERNMENT FURNISHED RESOURCES

The Government will provide access to the SAS Visual Analytics (VIiya) system and all its components listed in Section 3.1. Additionally, the government will provide software and permissions to work remotely for this SOW in accordance with Section 4.5. The government will also provide a workspace with a computer and permissions for this SOW.

The Contractor must use Government furnished information, data and documents only for the performance of work under this contract, and must be responsible for returning all Government furnished information, data and documents to the Government at the end of the performance period. The Contractor must not release Government furnished information, data and documents to outside parties without the prior and explicit consent of the KO.

6.0 CONTRACTOR FURNISHED PROPERTY

The Contractor must furnish all facilities, materials, equipment and services necessary to fulfill the requirements of this contract, except for the Government Furnished Resources specified in this SOW.

7.0 GOVERNMENT ACCEPTANCE PERIOD

The COR will review deliverables prior to acceptance and provide the contractor with an e-mail that provides documented reasons for non-acceptance. If the deliverable is acceptable, the COR will send an e-mail to the Contractor notifying it that the deliverable has been accepted.

7.1 The COR will have the right to reject or require correction of any deficiencies found in the deliverables that are contrary to the information contained in the Contractor’s accepted proposal. In the event of a rejected deliverable, the Contractor will be notified in writing by the COR of the specific reasons for rejection. The Contractor may have an opportunity to correct the rejected deliverable and return it per delivery instructions.

8.0 DELIVERABLES

LAST UPDATED: 02/23/2023 PAGE 12/12

The Contractor must consider items in BOLD as having mandatory due dates. Items in italics are deliverables or events that must be reviewed and/or approved by the COR prior to proceeding to next deliverable or event in this SOW.

ITEM

SOW

REFERENCE

DELIVERABLE / EVENT DUE BY

QUANTITY

1 4.8 Post-Award Conference Five (5) business days after purchase order award

2 2.2 Create and Update

Documentation As directed by the

COR

For each process, modified or developed process in support of all sections under

Section 2.0

3 2.2 System Documentation As directed by the

COR

For each process, modified or developed process in support of all sections under

Section 2.0

4 2.3 Ad-hoc Trainings As directed by the

COR

When new measures and/or reports are developed/updated

5 2.5 Progress Reports Monthly

6 per month during base year, and 12 per purchase order period for each OY