AURAAutomated Unified Reporting & Aggregation Platform

No. AURA reads OPC tags on a read-only connection and has no capability whatsoever to write to a DCS, PLC or SCADA system. Nothing is installed on control hardware. It runs on a separate server inside your network and the plant continues exactly as it does today. This is a design constraint rather than a configuration setting — the write path does not exist in the software.

None. AURA runs on a server inside your firewall and writes the report to your local shared drive over the LAN. There is no internet path, no cloud service and no external transfer of any kind. There is nothing to leak because there is nowhere for data to go. For groups who do want head-office consolidation we can add a controlled one-way replication of aggregated figures only, and that is an explicit decision you make, not a default.

Yes, and we insist on it for the first release. Matching the format your management already reads removes the adoption problem entirely — nobody has to learn anything, and the change is invisible except that the file arrives earlier and is always correct. We have reproduced genuinely complicated multi-sheet templates with merged cells, conditional formatting and embedded charts intact. Improvements to the report come later, once trust is established.

Readings buffer locally and back-fill automatically once the link returns, with their original timestamps preserved. This store-and-forward behaviour is standard because in Indian plant environments the link will drop, and a system that loses data during those windows never earns trust. The audit sheet marks any back-filled period explicitly so nobody is misled about when data actually arrived.

As configuration, not as custom code. Tags, calculations, targets, aggregation rules and deviation thresholds are all configurable, and adding a new KPI or changing a formula does not require a software release. We arrive with a cement and process KPI library already built — clinker TPD, specific heat consumption, TSR, specific power, WHR share, availability and utilisation — so most of the work is mapping to your tags rather than defining metrics from scratch.

Two mechanisms. First, a parallel run: AURA produces the report alongside your existing manual process until the numbers reconcile every day, typically for three to six weeks, and only then does the manual process stop. Second, the audit sheet: every figure in the published report traces back to its source tags, timestamps and formula, so "how did we get this number" is always answerable months later without an investigation.

Typically six to ten weeks from start to the beginning of parallel running, depending on how quickly the tag inventory can be completed and how complex the report template is. Parallel running then continues until reconciliation is consistently clean. Subsequent plants deploy considerably faster because the configuration pattern and the KPI library are already established.

Every report carries a unique dated and timestamped filename, so an identical name can never overwrite yesterday's file. History is preserved automatically, which matters both operationally and when an auditor asks for a report from eight months ago. Folder permissions honour your existing Active Directory structure, and every configuration change or manual override is logged with the user and time.