OHIO/INDIANA UAS CENTER AND TEST COMPLEX COA and Range Management Web Application WebUAS Request for Information (RFI) Issuing Agency: Ohio Department of Transportation Issue Date: 12/10/2013 Respond by: 12/20/2013 1
Table of Contents Confidentiality... 3 Introduction... 4 RFI Procedure... 5 Background... 6 Scope... 7 WebUAS Minimum Application Requirements... 7 WebUAS Range Management Option... 8 WebUAS Flight Tracking Option... 9 WebUAS UAS Maintenance Option... 9 WebUAS Pilot In Command (PIC) and Observer Management Option... 9 RFI Questionnaire Section... 11 2
Confidentiality All Respondents are strongly discouraged from including in a RFI any information that the Respondent considers to be a trade secret, as that term is defined in Section 1333.61(D) of the Ohio Revised Code. All information submitted in response to this RFI is public information unless a statutory exception exists that exempts it from public release. If any information in the RFI is to be treated as a trade secret, the RFI must: Identify each and every occurrence of the information within the RFI with an asterisk before and after each line containing trade secret information and underline the trade secret information itself. Answer Yes to RFI Question 2 on the Respondent s Information Page, Does this RFI contain information considered a trade secret? Include a page immediately after the Respondent Information Page that lists each page in the RFI that includes trade secret information and the number of occurrences of trade secret information on that page. To determine what qualifies as trade secret information, refer to the definition of trade secret in the Ohio Revised Code, which is reproduced below for reference: (D) Trade Secret means information, including the whole or any portion or phase of any scientific or technical information, design, process, procedure, formula, pattern, compilation, program, device, method, technique, or improvement, or any business information or plans, financial information, or listing of names, addresses, or telephone numbers, that satisfies both of the following: (1) It derives independent economic value, actual or potential, from not being generally known to, and not being readily ascertainable by proper means by, other persons who can obtain economic value from its disclosure or use. (2) It is the subject of efforts that are reasonable under the circumstances to maintain its secrecy. 3
Introduction This is a request for information (RFI), and does not constitute a commitment, implied or otherwise, that the Ohio Department of Transportation (ODOT) will take procurement action in this matter. This RFI is being used to gather information for ODOT to make decisions regarding the development of a COA and Range Management System which will be called WebUAS in this RFI and on the Respondent s submitted RFI Questionnaire. This RFI is designed to provide Respondents with the information necessary for the preparation of an appropriate response. It is not intended to be comprehensive, and each Respondent is responsible for determining all factors necessary for submission of a comprehensive response. Responses should be based on the material contained in this RFI or any other relevant information the Respondent thinks is appropriate. By submitting a response, each Respondent agrees that it will not bring any claim or have any cause of action against the ODOT, the State of Ohio, or any employee of ODOT or the State, based on any misunderstanding concerning the information provided or concerning the ODOT s failure, negligent or otherwise, to provide the Respondent with pertinent information as intended by this RFI. Information submitted in response to this RFI will become property of the State of Ohio. The State of Ohio will not pay for any information herein requested nor is it liable for any cost incurred by the vendor. 4
RFI Procedure Respondents to this RFI should complete the RFI Questionnaire Section. All responses and/or questions must be emailed as PDF or Word documents to: ODOT Office of Contracts Contracts.purchasing@dot.state.oh.us Responses are due by 5 pm on Friday, 12/20/13. 5
Background The Ohio\Indiana UAS Center and Test Complex (UASC&TC) operate on the directive to manage the new Unmanned Aircraft Systems (UAS). Managing UAS involves accessing the information needed for management of Certificate of Authorization (COA), issued to the FAA, by the UASC&TC and specific flight areas (ranges) for test use of UAS by county and local government agencies, metropolitan planning organizations, corporate organizations, and the general public. UASC&TC currently maintains the FAA Certificate of Authorization (COA) and Range Management Web Application WebUAS information on a SharePoint list and does not have a way to track or schedule testing COA data and range assets. Going forward the WebUAS must enable users to input UAS data and specific COA data through a web portal. The general requirements of this WebUAS portal are to support a diverse skill level of users on operating systems ranging from mobile to desktop allowing them to input and manage the COA data as well as schedule range time for flight operations in a secure, effective, user friendly manner. The purpose of this RFI is to manage the COA information (with a potential to provide a dynamic linkage to the FAA) coordinate and manage range assets as well as the option to gather other pertinent information related to flight operations in a secured web application that serves as a central portal for UASC&TC personnel. A suitable enterprise solution would need to maintain a complex database for efficient real time storage and retrieval of the data, offer document management and graphics capabilities, support pre defined reports and user defined reports. The RFI Questionnaire completed by respondents will provide UASC&TC valuable information to support a decision regarding the development/purchase of a FAA COA and Range Management Web Application. 6
Scope The WebUAS system must have a certain minimum level of functionality; see WebUAS Minimum Application Requirements below. Additional options important to the UASC&TC s operations are also listed below and may be implemented in later phases; see WebUAS Range Management Option, WebUAS Flight Tracking Option, WebUAS UAS Maintenance Option, and WebUAS Pilot in Command (PIC) and Observer Management Option. The WebUAS system must provide a minimum level of functionality: WebUAS Minimum Application Requirements The WebUAS must have the following required minimum functionality: 1. Must have the ability to meet all reporting requirements as defined in the FAA s Other Transaction Agreement (OTA) for the UAS testing center requirements (https://faaco.faa.gov/index.cfm/announcement/view/14348) 1.1. OTA reporting requirements are currently not fully defined from the FAA. The application is required to include the ability to modify the database to insure that the reporting requirements are met without the need for additional programming. 1.2. Custom reporting must be able to work with the modifications made in 1.1. 1.3. Dashboard reporting must be able to work with the modifications made in 1.1. 2. XML API features for communication protocols such as RSS\GeoRSS for communication with the FAA as well as other potential UASC&TC customers 3. Access to the application through a secure login 4. User account creation and management tools 5. UAS management reporting tools 6. COA tracking and management tools 6.1. Includes all information required by the current FAA COA application process 6.2. Includes oversight capabilities between the testing center personnel and the applicant 6.3. Includes linkage to automate the COA application between the UASC&TC and the FAA 6.4. Includes linkage to automate the COA cancelation between the UASC&TC and the FAA upon failure for monthly reporting 7. Interactive end user help system for all areas including 7.1. FAR References 7.2. Frequency Spectrum References 7.3. Technical Definitions 7.4. Contact Information 8. Device independent compatibility with mobile, tablet, and desktop devices. 9. All time data is displayed in the appropriate local time zone as well as Zulu (GMT) 10. Real time configurable dashboard showing (Note all data that has a spatial context will be displayed in a spatial context): 10.1. Status, Active, Pending, Draft COA s 10.2. Map of Operations 10.2.1. COA locations by status 10.2.2. Temporal querying 10.3. Aerial Overlays 10.4. Sectional Charts 10.5. Shaded Reliefs 10.6. Weather Information 10.6.1. Including National Oceanic and Atmospheric Administration (NOAA) Aviation Weather 10.6.1.1. Reports both aviation METAR format and Laymen weather forecasts 10.7. Local weather information 10.7.1. Ohio Roadway Weather Information 7
10.7.2. Indiana Roadway Weather Information 10.7.3. Other local sources 10.8. Extended Weather Forecasting 11. Records data that meets FAA requirements for monthly reporting 11.1. Automated alerts prior to reporting deadlines 11.2. Automated warnings post deadline 12. Records Notices to Airman (NOTAM) and Air Traffic Control (ATC) Coordination 13. Configurable automated notifications for time events 13.1. Notifications should be e mail, SMS or application based alert. 14. Development of an outward facing website with secured web login. 15. Fully integrated into the WebUAS Range Management System Additional Optional considerations should be addressed by the WebUAS System: WebUAS Range Management Option The WebUAS Range Management Option must have the following functionality: 1. Must have the ability to meet all reporting requirements as defined in the FAA s Other Transaction Agreement (OTA) for the UAS testing center requirements (https://faaco.faa.gov/index.cfm/announcement/view/14348) 1.1. OTA reporting requirements are currently not fully defined from the FAA. The application is required to include the ability to modify the database to insure that the reporting requirements are met without the need for additional programming. 1.2. Custom reporting must be able to work with the modifications made in 1.1. 1.3. Dashboard reporting must be able to work with the modifications made in 1.1. 2. Schedule and track all flights operations in ranges (MOA, Restricted Airspace, Training Areas) 3. Range Status 3.1. Active or Inactive 3.1.1. Time and Date of Operations 3.1.2. Descriptions of each flight operation 3.1.3. Operational areas and altitudes 4. Range Deconfliction Tools 4.1. Automatic notification of conflicts in flight operations 4.2. Suggests alternative operation times 5. Integrated customizable dashboard\reporting functions 5.1. View and query all range operations/information historical, current and future 5.2. Generate reporting on all operations with sort and filter functions 5.3. Display all data in tabular and spatial concurrently 5.4. Flight data requirement reporting function to insure all requirements are met for flight operations 6. Detailed information on each range including: 6.1. Operational requirements and limitations 6.2. Detailed training asset information 6.3. Contact and location information 6.4. Spectrum capabilities\limitations 7. Interactive end user help system for all areas including 7.1. Access to all range specific documents for operations 7.2. Technical Documents 7.3. Contact Information 8. Schedule and tracking of alerts and notifications including: 8.1. Notices to Airmen (NOTAMS) 8.2. Air traffic control notices and communications as required by the COA 8.2.1. Phone Communications 8
8.2.2. Emails 8.2.3. Fax Documents 8.2.4. Agreements 8.3. Temporary Flight Restrictions (TFR) 9. Go Fly documentation for Safety Review Board (SRB) and Transportation Research Board (TRB) reporting requirements 10. Fully integrated into the WebUAS Application WebUAS Flight Tracking Option The WebUAS Flight Tracking Option must have the following functionality: 1. Must have the ability to meet all reporting requirements as defined in the FAA s Other Transaction Agreement (OTA) for the UAS testing center requirements (https://faaco.faa.gov/index.cfm/announcement/view/14348) 1.1. OTA reporting requirements are currently not fully defined from the FAA. The application is required to include the ability to modify the database to insure that the reporting requirements are met without the need for additional programming. 1.2. Custom reporting must be able to work with the modifications made in 1.1. 1.3. Dashboard reporting must be able to work with the modifications made in 1.1. 2. Time of flights 3. Flight location 4. Duration of flights 5. Pilot in Command and Observer 6. COA being exercised 7. Lost Link/Incident information 8. Aircraft type/serial #, etc. 9. Other TBD (altitude, flight path, etc.?) WebUAS UAS Maintenance Option The WebUAS UAS Maintenance Option must have the following functionality: 1. Must meet all reporting requirements as defined in the FAA s OTA for the UAS testing center requirements 2. Aircraft status notifications 3. Service notification 4. Maintenance logging 4.1. Parts required 4.2. Technician 5. Maintenance reporting tools 6. Work orders 6.1. Assign 6.2. Track 6.3. Notification WebUAS Pilot in Command (PIC) and Observer Management Option The WebUAS PIC and Observer Management Option must have the following functionality: 1. Must have the ability to meet all reporting requirements as defined in the FAA s Other Transaction Agreement (OTA) for the UAS testing center requirements (https://faaco.faa.gov/index.cfm/announcement/view/14348) 1.1. OTA reporting requirements are currently not fully defined from the FAA. The application is required to include the ability to modify the database to insure that the reporting requirements are met without the need for additional programming. 1.2. Custom reporting must be able to work with the modifications made in 1.1. 9
1.3. Dashboard reporting must be able to work with the modifications made in 1.1. 2. Registry 3. Currency information and notifications 4. Qualification 5. Training history 6. Flight and UAS platform history 10
RFI Questionnaire Section RFI Questionnaire is to be completed by Respondent. 1. Provide the following Respondent Information: Organization: Address: Point of Contact & Title: POC Phone Number: Email Address: 2. Does this RFI contain information considered a trade secret? Yes / No 3. Describe any current solutions that meet the requirements. 4. Describe any current or similar applications which exist with comparable functionality. 5. Describe any limitations or areas of improvement for existing applications of comparable functionality. 6. Describe known problems when performing similar data management processes on similar datasets. 7. Describe the general amount of time necessary to develop and implement an application of this nature. 8. Please indicate any functionality included in the solution which might be beneficial but was not mentioned as a requirement. 11
9. Describe known limitations of the solution. 10. Describe the methods this solution would employ for the database design. 11. Describe the maintenance and upkeep expected with this solution. 12. Describe the timeline associated with implementing this solution. 13. Has any or all of this solution been implemented? If so, please provide the agency and contact information. 14. Describe an example of pricing structure (not specific prices, instead a description of how products are priced, i.e. one time fee, individual module fee, annual service fee, upgrade fees, maintenance fees, etc.). 15. Please provide any additional comments relevant to this RFI. 12