Integrations and source ownership

• Meter data. Import readings from the meter data service or data logger with the meter number and read time. Duplicate deliveries are ignored, so a resent file is safe.

• Turbine controller and SCADA. Import turbine production intervals, and alarms that should open events, from the control system. Instrument data and turbine control stay in that system.

• Finance and settlement. Send validated energy and tariff history to your finance system for invoicing and settlement with offtakers.

• Identity provider. Map staff and contractors to user accounts so every record shows who entered it.

Each connection needs an agreed source of truth, a field mapping, an event identifier and a retry policy. Keep credentials in the approved secret store with the smallest scope that works. A repeated delivery must not create a second reading, interval or event. Rejected records wait in a queue with the original identifier and a visible reason.

Reconcile reading counts and energy totals with the meter operator each day during the pilot. Test a resent file, a meter reset, a dropped connection and a revoked credential before turning on schedules. Availability depends on each provider’s interface, commercial access and configuration.

Use the implementation plan to agree integration acceptance criteria.