Files
scadaproj/impeccable/ScadaBridge.md
T
2026-11-13 14:40:42 -05:00

30 KiB
Raw Blame History

ScadaBridge — shared-theme review and proposed updates

Reviewed 2026-11-12. Mode: Operate. Source baseline: ScadaBridge 482ac665; shared Theme package pinned to 0.5.3 in Directory.Packages.props:120. This is a source-backed Impeccable audit and refinement proposal, not a replacement visual identity or production change.

Open topology mockup · Open audit mockup · Suite index

Direction and integrity verdict

Keep the shared chassis; consolidate the page-level patterns. ScadaBridge already consumes ThemeShell, ThemeHead, ThemeScripts, IBM Plex, the neutral Technical-Light palette, the 220px rail, and shared button sizing. Its complex operational screens have legitimate domain-specific behavior. The main inconsistency is underneath that chrome: stock Bootstrap dark table headers, repeated h4 page titles, custom badges, local dark-mode tokens and several modal implementations create different rules inside one application.

Preserve the current information model: templates, site/area/instance topology, deployment staleness, operational audit, and two-person secured writes. Keep existing role checks, replay-only auditor access, transaction boundaries, confirmation behavior and server authorization. The recommendations below change presentation and clarify behavior; any proposed new backend data is explicitly a later feature.

No P0 blocker was established. Seven P1 findings and eight P2 findings are documented below. P1 means a concrete accessibility, interpretation, or recovery defect to resolve before relying on the affected workflow; it does not imply every route is unusable.

Evidence and limitations

  • Inspected current source, package pins, shell, shared controls, route declarations, global/scoped CSS and selected codebehind. No browser session against a running ScadaBridge deployment was available in this review; no server was started and no operational action was executed.
  • The repository's PNG search found architecture diagrams, not reliable current UI goldens. Findings about layout and focus behavior are source findings requiring the runtime checks specified below.
  • All 44 routable page components (57 route declarations, including aliases and create/edit variants) were inventoried; deep review concentrated on the shared controls and the principal topology, dashboard, health, design and audit workflows. The inventory at the end distinguishes deep inspection from surface scanning. Every route is included; this is not a claim that all backend behavior was executed.
  • The mockups use illustrative names, states, counts and timestamps. They demonstrate proposed presentation and safe local interactions only. Their identity and environment labels are examples, not deployment facts.
  • Detector run: impeccable detect --json <CentralUI source directory>, recorded in ScadaBridge-detector.json. It produced 21 warnings: two authored side-border findings, nine generated copies, ten third-party Monaco findings. The last 19 are not independent application defects. Monaco worker strings such as <img> are syntax-service content, not broken app images; do not rewrite vendored Monaco to silence the detector.

What to preserve

  • Components/Layout/MainLayout.razor:11 delegates to ThemeShell with ScrollNav="true", so a long role-aware nav scrolls independently and the session footer remains available.
  • Components/Layout/NavMenu.razor gates sections and items by actual policies. The Flow Debugger route distinguishes audit replay from live execution (Pages/Deployment/FlowDebugger.razor:6–9, 99–145). Reuse those policies for related shortcuts.
  • Components/Shared/DialogHost.razor:97–159 already handles initial focus, focus return, Escape and Tab wrapping. Extend this implementation instead of replacing it with another ad-hoc modal.
  • Components/Shared/TreeView.razor:71–100 includes tree position/state semantics and keyboard handling; TreeView.razor.css:91–98 follows roving focus. Preserve these details in a visual refresh.
  • Pages/Deployment/Topology.razor:106–108 truthfully explains loaded-branch search and paging. Keep that qualification visible after consolidating the toolbar.
  • Site management already distinguishes no configured sites from no matches and offers an initial action (Pages/Admin/Sites.razor:76–96). Use that pattern elsewhere.
  • Topology polling uses a gate and bounded staleness checks (Topology.razor:149–155, 244–250). No recommendation here removes those protections.
  • Dark mode is applied before paint in ScadaBridge.Host/Components/App.razor:13–24; keep this protection while moving palette ownership upstream.

Findings and acceptance criteria

Paths below are relative to ScadaBridge/src/ZB.MOM.WW.ScadaBridge.CentralUI/ unless the Host or repository root is named. Source line references identify the reviewed baseline.

SB-01 · P1 · Name dialogs and prompt controls

Evidence: Components/Shared/DialogHost.razor:14–24 has role="dialog" and aria-modal="true" but no accessible name; :37–42 renders a prompt label without a matching input id/for. Existing focus management is present and must be retained.

Impact: A screen-reader user arrives at an unnamed dialog and may not receive the prompt context. This affects the reusable confirmation/prompt surface.

Owner: Local markup correction; propose a shared modal accessibility contract in Theme. Recommend: Give the title a unique id, reference it through aria-labelledby, link explanatory content with aria-describedby where appropriate, and connect each prompt label to its input. Accept when: confirm, caution, destructive and prompt dialogs announce their title and purpose; Escape and focus return still work; unique ids hold if custom dialog content contains fields. WCAG 1.3.1 / 4.1.2. Command: $impeccable harden.

SB-02 · P1 · Make the audit drawer a complete keyboard interaction

Evidence: Components/Audit/AuditDrilldownDrawer.razor:12–41 manually displays a backdrop and offcanvas; it has tabindex=-1 but no dialog role, modal state, title relationship or key handler. Its .razor.cs contains presentation parameters and close callback only; the parent page renders it directly at Pages/Audit/AuditLogPage.razor:119.

Impact: Visually modal audit details do not establish modal focus semantics or a keyboard return path. A focusable container alone does not transfer focus.

Owner: Local drawer adapter, shared overlay contract. Recommend: Use the existing dialog focus helpers or a tested offcanvas adapter to move/trap/restore focus, provide an accessible name, and close on Escape. For a nonmodal desktop side inspector, remove the blocking backdrop and explicitly use nonmodal semantics instead; choose one behavior per breakpoint and document it. Accept when: open from a row using keyboard, inspect/copy details, close with Escape, and return to the originating row without reaching blocked background controls. WCAG 2.1.1 / 2.4.3 / 4.1.2. Command: $impeccable harden.

SB-03 · P1 · Associate labels throughout reusable forms and filters

Evidence: Components/Shared/DataTable.razor:10–11 has placeholder-only search; Pages/Deployment/Topology.razor:75–77 and Pages/Admin/Sites.razor:88–91 do likewise. Pages/Design/DataConnectionForm.razor:38–78, Pages/Design/TemplateEdit.razor:358–363, and Pages/Deployment/FlowDebugger.razor:40–42, 54–56, 78–80 place labels next to fields without id/for connections. Components/Audit/AuditFilterBar.razor:31–74 labels dropdown groups visually but does not pass label relationships into MultiSelectDropdown.

Impact: Field names become ambiguous in screen-reader forms mode and after typing removes placeholder text.

Owner: Local callsites plus shared field/control API. Recommend: Persistent labels with id/for or aria-labelledby; add label-id parameters to custom controls and wire errors/hints with aria-describedby. Accept when: every rendered input/select/textarea and custom picker exposes the visible label as its accessible name; field errors are connected and the whole form works at 200% zoom. WCAG 1.3.1 / 3.3.2 / 4.1.2. Command: $impeccable harden.

SB-04 · P1 · Specify the time zone instead of relabeling local inputs UTC

Evidence: Components/Audit/AuditFilterBar.razor:94–104 says the input contains local wall time but labels it “From (UTC)” / “To (UTC)”. AuditFilterBar.razor.cs:168–201 applies DateTimeKind.Local then ToUniversalTime(). The Host uses InteractiveServer in ScadaBridge.Host/Components/App.razor:29, so this conversion uses the server's local zone, which is not proof of the operator's browser zone.

Impact: An operator can select the wrong audit window while reading a UTC label. Cross-zone deployments require particular attention; the actual deployed zone mismatch has not been measured.

Owner: Local filter conversion, shared date-range contract. Recommend: Choose either explicitly UTC wall-clock inputs with UTC parsing, or browser-zone inputs with a displayed zone/offset and explicit conversion. Store and query UTC consistently. Apply the same policy to notification/site-call reports and timestamp tooltips. Accept when: a known event is found for UTC, Indianapolis and a different browser/server zone, including DST boundaries; labels, picker values, query boundaries and exported timestamps agree. Command: $impeccable clarify then $impeccable harden.

SB-05 · P1 · Distinguish unavailable dashboard counts from zero

Evidence: Pages/Dashboard.razor:104–117 catches any count-loading failure without surfacing it and sets _loaded=true; integer defaults remain zero. Four KPI cards at :23–55 then display those values as counts.

Impact: A failed API-key or repository lookup can look like an empty configured system. Partial success can also leave later counters at zero.

Owner: Local dashboard state. Recommend: Model each counter as loading/success/unavailable separately; retain successful results and offer a retry for failed counts. Keep “0” exclusively for a confirmed empty response. Accept when: fail each lookup independently and after partial success; failed counters show “Unavailable” with recovery, successful counts remain valid, and screen readers receive a restrained status update. Command: $impeccable harden.

SB-06 · P1 · Give toast dismissal a name

Evidence: Components/Shared/ToastNotification.razor:20 renders an icon-only close button without aria-label or text.

Impact: Users navigating by control name cannot identify the dismiss action. Owner: Local toast, shared feedback contract. Recommend: Label it “Dismiss [toast title]” and preserve the live region. Accept when: each notification's close button has a meaningful name and focus remains sensible when the notification disappears. Review the five-second default at :28, 75 for actionable errors: persistent inline errors should hold important recovery instructions instead of relying on an expiring toast. WCAG 4.1.2. Command: $impeccable harden.

SB-07 · P1 · Use readable semantic foregrounds in both themes

Evidence: local dark palette wwwroot/css/site.css:117–153 sets --ink-faint:#6b727c on --paper:#1b1d21 and --card:#25282d; normal small text uses the faint token in Pages/Deployment/FlowDebugger.razor.css:16–20 and pending-update details use it at site.css:178–181. Calculated flat-pair contrasts are approximately 3.5:1 on paper and 3.0:1 on card, below 4.5:1 for normal text. Light-state text also inherits shared status foregrounds, e.g. .fd-chip.completed at FlowDebugger.razor.css:36.

Impact: Important state labels and update details are hard to read, especially on dim operator displays.

Owner: Theme first, local migration. Recommend: Separate decorative dot/border colors from text colors; use accessible muted/status foreground tokens and publish the light/dark palette together. Keep labels as well as color. Accept when: every actual foreground/background pair used for small state labels, hints and empty states reaches 4.5:1, focus and relevant controls reach 3:1, in both schemes. Runtime computed styles remain to be checked. WCAG 1.4.3. Command: $impeccable colorize.

SB-08 · P2 · Unify page titles, tables and button hierarchy

Evidence: Pages/Dashboard.razor:11, Pages/Admin/Sites.razor:26 and Pages/Deployment/Topology.razor:72 use h4 as the page heading; Components/Shared/DataTable.razor:29–30 uses stock table styling and table-dark within the light shared world. The shared Theme provides .page-head / .data-table patterns. Topology.razor:74–98 has multiple equally weighted toolbar actions.

Impact: Switching between domain screens changes hierarchy and table density even though the rail remains familiar.

Owner: Shared page/table/action patterns, local adoption. Recommend: One semantic h1 per page with a compact shared visual style; a title/description/action row; consistent hairline table headers; one primary action for the task; move lower-frequency toolbar actions into a native disclosure/menu. Keep domain table features in ScadaBridge. Accept when: page titles and table headers match the sister-app gallery at the same viewport, semantic heading order is valid, and primary/secondary/destructive actions are distinguishable without color alone. Command: $impeccable layout.

SB-09 · P2 · Contain shared tables and correct the empty count

Evidence: Components/Shared/DataTable.razor:29 renders a table without a scroll wrapper; some consumers may wrap it externally, but the component itself gives no guarantee. The final count line :89–90 calculates first row as 1 even when there are no filtered items, producing “Showing 1–0 of 0 items”.

Impact: Wide data can widen a narrow page, and an empty count is contradictory. Owner: Local reusable table; propose shared table-container styles only. Recommend: Add a labelled/focusable scroll container where overflow occurs, retain semantic headers and a visible result count, and render “0 items” for an empty result. Accept when: a long identifier plus multiple columns stays inside the main region at 390px/200% zoom; keyboard users can inspect overflow; zero, one, filtered-zero and final-page counts are correct. Command: $impeccable adapt.

SB-10 · P2 · Show role-appropriate dashboard destinations

Evidence: Pages/Dashboard.razor:62–90 unconditionally links to health, configuration audit and templates for every authorized user; Components/Layout/NavMenu.razor applies OperationalAudit / RequireDesign to the corresponding navigation items.

Impact: Users see shortcuts that the main navigation correctly hides, then reach a denied page. Owner: Local dashboard. Recommend: Use the same policies as the rail and prioritize a small set of permitted tasks. Do not weaken route authorization. Accept when: Viewer, Designer, Deployer and Administrator identities get matching shortcuts and nav visibility; a role with no design access sees no create/edit promise. Command: $impeccable clarify.

SB-11 · P2 · Reduce dashboard and health scanning effort

Evidence: Pages/Dashboard.razor:23–94 leads with four equal KPI cards and three equal destination cards. Pages/Monitoring/Health.razor:201–234 adds equal count cards before per-site detail cards at :238 onward.

Impact: Configuration inventory and operational exceptions have equal visual weight. Operators must scan many containers to find the site needing action.

Owner: Local information hierarchy, shared section/list styles. Recommend: A compact facts line for inventory, then an actionable site/instance status list ordered by severity, with a clear route into existing detail. Counts should summarize the list rather than become another dashboard layer. New aggregated backend measures are optional follow-up work, not implied by the mockups. Accept when: an operator can find a stale deployment or offline site without opening every card; all existing health detail remains reachable. Command: $impeccable distill.

SB-12 · P2 · Make dense topology controls work for touch and short viewports

Evidence: Components/Shared/TreeView.razor.css:11–30 documents ~32px rows and a 20px toggle slot; Pages/Deployment/Topology.razor:110 hard-codes max-height:calc(100vh - 240px) for its scrolling region. The real header/toolbar height changes on small screens and at zoom.

Impact: Narrow, wrapped toolbars can leave an unnecessarily small nested viewport; small tree toggles are difficult to hit on a plant-floor tablet. Owner: Local tree sizing and page layout; shared density tokens. Recommend: Keep compact fine-pointer desktop density, enlarge hit regions for coarse pointers, and use available-space flex/grid layout with dvh support rather than subtracting a guessed header height. Accept when: touch rows/actions have at least 44px practical hit height, 390px/768px and short landscape screens retain usable content, and focus is never hidden under headers. Command: $impeccable adapt.

SB-13 · P2 · Move local dark palette upstream without duplicating it

Evidence: wwwroot/css/site.css:117–172 defines the full dark palette; MainLayout.razor:3–10 explains why an inline shell accent previously prevented dark overrides.

Impact: ScadaBridge is responsible for a separate palette/interaction contract, so sister projects can drift even after adopting the same Theme package.

Owner: Theme package with ScadaBridge migration. Recommend: Publish light/dark semantic tokens and a theme-preference contract from Theme; support intentional per-product accent values through both schemes. Migrate local tokens only after package rollout, preserving saved sb-theme preference or a documented migration. Accept when: the same theme fixture renders light/dark status, forms, tables, dialogs and nav for every consumer; no shell inline accent bypasses the selected scheme. Command: $impeccable extract.

SB-14 · P2 · Simplify audit filters without losing precision

Evidence: Components/Audit/AuditFilterBar.razor:15–171 displays channel, kind, status, site, node, time range, instance, script, target, actor, execution id, parent execution id, errors-only and actions in one wrapping grid. :136–153 explicitly notes malformed GUIDs silently drop their constraints.

Impact: The common case is hard to scan; a mistyped exact id can silently broaden the query.

Owner: Local filter model/presentation; shared toolbar/disclosure styles. Recommend: Keep time range, site, outcome and Apply visible; use “More filters” for correlation and advanced fields with an active-filter count. Show a persistent applied-filter summary. Reject invalid exact ids inline instead of omitting them. Keep existing supported query semantics. Accept when: common audit search fits a predictable first row at desktop width, hidden active filters remain visible in the summary, invalid ids never run a broader search, and resetting returns all controls to a known state. Command: $impeccable distill, $impeccable harden.

SB-15 · P2 · Consolidate flow/audit status treatment

Evidence: Pages/Deployment/FlowDebugger.razor.css:36–38, 123–124 mixes Theme status colors with Bootstrap danger tokens; Components/Shared/FlowTraceList.razor.css:12–15 does likewise. The detector confirms thick side borders in Components/Audit/AuditEventDetail.razor.css:20 and FlowDebugger.razor.css:77.

Impact: The same outcome is drawn differently in graph, trace, detail and suite status components; thick colored edges compete with the actual event message.

Owner: Shared semantic status tokens, local domain labels. Recommend: Keep Completed/Predicted/Pending/Parked/Timed out/Failed labels and existing distinction between an error log and a failed step. Map each label to the shared status text/background/border pattern; use a thin surrounding rule and explicit error heading instead of a thick side bar. Accept when: graph, trace and inspector use the same state vocabulary/palette, and predicted/replayed/live results remain unmistakable. Command: $impeccable colorize then $impeccable polish.

Screen-by-screen follow-through

Family Recommended presentation after shared fixes Required states to verify
Dashboard Compact inventory facts, role-appropriate task links, status-first operational handoff Loading per count, partial failure, true zero, no permitted design actions
Sites / LDAP / API keys Shared page header, named filter, consistent list/detail actions; keep site artifacts distinct from instance staleness No configured records vs no matches; denied role; failed save/delete; long identifiers
Templates / shared scripts / schema Retain tree/editor structure; shared headings and field labels; selected-object context near save Unsaved changes, invalid script/schema, inherited value, empty folder, conflict
Data / DB connections / certificates / external systems / API methods Same field widths, hint/error placement, test/save hierarchy and certificate detail pattern Offline test, invalid endpoint, expired/untrusted cert, secrets omitted, pending mutation
Bundle export/import Retain preview, blocker text, passphrase and environment safeguards; group stages in a readable progress sequence Invalid bundle/signature, unresolved mapping, blocker, review, apply failure, success
Topology / create/configure instance Shared master/detail layout and compact toolbar; visible loaded-search scope and staleness Never deployed, current, stale, branch loading, no matches, unavailable staleness
Deployments / debug / Flow Debugger Same status strip and inspector; visually separate live execution from replay Active/standby refusal, running, pending outcome, truncated event list, error log on successful step
Health / alarms / event logs / parked messages Severity-first index, clear last-successful timestamp and freshness, one detail affordance Offline vs unknown, active errors vs historical counts, retry in progress, failed retry
Audit / execution tree / configuration audit Common zone policy, applied filters and count, accessible drawer, consistent correlation links Invalid GUID/time range, no matches, query failed, partial payload, redacted data
Notification lists / SMTP / SMS / notification reports/KPIs / site calls Shared filter and form rhythm, quiet summary before detailed delivery/call results Unconfigured channel, test failure, no activity, partial delivery, paging/export
Secured writes Preserve Operator/Verifier separation and server validation; show target/value/requester before action Self-approval disabled, pending, rejected, failed relay, unauthorized, expired request
Login / session / reconnect Keep static login POST and anti-CSRF; same form/status patterns and explicit recovery Invalid login, expired session, reconnecting, reconnect failed, draft preservation
Embedded Secrets UI Shared component should follow the Secrets review; ScadaBridge owns host navigation/auth context only See Secrets report; never put actual secret values in fixtures

Delivery order

  1. Shared foundation: agree on accessible semantic text/status colors, light/dark palette, density, page header/table/action/feedback/overlay/time-range contracts. Ship Theme additions with visual fixtures; do not fork a ScadaBridge-only theme.
  2. Local correctness: SB-01–07, then invalid exact-id handling from SB-14. Verify screen-reader names, keyboard paths, per-count errors and time zones before stylistic cleanup.
  3. High-frequency operations: SB-08–12 and SB-14, beginning with topology, audit and health. Migrate one page per family, then apply that pattern to its siblings.
  4. Consistency: SB-13/SB-15 after the shared release; remove duplicate palette rules only when no remaining local callsites depend on them. Finish with $impeccable polish, then re-run $impeccable audit.

You can ask to run these one at a time, all at once, or in another order. This delivery deliberately contains recommendations and mockups only.

Runtime acceptance pass for implementation

Use desktop 1440×900, tablet 768×1024, phone 390×844, 200% zoom and both existing color schemes. Batch keyboard/screen-reader/focus/overflow/contrast checks with the first screenshots. Then perform one correction batch and one confirmation pass. Exercise Viewer/Designer/Deployer/Administrator/Operator/Verifier identities, live/replay restrictions, long names and payloads, empty and failed responses, reconnect, and differing browser/server time zones. Use read-only fixtures except a disposable test environment for mutation confirmation; do not treat these mockups as proof of production behavior.

Performance remains unmeasured: source protections exist, but no latency, browser long-task, rendering cost or bundle-waterfall claim is made. Inspect large topology/filter datasets and a substantial execution graph before deciding whether virtualization, render caching or lazy Monaco startup is needed.

Route inventory and review depth

“Deep” means markup plus relevant styles/state or shared-control code was inspected. “Scanned” means route, visible structure and recurring patterns were inspected; it does not imply complete state-machine review. Source file paths below are relative to Components/Pages/. Non-routable dialogs, pickers, tree, table, toast, filter bar, layouts and shell integration were also inspected as described above.

Page component Routes Depth
Admin/ApiKeyForm.razor /admin/api-keys/create
/admin/api-keys/{KeyId}/edit
Scanned
Admin/ApiKeys.razor /admin/api-keys Scanned
Admin/LdapMappingForm.razor /admin/ldap-mappings/create
/admin/ldap-mappings/{Id:int}/edit
Scanned
Admin/LdapMappings.razor /admin/ldap-mappings Scanned
Admin/SiteForm.razor /admin/sites/create
/admin/sites/{Id:int}/edit
Scanned
Admin/Sites.razor /admin/sites Deep
Audit/AuditLogPage.razor /audit/log Deep
Audit/ConfigurationAuditLog.razor /audit/configuration Deep
Audit/ExecutionTreePage.razor /audit/execution-tree Deep
Dashboard.razor / Deep
Deployment/DebugView.razor /deployment/debug-view Scanned
Deployment/Deployments.razor /deployment/deployments Scanned
Deployment/FlowDebugger.razor /deployment/flow-debugger Deep
Deployment/InstanceConfigure.razor /deployment/instances/{Id:int}/configure Scanned
Deployment/InstanceCreate.razor /deployment/instances/create Scanned
Deployment/Topology.razor /deployment/topology
/deployment/instances
Deep
Design/ApiMethodForm.razor /design/api-methods/create
/design/api-methods/{Id:int}/edit
Scanned
Design/ConnectionCertificates.razor /design/connections/{Id:int}/certificates Scanned
Design/DataConnectionForm.razor /design/connections/create
/design/connections/{Id:int}/edit
/design/data-connections/create
/design/data-connections/{Id:int}/edit
Deep
Design/DataConnections.razor /design/connections
/design/data-connections
Scanned
Design/DbConnectionForm.razor /design/db-connections/create
/design/db-connections/{Id:int}/edit
Scanned
Design/ExternalSystemForm.razor /design/external-systems/create
/design/external-systems/{Id:int}/edit
Scanned
Design/ExternalSystems.razor /design/external-systems Scanned
Design/SchemaLibrary.razor /design/schema-library Scanned
Design/SharedScriptForm.razor /design/shared-scripts/create
/design/shared-scripts/{Id:int}/edit
Scanned
Design/SharedScripts.razor /design/shared-scripts Scanned
Design/TemplateCreate.razor /design/templates/create Scanned
Design/TemplateEdit.razor /design/templates/{Id:int} Deep
Design/Templates.razor /design/templates Deep
Design/TransportExport.razor /design/transport/export Scanned
Design/TransportImport.razor /design/transport/import Deep
Login.razor /login Deep
Monitoring/AlarmSummary.razor /monitoring/alarms Scanned
Monitoring/EventLogs.razor /monitoring/event-logs Scanned
Monitoring/Health.razor /monitoring/health Deep
Monitoring/ParkedMessages.razor /monitoring/parked-messages Scanned
Notifications/NotificationKpis.razor /notifications/kpis Scanned
Notifications/NotificationListForm.razor /notifications/lists/create
/notifications/lists/{Id:int}/edit
Scanned
Notifications/NotificationLists.razor /notifications/lists Scanned
Notifications/NotificationReport.razor /notifications/report Scanned
Notifications/SmsConfiguration.razor /notifications/sms Scanned
Notifications/SmtpConfiguration.razor /notifications/smtp Scanned
Operations/SecuredWrites.razor /operations/secured-writes Deep
SiteCalls/SiteCallsReport.razor /site-calls/report Scanned

Rendered proposal previews

These are proposed UI artifacts with illustrative data, not screenshots of the current application. All use the same shared stylesheet. See verification and limits.

ScadaBridge

Interactive HTML · Desktop PNG · Mobile PNG

Proposed ScadaBridge desktop UI

ScadaBridge-Audit

Interactive HTML · Desktop PNG · Mobile PNG

Proposed ScadaBridge-Audit desktop UI