Unit 08 · lesson

Read the Game as an Engineering Problem

Every FRC season changes the game, but the reasoning process stays familiar.

The manual gives you objectives, scoring rules, constraints, field geometry, match timing, penalties, ranking incentives, and robot-construction rules.

Strategy begins by turning those rules into requirements.

Separate scoring from winning

The highest-value individual action is not always the best strategic action.

A team may need to prioritize:

  • ranking points;
  • consistency;
  • alliance balance;
  • defense;
  • endgame reliability;
  • cycle time;
  • field position;
  • partner compatibility.

The current game defines the details. Your method should survive next season.

Convert rules into capabilities

Build a capability table:

Game objectiveRequired robot capabilityEvidence needed
cross field quicklyreliable mobilitytimed path/cycle data
acquire game pieceintake toleranceacquisition tests
score at targetcontrolled mechanismsuccess rate
endgame taskdedicated mechanismrepeated full-load test

Then ask which capabilities create the most value for the least complexity.

Constraint example

A team wants three scoring mechanisms because the game offers three scoring locations.

Constraints:

  • limited build time;
  • weight;
  • electrical demand;
  • programming effort;
  • driver training;
  • maintenance;
  • inspection;
  • spare parts.

A robot that does one high-value task reliably can outperform a robot that does three tasks badly.

Strategy should influence design before the robot becomes a collection of unfinished mechanisms.

Read the current manual correctly

When a strategy depends on a rule, cite the exact current rule or section in your team notes.

Do not rely on:

  • last year's rule;
  • a social media summary;
  • what another team said in the queue;
  • memory from kickoff.

The current official manual and updates are the authority.

Strategy brief

Choose a current or historical FRC game.

Write:

  1. three ways to earn meaningful match value;
  2. two ranking/strategic incentives;
  3. four robot capabilities;
  4. one capability you would intentionally not build;
  5. the evidence supporting that decision.

Failure mode: designing from highlight videos

Highlight reels select spectacular moments. They hide repair time, failed cycles, missed matches, driver difficulty, and mechanisms that worked twice all season.

Strategy needs distributions, not only highlights.

What can the robot do repeatedly?

That question leads directly into scouting.

process flow

Competition Operations and Troubleshooting: FRC Evidence Flow

  1. Plan

    Name the role, rule, criterion, constraint, and safety condition.

  2. Model

    Trace the subsystem or match decision and its dependencies.

  3. Test

    Use a bounded approved test or simulation and record evidence.

  4. Review

    Document correction, limitation, and next team action.

Read this concept flow as plain text
  1. Plan. Name the role, rule, criterion, constraint, and safety condition.
  2. Model. Trace the subsystem or match decision and its dependencies.
  3. Test. Use a bounded approved test or simulation and record evidence.
  4. Review. Document correction, limitation, and next team action.