Taxonomy feed.
In digital-substation projects most attention goes to GOOSE, SV, PTP and the network. But there is another important layer — MMS exchange and IEC 61850 reports, through which SCADA, HMI, gateways and monitoring systems receive telemetry from IEDs. In practice the problems here are deceptively simple: the MMS connection is up, the device is reachable, the client «sees» the server — yet data does not update, some signals disappear, events are duplicated, or the report control block does not activate at all. This article covers the sharpest problems with report control blocks (RptEna, ConfRev, a block already taken by another client, TrgOps, a DataSet mismatch, duplication from the buffer via entryID and too much faith in the SCL file) and a practical principle: cross-check the SCL file, the device's actual MMS model and a PCAP capture together.
One run of Tekvel Magic software over SCL data — and you have a ready MS Word document - Signal list: a per-device summary, full detail of every URCB/BRCB control block and an element-by-element breakdown of every DataSet, with signal descriptions taken straight from the SCL. The module runs offline — from an SCD file or a folder of CID files, with no need to connect to the devices. The third case in the series closes the «how do you hand it over» task: handover documentation and as-built documentation in a single run, plus a separate «Configuration findings» document with a lightweight offline audit.
One click in Tekvel Magic software — and you have a MS Word protocol that covers every IED on the substation: a summary of all URCB/BRCB control blocks with their MMS reference, type, RptEna state, Owner client, triggers, optional fields, DataSet reference, BufTm and IntgPd; plus a detailed section decoding the bit fields and the element-by-element composition of every DataSet — with descriptions taken from the SCL file. The case closes the second half of the SCADA acceptance questions: «how it is configured» is now complemented by «how it is actually working right now», and you instantly see whether reports are sitting idle while SCADA collects data by periodic polling.
A contractor hands over an SCD file claiming it matches the actual device configuration. But how do you verify that quickly and provably when there are 76 IEDs on site and no permanent monitoring system? A field case from Tekvel: the verification module in the Tekvel Magic software automatically compared the device configurations against the SCD and produced an engineering deviation report covering DataSets, GOOSE, Sampled Values and MMS reports in 15 minutes.