Skip to content

PlantCraft 0.6.0

Choose a tag to compare

@jonathanwvd jonathanwvd released this 02 Nov 13:14
· 50 commits to main since this release
129b05a

PlantCraft 0.6.0

The suite in three languages (English, Brazilian Portuguese and Spanish), an installation file and requirements check for whoever installs the server, Operations as a built-in app, per-visit public demo sessions, and security hardening across the platform and apps.

[0.6.0] - 2026-11-02

Added

The suite in three languages

  • Brazilian Portuguese and Spanish for the whole suite. Every screen, message, report and
    help page of the platform and the six apps, Analytics' block catalogue included, with one
    language choice for the whole suite. The assistant answers in the language chosen. A check in
    make ci keeps the three languages complete (translations.md).

Installing and running the suite

  • Platform: the installation file. Choices that belong to whoever installs the server live
    in /etc/plantcraft/installation.conf. The file is owned by root and never mounted in a
    container. It sets the apps, demo, machine profile, CPU and memory ceilings, network and
    language-model switch, and its values win over the command line and .env.
    ./install.sh --show-config says whether it is applied (installation-file.md).

  • Platform: requirements check before installing. ./install.sh --check (or preflight.sh,
    --json) checks these and changes nothing:

    • system and processor;
    • Docker, Compose and Docker Desktop's licence;
    • control groups, CPUs, memory, swap and free disk;
    • the HTTPS port, internal networks and clock.

    install.sh runs it first and stops on a FAIL. It now also accepts Rancher Desktop's docker
    in WSL.

  • Platform: one machine profile sizes the whole suite. ./install.sh --machine small|medium|large|xlarge|auto|off sets every container's CPU and memory limit, processes
    and pools from one choice. The default auto picks by the CPUs and memory Docker sees, and
    values edited by hand in .env are kept. Operations shows the machine and its profile, and
    suggests the profile that fits after the machine changes.

  • Platform: Docker Engine in the bundle. On a Linux server with no Docker,
    ./install.sh --install-docker installs the Docker Engine 29.9.2 and Compose 5.6.1 the bundle
    carries, offline.

  • Platform: setup wizard (first version). The installer's screens open in a browser on the
    server (127.0.0.1, a random key per start). They ask for the apps, check the requirements for
    those apps, write the installation file and run the install.

  • Platform: ./install.sh --rotate-admin-password. A new emergency administrator password,
    shown once.

  • Platform: uptime by app and maintenance windows in Operations › Status, and an official
    Zabbix template in the bundle (monitoring/plantcraft_zabbix_agent.yaml).

  • Platform: health that tells the truth. /healthz answers 503 when an app's engine is in a
    crash loop, so Docker, System health, Operations and Zabbix all see it.

  • Platform: plantcraft llm set|show. The default language model and its key are set from
    the server's shell, the key read from standard input, with no browser.

  • Operations: the plant's holidays stop the clocks of queues with working hours.

  • Compute: a revoked worker enrolls again with a new one-time code, under the same name.

The public demo

  • Each visit is its own. A visible 30-minute clock, the visit ends after 5 idle minutes, 30
    places with a waiting page, and a notice before an update. With the switch on, each visit gets
    its own copy of every app's data, so what a visitor saves in Alarms, Analytics and View goes
    with the visit; writes to the platform stay refused. The demo says which parts are locked for
    security, and how long the visit lasts.
  • The assistant can be on in the demo. Ask-only, with per-visit chats, 10 questions per
    visit, limits per address, minute and day, and the tokens of every answer counted
    (PLANTCRAFT_PUBLIC_DEMO_LLM, off by default). A provider without credit reads as a pause, not
    an error, and the question does not count.

Operations, a built-in app for the people who keep the suite running

  • Operations sits beside Desk for administrators and the new Operations role.
  • Requests: anyone asks IT or an integrator for help from any app ("Ask for help"). Each
    request has first-answer and resolution targets per priority, and a queue's clocks run only
    in its working hours.
  • Partners: the companies working at the plant, each with its coordinator, teams, a sponsor
    at the plant and a last day of access. A sponsor approves each month's hours.
  • Temporary support access: a person gets Operations for up to 72 hours, for a reason. The
    access ends by itself.

Apps

  • Analytics: a plant map on the Overview, with every loop coloured by the KPI you pick. Also:
    • effective control and loop-hours lost by cause;
    • days until a falling health reaches its limit;
    • oscillations several loops share, grouped, with the likely origin;
    • overshoot, rise and settling times and IAE of each setpoint step found in the history;
    • a read-only PI tuning suggestion (Lambda/IMC);
    • a loop compared with a recorded reference;
    • Horch's cross-correlation in the stiction screen;
    • signal checks for rate of change, NE 43 fault levels and the source's own quality;
    • a Virtual sensor algorithm (Kalman filter and drift);
    • algorithms that run on every asset of an equipment type;
    • third-party APC health and the cost of each active limit: % on, MVs in service, CVs at
      a limit, and limits ranked by shadow price, also in the weekly report;
    • virtual sensors and models without a physical model: lab fusion (the online value
      corrected by the lab at each sample's time), a regression block (OLS, Ridge, PLS) trained by
      Calibrate with its validity range, an empirical model block (PCA, T² and SPE), mass balance
      reconciliation with gross error detection, and drift of a redundant pair;
    • "New action" on every loop result, with the loop's charts attached;
    • the diagram of an algorithm with lit, clickable wires and full screen.
  • Alarms:
    • import the DCS alarm list (CSV or Excel) as a draft;
    • consoles (operator positions) with their own alarm-rate targets;
    • limits by product grade;
    • state-based alarms, enabled only while a permissive holds;
    • an alarm performance section (ISA-18.2) in View's reports;
    • the EEMUA 191 performance level, floods with hysteresis, and what the journal tells.
  • Historian:
    • store and forward at the gateway (MQTT, Modbus and SQL survive a collector outage);
    • sources with owners, a contact and an expected interval, whose owners hear when a source
      fails;
    • audited edits of archived values;
    • OPC UA status codes kept with quality;
    • notes on a signal;
    • shortest interval between archived values (CompMin);
    • laboratory results as signals, and a LIMS read as a SQL source;
    • a limit on the points it records (MAX_SIGNALS);
    • daily and monthly rollups, each with its own retention, and the disk each one takes;
    • interpolated reads with a maximum gap, and summaries (count, % good, totals, time-weighted
      statistics) in API v1;
    • Sparkplug B sources, read only, with points added from births;
    • OPC UA subscriptions, opt-in per source (still read only).
  • View:
    • a multivariable controller (APC) panel;
    • reports made when a batch or a start-up ends;
    • assistant report sections that cite their facts as numbered footnotes;
    • reports over whole calendar periods;
    • trends compared with earlier periods;
    • laboratory results in trends;
    • ISA-101 analog indicators and alarm marks by priority;
    • a generated Level 1 overview of the whole plant;
    • Back between diagrams.
  • Models:
    • tracking: the model checked against the plant on a schedule, with model-minus-plant signals
      and a "Model off the plant" event;
    • an example optimization that tunes a PI for the least IAE;
    • OMChemSim in the runner, with a methanol and water flash drum that runs;
    • Compile a model and see whether it is compiled.
  • Simulator: operator training with scheduled faults and a separate answer key, snapshots,
    freeze and speed.

For app developers (plantcraft-sdk 0.80.0 → 0.105.0)

  • Images in an app's language model calls (POST /api/v1/llm/{use}, 0.86.0).
  • PlantCraftClient.lab_samples reads laboratory results with their status and times.
  • GET /api/v1/signals/{id}/value takes end, for the value of a window that closed earlier.
  • plantcraft_sdk.files.write_atomic and write_json (0.91.0).
  • A binary series answer, plantcraft_sdk.wire (0.85.0).
  • plantcraft_sdk.server.workers (0.80.0).
  • Starter asset types for a third-party multivariable controller: apc, apc_mv and apc_cv
    (0.93.0).
  • fuse_lab (0.94.0); series(..., sampling="interpolated", max_gap=) and summary()
    (0.95.0).
  • A copy of every app's database for each public demo visit (0.97.0, off by default).
  • askText and showToast in @plantcraft/ui replace window.prompt and window.alert.
  • One translation mechanism: createI18n in @plantcraft/ui, plantcraft_sdk.i18n with
    LanguageMiddleware, and python -m plantcraft_sdk.i18n_check --strict (0.102.0 to 0.105.0).
  • The app template (StarterCraft 0.2.0) keeps only the basics in its code, with full guides and
    recipes in its docs/.

Changed

  • Platform and apps: a new look for the whole suite (ui 0.102.0): page, card and text on one
    vertical rhythm, the new PlantCraft mark as the favicon in every app, and a display size in
    five steps, from Larger text to More space.

  • Platform and apps: pages load less script.

    • Plotly and the fonts download once for the whole suite, not once per app (ui 0.96.0).
    • Pages fetch Plotly only when they draw a chart.
    • The platform's pages load a quarter less script.
    • Analytics' Algorithms list and loop page, and the schedule and block pages, open without
      the diagram editor.
  • Platform: the Historian is read lighter.

    • Analytics' rounds read it 9 to 77 times lighter.
    • Notebooks read raw series 7 to 9 times faster through the binary answer.
    • View's min and max trend lines come from the Historian 10 times faster.
    • Means on a grid take one pass.
    • The Historian decodes each archive chunk once per process (HISTCRAFT_CHUNK_CACHE_MB).
  • Platform: tokens are verified once, not on every request. The notification feed is 36
    times faster, and a backup copies every app's SQLite at one instant.

  • Platform: sizing follows the container, not the host. Pools are sized by the container's
    CPUs, install.sh fits every CPU limit to small hosts, the Historian's database has its own
    CPU limit (HISTCRAFT_DB_CPUS), and a 4 GB machine needs 2 GB of swap for the demo with every
    app on.

  • Platform: ./install.sh --security-check runs in 1.5 s instead of 3.9 s.

  • Platform: state files are written whole or not at all, everywhere.

  • Platform: customizing an overview shows that it is on (ui 0.97.0).

  • Platform: the demo's plant data loads beside the rest of the seed, and the install log
    times each demo step.

  • Analytics:

    • a round hands each loop only its own samples;
    • history keeps a configurable time;
    • the Overview answers 50 people in 0.15 s (p95);
    • the stiction screen finds stiction behind a smooth controller;
    • asset runs are 70 times faster (side tables for filters inside JSON lists), and
      linkcraft compact gives the disk back after history thinning.

Fixed

  • Platform and apps: current names everywhere. Screens, docs, log lines and messages say
    Analytics, Historian, View, Models and Alarms, and commands say plantcraft; ids, images and
    settings keep their old names, so nothing in an installation changes.

  • Platform: the interface pass, with every page clicked like a person in light, dark and
    phone layouts:

    • the suite's dialog asks before every delete;
    • windows close the same way everywhere;
    • page titles are consistent;
    • no WCAG AA finding is left in the suite's frame (axe-core, 35 pages).
  • Platform: sizes from the 3-month load test. On an 8 GB machine Analytics gets 2 GB and the
    Historian 3 GB; Alarms no longer answers 500 with many alarms and people at once; long Historian
    reads no longer end in a 502; Operations shows only the live free disk.

  • Platform: the guided tour reaches its end on a phone, in the platform and in every app.

  • Platform: install and update.

    • APPS=all and --all-apps install every app.
    • Installing again, or a release after its candidates, needs no manual step.
    • --uninstall --purge no longer deletes another installation's images.
    • A backup restores on a machine with fewer CPUs.
    • Release bundles build again, and they carry the setup wizard.
    • The WSL and clean-VM first tries are fixed, including the certificate named after the WSL
      machine.
  • Platform: an app the installation left out no longer reads as broken.
    PLANTCRAFT_MCP=off and PLANTCRAFT_NOTEBOOKS=off in .env take effect.

  • Platform: charts. Trends keep their spikes and long trends come already reduced. Long
    tables sort by text in a fraction of a second.

  • Analytics: rounds and signal checks that could not reach the data are retried.

  • Alarms:

    • the flood count reads only the last minutes;
    • colours follow the dark theme.
  • Documents:

    • colours follow the dark theme.
  • Historian: the points export's file name is safe.

  • Models:

    • state files are written whole;
    • a study's ranking table scrolls on a phone.
  • View:

    • a process display opens in under a second (289 bindings in one read);
    • report tables scroll on a phone.

Security

  • Platform: ./install.sh --security-check.
    • 36 checks with stable ids, a score and JSON, JUnit, SARIF or evidence output.
    • A signed catalogue of checks.
    • Exceptions that expire.
    • Lynis and OpenSCAP when the host has them.
  • Platform: sessions.
    • Sign-out ends the session on the server and the browser's token in every app.
    • A fair sign-in throttle.
    • Sign-in no longer tells which usernames exist.
  • Platform: the assistant.
    • A daily limit on what it reads for each person, and extraction flags in the audit log.
    • It no longer says it created what it only prepared.
    • Links to other sites are shown as text.
    • Documents keeps documents that look confidential from it.
  • Analytics and Alarms: the code sandbox. Four ways out of block and rule code are closed,
    and Alarms' rule code runs in a container of its own.
  • Documents: files are read in a worker with time and memory limits, no network
    and no file writes.
  • Platform: the API surface is smaller.
    • GET /api/users gives non-administrators names and roles only.
    • openapi.json is served only on request.
    • Apps refuse cross-site cookie writes.
    • Junk input answers 4xx, not 500.
  • Platform: the bundle and its images.
    • install.sh checks SHA256SUMS.sig before docker load.
    • --export-backup writes an encrypted copy of a backup.
    • Fresher proxy (Caddy 2.11.6), installer and runner images.
    • pyasn1 0.6.5 and pypdf 6.21.4 fix known CVEs.
  • Platform: app keys with scopes (needed before third-party apps). A key may hold less than
    its app, for example a read-only key for a collector; each API v1 route needs a permission both
    the app and the key hold. PLANTCRAFT_APP_PERMISSIONS=strict gives an app that declared no
    permissions none.
  • Platform: the public demo's visitor password is no longer in .env (PC-SEC-02): it lives
    in data/public-demo-password, handed to the platform as a Compose secret.

Downloads

Bundle For Size SHA-256
plantcraft-0.6.0-linux-amd64-bundle.tar.gz most servers 2,304,451,341 bytes (2.1 GiB) 9a4e2d8c77fae44801357a8ce69dd5d89c4483cfa91036d720ba359101d1c3fe
plantcraft-0.6.0-linux-arm64-bundle.tar.gz ARM servers and Apple silicon 2,234,318,360 bytes (2.1 GiB) a2177876deb1f198f348d542ad34edfe03ae04ca5c7c0fcd1f83fd4a5978b29d

Each bundle comes with its .sha256 and .sha256.sig. docs/verify-a-release.md explains how to check them with ssh-keygen as release@plantcraft (OpenSSH fingerprint SHA256:9l/yDgR8/Pzel1pncxrXz2IGCIhFirKpDT78tO49fG8).

Upgrading

Run ./install.sh from the new bundle. Data, settings and accounts are kept, and the previous version stays available for rollback (./install.sh --rollback).

Each app's own changes are in its CHANGELOG.md under apps/.

Joining the parts

GitHub limits each file to 2 GiB, so each bundle comes in parts. Download every part of your processor, join them, then check the hash and signature as usual:

cat plantcraft-0.6.0-linux-amd64-bundle.tar.gz.part-* > plantcraft-0.6.0-linux-amd64-bundle.tar.gz