Attachment_J.3_-_Contract_Document_Requirements_List.pdf

Attachment J.3 - Contract Document Requirements List

U.S. DEPARTMENT OF COMMERCE

NATIONAL OCEANIC AND ATMOSPHERIC

ADMINISTRATION

NATIONAL WEATHER SERVICE

ADVANCED WEATHER INTERACTIVE PROCESSING

SYSTEM

CONTRACT DATA REQUIREMENTS LIST

JULY 08, 2015

ACQUISITION AND GRANTS OFFICE

EASTERN ACQUISITION DIVISION

NORFOLK, VIRGINIA

1. INTRODUCTION

This document provides the Contract Data Requirements List (CDRL) with the associated Data

Item Description (DIDs) of all data, information, and/or document deliverables that shall be provided by the Offeror in support of the Advanced Weather Interactive Processing System

(AWIPS).

2. IDENTIFICATION, REFERENCE, DELIVERY, AND ACCEPTANCE

The Contractor shall include a formal letter of transmittal with each submission, addressed to the Contracting Officer (CO) as follows:

Timothy Wampler, AWIPS Contracting Officer

National Weather Service Branch

U. S. Department of Commerce/NOAA/EAD

Norfolk Federal Building

200 Granby Street--Suite 815

Norfolk, VA 23510-1811

Telephone: 757.441.6563

Email: timothy.wampler@noaa.gov and Contracting Officer’s Representative (COR) at:

Beraq Azeem, AWIPS Contracting Officer’s Representative

Central Processing (W/CP)

U. S. Department of Commerce/NOAA/NWS

1325 East-West Highway

SSMC-2, Room 15130

Silver Spring, MD 20910

Telephone: 301.427.9230

Email: Beraq.Azeem@noaa.gov

3. DELIVERY FORMAT

Unless otherwise indicated, all data items shall be provided in electronic format to the

Government. Electronic deliverables shall be provided in the following Microsoft Office® formats unless otherwise approved by the CO:

Text Documents: Microsoft (MS) Word®

Presentations: Microsoft (MS) PowerPoint®

Spreadsheets: Microsoft (MS) Excel®

Databases: Delimited ASCII files accompanied by either database schema document defining tables and entries or XML schema and tagged definitions

Schedules: Microsoft (MS) Project®

Schematics and Drawings: Portable Document Format (PDF) and Microsoft Visio®

Photographs: JPEG or current industry standard

Video: Any readily available open standard (e.g., AVI, MPEG)

Hard copy: Hard copy deliverables include data that is typed, drawn or printed on paper by common conventional practices. If printed copies are required, they shall be produced from the original, the record copy, or a reproducible equivalent.

mailto:timothy.wampler@noaa.gov mailto:Beraq.Azeem@noaa.gov

Wiki: Provided in a format suitable for posting on the VLab.

Unless indicated or specifically requested, electronic submissions are the standard. All deliverables shall be provided to the COR at the address below, unless otherwise requested by the CO:

Beraq Azeem, AWIPS Contracting Officer’s Representative

Central Processing (W/CP)

U. S. Department of Commerce/NOAA/NWS

1325 East-West Highway

SSMC-2, Room 15130

Silver Spring, MD 20910

Telephone: 301.427.9230

Email: Beraq.Azeem@noaa.gov

4. DELIVERABLE ACCEPTANCE CODE

The following codes apply to submittal of all CDRL data items (i.e., initial, final, and updates):

Code Nomenclature Description

A Approval

Documents in this category must be submitted to the Government within the time specified. The Government will act on items requiring approval within thirty (30) calendar days of receipt of the item.

Documents in the Approval category require written approval prior to Contractor implementation unless more than thirty (30) calendar days have elapsed since Government receipt of the item, and no written response from the Government has been received.

Requirements for data item resubmission or conditional use will be as specified in CO notice(s) of disapproval.

R Review

Documents in the Review category shall be submitted to the

Government within the time period specified, and will be subject to evaluation. Review category documents shall be implemented upon issuance unless otherwise noted. When an evaluation reveals inadequacies in a Review document, the Contractor shall correct the document as specified by the Government.

I Information

Documents in this category will be used by the Government to determine current project status and progress, and for future planning requirements.

5. FORMAT

The Contractor shall produce document deliverables containing a table of contents that provided the number, title, and page number of the titled paragraph and subsequent appendices to a level adequate to assist the reader in locating the desired information. Each paragraph of the deliverable need not be included. The table of contents shall contain the number, title, and page number for each figure and table presented.

The Contractor shall produce, for data in a database or other alternative form, information consisting of an internal or external table of contents containing pointers to, or instructions for accessing, each paragraph, figure, table, and appendix or their equivalents.

Unless otherwise specified in the individual Data Item Description, Contractor format is acceptable.

6. DOCUMENT CHANGE PROCEDURES

Documentation change procedures are described below:

The Contractor shall issue documentation change notices (DCNs) whenever minor changes or updates occur in data items that have been provided to the Government.

Change bars shall be used to indicate changes or updates.

When major changes to a document are made, a complete revision of the document shall be issued and provided to the Government.

7. DOCUMENT MARKINGS

The Contractor shall mark documents containing materials or information covered and controlled by International Traffic in Arms Regulations (ITAR) or Export Administration

Regulations (EAR), as determined by the Contractor, on the cover and on pages containing such materials.

The Contractor shall mark documents containing Contractor proprietary materials or information, as determined by the Contractor, on the cover and on pages containing such materials.

The Contractor shall not unnecessarily or unjustifiably mark documents with restrictive or limiting labels, nor shall such labeling be applied frivolously or indiscriminately.

8. CONTRACT DATA REQUIREMENTS LIST

The Tables in Section 8.3 through 8.6 are the Contract Data Requirements List for each category listed in Table 8.1. The Government reserves the right to modify any Data Item

Description to improve the quality and timeliness of deliverables.

Table 8.1: Data Item Prefix and Associated Functional Category

Data Item

Prefix

Functional Category of the Work

Breakdown Structure

PM Program Management

OM Operations and Maintenance

IT Information Technology Security

PI Product Improvement

Please note that, where delivery to the Contracting Officer is indicated, the Contractor need furnish only the letter of transmittal (unless otherwise specified).

The following codes as shown in Table 8.2 indicate the NOAA personnel to whom the data shall be provided:

Table 8.2: NOAA Personnel Codes to Received AWIPS Data, Information, and

Documents

CO AWIPS Contract Officer

COR AWIPS Contract Officer Representative

PM AWIPS Program Manager

DPM—O&M Deputy AWIPS Program Manager for Operations & Maintenance

DPM—PI Deputy AWIPS Program Manager for Product Improvement

SO AWIPS System Owner

ISSO Information System Security Officer

ACA AWIPS Chief Architect

The objective number references in the tables below are from the Advanced Weather

Interactive Processing (AWIPS) Statement of Objectives (SOO) document dated July 08, 2015. Any RFP section references in the tables below are from the Advanced Weather

Interactive Processing Request for Proposal (RFP) document dated July 08, 2015.

Table 8.3: Program Management Data, Information, and/or Documents

CDRL

ITEM #

SOO/RFP REF TITLE DUE/FREQUENCY

DELIVERY

MODE

(HARD

(#)/SOFT)

DELIVER TO:

A C

C E

P T

A N

C E

O

D

PM-01

RFP - Table L.6.2

SOO - 4.1.2; 4.1.3; 4.1.4; 4.1.5;

4.1.6; 4.1.7; 4.1.8; 4.1.9; 4.1.10;

4.1.11; 4.1.12; 4.1.13

Program Management Plan Initial: Per Terms of the Contract

Final: Per Terms of the Contract

HARD

(1)/SOFT

CO, COR A

PM-02 RFP - H.8 Travel Request As required SOFT CO, COR A

PM-03

RFP - H.19

SOO - 4.1.2; 4.1.3; 4.1.4; 4.1.5;

4.1.6; 4.1.7; 4.1.8; 4.1.9; 4.1.10;

4.1.11; 4.1.12; 4.1.13

Risk Management Plan

Initial: Contract Award + 30 calendar days

Updates: Annual

HARD (1)/

SOFT

CO, COR, PM,

DPM-O&M,

DPM-PI, ACA,

ISSO

A

PM-04

SOO - 4.1.2; 4.1.3; 4.1.4; 4.1.5;

4.1.6; 4.1.7; 4.1.8; 4.1.9; 4.1.10;

4.1.11; 4.1.12; 4.1.13

Risk Register and Risk

Register Review Meeting

Initial: Contract Award + 30 calendar days

Updates: Monthly

SOFT

CO, COR, PM,

DPM-O&M,

DPM-PI, ACA,

ISSO

R

PM-05

SOO - 4.1.2; 4.1.3; 4.1.4; 4.1.5;

4.1.6; 4.1.7; 4.1.8; 4.1.9; 4.1.10;

4.1.11; 4.1.12

Integrated Master Schedule

Final: Contract Award + 120 calendar days

Updates: As Required (e.g., variance greater/less than 10%;

Initiation of new project; etc.)

SOFT

CO, COR, PM,

DPM-O&M,

DPM-PI, ACA,

ISSO

A, R

PM-06 RFP/G.8 Invoices Final: Monthly through POP SOFT CO, COR A

PM-07

RFP – FAR 52.234-4

SOO - 4.1.2; 4.1.3; 4.1.4; 4.1.5;

4.1.6; 4.1.7; 4.1.8; 4.1.9; 4.1.10;

4.1.11; 4.1.12; 4.1.13

Earned Value Management

System reports

Initial: Contract Award + 60 calendar days

Updates: Monthly

SOFT CO, COR A, R

CDRL

ITEM #

SOO/RFP REF TITLE DUE/FREQUENCY

DELIVERY

MODE

(HARD

(#)/SOFT)

DELIVER TO:

A C

C E

P T

A N

PM-08 SOO Section 8 Service Level Agreement

Descriptions

Initial: As specified in the

Quality Assurance Plan

(QAP)/Quality Assurance

Surveillance Plan (QASP)

Updates: As specified in the

QAP/QASP

SOFT

CO, COR, PM,

DPM-O&M,

DPM-PI

A

PM-09 SOO – 4.1.2; 4.1.3

Performance and Availability

Reports

Initial: Contract Award + 60 days

Updates: Monthly

SOFT

COR, PM,

DPM-O&M,

DPM-PI

I

PM-10 SOO Section 8 Service Level Agreement

Metrics Reports

Initial: As specified in the

QAP/QASP

Updates: As specified in the

QAP/QASP

SOFT

CO, COR, PM,

DPM-O&M,

DPM-PI

A, R

PM-11 SOO – 4.1.2; 4.1.4; 4.1.12

Program Status

Reports/Meetings

Initial: Contract Award + 30 days

Updates: Weekly (Alternating

OM and PI)

SOFT

CO, COR, PM,

DPM-O&M,

DPM-PI

R

PM-12 RFP – I.7, I.8, I.9

Corrective Action Plan and

Reports Initial: As needed

Updates: As needed

SOFT

CO, COR, PM,

DPM-O&M,

DPM-PI

A

PM-13 Defined at the Task Order Level Preliminary Engineering

Change Proposals As needed, proposal response to

Task Order SOW

SOFT

CO, COR, PM,

DPM – O&M

A

PM-14

Deliverable defined at the Task

Order Level

Engineering Change

Proposals As specified in Task Order

SOFT

CO, COR, PM,

DPM—O&M,

DPM—PI

A

PM-15

Deliverable defined at the Task

Order Level

Installation Modification

Notes As specified in Task Order SOFT

CO, COR, PM,

DPM—O&M,

DPM—PI

A

Table 8.4: O&M Data, Information, and/or Documents

CDRL

ITEM #

SOO/RFP REF TITLE DUE/FREQUENCY

DELIVERY

MODE

(HARD

(#)/SOFT)

DELIVER TO:

A C

C E

P T

A N

OM-01 SOO – 4.1.2; 4.1.7; 4.1.11 AWIPS User Manual (UM)

Initial: Final version 5 days after initial software release acceptance.

Updates: Final version 5 days after software release acceptance

SOFT

COR, PM,

DPM-O&M

R

OM-02 SOO – 4.1.2; 4.1.7; 4.1.11 AWIPS Release Notes

Initial: Final version due 5 days after initial software release acceptance.

Updates: Final version due 5 days after software release acceptance

SOFT

COR, PM,

DPM-O&M,

DPM-PI, ISSO,

ACA

R

OM-03 SOO – 4.1.2; 4.1.7; 4.1.11

AWIPS System Manager’s

Manual

Initial: Final version due 5 days after initial software release acceptance.

Updates: Final version due 5 days after software release acceptance

SOFT

COR, PM,

DPM-O&M,

ACA

R

OM-04 SOO – 4.1.2; 4.1.7; 4.1.11

AWIPS Software Version

Document

Initial: Final version due 5 days after initial software release acceptance.

Updates: Final version due 5 days after software release acceptance

SOFT

COR, PM,

DPM-O&M,

DPM-PI, ISSO,

ACA

R

CDRL

ITEM #

SOO/RFP REF TITLE DUE/FREQUENCY

DELIVERY

MODE

(HARD

(#)/SOFT)

DELIVER TO:

A C

C E

P T

A N

OM-05 SOO – 4.1.2; 4.1.7; 4.1.11

AWIPS Stand-Alone

Installation Instructions

Initial: Final version due 5 days after initial software release acceptance.

Updates: Final version due 5 days after software release acceptance

SOFT

COR, PM,

DPM-O&M,

DPM-PI, ISSO,

ACA

R

OM-06 SOO – 4.1.2; 4.1.7; 4.1.11

AWIPS Cluster Installation

Instructions

Initial: Final version due 5 days after initial software release acceptance.

Updates: Final version due 5 days after software release acceptance

SOFT

COR, PM,

DPM-O&M,

DPM-PI, ISSO,

ACA

R

OM-07 SOO – 4.1.2; 4.1.7; 4.1.11

AWIPS Development

Environment Installation and Set-up Instructions

Initial: Final version due 5 days after initial software release acceptance.

Updates: Final version due 5 days after software release acceptance

SOFT

COR, PM,

DPM-O&M,

DPM-PI, ISSO,

ACA

R

OM-08 SOO – 4.1.2; 4.1.7; 4.1.11

AWIPS Software System

Design Description

Initial: Contract Award + 6 months

Updates: Semi-annually or as needed

SOFT

COR, PM,

DPM-O&M,

DPM-PI

R

OM-09 SOO – 4.1.2; 4.1.6 AWIPS Network Data Flow

Initial: Contract Award + 6 months

Updates: Annually

SOFT

COR, PM, DPM

– O&M, ACA

CDRL

ITEM #

SOO/RFP REF TITLE DUE/FREQUENCY

DELIVERY

MODE

(HARD

(#)/SOFT)

DELIVER TO:

A C

C E

P T

A N

OM-10 SOO – 4.1.2

AWIPS Contingency Test

Plans

Initial: Contract Award + 30 days

Updates: Monthly or as needed

SOFT

COR, PM, DPM

– O&M, ISSO

I

OM-11 SOO – 4.1.2

Periodic AWIPS

Government Property List

Updates

Initial: Contract Award + 30 days

Updates: Semi-annually or as needed

SOFT

CO, COR, PM,

DPM-O&M

I

OM-12 SOO – 4.1.2 AWIPS Hardware Matrix

Initial: Contract Award + 6 months

Updates: Semi-annually or as required

SOFT

COR, PM,

DPM-O&M

I

Table 8.5: IT Security Data, Information, and/or Documents

ITEM #

SOO/RFP REF TITLE DUE/FREQUENCY

DELIVERY

MODE

(HARD

(#)/SOFT)

DELIVER TO:

A C

C E

P T

A N

IT-01 SOO – 4.1.4

Plan of Actions and

Milestone Remediation

Progress Report

Initial: Transition Complete + 60 days

Updates: Quarterly

SOFT COR, SO, ISSO A

IT-02 SOO – 4.1.4 Vulnerability Scan Report Initial: Contract Award + 60 days

Updates: Monthly

SOFT COR, SO, ISSO A

IT-03 SOO – 4.1.4 Patch Report Initial: Contract Award + 60 days

Updates: Monthly

SOFT COR, SO, ISSO A

Table 8.6: Product Improvement Data, Information, and Documents

ITEM #

SOO/RFP REF TITLE DUE/FREQUENCY

DELIVERY

MODE

(HARD

(#)/SOFT)

DELIVER TO:

A C

C E

P T

A N

PI-01 SOO - 4.1.12

Product Improvement

Monthly Task Order Report Updates: Monthly SOFT

COR, PM,

DPM-PI

R

PI-02 SOO - 4.1.12 Product Improvement Plan

Initial: Contract Award + 12 months

Updates: Annually or as needed

SOFT

CO, COR, PM,

DPM-O&M,

DPM-PI

The Data Item Descriptions associated with the foregoing are as follows:

DATA ITEM DESCRIPTION

NUMBER: PM-01

TITLE: Program Management Plan

REVISION: None

DATED: 26 June 2015

1. Description/Purpose

The Program Management Plan (PMP) provides a detailed and comprehensive explanation of the strategies to be used for project plan execution and project integration, and delineate the organizational policies, tools, and techniques proposed for coordination and direction of the various technical and organizational interfaces required for successful execution of the AWIPS project.

2. Intended Use

The PMP provides a mechanism to understand how the Contractor intends on managing the AWIPS program.

3. Basic Content

The PMP shall address the following information…

Inter-relationships with the prime Contractor and the subcontractors, and relationship with the Government.

Overall organization, management approach, and structure plus interrelationships with the parent company and the subcontractors, and relationship with the

Government.

The nature of the tasks and related potential problems, discuss the approach to problem avoidance and/or solution, and address the degree to which proposed procedures are proven through similar experience.

Interfaces with the AWIPS Operations and Maintenance activities and the integration of product development activities and new projects.

Explanation of the process to be followed by the program manager in obtaining decisions beyond his/her authority and in resolving priority conflicts for resources and functions not under the project manager’s direct control such as personnel, finances, and facilities.

Work Breakdown Structure (WBS) with details of the major activities/projects.

Procurement management.

How any subcontracts will be managed and reviewed plus the interrelationships with the parent company and the subcontractors.

Contractual procedures proposed for the program to effect administrative and engineering changes, describing any differences from existing procedures.

Management techniques to be employed in minimizing project costs and schedule impacts, including controls to be exercised over subcontractors and suppliers.

Communications management of O&M activity and active project status, budget, schedule, and quality performance.

Quality management, including staffing plans, reporting channels, authority and responsibilities, and management visibility.

Techniques used to measure and control the work process and product quality.

Quality assurance of work processes, verification and validation, joint reviews, audits, and process assessment.

Process for performing process improvement activities.

4. Format

The Program Management Plan shall be provided in PDF.

DATA ITEM DESCRIPTION

NUMBER: PM-02

TITLE: Travel Requests

REVISION: None

DATED: 26 June 2015

1. Description/Purpose

Travel will be authorized in writing and in advance by the COR or CO, except in emergencies. Emergency travel will be documented by a retroactive request complying with this DID as soon as is practicable after the travel occurs.

2. Intended Use

Travel requests allow the COR or CO to approve the trip prior to expending the costs.

3. Basic Content

All travel requests shall comply with the requirements of the Federal Travel Regulation

(FTR), available online at http://www.gsa.gov/portal/content/104790 .

Travel not planned for within executed Task Orders be completed at least five (5) business days prior to the first day of planned travel, except in the case of emergencies. If the travel was planned for within the execution of Task Orders, then the obligation of the Task Order provides necessary approval for the required trips.

Travel Requests shall document the purpose and duration of the trip; the destination; the number of people traveling and their titles; the means and cost of conveyance (whether by personally-owned vehicle—POV, rental vehicle(s), or public ground or air transportation);

and the anticipated per diem/meals and incidental expenses (MI&E).

Travel Requests shall also include any other necessary and appropriate Other Direct Costs

(ODCs).

4. Format

Travel requests not included within executed TOs shall be submitted via e-mail to the COR or CO.

http://www.gsa.gov/portal/content/104790

DATA ITEM DESCRIPTION

NUMBER: PM-03

TITLE: Risk Management Plan

REVISION: None

DATED: 26 June 2015

1. Description/Purpose

The Risk Management Plan describes the process and procedures used to govern risks and opportunities for the AWIPS program.

2. Intended Use

The Risk Management Plan is used by the stakeholders to identify, assess and analysis, qualify, monitor and implement, and measure and control risks and opportunities within the AWIPS program.

3. Basic Content

Risk Management Plan shall

Describe the process and procedure of how risks and opportunities are identified, assessed, analyzed, qualified, monitored, implemented, and measured.

Describe how the Contractor will participate in the AWIPS risk management process.

Address how risks/opportunities will be tracked and the escalated into issues within the risk register.

Describe risk meetings, including Contract participants, risk register update process, and action tracking.

When qualifying a joint Government and Contract risk for the program, the following 5x5 matrix shall be used

The Risk Management Plan shall be provided in PDF.

DATA ITEM DESCRIPTION

NUMBER: PM-04

TITLE: Risk Register and Risk Register Review Meeting

REVISION: None

DATED: 26 June 2015

1. Description/Purpose

The Risk Register provides a listing of all risks and opportunities associated with the

AWIPS program. The Risk Register Review Meeting allows the Contractor and

Government to jointly review performance, cost, and schedule risks/opportunities of the program, activity projects and operations and maintenance activities.

2. Intended Use

The Risk Register provides all stakeholders with the current status of risk/opportunity and associated mitigations. The Risk Register Review Meeting provides a mechanism to discuss/update the risk register jointly between the Contractor and Government.

3. Basic Content

The Risk Register shall:

Be prepared in accordance with the Contractor’s Risk Management Plan;

Be used to document any AWIPS program risks/opportunities, including those identified during operations, through meetings, and in execution of O&M and product improvement projects;

Include any mitigation strategies (if applicable) to prevent the risk from occurring or recurring, and the mitigation plan, shall the undesired event occur in the future;

Include an estimate of the likelihood and consequence of risk in area of schedule, technical, and cost along with actions, status or comments associated with the risk;

and

Include additional risk tracking information, including risk number, risk description, risk category, risk owner, date reported, consequence, likelihood, mitigation strategy, mitigation cost (if available), action/status/comments, risk status, and whether the risk is a joint Government/Contractor risk or just a

Contractor risk.

4. Format

The Risk Register format shall be Microsoft Excel® or PDF. It is acceptable to use Risk software package as long as the software can create report(s) containing required information in either Microsoft Excel® or PDF.

DATA ITEM DESCRIPTION

NUMBER: PM-05

TITLE: Integrated Master Schedule

REVISION: None

DATED: 26 June 2015

1. Description and Purpose

The Integrated Master Schedule (IMS) is an integrated, resource loaded, and networked schedule containing all of the agreed upon work packages, planning packages, and tasks and activities required to successfully complete the work. It is vertically traceable to the

WBS, and PWS.

2. Intended Use

The IMS is used to verify attainability of task order objectives, to objectively evaluate progress toward meeting project objectives, and to integrate the project schedule activities with all related components.

The IMS provides an overview of all planned changes to the development, integration and test, and operational environments.

3. Basic Content

The Integrated Master Schedule shall include the full scope of activities potentially impacting AWIPS operations and maintenance and product improvement projects.

The IMS format shall be Microsoft Project® and Portable Document Format (PDF).

DATA ITEM DESCRIPTION

NUMBER: PM-06

TITLE: Invoices

REVISION: None

DATED: 26 June 2015

1. Description/Purpose

Invoices identify services and products provided to the Government, and the payment amount expected by the Contractor.

2. Intended Use

The invoice provides a basis for the COR to approve payment to the Contractor.

3. Basic Content

Invoices shall list each products and services provided by the associated project Work

Breakdown Structure (WBS) element. Invoices shall include

Payment term, typically thirty (30) day net

Contract Number

Invoice Date

Billing Date

Period of Performance

Invoice Number

Include the Vendors Address

WBS number/Task number

Total Monthly Amount

Cumulative Amount

Task Value

Funded Value

Labor Cost

Direct Cost

Indirect Cost

Fringe

Overhead

G&A

Burden

Hours

Cumulative Hours

Description of Services Provided and total number of hours billed

Other than Direct Charges.

Invoices shall be provided in PDF format.

DATA ITEM DESCRIPTION

NUMBER: PM-07

TITLE: Earned Value Management System Reports

REVISION: None

DATED: 26 June 2015

1. Description/Purpose

An earned Value Management System (EVMS) report provides a summary of cost and schedule performance within the program.

2. Intended Use

EVMS reports provide the stakeholders with insight in project execution performance for cost and schedule. The information contained in these reports is used to support AWIPS programmatic reporting requirements within the Exhibit 300.

3. Basic Content

The EVMS report shall include

Contractor Name and Address

Contract Number

Type of Contract (or Task Order)

Report Period

Performance Data - BCWS - BCWP - ACWP - Schedule VAR Cost-VAR

BAC Dollars

Problems Analysis

Task/Project Impact

Correction Action Plan, if required

Signed by the preparer

Submission Date

The EVMS report shall be provided in Microsoft Excel®.

DATA ITEM DESCRIPTION

NUMBER: PM-08

TITLE: Service Level Agreement Descriptions

REVISION: None

DATED: 26 June 2015

1. Description/Purpose

The Service Level Agreements (SLA) descriptions provide the agreed upon SLAs per the terms defined in the Quality Assurance Plan (QAP) and Quality Assurance Surveillance

Plan (QASP).

2. Intended Use

The agreed upon SLA guide the measurement of contractor performance per the terms defined in the QAP/QASP.

3. Basic Content

The SLA description document shall contain

Metric Name

Work Breakdown Structure reference number

Metric Description, including any definitions required

Metric Purpose

Data source for the SLA evaluation

Any formulas required to calculate the SLA results

SLA Weight

Acceptable Performance Level

Any applicable examples of how to evaluate the SLA

The SLA descriptions shall be provided in Microsoft Word®.

DATA ITEM DESCRIPTION

NUMBER: PM-09

TITLE: Performance and Availability Report

REVISION: None

DATED: 26 June 2015

1. Description/Purpose

The Performance and Availability Report (PAR) provides information on the performance and availability of AWIPS.

2. Intended Use

The PAR is used to monitor performance and availability of key areas of AWIPS, including Satellite Broadcast Network, Wide Area Network, Network Control Facility, and software and hardware issues at operational locations.

3. Basic Content

The PAR shall include the following information across the enterprise and at each operational location:

An executive summary of the overall health of AWIPS

Trouble Ticket Information and statistics

Database status

Hardware status

Software status

System Monitoring status

SBN status

OpsNet status (in support of AWIPS)

Bandwidth utilization

Network availability

The PAR shall be provided in PDF.

DATA ITEM DESCRIPTION

NUMBER: PM-10

TITLE: Service Level Agreement Metric Report

REVISION: None

DATED: 26 June 2015

1. Description/Purpose

The Service Level Agreement (SLA) Metric Report provides analysis of the Contractor’s performance during the review period as specified in the Quality Assurance Plan (QAP) and Quality Assurance Surveillance Plan (QASP).

2. Intended Use

This report provides Government monitors a monthly status of the Contractors’ performance against the agreed upon SLAs.

3. Basic Content

The SLA Metric Report shall contain

Work Breakdown Structure number reference

Metric Name

Acceptable Performance Level (APL)

SLA Weight

Negative percentage for metrics below APL

Percentage for metrics that meet APL

Percentage for metrics that exceed APL

Raw score

Evaluation of raw score against APL

The SLA Metric Report shall be provided in Microsoft Excel®.

DATA ITEM DESCRIPTION

NUMBER: PM-11

TITLE: Program Status Reports and Meetings

REVISION: None

DATED: 26 June 2015

1. Description/Purpose

These status meetings provide stakeholders with an update on all active projects and

Operation and Maintenance (O&M) activities. The meetings take place weekly, alternating between O&M activities and active O&M Task Orders (TOs) and Product Improvement

(PI) bi-weekly Status Meeting for active PI TOs.

2. Intended Use

The weekly status meetings provide a means for the Government to monitor active O&M activities, projects and PI project status and discuss any issues, risks and mitigations, or other concerns with the Contractor to ensure that each task order is being successfully executed.

3. Content

The Contractor shall meet and/or tele/videoconference with the Government for up to 90 minutes on a weekly basis. For each active task order or significant O&M activity, the

Contractor shall provide a Quad Chart that includes the following information:

Task Description Summary

Status

Color coded summary and forecast for schedule, cost, and technical risk

Task milestones and their completion status

Risk/Issues and mitigations

Action Item Status

Quad Charts shall be provided to the Government electronically no less than 24 hours before the weekly meeting to allow the Government sufficient time to review and prepare for the meeting. Meetings shall be scheduled on the same day of the week at the same time, as agreed beforehand, and changed only with sufficient notice. Action Items shall be tracked by the Contractor and new ones identified at the meeting shall be provided to the

Government electronically by the close of business next business day.

The Quad Chart shall be provided in Microsoft PowerPoint®.

DATA ITEM DESCRIPTION

NUMBER: PM-12

TITLE: Corrective Action Plan and Reports

REVISION: None

DATED: 26 June 2015

1. Description/Purpose

The Correct Action Plan (CAP) is initiated by the CO and COR in response to a failing by the Contractor. This plan allows the Contractor to identify and implement approved corrective measures.

2. Intended Use

The CAP is used by the Government to correct major issues during the execution of this contract. This plan allows the Government and Contractor to develop an agreement on how to resolve an execution issue within the contract and then track the implementation of this agreement.

3. Basic Content

The CAP request (Government) contains the following

Date prepared

Date response is due from Contraction

Description of discrepancy or problem to be addressed, including any specific requirements

CO and COR Signature

The CAP response (Contractor) shall contain the following:

CAP Number

CAP Title

Description of discrepancy or problem

Root Cause Analysis

Proposed solution to resolve discrepancy or problem including schedule and any cost impacts

Description of impact on SLA resulting from this discrepancy or problem.

Applicable Contract signatures

Upon the Government’s approval of the CAP, the Contractor shall treat the CAP as an active project and report on the status as described in Program Status Reports/Meetings

Data Item Description.

The CAP shall be provided in Microsoft Word®.

DATA ITEM DESCRIPTION

NUMBER: PM-13

TITLE: Preliminary Engineering Change Proposals (PECPs)

REVISION: None

DATED: 26 June 2015

1. Description/Purpose

The Preliminary Engineering Change Proposal (PECP) is the “umbrella” under which all components (Request for Change, Technical Solution, Supporting Material, Bill of

Material, Site Listing Allocation, Modification Notes, etc.) of a system modification are organized.

A PECP is required in response to a Government issued Task Order Statement of Work

(TOSOW).

2. Intended Use

The Preliminary Engineering Change Proposal provides specific technical details necessary to implement changes defined in the TOSOW.

3. Basic Content

The PECP shall contain all information necessary to describe the technical response to a

Government issued TOSOW. The PECP shall be supported by drawings and other data

(e.g., Logistic Support Analysis (LSA) data, detailed cost proposal data (under separate cover), site deployment data, etc.) as specified in the contract to justify and describe the change and to determine its total impact including assessments of changes to system operational employment characteristics.

The PECP and cost portion shall be provided in PDF format as separate documents.

DATA ITEM DESCRIPTION

NUMBER: PM-14

TITLE: Engineering Change Proposals

REVISION: None

DATED: 26 June 2015

1. Description/Purpose

Engineering Change Proposals (ECP) are the final versions under which all components

(Request for Change, Technical Solution, Supporting Material, Bill of Material, Site

Listing Allocation, Modification Notes, etc.) of a system modification are organized.

2. Intended Use

The ECP provides the technical details and support documentation for a change to be implemented within the AWIPS baseline. The ECP forms the bases of the Request for

Change that is reviewed and approved by the Government’s Change Control Board.

3. Basic Content

The ECP shall contain all information necessary to describe the final technical solution that will be implemented as a change to the AWIPS baseline. The ECP shall be supported by drawings and other data (e.g., Logistic Support Analysis (LSA) data, site deployment data, etc.) as needed to fully explain the change and impact to the AWIPS baseline. The ECP shall use the Request for Change form, found in the AWIPS technical Library, to document the technical changes and impact to AWIPS. The ECP shall be submitted to a Government representative on the Change Control Board in order to get final approval to implement described change.

The ECP shall be provided in PDF format.

DATA ITEM DESCRIPTION

NUMBER: PM-15

TITLE: Installation Modification (Mod) Note

REVISION: None

DATED: 26 June 2015

1. Description/Purpose

The Installation Modification Note (ModNote) provides installation instructions and related information for the replacement and upgrade of AWIPS hardware and software releases at field offices (WFO, RFC, NCEP, TWCs, NWC, and test beds).

The authority for this note is the Request for Change (RC) that is reviewed and approved by voting members of the Government’s Configuration Control Board (CCB).

2. Intended Use

The Installation ModNote is utilized by local office Electronic Systems Analyst (ESA) and or the Information Technology Office (ITO) in pursuance of standardization of AWIPS hardware or software installation across the AWIPS Enterprise to ensure uniformity and functionality.

3. Basic Content

The Installation ModNote will include the following items:

3.1 The sites affected

3.2 Verification Statement

3.3 Authorization

3.4 Estimated Completion Date

3.5 Accomplished By

3.6 Equipment Affected

3.7 Parts/Materials Required, if applicable

3.8 Source of Parts/Materials, if applicable

3.9 Tools Needed, if applicable

3.10 Reporting Instructions

3.11 Steps and procedures for completing installation

3.12 Test procedures

3.13 Warranty access information, if applicable

Reference: https://vlab.ncep.noaa.gov/web/awips-technical-library

The Installation ModNotes shall be provided in Microsoft Word® format.

https://vlab.ncep.noaa.gov/web/awips-technical-library

DATA ITEM DESCRIPTION

NUMBER: OM-01

TITLE: AWIPS User Manual

REVISION: None

DATED: 26 June 2015

1. Description/Purpose

The AWIPS User Manual (UM) provides end users with the information needed to access and utilize the User Interface (UI) of AWIPS for the retrieval and display of weather data.

2. Intended Use

The AWIPS UM describes the usages of Display 2-Dimensions Perspective within the

Common AWIPS Visualization Environment (CAVE), and the user interface components

(text and graphic displays) that comprise the AWIPS workspace.

The other perspectives — Graphical Forecast Editor, Hydro, Multi-Precipitation

Estimator, and Python (all of which are accessible from the CAVE main display) are currently outside the scope of this manual and are therefore not discussed in any detail.

3. Basic Content

The AWIPS UM shall remain consistent with the latest approved operational software release. The UM shall describe

The organization of the manual;

The AWIPS workstation and graphical UI in detail including how to get started using the graphical UI;

The AWIPS textual UI in detail including how to get started using the textual UI;

The WarnGen application;

The Interactive NsharpSkewt (NSHARP) application;

The Radar applications;

Local Data Acquisition and Dissemination functions;

Quality Control and System Monitoring functions;

Thin Client Remote Access;

Alert Visualizations functions;

Data Delivery functions;

Collaboration functions;

AWIPS II Archiver functions;

Statistical functions;

Geographical Information System data; and

Other applications, including o Climatological Reports Formatter o Hourly Weather Roundup, and Monitoring controller o Aviation Forecast Preparation System o System for Convection Analysis and Nowcasting o Flash Flood Monitoring Prediction o System on AWIPS for Forecasting and Evaluation of Seas and Lakes o Fog Monitor o Four-dimensional Stormcell Investigator o System for Nowcasting of Winter Weather o Hydrologic related functions

Reference: https://vlab.ncep.noaa.gov/web/awips-technical-library

The UM shall be provided in PDF with Table of Contents with embedded links.

DATA ITEM DESCRIPTION

NUMBER: OM-02

TITLE: Release Notes

REVISION: None

DATED: 26 June 2015

1. Description and Purpose

The AWIPS Release Notes provide stakeholders with information specific to each software release.

2. Intended Use

The Release Notes are used by the operational field offices to configure and understand the applicable software release.

3. Basic Content

The Release Notes shall meet all AWIPS CM and Technical Documentation Management requirements. The Release Notes shall include a listing of

Requirements-based and enhancement-based Discrepancy Reports (DRs) included within the release. The list shall include the DR numbers, DR titles, and a brief description of each DR;

DRs that passed acceptance testing and were included with the release. The list shall include the DR numbers, DR titles, and a brief description of each DR.

DRs and Design Change Specifications (DCSs) that are open and deferred to the next scheduled AWIPS release. The list shall include the DR and DCS numbers and

DR and DCS titles

Summarization of design changes made within the release.

Description of known problems, workarounds, and other release notes applicable to the release. The known problems shall be listed with their DR number.

XML base files, baseline templates, and the RPMs that have changed in the AWIPS release

Reference: https://vlab.ncep.noaa.gov/web/awips-technical-library

The AWIPS Release Notes shall be provided in PDF with Table of Contents with embedded links.

https://vlab.ncep.noaa.gov/web/awips-technical-library

DATA ITEM DESCRIPTION

NUMBER: OM-03

TITLE: System Manager’s Manual

REVISION: None

DATED: 26 June 2015

1. Description/Purpose

The AWIPS System Manager’s Manual (SMM) provides information for use in managing the Advanced Weather Interactive Processing System (AWIPS) at a site level. System management includes controlling user access, supporting user functions, and some file and database maintenance. Each area of responsibility requires knowledge of and the ability to use AWIPS components.

2. Intended Use

The AWIPS Systems Managers Manual is intended to be used by AWIPS system managers, and designed to serve as a guide for the management of operational AWIPS.

Users are assumed to have a basic understanding of, and some experience using, UNIX, Linux, Postgres, SQL, Java, and Python.

3. Basic Content

The AWIPS System Manager’s Manual shall provide a description of the… system architecture;

user accounts;

data flow overview;

ingesting of satellite imagery;

ingesting of NWS Telecommunications Gateway data;

ingesting of RADAR data;

Local Data Acquisition and Dissemination processes;

Background applications, include Climatological Reports formatting, Hourly

Weather Roundup, Aviation Forecast Preparation System, and NOAA Weather

Radio Editor;

Asynchronous Product Scheduler;

Crons and Purging;

Database Management;

Event Notification;

Message Handling System;

Localization;

Customization;

System Monitoring;

Failover Management Procedures;

System Backup and Recovery Procedures;

System Console;

System Shutdown and Startup Procedures;

Maintenance Management Procedures;

NCF Archive;

Data Archive Server;

AWIPS Environmental Data Exchange (EDEX) Administration Guide;

Thin Client;

Collaboration;

Weather Event Simulator II Bridge;

Data Delivery System Administrator’s Guide; and

User Administration.

Reference: https://collaborate2.nws.noaa.gov/partners/

The SMM shall be provided in PDF with Table of Contents with embedded links.

https://collaborate2.nws.noaa.gov/partners/

DATA ITEM DESCRIPTION

NUMBER: OM-04

TITLE: AWIPS Software Version Document

REVISION: None

DATED: 26 June 2015

1. Description/Purpose

The Software Version Document (SVD) provides stakeholders with a listing of the contents of each software release.

2. Intended Use

The SVD is used to inform stakeholders of the contents both Contractor developed software as well as COTS and FOSS packages included in a specific software release.

3. Basic Content

The SVD shall include a listing of each baseline file included with the AWIPS software release. At a minimum, the listing shall include the filename/path, date, size (bytes), CM author, and CM workset, and revision number. The SVD shall also include a listing of each

FOSS and COTS package included with the AWIPS release. At a minimum, the listing shall include the FOSS and COTS package name, version number, a brief description of the package, the license governing its use (and the license renewal dates, if applicable), and an indication if the package was Modified in any way for use in AWIPS.

Reference: https://collaborate2.nws.noaa.gov/partners/

The SVD shall be provided in PDF with Table of Contents with embedded links.

DATA ITEM DESCRIPTION

NUMBER: OM-05

TITLE: AWIPS Standalone Installation Instructions

REVISION: None

DATED: 26 June 2015

1. Description and Purpose

The Standalone Installation Instructions provide stakeholders with a full set of instructions that will describe how to install each new release of AWIPS software on a standalone machine.

2. Intended Use

These instructions enable stakeholders to successfully install AWIPS software in a standalone configuration.

3. Basic Content

Each set of instructions shall provide all commands necessary for both a clean installation of the AWIPS release and an upgrade from a previous version of AWIPS.

The Stand-alone Installation Instructions shall include

An introduction of the document, including a description of the purpose and font/typographical conventions used within the document;

Detailed and specific instructions and commands to be used for the installation of the AWIPS release on a standalone system. The instructions shall be clear as to which steps are needed for first-time (clean) installations, which are for upgrades

(on top of a previous version of AWIPS), and which are for both installation types.

Steps to perform a “Smoke Test,” a set of basic steps used to confirm if the installation was successful.

Reference: https://collaborate2.nws.noaa.gov/partners/

4. Format

The Standalone Installation Instructions shall be provided in PDF with Table of Contents with embedded links.

DATA ITEM DESCRIPTION

NUMBER: OM-06

TITLE: Cluster Installation Instructions

REVISION: None

DATED: 26 June 2015

1. Description/Purpose

The Cluster Installation Instructions provide stakeholders with a full set of instructions that will describe how to install each new release of AWIPS software in a cluster hardware configuration.

2. Intended Use

These instructions enable stakeholders to successfully install AWIPS software in a cluster configuration.

3. Basic Content

Each set of instructions shall provide all commands necessary for both a clean installation of the AWIPS release and an upgrade from a previous version of AWIPS.

The Cluster Installation Instructions shall include

An introduction of the document, including a description of the purpose and font/typographical conventions used within the document;

Detailed and specific instructions and commands to be used for the installation of the AWIPS release on a cluster hardware configuration. The instructions shall be clear as to which steps are needed for first-time (clean) installations, which are for upgrades (on top of a previous version of AWIPS), and which are for both installation types.

Steps to perform a “Smoke Test,” a set of basic steps used to confirm if the installation was successful.

Reference: https://collaborate2.nws.noaa.gov/partners/

4. Format

The Cluster Installation Instructions shall be provided in PDF with Table of Contents with embedded links.

NUMBER: OM-07

TITLE: AWIPS Development Environment Installation and Setup Instructions

REVISION: None

DATED: 26 June 2015

1. Description/Purpose

The AWIPS Development Environment (ADE) Installation and Setup Instructions provide stakeholders with a full set of instructions that will describe how to install the ADE in support of developer usage.

2. Intended Use

These instructions enable stakeholders to successfully install ADE.

3. Basic Content

The ADE Installation and Setup Instructions shall include

An introduction of the document, including a description of the purpose and font/typographical conventions used within the document.

Detailed and specific instructions and commands to be used for the installation of the ADE.

Detailed and specific instructions to setup the ADE.

Detailed and specific instructions on how to run and debug EDEX within the ADE.

Detailed and specific instructions on how to run and debug CAVE within the ADE.

Reference: https://collaborate2.nws.noaa.gov/partners/

4. Format

The ADE Installation and Setup Instructions shall be provided in PDF with Table of

Contents with embedded links.

NUMBER: OM-08

TITLE: Software System Design Description

REVISION: None

DATED: 26 June 2015

1. Description/Purpose

This Software System Design Description (SSDD) provides AWIPS software developers with a reference of key information when developing software in the AWIPS environment.

2. Intended Use

The purpose and scope of the SSDD document provides information and best practices to developers using the AWIPS Development Environment (ADE).

3. Basic Content

The SSDD shall contain:

An overview of o AWIPS Architecture o Plug-ins o Use of ADE o RPMs

A Description of Common services o EDEX Plug-ins o Localization o Serialization o Java Message Service/QPID o A how to:

Create new classes

Interactive with point data

Use of GeoTool

Use of Python

Use of Data Access Framework

EDEX

o Modes o Adapters o Thread Pools o Data Routing o Decoder Plug-ins o Data Purging o Clustering o Deploy and install o Logging configuration

Common AWIPS Visualization Environment (CAVE) o RCP Framework o SWT o Resources o Alert Observer o Features o Maps o Derived Parameters o How to Write Dialogs for CAVE Classes o How to customize SAVE

Data Flow o Standard data and notification flow o How to ingest data into CAVE o Ingest using manual dropped-in files

Reference: https://collaborate2.nws.noaa.gov/partners/

The SSDD shall be provided in PDF including Table of Contents with embedded links.

NUMBER: OM-09

TITLE: AWIPS Network Data Flow Diagrams

REVISION: None

DATED: 26 June 2015

1. Description/Purpose

The Network Data Flow Diagrams are a graphical and visual representation that shows the path and flow of data in the AWIPS system. These are visual diagrams of the AWIPS system from both physical and logical views.

2. Intended Use

Build graphical representations (a Network Data Flow Diagram) of the physical and logical network data flow of the AWIPS system that will be used as a tool to visualize the data and packet flow in the AWIPS system

3. Basic Content

The physical data flow diagram shall identify all physical components and how they are connected, including all sources of input and output to the AWIPS system; and all interfaces within and without the AWIPS system showing data flow media, protocols, and speeds.

The logical flow diagram shall identify all the modules in the AWIPS system and describe how data flows between them

4. Format

The Network Data Flow Diagram format shall be provided in two (2) ways; 1. in a native graphical format for editing and 2. in a PDF format.

NUMBER: OM-10

TITLE: AWIPS Network Control Facility Contingency Plan

REVISION: None

DATED: 26 June 2015

1. Description/Purpose

In the event of a catastrophic incident, the AWIPS Network Control Facility (NCF)

Contingency Plan will describe the require preparations and procedures to be used to restore service of the NCF.

2. Intended Use

This document describes how the NCF will continue to operate during a catastrophic event.

3. Basic Content

The AWIPS NCF Contingency Plan shall describe the require preparations and procedures necessary to be executed when an update to an operational system is made or in the event of an emergency when the NCF needs to switch over to the BNCF or reverse. In addition, this document shall include Test plans that include all of the necessary steps and policy to execute a switch over to the BNCF or reverse.

Contractor employees, especially those in the NCF, shall be required to verify the plan and familiarize personnel of the policy, plan, steps and procedures required.

The AWIPS NCF Contingency Plan shall be exercised once a year, at a minimum.

The AWIPS NCF Contingency Plans shall include:

Purpose

Objectives

Roles and Responsibilities

Requirements

Design of the plan

Develop Documentation for the Contingency Test

Conduct Tests

Document Results

Evaluate Lessons Learned

The AWIPS NCF Contingency Plan shall be provided in Microsoft Word®.

DATA ITEM DESCRIPTION

NUMBER: OM-11

TITLE: AWIPS Government Property List Updates

REVISION: None

DATED: 09 July 2015

1. Description/Purpose

Independently of the formal Government Property Reporting required under FAR

52.245-1—Government Property, the Contractor shall periodically update the listing provided at Attachment J.8 - Government Furnished Property in accordance with contract clause G.11, CAR 1352.245-70—Government Furnished Property (APR 2010), to ensure that it is complete, current, and accurate as of the date of the report.

2. Intended Use

The purpose of the updates is to keep the AWIPS Program Office apprised on a “real time” basis of any changes in the inventory (quantity, location, or composition) of all

Government Property in its possession.

3. Basic Content

Provide complete, current, and accurate updates to the information set forth in Attachment

J.8 - Government Furnished Property, as required. The format is as shown below:

Item

No Description Quantity Delivery Date

Property/Tag

No. (If

Applicable)

The Government Property List Updates shall be provided in Microsoft Word® or

Microsoft Excel®.

DATA ITEM DESCRIPTION

NUMBER: OM-12

TITLE: AWIPS Hardware Matrix

(Available online at: https://vlab.ncep.noaa.gov/web/awips-technical-library/home)

REVISION: None

DATED: 08 July 2015

1. Description/Purpose

Independently of the formal Government Property Reporting required under FAR

52.245-1—Government Property, the Contractor shall periodically update the AWIPS

Hardware Matrix to ensure that the status of all AWIPS hardware supporting Operations &

Maintenance (O&M) and the urgency of refreshment requirements associated with it is complete, current, and accurate, as of the date of the report. (This includes but is not limited to servers, workstations, storage facilities, network components, printers, power supplies, and all ancillary equipment and accessories.)

2. Intended Use

The purpose of the updates is to keep the AWIPS Program Office apprised on a “real time” basis of…