Holarch

Getting Around Holarch

Your First Project

Create a project, then work through the lifecycle groups from left to right.

Create or open a project

  1. Open Manage Projects (bottom of the rail).
  2. Click + New Project, enter a name, then Create & Go. To explore first, choose Project Files ▾ → Create Demo Project (the CubeSat EO-1 earth observation model) or Create Sample Project (a drone delivery model).
  3. Holarch opens the project on Home. Switch projects from the project name at the start of the top bar.

The core workflow

  1. Capture requirements: Write and Trace Requirements or Import Requirements from Word, Excel, CSV or ReqIF.
  2. Derive functions and a functional flow: Turn Requirements into Functions and an FFBD.
  3. Build the architecture and interfaces: Build the Architecture and Produce an ICD; track resources with Track Budgets and TPMs.
  4. Plan and run verification: Set Up Verification, Run Tests and Produce the RVTM.
  5. Manage risks and decisions: Run a Risk Register with the MIL-STD-882E Scale and Run a Trade Study and Record the Decision.
  6. Baseline and deliver: Produce a Review Package.

Every change is saved automatically and can be undone. See Data and Security for where projects are stored.

The demo project

Create Demo Project builds the CubeSat EO-1 model, a 6U earth observation satellite with content on every page:

  • Requirements: a System Requirements Specification with register attributes, TBD/TBR items with owners and due dates (one overdue), approvals, an SRR baseline and suspect links from changes made after it. See TBD/TBR Register and Suspect Links.
  • Behavior: functions F1–F11 with their FFBD and Tables 1 and 2, and the Run Nominal Imaging Pass action diagram to run in Simulator.
  • Architecture and interfaces: asset, BDD, IBD, state machine, use case, parametric, IDEF0, N², physical I/O and ICD diagrams; mass and power Budgets & TPMs with three TPMs (one at risk); interface status, item flows, typed and conjugated ports and one over-capacity link; a parametric power margin check that fails after Solve All; pictures and annotations on the asset and BDD diagrams.
  • Verification: two test suites with steps, run records and evidence, two completed test cycles, issues on the failed tests and the RVTM roll-up.
  • Risk and decisions: a risk register on the default 5×5 scale with a burn-down plan and snapshots, and a downlink band trade study with Pugh and sensitivity analysis and a recorded decision.
  • Plan, whiteboards and frameworks: a Kanban board, a Gantt chart and milestones; OV-1, causal loop and brainstorm whiteboards; DoDAF AV-1, OV-1, OV-5b and OV-6a products.

Requirement 6.5 (planning cycle time) has a Measure but no simulation result yet. To record one, open Run Nominal Imaging Pass in the Simulator, run Monte Carlo, then Check Against Requirement… and Record Result…. Scripts can do the same with Demo.recordSimCheck() after the demo is created.

Where each page is

The navigation rail groups every page by lifecycle stage. Generated from this installation: