Advances in design software offer greater efficiencies for designing, deploying and maintaining automation systems
Andy Stump • Business Manager • Design Software • Rockwell Automation
Manufacturing and industrial end users are turning to smart manufacturing to be more responsive, efficient and flexible in how they operate.
But this presents a new challenge for automation system designers and integrators. They’re now expected to deliver the flexible and information-enabled automation systems required for smart manufacturing, while also contending with pressures to increase profitability, improve time-to-market, optimize asset performance and meet regulatory standards.
System designers and integrators need to deliver more complex systems, and fundamentally change how they design, build and commission systems. Fortunately, recent advances in design software can help with that, while also delivering longer term operational and maintenance benefits.
An outdated design approach
The traditional approach to designing automation systems is no longer optimal for today’s connected systems.
Using multiple tools to design a system can be especially problematic. It forces designers to jump from one tool to another and learn different programming languages, menus and commands for each. This can be cumbersome and time-consuming, and increase the amount of training required for employees to become familiar with each tool.
The lack of interoperability between these tools restricts data sharing, forcing programmers to re-enter the same code and data in multiple tools. Such redundant programming adds time to the design process and results in coding and data-entry errors.
The use of disparate tools and processes is undesirable for complex systems that require the support of multiple teams. For example, projects for large end users may involve multiple design engineers and system integrators located in different countries and time zones. Schedules and costs can quickly soar out of control for these projects without fluid collaboration and easy data sharing.
Adopting an integrated development environment
Design software options are evolving. Systems that require multi-discipline control and visualization from one integrated development environment can simplify the design and commissioning processes.
Engineers can use an integrated environment to create common workflows, more easily share data across geographically dispersed teams and eliminate redundant processes.
An integrated environment gives you a standard way to share tags, alarms and other data across multiple design applications. You can configure information once and leverage it across the entire automation system. You can configure all elements of the automation system in one place, rather than using multiple tools for control and visualization.
Once a system is operational, the integrated development environment provides a central view for all system components. This view gives operators and maintenance technicians a
central location where they can re-configure devices, troubleshoot and access information about the system.
Modeling and simulation capabilities
A “virtual” design can increase design productivity and minimize risk. The ability to validate, test and optimize application code independent of physical hardware can reduce project costs, and minimize commissioning and startup time.
Modern integrated development environments incorporate virtual design for designers to emulate a control system within other simulation systems, including operator training systems and 3-D modeling applications. Designers can simply run their 3-D drawings through the virtual design program’s simulation and emulation processes to prove out their designs. System designers already have used virtual design to save anywhere from 40 to 60% in system costs.
Users looking to accelerate project creation by leveraging reusable content require library management capabilities. Library management best practices help improve design consistency, reduce engineering cost and achieve faster commissioning.
With library management tools, engineers can build, store and control versions of re-usable code that can be deployed across an enterprise.
Library development capabilities help users create parameterized modular code objects. These multi-discipline objects include control code, HMI faceplates, alarms and historical data collection tags.
Objects can range in size and complexity, but not every engineer who works with them has to be aware of all of the complexity and relationships. You can simply deploy objects by configuring parameters rather than develop code. Thus, you can deploy a large number of objects more efficiently. This strategy also reduces or eliminates the need to test and validate each instance of those objects.
For example, an engineer working on an application requiring 500 pumps could create a standard pump object in their library. The engineer would then select that object and configure parameters specific to the instance of that pump. The tool then creates all the necessary files for control code, visualization, alarming and historical data collection for all 500 pumps at one time.
There are organizational aspects of design software that can improve productivity, such as how it presents code that can help end users manage and maintain their systems.
Software that logically organizes code provides a way to create a model of the system based on the user’s perspective. This shift in code presentation – from the controller’s perspective to the user’s perspective – lets users maintain and quickly identify the code within the system that may need to be investigated.
Designing to the requirements of the current system and the long-term maintenance and potential expansion of that system helps ensure continued productivity and efficiency for end users.
Enabling smart manufacturing
These capabilities – an integrated development environment, modeling and simulation, library management, and system organization – all help engineers design smart machines and automation systems more efficiently, affordably and consistently.
A key responsibility of system designers, integrators and end users is to ensure the right tools are in place before design even begins. The design stage is only a small phase of the development lifecycle, but the benefits of a scalable, modular system design can exponentially enhance a system’s ease of use, expandability and maintenance long after it has been commissioned.
Design software selection should be based on the design time and costs savings it can deliver up front, as well as the maintenance and operations benefits it can offer down the road.