OPC Industry Studies RFP_QAs.pdf

OPC Industry Studies Questions / Answers

Question

Question Answer

Please advise an alternative submission method (e.g., DOD Safe) for the Offeror to provide its proposal in the event the electronic copy of the proposal is too large to submit via email (L.10).

There are no alternative submission instructions for this solicitation. E-mail submissions shall not exceed 10 MB.

Section L.5 is updated to reflect the file size limitation.

L.11 requests the Offeror complete SF1449 as part of Volume I. Given L.11 also states that no price shall be included in Volume I, should Offerors leave boxes 23 and 24 blank on SF1449 when submitting?

Section L.11 is revised to remove statement that no price shall be included in Volume I and currently states, "No experience or management data shall be included in the Administrative Volume."

L.11 requests the Offeror submit a Subcontracting Plan as part of Volume I, which includes pricing information, but L.11 also states that no price shall be included in Volume I. How should the Offeror handle this?

Section L.11 is revised to remove statement that no price shall be included in Volume I and currently states, "No experience or management data shall be included in the Administrative Volume."

After reviewing the USCG’s response to Question #70, we understand the 3D model will not be provided to offerors during the development of their proposals in response to the OPC Industry Studies (IS) RFP. Will the USCG provide the 3D model to those contractors that are awarded OPC IS contracts? This will allow the contractors to review the condition of the model and factor the condition into the contractors’ assessments of the efforts to transition from a functional design to a production design. Model reviews against functional design drawings will minimize the risk.

The USCG does not intend to provide 3D model files during Industry Studies.

The RFP states, “RFP, Section G.6. Complete the section with the responsible official, title and address who can receive notice of an improper invoice.” The Offeror noted that Section G.6 does not exist in the RFP. Is the intended section reference for this requirement G.3 Contractor Personnel?

Section L.11, Proposal Volume Instructions, administrative section revised to reflect correct reference from "RFP, Section G.6" to "RFP, Section G.3"

The CDRL due dates (DAISA) for Part 1 deliverables are different in J-1 than what is stated in J-2. For example, J-1 lists 2.2.1.1 as 45 DAISA, while J-2 lists it as 60 DAISA.

Should Offeror assume J-1 are the correct dates and J-2 will be corrected or vice versa?

The dates in J-1 are the correct dates. The dates outlined in J-2's Table 1, Technical Data, are corrected.

Section C.1.3., References 3 and 5 Drawings and files pertaining to References 3 and 5 were provided on disks. These references contain nearly 3,300 files. To aid offeror’s in navigating through the large number of files, will the Government please provide an index of the files/drawings contained within these references?

An index of the files/drawings has been provided to all data custodians in receipt of references.

Offerors are required to complete SF-1449 Blocks 12, 17, 23, 24, and 30 as instructed on the form. Offerors are required to enter unit prices for each Item in Block 23 and the amount (units X unit price) in Block 24. The SF-1449 as provided does not list the Items, or CLINs, in Block 19, the quantities of each item in Block 21, and the units in Block 23. Block 20, Schedule of Supplies/Services includes the language below. Will the OPC Team please advise how offerors should address Blocks 23 and 24? Note, there are not requirements or instructions in the RFP for offerors to complete Section B with their prices for each CLIN

Section L.11, Proposal Volume Instructions, administrative section revised to include "Complete Section B."

Question Answer

The Offeror noted that Section K lists K.5 on Page 59 as REPRESENTATION

REGARDING CERTAIN TELECOMMUNICATIONS AND SURVEILLANCE OR

EQUIPMENT (FAR 52.204–24) (AUG 2019), but on Page 65 there are two provisions identified as K.5, which are K.5 52.227-16, Additional Data Requirements (JUN 1987) and K.5 Representation Regarding Certain Telecommunications And Surveillance Or Equipment (FAR 52.204–24) (Aug 2019) (as listed on Page 59). Should K.5 on Page 59 be listed as Additional Data Requirements (JUN 1987), with Representation Regarding Certain Telecommunications And Surveillance Or Equipment (FAR 52.204–24) (Aug 2019) on Pages 59 and 65 identified as K.6, and ANNUAL REPRESENTATION AND CERTIFICATION (FAR 52.204-8) (JAN 2018) on Pages 59 and 66 identified as K.7?

RFP Section K is updated to reflect correct nomenclature.

Section I, 52.227-14 Rights in Data-General (MAY 2014)-Modified and OPC Industry Day Q&A Question #27. Upon reviewing the modified Rights in Data clause in Section I and Question #27, it is the Offeror’s understanding that the Government’s addition of the definition “Modified Limited rights” in paragraph (a) of the clause, and the language at paragraph (g)(4) of the clause are intended to provide for GPR or rights similar to GPR as prescribed in the DFARS Rights in Technical Data/Computer Software clauses.

Paragraph (a) provides definitions for “Limited rights data” and “Restricted computer software”, which defines which data and software are subject to “Limited rights” and “Restricted rights” respectively. The Offeror noted however that there is no definition for “Modified Limited rights data” to define what data and software are subject to “Modified Limited rights.” Will the Government further modify this clause to include a definition in paragraph (a) for “Modified Limited rights data” to define which data are subject to “Modified Limited rights.” Furthermore, would the Government consider adding definitions for “Modified Restricted rights” and “Modified Restricted software” to separately address computer software that are subject to rights similar to GPR, including an appropriate restrictive markings legend in paragraph (g)?

There is no definition for Modified Limited Rights Data as there is no DFARs equivalent definition for "Government Purpose Rights data." Please see Attachment J-2 for further information regarding Technical Data for this contract.

The Government does not have a CDRL/deliverable requirement for software. If the Offeror is proposing use of and delivery of software, then the Offeror should identify the license rights for that software based on the data rights in 52.227-14.

Volume I does not allow for pricing information, however it requires the Small Business Subcontracting Plan which typically contains pricing data. Please clarify whether Small Business Subcontracting Values are considered Pricing information.

Section L.11 is revised to remove statement that no price shall be included in Volume I and currently states, "No experience or management data shall be included in the Administrative Volume."

For consideration of the ability to seamlessly transition from a 2D Functional Design to a 3D Product Model (as referenced in section L11, p 76), it would be useful to know what (CAD) tool the Functional Design was created in and what format it will be delivered in (same CAD tool format or PDF).

The 2D Functional Design artifacts that are drawings are in AutoCAD 2013 compatible (.dwg) file format.

Question Answer

The deliverable file formats listed do not account for a 3D product model extraction format, such as STEP. Please advise what formats are expected or acceptable to allow the Govt. to visualize the CAD model data for these two spaces.

The deliverable file formats listed do not account for a 3D product model extraction format, such as STEP.

16 The RFP is silent regarding Payment Terms. The Offeror assumes that Payment Terms are subject to negotiation. Please confirm.

Payment terms are not subject to negotiation. Contractors may invoice for services rendered on a monthly fixed-price basis. RFP Section G.4, Request for Payment-Invoicing Procedures, is revised to include montly payment terms.

17 Is there a size limit of the OPC@uscg.mil mailbox? Yes. File size limit is 10 MB.

18 If there is a size limit, would the USCG allow for a test email to ensure the Proposal Volumes will be able to be delivered? Yes.

19 Will the USCG send a read receipt to ensure the Proposal was received by the USCG? Yes.

Some offerors, particularly the incumbent DD & C shipyard as well as those shipyards who were awarded a Phase I Preliminary Design Contract for the OPC, first produced data in connection with the performance of those contracts which data may again be submitted by them in connection with the performance of this contract. As a result such data will not have been first produced in the performance of this contract, and the Government’s presumption that it is entitled to Unlimited Rights is inaccurate. Further, it is highly likely that some of the data previously provided by these shipyards (and their subcontractors) was provided with restricted rights designations that do not grant the Asserted/Desired Rights as requested by the Government in Column 3 of Table 1 Technical Data In Attachment J-2. While the offeror is instructed to provide a cost to grant the asserted/desired rights, it may be impossible for the offeror to provide such rights at any cost, or at a cost that is not cost-prohibitive given the Government’s stated target pricing for this contract.

Can the Government please provide guidance on how such shipyards can submit a compliant proposal within these circumstances?

There is no Column 5 in Attachment J-2. Any reference or instruction to complete Column 5 has been deleted. If the Offeror chooses to propose a license right different than what has been identified in Column 3 by the Government the offeror must provide an explanation for asserting a different license right. Any difference in proposed license rights will be determined in accordance with 52.227-14(a).

Question Answer

If an offeror grants the asserted /desired rights in this contract, do the restrictive rights asserted in the prior contracts continue to apply or does the grant of rights in this contract amend the restrictive rights asserted in the prior contracts?

The only way to amend a contract is through a specific modification to that contract. An action under this contract would not amend a prior contract.

May an offeror revise Table 1 to add Column 5, to add footnotes, references, and/or other explanation or detail in order to address these circumstances without risk of their proposal being deemed non-compliant?

Offeror may include further explanation to address data rights assertions without being deemed non-compliant.

See the modified instructions for J-2. Offerors are required to include an explanation with J-2 when the proposed asserted rights by the offeror differ from those identified in Column 3.

23 The due dates for data items identified in Attachment J-1 differ from those included in "Table 1 Technical Data" on pages 48 and 49. All due dates have been updated via Amendment 0003.

On page 2 of Amendment 000002, should the offeror complete the “PRICE” blanks provided in Section B for CLINs 0001aa through 1001? If so, in which Volume should Section B be included? The RFP does not provide instruction on whether the offeror should complete Section B. However, the RFP states no pricing information shall be included in Volumes I-IV.

Section L.11, Proposal Volume Instructions, administrative section is revised to include "Complete Section B."

On page 2 of Amendment 000002, should the offeror complete the “PRICE” blanks provided in Section B for CLINs 0001aa through 1001? If so, in which Volume should Section B be included? The RFP does not provide instruction on whether the offeror should complete Section B. However, the RFP states no pricing information shall be included in Volumes I-IV.

Section L.11 is revised to remove statement that no price shall be included in Volume I and currently states, "No experience or management data shall be included in the Administrative Volume." Section L.11, Proposal Volume Instructions, administrative section is revised to include "Complete Section B."