Industry_Day_Q A_FBO_13_Oct_2015.pdf

PDF 224 KB Posted

Attached to
MQ-8C Maritime Search Radar
Solicitation number
N00019-15-PMA266-0029
Issued by

About this file

Industry Day Questions and Answers (Sorted)

View the file

Other files

File Type Posted
Q A_4NOV2015.docx DOCX document
MQ-8C_Maritime_Search_RADAR_Industry_Day_Attendees_09Oct2015.pdf PDF
Industry_Day_Q A_Unsorted_FBO_13_Oct_2015.pdf PDF
WP_CDRLs.pdf PDF
Attachment_5_Manufacturing_Readiness_Level_(MRL)_Users_Guide.xls XLS spreadsheet
RADAR_OEM_RFP_20150923.pdf PDF
TE_CDRLs.pdf PDF
Attachment_9_CPI_Work_Breakdown_Structure_(WBS).xls XLS spreadsheet
LG_CDRLs.pdf PDF
Attachment_3_DD_Form_254_Security_Classification_Specification.pdf PDF
Attachment_1_RADAR_POR_SOW.pdf PDF
Attachment_12_Priced_Bill_of_Material_Data_Item.docx DOCX document
Attachment_4_RADAR_PWBS_Index_Dictionary.xlsx XLSX spreadsheet
Attachment_6_Technology_Readiness_Assessment_(TRA).pdf PDF
CM_CDRLs.pdf PDF
PM_CDRLs.pdf PDF
Attachment_8_DD1921_Cost_Data_Summary_Report.xls XLS spreadsheet
Attachment_7_TRA_Critical_Technology_Element.xlsx XLSX spreadsheet
Attachment_11_CDRL_Submittal_Approval_Rejection_Form.docx DOCX document
Attachment_2_RADAR_POR_Perf_Spec.pdf PDF
SE_CDRLs.pdf PDF
N00019-15-R-4000_MQ-8C_RADAR_Industry_Day_FBO_20150727.pptx PPTX presentation
N00019-15-R-4000_Exhibit_A_DD1423_CDRL_DRAFT_20150717.pdf PDF
N00019-15-R-4000_Att_8_DON_CPI_WBS_ToolV1_01_(12_Aug_2008)_20150717.xls XLS spreadsheet
N00019-15-R-4000_Att_2_PBS_DRAFT_FBO_20150717.docx DOCX document
N00019-15-R-4000_Att_7_DD1921_CDSR_20150717.xls XLS spreadsheet
N00019-15-R-4000_RADAR_OEM_RFP_DRAFT_FBO_20150717.docx DOCX document
N00019-15-R-4000_Att_6_TRA_Guide_2011_20150717.pdf PDF
N00019-15-R-4000_Att_5_MRL_Users_Guide_V12.5.16_20150717.xls XLS spreadsheet
N00019-15-R-4000_Att_4_RADAR_PWBS_Index_Dictionary_20150717.xlsx XLSX spreadsheet
N00019-15-R-4000_Att_1_SOW_DRAFT_FBO_20150717.docx DOCX document
N00019-15-R-4000_Att_3_DD254_For_Bidding_Purposes_Only_20150717.pdf PDF
Registration_Sheet.xlsx XLSX spreadsheet
Show all 33

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Topic Quest # RFP Doc Section/Para Issue Question Government Response

TRL 1 General General How does the Government define TRL6+? Specific TRL guidance will be provided as an attachment in the

Final RFP.

2 General page 59 & 78 MTA m. - TRL Level Confusion What date does the RADAR need to be TRL6+? Prior to Final RFP submission. Note: Critical Technoology

Elements (CTE's) must have been demonstrated in a relevent environment - at a minimum. Bottom line: The government desires a non-developmental system.

3 RFP page 59 & 78 MTA m. - Provide documentation of system current/planned TRL.

TRL shall currently be 6+ Per Attachment 4.

Please clarify the evaluation criteria for System TRL; Is the evaluation criteria based on Hardware only or hardware and software? Does TRL 6+ Include message format?

The TRL-6 determination is relative to the system's identified

Critical Technology Elements (CTE's). This CTE self-assessment for TRL-6 assertion has to be supported/documented in the Final

Proposal submittal. Note: The Government intends to provide a template, as an attachment, for inclusion in the final RFP.

4 RFP page 59 & 78 MTA m. - TRL Level Confusion Is the definition of the TRL-6 at the component or system level? (Example: 95% at TRL 6 + 5% at TRL 3 = TRL

6?)

The TRL-6 determination is relative to the system's identified

Critical Technology Elements (CTE's). This CTE self-assessment for TRL-6 assertion has to be supported/documented in the Final

Proposal submittal. Note: The Government intends to provide a template, as an attachment, for inclusion in the final RFP.

Security / ITAR 5 RFP N/A Will a Security Classification Guide (SCG) be provided? The PMA266 SCG will be provided as GFI in the Formal RFP release, with subsequent updates provided as required.

6 RFP pages 59 & 78 MTA p. - Cybersecurity Detail technical explanation of how our radar complies with these paragraphs contains classified information. Is it acceptable to deliver a classified appendix to the proposal that addresses these paragraphs?

Yes. However, prior coordination with the PCO and/or Contract

Specialist is required.

7 RFP N/A General Which documents in the final RFP will be classified? Radar Specification Appendix

8 RFP N/A General Which documents in the final RFP will be ITAR-restricted?

Government will label any ITAR restricted materials in the Formal

FRP.

9 PBS General Is the government ensuring the "filtering" of ITAR restrictions.

ITAR Filtering will be accomplished by Offerors following the DSP-

5/TAA process.

threshold / objective 10 RFP pages 59-61 and 78-81

A number of the 31 elements comprising the Minimum Technically

Acceptable Subfactor map into paragraphs in the PBS which identify both threshold and objective requirements.

For example, is the government going to apply the TRL

6+ criteria to software related changes such as data formats? Does the Government require all software related changes to be TRL 6+ at the time of proposal submission?

For the MTA evaluation, Objective requirements will not be assessed. For TRL 6+, see response to question above.

11 PBS General Threshold and Objective requirements If Minimum Technical requirements are needed for acceptable bid, are these Threshold only?

Yes.

12 PBS General Threshold and Objective requirements How does Objective get graded when 5 Desired capabilities will drive the technical rating. The 5 desired elements are different from the objective requirements?

Government assumed both sentences were intended to be questions. The overall technical rating is based on successfully meeting all MTA requirements. The results of the Desired

Technical Subfactor will then drive the overall technical rating for the proposal.

13 PBS General The use of "Objective" and "Threshold" was not consistent. The PBS will be updated in the Final RFP.

14 General General Is there any value to exceeding threshold objectives? For the MTA, there is no "extra credit" for exceeding the threshold requirement. In the Desired Technical Subfactor, additional credit will be awarded based on exceeding Threshold requirements.

Admin 15 PBS 3.2.10.1.1.10 ISAR Strip? Typographical error - various paras impacted. Government requirement is for SAR Spot/Strip, and ISAR modes relative to this anomaly. PBS will be updated prior to final release.

16 PBS 3.2.12 Ground Moving Target Indicator Mode title paragraph 3.2.12 lists

GMTI as an objective capability, yet subparagraphs 3.2.12.1 &

3.2.12.2 are threshold requirements. Paragraph 2.1 of the RFP does not list GMTI as "Minimum Technically Acceptable Subfactor" requiring a POC basis. Paragraph 2.2 of the RFP lists GMTI as a desired or objective capability.

Can the Navy verify the GMTI Mode is an MQ-8C objective capability?

GMTI is an objective requirement.

17 PBS

Verification

Matrix

3.2.2.1 The table states that "The Radar System shall be capable of a surveillance field of view (FOV) of ±90 degrees in azimuth from the nose of the MQ-8C". The written section of the specification calls for

±120 degrees

Will the Navy clarify which requirement applies in the formal RFP?

Typographical error. The FOV will be corrected in the final RFP.

18 PBS

Verification

Matrix

3.2.2.2 The table states that the "Radar System shall be capable of a surveillance field of view (FOV) of -15 degrees to +5 degrees in elevation relative to the horizon (or as limited in by the airframe obstructions)". The written section of the specification calls for -18 degrees to 0 degrees.

Will the Navy clarify which requirement applies in the formal RFP?

Typographical error. The FOV will be corrected in the final RFP.

19 PBS

Verification

Matrix

3.2.4.3 The table does not provide a required time limit for the radar to transition from search to ISAR and from ISAR to search. The written portion of the specification requires the transition not exceed 450 msec.

Will the Navy clarify which requirement applies in the formal RFP?

Typographical error. The Government will add 450 msec.

20 PBS

Verification

Matrix

3.2.14.4 The Table calls for elevation scan capability of ±20 degrees, paragraph Table 4-1, 3.2.4.3 calls for -15 to + 5 and the written paragraph 3.2.4.3 calls for -18 to +0.

Will the Navy clarify which requirement applies in the formal RFP?

Typographical error. The Radar elevation scan will be corrected in the final RFP. Currently, -18 to 0 is correct, with the

Government considering replacing "0" with "+5".

21 PBS

Verification

Matrix

3.3.2.10 The table requires the 'Radar System require not more than 1,000

Watts', but the written paragraph 3.3.2.10 allows the radar to use

'not more than 1500 watts'.

Will the Navy clarify which requirement applies in the formal RFP?

Typographical error. Radar System power requirement is <1500 watts.

22 PBS

Verification

Matrix

3.2.10.1.1.6 "D" only The Government concurs with "D only". PBS will be updated prior to final release.

23 PBS

Verification

Matrix

3.2.10.1.1.7 "D" only The Government concurs with "D only". PBS will be updated prior to final release.

24 PBS Appendix A What is the expectation for Future Upgrades? Does the government expect pricing on the upgrade or information on the ability to incorporate these future upgrades?

Typographical error. Note: There are no future upgrades wrt this offer. (See RFP technical criteria including desired elements.)

PBS will be updated prior to final release.

25 PBS Appendix A Should Future Upgrades be priced? Typographical error. Note: There are no future upgrades wrt this offer. (See RFP technical criteria including desired elements.)

PBS will be updated prior to final release.

growth / future 26 PBS General Multi-mode Radar criteria was not specified in the DRAFT RFP. The PBS will be updated in the Final RFP.

27 PBS General Radar Growth criteria was not specified in the DRAFT RFP. The PBS will be updated in the Final RFP.

28 PBS 3.2.14 Airborne Collision Avoidance is listed as a future upgrade however the requirement is in the body of the PBS.

Why is it called out on Page 30 paragraph 3.2.14? Is paragraph 3.2.14 requirement inherent in the multimode radar and part of the base program? Please clarify.

Airborne Collision Avoidance is an "Objective" requirement.

29 PBS 3.2.15 Should an IFF interrogator be quoted as an option? The Government has afforded Industry great flexibility in the RFP to determine its' optimal performance and price solution.

30 General General Is Identification Friend or Foe (IFF) Mode 5 a requirement?

No.

SWaP 31 General General What is the goal of the Size, Weight, and Power (SwaP) requirement?

The goal is to minimize total Radar System package size and provide maximum flexibility for mounting options.

32 PBS General Is the Radome 30 pounds or is the full Radar system 30 pounds?

The maximum weight for the total radar system is 200 pounds.

The Government assumption for radome weight (not part of this solicitation) does not exceed 50 pounds.

33 PBS General Does the weight requirement include racks for the Radar

System?

No, racks are not included in the weight criteria.

34 PBS General Is there additional Size, Weight, and Power (SWaP) considerations available upon incorporation of

"desired" elements? (Note: Interrogators wt is potentially problematic, etc)

There is no additional SWaP consideration for additional components. Offerors must show that any additional modes can be met within the PBS SWaP requirements.

Installation 35 General General Can the Radar System be assumed to be mountable in the nose?

Yes, as long as the weight mounted in the nose is less than 46 lbs, inclusive of any radome(s).

36 RFP General Where will the Radar be mounted/located? Location will be determined during a execution of a subsequent contract.

37 General General MQ-8C Radar Installation Location. Is the Radar OEM required to make platform radar integration assumptions to meet intended Radar performance requirements?

No. The Government accepts the integrated Radar performance risk imposed by the MQ-8C integration uncertainty. Radar performance will be evaluated on the Radar integrated WRA's and will be exclusive of the platform and Radome.

38 PBS 3.11.2.1 The specification does not provide form factor constraints for the

WRA's to determine if they fit as is or have to be modified.

Will the Navy provide WRA size/form factor constraints in the specification?

No. General Radar System size and weight requirements have been specified for this procurement. Note: Government is accepting this risk. For Desired SubFactor A, Gov will evaluate only against WRAs that must be mounted externally.

39 PBS 3.11.2.2 Paragraph 3.11.2.2 provides the exterior dimensions of a belly mount configuration that can be used in estimating antenna size. There are no guidelines provided for a nose-mount.

Will the Navy provide size and location constraints in the forward section of the MQ-8C for the nose mount configuration so that an antenna size can be determined.

No. The Volume requirements which have been provided in the

RFP are the largest external SWaP which can be accommodated on the MQ-8C.

40 RFP General External Volume Requirements Is there any latitude in the external volume dimensions provided in the RFP?

No. The Volume requirements which have been provided in the

RFP are the largest external SWaP which can be accommodated on the MQ-8C.

41 PBS 3.11.2.2 Would the Government consider mounting the top of the antenna inside the fuselage (approximately 10” inside the fuselage would be required) as meeting the

Go/No-Go Criteria? Alternatively, would Government consider modifying the requirement to less than 18”?

Requirement 3.11.2.2 can not be modified, however other installation locations are possible.

42 PBS 3.2.2.1 Does the [T] vs [O] requirement imply that either a nose antenna or a centerline antenna is acceptable with centerline preferred?

The Government's intent is to have a uniform search volume.

43 PBS 3.3.3 Several pedestal options exist for a Belly Mount installation. The best option will depend on the space available inside the aircraft for the pedestal E-Box.

Will the Navy provide the installation constraints within the cabin for the Belly Mount installation?

Location will be determined during a execution of a subsequent contract.

44 PBS 3.11.2.1 WRA's are attached to mounting frames with various style mounting trays, locking devices air flow requirements and connector locations for maintenance. The specification provides no information or requirements on WRA installation requirements.

Will the Navy provide of a description of the AV radar mounting frames/ rack along with installation mounting requirements and constraints in the specification?

Location will be determined during a execution of a subsequent contract.

OSI 45 PBS 3.2.4.7.1 What mechanism is to select the output format? The Government envisions that this control will be provided via the Resource Manager (RM) and the Minotaur application.

46 PBS 3.2.4.7.2 At the output of the radar or inside the TCS? Inside the TCS. The Government envisions that this control will be provided via the Resource Manager (RM) and the Minotaur application.

47 PBS 3.2.5.4 Who Supplies the Database (DB)? Are there requirements for the unpopulated DB structure?

Target database is GFI, and may be included as a Minotaur function.

48 PBS 3.2.10.1.1.5.1 Why the radar? Where will the Air Vehicle ID information come from?

This is a Minotaur function and will not be a OEM requirement.

49 PBS 3.2.10.1.1.13

3.2.10.1.1.14

3.2.10.1.1.15

3.2.10.1.1.16

3.2.10.1.1.18

Several Specification requirements address radar sensor planning. Can the Navy confirm that the radar will be required to interface with an existing TCS RPP?

Yes, and likely handled by the Minotaur application.

50 PBS 3.2.10.1.1.20 Ship Air Upgrade - SAU 07000 interface is not called out in the documents?

The SAU-07000 is part of the GFI. This item will not be allocated to the RADAR.

51 PBS 3.2.11.1.2.1 Is this user selectable or what is the decision that decides which data to provide?

User-selectable. The Government envisions the Resource

Manager (RM) will provide a service request most likely via the

Minotaur application.

52 General General The intended use of the PMA290 Minotaur Software Application is unclear.

What is the intended path forward regarding the

Minotaur Software Application.

The governments' intention is that during subsequent radar control contracting actions, that the Small Business Innovative

Research (SBIR) resource manager, and classification aids be transitioned via NAVAIR PMA290E Minotaur software integration.

Interfaces 53 RFP N/A Is the operator control software Government-owned, and will it be provided as GFE to the contractor?

Operator control software is not Gov owned and will not be provided as GFE. However, Gov will provide a digital ICD and anticipates contracts between the Prime Integrator, Radar OEM, and Ground Station Contractor.

54 RFP N/A Similarly, does the Government intend to have one software baseline for both the MQ-8B and MQ-8C? If so, will the PIU software and message formatting be available to the Contractor?

The Government will have one baseline for both MQ-8C and MQ-

8B. Internal software discovery will determine aircraft variant and distribute messages accordingly. A Digital ICD will be provided to Contractor.

55 PBS 3.2.9.2,

3.2.11.2.2, 3.2.11.3.2

Will the Navy provide the model of the AV INS/GPS, installation location, and interface requirements?

INS/GPS equipment data can be provided upon contract award.

The Government presumes that the Radar interface is independent of INS/GPS type (Open Architecture).

56 PBS 3.2.10.1.1.7 What interface does the SDL use? Will it come through the PIU?

All the interfaces will be provided as GFI.

57 PBS 3.2.10.1.1.20 Part of radar scope of work? Yes, in that the Radar System shall provide the required interface functionality.

58 PBS 3.3.4 Please clarify if the interface to the Aircraft INS via PIU over 1553 or Ethernet, or some other network.

INS/GPS equipment data can be provided upon contract award.

The Government presumes that the Radar interface is independent of INS/GPS type (Open Architecture).

59 General General What is the Radar Interface definition/requirements? This data will be provided as GFI in the Formal RFP.

60 General General Is the MQ-8C PIU interface going to be GFI in the Formal

RFP?

This data will be provided as GFI in the Formal RFP.

File details come from the government source that posted it. Updated .