UASBVLOS Bidders Response Form Final.docx
DOCX document 226 KB Posted
- Solicitation number
- BD-24-1030-CPO1-CPO1-101747
- Issued by
- Suffolk County, Massachusetts
About this file
This document is a Respondents Response Form for the "Uncrewed Aircraft Systems (UAS), Integration & Program Support for Beyond Visual Line of Sight (BVLOS) Operations" contract opportunity issued by the Massachusetts Department of Transportation (MassDOT). The response form outlines the mandatory and preferred characteristics for the UAS system, including requirements for the uncrewed aircraft, ground control system, command and control link, and payload capabilities. Key mandatory specifications include compliance with Part 107 weight limits, FCC-approved C2 link, Standard Remote ID, VTOL capability, and an electro-optical payload. Preferred characteristics cover areas such as certification status, BVLOS experience, maintenance, training, and additional system specifications like encryption, endurance, and sensor integration.
The response form also requests additional information on UAS, ground control, detect and avoid, payload, mission planning, flight manual, security, limitations, and command and control specifications. Respondents must provide contact information, business references, and confirm their ability to provide the required hardware, software, training, and other services to safely operate the UAS system. This contract opportunity is open to qualified vendors who can meet the technical and operational requirements outlined in the response form.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| How to Create_a_Quote~3.pdf | ||
| UASGS_Consultant Madatory Form.pdf | ||
| UASBVLOS PromptPaymentDiscountForm.doc | DOC document | |
| standard-contract form watermark~1.docx | DOCX document | |
| Amended RFR Uncrewed Aircraft Systems Integration, & Program Support 5.9.2024~1.docx | DOCX document | |
| Intent to Award Notification~8.docx | DOCX document | |
| EPP Form to post.xlsx | XLSX spreadsheet | |
| RFR Uncrewed Aircraft Systems Integration, & Program Support_04182024.docx | DOCX document | |
| UAS MOA.docx | DOCX document | |
| UASGS RRF Submission Checklist~1.docx | DOCX document | |
| Q&A Answers~1.xlsx | XLSX spreadsheet |
Show all 11
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
Uncrewed Aircraft Systems (UAS), Integration & Program Support for Beyond Visual Line of Sight (BVLOS) Operations
RESPONDENTS RESPONSE FORM
All Respondents must complete and return this Attachment with their response in order to be considered responsive. Completing every section of this document fully is mandatory unless instructions for specific sections or questions state otherwise.
For your convenience, areas requiring data entry have been highlighted. Nevertheless, Respondents must read all the forms to ensure the accuracy and completeness of their responses.
Company Contact Information
| Company Information |
| Use this column for the answer |
Company Name
Street address, city, state, zip
Phone Number
Total number of years the principal(s) or company has been in business
Website
| Identification and Description of Key Personnel |
| Identify an individual to have primary responsibility for contact and communications with MassDOT |
Name, Title
Phone number
Section 2.2 - Respondents Response Form- Information Requested MassDOT has provided a list of key characteristics or information (mandatory characteristics indicated by a “SHALL” statement) as well as additional characteristics or information (preferred characteristics indicated by a “SHOULD” statement) that the respondent must address relative to the operational scenarios indicated above. The respondent should include any additional information not explicitly requested that may address requirements associated with specific operational scenarios (additional information) that “MAY” address specific mandatory or preferred characteristics MassDOT has identified.
| 2.3 Performance Specifications/Standards |
| Yes/No |
| 1 |
| Respondents SHALL include: All hardware and software required to operate the UAS to include: |
| a. |
| At least one and up to two uncrewed aircraft (UA) and ground control systems (GCS) |
| |_| |
| b. |
| Any power systems and peripherals (e.g., battery, battery systems, chargers, etc.) |
| c. |
| Carrying case and other accessories for transport |
| d. |
| Any additional accessories needed for routine operations (e.g., cables, spare parts, etc.) |
| 2 |
| Initial system Purchase, Setup, and Integration |
| |_| |
| 3 |
| Training, Maintenance, and other services necessary to safely operate the UAS and associated systems |
| |_| |
| 4 |
| All mandatory characteristics and information as set forth in Section 3.3.1. |
| |_| |
2.3.1 Mandatory Characteristics & Information The following specifications sets forth the key characteristics (mandatory characteristics) of the uncrewed aircraft system (UAS), including the uncrewed aircraft (UA), ground control system (GCS) and all command and control (C2) link system(s):
| A. |
| The UAS at full takeoff configuration (i.e., with payload and any batteries) SHALL comply with 14 CFR Part 107 weight limitations. |
| |_| |
| B. |
| The Respondent SHALL provide a Federal Communication Commission (FCC)-approved integrated command and control (C2) link system(s) to send real-time telemetry and pilot commands between the UA and GCS and SHALL provide FCC identification (FCC ID) of chosen C2 link system(s). |
| |_| |
| C. |
| The Respondent SHALL provide the following information regarding the C2 link system(s): a. Manufacturer, type, and brand - b. Link architecture including wireless provider, frequency(ies), and priority information. |
| |_| |
| D. |
| The C2 link system(s) SHALL support two or more means of connectivity between the GCS and UA. |
| |_| |
| E. |
| The UAS SHALL meet Standard Remote ID requirements, as defined by the FAA. |
| |_| |
| F. |
| The UA flight duration and the C2 link system(s) SHALL support a flight of at least 10 nautical miles (NM). |
| |_| |
| G. |
| The UA SHALL include a vertical take-off and landing (VTOL) capability. |
| |_| |
| H. |
| The UA SHALL be able to operate up to at least 400 feet altitude above ground level (AGL). |
| |_| |
| I. |
| The UA SHALL have anti-collision lighting viewable at a distance of at least 1 nautical mile (NM). |
| |_| |
| J |
| The Respondent SHALL provide an electro-optical (EO) payload. |
| |_| |
| K. |
| UA payload capability SHALL allow for integration of multiple sensor types. |
| |_| |
| L. |
| The Respondent SHALL enter into a Memorandum of Agreement (MOA) in substantially the same form as set out in Appendix 5 regarding collaboration for BVOS UAS Operations in the following areas: Certification & Regulatory Compliance; Use case integration; In-the-field system testing and flight data collection to support FAA waiver application materials; Detect and Avoid system integration |
| |_| |
2.3.2 Preferred Characteristics & Specifications - 2.3.2.1 Preferred Program Characteristics The following information related to the Respondent’s ability to provide program support and integration services should be provided:
| A. |
| Certification and Regulatory Compliance The aircraft SHOULD have, or be in the process of obtaining, an FAA type and airworthiness certificate. The respondent SHOULD provide: (a.) Type certification (TC) status, project timeline, and any other relevant information related to the TC process. (b.) Summary of real flight test data and results related to certification or FAA means of compliance for operations over people. ,(c) Summary of results (data) and analysis of real-world flight tests done to validate claimed performance and reliability. |
| |_| |
| B. |
| Experience and Qualifications The Respondent SHOULD have at least 1 year of previous experience related to BVLOS operations; more experience is preferred. The Respondent SHOULD provide: (a.) Summary of previous experience related to BVLOS operations independently and/or while participating with BVLOS stakeholders as a team member. (b.) Summary of historical flight data including any history flying under BVLOS waivers or other advanced operations (c) Summary of previous waivers, exemptions, or component certifications obtained (d.) Summary of certification of hardware (e.g., transponder), if applicable (e.) Summary of experience integrating subcomponent such as payload sensors or Detect and Avoid (DAA) capabilities |
| |_| |
| C. |
| Maintenance The respondent SHOULD have established maintenance documentation: (a.) Original equipment manufacturer (OEM) maintenance program, documents, and/or continued airworthiness documentation. (b.) Description of technical support services that would be provided to MassDOT in the event of a technical issue with the UAS (e.g., loaner aircraft, replacement parts, and in-person or remote aircraft service). |
| |_| |
| D. |
| Training The respondent SHOULD have a documented training program(s) to support BVLOS flight: (a.) Summary of documented training program documents specific to the UAS. (b.) List of manuals and summary of procedures necessary for BVLOS operations. (c.) Description of on-site training plan including number of MassDOT personnel who will be trained and number of training sessions/days. |
| |_| |
2.3.2.2 Preferred System Specifications The Respondent should provide a description as to whether and how their system meets the following preferred system-level characteristics
| A. |
| The C2 link system(s) SHOULD NOT utilize ISM Band or other unlicensed frequencies for BVLOS operations (Note: ISM Band or other unlicensed frequencies may be used for VLOS portions of a flight, for example during takeoff and landing). |
| |_| |
| B. |
| The C2 link system(s) ground-to-air and air-to-ground signals SHOULD be encrypted and authenticated. |
| |_| |
| C. |
| The UAS SHOULD be able to operate for at least 40 NM at cruise speed. |
| |_| |
| D. |
| The UAS SHOULD be able to operate at 400 to 3,000 feet altitude above ground level (AGL). |
| |_| |
| E. |
| The UAS SHOULD be able to be carried in its transporting equipment and to be set-up and broken down in the field by two people. (a.) The respondent SHOULD provide size/weight/dimensions including the airframe dimensions and physical aspects. (b.) The respondent SHOULD provide size/dimensions of the transporting equipment (e.g., case) and weight of the entire system when packed for transportation (c.) The respondent SHOULD provide estimate time to set-up and to breakdown the system in the field and how many people are required to perform the set-up and breakdown. |
| |_| |
| F. |
| The aircraft payload capability SHOULD support integration of infrared (IR) sensors or multi-spectral sensors such as Micasense Altum Multispectral, Slantrange 4P, or similar sensors, and LIDAR sensors such as the Phoenix miniRanger-LITE, or similar sensors. |
| |_| |
| G. |
| The UAS SHOULD have a demonstrated geospatial accuracy correction system, such as Real Time Kinematics (RTK). |
| |_| |
| H. |
| The UAS SHOULD be capable of integrating a detect and avoid (DAA) capability to deconflict with crewed aircraft. (a.) The respondent SHOULD specify an architecture approach for DAA integration. (b.) The respondent SHOULD specify the standards (e.g., ASTM or RTCA), if any, being followed for the DAA approach. |
| |_| |
2.3.2.3 Preferred Component Specifications The Respondent should provide a description as to whether and how their system meets the following preferred component characteristics:
| A. |
| The aircraft SHOULD include assisted human-in-the-loop or fully autonomous takeoff and landing configurations. |
| |_| |
| B. |
| The aircraft SHOULD contain anti-collision lighting visible from three (3) statute miles or more with a flash rate sufficient to avoid collision. |
| |_| |
| C. |
| The EO payload SHOULD be capable of 1 cm at 200’ spatial resolution ground sampling distance (GSD). |
| |_| |
| D. |
| The EO payload SHOULD be capable of greater than 60 degree field of view (FOV). |
| |_| |
| E. |
| The aircraft payload SHOULD have the ability to support real-time streaming of payload data such as high-resolution imagery or video |
| |_| |
| F. |
| The ground control station (GCS) display SHOULD be capable of displaying the following information in real time: a. Position - b. Altitude - c. Airspeed - d. Vertical speed - e. Ground speed - f. Global Positioning System (GPS) or Guidance, Navigation, and Control (GNC) location - g. GPS or GNC strength and reliability - h. Payload health - i. Operational air traffic (Cooperative / Non-Cooperative w/ Sensor) - j. Wind speed and direction |
| |_| |
| G. |
| The GCS SHOULD be provided with appropriate autopilot/mission planning software. |
| |_| |
| H. |
| The GCS SHOULD provide near real-time (NRT) or real-time telemetry to the remote pilot in command. |
| |_| |
| I. |
| The UAS SHOULD have a demonstrated lost link capability with documented procedures. |
| |_| |
| J. |
| The UAS SHOULD include geofencing and have a return-to-home/return-to-land capability along the preplanned flight, along with documented procedures. |
| |_| |
| K. |
| The UAS SHOULD be able to store and export flight telemetry and payload data for analysis. |
| |_| |
2.3.3 Additional Information
MassDOT requests that the following information is provided (as an attachment, figures/diagrams, or technical descriptions) as additional system information to evaluate SHALL/SHOULD requirements.
| A. |
| UAS Specifications |
a. Manufacturer including the company and relevant information related to the UAS subcomponents/system
b. Powerplant including approved type of fuels and/or batteries.
c. Generators or electrical equipment to power payload and other technology, electrical load, and electrical diagram
d. Aircraft landing and takeoff configurations including known performance numbers.
e. Aircraft landing and takeoff hardware including appropriate diagrams and information for each component necessary to launch and recover the aircraft.
f. Table of maximum, minimum, and normal operating ranges for various speeds given the aircraft configuration including cruise/stall speed
g. Any information related to operations over human beings and operation at night compliance (14 CFR Part 107.39 Subpart D and 14 CFR Part 107.29)
h. Component and system maintenance intervals and compliance with continued airworthiness of aircraft
| B. |
| Ground Control Station Specifications |
a. GCS interface including pictures indicating compliance with mandatory characteristics.
b. All available autopilots and mission planning software (e.g., Site Scan or DroneDeploy) compatible with GCS including associated performance or limitations.
c. Information related to airspace and operational situational awareness for cooperative and non-cooperative aircraft, including description on how the RPIC is alerted to possible conflicts with crewed aircraft.
| C. |
| Detect and Avoid (DAA) Specifications: |
a. Describe any existing DAA sensors or solutions or ability to detect and deconflict with crewed aircraft in the vicinity b. Describe any BVLOS waivers obtained using existing DAA solutions
| D. |
| Payload Specifications |
a. Provide a list of OEM or other sensors that the UAS can readily integrate with, including (if applicable) the sensors’ ground sampling distance (GSD) at 200 feet and field of view (FOV). B. Payload capabilities including power requirements, weight, CG, and other factors associated by various payloads (e.g., electro-optical IR, multi-spectral). Examples/diagrams should be provided. C. Network capability including data or demonstration of ability to send real-time payload data through the network d..Any known coverage, signal, or range limitations associated with the payload link e. Any known mechanical or operating limitations associated with the payload link. F..Other payload specifications or limitations specific to the sensor type g. Package delivery payload capabilities
| E. |
| Mission Planning Specifications |
a. UAS navigation modes and methods, specifically relating to telemetry assurance, reliability, and integrity
b. Any security or encryption features used by the autopilot
| F. |
| Flight Manuals |
a. Flight Operations Manual and/or Operating Handbook
b. Standard Operating Procedures
c. Emergency Procedures
d. Landing/take off area Requirements
e. Performance Charts
f. Data to Support Limitations
| G. |
| Security & Encryption |
a. Any information related to Payload, GCS, Autopilot, or UAS link security and encryption
| H. |
| Limitations |
a. Information regarding known limitations for the following:
i. Wind (Launch / Recovery) (Kts.)
ii. Precipitation (In./Hr)
iii. Crosswind (Kts.)
iv. Flight Into Known Icing (FIKI)
v. Temperature I
vi. Min/Max Altitude (MSL)
vii. Min/Max Cruise Speed (Kts.)
viii. Line of Sight (LOS) Range (Miles)
ix. Beyond Visual Line of Site (BVLOS) Range (Miles)
x. Maximum Endurance (Minutes)
xi. Maximum Range (Miles)
xii. Maximum Gross Take-Off Weight (MGTW) (Lbs.)
xiii. Minimum Payload Weight (Lbs.)
xiv. Maximum Payload Weight (Lbs.)
xv. Center of Gravity (CG) / Load Limitations
xvi. Other Limitations
| I. | |
| Ground and Air Risk Mitigation/ Fail Safe Specifications | |
| a. | Parachute compliance information including testing, if equipped |
| b. | Frangibility compliance information including testing |
| c. | Compliance information including testing or any other equipment used to mitigate ground and/or air risk |
| |_| |
| J. |
| Command and Control (C2) Specifications |
a. Continuity including the expected duration for connections to hold
b. Signal level coverage including any known coverage, signal, or range limitations Note: Expected RF coverage is from the ground level for take-off and landing and up to 400 feet AGL within the intended area of operation
c. Latency including the end points for latency broken down by architectural segments
d. Data or demonstrated capability of seamless C2 link handovers or transition of control without experiencing a lost link event
e. Network capability including data or demonstration of real-time telemetry sent through the network
f. The number of simultaneous operations the C2 capability can support
g. Any known mechanical or operating limitations associated with the C2 hardware
h. Reference to any standards the C2 capability complies with or was tested to
Customer Reference The references shall include the name, address, contact person, telephone number, length of service and a description of the goods and services that the Bidder provided to the client.
Business Reference #1
Required Use this column for the answer
Company Name
Street address, city, state, zip
Contact Person
Phone Number
Length of relationship/service
Business Reference #2
Required Use this column for the answer
Company Name
Street address, city, state, zip
Contact Person
Phone Number
Length of relationship/service
Business Reference #3
Required Use this column for the answer
Company Name
Street address, city, state, zip
Contact Person
Phone Number
Length of relationship/service image1.jpeg
File details come from the government source that posted it. Updated .