An on-premises log ingestion and analysis appliance that instruments every hop between plant instrumentation and enterprise analytics — so missing, stale, or silently dropped data can be located and evidenced rather than estimated.
Between a field sensor and a corporate analytics platform, plant data passes through a long chain of independent systems: the device itself, the control network, the SCADA platform, an OPC or tag-translation layer, one or more databases, and a transport link to the enterprise. Each hop is owned by a different vendor, configured by a different team, and logged in a different format.
When a value stops arriving, nothing fails loudly. The historian records a gap or holds the last good value. Downstream reports still generate. Availability and performance calculations still return a number — the number is simply wrong, and remains wrong for as long as nobody isolates which hop dropped it. Losses get attributed to equipment that is operating correctly, and generation revenue is reported against data that was never actually measured.
At a utility-scale solar site, four plane-of-array irradiance sensors were reporting no values into SCADA. Because loss attribution is calculated against measured irradiance, the absence propagated into roughly 40% of the site's performance accounting. The instruments were inexpensive and the fix was straightforward — but the fault was invisible in every dashboard that consumed the data, and it persisted through a complete SCADA platform replacement.
This is not a SCADA problem and it is usually not fixed by replacing SCADA. It is an observability gap in the chain between systems, and it persists because no single system in that chain can see the whole path.
The ENERDYNE Log File Server is a dedicated on-premises appliance that collects the operational logs, event records, and data-transfer telemetry produced by every system in the plant data path. It timestamps and normalizes them into one queryable timeline, then correlates across systems to identify precisely where a value was last seen and where it stopped.
| Capability | Description |
|---|---|
| Multi-source log ingestion | Collects logs and event records from control, translation, database, and transport systems over standard mechanisms (syslog, file collection, database query, API read). |
| Normalization & time alignment | Parses heterogeneous formats into a common schema with a single time base, so events from different systems can be compared directly. |
| Continuity analysis | Detects gaps, stalls, frozen values, and last-known-good conditions per tag or per data stream, and reports the stage at which continuity was lost. |
| Chain reconciliation | Compares what each stage reports receiving against what the previous stage reports sending, isolating the hop where records are lost. |
| Retention & replay | Retains collected records for a configured period so intermittent and historical faults can be investigated after the fact. |
| Evidence export | Produces exportable findings suitable for root-cause documentation, vendor escalation, and process-improvement reporting. |
| Alerting | Notifies on configured continuity conditions via on-premises mechanisms selected at commissioning. |
The following statements describe the capabilities and constraints of the system as designed. They are provided to support a customer's own security review. Enerdyne LLC does not assert that this product is certified or compliant under any standard; applicability of any regulatory framework is determined by the registered entity operating the facility.
System integration, software authorship, and configuration: United States — Enerdyne LLC, a Montana limited liability company.
Hardware: assembled from commercial off-the-shelf components. The manufacturer, model, and country of origin of each hardware component are identified individually on the as-built bill of materials supplied with the delivered unit. Enerdyne does not represent the country of origin of components it does not manufacture, and supplies component manufacturers' documentation unmodified.
The appliance is built to order and sized to the collection volume and retention period of the target site. Final hardware selection, operating system baseline, and analysis component versions are recorded on the as-built configuration record delivered with the unit.
The Log File Server is a diagnostic instrument. It identifies and evidences where operational data is lost. Remediation of the identified fault — replacing an instrument, correcting a tag mapping, resizing a server, repairing a link — is separate scope, performed by the responsible system owner or quoted separately.
| Part Number | Description | Scope |
|---|---|---|
EDY-LFS-100 | ENERDYNE Log File Server — single-site license | One facility |
EDY-LFS-500 | ENERDYNE Log File Server — fleet license | Multiple facilities, quantity per agreement |
EDY-LFS-100-C | Commissioning, integration, and operator handover | Per deployment |
EDY-LFS-100-S | Support and tuning term | Per term |
On-premises log ingestion and analysis appliance for industrial control system data pipelines. Collects, timestamps, normalizes, and retains operational log and event data from plant control, historian, and data-transport systems for the purpose of diagnosing data-integrity and data-continuity faults between plant instrumentation and enterprise analytics. Read-only data consumer; no write path to control systems. Integrated in the United States by Enerdyne LLC, Montana.
The Log File Server establishes trustworthy operational data capture at a single site. Where a customer subsequently wants fleet-wide historical retention and pattern-based fault analysis across that data, the ENERDYNE Virtual Plant Operator (EDY-VPO-100) operates on the same one-way capture foundation. The Log File Server is a complete product on its own and does not require the Virtual Plant Operator.
Configuration, pricing, and a site-specific data-flow diagram are prepared per facility.
Contact Enerdyne