Select PlantStruxure reference architectures? - Schneider Electric ...
Select PlantStruxure reference architectures? - Schneider Electric ... Select PlantStruxure reference architectures? - Schneider Electric ...
1 – Introduction1.4. PlantStruxure reference architecture principlesThe aim of using pre-tested reference architectures is to reduce project development time andrisk.The definition of automation system architectures from project specification (P&ID, devices list) isnot based only on the product catalog , but also on reference architectures catalog. Therefore,each system is based on pre-tested architectures. A customization is required to adapt theselected architecture to meet the project requirements and constraints.From customer requirements…ProjectrequirementsServicesPsXProductsPSxcatalog ProductcatalogCustomer SystemCustomerSolutionPSxReferencearchitectureCatalogTVDA guides…to customer solutionFigure 3: PlantStruxure reference architectures model1.5. GlossaryA glossary is available in the appendix chapter of this document. Please refer to it whenevernecessary.16© 2012 Schneider Electric All Rights Reserved
2 – Selection2. Selection2.1. Reference architecture descriptionPlantStruxure automation system provides a solution for process applications such as waterplant, cement plant, mining plant, or food and beverage plant.Customers’ systems are designed using reference architectures. Some are designed for theoverall control systems and some are designed for more specific elements such as the controlroom or the functional units.Therefore, PlantStruxure reference architectures are a combination of a control room architectureand several functional unit architectures that are assembled following an overall networkarchitecture topology.The control room architecture includes all the components that allow monitoring and control of theentire process. The functional unit architecture integrates the control system and the peripherals.Operation networkControl roomArchitectureOverallnetworkarchitectureControlnetworkDevicenetworkFunctionalunitArchitectureFigure 4: PlantStruxure architecture structuringA comprehensive description of a PlantStruxure process automation system is done along threeaxes:From a technological axis: How is this architecture built?From a functional axis: Which are the services provided by this architecture?Or from an application axis: How can this architecture be used?17© 2012 Schneider Electric All Rights Reserved
- Page 3 and 4: Important InformationNoticePeople r
- Page 5 and 6: the applicable local and national s
- Page 7 and 8: The architecture described in this
- Page 9 and 10: The STN CollectionThe implementatio
- Page 11 and 12: Table of Contents1. Introduction 13
- Page 13 and 14: 1 - Introduction1. Introduction1.1.
- Page 18 and 19: 2 - Selection2.2. PlantStruxure tec
- Page 20 and 21: 2 - Selection2.3. PlantStruxure fun
- Page 22 and 23: 2 - Selection© 2012 Schneider Elec
- Page 24 and 25: 3 - Global ref. archi.Two types of
- Page 26 and 27: 3 - Global ref. archi.3.3.2. Centra
- Page 28 and 29: 3 - Global ref. archi.3.4.2. Modula
- Page 30 and 31: 3 - Global ref. archi.Functional ax
- Page 32 and 33: 3 - Global ref. archi.3.6. PlantStr
- Page 34 and 35: 4 - Control room ref. archi.4.2. Pl
- Page 36 and 37: 4 - Control room ref. archi.Histori
- Page 38 and 39: 4 - Control room ref. archi.4.5. Co
- Page 40 and 41: Communication5 - Func. unit ref. ar
- Page 42 and 43: 5 - Func. unit ref. archi.VSD Modbu
- Page 44 and 45: 5 - Func. unit ref. archi.EthernetB
- Page 46 and 47: 5 - Func. unit ref. archi.The three
- Page 48 and 49: 5 - Func. unit ref. archi.60 instru
- Page 50 and 51: 5 - Func. unit ref. archi.Modicon S
- Page 52 and 53: 5 - Func. unit ref. archi.5.4.2. Fu
- Page 54 and 55: 5 - Func. unit ref. archi.© 2012 S
- Page 56 and 57: Redundant I/Oserver,alarm servertre
- Page 58 and 59: 6 - ExamplesProcess Control roomH i
- Page 60 and 61: 7 - AppendixTermQEIORIOX80Descripti
1 – Introduction1.4. <strong>PlantStruxure</strong> <strong>reference</strong> architecture principlesThe aim of using pre-tested <strong>reference</strong> <strong>architectures</strong> is to reduce project development time andrisk.The definition of automation system <strong>architectures</strong> from project specification (P&ID, devices list) isnot based only on the product catalog , but also on <strong>reference</strong> <strong>architectures</strong> catalog. Therefore,each system is based on pre-tested <strong>architectures</strong>. A customization is required to adapt theselected architecture to meet the project requirements and constraints.From customer requirements…ProjectrequirementsServicesPsXProductsPSxcatalog ProductcatalogCustomer SystemCustomerSolutionPSxReferencearchitectureCatalogTVDA guides…to customer solutionFigure 3: <strong>PlantStruxure</strong> <strong>reference</strong> <strong>architectures</strong> model1.5. GlossaryA glossary is available in the appendix chapter of this document. Please refer to it whenevernecessary.16© 2012 <strong>Schneider</strong> <strong>Electric</strong> All Rights Reserved
Change language