DIU SRR P-spec FAQ (12-10-18)

Q: What will be SRR UAS configuration and flight profile to meet the 30 minute flight time?
A: The SRR UAS should have a 30 minute operational flight time (target) during a mission where it will achieve and hold an altitude of 400 feet and fly in a linear trajectory from origin to 3km out and back. Rest of flight profile can be hovering. Payload configuration should be heaviest configuration to meet other SRR requirements.

Q: What are the requirements to send full motion video from the SRR UAS to a ground control station?
A: The operator of a ground control station should be able to detect a person at 300m standoff distance in daytime and 200m standoff distance in low light or nighttime conditions. Round trip latency from control to UAS to ground control station displayed video should be < 300ms. (target)

Q: Under what conditions should the SRR UAS achieve 3km of operational range?
A: The SRR UAS should achieve a 3km operational range in clear line of sight. (target). Non line of site performance is also a critical operational need.

Q: What is the plan for a government-supplied ground controller to be used in this project?
A: The government will release specifications for a ground controller, known as Tactical Open Government-owned Architecture (TOGA), shortly after any award is made. The ground controller will be capable of operating open-source SW, QGroundControl, for display of video, modifications of parameters, mission planning, and manual control of the SRR UAS. In addition to mandatory control using QGroundControl on TOGA, the SRR UAS may also be controlled using alternative means such as QGroundControl on an Android device or using standalone software/application from the UAS vendor.

Q: What defines situational awareness of people and vehicles at the given ranges?
A: An operator should be able to not only distinguish objects from their respective backgrounds but also be able to recognize the object as a human or a vehicle at a stand-off distance of 300m using an EO camera or 200m using an IR camera. (target)

Q: Who is able to participate in the SRR UAS commercial solutions opening?
A: Any company is allowed to submit their solution brief for a proposed SRR UAS.

Q: How rigid are the posted timelines & what are the expectations of delivery of prototypes?
A: More detailed information regarding schedules, milestones, and deliverables will be provided when the area of interest (AOI) is posted to www.diux.mil.

Q: What is an acceptable performance criteria for being inaudible?
A: The vehicle should be reasonably indistinguishable from background noise of 65dBA while flying overhead at 200ft AGL. (target)

Q: What configuration of IR camera is acceptable?
A: There are a number of configurations possible for the thermal camera. A combined EO/IR camera on a gimbal is acceptable, but, if size/weight constraints require the IR camera to be modular to the platform, that is also acceptable. Ideally the IR camera would move in at least the tilt axis if modular. Ideally operator would have an EO camera option while using the IR camera. (target)

Q: What type of IR camera is acceptable?
A: The IR camera should be sensitive to the “thermal imaging” region (also called LWIR) where passive detection of thermal radiation is observed.

Q: When can companies expect award and what is the program schedule?
A: The notional program schedule assumes an approximate award date in early Q2 of CY19 and an assessment no earlier than Q4 of CY19. The Government reserves the right to alter the program schedule based upon the maturity of proposed solutions and individual company performance throughout the agreement period.

Q: Is a second, separate processor in the architecture necessary to serve as the mission processor or is the partitioning of an existing processor acceptable?
A: Partitioning is acceptable.

Q: Is the following description a correct interpretation of the project?: DIU will acquire 10 off-the-shelf, unmodified Unmanned Aircraft (UA), (referred to as the Alpha model) which will be evaluated by the users. Following field evaluation, these units will be returned to the vendor for upgrade to the next UA configuration (Beta, Charlie, etc.) as integration efforts proceed. This will continue through various “block” upgrades until all modifications are completed.
A: Quantity of alphas/betas is to be determined and will be part of agreement negotiation. Units can be returned to vendor for upgrades or vendor can build up new units as needed.

Q: Considering the recurring user evaluation and feedback, and potential to impact change, will this be a cost-reimbursement type contract?
A: No.

Q: Will users be in a central location or come from various geographically separated units? If the latter, will there be a centralized or a mobile training activity ahead of the user evaluations?
A: Vendors will be expected to provide training support as needed at various geographical locations in support of end user evaluations.

Q: What is driving the packaging constraint of 576in3? Is an alternative, slightly larger packaging solution permissible?
A: Package constraint in the PSPEC is a target as defined in the AOI. Desire is to make system as “rucksack portable” as possible, balanced with other design considerations. Minimizing system size and weight as well as maximizing ease/quickness of utilization are important warfighter considerations.

Q: When will companies be notified if they have been selected for participation in the Phase II Pitch?
A: DIU expects pitch invites to be sent out after Dec. 16th.