DVES_Pre-Solicitation_Conference_Questions.pdf

DVES Pre-Solicitation Questions

1. How will the government assign evaluation credit for solutions that achieve objective requirements?

The Government will assign evaluation credit in accordance with Section M of the RFP, FAR 15.101-2 and 15.3, DFARS 215.300, and AFFARS Mandatory Procedures 5315.3

2. Will the Government make the SRD Appendix B (CONOPS Document) available to industry for review prior to the pre-solicitation conference?

No. The CONOPS document will be released with the final RFP.

3. The final contract option is omitted from the contract document (4000-series CLIN).

Does the Government intend to include?

4000-series CLIN have been removed from the RFP.

4. When should industry plan to see the release of the final RFP?

The final RFP is estimated to be released within 30 days after the completion of the pre-solicitation conference

5. CLIN 0004 references Firm Fixed Price for quantity six (6) kits. Why did the government assign Firm Fixed Price to these 6 kits and Cost type to the prototype kit system (CLIN 0002) given the fact that they are both shown as due 18 Months ARO.

CLIN 0004 is for Group B kit components only, and the Government believes these components should be well-defined and firmly priced. CLINs 0002 and 0003 are for complete kits (Group A and B components), and the Government understands there will be more risk associated with the contents and cost of the Group A kits.

6. Respectfully request clarification as this statement conflicts with FAR requirements.

PWS, section 4.4: “The Government will have Government Purpose License Rights if any proprietary hardware, drawings or data developed at private expense is used.”?

All licensing and proprietary assertions must meet FAR and DFAR requirements.

7. Please describe the existing host aircraft functions of the AN/AAQ-29A FLIR and the current weather radar as referenced in the draft SRD.

Technical documentation detailing the functions of the listed components will be in the technical data package (TDP) to be provided to verified proposers with the release of the RFP.

8. What is the current method of controlling /managing the Embedded GPS/INU (EGI) and describe the system interaction?

The two EGI are controlled by the CDU via the MIL-STD-1553 to push all navigational data to the bus.

9. Air worthiness certification level requirements:

a. Will the DVE imagery be used for SA only? What is the required certification/assurance level for that symbology?

Yes, DVES imagery with be for situational awareness only. There is no requirement for certification.

b. Will the system be required to duplicate the symbology on PFD? What is the required certification/assurance level for that symbology?

The SMFCD is not considered a PFD. There is no requirement for certification.

c. Will the formal RFP include requirement for DO-178C SW certification and DO-254 HW certification?

No.

10. Can the customer provide a description of how the 1 TB data storage will be used?

Specific data storage requirements will be described in the final SRD.

11. Is it possible to receive a sample of data in the DGED format as defined by

DGIWG?

No. DGED is an emerging standard; compatibility with it is not a threshold requirement.

A system that provides an approach for incorporating emerging and future standards in geospatial and obstacle data such as DGED may be considered an objective requirement.

12. Will the customer provide pictures of the HH-60G aircraft systems?

Pictures of the HH-60G and systems were taken by request on 30 May 2018 and were sent to the Pre-Solicitation Conference attendees and will be posted with the TDP for verified proposers with the release of the RFP.

13. Please provide technical data package (specifications for hardware/software, requirements specification, ICD, and implementation guide) to include the list of document in the table below for the follow list of aircraft equipment and any other component or system to which the DVE solution will be required to interface. APN- 239 Radar, MFD, SGU/DSGU, VSDS, FLIR, EGI, FMS

Technical documentation detailing the functions of the listed components will be in the technical data package (TDP) to be provided to verified proposers with the release of the RFP.

14. Paragraph 3.2.4 of the SRD specifies the criteria for detection and recognition as defined by the Johnson criteria. These are based on human detection performance, respectively recognition performance, on 2D imagery. For a 3D sensor data other criteria for detection and recognition have to be established as data can be accumulated over time and scan patterns over time are not as rigid as a camera sensor matrix. These 3D sensor detection and recognition criteria have to consider the beam divergence versus the object extension at the given distance as well as the acceptable accumulation time. Which are acceptable criteria in this sense?

[proposed values are: extension of object > 2 beam diameters in largest dimension for detection and > 5 beam diameters in largest dimension for recognition

a) maximum allowable accumulation time 5 seconds

b) number of hits on object > 5 within accumulation time for detection and > 25 for recognition]

Section 3.2.4 applies to the 3D sensor data as presented to the aircrew in the form of 2D imagery (in accordance with Section 3.3.1). The requirement for the 3D sensor is to collect data (within the time constraints specified in Section 3.2.6.1.2) and to present it (within the latency requirements established in Section 3.9.2) as 2D imagery that allows aircrew to perform detection/recognition tasks as specified in terms of the Johnson criteria.

15. What is meant by the requirements [DVES0190], [DVES0200], [DVES0210] and [DVES0220] (SRD paragraphs 3.2.4.1 – 3.2.4.4) asking for “[…] assessment of obstacles within the […] zone […] from a slant range of XXX feet […]”?

Does this ask for:

• Option 1: “[…] assessment of obstacles within the […] zone […] from a slant range of XXX feet […] to these obstacles” or is the requirement:

• Option 2 “[…] assessment of all obstacles located within the […] zone […] from a slant range of XXX feet […] to the landing point”?

Option 1, as provided by the questioner, is an accurate representation of the intent of the requirement.

16. Paragraph 1.1 b) of the SRD lists an SMFCD. Can the Government please provide the part number of the specific SMFCD?

The Smart Multi Function Color Display (SMFCD) part number is 846HN0001.

17. Paragraph 1.2 of the SRD Talks about DVE providing Advanced Flight Controls on page 2 but paragraph 3.2.1, Functional Isolation from Existing Flight Control Systems, says the “DVES shall be functionally isolated from current HH-60G flight control systems”. Please clarify the requirement for Advanced Flight Controls.

SRD para 1.2 does not say that the USAF DVES will provide Advanced Flight Controls. The statement being referenced was a general DVE statement for an estimated/optimized full DVE solution. The SRD requirements take precedence.

18. What are the SWAP requirements associated with the following systems?

1. SGU/ DGSU AN/ASN-161

2. Color Weather Radar AN/APN-39 or RDR-1600

3. AN/AAQ-29A FLIR

Technical documentation detailing the functions of the listed components will be in the technical data package (TDP) to be provided to verified proposers with the release of the RFP.

19. What is the difference between the Block 152 and Block 162 Aircraft?

During the Operation Loss Replacement (OLR) program, 5 legacy systems were deemed obsolete and were replaced with new systems. The Block 152 aircraft are outfitted with these legacy systems: RDR-1400 Color Weather Radar (CWR), Symbology Generator Unit (SGU), Inter-Communication System (ICS), and AN/ARN-118 Tactical Air Navigation System (TACAN). This new configuration is known as Block 162, and these aircraft are outfitted with a RDR-1600 Color Weather Radar, Digital Symbology Generator Unit (DSGU), Digital Inter-Communication System (DICS), and AN/ARN-153 TACAN.

20. What type of Intercom System (3.2.9.1) is equipped on the aircraft?

An analog Inter-Communication System (ICS) is installed on the Block 152 aircraft, and a Digital ICS is installed on Block 162 aircraft.

21. Is there a preference for Information Assurance (IA) or RMF compliance?

RMF compliance is the standard.

22. The HH-60G SRD, while clear on the need for an active sensor to build a 3D picture of the flying environment (read: LIDAR), is ambiguous on the need for a see-through sensor. SRD Para 3.2.4.1 requirement to "collect process and display imagery...to allow assessment...under clear and DVE conditions" implies the requirement for a see through sensor for imaging through the DVE conditions at range for the initial and subsequent LZ Assessments in subsequent paragraphs. Para 3.2.4 makes it clear that see and remember is adequate to build geo-rectified imagery SA within the dust or snow cloud. Will the government clarify the SRD to remove perceived ambiguity?

The requirement will be clarified in the final SRD.

23. Paragraph 3.2.2 talks about primary flight displays. The HH-60G has 60L-era steam gauges for primary flight reference. Is this paragraph referring to the PFR provided in the SGU VSDS symbology in terms of keeping them functionally isolated? If not please clarify the concern for remaining isolated from these systems.

The Primary Flight References (PFR) will not be affected by DVES, albeit DVES can consume existing PFR data as long as the PFR data remains un-modified.

24. Paragraph 3.2.6 does not include flight conditions (range of Altitudes and airspeeds) within which this latency requirement will be tested and does not define "accurately" in terms of spherical error probable.

The latency requirements are independent of flight conditions. Accuracy in SRD para 3.2.6 will be assessed qualitatively and quantitatively per the approach profiles in the CONOPS.

25. Does the government desire some means to display the resolution of DTED currently being used (0,1,2) such that users can see when they are approaching a boundary of greater or lesser DTED resolution and can compensate tactically for lower resolution A-Priori data in their 3D display?

The technical requirements for DVES are defined in the SRD and RFP.

26. SRD Paragraph 3.2.7.1 Does the government intend to include NGA vertical obstruction data files in the list of types of data? Will the gov't provide a list of expected data types?

The technical requirements for DVES are defined in the SRD and RFP.

27. SRD Para 3.2.8.1 does not mention approach angles, approach initiation speeds, approach initiation range, rate of descent, rates of deceleration. This information is essential to design a system's performance parameters. Will the government provide these as part of the SRD or will vendors derive the data from the described SRD Appendix B - CONOPS?

The Appendix B - CONOPS document will contain this information and will be released with the technical documentation to verified proposers with the release of the RFP.

28. SRD Para 3.3 second to last paragraph. The USAF has nine HH-60G with center mounted weather radar assemblies. Are those aircraft included in the planned 61 aircraft mods? In those aircraft, there will be dimensional constraints for two EGI's on the nose deck with the radar system as installed. Will the Gov't consider installation of either the original Block 152 nose mount or the HH-60W nose mount which both provide more clearance for radar and nose avionics as a design alternative for all HH-60G DVES recipient aircraft? Would that willingness to adopt a center mount for all DVES be included in the final RFP?

The center-mounted CWR aircraft are not planned to be modified with DVES. Other related space requirements and potential DVES integration with or replacement of existing subsystems are clear in the SRD.

29. SRD Paragraph 3.3.7.2. Does this system record maintenance and fault data to the IVHMS or still record it to the Mode/Status/History section of the mission data file?

Please specify in the SRD for more accurate cost estimations

The technical requirements for DVES are defined in the SRD and RFP. Interface with the IVHMS is not required.

30. SRD Para 3.6.2.3, Does the existing AAQ-29 sensor with its de-ice capability meet the moderate icing requirement such that reliance on its imagery for a 3D multi-sensor solution can be counted on in the DVES design? Historically the de-ice function of the AAQ-16 and AAQ-29 series FLIR turrets degrades the FLIR image.

Icing requirements have been refined in the final SRD and are specific to DVES.

31. Para 3.6.2.8, Rain as specified in Table 3-4 will undoubtedly degrade and increase imagery generation latency from any LIDAR in production. Would the government consider loosening the rain requirement to medium or light?

The requirement for performance in rain remains as stated in the SRD. Table 3-4 specifies threshold DVE conditions as aircraft induced brownout and whiteout. All others may be considered objectives.

32. Para 3.7.3.7. In what band of Infrared is the gov't specifying not to increase? Band I/II, Band IV, Both?

This requirement will be removed in the final SRD. Characterization of the DVES IR signature will be a task within the PWS.

33. Para 4.2.4.6, slope estimation will be dependent upon accuracy of EGI boresight in each individual aircraft. Will the government consider specifying the tolerable error budget for determining slope accuracy given this constraint which is out of the vendor's control?

DVES measurement of slope is an objective, not a threshold, for this program.

34. Gov't furnished SMFCD refresh rate is referenced in several places in the SRD but never defined. Please provide that rate for appropriate technical design consideration.

Technical documentation detailing the functions of the legacy systems will be in the technical data package (TDP) to be provided to verified proposers with the release of the RFP.

35. Is it acceptable to have two phase approach for the robust DVE solution, using the see-and remember (Lidar) and actual penetrating sensors through the obscurants which may not have TRL 7 currently?

DVES requirements are defined in the SRD and RFP.

36. Is HH-60G program considering using Integration Cueing Environment (ICE) as a baseline with flexibility of appropriate capability for tailoring the symbology set to meet HH-60G needs? Is it possible to get ICE set as GFE?

Yes, we can provide ICE as-is as GFE post contract award, with no certification and no guarantee of its stage of productionization and all certification is at burden of offeror.

37. Will we receive a copy of the briefing?

Yes, all DVES Pre Solicitation Conference attendees will receive an edited version of the HH-60G 101 briefing. The full HH-60G 101 briefing will be released with the TDP to be provided to verified proposers with the release of the RFP.

38. Do you name the seats in the aircraft?

Yes, the right front seat is the Pilot Crew Position, and the left front seat is the Co- Pilot Crew Position. The right rear seat is the Flight Engineer Crew Position and the left rear seat is the Aerial Gunner Crew Position.

39. Does the HH-60 have the same generators as the Black Hawk? Have they been upgraded?

The H-60G has two 30/45 KVA generators for primary AC power. The auxiliary is a 20/30 KVA generator.

40. Where is the testing lab located?

The HH-60G Software Integration Lab (SIL) is located at Robins AFB, GA.

41. Will all of the aircraft be upgraded?

Currently, the Government plans to modify 85 HH-60G aircraft.

42. How do the Night Vision Goggles (NVGs) change the CONOPS?

NVGs do not change the CONOPS.

43. What software does the lab support?

The HH-60G SIL supports Control Display Unit (CDU), SGU, and DSGU. The SIL has SMFCD support capability, but currently Raytheon retains that function.

44. Can Ethernet video be transmitted to the SMFCD?

The SMFCD is capable of transmitting and receiving over a gigabit Ethernet port.

45. Can FLIR symbology be generated directly on the SMFCD or does it have to go on the CDU?

In FLIR MUX mode, symbology is currently generated by the SGU/DSGU and is directly sent to the SMFCD over the RS-170.

46. How many colors can the SMFCD display?

Technical documentation detailing the functions of the SMFCD will be in the technical data package (TDP) to be provided to verified proposers with the release of the RFP.

47. How much info can be stored on a MDR if one is present? Does image quality need to be degraded to 800X600 or can it be full resolution?

There is currently no Mission Data Recorder capable of storing video/imagery.

48. Does the CDU provide command to the FLIR to initiate mode? How is data transmitted to the FLIR?

Yes, the CDU controls the FLIR MUX in mode via the 1553 bus.

49. Does the SIL modify EGI OFP?

No

50. How is FLIR used during landings?

The FLIR is used in flight path vector mode typically during landing.

51. Do we have a Heads Up Display (HUD)?

No

52. How will the contractor go about doing a risk assessment?

To do a Cyber Security risk assessment the contractor should follow the RMF guidelines.

53. Does DVES have a specified system FOV/FOR?

The DVES specifications are defined in the SRD.

54. Are we going to release the cyber briefing slides?

Yes, the cyber briefing from the Pre Solicitation Conference was sent to conference attendees and will be released in the TDP to be provided to verified proposers with the release of the RFP.

55. Are we expecting the cyber requirements to flow down to DVES

Yes, cyber security requirements can be found in the RFP and the PWS.

56. Will DSGU be a requirement for the SRD?

IAW the PWS integration with Block 152 (SGU) and Block 162 (DSGU) will be required.

57. Is the DSGU on the OLR station installed in your lab?

Yes.

58. Is the intent to put the DVES in the lab?

Yes.

59. Is the SIL updated as part of the new mod programs?

Yes.

60. Is there another HH-60G SIL?

No, the only HH-60G SIL is at Robins AFB.

61. Do contractors typically test in the SIL?

The SIL is available for test support use and data collection and has been used for those purposes in the past.

62. Is the VSDS installed upside down?

It depends on perspective. Seated pilots look back at the VSDS, and installation is designed so that controls correspond to the matching side of the aircraft.

63. Will the second (over-watch) aircraft have a DVES?

Yes.

64. Do you use DTED for approach heights?

No, radar altimeter is the primary source for altitude information on approach.

65. Can you describe distances for approach to the LZ?

Typical tactical approaches begin within ½ nautical mile of the landing zone

66. At what speeds (conditions) does the FLIR automatically switch to ahead mode because a flight-path-vector cannot be determined?

The FLIR does not switch to Ahead mode unless the user commands this mode switch. The specific ground speed limitations are outlined in the TOs; the values provided there conflict with actual system behavior.

Per TO 1H-60(H)G-1-1 and TO 1H-60(H)G-2-11: in Flight Path Vector mode, if the ground speed is less than 15 knots, the FLIR azimuth angle is commanded to zero and the FLIR elevation angle is limited to less than -1.5 degrees. A ground speed of less than 5 knots causes the FLIR elevation angle to become fixed at 1.5 degrees.

(values from TO 1-1 and 2-11)

Per actual system behavior: In Flight Path Vector mode, if the ground speed is less than 15 knots, the FLIR azimuth angle is commanded to zero and the vertical velocity input used for processing is set to zero if vertical velocity is positive (up). A ground speed of less than 5 knots causes the FLIR elevation angle to become fixed at -1.5 degrees (i.e., 1.5 degrees down from aircraft centerline).

67. Question about symbology. Can you talk to the use of imagery versus symbology please?

Both imagery and symbology will be used for situational awareness.

68. Do you fly with goggles/HUD?

Yes, we fly with Night Vision Goggles (NVGs). No, we don’t have a Helmet Mounted Display (HMD) or Heads Up Display (HUD).

69. Do you envision DVES changing the current approach variants/methods?

Unknown at this time.

70. Will maintenance be required in austere environments?

Yes.

71. Is SADL coming out with the PRSA upgrade?

No, SADL remains after the PRSA upgrade.

72. Is there a fielding timeline for the new Block 162 configuration?

Not currently.

73. Can you talk about en route distances and closure rates at which obstacles are expected to be seen?

This information will be provided in the CONOPS.

74. Is there an objective requirement in L&M for enroute DVE detection? Also for landing/takeoff?

Yes, in accordance with the SRD, en route detection will be an objective requirement and landing/ takeoff will be considered a threshold requirement.

75. What level of DTED do you use now?

We use up to DTED level 2.

76. How much time does it take to get from point-to-point in your approach procedure diagram [in the HH-60G 101 slides]?

It depends on the tactical situation.

77. What do you feel about a requirement for heads-up vs. heads-down display for DVE solutions?

The threshold and objective display requirements are found in the SRD.

78. When will the CONOPS be released and via which mechanism?

The CONOPS document and other technical packages will be released with the final RFP utilizing a secure delivery method utilizing FEDBIZOPS.

79. What is the Period of Performance?

Refer to the final RFP.

80. How much funding is allocated to this program?

The program funding portfolio can be found in the FY19 President’s Budget.

81. How is FLIR footage recorded?

FLIR footage is not currently recorded.

82. What agency signs off on air-worthiness for the HH-60G aircraft?

AFLCMC/WIE.

83. What orientations of slopes are aircrew concerned about most?

Sideward and nose down slopes are more critical than nose up. Aircraft nose down slope limit is the most stringent. If other conditions permit and a slope must be accepted, a nose up slope is preferred.

84. What are the locations of PRSA components?

Proposed location of primary PRSA components are illustrated in the HH-60G 101 slides, which will be part of the technical data package.

85. Do you plan to introduce a Bedford scale [to measure pilot workload]?

We may possibly utilized such a scale, but we haven’t made that decision yet.

86. In the SRD, the ground clearance requirement [3.8.2] is described as a worst case scenario of flat tires and fully compressed struts. What is the numerical value associated with this worst case scenario?

The ground clearance requirements will be clarified in the final SRD.

87. In cold temperatures, can warm-up time [requirement in the SRD] be extended?

This requirement will be clarified in the final SRD.

88. Will awardee have access to aircraft before project milestones for test fits, measurements, etc?

Yes, in accordance with the PWS, there are site surveys and “fit checks” available for the awardee.

89. Will credit be given for proposals exceeding the threshold but not meeting the objective requirements?

The Government will assign evaluation credit in accordance with Section M of the RFP, FAR 15.101-2 and 15.3, DFARS 215.300, and AFFARS Mandatory Procedures 5315.3

90. Does MTTR [Mean Time To Repair; SRD paragraph 3.7.2.1] include calibration time?

MTTR requirements will be clarified in the final SRD.

91. For Government-managed software (SGU and CDU OFP), will the Government software team be responsible for integration software changes or is a contract required with the OEM?

Software integration changes are at the discretion of the DVES integration contractor.

92. Can software be submitted earlier for lab testing to minimize aircraft testing?

Yes, the Government is open to that.

93. Does a shorter schedule offer competitive advantage?

While a shorter schedule is acceptable, no credit is being offered for reduced period of performance.

94. What is the ground system used for mission data planning?

Joint Mission Planning System (JMPS). More details will be offered in the

CONOPS.

95. Is it acceptable to replace the color weather radar?

Yes, however any replaced system must retain legacy functions IAW SRD paragraph 3.2.3.

96. Is there any credit given for replacing a legacy system with a higher performance unit?

No, credit will only be given for the factors outlined in Section M of the final RFP.

Any replaced system must retain legacy functions IAW SRD paragraph 3.2.3.

97. Are all the conditions listed in Table 3.4 considered threshold or are some threshold and some objective?

Table 3.4 is color-coded to denote threshold and objective conditions.

98. Does the system need to be TRL 7, or just the individual components?

The system components need to be at TRL 7. It is understood that integration of the system with the HH-60G is currently an unproven concept.

99. Are there vibration data publicly available for the HH-60G?

Vibration requirements are provided in the SRD. Current HH-60G vibration data is not available.

100. Why is sensor fusion excluded in the SRD?

Sensor fusion is not excluded per se, but it is not required given schedule and maturity constraints.

101. Is TRL 7 required at award or after 24 months NRE period?

The system must be TRL 7 or above at the time of the proposal submission.

102. How far along is the mission data server [for the PRSA modification]?

Post-CDR.

103. Where is DSGU in life cycle?

The DSGU has been through Developmental Testing but has not undergone Operational Testing.

104. For multiple sensor solutions, can fusion be included?

This is at the discretion of the contractor.

105. Is it okay for same company to be prime and sub?

There is a limit of 1 proposal per CAGE code as prime offeror.

106. Are Air Force pilots involved with the source selection process?

Yes.

107. Can we share weight info on HH-60W?

The DVES program is for the HH-60G and does not information on the HH-60W.

108. Can a Helmet Mounted Display (HMD) tie into IAHHS? For example, designate an LZ point in space and then IAHHS then “flies” to that point?

SRD 3.2.1 is clear that IAHHS cannot be modified and DVES must be functionally isolated.

109. Can an HMD tie into the FLIR? i.e. be used to designate a point from FLIR video

FLIR usage/modification requirements are clear in the SRD. Additional information may be contained in the TDP to be released with the final RFP.

110. Do the weight threshold and objective requirements take into account legacy systems that are replaced?

Yes, the weight requirement is for the net system weight, including savings from removed/replaced systems. The requirement is firm, and the trade space is clearly defined in the SRD.

111. During fly-over of LZ and marking, where is that point stored, and how? How is this transmitted around and where?

CDU is used to mark and store point, which is either already sent out on the 1553 bus, and if not, it can be put there for other systems (i.e. DVES) to consume. The RadAlt is used for AGL height, during fly-over marking.

112. Data Rights are a problem potentially, since there is no R&D funding but TRL 7 required. For companies who have developed systems in-house under own internal funds, including certifications. Can the Government clarify data rights?

Yes, vendor-funded code and data can be retained by vendor per FAR/DFARS.

Anything created under this DVES contract must be Government Rights, as stated in RFP, PWS, and FAR/DFARS.

113. How do Special Mission Aviators (SMAs) assist with DVE approaches?

SMAs assist in HH-60G DVE approaches by visually scanning out the side and below the aircraft from the nose to the tail, and by providing directive voice commands to the flying pilot to help avoid obstacles and mitigate adverse drift. SMAs also provide descriptive voice advisories of dust cloud development as the aircraft slows and the cloud moves from the tail toward the cockpit. These descriptive calls help pilots to better time their transition to heads down hover cues and avoid disorientation as visual reference with the ground is lost or degraded. SMAs typically have the best view of the ground at the end of the approach as the area directly under the aircraft tends to become clear of dust as the aircraft approaches touchdown, providing the crew with a final opportunity to determine if a safe landing can be made.

114. Would the USAF consider a Helmet Mounted Display only?

The DVES display requirements are defined in the SRD.