This is the second part of the five part series on how to write an effective User Requirement Specification. If you missed the first on, see Considerations for Your User Requirement Specification. The topic of this post is ‘Process Overview’. We will address Scope, Control Philosophy and then Hardware in future posts.
As before, I would very much appreciate your comments and input. The points which I would like authors of User Requirements Specifications to consider are as follows:
Separator P&ID – Click to enlarge
Remember to ensure that you check the information. The numbering and terminology contained on the process flow diagram and in the P&ID documents should be consistent with those in the written paragraphs. Any terms or abbreviations which the reader may not be familiar with should be fully explained.
I find that it helps to put a table at the front of the document explaining what the abbreviations are. If you can, please provide a legend with your P&ID diagrams. Different companies present instruments differently. A P&ID diagram legend sheet will reduce the number of questions you may be asked.
What tips would you add or like to see clarified? Add a comment below.
From Jim: You can connect and interact with other project professionals in the Plan & Design group in the Emerson Exchange 365 community.
The post Process Overview for Your User Requirement Specification appeared first on the Emerson Automation Experts blog.