UAS Challenge Submission Details
UAS Challenge Application
Those interested in participating in the MITRE Challenge must submit a white paper outlining their approach and a Participant Agreement. Three approaches are available for this submission, and applications must be received no later than February 7, 2016, to be considered:
- Via email to email@example.com
- Via the regular mail:
The MITRE Corporation,
Challenge Team, MS: T760,
7525 Colshire Drive, McLean, VA 22102-7539.
- Via a secure transfer mechanism
- Email firstname.lastname@example.org no later than February 2, 2016, to receive an account on this mechanism
MITRE will confirm receipt of applications via email.
White Paper Sections
Applicants must submit a white paper describing their system that includes the following items. The paper must be no more than 15 pages long; links or references to additional material will not be reviewed.
1.0 Introduction and Overview
1.1 Contact information
- Provide your company/team name, the name of the system, affiliation, and a primary POC (to include email and phone number)
- Select the category that best describes your system:
(A) Detection/determination only, (B) Interdiction only, or (C) Complete End-to-end Solution
1.3 Company/Team Overview
- Give a short overview of the history of the company and/or the team which developed the system solution
1.4 System Overview
- Give a general overview of the system including a description of the sensor technology, processing algorithm, and interdiction method as applicable.
- Describe unique dependencies or risks for your system (Examples: authority for RF jamming, hazardous materials, physical danger zones, etc.)
- Describe the key small UAS features that your system exploits (Examples: RF emissions, metal components, heat signature, etc.)
1.5 Technical Specifications
- Include technical specifications of your system
- Power requirements
- Environmental constraints
2.0 System Description
Provide details about your conceptual design, at a level sufficient for reviewers to understand the technical efficacy of your proposed design. Be sure to explain your design’s existing maturity (examples: summary of lab testing, live flight-testing, and exercises or events in which your system has participated, etc.)
2.1 High-level Concept of Operations
- Provide a high-level concept of operations for how the system would be used.
- Example scenarios would be useful.
- Briefly describe analysis and testing done to confirm performance.
Note: Complete sections 2.2 and 2.3, as applicable to your proposed system. The more information you provide, the more confidently we will be able to evaluate it against other proposals.
2.2 Detection/Determination Technical Approach
Detection and Tracking
- Describe the detection (sensor) modalities used, e.g. radar, RF detection, EO/IR cameras, etc. Consider including more details on effective range, altitude above the surface, resolution of target, and probability of detection.
- Describe your system’s capabilities to detect one or more small UAS.
- Describe any operational constraints of your system, e.g., susceptibility to interference from atmospherics, etc.
- Describe the tracking algorithms used to track one or more potential targets. Describe the algorithms' pedigree, if applicable
- Describe your approach used to determine if UAS is a threat based on its trajectory.
- Describe how your approach deals with maneuvering aircraft.
- Describe any operational constraints of your system, e.g., the maximum number of systems that can be tracked simultaneously, etc.
- Describe how a human operator is notified when your system perceives a potential threat.
2.3 Interdiction Technical Approach
- Describe your system interdiction approach.
- Describe how your system can interdict multiple small UAS at the same time. Consider including more details on recovery time between interdictions or other operational constraints.
- Describe the expected results of the interdiction e.g., will it crash, land safely, return to launch point, etc.
- Describe any operational constraints of your system, e.g., range, interference, atmospherics, etc.
- Describe the input your system requires to perform interdiction.
2.4 Operational Requirements
- Explain the requirements for deploying your system, including the number of personnel required to operate the system and any specialized training requirements.
- Explain the maintenance requirements of the system.
- Describe the environmental requirements required to operate system, including need for power, shelter, mounting requirements, etc.
2.5 Initial and Recurring Costs
- Provide a cost estimate for the initial and recurring costs including consumables.
- Provide a basis and explanation for these estimates.
3.0 Alignment to Challenge Criteria
Explain how your system satisfies the objectives of the challenge. The following items form the basis of the criteria we will be using for the first down select of the competition. Please write to each and include any other information that you feel reviewers will require.
3.1 Aligning with domestic safety and legal requirements
- Explain how your system would be deployable in a populated, U.S. domestic environment, with consideration of public safety and applicable laws and regulations.
- Explain how your system would be potentially deployable on a large scale to protect a wide variety of interests, from critical infrastructure, to sensitive security locations, to civil airports.
3.3 Technical Scalability
- Explain how your system can function against multiple simultaneous threats.
- Explain how your system will be able to continue to be effective as UAS technology evolves and steps that might be taken to defeat countermeasures.
3.4 Additional Value
- Explain additional advantages or value your specific solution might bring to the community concerned about unauthorized UAS operations, e.g., whether your system can identify the operator and/or the operator's location of the aircraft characterized as a threat.
3.5 Technology Readiness
- Using the Office of the Secretary of Defense Technology Readiness Assessment (TRA) document, section 2.5, estimate your system's current and future (by fall of 2016) TRL.
- Note: there is no minimal TRL for the challenge, this is just a tool to help us understand your current capabilities.
- Include a summary of any laboratory experiments, field trials, operational evaluations, and/or deployments.