IT signs off. Your people build.
SensorUp is the system IT signs off on and the surface your people build on: one foundation, three layers, one way of working across every business domain.
- Studio build
- Autopilot agentic
- Warehouse foundation
How it works
Three layers, one way of working
The signal lands in the Warehouse. Studio prioritizes it against your operating plan. Autopilot runs the routine under supervision and routes each decision to the right team. You need all three, or it breaks.
Business domains
A finite set of building blocks, the same ones in every solution
The composable units the layers are built from, not product lines or separate databases. Hover any one to see what it does.
- Calculations Continuous calculation engines: emission rates, intensity, KPIs, derived as Observations land.
- Scenarios Modeling and forecasting: ESG projections, trajectories, forecast-vs-actual variance.
- Events Lifecycle-tracked occurrences: emission events, pressure exceedances, incidents.
- Work Process orchestration: issues, workflows, LDAR sequences, repair orders, escalations.
- Metrics Tracked targets: KPI definitions, methane-intensity targets, performance metrics.
- Reports Automated reporting and document generation: OGMP 2.0, TCFD, and ESG outputs.
- Compliance Obligations and tracking: regulatory programs, schedules, and status.
- Agents Managed, supervised AI agents with an audit trail. Engaged and monitored, not unleashed.
- Cora The copilot: chat-driven composition and the agentic builder experience.
- Solution Builder Compose solutions with Cora, binding domains to resources.
- Workflows Routing, escalation, and scheduled or event-driven automation.
- Assets Infrastructure hierarchy: facilities, wells, compressors, tanks, valves, sensors.
- Integrations Connectors: SCADA (PI, CygNet), ERP (SAP, Maximo), satellite, continuous monitors.
- Datasets Structured collections: OGI definitions, CEMS configs, satellite schemas, tag registries.
- Relationships Entity links across domains: Asset HAS Events, Work RESOLVES Event.
- Reference Library Reusable factors, rule sets, methodologies, and equipment taxonomies.
- Ledgers Immutable chain-of-custody: credit ledgers, compliance audit trails, verification records.
- Approvals Multi-stage review and sign-off across the record.
Fits how you operate
It fits what you already run, and all of it stays yours
No rip-and-replace, nothing new on your control network. It reads the systems you already operate, your own team runs it, and your data is yours to take with you.
It reads the systems you already operate
Historians (PI, CygNet), ERP (SAP, Maximo), continuous monitors, satellite, and OGI. Read-only, so nothing new is opened up on your control network.
Your people change it, not a vendor
The next solution, a changed workflow, an adjusted calculation: your operations team builds it in Studio, from the same blocks every shipped solution uses.
Your data leaves with you
The full operational record exports on demand, complete. Access runs through your own login. If the software stops earning its place, your data walks out with you.
Security and compliance
Because your security review will ask
Request a technical demo
Bring your stack diagram and your second problem. We'll name which domains bind it, against your actual asset hierarchy, and tell you what configuration can and cannot do before you scope the work.