Reference deployment
PV in the petroleum sector — 14 MWp, commissioned 2023.
LumeTrax® is running on a 14 MWp PV project in the petroleum sector, commissioned 2023. The deployment context — operating-data discipline, OT/IT boundary enforcement, lender-grade reporting — informs every plant we scope. Customer name held confidential at the customer's preference.
Customer name is confidential. Operating context, architecture, and modules deployed are described below.
- 14 MWpPlant capacity
- 2023Commissionedrunning in production since
- PVAsset classpetroleum-sector deployment
- 4Modules deployedCore · Asset Manager · Vision · Audit
What the deployment is.
The asset is a 14 MWp utility-scale PV solar plant, commissioned in 2023, deployed within a customer operating in the petroleum / energy sector. The customer's operational context required lender-grade reporting, OT/IT segregation under enterprise security policy, and integration with existing customer infrastructure. Customer name and specific location held confidential.
The project entered LumeTrax operations as the customer's primary operating layer for the asset — SCADA, maintenance workflow, performance analytics, and lender-grade reporting under one tenant. The deployment shape was selected after a Core questionnaire pass that surfaced the customer's specific OT/IT segmentation requirements, identity-provider integration, and reporting cadence.
The deployment has been running in production since commissioning. Customer-specific outcome figures are not published at the customer's preference, but the operational structure, the architecture, and the methodology applied are described here.
Modules in production.
| Module | Role on this asset |
|---|---|
| Core — Industrial SCADA & Plant Control | Real-time plant supervision, control authority matrix, multi-protocol ingestion, alarm philosophy enforcement, high-resolution historian |
| Asset Manager — O&M Workflow | Alarm-to-ticket routing, preventive + corrective programs, SLA tracking, downtime classification per attribution category |
| Vision — Performance Analytics | Weather-normalized PR, availability, loss attribution, source-linked figures, periodic performance reporting |
| Audit & Assurance | Engaged for periodic technical review per customer-agreed cadence |
Optimizer is not in scope for this asset (PV-only configuration). Where the customer adds BESS or DG to the deployment in future, Optimizer becomes a configurable activation under the same tenant.
How the deployment is built.
- OT layer: plant device layer ingested over standard protocols (Modbus, IEC 61850, SunSpec where applicable, OEM APIs for vendor-specific extensions)
- Edge gateway: industrial-grade hardware on-site, with offline buffering and OT/IT segregation enforced at the network layer
- Deployment shape: customer-selected per the questionnaire (cloud / private / on-prem / air-gapped — specific shape held confidential)
- Identity: integrated with customer's enterprise identity provider via SAML / OIDC; MFA enforced; RBAC scoped per customer policy
- Data residency: pinned per customer regulatory requirements
What gets produced.
| Cadence | Deliverable | Audience |
|---|---|---|
| Real-time | Operator dashboard (SCADA view, alarm panel, one-line diagram) | Plant operator team |
| Daily | Operations summary (energy delivered, availability, alarm count, open tickets) | O&M lead, asset manager |
| Monthly | Performance report (PR vs. weather-normalized expected, availability decomposition, loss attribution waterfall, classified downtime, OPEX summary) | Asset owner, asset manager |
| Quarterly | Lender-format performance pack (DSCR-relevant metrics, contracted-vs-actual, evidence pack, period-over-period comparability) | Lender, asset-management committee |
| Per-event | Warranty-claim evidence packs (alarm chronology, historian snapshot, work-order trail, parts consumed, attribution) | Owner, OEM, contract counterparty |
Each deliverable's methodology is documented and source-linked. Customer-specific figures are not published; deliverable structure and source classification are.
Operational outcomes (anonymised, qualitative)
What changed in day-to-day operations.
The deployment moved the customer's operating model from multi-portal manual reconciliation to single-tenant operating layer for the asset. Specifically:
- Alarm response moved from email-based escalation to alarm-to-ticket workflow with SLA tracking
- Performance reporting moved from period-end manual assembly to continuous methodology-documented automation
- OEM warranty claims assembled from the work-order trail and historian record automatically rather than reconstructed after the fact
- Lender reporting standardised to a single quarterly template, source-linked
Quantified outcomes are at customer preference — not published.
Why this deployment is referenceable for lender-grade context.
The deployment exercises every layer of the financial-grade methodology LumeTrax claims publicly: source-classified outputs, weather-normalized performance, classified downtime per attribution category, and audit-ready evidence packs.
A lender or independent engineer asking "can LumeTrax actually deliver this on a real asset?"has a live deployment to point at — even though the customer name itself is not disclosed. Independent technical reviews (Audit & Assurance) on this asset run on the same operating-data record the platform produces, distinguishing measured / calculated / assumed / judged data per the methodology page.
What this deployment taught the platform.
- The right OT/IT segmentation pattern for petroleum-sector enterprise security policies
- Identity-provider integration patterns for customers operating under enterprise IdP frameworks
- Methodology refinements in availability decomposition and counterparty allocation that have since been generalised across the platform
- Reporting-cadence preferences for asset owners with parallel financing structures
Specific learnings are not customer-disclosable. The methodology and architecture have evolved with this deployment as a reference point.
Engagement