Identify the Installed Equipment
Start with the full CPU, I/O and power-supply part numbers, including revision suffixes. MOSCAD and MOSCAD-L documentation covers different equipment arrangements. A module's appearance or a shortened inventory description is not enough to identify an equivalent replacement.
Send label photographs, panel and wiring drawings, the reported fault and any diagnostic information. Include supply voltage, installed radio model, application software details and whether the problem is continuous or intermittent. This helps distinguish a failed component from a power, wiring, communications or application problem before equipment is removed.
Review Repair and Replacement Options
GDS reviews the equipment and reported symptoms to determine whether repair or sourcing a replacement is practical. Available parts, condition and compatibility influence the proposed work. Contact us for shipping instructions before sending a unit, and retain the configuration and application backups needed to return it to service.
The quote should identify what is included, the condition of any replacement unit and the expected timing. GDS does not provide a separate equipment or repair warranty. Manufacturer coverage, where applicable, is identified for the offered equipment. Repair evaluation does not imply that every legacy module can be restored or that a standard turnaround applies.
I/O and Field Wiring
Review each input and output against the installed module's electrical requirements. Useful records include signal ranges, contact arrangements, relay loads, terminal assignments and the control narrative. The MOSCAD library includes separate references for CPU, digital, analog and mixed I/O equipment; use the document that matches the actual module family.
A modernization plan should preserve the meaning of each field signal, even when terminal numbers or software addresses change. Document engineering units, scaling, alarm limits and command feedback. During conversion, verify both the field value and the indication seen by the operator so a wiring change does not become a hidden application error.
Communications and SCADA Continuity
Identify how the RTU exchanges data with other sites and the central application. Record the radio and interface configuration, site addressing and the host software version. A replacement controller must be reviewed in that system context, including the behavior expected during loss of communications and recovery.
An HMI change may be possible while suitable field equipment remains. GDS's Medina County work replaced Wonderware with VTScada while retaining Motorola RTUs. That approach depends on the installed models and interfaces; the project record is an example of a phased upgrade, not a guarantee for every MOSCAD installation.
Plan a Staged Controls Upgrade
Where repair is unsuitable, we can define a replacement scope around the equipment and operating requirements. The work may include a new controller, power and I/O arrangement, application conversion, communications changes and updated drawings. Compare the full installed cost and disruption with continued repair and spare-parts support.
Agree the work sequence with operations before field conversion. Identify backups, access windows, temporary arrangements, acceptance checks and a way to restore service if the planned change cannot be accepted. Training and handover should cover the new controls, alarm response, diagnostic information and the location of current application files.
Use the Correct Manual
The MOSCAD owner's manual covers installation, operation and field replacement for the equipment described in that edition. The MOSCAD-L owner's manual is a separate reference. Neither an older manual nor an online listing establishes current stock or support dates.
For a parts inquiry, send the manual reference alongside the equipment label if available. GDS can review those details against the proposed repair or replacement and identify where further documentation is needed. Requests involving application changes should also include the operating problem and desired behavior so the scope addresses the system as well as the hardware.