The initial submission for the Innovation Challenge is a proposal that identifies the team taking part in the Innovation Challenge, including the Faculty Advisor and a description of the system being proposed.
Teams will complete the Initial Submission template and submit the package no later than September 22, 2017 at 11:59PM (Arizona Time). Submission received after this time are not eligible to take part in the Innovation Challenge. Eligible submissions are evaluated by the Review Committee based upon on innovation, technical merit, and ability to produce the solution. Based upon the proposal evaluation an initial down select will occur. Semi-finalists will be announced on September 29, 2017.
Semi-Finalists will be invited to present their solution to the Innovation Challenge Review Committee. The proposal presentation is an opportunity for teams to describe the capability, how the requirements will be implemented, and answer questions from the Review Committee.
Team will complete the Proposal Presentation template and submit the package no later than October 10, 2017 at 11:59PM. Submissions received after this time are disqualified from the Innovation Challenge.
Proposal presentation will occur on the 11th or 12th of October 2017. Teams will schedule their presentations on a first come first served basis. Scheduling for Proposal Presentation opens on September 30, 2017.
The Review Committee will evaluate the proposals based upon innovation, technical merit, and ability to produce the solution. Based upon an evaluation of the presentations a final down select will occur and the finalists announced on 13 October 2017.
In Progress Reviews
Progress is monitored during the conceptualization, development, and production phases through a series of reviews with Review Committees and the teams. The primary goal of the review is to ensure the teams develop their intended solution and resolve any roadblocks to development.
Teams will schedule the specific time and date for their review using the Innovation Challenge website on a first come, first served basis. To the fullest extent possible the entire team is expected to be present and support the reviews.
Initial Design Review
The Initial Design Review evaluates the architecture of the system (and subsystems) to ensure the design has an expectation of being developed within the allotted budget and schedule and accomplish the goals of the Innovation Challenge. The review will assess the design documentation (conceptual design and specific hardware and software designs), cost estimates, Key Performance Measure, and risks to implementation.
Teams will complete the Initial Design Review template for this review and submit the review package prior to the review. The Initial Design review is anticipated to take approximately 15 minutes followed by a brief question and answer phase. Teams may add additional information into the back-up section of the briefing to add context and demonstrate the maturity of the design.
The Development/Production Review evaluates the maturity of the design and assesses the design's readiness for production. The review will focus on ability of the design to meet the team’s performance requirements and adequate design definition to support procurement, fabrication, and assembly.
Teams will complete the Development/Production Review template for this review and submit the review package prior to the review. The Development/Production readiness reviews are anticipated to take approximately 15 minutes followed by a brief question and answer phase. Teams may add additional information into the back-up section of the briefing to add context and demonstrate the maturity of the design.
Flight/Test Readiness Review
The Flight/Test Readiness Review evaluates that the system has demonstrated it can safely fly, meet the requirements defined by the team, and complete the challenge. The review will focus on the built system and actual system performance.
Teams will complete the Flight/Test Readiness Review template for this review and submit the review package prior to the review. Flight/Test Readiness Review is anticipated to take approximately 10 minutes followed by static display and briefing of the developed system. Teams may add additional information into the back-up section of the briefing to add context and demonstrate the maturity of the design.
Teams will be required to develop and deliver a final report on the system No Later Than 1 June 2018. The report shall document the systems intended mission and the function of the key components that enable the capability. This should include a functional description of the major components and functions, software operation (major functions, interactions, and output), and operator interface.
An assessment of system performance during the Fly-Off should also be included the report. The assessment should describe performance during the Fly-Off but also an assessment of intended system role and actual performance.
The conclusion should include recommended updates to the system to address any shortcomings identified during the Innovation Challenge and or enable the full capability intended by the team.
The report is limited to 10 pages, 10 point font, double spaced.
After the design has been produced and is ready for flight a Safety Review shall be scheduled with the DSO. Teams will schedule the Safety Review directly with the DSO. The Safety Review may result in items to be resolved prior to issuance of an Authority To Operate (ATO). Once the ATO has been issued flight operations can be conducted in the designated indoor flying facility.
NOTE: THE TEAM SHALL NOT CONDUCT FLIGHT TESTING WITHOUT AN AUTHORITY TO OPERATE BY THE SAFETY OFFICER. FAILURE TO COMPLY WITH THIS RULE SHALL RESULT IN IMMEDIATE DISQUALIFICATION FROM THE INNOVATION CHALLENGE
Flight testing shall occur only in the designated indoor flying facility and only with systems that have received an ATO.
Flight testing will be scheduled through the Innovation Challenge website (http://asure.asu.edu/innovation-challenge) and will only be conducted during scheduled time. The team’s Faculty Advisor will be in attendance for all flight operations. If the faculty advisor cannot attend, coordinate with the DSO or ASURE for an appropriate alternate to attend. Only members of the team and the Innovation Challenge staff are permitted to attend any events that include flight operations.
The team’s safety lead will conduct a preflight safety briefing and ensure the team follows the flight operations checklist and conducts the event with a focus on safety.
The final phase of program is a fly-off event to evaluate the technical and operational capabilities developed by the various teams. A series of tasks will be used to assess the technical and operational performance of each team’s air vehicle, sensor package, and control station. The winner of the challenge will be selected by the Review Committee based upon the capabilities demonstrated during the fly-off event.
A detailed briefing will be given at the beginning of the fly-off event covering the logistics and timings of the event, rules and good conduct for safe operations, pre-flight briefings, etc.
Teams will also be given an order of events and strict time schedule for flight test. The schedule is necessarily tight and teams who are not ready to fly at their appointed slot time will be disqualified. It is expected that teams will arrive with a fully serviceable sUAS that is in good working condition.
The specific tasks and course layout will be announced at a later date.
The DSO shall have absolute discretion to refuse a team permission to fly, or to order the termination of a flight in progress. Only teams with an ATO will be eligible to enter the fly-off event.