What to Consider When Specifying Intelligent MCCs

May 13, 2019

Specification of intelligent MCCs requires taking into consideration the variables of cost, capability, and complexity. Therefore, it is important to realistically assess your capabilities and objectives. Keep in mind that additional functionality usually comes with additional cost or complexity that you may not need.

The following list are questions to consider when specifying intelligent MCCs.

  • Will I maximize my return on investment by lowering the installed cost of the MCC equipment or by providing significant additional functionality?
  • Will last minute changes be likely?
  • Is future expansion or modification likely?
  • How valuable is a reduction in installation and commissioning time?
  • Can the equipment be integrated into my overall control and information architecture?
  • Does my control system or network have enough capacity to handle the data provided?
  • Do I have a technical staff capable of maintaining the system?
  • What are the cabling and connection requirements of the system?

A good MCC supplier will offer a range of options; one size does not fit all. The manufacturer should be able to help you answer these questions, so you can select the best approach for your application. The supplier also should be able to integrate with multiple networks and existing control systems. They must be willing to work with third parties and value-added system integrators. And they should be able to provide total solution packages where appropriate.

Finally, a complete functional test of the equipment prior to shipment is essential to realising reductions in commissioning time. Be sure the vendor intends to conduct the test by actually energising the I/O, not with simple point-to-point wiring checks.

Facebook
Twitter
LinkedIn
Search Saftronics

© 2022 Saftronics

We use cookies to ensure that we give you the best experience on our website. By clicking Accept, you consent to store on your device all technologies described in our Privacy Policy.