A first objective of a FEED study is to build a complete IO list. Often this is a tedious, time consuming activity. P&IDs and other references are often manually combed through to build the list. Once compiled, this IO list must be reconciled against the devices installed in the field.
One approach I’ve used successfully is to run an analysis of the legacy control systems configuration and extract the IO list programmatically. This approach to building an IO list is much more accurate and timely. Weeks can be shaved off the FEED study schedule. Accurate device data, ranges and alarm values are extracted.
Recently I ran an analysis to extract Modicon IO data for a Novatech D3 modernization project. Having the Modbus IO data in hand prior to the FEED starting allowed for quicker and more accurate field reconciliation of the I/O, the assignment of CHARMs channels, tag tracking and most importantly – fully defining the I/O scope of the execution phase of the project.
The ability to conclude the FEED study earlier pulls in the timeline for the actual project. The quality of the digital IO list builds confidence in the deliverables for the project team and the end user.
What are others doing in regarding to creating a valid IO list for FEED purposes or project execution? Does anyone have any good examples or success stories?
Stop by the Modernization booth at Emerson Exchange 2015 to discuss your project with me and how I can help.