Release notes v0.2 (draft)

What the v0.2 release contains, what is planned, and its known limits.

Diagnosis

• Diagnosis prepared on every stop and trip, shown on the asset pages of the equipment the interlock acts on.
• The evidence card within 2 seconds, without a language model: first signs, the holding interlock, values, code changes and the last confirmed fix.
• Up to three ranked candidate causes, each with cited statements, evidence labels, values at the stop and now, and checks that confirm or rule it out; check results re-rank the candidates.
• Draft causes streamed while the answer is written; a stored answer reused when nothing has changed.
• Sequence of events with up to three ranked candidate initiating events, routine and start-up changes filtered, alarm floods grouped by cause, chattering alarms, and the step compared with good runs.
• Behavioural model replay of healthy and degraded variants (mdl://), validated on the site's own healthy runs; FMU models in an isolated runner.
• Wiring and drawing traces, drawing-set mismatches, spare parts and stock, confirmed diagnoses (dx://) as sources.
• Voice questions and HMI photo codes, processed on the edge PC. Answers in eleven languages; the interface in English and Polish. Light and dark themes, remembered per user; ISA-18.2 alarm priorities shown as word, shape and colour on every screen.

Around the diagnosis

• Shift handover with Markdown and PDF export; escalation package; work-order draft.
• Technician journal, versioned and cited; knowledge health and the gap log.
• Alarm health and recurring-fault reports; pilot measurements through the API.
• Workflows on plant events with a review inbox: alarm briefing, stop and trip evidence, maintenance briefing, return to service, part-change draft and 24-hour watch, shift handover, code change review, recurring fault.
• Early warnings: drift against good runs, slow starts, model residuals, models needing revalidation.
• Training mode (where the site turns it on): past stops replayed with the cause hidden, the trainee's diagnosis scored, nothing recorded as a diagnosis or KPI.
• Week-0 assessment report, site replay scoring, legacy code review report.
• Nightly evaluation on the fault library against a committed baseline, with tokens and estimated cost per answer for each model.
• Machine knowledge packs, signed by the builder, and anonymised field fixes shared only where the site turns it on.

Data and integration

• Code importers for Siemens TIA, STEP 7 Classic (STL and SCL sources with the symbol table), Rockwell L5X, RSLogix 500 and 5, Schneider XEF, Mitsubishi GX Works3, Omron Sysmac, B&R Automation Studio, PACSystems, CODESYS V3.5, PLCopen XML, and DeltaV, PCS 7 and 800xA exports; WinCC and FactoryTalk View HMI exports.
• Documents (PDF with OCR, DOCX, Markdown, text), spreadsheets by row, ECAD reports, DXF and DWG, DEXPI and Visio.
• Documents read in place, never copied, from a read-only file share or SharePoint Server (every profile), and from SharePoint Online, OneDrive and Google Drive (hybrid and client-cloud profiles, approved endpoints only), each through a read-only account and only the listed sites, libraries and folders; the document catalogue with revision, assets, index state and a cited summary per document; questions answered from one document; the source viewer showing where a document lives, an unreachable source and changes since a citation, with an optional cited-page cache.
• Live data over OPC UA, Modbus TCP, MQTT Sparkplug B, BACnet/IP, SNMPv3, DNP3 and IEC 61850; the Ignition and AVEVA PI (PI Web API) historians; live CMMS work orders from SAP PM, Maximo or SQL; alarm, trend, device-log and batch files.
• Read-only integration API (prepared answers, sequences of events, workflow results, site summary), an MCP bridge for AI assistants, and the site-group server.

Platform

• Deployment profiles: production (default), offline import, hybrid, client cloud, development.
• Named accounts, four roles, the site directory over LDAPS, the sign-in lockout, the append-only audit log.
• HTTPS only outside development; OPC UA Sign or SignAndEncrypt.
• Daily backup and restore; retention; signed offline updates and rollback; decommissioning erase with a deletion record.
• High availability with a standby edge PC.
• Personal data export and erasure.
• Offline licence bound to the edge PC, with 30 days' grace after expiry.
• Remote support window opened by a site administrator for at most 4 hours, with a one-off account and every request audited; off unless the site turns it on.
• Twelve demo plants, the pharma and biotech SIP skid (non-GMP) among them, switched in the running bench stack without a restart.

Planned, not in v0.2

• Administration screen and line overview home screen.
• Alarm-priority colours chosen per site.
• Connectors for other historians.
• A KPI panel on the Reports screen.

Known limits

• High availability has two nodes and no witness: a broken HA link alone makes both PCs active until an administrator resolves it.
• The Ignition alarm journal has no shelving or suppression transitions.
• The PI connector authenticates with Basic or a bearer token; Kerberos is not supported. PI event frames give active, acknowledged and cleared transitions only.
• SharePoint Server is read with basic or bearer authentication only, not NTLM or Kerberos. The SharePoint, OneDrive and Google Drive adapters are tested against in-process fakes of the services and still need confirming against a real tenant.
• Every code importer is in early access: each is confirmed against synthetic exports of the bench and demo plants and still needs confirming against a real site export (Siemens TIA, Rockwell L5X, Mitsubishi GX Works3, Omron Sysmac and PLCopen XML included). The STEP 7 Classic and CODESYS importers follow the vendors' documented formats.