SOW - FY23 SAS AF-SCL Modernization - Final.pdf

FY 2024 NASS SAS to CIPSEA Cloud Page 1 of 10

US Department of Agriculture (USDA)

Statement of Work

FY 2024 SAS to CIPSEA Cloud

FY 2024 NASS SAS to CIPSEA Cloud Page 2 of 10

Contents Project General Information

1.0 Scope of Work

2.0 Background

Contract Requirements

3.0 Technical Requirements / Tasks

Task 1 - Migration Approach Task 2 - Documentation Review Task 3 - Code and Catalog Review Task 4 - Recorded Interviews Task 5 – Data & Environment Setup Task 6 - Development Iterations

4.0 Place of Performance and Government Furnished Equipment

5.0 Deliverables / Schedule

6.0 Period of Performance

7.0 Contractor’s Key Personnel

8.0 Security Requirements

9.0 Confidentiality Certification and Non-Disclosure Agreement

10.0 Personal Identity Verification of Contractor Personnel

11.0 Section 508 – Accessibility of Information and Communications Technology

Section 508 Compliance

FY 2024 NASS SAS to CIPSEA Cloud Page 3 of 10

Project

FY 2024 SAS to CIPSEA Cloud

General Information

1.0 Scope of Work

The United States Department of Agriculture (USDA) National Agricultural Statistics Service (NASS) is seeking support services for the development, enhancements, and maintenance for its data collection, editing and dissemination. The Contractor shall provide all necessary labor, materials, and equipment (except those provided by the Government) and services to perform the work outlined in this statement of work (SOW).

2.0 Background

NASS is one (1) of four (4) agencies that serve USDA’s Research, Education, and Economics (REE) mission area.

REE is dedicated to creating a safe, sustainable, competitive U.S. food and fiber system, as well as building strong communities, families, and youth through integrated research, analysis, and education. NASS serves the basic agricultural and rural data needs of the country by providing objective, important and accurate statistical information and services to farmers, ranchers, agribusinesses, and public officials. This data is vital to monitoring the ever-changing agricultural sector and carrying out farm policy. More information on REE and NASS can found here: https://www.ree.usda.gov/ and https://www.nass.usda.gov/, respectively. Also, the guide entitled Talking About NASS may be helpful. While NASS is headquartered in Washington, D.C., staff members are located across the contiguous United States.

NASS is one of the primary suppliers of statistics covering U.S. agriculture. NASS conducts hundreds of surveys and the Census of Agriculture, as well as prepares reports covering virtually every facet of U.S. agriculture including production and supplies of food and fiber, prices paid and received by farmers, farm labor and wages. In addition, NASS' various Field Offices (FO's) publish data about many of the same topics for local audiences. NASS publications cover a wide range of subjects, from census reports, traditional crops, such as corn and wheat, to specialties, such as mushrooms and flowers; from calves born, to hogs slaughtered; from agricultural prices to land in farms.

Contract Requirements

3.0 Technical Requirements / Tasks

This SOW focuses on the following tasks:

• Task 1 - Migration Approach

• Task 2 - Documentation Review

• Task 3 - Code and Catalog Review

• Task 4 - Recorded Interviews

• Task 5 - Data & Environment Setup

• Task 6 - Development Iterations

The contractor shall make maximum usage of existing NASS hardware and software.

Task 1 - Migration Approach

The Contractor shall:

• Create a migration approach from SAS AF /SCL that can be performed offsite with the following benefits:

https://www.ree.usda.gov/ https://www.nass.usda.gov/ https://www.nass.usda.gov/About_NASS/pdf/Talking-About-NASS-Guide.pdf

FY 2024 NASS SAS to CIPSEA Cloud Page 4 of 10 o Zero risk to existing applications or SAS environments o Rapid development unencumbered by access restrictions.

o Delivery of a self-contained test instance (with associated test data)

Task 2 - Documentation Review

The Contractor shall:

• Review any available documentation provided by NASS, so the project team can review and make use of any insights gained. Examples such documentation might include:

o User Manual(s) o Developer Guide o Data Dictionary o Data Flow Diagrams o Technical Architecture Diagrams o Platform Handbook o Explanatory emails

• Create a report on the current and target technology stacks, for circulation amongst the enterprise architects.

Task 3 - Code and Catalog Review

• Review source code for AF/SCL applications is stored on network drives.

• Look for ‘migration challenges’ such as the use of XCMD, embedded passwords, DDE, or other non-SAS routines/libraries.

Task 4 - Recorded Interviews

The Contractor shall:

• Conduct interviews with end users and domain specialists.

• Provide a series of requirements (user stories) for project planning and delivery.

• Provide an explicit list of functionalities that does not need to be migrated.

Task 5 – Data & Environment Setup

• deploy a unique SAS environment for each development iteration / feature / test cycle.

• Work with the Data Owner(s) to enable the release of appropriate/useful test data and associated output results (for validating the business logic in the final solution)

• Configuration of the “build environment” job

• Auto creation of the folder structure, datasets, binary files and user accounts (with associated permissions)

• The contractor shall Leverage version controlling for all code via Github

Task 6 - Development Iterations

• Develop code based on user stories, as identified in the documentation review or user interviews.

• Replace AF Frames with a modern User Interface using open-source JavaScript components.

FY 2024 NASS SAS to CIPSEA Cloud Page 5 of 10

• Produce Code documentation.

• Ensure the DSE, Census summaries and calibration is running in the cloud

• Mainframe can GAT summaries are in the cloud API interaction to "call" stored procedures (SAS jobs) are in the cloud.

• Convert the existing system, which is stateful and SCL based, to one based on pure SAS code in which every data request is made in a new / clean SAS session.

• Identify the data and logic that flows into the frontend.

• Make this available in a web service (macros, program logic etc) .

• Create the tests (for each macro and web service) .

• Write the Code Documentation (in the header of each .sas file).

• Update the Developer Documentation where appropriate.

• Re-architect code in some cases where the code contains AF or SCL or INCLUDE statements or

SAS/SHARE sections or XCMD etc.

4.0 Place of Performance and Government Furnished Equipment

NASS Headquarters is location at the USDA South Building at 1400 Independence Avenue SW Washington, D.C. 20250. In light of ongoing public health matters, the work identified herein will be remote in nature until further notice.

The contractor will be given access to systems documentation and code, as needed, for systems (applications and databases) in this SOW. NASS. The Contractor will be given remote access to the NASS network.

Government furnished equipment can be obtained Monday through Friday between the hours of 6:00 am to 9:00 pm ET at the USDA South Building, unless otherwise agreed up by NASS project manager.

5.0 Deliverables / Schedule

The contractor shall submit all required report(s)/deliverables, to the COR via electronic mail, in accordance with the schedule outlined below. All reports shall reference and cite the contract/order number. The Government will apply the following general inspection standards to the reporting and delivery requirements:

1. Meeting designated schedule dates.

2. Submission of all deliverables as specified.

The Government will inspect the work for both quality and timeliness and notify the contractor regarding problems and any corrections needed within 5 business days after receipt of deliverables. The contractor shall be notified in writing of the problems with the work and the contractor shall provide an acceptable correction, correction plan or recommendation within 5 business days after notification.

The contractor shall submit all deliverables via email in accordance with chart below.

Key Deliverables Task No.

Deliverable Objective Due

1 Project Kick-Off Meeting

• A meeting between the Contractor, and USDA NASS Contracting Officer’s Representative

• USDA NASS will utilize the Project Kick-Off Checklist to drive the meeting and deliverable outcome

NLT 10 business days after contract award

2 Sprint Backlog A list of all defined requirements broken down into Sprints based on the Product Backlog. This is reviewed and updated at the start of every Sprint cycle.

Start of each Sprint Cycle

FY 2024 NASS SAS to CIPSEA Cloud Page 6 of 10

3 Sprint Retrospective Documentation of Sprint results and feedback based on the Sprint Reviews. This marks the completion of the Sprint.

End of each Sprint

4 Monthly Status Report Document summarizing services activities completed in the previous month and risk.

Third business day of the month (covering the previous calendar month)

Task Name Completion Date

MVP/POC complete

• Genesis PopDev or Sampling Module

Asses the viability and timeline to get screens converted that includes documentation and training.

• Prism o SAS AF/SCL o Macro Analysis o View\Editing o Data loading o Summary

• Gensis o Sampling Level Creation o Survey Prep o Frontend and Backend process o Data Manipulation enhancements (ex: offload work from sas files to database)

• Poultry Slaughter

• Mainframe Summaries

Provide bimonthly status updates during the POP.

Date of award for 3 months of the contract origination date

EST. 30 Sept 2024 (base year)

Migrate essential Prism and Gensis components.

• Prism o Macro Analysis o View\Editing

• Ensure screens can communicated with database and servers

• Genesis o Main Sampling

Work on Mainframe Summaries

• Solution to be flexible to connect and migrate off Aix Environment

• Less complicated CLIST that does not involve imputation

Increased ability for systems to integrate with other systems

Provide bimonthly status updates during the POP. documentation and training

30 Sept 2025 (opt 1)

Overall Standard Operations of Procedures and Data Process flow documentation to describe the systems and processes

30 September 2025

FY 2024 NASS SAS to CIPSEA Cloud Page 7 of 10

6.0 Period of Performance

The performance period from approximately July 2024 through September 2025. Provided the deliverables described in this task order are submitted to the NASS point of contact per the performance requirements, 1 option year may be pursued for this task order. The option period award will depend on the availability of funding, the need for continuing services, and contractor’s performance.

Base– Have proof of concept/minimum viable product for Genesis POP def or Sampling Frames and asses what it will take to migrate other code.

Option Year One:

• Task 1 – Migrate essential Prism and Gensis components cloud with full functionality and viability with documentation and training to NASS FTE

• Task 2 - Work on Mainframe Summaries

• Task 3 – Migrate any additional Prism and Gensis components.

• Task 4 - Mainframe summaries to the cloud with full functionality and viability with documentation and training to NASS FTE

7.0 Contractor’s Key Personnel

Key personnel must be assigned for the duration of the task order and have the experience to complete the SOW requirements. Key project personnel shall have successfully participated in the completion of similar projects.

Key personnel must not be replaced or removed without prior notification to NASS’s Project Manager and COR. A comparable replacement must be chosen and agreed to by the NASS Project Manager and COR.

Resumes must be submitted for all key personnel with the Contractor’s proposal, and for any key personnel replacements for the duration of this SOW, if applicable. NASS reserves the option to interview key personnel prior to beginning work on the SOW requirements.

All contractor and subcontractor personnel working on the requirements of this SOW shall be U.S. Citizens or a green card holder.

8.0 Security Requirements

Contractor personnel shall have a “Modified Background Investigations” for moderate risk personnel at the cost of the contractor.

Due to NASS data security and confidentiality requirements, work requiring access to sensitive data will be accomplished at 1400 Independence Ave, SW, Washington, DC, unless an agreeable alternate agreement is reached between the COR and the contractor.

As mandated by the USDA Office of the Chief Information Officer, contractors that have access to NASS computer systems or data are required to complete the annual USDA Information Security Awareness (ISA) and Rules of Behavior (ROB) Mandatory Training, in accordance with the Federal Information Security Management Act (FISMA), at the cost of the contractor.

9.0 Confidentiality Certification and Non-Disclosure Agreement

FY 2024 NASS SAS to CIPSEA Cloud Page 8 of 10

Employees and anyone with approved access to NASS computer systems, databases and/or data files are required to sign a confidentiality certificate that defines the penalties for compromising or disclosing NASS confidential data. The penalties include fines and/or imprisonment. All contract employees who have access to NASS facilities, computer systems or data must sign the confidentiality certifications. All subcontractor employees that the contractor may employ will also be required to sign the confidentiality certification.

Certain system documentation may be available for potential Contractors to review at a reading room at 1400 Independence Ave SW, Washington, DC. 20250. Contractors who review such documentation will be required to sign the Non-Disclosure Agreement.

10.0 Personal Identity Verification of Contractor Personnel.

In accordance with FAR 52.204-9 Personal Identity Verification of Contractor Personnel (JAN 2011)

(a) The Contractor shall comply with agency personal identity verification procedures identified in the contract that implement Homeland Security Presidential Directive-12 (HSPD-12), Office of Management and Budget (OMB) guidance M-05-24 and Federal Information Processing Standards Publication (FIPS PUB) Number 201.

(b) The Contractor shall account for all forms of Government-provided identification issued to the Contractor employees in connection with performance under this contract. The Contractor shall return such identification to the issuing agency at the earliest of any of the following, unless otherwise determined by the Government:

a. When no longer needed for contract performance.

b. Upon completion of the Contractor employee’s employment.

c. Upon contract completion or termination.

(c) The Contracting Officer may delay final payment under a contract if the Contractor fails to comply with these requirements.

11.0 Section 508 – Accessibility of Information and Communications Technology

This contract vehicle is subject to Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 749d) as amended by the Workforce Investment Act of 1998 (P.L. 105-220). The Revised Section 508 Standards, which consist of 508 Chapters 1 and 2 (Appendix A), along with Chapters 3 through 7 (Appendix C), contain scoping and technical requirements for information and communication technology (ICT) to ensure accessibility and usability by individuals with disabilities. Compliance with these standards is mandatory for Federal agencies subject to Section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. 794d).

Each ICT product or service furnished under this contract shall comply with the Revised Section 508 ICT Accessibility Standards at a minimum, as specified in the contract. If any furnished product or service is determined to be noncompliant, the Contracting Officer will notify the Contractor in writing. The Contractor shall, without charge to the Government, remediate or replace the noncompliant products or services within a specified timeframe as determined by the Government in writing. If such remediation or replacement is not completed within the time specified, the Government shall have the following recourses:

1) Cancellation of the contract, delivery, task order, purchase, or line item without termination liabilities;

or

2) In the case of custom ICT being developed by a contractor for the Government, the Government shall have the right to have any necessary changes made or repairs performed by itself or by another firm

FY 2024 NASS SAS to CIPSEA Cloud Page 9 of 10 for the noncompliant ICT, with the contractor liable for reimbursement to the Government for any expenses incurred thereby.

The contractor must ensure all noncompliant ICT products and services are provided pursuant to extensive market research and exhibit the highest level of compliance while satisfying the contract requirements.

For every ICT product or service accepted under this contract by the Government that does not comply with the Revised Section 508 Accessibility Standards, the contractor shall, at the discretion of the Government, remediate or upgrade the item with a compliant equivalent product or service, if commercially available and cost neutral, on either a contract specified refresh cycle for the product or service, or on a contract effective option/renewal date, whichever shall occur first.

Section 508 Compliance

Vendors, contractors, and their respective ICT products and services shall comply with the following standards, policies, and procedures. In the event of conflicts between the referenced documents and this contract vehicle, the contract vehicle shall take precedence.

1) Revised Section 508 ICT Accessibility Standards

2) Section 508 of the Rehabilitation Act as amended (29 U.S.C. 794d)

3) Federal Acquisition Regulation (FAR) Subpart 39.2

4) USDA Section 508 Departmental Regulation

Additionally, all contract deliverables are subject to these standards.

All ICT products and services, regardless of format, must conform to the applicable Section 508 standards to allow Federal employees and members of the public with disabilities equivalent access to and use of information and data provided to those without disabilities.

All contractors, sub-contractors, and consultants are responsible for preparing or posting content must comply with the applicable Section 508 accessibility standards and, where applicable, those set forth in the referenced policy or standards document. Remediation of any noncompliant ICT or materials as set forth in this contract vehicle shall be the responsibility of the contractor, sub-contractor, or consultant.

According to the Access Board’s Section 508 Scoping Requirements The following Section 508 provisions apply to the products and/or services identified in this contract vehicle:

• C202 Functional Performance Criteria: Where the requirements in Chapters 4 and 5 do not address one or more functions of telecommunications or customer premises equipment, the functions not addressed shall conform to the Functional Performance Criteria specified in Chapter 3.

• C203 Electronic Content: Electronic content that is integral to the use of telecommunications or customer premises equipment shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0.

• C204 Hardware: Where components of telecommunications equipment and customer premises equipment are hardware, and transmit information or have a user interface, those components shall conform to applicable requirements in Chapter 4.

• C205 Software: Where software is integral to the use of telecommunications functions of telecommunications equipment or customer premises equipment and has a user interface, such software shall conform to C205 and the applicable requirements in Chapter 5.

WCAG Conformance: User interface components, as well as the content of platforms and applications shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0.

https://www.access-board.gov/ict/#about-the-ict-accessibility-standards https://www.access-board.gov/law/ra.html#text-of-section-508-of-the-rehabilitation-act-of-1973-as-amended-29-usc-794d https://www.acquisition.gov/sites/default/files/current/far/html/Subpart%2039_2.html http://www.ocio.usda.gov/document/departmental-regulation-4030-001 https://www.access-board.gov/ict/#508-chapter-2-scoping-requirements https://www.access-board.gov/ict/#C202-functional-performance-criteria https://www.access-board.gov/ict/#C203-electronic-content https://www.access-board.gov/ict/#C204-hardware https://www.access-board.gov/ict/#C205-software

FY 2024 NASS SAS to CIPSEA Cloud Page 10 of 10

• C206 Support Documentation and Services: Where support documentation and services and provided for telecommunications equipment and customer premises equipment, manufacturers shall ensure that such documentation and services conform to Chapter 6 and are made available upon request at no additional charge.

In addition, vendors and contractors shall comply with the standards, policies, and procedures below for all ICT pursuant to this contract:

• For Custom ICT Development Services, the vendor or contractor shall ensure the ICT fully conforms to the applicable Revised Section 508 standards prior to delivery and before final acceptance.

• For Installation, Configuration, and Integration Services, the vendor or contractor shall not install, configure, or integrate the equipment and software in a way that reduces the level of conformance with the applicable Revised Section 508 standards.

• For Maintenance, Upgrades, and Replacements, the vendor or contractor shall ensure maintenance upgrades, substitutions, and replacements do not reduce the original level of conformance with the applicable Revised Section 508 standards at the time of the contract award.

• Service Personnel are ensured by the vendor or contractor to possess the knowledge, skills, and ability necessary to address the applicable Revised Section 508 standards and shall provide supporting documentation upon request.

• When providing Hosting Services, the vendor or contractor shall not reduce the existing level of conformance of the electronic content with the applicable Revised Section 508 standards.

• When purchasing ICT where 1) Section 508 validation is not possible prior to award, 2) the ICT will be changed after the award, or 3) ICT will be hosted in a third-party environment, the vendor or contractor shall test and validate the ICT solution for conformance to the Revised Section 508 standards, in accordance with the required testing methods as defined by the agency.

• The vendor or contractor shall document and maintain information regarding the measures taken to ensure compliance with the applicable requirements. This documentation includes but is not limited to testing records, product demonstrations, and reported defects by end users and testers.

• Prior to acceptance, the vendor or contractor shall provide an Accessibility Conformance Report (ACR) for each ICT item that is developed, updated, and/or configured for the agency, and when product substitutions are offered. The ACR should be based on the latest version of the Voluntary Product Accessibility Template (VPAT) provided by the Information Technology Industry Council (ITI). To be considered for award, an ACR must be submitted for each ICT item, and must be completed according to the instructions provided by the ITI.

Note: A supplemental ACR may be required if the agency has additional or stricter accessibility requirements than what is outlined in the VPAT.

• Prior to acceptance, the agency reserves the right to require a full working demonstration of the completed ICT item to demonstrate conformance to the agency’s accessibility requirements in addition to independent testing to validate.

• In the case of non-compliance where the vendor or contractor claims its products and/or services satisfy the applicable Revised Section 508 standards specified in the contract vehicle, the contracting officer will promptly inform the vendor or contractor in writing of the non-compliance. The vendor or contractor shall, at no cost to the agency, repair or replace the non-compliant products or services within the period specified by the contracting officer.

All Information and Communications Technology (ICT) subject to the Revised Section 508 standards will be evaluated for Section 508 conformance and usability. The test must be administered by a Federal Section 508 Testing Center. All maintenance for ICT that requires upgrades, modifications, installations, repairs, and purchases shall adhere to the Revised Section 508 standards.

https://www.access-board.gov/ict/#C206-documentation-services https://www.section508.gov/sell/vpat https://www.section508.gov/sell/vpat http://www.itic.org/policy/accessibility