Build a process, test a plan and understand the result. These guides cover the browser workspace, modeling rules, experiments and the standalone engine.
Open Loopset → · Watch the demos · Project overview
| Your goal | Follow this path |
|---|---|
| Try Loopset for the first time | Quickstart → Service Studio video experiment |
| Build a layout from scratch | Facility guide → Workspace controls |
| Explore a ready-made process | Starter templates → Read a result carefully |
| Understand results and uncertainty | Read results in the workspace → Measurement and interpretation |
| Integrate or extend the engine | Headless API → Architecture → Contributing |
| Guide | What you will find |
|---|---|
| Quickstart | Open a template, try a capacity decision, reproduce the demo, calculate, save and reopen a project. |
| Workspace guide | Properties, demand and duration, teams and shifts, process editing, comparisons, replay, keyboard controls and smaller screens. |
| Build a facility | Start empty, place and arrange objects, connect process cells, save templates and transfer the complete facility. |
| Starter templates | All twelve starters, their process questions, two alternatives each, assumptions and personal templates. |
| Export and share | Choose project JSON, run JSON, CSV, PNG, HTML or print/PDF and keep the calculation context with the result. |
The visual world and the numerical model have different roles. Artwork and walking make a process easier to follow; arrivals, durations, routing, queues and capacity determine its results.
- Model guide: process steps, distributions, priorities, patience, resources, calendars, event ordering, measurement, reproducibility and CSV inputs.
- Measurement and interpretation: completed versus unfinished work, waiting samples, percentiles, warm-up, replay limits and uncertainty.
- Replications and paired comparisons: run repeated experiments and compare compatible plans through the headless API.
- Bounded capacity search: search a finite set of shared-resource capacities and retain separate verification runs.
- Portable examples: synthetic reference projects and reproducible command-line runs.
The supplied examples are learning models. Real decisions need appropriate inputs, validation and an understanding of uncertainty. A single run is not a general improvement guarantee.
| Guide | What you will find |
|---|---|
| Headless API | Build/import commands, public exports, project validation, one run, replay statistics, experiments and the CLI contract. |
| Architecture | Model, calculation, rendering and storage boundaries; immutable results; templates and empty layouts. |
| Contributing | Where to make a change, what evidence to include, template/demo exports and publication checks. |
| Testing | Automated coverage and browser smoke-check commands. |
| Static hosting | Build a static deployment, configure a subpath, serve media and verify the deployed source revision. |
| Security | Supported reporting and handling of vulnerabilities. |
- Prepared asset catalogue: the browser-ready inventory, source preparation and verification.
- World assets and attribution: model, people, surroundings and lighting sources, plus browser adaptations.
- Demo media: videos, screenshots, repository artwork, recording scope and credits.
- Third-party notices: the separate licenses for dependencies, artwork, fonts, music and effects.
- Code license: MIT terms for original Loopset code.
New to the product? Try a first-use task and tell us where you got stuck. No code or private project is needed.
Open an issue with a small synthetic example, the actions you took and the result you expected. Keep personal or customer data out of public examples.