{"id":56574,"date":"2026-04-27T19:10:15","date_gmt":"2026-04-27T19:10:15","guid":{"rendered":"https:\/\/www.europesays.com\/ch\/56574\/"},"modified":"2026-04-27T19:10:15","modified_gmt":"2026-04-27T19:10:15","slug":"modularizing-engineering-a-concept-for-large-scale-process-industry-plants","status":"publish","type":"post","link":"https:\/\/www.europesays.com\/ch\/56574\/","title":{"rendered":"Modularizing engineering: A concept for large-scale process industry plants"},"content":{"rendered":"<p>    \u00a0<\/p>\n<p>\u00a0<\/p>\n<p>Type-based engineering<\/p>\n<p>Following a type-based engineering approach, the FM is engineered before creating the actual instance of a process function. Because the automation software relevant parts are described generically, no automation system-specific information is required.<\/p>\n<p>\u00a0<\/p>\n<p>Once completed, the resultant type can be instantiated during the plant engineering phase. Every FM instance of a type has identical behavior and can be bound to an automation system in a later step with suitable controllers, eg, Freelance or System 800xA family, depending on the process and automation system requirements.<\/p>\n<p>\u00a0<\/p>\n<p>For every FM instance, instrumentation can be assigned to the FM\u2019s instrumentation connectors. For practicality, for the same measurement value of different FM instances that belong to the same FM, different sensor types can be used within the FM instance. If a different measurement principle is required, another instrument type can be used for a specific FM instance. Thus, FMs are neither bound to specific instrumentation nor equipment type.<\/p>\n<p>\u00a0<\/p>\n<p>While an automation system-specific MTP is needed to describe automation system-specific information, only a generic MTP is required for the description of the FM. Thus, the concept of MTP is generalized; this means that the target system-specific information is not contained in the MTP for the FM.<\/p>\n<p>\u00a0<\/p>\n<p>\u00a0<\/p>\n<p>\u00a0<\/p>\n<p>Engineering workflow of the automation system<\/p>\n<p>The engineering workflow can be divided into two different, yet not necessarily sequential, conceptual phases: phase A; FM engineering, and phase B: plant engineering; both can follow alternating or concurrent phases in the workflow.<\/p>\n<p>\u00a0<\/p>\n<p>FM engineering is initiated in step 1 with the description of the FM-type using HMIs, tags, services, etc. \u219202, while the generic MTP of the FM type is generated in step 2; thereby concluding phase A \u219202.<\/p>\n<p>\u00a0<\/p>\n<p>If a supervisory control is required, step 3 of phase B can be employed. In step 4, the automation system software for all instances and the specific automation system is created automatically. The MTPs for the instances are customized based on the automation system information \u219202.<\/p>\n<p>\u00a0<\/p>\n<p>\u00a0<\/p>\n<p>Project execution workflow<\/p>\n<p>ABB\u2019s engineering concept, using FMs, makes distributed off-site engineering for conventional process plants possible. Module fabrication yards can continue constructing modules for the plants, including I\/O, while the corresponding counterparts, on the automation side, are created off-site and later assigned to the I\/O, as per \u219203.<\/p>\n<p>\u00a0<\/p>\n<p>Critically, testing is performed at every stage. A type test is performed for every FM. Once the FM instances are created and assigned to the modules in the module fabrication yard, a virtual factory acceptance test (FAT) can be performed using a virtual control environment already connected to the I\/Os of the modules. The mechanical parts can then be transferred with the corresponding FM instances on-site. Here, a site acceptance test (SAT) can be executed with the installed real-world control system.<\/p>\n<p>\u00a0<\/p>\n<p>Thanks to the project workflow methodology, the plant engineering can be performed in the office, tested in the virtual environment with the FM instances and finally transferred on-site. To foster reuse, the FMs could then be stored in an FM library and be reused in other projects.<\/p>\n<p>\u00a0<\/p>\n<p>\u00a0<\/p>\n<p>\u00a0<\/p>\n<p>Variant management using FMs<\/p>\n<p>To enable reuse of larger parts of a plant, management of variants by means of optional functionality and nesting (the nesting of other FMs and PEAs) might be useful, especially whenever it is desirable to develop a multi-functional type that can be parameterized for every instance separately, at a later time \u219204 [10,11].<\/p>\n<p>\u00a0<\/p>\n<p>\u00a0<\/p>\n<p>\u00a0<\/p>\n<p>Plant engineering using parameterizable FMs<\/p>\n<p>Since FMs can be used to create instances and their parameters according to the needs of the process plant, whenever an instance of an FM is created during plant engineering, all nested FMs \u219204, PEAs, and optional functionality \u219204 are enabled by default, thereby streamlining the process. The instances are connected as for standard modular plants: by using material flow (pipes) and information flow (signal) connections, \u219205 [12].<\/p>\n","protected":false},"excerpt":{"rendered":"\u00a0 \u00a0 Type-based engineering Following a type-based engineering approach, the FM is engineered before creating the actual instance&hellip;\n","protected":false},"author":2,"featured_media":56575,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[130],"tags":[232,2056],"class_list":{"0":"post-56574","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-abb","8":"tag-abb","9":"tag-motion"},"share_on_mastodon":{"url":"https:\/\/pubeurope.com\/@ch\/116478255118350953","error":""},"_links":{"self":[{"href":"https:\/\/www.europesays.com\/ch\/wp-json\/wp\/v2\/posts\/56574","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/ch\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/ch\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ch\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ch\/wp-json\/wp\/v2\/comments?post=56574"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/ch\/wp-json\/wp\/v2\/posts\/56574\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ch\/wp-json\/wp\/v2\/media\/56575"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/ch\/wp-json\/wp\/v2\/media?parent=56574"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/ch\/wp-json\/wp\/v2\/categories?post=56574"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/ch\/wp-json\/wp\/v2\/tags?post=56574"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}