RFP Attachment 1 Task Order 01 Performance Work Statement (PWS).pdf

Attachment 1: Task Order 01 Performance Work Statement 70Z044-21-R-21000300

Search and Rescue Optimal Planning System (SAROPS) Preventative and Corrective Maintenance

(Task Order 1)

PERFORMANCE WORK STATEMENT (PWS)

1. Scope

1.1. The scope of this Task Order includes the Preventative and Corrective Maintenance for all software and infrastructure components of the SAROPS system and further refinement of the system to ensure all Operational, Functional, and System requirements are met.

1.2. Planned Sustainment work for this Task Order includes but is not limited to:

1.2.1. Migration of SAROPS into the Coast Guard One View (CG1V) Ozone Widget

Framework (OWF).

1.2.2. Continued refinement of the simulated movement of objects and vessels prior to entering a distressed state.

1.2.3. Continued refinement of optimal search pattern placement.

1.2.4. Continued work to ensure current functionality remains in compliance with

Sponsor defined requirements.

1.2.5. Continued modifications to the system to remain within CYBER Compliance.

1.2.6. Continued work to address and System Trouble Reports (STRs) or System

Improvement Requests (SIRs).

1.3. Other tasks may include implementation of additional automated testing tools, backlog maintenance, documentation updates, architecture diagrams, and other modifications to the User Interface (UI).

IDIQ SECTIONS. All sections in the IDIQ #70Z04421R21000200 (Formerly #70Z04420R20002700) PWS are applicable to this Task Order. The following are specific to this Task Order.

2. Performance Objectives

2.1. The Government’s objective of this TO is to sustain SAROPS, maintain Operational

Availability and improve the efficiency of SAROPS through the use of Agile Methodologies and a Sprint Cycle Process.

2.2. The Contractor shall prepare and submit a Monthly Progress Report (MPR) in accordance with CDRL A001. The Contractor’s MPR shall be submitted to the COR no later than the 5th working day of each month. The Contractor shall include a summary of its previous month’s project planning activity in the MPR, as required by the CDRL.

2.3. The Contractor shall prepare and submit a Work Breakdown Structure (WBS) in accordance with CDRL A002. The Contractor’s WBS shall be submitted to the COR annually with the first report due 30 days after award.

Attachment I: Task Order 01 Performance Work Statement 70Z044-20-R-21000200

2.4. Following the Contractor’s Agile Methodology, the Contractor shall meet the following requirements:

2.4.1. The Contractor shall, at the end of the Sprint Cycle, deliver the updated software, Software Code (CDRL A009), for installation on the CGTest enclave for further test and evaluation.

2.4.2. The Contractor shall also track the ratio of story points planned to story points completed to record the Velocity of work in accordance with CDRL A003.

2.4.3. The Contractor shall document the findings and recommendations of the sprint team within Monthly Progress Reports (CDRL A001) and summarize the findings and recommendations during quarterly progress review meetings.

2.4.4. The Contractor shall prepare and maintain Software Design Documents (CDRL A005, Interface Requirement Specification, Database Design, Data Dictionary and Schema. The Contractor shall deliver all Software Design Description in accordance with CDRL A005, Software Design Document.

2.4.5. The Contractor shall prepare and maintain Software Version Description (CDRL A006)

2.4.6. The Contractor shall prepare and maintain Software Test Reports (CDRL A007).

2.4.7. The Contractor shall propose Software Test Plans (CDRL A008) to the Government prior to the final sprint of a build and execute the approved Test Plan during the final sprint of a build.

2.4.8. After every build, the Contractor shall compile and integrate system modules to create builds which are delivered after every sprint. The software delivery, with the associated installation routines and procedures, is the number one objective of this task order. The Contractor shall deliver the Software Code (CDRL A009) at this time.

2.4.9. The Contractor shall maintain the product backlog with the agile toolset determined by the government (e.g. DI2E) in accordance with CDRL A010, Product Backlog List. The agile toolset is the primary conduit for team coordination, communication and work management.

2.5. Performance Requirements Summary

2.5.1. At a minimum, the contractor shall track and report the following metrics listed in the table below. This list is not all-inclusive; the contractor shall propose their recommendation for performance metrics in the area of Code Quality and Standards Adherence. Each change request completed by the contractor team will be evaluated by the Government Product Owner for that team, and possibly Subject Matter Experts (SMEs) assigned to the team. At each release review, held during the Interim Progress Review (IPR) week, the functionality will be evaluated by a wider audience of stakeholders. It is expected that the agreed-to functionality that is being delivered at the end of the each sprint iteration meets the agreed upon definition of done. A key indicator of business satisfaction will be Government acceptance at the end of each sprint cycle. Because automated tests are a key component of this process, test scripts will be assessed for their quality and for the extent to which the scripts test the appropriate functions. This evaluation will be performed by Government employees. At a minimum, the contractor shall track and report metrics within the Monthly Progress Report, CRDL A001, as identified in the table below.

Performance Objective Acceptable Quality Level

(AQL)

Positive Incentive Negative incentive

# Defects found in each sprint delivery - defect density, as determined by use of automated test tool.

<5% of test cases

Contractor Past Performance Evaluation may note success in pass AQL.

Contractor Past Performance Evaluation may note failure to pass AQL.

# Defects found in each candidate release delivery - defect density, as determined by use of automated test tool.

<2% of test cases

Contractor Past Performance Evaluation may note success in pass AQL.

Contractor Past Performance Evaluation may note failure to pass AQL.

# Successful candidate releases installed and positively tested on staging enclave.

>74% Contractor Past Performance Evaluation may note success in pass AQL.

Contractor Past Performance Evaluation may note failure to pass AQL.

# Accepted User Stories at end of each sprint

>80% Contractor Past Performance Evaluation may note success in pass AQL.

Contractor Past Performance Evaluation may note failure to pass AQL.

Customer Defect Rate. Amount of defects in functionality reaching customer after release.

<2% of test cases

Contractor Past Performance Evaluation may note success in pass AQL.

Contractor Past Performance Evaluation may note failure to pass AQL.

Release rollback efficiency. The number of times a release is rolled back do to non-compliance of requirements.

<2% of the time

Contractor Past Performance Evaluation may note success in pass AQL.

Contractor Past Performance Evaluation may note failure to pass AQL.

Qualitative Analysis on how well the team is adhering to Agile Standards/Best Practices, and Team Process Agreements.

100% of the time

Contractor Past Performance Evaluation may note success in pass AQL.

Contractor Past Performance Evaluation may note failure to pass AQL.

3. Roles and Responsibilities

3.1. Government Furnished Resources

3.1.1. There will be no Government Furnished Resources as part of this Task Order.

3.2. Contractor Furnished Property

3.2.1. The Contractor shall furnish all facilities, materials, equipment and services necessary to fulfill the requirements of this contract.

4. OPERATIONAL REQUIREMENTS

4.1. Personnel - Skills and Knowledge

4.1.1. The Contractor shall provide qualified personnel to perform all tasks specified, and within the timeframes specified. All employees supporting this contract shall be citizens of the United States due to Department of Homeland Security information security requirements. The Contractor shall provide qualified personnel to perform the tasks specified within this TO.

4.2. Project Management- Point of Contact.

4.2.1. The Contractor shall provide a single Point of Contact (POC) who shall be responsible for all Contractor work performed under this TO. The POC shall be a single point of contact for the Contracting Officer (KO) and the Contracting Officer’s Representative (COR). The name of the POC, and the name(s) of any alternate(s) who shall act for the Contractor in the absence of the Point of Contact, shall be provided to the Government as part of the Contractor's proposal. During any absence of the POC, only one alternate shall have full authority to act for the Contractor on all matters relating to work performed under this TO. The POC and the designated alternate shall be able to read, write, speak and understand English.

Additionally, the Contractor shall not replace the POC without prior notification to the COR.

4.3. Key Personnel

4.3.1. The Key Personnel required for this TO are:

4.3.1.1. System level Subject Matter Expert and Integrator;

4.3.1.2. Simulator and Planner Module Subject Matter Expert;

4.3.1.3. Environmental Data Interface GIS Subject Matter Expert.

4.3.2. Before replacing any individual designated as Key by the Government, the Contractor shall 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).

4.3.3. All proposed substitutes shall possess qualifications equal to or superior to those of the Key person being replaced, unless otherwise approved by the Contracting Officer.

4.3.4. The Contractor shall not replace Key Contractor personnel without approval from the Contracting Officer.

5. Deliverables

5.1. The Contractor is required to provide the following deliverables within the designated timeframes in addition to those required by the IDIQ:

Deliverable Due Date Delivery Method

Monthly Progress Report (CDRL A001)

Monthly by the 5th of each month

In electronic format with read/write capability using DHS compatible applications

Work Breakdown Structure (CDRL A002)

At the Project Kickoff Meeting and updated at the beginning of each sprint

In electronic format with read/write capability using DHS compatible applications

Sprint Metrics (CDRL A003)

End of every sprint. Electronic / visual board accessible via web (e.g. DI2E, etc.)

Meeting Minutes

(CDRL A004)

Within two (2) days of meeting

In electronic format with read/write capability using DHS compatible applications

Software Design Description (CDRL A005)

At the completion of each Build

In electronic format with read/write capability using DHS compatible applications

Software Version Description (CDRL A006)

At the completion of each Build

In electronic format with read/write capability using DHS compatible applications

Software Test Report

(CDRL A007)

Upon completion of testing In electronic format with read/write capability using DHS compatible applications

Software Test Plans

(CDRL A008)

Prior to the last sprint of each build

Electronic / visual board accessible via web (e.g. DI2E, etc)

Software Code (CDRL A009)

End of every sprint. Version-controlled Open Source repository of code that comprises product that will remain in the public domain

Product Backlog List

(CDRL A010)

Beginning of each sprint Electronic / visual board accessible via web (e.g. DI2E, etc.)

5.2. General Report Requirements

5.2.1. As per IDIQ PWS Section 7.2 General Reporting.

6. Review and Acceptance

6.1.1. As per IDIQ PWS Section 8.2 Government Acceptance.

7. Travel and Other Direct Costs (ODC)

7.1. There are no anticipated travel or reimbursable costs associated with this Task Order. The

Contractor shall be responsible for any travel costs incurred during attendance at meetings and reviews.

8. Terms and Conditions

8.1. Type of Contract

8.1.1. This is a Firm Fixed Price Task Order.

8.1.2. Period of Performance (POP) The Period of Performance (POP) shall be for 12 months from date of TO award. With four (4) twelve month (12) options.

8.2. Place of Performance

8.2.1. The primary place of performance will be the Contractor’s facility. The

Contractor shall provide 1 to 2 Team Members, 1 to 2 times per week to collaborate onsite at the Government’s facility located at: Department of Homeland Security, US Coast Guard, Command Control Communications Engineering Center (C3CEN) at 4000 Coast Guard Blvd, Portsmouth VA 23703 or virtually.

8.3. Contract Administration

8.3.1. The TO Contracting Officer (KO) is Mr. Robin Spelman. Contact information for Mr. Spelman is (757) 686-6781or Robin.C.Spelman@uscg.mil.

8.3.2. The Task Order Contracting Officer Representative (COR) is Ms. Julie Haug.

Contact information for Ms. Haug is (757) 686-4158 or julie.a.haug@uscg.mil.

mailto:julie.a.haug@uscg.mil