Preliminary Design Review Reports Due December 2!
Through the Preliminary Design Review (PDR), judges will be assessing each team's overall level of readiness to undertake the URC competition, specifically whether teams will be ready to submit a System Acceptance Review (SAR) package by early March, and be prepared to compete by June (if selected). Judges view this report as a tool that will help teams to solidify and articulate the essential elements of a successful team early in the competition cycle.
The URC PDR combines many elements of both a traditional proposal and PDR in the business world.
Deadline: Preliminary Design Review (PDR) Reports are due no later than 11:59pm Mountain Standard Time (MST; UTC-7) on December 2, 2026.
Submission: PDR Reports must be submitted electronically through the URC2027 PDR Submission Form (link to be posted soon).
Format & Layout: Reports are limited to 6 pages total on standard letter paper (8.5 in. x 11 in.) with 1-inch margins, using single-spaced Calibri 11-point font (minimum 8-point font for captions/tables). Submissions must be in *.pdf format, with embedded figure text legible at 250% zoom.
Page & Content Allocations: PDR Content must appear on the pages designated below. Each page may contain a combination of text, tables, figures, etc. unless otherwise noted.
Header (top of Page 1): Team Name, University, City and Country, Student Team Lead, and Alternate Point of Contact
Page 1: Team Structure
Page 2: Team Resources
Pages 3-4: Project Management Plan, with Gantt chart on Page 4
Pages 5-6: Preliminary Technical Design
The following are essential elements of information that teams are required to address. Teams may expand upon each content category at their discretion, while still following the format requirements.
Discuss your team's structure, to include the leadership and overall membership. A summary the team's academic demographics (which academic departments are represented, academic year, project experience, etc.) should also be discussed. Discuss your team's recruiting/training plans, and educational/public outreach plans (note: educational outreach is different than your team's recruiting plan). A team photograph must also be included.
Do not include individual member biographies.
Discuss your team's facility resources. This should include your access to appropriate design and fabrication spaces, as well as test facilities/locations. Captioned photographs of key facilities must be included.
Discuss your team's financial resources. This should include a project budget, and your fundraising and financial management plan. Finances should be listed in USD (United States Dollars). The project budget should be presented as a table, including income categories and total to date, expense categories, total required, funding required, and income sources that satisfy the deficit (if any). Teams are required to use the provided Project Budget Table template.
Simply stating that you will build a budget and raise funds is considered insufficient - please describe your budget, fundraising plan, etc.
Page 3: Discuss your team's overall approach to the URC system development life cycle (e.g. plan, design, manufacture, integrate, test). This plan should explain how you intend to solve the problems, not necessarily the exact solution. Additional required elements of the Project Management Plan include:
Document sharing and knowledge management plan;
Systems engineering and integration plan;
Note: Teams intending to compete for the INCOSE Foundation Excellence in Systems Engineering Award (details forthcoming) are encouraged to begin the requirements and verification table now, starting from mission threads (use cases) that walk through each competition mission end-to-end, and including the team's derived requirements. This additional content is optional, but will be helpful for future deliverables related to the systems engineering award.
Testing and evaluation plan;
A narrative explanation of your Gantt chart that justifies how you will complete remaining tasks on time.
Page 4: Provide a full page Gantt chart documenting your team's integrated master schedule (IMS).
The Gantt chart must cover September 2026 through June 2027, and be an accurate reflection of the team's planned system development life cycle. Time resolution must be 1 week or shorter.
The Gantt chart must include the following for each task: start/end dates, percentage complete, and task owner (individual or subteam).
Tasks must be organized through a logical work breakdown structure that reflects the system architecture. Tasks and subsystems specific to URC2027 should be emphasized.
Identify all work completed and all work remaining (to include integration and testing). Accurately depict the critical path for project completion (the sequence of interdependent work elements which determine the shortest schedule to completion).
Teams must present their system architecture, specifically differentiating which subsystems are a) new for URC2027; b) being modified from a prior rover; or c) being reused without modification from a prior rover. This must be shown in system architecture diagram(s) of the team's choosing.
Teams should present their preliminary technical design for major rover systems (e.g. mobility, communications, arm, command and control, science payload). Details are encouraged. Design drawings, 3D renderings, photographs, or other technical artifacts are expected to accurately reflect the progress documented in your team's Gantt chart.
For URC2027 judges will place an increased emphasis on teams clearly differentiating between systems carried over from prior years' work, and what is being developed during the URC2027 competition cycle.
Teams may be penalized for violating the format requirements, failing to provide proper citations, or other critical issues as assessed by the judges.
Follow Instructions Carefully: Read all PDR requirements and the Tips From the Judges section thoroughly. Historically, the majority of negative PDR feedback has been due to teams failing to follow explicit instructions and guidance.
Maximize Allowed Space: Use all six pages allowed. While six pages may seem short for the volume of information requested, the format is designed to keep your report focused and concise.
Avoid Biographical Filler: A full biography of each team member is not required when addressing Team Structure. Be thoughtful about the space devoted to each section of your report.
Provide Actionable Details: Simply stating that your team has a subsection of the plan (e.g., “we will create and follow a test and evaluation plan”) will be considered insufficient. The goal is to demonstrate to judges that your team has a real plan tailored to your team that will ensure success.
Do Not Rely on Past Success: Do not rely on your team's past competitive success as a substitute for addressing the required elements of information.
Pay Close Attention to Specific Required Elements:
Team Structure - Include a graphical organization chart and team photo;
Team Resources - Include the Project Budget Table in the required format, and captioned photographs of key facilities;
Project Management Plan: Include the Gantt chart in the required format on Page 4, and ensure that it accurately reflects both your current status and overall project management plan;
Preliminary Technical Design: Include one or more system architecture diagram(s) that can be used to illustrate new work being undertaken for the current competition cycle, and technical artifacts that communicate your design.
Follow Mandatory Guidance: Additional resources and guidance on creating proper budget tables and Gantt charts are available. Teams are required to follow this guidance.
Plan Ahead for Systems Engineering: The INCOSE Foundation Excellence in Systems Engineering Award will return for URC2027. URC2027 Finalists (following post-SAR downselection) will be asked to submit a supplementary Systems Engineering Annex later in the competition cycle. Teams that carefully document their requirements baseline during the PDR phase will find the future annex process much more straightforward.
Utilize Available Systems Engineering Resources: Systems engineering resources for URC teams, including the INCOSE Foundation judges’ Top 20 Rules of Rover Design, are available from the INCOSE Michigan Chapter: https://michigan.incose.org/university-rover-challenge/