Quick answer
Prepare the SCADA signal list before ordering the gateway and finalising control wiring. Each point needs an agreed meaning, source and receiving destination; commands also need authority, permissives and feedback. A protocol name describes part of the communications arrangement, not the complete integration deliverable.
Separate functions from the communications product
An RTU can combine monitoring, control and multiple protocol options. ABB's NETCON 200 product information illustrates this range of functions in a specific device. The buyer still has to define which functions and interfaces the project requires, and whether the selected equipment includes them. ABB NETCON 200 product information.
Begin with operational decisions: which states must operators see, which measurements support decisions, and which actions may be initiated remotely? Then trace each requirement to a field device, panel terminal, relay or communications source.
Give each point a complete definition
The following worksheet uses illustrative point descriptions. It is not a claim about signals included in any standard Jinxing panel.
| Point type | Fields to define | Acceptance question |
|---|---|---|
| Breaker position | Source contacts, open/closed meaning and invalid state | Can the receiver distinguish a valid state from a wiring or data problem? |
| Current measurement | Source, phase, unit, ratio, scaling and update behaviour | Does the displayed value correspond to the approved input? |
| Protection alarm | Exact event, persistence and reset behaviour | Is the alarm meaning consistent at panel and control centre? |
| Remote command | Authority, permissives, command method and feedback | Does the accepted or rejected command produce the agreed indication? |
| Communications status | Detection source, time basis and recovery behaviour | Is unavailable information clearly represented? |
Add unique point identifiers and revisions. Use them in the wiring schedule, gateway database and control-centre list so that the same requirement remains traceable across suppliers.
Resolve quality and timing expectations
A displayed value without its validity condition can mislead an operator. Define how stale, unavailable or invalid information is represented, and which system determines that state. Agree timestamp origin, time synchronisation responsibility and event ordering requirements where they matter to the project.
Avoid requiring every available device point simply because it can be exported. Ask the owner to identify the decision supported by each point. This keeps the interface review manageable and helps distinguish essential alarms from optional diagnostic data.
Example: the same “open” point means two things
Consider a hypothetical integration in which one team interprets an absent closed indication as “open,” while another expects independent open and closed inputs with an invalid combination. The protocol connection can operate correctly while the operational meaning remains inconsistent.
A point definition resolves the ambiguity by stating the actual input source, state mapping and invalid-state response. The acceptance test can then verify all agreed states using a suitable approved test method, rather than checking only that a label changes on a screen.
Similarly, a remote command should have an agreed acceptance or rejection response. Receiving a network message does not by itself demonstrate that the intended equipment action occurred.
Divide factory and site acceptance
Allocate panel wiring checks, relay data mapping, gateway configuration, network provision and control-centre configuration separately. Define where factory testing ends and which external interfaces require site testing. If a simulator is used, record what it represents and what remains to be verified against the actual receiving system.
Retain the accepted point database and configuration versions with the final drawings. Future firmware, relay or panel changes should trigger review of affected points instead of relying on an undocumented copy of the original mapping.
Inputs for a connected switchgear enquiry
For medium-voltage switchgear configurations, provide the owner-approved point list, protocol and network requirements, command philosophy and control-centre contact responsibilities.
Use the project enquiry page to request a clear panel-to-SCADA scope for the proposed KYN28-12 equipment. Available signals, gateway hardware and integration services need confirmation against the order.