Author: Scott Turner
This is the fourth part of my five part series on how to write an effective User Requirements Specification. The topic for this part is the ‘Control Philosophy’. The first three in the series include Considerations for Your User Requirement Specification, Process Overview for Your User Requirement Specification and Scoping Your User Requirement Specification. The fifth and final part to be written soon will be about hardware.
If you would like to comment and add to the contents of this post, please do so. It will make it a more rounded and complete guide.
I recommend that authors of Control Philosophies consider the following points:
Describe the principal forms of control including control module tags
Include as much information in the control philosophy as you can and pay particular attention to how the system responds to failures. This is an area of the philosophy which is often not considered but is immensely important to the person who configures the control system. The system will be much more robust if it can respond to failures in a controlled manner and not get into a situation where the logic locks up.
Please feel free to let me know your thoughts on the control philosophy in the comments section below.
From Jim: You can also connect and interact with other project experts in the Plan & Design group in the Emerson Exchange 365 community.
The post Effective Control Philosophies for Your User Requirement Specification appeared first on the Emerson Process Experts blog.