6.6 KiB
Impeccable review of the SCADA web UI family
November 12, 2026. Recommendations and mockups only; production applications were not edited.
Start with the visual review index, then read the shared design contract. The priority is one Technical-Light family: IBM Plex, warm surfaces, restrained product accents, consistent labels/actions/statuses, and accessible behavior. The proposed mockups refine the existing identity.
Project deliverables
| Project report | Main mockup focus | Open HTML concepts |
|---|---|---|
| OtOpcUa | Fleet triage and Raw device workspace | OtOpcUa · OtOpcUa-Raw |
| MxAccessGateway | Faulted-session triage and repository context | MxAccessGateway |
| ScadaBridge | Topology freshness and audit investigation | ScadaBridge · ScadaBridge-Audit |
| HistorianGateway | Read history console and write separation | HistorianGateway |
| BTDB | Batch editing with clear validation and context | BTDB |
| ignitionoee | Router jobs, registry eligibility and native operator view | ignitionoee · ignitionoee-Registry · ignitionoee-Perspective |
| Overview | Read-only fleet status and freshness | Overview |
| Secrets | Metadata and target-aware secret rotation | Secrets |
| Theme | Common status, fields and interaction language | Theme |
Every report includes source evidence, prioritized findings, ownership, acceptance checks, coverage and limitations. Shared findings are defined once in the shared contract rather than counted again as independent defects in every application. Multiple mockups illustrate major workflows; they do not represent every audited route.
Detailed implementation plan
Implementation plan: standardize all seven existing bUnit projects on 2.7.2 first, then implement the shared theme and sister UI updates. Includes per-project chapters, dependency gates, regression checks, rollout and rollback.
First implementation priorities
- Shared Theme: readable status/secondary inks, associated labels/errors, complete accent states, focus/busy/reduced-motion behavior.
- Shared Secrets UI: isolate draft state when switching target secrets; give delete confirmations a full modal focus lifecycle.
- App P1 findings: keyboard-accessible row/tree workflows, named fields/dialogs, truthful failed/unknown states and unambiguous time-zone handling.
- Apply shared filter/table/detail patterns, responsive structure, and role-aware navigation locally while retaining each project's domain behavior.
- Release the reviewed shared version, migrate consumers, then validate real routes and finish with Impeccable audit and polish.
See project reports for the local priorities and exact locations. No proven P0 is asserted from the source scan. A prioritization label is a recommendation, not a filed issue or a release authorization.
Scope and review method
The user requested subagents. Three specialist agents reviewed the sister repositories in parallel; a second assignment covered BTDB and an independent pass checked Overview, Secrets and Theme. The parent established the shared contract, measured token contrast, reconciled coverage, and built/verified the artifact collection. Impeccable's installed 4.3.1 skill, audit guidance, Operate guidance and craft floor informed the work. This is a coordinated source audit and design recommendation exercise, not the formal critique command or a scored live accessibility assessment.
Active checkouts reviewed: OtOpcUa, MxAccessGateway, ScadaBridge, HistorianGateway, BTDB, ignitionoee, and hosted ZB.MOM.WW.Overview, ZB.MOM.WW.Secrets.Ui and ZB.MOM.WW.Theme. ignitionoee includes router, registry and Perspective operator views. Hidden worktrees, duplicate checkouts and generated/vendor code were excluded from the active route inventory. Detector invocations may have traversed vendored assets; reports identify those warnings rather than treating them as application findings.
Other hosted libraries (Auth, Audit, Health, Configuration, LocalDb, Telemetry, GalaxyRepository and SPHistorianClient) have no standalone authored web UI in this checkout. Shared Auth login rendering and domain audit/health consumers are included in the relevant reports. Database/CLI utilities, historical design-only siblings, unrelated Desktop directories, Bootstrap/Monaco implementations and generated outputs are not separate web projects in this review.
Source inventory records checkout HEADs, active route templates and source paths. Discovery counts include aliases; project reports distinguish route templates, routable components and support files. Route discovery is broader than deep manual inspection. Reports mark which families received deep inspection and which were scanned. Current source outranks old adoption docs and stale screenshot fixtures. A package pin in source does not establish a deployed version.
Mockups and verification
There are 13 responsive HTML concepts for 9 project/library reports, all using shared.css and local Plex fonts. Product-specific colors remain intentional: Historian green, BTDB teal and Overview purple. Perspective uses a native operator-oriented composition; the HTML is a visual specification for Ignition view/style resources, not a claim that the Blazor package runs there.
Mockups contain synthetic data, local filters/disclosures/previews and clear proposed-state labels. They send no SCADA queries or mutations. Controls representing production writes are explanatory, disabled or local demonstrations.
Each concept has full-page desktop and mobile PNGs in evidence/, linked in the visual index. Verification record describes the bounded browser checks and their limits. Contrast evidence contains current and proposed pair calculations. Source detector JSON is retained alongside reports. No mockup result proves production accessibility, backend behavior, production performance, or native Perspective runtime acceptance.
Open index.html in a browser; no package installation, build or server is needed. Keep the folder intact so its relative HTML/CSS/font/image links work.