SF30_EA133W-15-RP-0044_Amendment_0001.pdf

Except as provided herein, all terms and conditions of the document referenced in item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. Name and Title of Signer (Type or Print) 16A. Name and title of Contracting Officer (Type or Print)

Timothy Wampler

AWIPS Contracting Officer

15B. Contractor/Offeror 15C. Date Signed 16B. United States of America

(Signature of Contracting Officer)

16C. Date Signed

(Signature of person authorized to sign)

NSN 7540-01-152-8070 30-105 STANDARD FORM 30 (REV. 10-83)

PREVIOUS EDITIONS UNUSABLE Prescribed by GSA FAR (48 CFR) 53.243

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

1. Contract ID Code Page of Pages

1 16

2. Amendment/Modification No. 3. Effective Date 4. Requisition/Purchase Req. No. 5. Project No. (if applicable)

0001 AUG 28, 2015 NWWH0000-15-04009

6. Issued By Code AJ930073 7. Administered By (If other than Item 6) Code SEE BLOCK 6

NOAA/EASTERN REGIONAL ACQUISITION DIV

200 GRANBY STREET

8TH FLOOR

NORFOLK, VA 23510

8. Name and Address of Contractor (No., Street, County, and Zip Code) (X) 9A. Amendment of Solicitation No.

X

EA133W-15-RP-0044

9B. Date (See Item 11)

10A. Modification of Contract/Order No.

10B. Date (See Item 13)

Code Facility Code

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X

The above numbered solicitation is amended as set forth in item 14. The hour and date specified for receipt of Offers is extended X is not extended.

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing items 8 and 15, and returning 1 copy of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDG-

MENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT

IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. Accounting and Appropriation Data (if required)

N/A

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACT/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

(x) A. This change order is issued pursuant to: (Specify authority) The changes set forth in item 14 are made in the Contract Order No. in item 10A.

B. The above numbered Contract/Order is modified to reflect the administrative changes (such as changes in paying office, appropriation date, etc.)

Set fourth item 14, pursuant to the authority of FAR 43.103 (b)

C. This supplemental agreement is entered into pursuant to authority of:

D. Other (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, X is required to sign this document and return one (1) copy to the issuing office.

14. Description of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

Amendment 0001 to EA133W-15-RP-0044 (1) Incorporates Questions and Answers and makes changes to (2) Request for Proposal (RFP)

Secion B.4 Schedule of Prices, (3) RFP Section L.6 Commerce Acquisition Regulaiton (CAR) 1352.215-70 Proposal Preperation Paragraph

(b)(1)(ii)(B), (4) RFP Section L.6 Commerce Acquisition Regulaiton (CAR) 1352.215-70 Proposal Preperation Paragraph (b)(2)(i)(C), (5) RFP

Section L.6 Commerce Acquisition Regulaiton (CAR) 1352.215-70 Proposal Preperation Paragraph (b)(1)(iii)(A) Table L.6.1 – AWIPS

Technical Solution Areas, (6) RFP Section L.6 Commerce Acquisition Regulaiton (CAR) 1352.215-70 Proposal Preperation Paragraph

(b)(1)(iii)(B) Table L.6.2 – AWIPS Management Solution Areas, (7) Attachment J.1 - Statement of Objectives (SOO) Section 4.1.8, (8)

Attachment J.1 - Statement of Objectives (SOO) Section 8, Table 1 – Mandatory, Numbers 2, 3, 4, 5, and 7, (9) Attachment J.1 - Statement of

Objectives (SOO) Section 8, Table Table – 2 Mandatory, but subject to adjustment based on the Offeror’s proposed solution, Numbers 2, and

6.

1) EA133W-15-RP-0044 Amendment 0001 incorporates the following Questions and Answers:

Industry Question 1)

Can a current Contractor Performance Assessment Reporting System (CPARS) report on the program take the place of a customer

Reference Data Sheet (Appendix L.3)?

DOC/NOAA Response to Industry Question 1)

No. A CPAR can be submitted in addition to Appendix L.3.

Industry Question 2)

Should Work Breakdown Structure (WBS) through Level VII be interpreted as guidance to bidders, or as an absolute? Suggest that the wording above be changed to: “Offerors shall include a comprehensive WBS and WBS Dictionary that cover all tasks, including operational activities, maintenance activities, and transition activities, down to a level of detail sufficient to accurately describe, plan and estimate the work required (up to Level VII) …”

DOC/NOAA Response to Industry Question 2)

See Request For Proposal (RFP) EA133W-15-RP-0044 - Amendment 0001, Table L.6.2 – AWIPS Management Solution

Areas.

Industry Question 3)

Can resumes be removed from the response page count?

DOC/NOAA Response to Industry Question 3)

Yes. See Request For Proposal (RFP) EA133W-15-RP-0044 - Amendment 0001, Section L.6(b)(2)(i)(D)(6).

Industry Question 4)

Request adding Transition as a WBS Level 1 element or identify under which WBS Level 1 element (Operations and Maintenance, Product Improvement, or Communications) transition activities are to reside.

DOC/NOAA Response to Industry Question 4)

See Request For Proposal (RFP) EA133W-15-RP-0044 - Amendment 0001, Table L.6.2 – AWIPS Management Solution

Areas.

Industry Question 5)

Will the Government remove the WBS and WBS dictionary from the Volume I, Technical Proposal, page count?

DOC/NOAA Response to Industry Question 5)

No.

Industry Question 6)

Since a page is defined as “one sheet of paper with typing on one or both sides”, does this mean there can be up to 400 printed sides?

DOC/NOAA Response to Industry Question 6)

No. See Request For Proposal (RFP) EA133W-15-RP-0044 - Amendment 0001, Section L.6(b)(2)(i)(C)

Industry Question 7)

Is the government looking for our approach on a Program Management Plan (PMP) or the completed PMP as part of our response?

DOC/NOAA Response to Industry Question 7)

A completed Program Management Plan is due with Offeror’s proposal.

Industry Question 8)

When is the PMP due?

DOC/NOAA Response to Industry Question 8)

A completed Program Management Plan is due with Offeror’s proposal.

Industry Question 9)

Can the PMP be removed from the page count?

DOC/NOAA Response to Industry Question 9)

Industry Question 10)

Request for Proposal section H.18 identifies several pieces of information that are not identified in Section L but need to be submitted with the proposal. Please verify that these are to be included in Volume I – Business Proposal.

DOC/NOAA Response to Industry Question 10)

Yes. See Request For Proposal (RFP) EA133W-15-RP-0044 - Amendment 0001, Section L.6 (b)(1)(ii)(B).

Industry Question 11)

Request for Proposal section B.3 states that the contract will begin on “August 15, 2016, or date of contract award, whichever occurs later.” Section L states that the offeror shall stipulate a 120 day acceptance period in its business proposal. Is it the Government’s intention to award this contract within 120 days of proposal submission (i.e., by February 2016) with a start date of August 15, 2016?

DOC/NOAA Response to Industry Question 11)

Yes. The Government anticipates 120 calendar days will be sufficient for either contract award or to go to discussions.

Industry Question 12)

Is not including transition CLIN for Base Period Year 6, Option Period I—Year 2, and Option Period II—Year 2 in Section B.4 correct? Where are phase-out costs to be captured? Request B.4 be updated to reflect Phase-Out costs.

DOC/NOAA Response to Industry Question 12)

See Request For Proposal (RFP) EA133W-15-RP-0044 - Amendment 0001, Section B.4—Contract Line Item Numbers

(CLINs). The Transition-Out CLIN is included in the Base Period Pricing Year Six (CLIN 6004), Option Period I—

Pricing Year Two (CLIN 8004), and Option Period II—Year Pricing Year Two (CLIN 10004).

Industry Question 13)

How would the Government like to see incentive fee obtained from Service Level Agreement (SLA) compliance within a Firm-Fixed

Price (FFP) Contract Line Item Number (CLIN)?

DOC/NOAA Response to Industry Question 13)

The Government would prefer to have any incentive fee associated with the SLA separated from the FFP in the Offeror’s build-up of its pricing.

Industry Question 14)

Does the Government intend to issue a cost plus incentive fee CLIN so that incentive fee can be accrued?

DOC/NOAA Response to Industry Question 14)

See Request for Proposal (RFP) EA133W-15-RP-0044 Amendment 0001, Section B.1, Contract Type. The Government will award task orders as appropriate.

Industry Question 15)

Is the current contractor meeting/exceeding the SLAs?

DOC/NOAA Response to Industry Question 15)

NOAA will not disclose incumbent performance information.

Current Service Level Agreements (SLA’s) can be found on the AWIPS Technical Library.

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

Go to the above link, click on the “Specifications” folder, then click on the “SLAs” folder.

Industry Question 16)

Please confirm that the total price for CLINs x001A should not be included in the CLIN x001 total, even though this is a sub-CLIN.

DOC/NOAA Response to Industry Question 16)

Yes.

Industry Question 17)

Will the Government identify desired access points? i.e. Does the Government desire secure external connectivity to the AWIPS enclave and/or secure intra-AWIPS connectivity between sites?

DOC/NOAA Response to Industry Question 17)

See Request for Proposal (RFP) EA133W-15-RP-0044 Amendment 0001, Attachment J.1 – Statement of Objectives, Section 4.1.8.

Industry Question 18)

Risk associated with using an alternative satellite provider than SES-1 places vendor(s) at a competitive disadvantage to the incumbent. Will the government consider using an estimated lease value for all offeror(s) to level the playing field?

DOC/NOAA Response to Industry Question 18)

Industry Question 19)

Technical Q&A indicated the metrics were posted on the AWIPS Technical Library. Appears to be only the test steps were published and not results. Could the Government please identify the specific location of the published Table 3 reported metrics?

DOC/NOAA Response to Industry Question 19)

This information can be found on the AWIPS Technical Library at:

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

Go to the above link, click on the "Testing" folder, then the "Tests" folder, and click on "Performance Tests Results --

OB14.4.1 v2.xlsx".

Industry Question 20)

Technical Q&A indicated the SLA metrics were posted on the AWIPS Technical Library. Could the Government please identify the specific location of the published SvcBU reported metrics?

DOC/NOAA Response to Industry Question 20) https://vlab.ncep.noaa.gov/web/awips-technical-library/document-library

Current contract does not have explicit SLA for this measure.

Industry Question 21)

Does the Government have Software Line of Code (SLOC) counts for the AWIPS II software? Ideally they would either be by component or for major groups of the software, such as CAVE.

DOC/NOAA Response to Industry Question 21)

The Government does not have SLOC counts for AWIPS II by component.

Industry Question 22)

Graphics and tables are generally more readable when a san serif font is used. Will the government specify a san serif font (such as

Helvetica) for use in graphics and tables?

DOC/NOAA Response to Industry Question 22)

Yes. See Request For Proposal (RFP) EA133W-15-RP-0044 - Amendment 0001, Section L.6(b)(2)(i)(C).

Industry Question 23)

Attachments J.5 – Key Personnel Definitions appears complete already. What information does the government wish offerors to add to it?

DOC/NOAA Response to Industry Question 23)

See Request for Proposal EA133W-15-RP-0044 Amendment 0001 - Section L.6.(b)(2)(i) (D)has been corrected.

2) Request for Proposal (RFP) Secion B.4 Schedule of Prices is updated as follows:

B.4. SCHEDULE OF PRICES

Contractor pricing shall be in accordance with the following Contract Line Item Number (CLIN) structure:

BASE PERIOD: SIX (6) YEARS TOTAL

(To be priced separately by individual contract year)

The Government reserves the right to place orders for FFP CLINS in monthly increments

BASE PERIOD PRICING YEAR ONE

CLIN DESCRIPTION

CLIN

TYPE

QTY

UNIT OF

ISSUE

UNIT

PRICE

AMOUNT

Operations and Maintenance - Includes Hardware and Software

Maintenance and Hardware and Software Refresh.

In accordance with the Statement of Objectives (SOO), attached herein from

August 15, 2016, or date of award whichever occurs later, through twelve

(12) months thereafter.

FFP 12 MONTHS

1001A

Operations and Maintenance - Information Technology Security

Support

In accordance with the Statement of Objectives (SOO), attached herein from

August 15, 2016, or date of award whichever occurs later, through twelve

(12) months thereafter.

FFP 12 MONTHS

Product Improvement

In accordance with the Statement of Objectives (SOO), attached herein.

Priced in accordance with Attachment J.7. - Product Improvement Pricing

Schedule. From August 15, 2016, or date of award whichever occurs later, through twelve (12) months thereafter.

To Be

Determined (TBD) at time of task order award

12 MONTHS

Communications

In accordance with the Statement of Objectives (SOO), attached herein from

August 15, 2016, or date of award whichever occurs later, through twelve

(12) months thereafter.

FFP 12 MONTHS

Transition (Phase-in)

In accordance with the Statement of Objectives (SOO), attached herein, from August 15, 2016, or date of award whichever occurs later, through three (3) months thereafter.

FFP 3 MONTHS

BASE PERIOD PRICING YEAR TWO

FROM EXPIRATION OF BASE PERIOD PRICING YEAR ONE THROUGH TWELVE (12) MONTHS THEREAFTER

The Government reserves the right to place orders for FFP CLINS in monthly increments

CLIN

NO.

DESCRIPTION

CLIN

TYPE

QTY

UNIT OF

ISSUE

UNIT

PRICE

AMOUNT

Operations and Maintenance - Includes Hardware and Software

Maintenance and Hardware and Software Refresh.

In accordance with the Statement of Objectives (SOO), attached herein.

FFP 12 MONTHS

2001A

Operations and Maintenance - Information Technology Security Support

In accordance with the Statement of Objectives (SOO), attached herein.

FFP 12 MONTHS

Product Improvement

In accordance with the Statement of Objectives (SOO), attached herein. Priced in accordance with Attachment J.7. - Product Improvement Pricing Schedule

TBD at time of task order award

12 MONTHS

Communications

In accordance with the Statement of Objectives (SOO), attached herein.

FFP 12 MONTHS

BASE PERIOD PRICING YEAR THREE

FROM EXPIRATION OF BASE PERIOD PRICING YEAR TWO THROUGH TWELVE (12) MONTHS THEREAFTER

The Government reserves the right to place orders for FFP CLINS in monthly increments

CLIN

NO.

DESCRIPTION CLIN TYPE QTY

UNIT OF

ISSUE

UNIT PRICE AMOUNT

Operations and Maintenance - Includes Hardware and Software

Maintenance and Hardware and Software Refresh.

In accordance with the Statement of Objectives (SOO), attached herein.

FFP 12 MONTHS

3001A

Operations and Maintenance - Information Technology Security

Support

In accordance with the Statement of Objectives (SOO), attached herein.

FFP 12 MONTHS

Product Improvement

In accordance with the Statement of Objectives (SOO), attached herein.

Priced in accordance with Attachment J.7. - Product Improvement

Pricing Schedule

TBD at time of task order award

12 MONTHS

Communications

BASE PERIOD PRICING YEAR FOUR

FROM EXPIRATION OF BASE PERIOD PRICING YEAR THREE THROUGH TWELVE (12) MONTHS THEREAFTER

The Government reserves the right to place orders for FFP CLINS in monthly increments

CLIN

NO.

DESCRIPTION FFP QTY

UNIT OF

ISSUE

UNIT

PRICE

AMOUNT

Operations and Maintenance - Includes Hardware and Software

Maintenance and Hardware and Software Refresh.

In accordance with the Statement of Objectives (SOO), attached herein.

FFP 12 MONTHS

4001A

Operations and Maintenance - Information Technology Security

Support

In accordance with the Statement of Objectives (SOO), attached herein.

FFP 12 MONTHS

Product Improvement

In accordance with the Statement of Objectives (SOO), attached herein. Priced in accordance with Attachment J.7. - Product

Improvement Pricing Schedule

TBD at time of task order award

12 MONTHS

Communications

In accordance with the Statement of Objectives (SOO), attached herein.

BASE PERIOD PRICING YEAR FIVE

FROM EXPIRATION OF BASE PERIOD PRICING YEAR FOUR THROUGH TWELVE (12) MONTHS THEREAFTER

The Government reserves the right to place orders for FFP CLINS in monthly increments

CLIN

NO.

DESCRIPTION CLIN TYPE QTY

UNIT OF

ISSUE

UNIT

PRICE

AMOUNT

Operations and Maintenance - Includes Hardware and Software

Maintenance and Hardware and Software Refresh.

In accordance with the Statement of Objectives (SOO), attached herein.

FFP 12 MONTHS

5001A Operations and Maintenance - Information Technology Security

Support

In accordance with the Statement of Objectives (SOO), attached herein.

FFP 12 MONTHS

Product Improvement

In accordance with the Statement of Objectives (SOO), attached herein.

Priced in accordance with Attachment J.7. - Product Improvement

Pricing Schedule

TBD at time of task order award

12 MONTHS

Communications

BASE PERIOD PRICING YEAR SIX

FROM EXPIRATION OF BASE PERIOD PRICING YEAR FIVE THROUGH TWELVE (12) MONTHS THEREAFTER

The Government reserves the right to place orders for FFP CLINS in monthly increments

CLIN

NO.

DESCRIPTION CLIN TYPE QTY

UNIT OF

ISSUE

UNIT

PRICE

AMOUNT

Operations and Maintenance - Includes Hardware and Software

Maintenance and Hardware and Software Refresh.

In accordance with the Statement of Objectives (SOO), attached herein.

FFP 12 MONTHS

6001A Operations and Maintenance - Information Technology Security

Support

In accordance with the Statement of Objectives (SOO), attached herein.

FFP 12 MONTHS

Product Improvement

In accordance with the Statement of Objectives (SOO), attached herein.

Priced in accordance with Attachment J.7. - Product Improvement

Pricing Schedule

TBD at time of task order award

12 MONTHS

6003 Communications

In accordance with the Statement of Objectives (SOO), attached herein.

FFP 12 MONTHS

Transition (Phase-out)

In accordance with the Statement of Objectives (SOO), attached herein.

Option Period I: Two (2) years total

(to be priced separately by individual option year)

OPTION PERIOD I — PRICING YEAR ONE

UPON EXPIRATION OF THE BASE PERIOD THROUGH TWELVE (12) MONTHS THEREAFTER

The Government reserves the right to place orders for FFP CLINS in monthly increments

CLIN NO. DESCRIPTION

CLIN

TYPE

QTY

UNIT OF

ISSUE

UNIT

PRICE

AMOUNT

Operations and Maintenance - Includes Hardware and Software Maintenance and

Hardware and Software Refresh.

In accordance with the Statement of Objectives (SOO), attached herein.

FFP 12 MONTHS

7001A Operations and Maintenance - Information Technology Security Support

In accordance with the Statement of Objectives (SOO), attached herein.

FFP 12 MONTHS

Product Improvement

In accordance with the Statement of Objectives (SOO), attached herein. Priced in accordance with Attachment J.7. - Product Improvement Pricing Schedule

TBD at time of task order award

12 MONTHS

Communications

OPTION PERIOD I — PRICING YEAR TWO

FROM EXPIRATION OF OPTION PERIOD I — PRICING YEAR ONE THROUGH TWELVE (12) MONTHS THEREAFTER

The Government reserves the right to place orders for FFP CLINS in monthly increments

CLIN

NO.

DESCRIPTION

CLIN

TYPE

QTY

UNIT OF

ISSUE

UNIT

PRICE

AMOUNT

Operations and Maintenance - Includes Hardware and Software Maintenance and

Hardware and Software Refresh.

In accordance with the Statement of Objectives (SOO), attached herein.

FFP 12 MONTHS

8001A Operations and Maintenance - Information Technology Security Support

In accordance with the Statement of Objectives (SOO), attached herein.

FFP 12 MONTHS

Product Improvement

In accordance with the Statement of Objectives (SOO), attached herein. Priced in accordance with Attachment J.7. - Product Improvement Pricing Schedule

TBD at time of task order award

12 MONTHS

8003 Communications

In accordance with the Statement of Objectives (SOO), attached herein.

FFP 12 MONTHS

Transition (Phase-out)

Option Period II: Two (2) years total

(to be priced separately by individual option year)

OPTION PERIOD II — PRICING YEAR ONE

FROM EXPIRATION OF OPTION PERIOD I THROUGH TWELVE (12) MONTHS THEREAFTER

The Government reserves the right to place orders for FFP CLINS in monthly increments

CLIN

NO.

DESCRIPTION

CLIN

TYPE

QTY

UNIT OF

ISSUE

UNIT

PRICE

AMOUNT

Operations and Maintenance - Includes Hardware and Software Maintenance and

Hardware and Software Refresh.

In accordance with the Statement of Objectives (SOO), attached herein.

FFP 12 MONTHS

9001A Operations and Maintenance - Information Technology Security Support

In accordance with the Statement of Objectives (SOO), attached herein.

FFP 12 MONTHS

Product Improvement

In accordance with the Statement of Objectives (SOO), attached herein. Priced in accordance with Attachment J.7. - Product Improvement Pricing Schedule

TBD at time of task order award

12 MONTHS

Communications

OPTION PERIOD II — PRICING YEAR TWO

FROM EXPIRATION OF OPTION PERIOD II — PRICING YEAR ONE THROUGH TWELVE (12) MONTHS THEREAFTER

The Government reserves the right to place orders for FFP CLINS in monthly increments

CLIN

NUMBER

DESCRIPTION

CLIN

TYPE

QTY

UNIT OF

ISSUE

UNIT

PRICE

AMOUNT

10001 Operations and Maintenance - Includes Hardware and Software Maintenance and

Hardware and Software Refresh.

In accordance with the Statement of Objectives (SOO), attached herein.

FFP 12 MONTHS

10001A Operations and Maintenance - Information Technology Security Support

In accordance with the Statement of Objectives (SOO), attached herein.

FFP 12 MONTHS

10002

Product Improvement

In accordance with the Statement of Objectives (SOO), attached herein. Priced in accordance with Attachment J.7. - Product Improvement Pricing Schedule

TBD at time of task order award

12 MONTHS

10003 Communications

In accordance with the Statement of Objectives (SOO), attached herein.

FFP 12 MONTHS

10004 Transition (Phase-out)

3) RFP Section L.6 Commerce Acquisition Regulaiton (CAR) 1352.215-70 Proposal Preperation Paragraph (b)(1)(ii)(B) is restated as follows:

(a) Overall Arrangement of Proposal

(1) VOLUME I – BUSINESS PROPOSAL

(i) Volume I - Business Proposal, consists of the actual offer to enter into a contract to perform the desired work. It also includes required representations, certifications, and acknowledgments, if applicable; justifications for noncompetitive proposed subcontracts; identification of technical data to be withheld; and any other required administrative information.

(ii) Format and Content. Volume I - Business Proposal, shall include the following documents (in the order listed):

(A) Proposal Form:

(1) Use of the Form - The Proposal Form (Standard Form 33), is to be executed fully and used as the cover sheet

(or first page) of Volume I – Business Proposal. Include three (3) original signed copies of the form in the original Volume I – Business Proposal.

(2) Acceptance Period - The acceptance period entered on the Proposal Form by the offeror shall not be less than that prescribed in the solicitation (120 calendar days), which shall apply if no other period is offered.

(3) Signature Authority - The person signing the Proposal Form must have the authority to commit the offeror to all of the provisions of the proposal, fully recognizing that the Government has the right, by terms of the

Solicitation, to make an award without discussion if it so elects.

(B) Address any Supply Chain Risk Assessment Information per the instructions in Section H.18. DOC-

PM 2014-03 Supply Chain Risk Assessment Information (MAR 2014).

(C) Request for Proposal Section K “Representations, Certifications and Other Statement of Offerors” completed by the Offeror. Annual Representations and Certifications: Offerors should complete Section K – Representations, Certifications, and the Submission of Other Information via the On-Line System for Awards Management (SAM) website: https://www.sam.gov/portal/public/SAM/

(D) Address any organizational conflict of interest per the instructions in CAR 1352.209-74 Organizational

Conflict of Interest.

(E) (1) A completed copy of Appendix L.2- Accounting System Questionnaire and (2) a completed copy of

Appendix L.5 - Property Management System Questionnaire.

(F) Other documentation identified in Section (A) above. The offeror shall submit one (1) original and three (3) copies of Volume I – Business Proposal, marked as such.

https://www.sam.gov/portal/public/SAM/

4) RFP Section L.6 Commerce Acquisition Regulaiton (CAR) 1352.215-70 Proposal Preperation Paragraph (b)(2)(i)(C) Is restated as follows:

(2) VOLUME II - TECHNICAL PROPOSAL

(i) General

(A) Volume II - Technical Proposal consists of the Offeror's Technical Solution delineating its capabilities and how it intends to perform contract requirements. Volume II - Technical Proposal will be evaluated in accordance with the criteria contained in Section M. The offeror shall submit one (1) original of Volume II – Technical Proposal, marked as such, and five (5) copies and two (2) CD-ROM copies.

(B) In order that the Technical Proposal may be evaluated strictly on the merit of the material submitted, no contractual price information is to be included in Volume II – Technical Proposal. However, the type and quantity of labor and materials is to be included in Volume II - Technical Proposal, without any associated cost information.

(C) Volume II – Technical Proposal shall be prepared on standard white bond paper, 8-1/2 x 11” size, single spaced, with the exception of foldouts. Each page shall contain a header indicating the Offeror’s name and the solicitation number, and a footer indicating the page number. Margins shall measure 1” on the top, bottom, and sides of each page, with the exception of full-page tables and charts. A “page” is defined as a typed page of the proposal document, i.e., one sheet of paper with typing on one side. A “fold” is defined as one part of the page laid over another part of the page. A “foldout” is defined as a page that has been folded to meet the size restriction of 8-1/2” width by 11” height. Foldouts shall fold from left to right (sideways), shall not exceed 8-1/2” width by 11” height as folded, and shall count as one page, provided that they do not exceed three (3) folds. Each fold in excess of the three

(3)—fold limit shall count as an additional page. The page limit for the Volume II – Technical Proposal is two hundred (200) pages. Proposal font type shall be Times New Roman. No substitutions of font type will be allowed, except as expressly identified herein. Proposal font size shall be 12 point. No reduction of font size will be allowed in the proposal. Helvetica 10 point font is to be used for graphics, figures, tables, footnotes and legends. Costly, complex presentations are neither required nor desired. Any pages in excess of two hundred (200) will be removed, unread and returned to the Offeror. Failure of the Offeror to comply with the page limitations, resulting in the excess pages not being evaluated, shall not constitute grounds for a protest. The covers for volumes, tables of contents, indices, title pages, cross reference indices and section dividers shall not be included in the page count if they are inserted solely to provide ease to the reader in locating parts or sections of the proposal.

(D) (1) Completed copies of Tables L.6.1 – AWIPS Technical Solution Areas, L.6.2 – AWIPS Management Solution

Areas, and L.6.4 – AWIPS Small Business Subcontracting Plan and Socioeconomic Goals shall be submitted as part of Volume II – Technical Proposal; these tables do not count towards the Technical Proposal page limitation.

Offerors are required to reference the applicable page(s) of their proposal that respond to the information requested in each table. Offerors may modify the tables to add topics that are not specifically called out in the tables but they may not remove topics. (2) Completed copies of Appendix L.3 - Reference Data Sheet and Appendix L.4 - Relevant

Project Questionnaire shall be submitted as part of Volume II – Technical Proposal. Appendix L.3 - Reference Data

Sheet and Appendix L.4 - Relevant Project Questionnaire will not count towards the Volume II – Technical

Proposal page limitation. Past Performance information will not count towards the Volume II – Technical Proposal page limitation. (3) Offerors response to the Small Business Subcontracting Plan and Socioeconomic Goals will not count towards the Volume II – Technical Proposal page limitation. (4) A completed copy of Attachment J.6. -

Information Technology – Addendum stating the Offerors identification of data rights shall be submitted as part of Volume II – Technical Proposal. Attachment J.6. - Information Technology - Addendum does not count towards the Volume II – Technical Proposal page limitation.

(ii) Format and Content. Volume II - Technical Proposal, shall include the following contents:

(A) Table of Contents

(B) List of Tables and Figures

(C) Summary of Technical Proposal

(D) Technical Proposal

These major headings may be subdivided or supplemented by the offeror as appropriate.

(1) Summary. This section shall provide a summary that addresses each of the technical evaluation factors set out in Section M.

(2) Technical Proposal. The offeror shall submit a technical proposal that is clear, and thoroughly addresses all the requirements in the SOO consistent with Section M of this RFP. The Technical Proposal shall be properly cross-referenced in the matrices provided in tables L.6.1 – AWIPS Technical Solution Areas, L.6.2 – AWIPS

Management Solution Areas, and L.6.4 – AWIPS Small Business Subcontracting Plan and Socioeconomic

Goals of this RFP.

5) RFP Section L.6 Commerce Acquisition Regulaiton (CAR) 1352.215-70 Proposal Preperation Paragraph (b)(1)(iii)(A) Table L.6.1 – AWIPS Technical Solution Areas, A completed copy of Table L.6.1 – AWIPS Technical Solution Areas shall be submitted as part of Volume II – Technical Proposal; the table does not count towards the Technical Proposal page limitation.

Offerors must reference the applicable page(s) of their proposals that respond to the information requested in Table L.6.1 – AWIPS Technical Solution Areas.

Table L.6.1 – AWIPS Technical Solution Areas

VOLUME II - TECHNICAL PROPOSAL

AWIPS TECHNICAL SOLUTION AREAS

Reference Applicable

Page(s) of Offerors

Proposal

Operations and

Maintenance (O&M)

Solution

The O&M Solution shall include, consistent with the SOO, the following:

O&M Solution

1. The Offeror’s solution shall provide necessary support to ensure that system availability and reliability requirements are met, including the procedures for providing preventative and remedial maintenance. Offerors shall recommend solutions that provide continuous identification and implementation of cost saving measures to maintain a stable cost model, especially in relation to increasing the O&M capacity over the life of the contract.

2. The Offeror’s solution shall provide necessary support to manage the AWIPS Network Control Facility (NCF). The solution shall include sufficient detail to describe how the Offeror plans to manage the NCF on a 24/7/365 basis, and address, at minimum, the following:

(a) monitor central interfaces and telecommunication network;

(b) monitor all sites' AWIPS equipment;

(c) use NCF diagnostic capabilities to analyze site and network problems;

(d) operate the AWIPS network help desk;

(e) generate requests and periodic reports on NCF performance;

(f) support software and hardware upgrades and patch distribution; and

(g) support the current NCF centralized archive function.

3. The Offeror’s solution shall detail the quality metrics for providing O&M support throughout the life of the contract, and track all changes to application(s), system architecture, hardware configuration, and troubleshooting efforts through rigorous documentation

4. The Offeror’s solution for providing hardware maintenance, refresh and logistics support services for all installed AWIPS hardware, to meet AWIPS operational availability requirements

O&M Solution 5. The Offeror’s solution for the maintenance of legacy, baseline, and future software development.

Communications

(COMMS) Solution The Communications Solution shall include, consistent with the SOO, the following:

COMMS Solution

1. The Offeror’s solution for Satellite Broadcast Network, point to multi-point distribution. This strategy shall include details on O&M and all logistics necessary to support the Master Ground Station, Backup Master Ground Station, and Site Ground

System equipment.

System Development Life

Cycle (SDLC) Solution The SDLC Solution shall include, consistent with the SOO, the following:

SDLC Solution

1. The Offeror’s solution shall cover all aspects of engineering and evaluation of implementing changes to AWIPS baseline software and hardware solution.

SDLC Solution 2. This Offeror’s solution shall indicate how the Offeror intends to perform integration, test, and deployment of Contractor, Government, and partner developed software.

SDLC Solution 3. The Offeror’s solution shall describe in detail the formal system for testing of the AWIPS software and hardware changes;

configuration management of AWIPS software and hardware; and the software release strategy.

SDLC Solution 4. The Offeror’s solution shall describe the process for providing and tracking maintenance for all AWIPS Commercial-Off-the-Shelf (COTS) and Free and Open Source Software (FOSS), including software licenses and annual software support, as well as for providing vendor assistance, and any applicable vendor software updates, patches, or fixes.

Security Solution The Security Solution shall include, consistent with the SOO, the following:

Security Solution

(General)

1. The Offeror’s solution shall address the quality and comprehensiveness of the security solution, and assesses its ability to meet the security specifications identified in the solicitation. Solutions must be capable of meeting security requirements for a FISMA High-rated system. AWIPS’ present FISMA rating is Confidentiality=Moderate, Integrity=High, Availability=High.

Security Solution

(Adaptability to Policy

Changes)

2. The Offeror’s solution shall include methods of adapting and/or adjusting the security solution in the event that security requirements as defined in section 4.1 of the SOO change during the term of the contract.

Security Solution

(Development Security)

3. The Offeror’s solution shall integrate security requirements into the software development process. This includes identification and management of security requirements through all stages of the development lifecycle (design, implementation, testing, deployment, maintenance).

Security Solution

(External Threat

Management)

4. The Offeror’s solution shall identify methods by which the system will be protected against threats, compromise, or attacks originating from external sources. The Offeror’s solution shall identify techniques used to conduct system monitoring and control and responsiveness associated with an incident.

Security Solution

(Internal Threat

Management)

5. The Offeror’s solution shall identify methods by which the system will be protected against threats, compromise, or attacks originating from internal sources. The Offeror’s solution shall identify techniques used to conduct system monitoring and control and responsiveness associated with an incident.

Security Solution

(Adaptability to Changing

Threat Environment)

6. The Offeror’s solution shall propose methods of monitoring both new and evolving threats to the system and adapting the security solution to permit mitigation of risks created by those threats.

Security Solution (Supply

Chain Risk)

7. The Offeror’s solution shall provide for security requirements in the software and hardware procurement process, including considerations such as country of origin and restrictions on acquisition from sources identified by the U.S.

Government as malicious; and license compliance management Commercial Off the Shelf (COTS) and Free and

Open Source Software (FOSS) must also be managed with respect to country of origin and license restrictions.

Product Improvement

(PI) Solution

The Offeror shall submit a Product Improvement Solution (hardware, software, and communications), to include, consistent with the SOO, the following:

PI Solution

1. This solution shall specifically address solutions to the product improvement objective numbers 4.1.8, 4.1.9, 4.1.10 and

4.1.12 from the AWIPS SOO document dated July 08, 2015.

2. This solution shall take into account the processes and abilities to provide continuous improvement of the AWIPS through system engineering, architecture, and implementation of hardware and software solutions that will enable AWIPS to support the technological evolution and scientific advances associated with the advancement of the NWS mission.

PI Solution 3. This solution shall also include specific methodologies to accommodate emerging requirements over the life of the contract.

4. This solution shall take into account maintaining the Government’s unlimited rights and ownership rights of the

Government a described in Section H.21 as well as the open source nature of the AWIPS software baseline when addressing product improvements.

Representative Task

Order (RTO) The Offeror shall submit a Solution to the Representative Task Order found at Appendix L.1 – Representative Task Order

RTO

1. Offerors shall delineate their understanding of the requirements and propose a solution in sufficient detail to demonstrate that the proposed methodologies will ensure successful delivery of all items and services required. The RTO shall address how the Contractor will conduct the initial steps (engineering assessment of potential solutions) required to address section

4.1.8 of the SOO.

6) RFP Section L.6 Commerce Acquisition Regulaiton (CAR) 1352.215-70 Proposal Preperation Paragraph (b)(1)(iii)(B) Table L.6.2 – AWIPS Management Solution Areas, is restated as follows:

(A) Factor 2 - Management Solution

Offerors shall include a section in their proposal that demonstrates their understanding of the Government’s requirements, and delineate the methodologies that will be used to ensure the quality, timeliness, and cost-effectiveness of all deliverables required under the AWIPS contract. Offerors shall provide resumes of each key personnel proposed. Offerors proposals shall address the functional areas delineated in Table L.6.2 – AWIPS Management Solution Areas. Offerors

Management Solution shall take into account maintaining the Government’s unlimited rights and ownership rights of the Government as described in Section

H.21

A completed copy of Table L.6.2 – AWIPS Management Solution Areas shall be submitted as part of Volume II – Technical Proposal; the table does not count towards the Technical Proposal page limitation. Offerors must reference the applicable page(s) of their proposals that respond to the information requested in Table

L.6.2 – AWIPS Management Solution Areas.

Table L.6.2 – AWIPS Management Solution Areas

VOLUME II: TECHNICAL PROPOSAL

AWIPS MANAGEMENT SOLUTION AREAS

Reference Applicable

Page(s) of Offerors

Proposal

Program

Management Plan

(PMP)

The Program Management Plan shall include, consistent with the SOO, the following:

PMP

1. The Offeror shall include 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, including communication plans. Offerors shall delineate the approaches they plan to utilize to satisfy the requirements of each Contract Line Item Number.

Human Resource

Management Plan

(HRMP)

The Human Resource Management Plan (HRMP) shall include, consistent with the SOO, the following:

HRMP

1. Proposals submitted in response to the AWIPS solicitation shall include a description of all Contractor personnel to be assigned to the AWIPS program, the anticipated level of their dedication to this assignment (i.e. full- or part-time, permanent or temporary) and the methodologies for staff acquisition, scheduling, and retention policies.

2. If offering professional services (as defined by 29 CFR 541), Offers shall submit a Professional Compensation Plan setting forth salaries and fringe benefits proposed for the professional employees who will work under the contract in accordance with FAR Clause 52.222-46 “Evaluation of Compensation for Professional Employees (FEB 1993)”.

Individual compensation disclosure is not required. Submission of general compensation practices often printed in an employee handbook is sufficient.

3. Proposals submitted in response to the AWIPS solicitation shall include a copy of the Offeror’s policy that addresses uncompensated overtime in accordance with Clause 52.237-10 “Identification of Uncompensated Overtime (OCT

1997)”.

Key Personnel The Offeror shall propose Key Personnel that meet the standards found in Attachment J.5 - Key Personnel

Definitions

Key Personnel

1. Offerors shall propose key personnel in accordance CAR 1352.237-75—Key Personnel and Attachment J.5 - Key

Personnel Definitions. Offerors shall provide their key personnel’s proposed responsibilities, the percentage of time that each individual will be committed to the AWIPS project; any other contractual obligations these individuals may have during the course of the AWIPS period of performance; and provide copies of their resumes highlighting all experience, education, and training relevant to this effort. Written requests for waiver of the key personnel proposed by the

Contractor if their qualifications do not meet the minimum qualifications specified in the labor category for which they are being proposed shall also be provided if applicable.

Performance Work

Statement (PWS) and

Work Breakdown

Structure (WBS)

The Performance Work Statement and Work Breakdown Structure shall include, consistent with the SOO, the following:

PWS/WBS 1. Offerors shall include a PWS that is consistent with the AWIPS SOO.

PWS/WBS

2. Offerors shall include a comprehensive WBS and WBS Dictionary that cover all tasks, including operational activities, maintenance activities, and transition activities, down to a level of detail sufficient to accurately describe, plan and estimate the work required, up to Level VII, (in accordance with the WBS diagram dated July

08, 2015 provided in Section J - Work Breakdown Structure, at minimum). Offerors may add additional elements at WBS Level I and II as needed to capture other activities, such as Transition.

Risk Management

Plan (RMP) The Risk Management Plan shall include, consistent with the SOO, the following:

RMP

1. Offerors shall include their methodology for identifying and managing risks and opportunities associated with the

AWIPS program. In addition, the initial risk register shall include a detailed discussion of risks, and opportunities through the life of the AWIPS contract, and the proposed mitigating strategies.

Earned Value

Management Plan

(EVMP)

The Earned Value Management Plan shall include, consistent with the SOO, the following:

EVMP

1. Offerors shall include an Earned Value Management Plan (EVMP) that shall delineate its proposed approach to Earned

Value Management. This shall include an explanation of the application of American National Standards Institute /

Electronic Industries Alliance Standard 748 to monitor and compare actual performance to planned results.

EVMP

2. The EVMP shall explain the process for monitoring the Contractor’s performance under the contract, and determining the need for corrective action. The plan shall provide sufficient tracking, monitoring, and comparison of projected performance objectives to actual results.

Transition Plan The Transition Plan shall include, consistent with the SOO, the following:

Transition Plan

1. Offerors transition plans shall provide a detailed discussion of the methodologies and procedures to be used to minimize disruption of mission-critical services during Phase-In of the AWIPS program, and delineate its start-up requirements.

2. The transition plan shall detail the Offeror’s plans to address staffing, including recruiting, hiring, training, and

Contractor personnel compliance with NOAA’s security requirements, as well as any other special considerations that may affect onboarding or retention. The Plan shall reflect Phase-In and Phase-Out transition periods that are at a maximum three (3) months in length, and sufficiently comprehensive to ensure smooth transition from the incumbent to the awardee, and from the awardee to any successor(s).

3. The transition plan shall also provide details as to the proposed methodology for seamless transition of subcontracted services, logistics, and maintenance activities.

Quality Assurance

Plan (QAP) The Quality Assurance Plan shall include, consistent with the SOO, the following:

QAP

The Offeror's proposed Quality Assurance Plan (QAP) documents the methods used to measure performance of the

Contractor against the objectives in the AWIPS SOO document dated July 08, 2015. Offerors are required to identify performance metrics and positive/negative incentives. These measures will be identified in the Offeror's proposed QAP.

The Offeror shall propose a QAP consisting of a description of the review process, its documentation, methods of internal review, identification of staff position(s) performing the reviews, and the frequency of the reviews, which, when approved by the Government, shall be incorporated into and become part of the AWIPS CDRL document dated July 08, 2015.

The QAP shall contain and address the following areas:

QAP 1. Overall Approach to Quality Assurance. The QAP shall demonstrate the adequacy, relevance, and reasonableness of the

Offerors’s proposed approach, procedures, documentation, and methods for tracking the quality, timeliness, and cost-effectiveness of its performance in relation to the objectives and requirements set forth in the SOO and PWS, including communicating with the Government, handling corrective actions, and implementing improvements.

2. The QAP shall discuss the methods and metrics that will be used to evaluate the reliability, availability, and security of

AWIPS, with respect to its accessibility to the user community 24/7/365, as required by the SOO; and explain how and when these methods/metrics will be updated as the system evolves over the life of the contract.

3. Acceptable Quality Levels (AQLs)—AQLs define the lowest tolerable limit of defect in a product or deficiency in a service.

4. Positive/Negative Performance Incentives—The Offeror shall demonstrate the adequacy, reasonableness, and appropriateness of the proposed incentive and disincentive metrics; their granularity; and the scoring range and weighting factors for each performance requirement as it relates to the accomplishing the project's objectives.

5. Offerors’ QAPs shall comply with the Service Level Agreement documents listed within Attachment J.3 - Contract

Document Requirements List dated July 08, 2015.

7) Attachment J.1 - Statement of Objectives (SOO) Section 4.1.8, is restated as follows:

4.1.8. Develop an implementation plan that reduces the AWIPS hardware footprint such that the proposed solution meets or exceeds the established SLAs in Table – 1 Mandatory and Table – 2 Mandatory but subject to adjustment, below, improves

SvcBU and Continuity of Operations, secures existing remote intra-AWIPS access, drives towards Government initiatives such as the 2010 Federal Data Center Consolidation Initiative (available online at https://cio.gov/wp-content/uploads/downloads/2012/09/FAQ-May-2012-Update-V1.pdf), and reduces system downtime during installations, while minimizing operational risks, data latency, and required up-front investment.

8) Attachment J.1 - Statement of Objectives (SOO) Section 8, Table 1 – Mandatory, Numbers 2, 3, 4, 5, and 7, is restated as follows:

Table 1 - Mandatory

Number Title Definition Acceptable Performance Level

On-Time delivery of Contract

Deliverables without any changes or modifications

Delivery of all contract deliverables on-time and accepted the first time by the Government 100% accepted on-time, first time each month

SBN and Master Ground Station

(MGS) Availability

SBN MGS availability is defined as uninterruptible access to the MGS capability 99.99% per month

3 SBN Data Availability

SBN Data Availability is the measure of the amount of data that is transmitted successfully across the AWIPS SBN.

99.90% per month

4 Average Message Timeliness

Average Message Timeliness is defined as a performance metric to identify timeliness of weather products being delivered from a WFO to NWS customers via the SBN.

99.95% of Priority 1 messages delivered to WFO within ten (10) seconds after message is received at an

NCF Message Handling System

(MHS), logged and time stamped per month.

99.95% of Priority 2 messages delivered to WFO within thirty (30) seconds after message is received at an

NCF MHS, logged and time stamped per month.

99.85% of Priority 3 messages delivered to WFO within sixty (60) seconds after message is received at an

NCF MHS, logged and time stamped per month.

Service Restoration (Response to

Trouble Tickets)

A measure of the time required to restore services to the sites during a time of service interruption.

Level 1 (Sites in Critical Weather

Status): <3 minutes, 95% of the time per month.

Level 2 (Comparable to critical priority; but for sites not in Critical

Weather Status): <10 minutes 95% of the time per month.

System Performance (User

Experience)

Measures the system performance and data latency at the WFOs, RFCs and NCs. Table 3 contains specific performance metrics supporting this SLA.

Meet 98.00% performance objectives or better.

7 Vulnerability Scan to…