Thread Content
I have been working in instrument design for several years now. There may be other engineers like me who still have some confusion regarding the work involved in developing systems. Firstly, in earlier years, this type of work was usually handled by the person in charge of instrumentation for a project; if such a person was not available, then there was no opportunity to get involved in these tasks. Secondly, nowadays some project owners prefer to take care of the system development themselves. Thirdly, this part of the work involves working with intermediate files from the DCS manufacturers, and these files are not ultimately among those that need to be published as part of the project, which makes it somewhat difficult to learn on one’s own. All those who hope that an experienced senior engineer or an engineer from a DCS manufacturer working in collaboration with an engineering company can explain, in chronological order, the main tasks involved in system development. For example, what is the purpose of the DCS kickoff meeting, what are the files exchanged with the manufacturer, what is the general content of those files, and what are the main tasks during the FAT phase conducted at the manufacturer’s site, and so on
At the start of the project, it is necessary to determine the hardware configuration in consultation with the DCS manufacturer, based on the actual number of I/O points; identify the components that require redundant configurations; consider the communication requirements specified by third-party manufacturers; take into account any instruments that need special wiring on site; and establish a project schedule, among other things. The FAT test is equivalent to the factory acceptance test, which includes inspections of the hardware, verification of the completeness of the configuration, redundancy tests, and so on. Once FAT is completed, it means the DCS cabinet can be shipped to the site for installation and commissioning.