N6660418R1436_Amend_0003.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

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)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to respond to questions submitted in response to this solicitation. See page 2 for details.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 18

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 17-Apr-2019

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N6660418R1436

X 9B. DATED (SEE ITEM 11)

22-Mar-2019

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

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 Offer is extended, X is not extended.

Offer 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 copies 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 ACKNOWLEDGMENT 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)

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

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

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 FORTH IN 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, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

17-Apr-2019

CODE

NAVAL UNDERSEA WARFARE CENTER

KAITLIN SIMOES, CODE 0221

CONTRACTS DEPARTMENT

1176 HOWELL STREET

NEWPORT RI 02841-1708

N66604 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N6660418R1436

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The following have been added by full text:

GENERAL INFORMATION

The purpose of Amendment 0003 is to:

1. Answer questions submitted in response to this solicitation. Questions 16 through 28 are answered in this amendment.

2. Revise CLIN 0005 in Section B as detailed below.

3. Revise Provision UW L-2-0001 as detailed below.

4. Revise Provision HQ C-2-0065 as detailed below.

# Question Response

1 Where should the contractor place the Plan for

Obtaining Clearances and the

OCI Mitigation Plan (Pass/Fail requirements)?

The contractor shall include the Pass/Fail requirements identified in Provision UW L-2-0001, Section 2.0 of the solicitation as Volume VI.

2 Clause HQ C-2-0037(e): What is the

Government's intent for application of this clause? Does it apply only to specific tasks under this procurement or extend further in impact to preclude companies from being able to build ships?

The Government's intent for the application of this clause is to ensure a separation of functions and that the Government receives unbiased recommendations.

An example where this clause could apply is if a contractor were to test a prototype that they also developed. The intent of this clause is not to preclude contractors from shipbuilding on other Government contracts.

3 Do we not have to do a cost volume for the hypothetical tasks? On page 108 it says "there is no volume associated with this factor" for

Cost/Price but the earlier table with page counts says that the cost volume has unlimited pages (Page 103).

No, there is no cost volume associated with hypothetical tasks. The only items to be included in the Cost/Price Volume (which is Volume V of the table located at Provision UW L-2-0001 Section

1.3(c)) are the items identified at UW L-2-0001

Section 4.0.

4 We were only planning on submitting task orders for 4.1 and 4.2 however the hypothetical tasking mentions Ship Alterations which is handled in task order 4.3, can we still respond to the hypothetical task and only do work that corresponds to tasks 4.1 and 4.2 (Concept

Design Analysis and Assessment Studies and

Prototype Design, Fabrication, Integration, and

Test)?

Offerors shall not submit proposals for individual sub-sections of Statement of Work (SOW) Section 4.0, but rather for some or all of the six (6) Prototype Topic listed in SOW sub-sections 2.01 through 2.06, and listed again in Provision UW L-2-0001 Section 3.1.

As stated in Provision UW L-2-0001 Section 3.1.1, for each Prototype Topic being proposed, the Offeror shall provide a detailed response for each hypothetical task. The offeror must complete all instructions indicated in UW L-2-0001 Section 3.1.1. Factor 1 –

Hypothetical Tasks.

5 The government provided estimated hours for

CPFF CLINs 0004 and 0006. CLIN 0002 also has Labor and is CPFF but does not have an estimated number of hours. Question: Will the government provide estimated hours for CLIN

The Government will not be providing estimated hours for CLIN 0002. Please note Offerors shall use the Government provided ceiling numbers listed in

Provision UW L-2-0001, paragraph 5, in its pricing proposal.

0002? (Page 99, Note 5)

6 The government did not include NUWC eCRAFT LCATs. Per Volume 1, a Labor

Matrix with LCATs is to be completed.

Question: Can contractors use their companies

LCATs to complete the labor matrix or do we need to use the LCATs listed on the NUWC eCRAFT website? (Page 83, Section J)

Contractors shall use the labor categories listed on the

NUWC eCRAFT website:

https://www.navsea.navy.mil/Home/Warfare-

Centers/NUWC-Newport/Partnerships/Commercial-

Contracts/Labor-Categories/

7 The governments notes that submissions will be made via email. Understand that the government has file size restriction for emails.

Question: If true, what is the email files size restrictions, and can we submit multiple emails with various attachments if the files size is exceeded? (Page 100, para 1.2, Submission

Requirements)

Generally, Government file size restrictions are limited to 10MB per email. The Contractor may submit multiple emails with various attachments if the file size is exceeded. However, page limitations identified in UW L-2-0001 shall be strictly adhered to across multiple attachments associated with the same section.

8 Page 103, para (e) – States, “Offerors shall provide fill-in information for all clauses/provisions that require it.” Question:

What volume should all of the required fill-ins, Representations and Certifications, and other information be contained in and does it count against page count?

Clauses/provisions requiring fill in are not to be submitted as a volume, and as such do not count against the identified page count for any of the volumes; Clauses/Provisions requiring fill-ins shall be submitted as an individual attachment.

9 Page 36, HQ E-2-0015, QUALITY

MANAGEMENT SYSTEM

REQUIREMENTS (NAVSEA) (APR 2017) –

This clause states, “The Contractor shall provide and maintain a quality management system that, as a minimum, adheres to the requirements of ANSI/ISO/ASQ 9001-2015

Quality Management Systems and supplemental requirements imposed by this contract. Question: Please confirm that a

Quality Management System does not need to be provided as part of the proposal, but covered in the Management Plan.

The Quality Management System Requirements identified in Clause HQ E-2-0015 does not require the

Contractor to submit any documentation as part of their proposal for this solicitation.

10 Page 103, Section L, Para. 1.0 –

INSTRUCTIONS FOR THE SUBMISSION

OF PROPOSAL; Subpara. 1.3(c) – Proposal

Format; indicates that offerors are required to submitted their proposals in separate volumes to include a “Volume V”, “Cost/Price Proposal

– Factor 5”. However, Para 4.0 –

COST/PRICE indicates “There is no volume associated with this factor. Compliance with these instructions is mandatory and failure to comply may result in rejection of your proposal. Offerors shall not submit data beyond that required by these instructions.”

Question: Please confirm if the Cost/Price is volume 5 and what it needs to include?

The only items to be included in the Cost/Price

Volume (which is Volume V of the table located at

Provision UW L-2-0001 Section 1.3(c)) are the items identified at UW L-2-0001 Section 4.0. Please also see response to Question #3.

11 If an offeror submits against more hypothetical tasks then they are found acceptable in, will the government award the offeror a contract for the task areas found acceptable or will the

As stated in Provision UW L-2-0001 Section 3.1.1, for each Prototype Topic being proposed, the Offeror shall provide a detailed response for the associated hypothetical task. The offeror must complete all https://www.navsea.navy.mil/Home/Warfare-Centers/NUWC-Newport/Partnerships/Commercial-Contracts/Labor-Categories/ https://www.navsea.navy.mil/Home/Warfare-Centers/NUWC-Newport/Partnerships/Commercial-Contracts/Labor-Categories/ https://www.navsea.navy.mil/Home/Warfare-Centers/NUWC-Newport/Partnerships/Commercial-Contracts/Labor-Categories/ government find the contractor unacceptable in all task areas and not receive an award?

instructions indicated in UW L-2-0001 Section 3.1.1.

Factor 1 – Hypothetical Tasks. If the offeror is proposing for multiple Prototype Topic areas and its proposal for one Prototype Topic area is determined to be Unacceptable, but its proposal for another

Prototype Topic area is determined to be Acceptable, the offeror may receive an award for only the

Prototype Topic area(s) for which it submitted an

Acceptable proposal.

12 Will the government permit the addition of other Subcontractors post-award since we are unsure of the extent and type of work that will be placed on this contract?

The Government will consider the addition of other

Subcontractors post-award, if all requirements for adding a subcontractor are met and approved by the

Government.

13 Does participation in this Prototyping contract create an OCI issue for participation in any follow-on production contracts resulting from a successful prototyping effort?

All OCI or potential OCI issues will be evaluated at time of occurrence. Given there are currently no production plans as of yet for undeveloped prototypes, the Government cannot comment further on whether or not an OCI will exist in the future.

14 RFP states that 1) offeror shall submit a description of previous relevant experience…, and 2) Offerors shall also describe any previous relevant CMMI or equivalent model-based maturity appraisals… These two requirements are part of the overall page count, but the RFP does not state where these sections should be placed in the proposal. Please clarify. (Pg 98, HW L-2-0017(a) and (b)

If the Offeror is proposing on any of the following prototype topics, Payload Launch and Retrieval

Systems (SOW Task 2.1.1), Payload Integration

Systems and Payload Stowage / Handling Equipment

(SOW Task 2.1.2), and Simulators and Electronic

Equipment (SOW Task 2.1.5), the Offeror shall provide an initial Software Development Plan, in accordance with NAVSEA provision HQ L-2-0016 and a description of relevant Software Development experience, in accordance with NAVSEA provision

HQ L-2-0017. Only one submittal is required regardless of the number of prototype topics being proposed. The Software Development Plan shall be submitted as Volume III, Section 1.2 of the proposal.

15 RFP section HQ L-2-0017(b) RFP states that

Offerors shall describe any previous relevant

CMMI or equivalent model-based maturity appraisals performed within the past 24 months. RFP Section M, (2.0)(c)(3) states that offerors will be evaluated on results of any relevant standard model-based process maturity appraisals performed within 36 months. Please clarify whether the time period is 24 or 36 months. 36 months would make the most sense since CMMI appraisals are conducted every 3 years. (pg 98 & 110, HW L-2-0017(b) and

M(2.0)(c)(3))

The Government will evaluate the offerors previous relevant experience in CMMI or equivalent model-based maturity appraisals performed within the past

36 months; Clause HQ L-2-0017 is modified to be consistent with the 36 months stated in Provision UW

M-2-0001 Section 2.0(c)(3).

16 Page 4 and 8, Section B, CLIN 0005 is contradictorily priced as FFP and at Cost between pages 4 and 8. Please update.

CLIN 0005 is changed in Section B from FFP to Cost.

17 Page 101, Section L, 1.3(c). For the required labor matrix, can the two-page limit be utilized by submitting one (1) 11"x17" foldout page?

Yes, one (1) 11”x17” foldout page is acceptable for the labor matrix submittal.

18 Page 101, Section L, 1.3(a). The RFP states no pictures are allowed. Are diagrams, illustrations and drawings still permitted?

Diagrams, illustrations and drawings are permitted in accordance with Provision UW L-2-0001 Section

1.3(a).

19 Page 103, Section L, 1.3(c). SOW task #s in The Software Development Plan note at the bottom of the** note at the end of the table do not align with the numbering of SOW tasks in Section C.

Please update.

Provision UW L-2-0001 Section 1.3(c) and Provision

HQ C-2-0065 are modified to include the correct

Statement of Work Task numbers.

20 Page 105 and 106, General, Small Business

Participation. How should utilization of small businesses for procurement of supplies/materials be applied towards small business participation percentage if the labor matrix accounts for hours and not $ value?

Please see response to question 26.

21 Page 98, HQ L-2-0016 and HQ L-2-0017.

How will offeror’s “or equivalent process” be evaluated towards meeting CMMI requirements? Can a non-CMMI appraised offeror have a CMMI-appraised subcontractor conduct tasks requiring CMMI?

Yes – an offeror may propose a subcontractor to perform the SDP tasking and, therefore, use the subcontractor’s CMMI appraisal to satisfy the requirements of HQ L-2-0017. Please see Provision

UW M-2-0001, Section 2.0(c) for guidance on how the Government shall evaluate the Software

Development Plan.

22 HQ L-2-0016(b) states that offerors shall also submit an SDP rationale (if responding to SOW tasks 2.1.1, 2.1.2, or 2.1.5). It further states that the SDP rationale is subject to the technical proposal page limitation of the solicitation and shall not exceed 3 pages. Section M states that the SDP rationale shall be evaluated as part of

Volume VI Pass/Fail which isn’t identified as part of the technical proposal. Please clarify where in the overall proposal the SDP rationale should be located?

Please see response to question 25.

23 HQ L-2-0017(a) and (b) state that offerors shall

(a) submit a description of previous relevant experience within the past 36 months in developing software of similar size and complexity, and (b) describe any previous relevant CMMI experience performed within the past 36 months. Please clarify where in the overall proposal these sections should be located.

The submissions required by Provision HQ L-2-

0017(a) and (b) shall be submitted with the SDP as part of Volume VI Pass/Fail Requirements. Please see response to question 28 for further details.

24 UW L-2-0001 Section 4.0(b)(1) FCCOM. The last sentence states, “Additional narrative may be submitted as a separate document, if necessary, to describe derivation of labor rates, use of uncompensated overtime pools to which indirect rates are applied, etc.” Question(s):

How do offerors determine if additional narrative if necessary? Is this information required in an unpriced proposal? What content does the term ‘etc.’ include?

The additional narrative noted in UW L-2-0001

Section 4.0(b)(1) is not required for an unpriced proposal; however, a CASB-CMF shall still be required if FCCOM is being proposed.

25 Please confirm the content and page count of

Volume III, Technical Proposal – Factor 3

Management Approach. Volume III shall include the following:

a. Management Approach – 8 pages

b. Senior Technical Resume – 2 pages

c. Software Development Plan, HQ L-2-0016 –

No page limit

i. The SDP shall also include a

The SDP shall be submitted as part of Volume VI

Pass/Fail Requirements and not part of Volume III;

the table located at Provision UW L-2-0001 Section

1.3(c) has been modified to reflect this change. The

SDP Submission consists of four parts, which shall all be submitted as part of Volume VI, and have the following page limitations:

• Software Development Plan (initial submission):

No page limit;

SDP Rationale equivalent to those articulated by CMMI capability level 3 – 3 pages

ii. HQ L-2-0017 – Subject to the technical proposal page limitations of the solicitation

a) Previous relevant experience, within the past 36-months in developing software of the similar size and complexity– no page limit

b) Previous relevant CMMI or equivalent model-based process maturity appraisals performed within the past

36-months – 3 pages

• SDP Rationale: Three (3) page limit;

• Previous relevant SDP experience: No page limit;

•CMMI or equivalent: Three (3) page limit.

26 52.219-9 SMALL BUSINESS

SUBCONTRACTING PLAN (DEVIATION

2018-O0018) (AUG 2018) Offerors are instructed to represent goals expressed in terms of percentages of total planned subcontracting dollars, and Small Business Goals are addressed within each topic response.

Question: Shall the Small Business Individual and Master Subcontracting Plan itself be addressed in terms of intended percentage utilization only (no dollars), and in which volume should the Plan be placed?

Volume II, Technical Proposal – Factor 2 Technical

Capability shall contain the Small Business

Participation submittal outlined in Provision UW L-2-

0001 Section 3.1.2.2, and is separate from the Small

Business Subcontracting Plan identified in Provisions

52.219-9 and HQ L-2-0009. The Small Business

Subcontracting Plan shall be submitted as Volume

VII. The table located at Provision UW L-2-0001

Section 1.3(c) has been modified to reflect this change. As indicated in UW L-2-0001 Section

3.1.2.2(a), “The Offeror shall propose a Small

Business Participation percentage for each Prototype

Topic. A Small Business Offeroror shall indicate the percentage of work performed by themselves, as well as by any Small Business Subcontractors.” The Small

Business Subcontracting Plan identified in Provisions

52.219-9 and HQ L-2-0009 shall also propose in terms of percentages as opposed to dollars.

27 Section I - 52.219-9 and HQ L-2-0009 SMALL

BUSINESS SUBCONTRACTING PLAN

(NAVSEA) (JUN 1999): Offeror shall submit as part of its proposal a written proposed subcontracting plan in accordance with the clause entitled "SMALL BUSINESS

SUBCONTRACTING PLAN" (FAR 52.219-

9). The plan shall include the Congressionally mandated five percent (5%) goal for small disadvantaged business concerns or a detailed explanation as to why the goal cannot be included in the plan. The RFP does not provide guidance as to where in the proposal the SB

Subcontracting Plan should be included.

Should Offerors include the SB Plan in Volume

VI, Pass/Fail?

Please see response to question 26.

28 Section L, 1.0 Instructions for Submission of

Proposal, pg 100. May offerors include a

Cover Page, Table of Contents and Acronym

List outside of government-specified page limitations?

Offerors shall adhere to the two (2) page limitation for the Cover Page indicated in the table of Provision UW

L-2-0001, Section 1.3(c). No pages outside of the

Government specified page limitations shall be accepted.

SECTION B:

1. The Contract Type for CLIN 0005 is changed from Firm Fixed Price (FFP) to Cost.

SECTION C:

1. The Note at the bottom of Provision HQ C-2-0065 SOFTWARE DEVELOPMENT REQUIREMENTS

(NAVSEA) (JUN 2017) is modified to include the correct Statement of Work task numbers associated with the Applicable Prototype Topics.

SECTION L:

1. Provision UW L-2-0001, Section 1.3(c) table is modified as follows:

a. The **Software Development Plan Note at the bottom of the table is modified to include the correct Statement of Work task numbers associated with the Applicable Prototype Topics.

b. The Software Development Plan is moved in the table to be part of the Volume VI, Pass/Fail

Requirements submittal. The Software Development Plan is deleted from Volume III of the table.

c. Volume VII, Small Business Subcontracting Plan has been added to the table. A note associated with this Volume has been added to the bottom of the table.

All other solicitation terms and conditions remain unchanged.

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 0005

The contract type has changed from FFP to COST.

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0005 1 Lot

OTHER DIRECT COSTS

COST

Material and Travel in support of CLIN 0004, stand alone task orders in accordance with SOW Tasks 4.1 & 4.2.

FOB: Destination

PSC CD: AJ14

ESTIMATED COST

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

HQ C-2-0065 SOFTWARE DEVELOPMENT REQUIREMENTS (NAVSEA) (JUN 2017)

(a) The contractor shall define a general Software Development Plan (SDP) appropriate for the computer software effort to be performed under this contract. The SDP shall, at a minimum:

(1) Define the contractor's proposed life cycle model and the processes used as a part of that model. In this context, the term "life cycle model" is as defined in IEEE Std. 12207:2008;

(2) Contain the information defined by ISO/IEC/IEEE 15289:2017, section 7.3 (generic content) and the

Mapping of ISO/IEC 12207:2008 (IEEE Std. 12207:2008) Clauses to Information Items for Each Software Life

Cycle Process in Table 2 of ISO/IEC/IEEE 15289:2017. In all cases, the level of detail shall be sufficient to define all software development processes, activities, and tasks to be conducted;

(3) Identify the specific standards, methods, tools, actions, strategies, and responsibilities associated with development and qualification;

(4) Document all processes applicable to the system to be acquired, including the Primary, Supporting, and

Organizational life cycle processes as defined by IEEE Std. 12207:2008 as appropriate. Such processes shall be equivalent to those articulated by CMMI®;

(5) Include the content defined by all information items listed in Table 2 of ISO/IEC/IEEE 15289:2017, as appropriate for the system and be consistent with the processes proposed by the developers;

(6) Adhere to the characteristics defined in section 6.1 ISO/IEC/IEEE 15289:2017, as appropriate;

(7) Describe the overall life cycle and include primary, supporting, and organizational processes based on the work content of this contract;

(8) Be in accordance with the framework defined in IEEE Std. 12207:2008, including, but not limited to, defining the processes, the activities to be performed as a part of the processes, the tasks which support the activities, and the techniques and tools to be used to perform the tasks;

(9) Contain a level of information sufficient to allow the use of the SDP as the full guidance for the developers. In accordance with 7.3 of ISO/IEC/IEEE 15289:2017, such information shall at a minimum contain, specific standards, methods, tools, actions, reuse strategy, and responsibility associated with the development and qualification of all requirements, including safety and security.

(b) The SDP shall be delivered to the Government for concurrence under CDRL A007 and shall not vary significantly from that proposed to the Government for evaluation for award. The contractor shall follow the

Government concurred with SDP for all computer software to be developed or maintained under this effort. Any changes, modifications, additions or substitutions to the SDP also require prior Government concurrence.

NOTE: If the Offeror is proposing on any of the prototype topics listed below, the Offeror shall provide an initial Software Development Plan, in accordance with NAVSEA provision HQ L-2-0016 and a description of relevant Software Development experience, in accordance with NAVSEA provision HQ L-2-0017. Only one submittal is required regardless of the number of prototype topics being proposed.

Applicable Prototype Topics:

Payload Launch and Retrieval Systems (SOW Task 2.01)

Payload Integration Systems and Payload Stowage / Handling Equipment (SOW Task 2.02)

Simulators and Electronic Equipment (SOW Task 2.05)

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

UW L-2-0001 Instructions to Offerors

NOTES

UW L-2-0001 NOTES TO OFFERORS

1. The Naval Undersea Warfare Center Division, Newport (NUWCDIVNPT) intends to award indefinite-delivery indefinite quantity Multiple Award Contract (s) (MACs) to provide supplies and services as described in Section C, Statement of Work. The resultant contract(s) will also contain provisions for task/delivery orders to be awarded on a firm-fixed- price or cost-plus-fixed-fee basis as determined by the government. The MACs shall have a base ordering period from date of contract award through sixty (60) months after date of award.

2. The procurement for the planned MACs will be executed under full and open competition provisions through the use of competitive proposals as required by 10 U.S.C. 2304. After planned MAC award, all subsequent task and delivery orders will be competed among qualified contractors for the functional area (or areas) applicable to each requirement in accordance with FAR 16.505, unless one of the exceptions to fair opportunity at FAR 16.505(b)(2)(i) applies.

3. ONLY US COMPANIES ARE ELIGIBLE FOR AWARD. United States companies are the only eligible companies for award on this MAC IDIQ. This is due to the on-going requirement for base access in the execution of tasks. In making this determination, the Government considered the requirement for security compliance with the correlating policies of United States Navy Bases and Installations regarding base access by contractors.

4. The cumulative total of all Orders issued under the IDIQ Multiple Award Contract (MAC) among all MAC holders will not exceed the total contract amount of $46,867,283.00, and the services portion will not exceed

137,992 hours.

5. The Government’s best estimate of costs is set forth below. The Government does not guarantee either the amount for each CLIN or the total estimated amount:

CLIN Type Description $ Amount**

0002 CPFF Labor and hardware deliverables for projects under SOW Tasks 4.1 and 4.2

(Sm, Med, Lg tasks)

$23,095,536.00

0003 COST ODCs - Travel in support of CLIN 0002 $86,400.00

0004 CPFF Labor for stand-alone tasks under SOW Tasks 4.1 and 4.2 $1,372,784.00

0005 COST ODCs - Material and travel in support of CLIN 0004 $554,575.00

0006 CPFF Engineering Labor for SOW Tasks 4.3, 4.4 and 4.5 $20,062,888.00

0007 COST ODCs - Material and travel in support of CLIN 0006 $694,100.00

0008 FFP Labor and ODCs for stand-alone tasks under SOW Tasks 4.1 through 4.4 $1,000,000.00

0009 NSP* CDRLs

0010 FFP Data Rights

0011 NSP* Delivery of Contractor Acquired Property to Government Site

TOTAL $46,866,283.00

*Not Separately Priced

** IN SECTION B, OFFERORS ARE TO FILL IN THESE AMOUNTS IN THE RESPECTIVE CLINs

MINIMUM GAURANTEE

CLIN Type Description $ Amount

0001 FFP Post Award Conference $1,000.00

The quantities of labor hours below represent the Government’s current best estimate of the total requirements. The

Government does not guarantee these amounts:

CLIN Hours

0004 6,312

0006 131,680

TOTAL 137,992

6. DFARS Clause 252.211-7003 UNIQUE ITEM IDENTIFIER (UID) shall apply (See RFQ Section I) This clause also requires that UID information must be submitted in WAWF and that a UID tag must be affixed to the item prior to shipping.

7. Industry Submission of Questions. Offerors shall submit questions by 04/19/2019 – 2:00 PM local time.

Questions received after the designated time may not allow sufficient time for the Government to respond. All questions shall be submitted via email.

8. Guaranteed Contract Amount: The Government’s minimum obligation will be satisfied with an initial $1,000

Firm Fixed Price Order to attend a Post Award Conference (CLIN 0001) as described in Post Award Conference

Note C1.

9. Only one contract will be awarded per successful Offeror inclusive of all divisions, subsidiaries, and affiliates under common control.

1.0 INSTRUCTIONS FOR SUBMISSION OF PROPOSALS

1.1 General Information

All questions concerning this procurement, either technical or contractual, must be submitted via email. No direct discussion between the technical representative and prospective Offeror will be conducted. Questions and proposals shall be submitted to the following point of contact:

Name: Kaitlin Simoes

Email: kaitlin.simoes@navy.mil

1.2 Submission Requirements

(a) Each Offeror shall submit its entire proposal electronically. The Government will evaluate each Offeror's understanding of the Government's requirements and ability to perform the work on the basis of its proposal.

Offerors shall provide information and documentation in detail to clearly identify its overall qualifications.

(b) Proposals shall be submitted electronically via email to Kaitlin Simoes (kaitlin.simoes@navy.mil).

Offerors shall comply with the detailed instructions for the format and content of the proposals; proposals that do not comply may be considered unacceptable and may render the Offeror ineligible for award.

1.3 Proposal Format

(a) The proposal shall be submitted in the English language. The narrative material in the proposal shall be prepared in no smaller than 10-point font, single-spaced with no less than a one inch margin on all sides. In the event photo reduction is used for tables, charts, and drawings, their presentation must be clear and legible. No pictures or hyperlinks are allowed.

(b) Proposals and all attachments shall be readable by Microsoft Office or Adobe Acrobat.

(c) Offerors are required to submit their proposals in separate volumes as follows:

Volume

Section Section Title Page Limit

Cover

Letter

Cover Letter 2

I Technical Proposal - Factor 1 Hypothetical Tasks*

1.0 Payload Launch / Retrieval Systems

1.1 Hypothetical Task 4

1.1.1 Labor Matrix 2

mailto:kaitlin.simoes@navy.mil

1.1.2 Lead Person Resume 2

2.0

Payload Integration Systems and Payload Stowage /

Handling Equipment

2.1 Hypothetical Task 4

2.1.1 Labor Matrix 2

2.1.2 Lead Person Resume 2

3.0 Hatches, Trunks, and Closures Equipment

3.1 Hypothetical Task 4

3.1.1 Labor Matrix 2

3.1.2 Lead Person Resume 2

4.0 Payload Encapsulation Systems

4.1 Hypothetical Task 4

4.1.1 Labor Matrix 2

4.1.2 Lead Person Resume 2

5.0 Simulators and Electronic Equipment

5.1 Hypothetical Task 4

5.1.1 Labor Matrix 2

5.1.2 Lead Person Resume 2

6.0 Cables, Coatings and Materials

6.1 Hypothetical Task 4

6.1.1 Labor Matrix 2

6.1.2 Lead Person Resume 2

II Technical Proposal - Factors 2 Technical Capability*

1.0 Payload Launch / Retrieval Systems

1.1 Technical Capability

4 1.1.1 Facilities

1.1.2 Small Business Participation

2.1 Technical Capability

4 2.1.1 Facilities

2.1.2 Small Business Participation

3.0 Hatches, Trunks, and Closures Equipment

3.1 Technical Capability

4 3.1.1 Facilities

3.1.2 Small Business Participation

4.0 Payload Encapsulation Systems

4.1 Technical Capability

4.1.1 Facilities

4.1.2 Small Business Participation

5.0 Simulators and Electronic Equipment

5.1 Technical Capability

4 5.1.1 Facilities

5.1.2 Small Business Participation

6.0 Cables, Coatings and Materials

6.1 Technical Capability

4 6.1.1 Facilities

6.1.2 Small Business Participation

III Technical Proposal - Factor 3 Management Approach

1.0 Management Approach 8

1.1 Senior Technical Representative Resume 2

IV Technical Proposal – Factor 4 Past Performance*

1.0 Payload Launch / Retrieval Systems

1.1 Past Performance 3

2.1 Past Performance 3

3.0 Hatches, Trunks, and Closures Equipment

3.1 Past Performance 3

4.0 Payload Encapsulation Systems

4.1 Past Performance 3

5.0 Simulators and Electronic Equipment

5.1 Past Performance 3

6.0 Cables, Coatings and Materials

6.1 Past Performance 3

V Cost/Price Proposal – Factor 5 No Limit

VI

Pass/Fail Requirements ***

1.0 Software Development Plan ** No Limit

VII Small Business Subcontracting Plan ****

* For each Prototype Topic offerors are not submitting a proposal for, include the following in your technical proposal submission: "Intentionally left blank. Not proposing to this Prototype Topic"

** Software Development Plan: If the Offeror is proposing on any of the following prototype topics, Payload Launch and Retrieval Systems (SOW Task 2.01), Payload Integration Systems and Payload

Stowage / Handling Equipment (SOW Task 2.02), and Simulators and Electronic Equipment (SOW

Task 2.05), the Offeror shall provide an initial Software Development Plan, in accordance with

NAVSEA provision HQ L-2-0016 and a description of relevant Software Development experience, in accordance with NAVSEA provision HQ L-2-0017. Only one submittal is required regardless of the number of prototype topics being proposed.

***Pass/Fail Requirements Page Limitations: See UW L-2-0001, Section 2.0 “Pass/Fail

Requirements” for page limitations.

**** Small Business Subcontracting Plan: See Provisions 52.219-9 and HQ L-2-0009 for submittal requirements. The offeror shall propose in terms of percentages as opposed to dollars.

Important: Offerors shall not include classified material in the volumes.

(d) Offerors shall provide a cover letter with the following information:

(1) Solicitation number;

(2) The name, address, email address, telephone numbers, Cage Code, DUNS Number, and Tax

Identification Number (TIN) of the Offeror;

(3) A statement specifying the unconditional agreement of all terms and conditions;

(4) A statement that the proposal is valid through 180 calendar days from the date specified for receipt of proposals;

(5) Names, titles, telephone numbers, and e-mail addresses of persons authorized to negotiate on the

Offeror’s behalf with the Government in connection with this solicitation;

(6) DCAA and DCMA office points of contact, including branch location, contact name, telephone number, and email address;

(7) Name, title, and signature of a person authorized to sign the proposal;

(8) Identify all enclosures being transmitted as part of its proposal; and,

(9) The Prototype Topic(s) the Offeror is proposing to.

(e) Offerors shall provide fill-in information for all clauses/provisions that require it.

2.0 PASS/FAIL REQUIREMENTS

The Offeror shall submit the following information with its proposal which will be evaluated as a pass or fail:

(a) Plan for Obtaining Clearances:

(1) Personnel Clearances: The Offeror shall provide a plan for obtaining personnel clearances by the time of award, at the required level specified in the attached DD Form 254. The plan shall include confirmation of existing personnel clearances, detail the Offeror’s process for obtaining personnel clearances, and outline the schedule for obtaining any required new personnel clearances. This plan shall not exceed two (2) pages.

(2) Proof of a Facility Clearance: The offeror shall provide proof of a facility clearance at the required level specified in the DD Form 254. A statement that the offeror has a facility clearance is not sufficient proof. If the offeror does not provide proof of a facility clearance at the level required, or confirmation with the Government database determines that the offeror does not have a facility clearance at the required level, the offeror may be determined ineligible for award and no further evaluation of the offeror’s proposal will be performed. There is no page limitation with regard to proof of a facility clearance.

(b) Organizational Conflict of Interest (OCI) Mitigation Plan: In accordance with NAVSEA clauses HQ C-2-

0037 Organizational Conflict of Interest (JUL 2000) and HQ L-2-0005 Notification of Potential Organizational

Conflict(s) of Interest (JUN 1994), and in accordance with the requirements of FAR 9.5, the Offeror shall identify any and all conflicts of interest or potential conflicts of interest related to this solicitation and provide a mitigation plan to address the conflicts or potential conflicts. If no conflict of interest or potential conflict of interest exists, the

Offeror shall provide a statement certifying as such. There is no page limitation for this plan to allow the Offeror to adequately explain any OCI or potential OCI and related mitigations.

3.0 NON-COST/PRICE FACTORS

Offerors shall address each factor and subfactor in the format and sequence identified in the solicitation. Offerors must provide information in sufficient detail to allow the Government to make an assessment of the Offeror’s capability. Proposals that do not contain the information required in the solicitation risk being determined unacceptable.

Offerors may propose one or more of the Prototype Topics. For each Prototype Topic being proposed, Offerors must address each of the below factors and subfactors, with the exception of Factor Three (3).

In the response to the RFP, the Offeror must address the below factors and subfactors.

3.1 TECHNICAL FACTORS

Factor 1 – Hypothetical Task

Factor 2 – Technical Capability

Subfactor A: Facilities

Subfactor B: Small Business Participation

Factor 3 - Management Approach

Factor 4 - Past Performance

There are six (6) Prototype Topics identified in the Statement of Work (SOW). The Prototype Topics are:

1. Payload Launch / Retrieval Systems

2. Payload Stowage / Handling Equipment and Payload Integration Systems

3. Hatches, Trunks, Closures Equipment

4. Payload Encapsulation Systems

5. Simulators and Electronic Equipment

6. Cables, Coatings, and Materials

3.1.1 Factor 1 - Hypothetical Tasks

For each Prototype Topic being proposed, the Offeror shall provide a detailed response for each hypothetical task which demonstrates the Offeror’s understanding of the issue(s) and requirement(s).

Offerors shall include a list of all assumptions for each hypothetical task response.

For each hypothetical task response, the Offeror shall submit a labor matrix and a breakout of any material.

The labor matrix shall include the types of personnel (i.e. labor categories) required and the number of hours per labor category per task (i.e., labor mix) to complete each hypothetical task.

The Offeror shall identify a Lead Person for each hypothetical task response being proposed (e.g. Lead

Engineer, Task Manager). The Offeror shall provide a resume for the Lead Person not to exceed two (2) pages. Resumes shall include: employee name, number of years of professional experience, current position/title/employer, educational history, chronology of professional experience, current level of security clearance. The Offeror shall identify if the proposed Lead Person is not currently an employee of the

Offeror or proposed subcontractor.

1. Payload Launch / Retrieval Systems

The Offeror shall address the process to develop a prototype system to deploy and retrieve a Remotely

Operated Vehicle (ROV) from a submarine’s torpedo tube while underway. The prototype system shall be employed in a performance demonstration at a land-based test facility to assess the system’s operational utility. (SOW 4.1, 4.2 and 4.4) Areas of consideration shall include, at a minimum, the following: system engineering, requirements development / verification, design process decisions, interface requirements, test and evaluation processes, and system safety plans.

2. Payload Integration Systems and Payload Stowage / Handling Equipment

The Offeror shall address the process to develop a prototype system to on-load and off-load rectangular electronics equipment units from a submarine torpedo room. The prototype system shall be employed to on-load an electronic equipment unit during a pier side evolution on a Virginia Class submarine for use during an at-sea demonstration. (SOW 4.1, 4.2, 4.3, and 4.4) Areas of consideration shall include, at a minimum, the following: system engineering, requirements development / verification, design process decisions, interface requirements, test and evaluation processes, submarine temporary alteration processes, submarine installation processes, and system safety plans.

3. Hatches, Trunks, and Closures Equipment

The Offeror shall address the process to install a new penetration and closure on the wall of a large diameter submarine payload tube to allow inboard access to the payload inside. The penetration and closure will be installed on a land-based test facility that would replicate a configuration change that has been implemented on the Virginia Class submarine large diameter tubes. (SOW 4.2, 4.3, and 4.4) Areas of consideration shall include, at a minimum, the following: system engineering, requirements development / verification, design process decisions, interface requirements, test and evaluation processes, submarine alteration processes, and system safety plans.

4. Payload Encapsulation Systems

The Offeror shall address the process to conduct an at-sea demonstration of a prototype system that deploys an unmanned aerial vehicle (UAV) from a submarine’s trash disposal unit while underway. The prototype deployment system has successfully completed experimental testing at a land-based facility and operational testing on a submarine while pier side. Upon successful completion of an operational demonstration while underway, the prototype deployment system will transition to a production level for use on all U.S.

submarines. (SOW 4.3, 4.4, and 4.5) Areas of consideration shall include, at a minimum, the following:

system engineering, test and evaluation processes, submarine temporary alteration processes, submarine installation processes, system safety, acquisition planning, and logistics support.

5. Simulators and Electronic Equipment

The Offeror shall address the process used to develop a prototype compact solid state mass storage device for use with digital data collection from an instrumented test vehicle. The mass storage device shall fit inside a rectangular envelope of 16 inches x 16 inches x 16 inches to allow use of the storage device inside of an instrumented test vehicle. The prototype storage device shall be employed during an operational test on a submarine while pier side to assess the system’s digital data collection capability and storage capacity.

(SOW 4.1, 4.2, 4.3, and 4.4) Areas of consideration shall include, at a minimum, the following: system engineering, requirements development / verification, design process decisions, software design specifications, interface requirements, test and evaluation processes, submarine temporary alteration processes, submarine installation processes, and system safety plans.

6. Cables, Coatings and Materials

The Offeror shall address the process to develop a cable connector that will operate inside the torpedo tube in a water environment. The cable connector will provide the ability for power and communication to be transmitted to a payload deployment system that is located inside a submarine torpedo tube. The prototype cable connector shall be employed in a performance demonstration at a land-based test facility to assess the cable connector’s operational utility. (SOW 4.1, 4.2, and 4.4) Areas of consideration shall include, at a minimum, the following: system engineering, requirements development / verification, design process decisions, interface requirements, test and evaluation processes, and system safety plans.

3.1.2 Factor 2 - Technical Capability

3.1.2.1 Facilities

For each Prototype Topic proposed, the Offeror shall provide a description of the proposed facility(s) (to include manufacturing facilities, test facilities, laboratories, ranges, support craft, etc.…) to be used in completion of work under this contract. The Offeror shall address all requirements of the Statement of

Work that require use of the facilities, but does not require a description of any facilities used for any administrative or clerical work performed under the contract.

3.1.2.2 Small Business Participation (Separate from 52.219-9)

For each Prototype Topic proposed, the Offeror shall address the following:

The offeror shall provide sufficient detail to permit a complete evaluation. This factor applies to every offeror, regardless of size status or locations of working facilities or headquarters. Small Business

Participation shall include the following:

a) The Offeror shall propose a Small Business Participation percentage for each Prototype Topic. A Small

Business Offeror shall indicate the percentage of work performed by themselves, as well as by any Small

Business Subcontractors.

b) The Government’s goal for Small Business Participation percentage for each functional area is 20%.

The Offeror is encouraged to propose a Small Business Participation objective percentage as high as is practicable, as long as the percentage is supported by the related Small Business participation approach outlined in paragraph (c) below. Please note that the Offeror’s proposed Small Business Participation percentage for each functional area shall be incorporated into the Contract upon award.

c) The Offeror shall provide an approach for how they intend to meet the proposed Small Business participation percentage. The Offeror shall provide a rationale that demonstrates that the tasks assigned to the selected Small Businesses are meaningful to the overall success of this Contract. Offeror shall explain the reasons for and advantages of selecting particular Small Business subcontractors.

d) The North American Industry Classification (NAICS) code applicable to the requirements contained within this solicitation is 541330 and the Size Standard is $38,500,000.

3.1.3 Factor 3 – Management Approach

Only one submittal is required regardless of the number of Prototype Topics being proposed. The Offeror shall provide a description of their management approach demonstrating the Offeror’s ability to manage the tasks in the Statement of Work addressing each of the following:

Performance

Schedule

Affordability/Total Ownership Cost (including procedures, methods and controls used to establish baselines and reduction targets)

Quality

Reliability and maintainability

Program protection

Safety

Environmental

Human systems integration

Open system architecture

The Offeror shall include in this description an approach for monitoring progress of the design, including design documentation, design reviews, and Technical Performance Measures. The Offeror shall identify any areas of the management approach applicable to a specific Prototype Topic.

The Offeror shall explain the management of subcontractors to ensure their products are delivered on time and within budget, and are of sufficient quality to enable the Offeror to meet all contractual requirements.

The Offeror shall provide a matrix designating subcontractor assignments. The Offeror shall explain its approach toward subcontracting and how it will achieve the overall objectives of the resultant contract.

This explanation shall include contractual arrangements, qualification requirements, selection process(es), including a process that verifies that subcontractors’ products meet the Offeror’s flow down requirements, contingency plans, quality assurance, software interfaces, and management interactions. If the Offeror is proposing to use a subcontractor to meet a contractual requirement, it must identify the Contractor programmatic risk level and steps to reduce/retire the risk. If applicable, the Offeror shall explain the approach for managing how design information from one subcontractor’s design influences another subcontractor’s design and include this in the matrix designating subcontractor assignments.

The Offeror shall describe the proposed Quality Assurance Program and quality system to ensure the implementation of the requirements. The Offeror's proposed program shall include how quality assurance personnel are integrated into the manufacturing processes.

Senior Technical Representative (STR): Identify the STR designated to manage orders. Include a resume for the STR that shall include: employee name, number of years of professional experience, current position/title/employer, educational history, chronology of professional experience, current level of security clearance. Address the STR's authority, ability to independently commit company resources to performance under the contract, and the STR's line of communication to senior company management.

Describe the STR's previous experience managing similar efforts.

3.1.4 Factor 4 – Past Performance

(1) Past Performance:

(a) The Offeror shall provide a maximum of three (3) past performance references, per Prototype Topic being proposed, if available, that reflect recent relevant experience performed within the last three (3) years of the closing date of the solicitation that demonstrate the ability to handle the scope and breadth of the tasking in the Statement of Work related to the Prototype Topic proposed. Include a discussion on how the references provided are relevant to the work being proposed.