www.arrowhead.eu

ArrowheadFrameworkSummerschool16-24Aug2017LuleåUniversityofTechnologyProfessorJerkerDelsing

1

www.arrowhead.eu

EngineeringofIoTautomationsystems

Prof.JerkerDelsing

2

3Outline1. EngineeringofanSoSmulti-domainfacility

2. Component-basedengineeringmethodology

3. Comparisontolegacysystemengineering

www.arrowhead.eu

EngineeringofanSoSmulti-domainfacility

4

www.arrowhead.eu

5

Engineeringprocedures

www.arrowhead.eu

6

Automationengineeringwork-flow

180 Paper G

• Can a system providing this functionality be put to further use as an ArrowheadCore system?

Conceptually, the introduction of new automated systems in most domains, and espe-cially in industrial applications, go through five steps from idea to operation, as illustratedin Figure 1:

Figure 1: Five steps of an automation system engineering work-flow.

1. Conceptual application design: This step is comparatively informal and andusually not technically specific but should outline the purpose and motivation forthe application. Typically it should answer the question “Why?” and providebasic requirements to the design, given available resources and other constraints.

2. Functional design: This step will produce most of the overarching design doc-uments. The results of this should be a detailed design of the mission criticalfunctionality and functional requirements for the support systems.

3. Procurement and Engineering: These two activities are often performed inparallel, and will a↵ect each other. Certain requirements and design decisions maylimit procurement to a single option, that will a↵ect engineering. Subsequently,engineering decisions may pose additional requirements on procurement of otherparts or subsystems.

4. Deployment and Commissioning: As all equipment is purchased, configuredfor the application, and delivered to the site of operation, a process of deploymentand integration of all systems begin. When systems have been connected a seriesof integration tests and commissioning starts, after which the full, interconnectedsystem-of-systems is ready for operation by the end user.

5. Operation: When the operational phase starts, the full system-of-systems shouldperform at the requested level without any need for further engineering. However,in most scenarios there are minor details that were not foreseen during the designphases and must be adjusted. Similarly, external factors, such as markets or regu-lation, are likely to change during the operation of a large system. All of these mayrequire updates to design and engineering, including documentation and data.

www.arrowhead.eu

7

Workflow1. Conceptualapplicationdesign:Thisstepiscomparativelyinformal

andandusuallynottechnicallyspecificbutshouldoutlinethepurposeandmotivationfortheapplication.Typicallyitshouldanswerthequestion“Why?”andprovidebasicrequirementstothedesign,givenavailableresourcesandotherconstraints.

2. Functionaldesign:Thisstepwillproducemostoftheoverarchingdesigndocuments.Theresultsofthisshouldbeadetaileddesignofthemissioncriticalfunctionalityandfunctionalrequirementsforthesupportsystems.

www.arrowhead.eu

8

Workflow3. ProcurementandEngineering:Thesetwoactivitiesareoften

performedinparallel,andwillaffecteachother.Certainrequirementsanddesigndecisionsmaylimitprocurementtoasingleoption,thatwillaffectengineering.Subsequently,engineeringdecisionsmayposeadditionalrequirementsonprocurementofotherpartsorsubsystems.

4. DeploymentandCommissioning:Asallequipmentispurchased,configuredfortheapplication,anddeliveredtothesiteofoperation,aprocessofdeploymentandintegrationofallsystemsbegin.Whensystemshavebeenconnectedaseriesofintegrationtestsandcommissioningstarts,afterwhichthefull,interconnectedsystem-of-systemsisreadyforoperationbytheenduser.

www.arrowhead.eu

9

Workflow5. Operation:Whentheoperationalphasestarts,thefullsystem-of-

systemsshouldperformattherequestedlevelwithoutanyneedforfurtherengineering.However,inmostscenariosthereareminordetailsthatwerenotforeseenduringthedesignphasesandmustbeadjusted.Similarly,externalfactors,suchasmarketsorregulation,arelikelytochangeduringtheoperationofalargesystem.Allofthesemayrequireupdatestodesignandengineering,includingdocumentationanddata.

www.arrowhead.eu

10

WorkflowConceptualapplicationdesign:

NodifferencetolegacyengineeringFunctionaldesign:

IoTSoSpropertiesnotcapturedbylegacytoolsare:

Latebindingofinteractionsfor:

PipingandInstrumentationDiagram(P&ID)

FunctionaldesigndescriptionObjectlist

Technicalrequirements

ProcurementandEngineering:

DevicesandSystemsneedtobecapturedastraditionalbuildingblocks

www.arrowhead.eu

11

WorkflowProcurementandEngineering:

DevicesandSystemsneedtobecapturedastraditionalbuildingblocks

DeploymentandCommissioning:

SimplificationregardingverificationofinstallationandconfigurationofinstalledIoT’s

Operation:

Nodifferencetolegacysystems

www.arrowhead.eu

12

QualitativecomparisonIngeneral,thepresentengineeringwork-flowappearstopromoteand

supporttheexpectedflexibilityofIoT-basedautomationsystems,

Systematicmanagementofserviceinteractionsandsystemconfigurations.

IoT-automationengineeringwork-flow,basedontheArrowheadFramework,significantlydecreasestheeffortforcertainphasesoftheengineeringwork,withoutsignificantincreasesinanyotherphases.

www.arrowhead.eu

13

Statusandcomparisontolegacytools

14

EngineeringofautomationsystemsProductdesign

Manufacturingrecipe(MEStools)

Partsupply

ProductioninfrastructureCommunicationtopology(Eplan-98,ElproCAD)

Processdesign(ProDesign)

Equipmentlocation(AutoCAD,Solidworks)

Equipmentcapability/configuration(Codesys,Step7,ControlBuilder)

15

SystemofSystemsservicesmanagementArrowheadFrameworkSoTAPlantDescriptionsystemConfigurationsystem

Authorisationsystem

Orchestrationsystem

16

SystemtoolsArrowheadFrameworkSoTAMMI-OrchestrationMMI-Authorisation

Managementtool

TestTool

17

CanwebuildArrowheadautomationsystemstoday?RobustcommunicationIoTsensors,actuators,PLC:s,etc.

DCSandSCADAfunctionality

MESandERPfunctionality

Cloudintegrationtechnology

EngineeringtoolscloudautomationTesttoolsandsimulators

Migrationtocloudautomation

Suitablesecurity

➡Productsonthemarket➡Someproductsonthemarket

➡Firstproductsonthemarket

➡Firstproductonthemarket

➡Someproductsonthemarket➡Demonstratedinindustrialenv.➡Firstproductsonthemarket

➡Demonstratedinindustrialenv.

➡Someproductsonthemarket

18

SystemofSystemstoolgap

ArrowheadFramework

Designtoolinteroperabi

lity

Legacytools

SoSengineering

Tools

AutomationSystemofSystems

enabledbyArrowheadFramework

TheGAP