Getting Started
Daritas turns automation code into an evidence-backed, expert-reviewed model of what your control system does — and keeps it current as the system changes.
What is Daritas?
Industrial control systems — PLCs, SCADA, embedded controllers — run for decades, but the knowledge of how they work usually lives in one engineer's head. Everyone else inherits thousands of lines of ladder logic, structured text, and wiring with no reliable documentation. When that engineer retires or moves on, the knowledge leaves with them — and the installation keeps running code nobody fully understands.
Daritas recovers that knowledge. We read the actual control code and build a structured, plain-language model of what the system does. Every claim is grounded in a verbatim citation back to the exact source that supports it, and the whole model is reviewed and signed off by a qualified automation engineer. It is not a guess and not a black-box AI summary — it is an accountable, evidence-backed model, with the unknowns disclosed rather than papered over.
How it works
Every assessment follows a four-stage process:
| Stage | What happens | Who does it |
|---|---|---|
| 1. Submit | You provide your control-system export — the PLC project or source files, plus any schematics or manuals — and the scope you care about. | You |
| 2. Survey & extract | Daritas surveys the codebase, condenses it to its logic essence, and extracts what the system does — each behaviour tied to the exact source location that supports it. | Daritas |
| 3. Review | A qualified automation engineer verifies the model against the evidence, resolves ambiguities, and signs off. The reviewer is named and accountable. | Reviewer + AI |
| 4. Deliver | You receive an interactive model to explore, plus exportable documents for your own systems and meetings. | Daritas |
What you receive
Every assessment delivers:
- Interactive model — an explorable map of the system: its components, behaviours, dependencies, and risks, with every claim linked to the source evidence behind it. This is the primary deliverable.
- Document exports — select any part of the model and generate clean Markdown, Word, or PDF documents for internal discussion, audits, or handover.
- Structured export — your model in an open, documented format you own, so the knowledge stays portable and integrates with your own systems.
Who uses Daritas?
- Installation owners and operators — running control systems whose original engineers have moved on, who need to understand, document, and de-risk what they depend on every day.
- Machine builders and OEMs — maintaining ranges of products and variants, who need a consistent, current picture of what each one actually does.
- Engineering firms — verifying, modernizing, or replacing control systems, who need a trustworthy specification of the existing system to work from.
- Audit and inventory teams — assessing many systems across sites, who need a comparable overview of condition, risk, and obsolescence.
Your first assessment
Step 1: Identify the system and export the code
Pick one system to start with. Export its control program from your engineering tool — for example a PLCopen XML file or the project source — and gather any schematics, manuals, or notes you have. The more context you provide, the richer the model.
Step 2: Choose your scope
Scope sets how deep the assessment goes — from a focused look at a single subsystem to a full model of the whole system. See the Customer Guide for the options.
Step 3: Submit and track
Once submitted, you can follow your assessment's progress. You'll be notified when your model is ready to explore.