Robot product development path · Gate 02

Reference architecture, digital model & interface contract

Translate requirements into a versioned system architecture that connects mechanics, electronics, compute, software, data and human control.

Decision this gate must answerDo the models and interfaces describe one coherent machine that can be analysed, integrated and changed without losing traceability?

Inputs

Controlled information to bring in

  1. 01

    Approved use case, requirements and risk assumptions

  2. 02

    Candidate form factors, make-or-buy choices and component constraints

  3. 03

    Mechanical loads, energy, thermal, timing and communications budgets

  4. 04

    Licensing, export, supply and lifecycle constraints

Outputs

Artefacts that must be reviewable

  1. 01

    System context, functional and physical architecture

  2. 02

    Versioned CAD plus URDF, SDF, MJCF or equivalent description

  3. 03

    Electrical, data, software and human-control interface contracts

  4. 04

    Controlled component baseline, provenance record and change log

Core work packages

Every workstream leaves traceable evidence.

01

Allocate functions

Allocate perception, planning, control, power, communications, safeguarding and human decisions before selecting a fashionable model or body.

02

Create the physical model

Connect kinematics, mass, inertia, collision geometry, joint limits, transmissions, sensors and frames to controlled CAD revisions.

03

Control interfaces

Specify voltage, current, thermal, mechanical, timing, protocol, coordinate-frame, state and error semantics at every boundary.

04

Manage provenance and licences

Record every imported mesh, model, dataset, library and design reference with version, owner, terms, modification and distribution decision.

Gate review

Every answer should carry evidence, not only ‘yes’ or ‘no’.

  1. 01

    Are mass, inertia and joint limits identified rather than copied from a visual model?

  2. 02

    Can every external interface be tested without interpreting undocumented assumptions?

  3. 03

    Are safety functions independent from non-safety autonomy where required?

  4. 04

    Can one component be replaced without silently invalidating the model or evidence?

  5. 05

    Are third-party rights and redistribution conditions visible at file level?

This page can support

  • 01A coherent architecture baseline
  • 02Simulation-ready model packages
  • 03Traceable make, buy and integration decisions

This page cannot replace

  • 01Physical system identification
  • 02Supplier-controlled drawings and specifications
  • 03Engineering sign-off for high-energy or human-contact systems