
PHASE 1 — PROOF OF CONCEPT • INDUSTRIAL SENSING One 30-day methodology, six tracks — Monitoring, Measurement, Automation, Dashboards, SCADA-Lite, Fleet Management. The PoC validates whether Banalytics can operationally wrap your existing devices, module, or workflow — without changing your core algorithm, IP, or business logic. Mock or replayed inputs are acceptable; no device-specific deployment work is included. All six tracks below follow the same 30-day methodology; only what's being validated changes by track. • High-level architecture and module boundary • Input/output categories and interface contract • Mock/replayed data flow through your module, algorithm, or ruleset • Track-specific validation (see below) • Failure-state demonstration and pilot scoping • Hardware procurement • Vendor-specific or high-speed device integration • On-site installation or mechanical integration • Production hardening or SLA commitments • Unfunded deployment-specific engineering Banalytics — banalytics.live — [email protected]
Open the catalog to page 1PHASE 1 — PROOF OF CONCEPT • INDUSTRIAL SENSING Decision gate Days 1-5 Select one concrete use case; define 1-page PoC scope inputs, outputs, and success criteria for the chosen track. Problem and technical owner agreed. Build the track-specific validation (see Working architecture-level below) using mock/replayed data. PoC Days 15-20 Test failure behaviour relevant to the Technical acceptance note track (missing data, rule misfire, sync loss, etc.). Degraded/invalid states agreed. Days 21-25 Define the real-device pilot: hardware, Pilot SOW / proposal site, integration work, schedule, commercial...
Open the catalog to page 2PHASE 1 — PROOF OF CONCEPT • INDUSTRIAL SENSING Event Manager rule logic and action types (Modbus write, relay, MQTT, notification) using mock trigger conditions, no real actuators. • Rules fire correctly against mock threshold/pattern conditions. • Each required action type (Modbus write, relay, MQTT, notification) demonstrated. • Event History captures every action taken during the test. • Failure/edge-case rule behaviour agreed. Which dashboard types (Cesium 3D globe, Mapbox/OSM 2D map, 3D Sphere, SVG custom panel) fit your use case rendered against mock data. • At least one dashboard type...
Open the catalog to page 3PHASE 1 — PROOF OF CONCEPT · INDUSTRIAL SENSING Hardware / Integration Partner Owns the sensing concept, measurement logic, control rules, or visualization requirements, and provides sample data plus a technical owner. Owns orchestration, monitoring, rules, dashboards, event history, and PoC coordination for the chosen track. If required for the funded pilot, owns project-specific field hardware, wiring, and mechanical/site integration. Commercial Boundary The PoC is a short architecture-validation step. It should not turn into unpaid customer-specific integration. Real hardware support, on-site...
Open the catalog to page 4