Attachment J8 - Task Order SOW (Example).pdf

Version 2020.1.0 (01/2020) 1

Statement of Work (SOW) (Example)

**This document is meant to serve as a template for offerors. A SOW will be what you provide as your Task Order Technical Approach. Not all of the below listed categories are required and should be changed according to your solution framework. Important and suggested sections are marked as such. Do not copy or use any project information from this example.

C.1. Project Title

Software Development for Chronicling America 2021-2022

C.2. Background

Chronicling America (ChronAm) is the web site of the National Digital Newspaper Program (NDNP), a partnership between the National Endowment for the Humanities (NEH) and the Library of Congress (LC), is a long-term effort to develop an Internet-based, searchable database of U.S.

newspapers with descriptive information and select digitization of historic pages. The program’s current web site (http://chroniclingamerica.loc.gov) is being migrated to the Library’s main loc.gov application (https://www.loc.gov/collections/chronicling-america/about-this-collection/) as part of a program to consolidate legacy systems and modernize the Library’s overall web presence. Once the current ChronAm functionality and content are migrated, the loc.gov team will work with content owners to add additional content and functionality related to Chronicling America and Newspapers content.

C.3. Scope

The Contractor will support the development of features to support Chronicling America on loc.gov and the management of Chronicling America content as a part of an existing team using the SCRUM Agile Process in a series of 2 week sprints. The team will use standard Agile practices, including frequent stand up meetings, user story based development, continuous integration, and automated testing. The team will work on both the public-facing and administrative systems for loc.gov. The members of the agile team will participate in User Story creations sessions, stand ups, backlog grooming and sprint retrospective meetings.

Specific areas of work will include:

- Complete migration of Chronicling America legacy web site to loc.gov Digital Collections platform

- Sunset legacy Chronicling America site

- Complete development of visual map interface to search results for use with full text, digitized titles, and Newspaper Directory titles

- Plan and implement OCR re-processing for approximately 10 million pages digitized prior to 2012, and re-ingest into Chronicling America

- Develop visual timeline search results interface for use with full text, digitized titles and

Directory titles http://chroniclingamerica.loc.gov/ https://www.loc.gov/collections/chronicling-america/about-this-collection/

Version 2020.1.0 (01/2020) 2

- Develop integration of “non-NDNP” digitized title information into Newspaper Directory

IMPORTANT SECTION: The scope section defines and draws the parameters of the solution you are providing. It should be broad.

C.4. Requirements

The Contractor must support the development of Chronicling America functions on loc.gov as a part of a team using the SCRUM Agile Process in a series of 2 week sprints. Sprints shall be completed by a team of contractor support personnel that are working with the designated LOC Contracting Officer’s Representative (COR) and Program Management personnel that are assigned to this project. The contractor personnel will collaborate with the existing Chronicling America project team that includes software developers, a project manager, a product owner, a visual designer, and access to testing/QA support. A Sprint Planning session that includes contractor personnel shall be completed at the initiation of each sprint, determining the exact stories that the team must work on during the sprint.

The table below defines a proposed plan for a series of sprints (to be refined in collaboration with the project team following the Agile process):

Sprint Focus Specific Story Focus 1 • Search Results -

Geographic Map Interface

• Migration Support

• Requirements gathering

• Initial technical design for providing access to Chronicling

America search results via a US Map interface

• Migration Support

2 • Search Results - Geographic Map Interface

• Migration Support

• Finalize requirements and specs

• Create development backlog

• Migration Support

3 • Search Results - Geographic Map Interface

• Migration Support

• Development– back end development

• Migration Support

4 • Search Results - Geographic Map Interface

• Migration Support

• Development– back end development – full text

• Migration Support

5 • Search Results - Geographic Map Interface

• Development– back end development – Newspaper titles and Directory Titles

• Migration Support

Version 2020.1.0 (01/2020) 3

Sprint Focus Specific Story Focus

• Migration

Support 6 • Search Results -

Geographic Map Interface

• Migration Support

• Development – integration development

• Migration Support

7 • Search Results - Geographic Map Interface

• Migration Support

• Development – front end development – search results

• Migration Support

8 • Search Results - Geographic Map Interface

• Migration Support

• Development – front end development – search results

• Migration Support

9 • Search Results - Geographic Map Interface

• Migration Support

• Complete development – final integration and testing

• Accessibility testing and fixes

• Migration Support

10 • Search Results – Visual Timeline Interface

• Legacy Site Retirement Support

• Requirements gathering

• Initial technical design for providing access to Chronicling

America search results via a Timeline interface

• Migration Support

11 • Search Results – Visual Timeline Interface

• Legacy Site Retirement Support

• Finalize requirements and specs

• Create development backlog

• Legacy Site Retirement Support

12 • Search Results – Visual Timeline Interface

• Legacy Site Retirement Support

• Development– back end development

• Legacy Site Retirement Support

13 • Search Results – Visual Timeline Interface

• Legacy Site Retirement Support

• Development– back end development – Metadata and full text

• Legacy Site Retirement Support

Version 2020.1.0 (01/2020) 4

14 • Search Results –

Visual Timeline Interface

• Legacy Site Retirement Support

• Development– back end development – Newspaper titles and Directory Titles

• Legacy Site Retirement Support

15 • Search Results – Visual Timeline Interface

• Legacy Site Retirement Support

• Development – integration development

• Legacy Site Retirement Support

16 • Search Results – Visual Timeline Interface

• Legacy Site Retirement Support

• Development – front end development – search results

• Legacy Site Retirement Support

17 • Search Results – Visual Timeline Interface

• Legacy Site Retirement Support

• Development – front end development – search results

• Legacy Site Retirement Support

18 • Search Results – Visual Timeline Interface

• Legacy Site Retirement Support

• Complete development – final integration and testing

• Accessibility testing and fixes

• Legacy Site Retirement Support

19 • Integration of re-Processed

OCR

• Create backlog and test cases

• Review technical plan with team

20 • Integration of re-Processed

OCR

• Initial ETL and review/testing

• Determine any corrections needed and ticket/fix

21 • Non-NDNP Title Integration into Newspaper Directory

• Integration of re-Processed

OCR

• Create backlog and test cases

• Review technical plan with team

• Support ETL of re-Processed OCR

22 • Non-NDNP Title Integration into

• Initial ETL and review/testing

• Determine any corrections needed and ticket/fix Support

ETL of re-Processed OCR

Version 2020.1.0 (01/2020) 5

Newspaper Directory

• Integration of re-Processed

OCR

23 • Non-NDNP Title Integration into Newspaper Directory

• Integration of re-Processed

OCR

• Front End Development/Integration

• Support ETL of re-Processed OCR

24 • Non-NDNP Title Integration into Newspaper Directory

• Integration of re-Processed

OCR

• Final Fixes and Testing

• Support ETL of re-Processed OCR

25 • Non-NDNP Title Integration into Newspaper Directory

• Integration of re-Processed

OCR

• Support ETL of Non-NDNP Titles

• Support ETL of re-Processed OCR

26 Project Closeout • Project closeout activities

IMPORTANT SECTION: The Requirements Section is highly important but also highly variable. This section will have detail at a more granular level and will list the steps you will take to accomplish the stated objectives in the Task Order SOO. It may include a notional sprint plan if you are using a scrum- -or adjacent--framework. You may include a sprint plan as a separate attachment, if preferred.

C.5. Technologies and Tools

The table below summarizes the key functional areas in scope for this task order and the related technologies used by the loc.gov system.

Version 2020.1.0 (01/2020) 6

Functional Area Description Technologies

Front End/Web App

Front-end web app providing access to the public.

Provides search, browse, display of collections content, program information, and pages about the Library.

HTML/CSS

Python JavaScript

AJAX

Back End

Database and supporting management for web app MySQL MongoDB

API JSON/XML Endpoints for access to loc.gov data Python Django

JSON

ETL Components to handle transfer of data to/from numerous systems into and out of the loc.gov repository.

Solr Python Django

Search

Search engine to provide all search functions within the application.

Solr

Release Management

Suite of tools and custom components to track the lifecycle of development, testing and deployment.

Provides continuous integration and test execution.

Jenkins Git

Testing

Testing is done via a combination of automated and manual tests. Unit tests are executed by the continuous integration servers, while end to end, regression, functional testing and user acceptance testing is performed using a more manual process, supported by testing tools where applicable.

Selenium

Content Management Tools

Internal applications and supporting elements that author events, news items, biographies, etc.

Python MySQL WordPress Git loc.gov API

Infrastructure Servers and supporting devices/tools that deliver application in development, testing, staging, and production environments

VMWare Red Hat Linux Varnish Apache Amazon Web Services

Version 2020.1.0 (01/2020) 7

Functional Area Description Technologies

Front End/Web App

Front-end web app providing access to the public.

Provides search, browse, display of collections content, program information, and pages about the Library.

HTML/CSS

Python JavaScript

AJAX

C.6. Contract Performance

C.6.1. Schedule of Events/Deliverables

Paragraph Reference Description of Event/Deliverable Due Date

C.4 Completion of software development sprint for Chronicling America on loc.gov including:

• Check in of code to repository

• Completion of unit tests

• Completion of user stories or other documentation

• Completion of user story user acceptance criteria

• Completion of post-sprint review

Every 2 weeks

IMPORTANT SECTION: A deliverables table will assign tangible outcomes to your above stated efforts and provide a schedule for them. Please include a deliverables table that maps to your solution.

C.6.2. Quality Control

The Library of Congress uses a standard Quality Assurance Surveillance Plan (QASP) to make sure that systematic quality assurance methods are used in the administration of Agile Software Development Task Orders under the Agile Development and System Integration IDIQ. The intent of this plan is to ensure that the contractor performs in accordance with the performance metrics and the Government receives the quality of services called for in the contract.

The purpose of the QASP is to describe the systematic methods used to monitor performance and to identify the required documentation and the resources to be employed. The QASP provides a means for evaluating whether the contractor is meeting the established performance standards/quality levels.

The QASP defines the roles and responsibilities of all members of the OCIO acquisition team, identifies the performance objectives, defines the methodologies used to monitor and evaluate the contractor’s performance, describes quality assurance documentation requirements, and describes the analysis of quality assurance monitoring results.

Version 2020.1.0 (01/2020) 8

The QASP is intended to be a “living” document that can be reviewed as performance warrants;

revisions can be made upon contract award, if needed.

IMPORTANT SECTION: This section will match your submitted QASP.

C.7. Government Furnished Property (GFP)

The Government will provide a suitable laptop or workstation, telephone, including desk and general office supplies such as pens and paper for assigned personnel only. The contractor can provide Library-compatible workstations (or laptops) for remote work, all reference tools, training tools, and additional supplies to its personnel, as required.

Contractor personnel will have access to existing system documentation and subject matter experts, as needed; to perform successfully on tasks described this Task Order.

The government will provide appropriate development, testing, and production environments, as appropriate.

The Government will provide appropriate Contractor personnel with remote access to the development, testing and production environments in accordance with IT Security and OCIO directives and procedures.

If you expect the government to provide GFP, you must include that in your pricing workbook.

Section F – Deliveries or Performance

LC52.215-5 Place and Period of Performance

F.1. Period of Performance

Period of Performance: 52 weeks from Contract award

The contractor is responsible for determining its hours of operation in fulfilling the requirements of this contract. The Library’s standard operating hours are from 8:30 AM through 5:00 PM excluding federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. In the event the Government site is closed, the Contractor will direct its staff to take appropriate action consistent with its policies and those issued by the COR.

The Government observes the following federal holidays. When any such day falls on a Saturday, the preceding Friday is observed. When any such day falls on a Sunday, the following Monday is observed.

• New Year’s Day

• Martin Luther King, Jr.’s Birthday

Version 2020.1.0 (01/2020) 9

• Presidents’ Day

• Memorial Day

• Independence Day

• Labor Day

• Columbus Day

• Veterans’ Day

• Thanksgiving Day

• Christmas Day

There may be tasks and/or circumstances that require the Contractor to work outside of the core work hours. The need to deviate from the core work hours will be the exception rather than the rule. Any deviation from core work hours should be approved by the COR two working days prior to the requested deviation.

Please include a proposed period of performance in your Task Order SOW.

F.2. Place of Performance

The location of performance will be onsite at the Library of Congress, John Adams Building, 120 2nd Street SE, Washington, DC 20002 unless the government determines it to more advantageous and less costly for the work to be performed remotely.

Contractor travel is not currently anticipated in order to perform the tasks associated with this work or to interact with Library of Congress users and subject matter experts. If travel is determined to be required, travel must be pre-approved by the COR. All travel shall be in accordance with the Federal Travel Regulations and FAR 31.205-46. If applicable, a not-to-exceed travel amount will be identified under a separate CLIN on each Task Order.

Section G – Contract Administration

Please include the information of your point of contact here, as well as your company’s physical address.

Beyond these sections listed here, we strongly suggest you add a Key Personnel section and Management Approach section in your SOW.