Attachment J.2 Template-Statement-of-Work.docx

Template - Statement of Work

(Delete all notes before submitting the Statement of Work.)

Title: Click here to enter text.

SECTION 1 – BACKGROUND

(May insert from SOO)

SUBSECTION A – DEFINITIONS

(Note: If applicable, include a list of definitions. Otherwise, delete section and header)

SECTION 2 – PURPOSE

(May insert from SOO)

Note: Explain the purpose of the project and include:

SECTION 3 – SCOPE OF WORK

(Note: Provide an overall, non-technical description of the work to be performed. Expand on the project purpose and objectives, but do not detail all of the work required. Identify and summarize the requirements of the project, and define its limits in terms of specific objectives, time, special provisions, or limitations. This information must be consistent with the detailed requirements and tasks. Contractor responsibilities are often summarized here, as are the results or supplies expected. Government responsibilities may be considered in organizing the statement of work.)

SECTION 4 – TASKS TO BE PERFORMED

(Note: List all the tasks the vendor will perform to complete the purpose and fulfill the objectives. Each objective should be labelled as an independent task. This section should include the technical details of the work to be performed)

Attachment J.2

SECTION 5 – GOVERNMENT FURNISHED MATERIALS

(Note: No government furnished materials are expected under this requirement but if the contractor deems them necessary, list the government furnished materials and a brief description of their use(s).)

SECTION 6 – PERIOD OF PERFORMANCE

(Note: Outline the period of performance and include all option periods.)

SECTION 7 – DELIVERABLES/REPORTING SCHEDULE

(Note: See SOO for deliverables instructions. Deliverables table format may be proposed by the contractor.)

SECTION 8 – SPECIAL CONSIDERATIONS

(Include Section 8 in full text in the SOW)

CDC IT services and applications must comply with the Federal Acquisition Regulation (FAR), the Federal Information Security Management Act of 2002 (FISMA), the Office of Management Budget (OMB), and the National Institute of Standard and Technology (NIST) standards, regulations and laws. Additionally, IT services and applications must comply with HHS Acquisition Regulations (HHSAR) and any other HHS polices.

· The system shall store records in a manner compliant with both the Federal Records Act (FRA) of 1950.

· All applications must meet Section 508 Accessibility Requirements in accordance with the Rehabilitation Act of 1973 (29 U.S.C. 794d), as amended by the Workforce Investment Act of 1998, and the Architectural and Transportation Barriers Compliance Board Electronic and Information (EIT) Accessibility Provisions (36 CFR part 1194).

· During or after the life of this contract, the contractor shall not release any data, publications or materials developed under this contract without prior CDC clearance and approval. CDC retains the rights to all documents, deliverables, and data developed under this contract.

· In accordance with FAR 52.227-14 Rights in Data - General, CDC will assume “Unlimited rights” to software delivered under this order. The Government has the right to use, disclose, reproduce, prepare derivative works, distribute copies to the public, and perform publicly and display publicly, in any manner and for any purpose, and to have or permit others to do so.

· All custom developed code is developed as open source in alignment with OMB M-16-21 - Federal Source Code Policy. The contractor shall publish and maintain code in a CDC code repository and propose a method for delivering all associated technical and functional documentation and software code to CDC at the end of the Task Order.

· All work that is associated with government information and information systems must be in compliance with the Federal Information Security Management Act of 2002 as implemented by Federal Information Processing Standards Publication 200 (FIPS 200), “Minimum Security Requirements for Federal Information and Information Systems.” This standard specifies the minimum security requirements Federal agencies must meet, the appropriate security controls and assurance requirements to be selected are described in the National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53, “Recommended Security Controls for Federal Information Systems and Organizations” and associated documents. Specific impact levels required (per FIPS 200) for government information and information systems may vary and will be specified as requirements are identified.

· The Contractor shall be responsible for properly protecting all information used, gathered, or developed as a result of work under this Task Order. The Contractor shall also protect all government data, equipment, etc. by treating the information as sensitive. All information about the systems gathered or created under this task order should be considered as SBU information. It is anticipated that this information will be gathered, created and stored within the primary work location. If contractor personnel must remove any information from the primary work area they shall protect it to the same extent they would their proprietary data and/or company trade secrets. The use of any information that is subject to the Privacy Act will be utilized in full accordance with all rules of conduct as applicable to Privacy Act Information.

· Independently, and not as an agent of the Government, the Contractor shall furnish all the necessary personnel, facilities, supplies, and equipment required to conduct this project. The contractor shall also provide any required centralized administrative, clerical, technical writing and other related overhead functions. All documents and deliverables developed shall become the property of the Government.