Ubiquitous Computing in Business Processes Part II

Size: px
Start display at page:

Download "Ubiquitous Computing in Business Processes Part II"

Transcription

1 Ubiquitous Computing in Business Processes Part II Prof. Dr. Lutz Heuser Urban Software Institute Darmstadt November 17 th, 2017

2 Outline 1. Recap

3 What kind of Business Processes are out there? We can categorize typical enterprises business processes: Management processes, incl. strategy and process management, etc. Core business processes, incl. production, sales, marketing, purchasing, customer care, etc. Supporting processes, incl. human capital management, accounting, facility management, IT management, etc. Ubiquitous Computing in Geschäftsprozessen / Lutz Heuser, Zoltan Nochta / Page 3 Picture Source: SAP AG

4 Smart Items Generic Definition A smart item is Object of the Real world, Basically every thing - buildings, vehicles, machines, tools, pallets, boxes, shopping carts, shelves, consumer products, etc. Capable to store data about itself or its environment e.g. identifier, temperature, location, etc. Capable to exchange data via a communication interface wired or wireless Ubiquitous Computing in Geschäftsprozessen / Lutz Heuser, Zoltan Nochta / Page 4

5 Example HF RFID Tag Source: Auto-ID Center Ubiquitous Computing in Geschäftsprozessen / Lutz Heuser, Zoltan Nochta / Page 5

6 Outline 2. RFID in Business Processes: Asset Management

7 RFID supported Asset Maintenance Process 1.) Technician reads information stored on RFID-tag 2.) Maintenance and repair planning based on information on RFID tag loaded 4.) Information update on RFID tag after maintenance has been performed RFID tag on asset 3.) Execution of maintenance and repair activities Ubiquitous Computing in Geschäftsprozessen / Lutz Heuser, Zoltan Nochta / Page 7 Source: SAP AG

8 Benefits Assets can be identified locally without access to backend system Assets can be identified correctly (no manual data entry needed) Technician can perform work efficiently because all important information can be found on the tag, such as Manufacturer information Technical specification Production date Safety instructions or As-build configuration RFID tag stores service history (the item s memory ): Who did what by when? RFID tags can be read through non-metallic substances, paint, grease or other obscuring materials (rugged environmental conditions) Always access to up-to-date technical object information Ubiquitous Computing in Geschäftsprozessen / Lutz Heuser, Zoltan Nochta / Page 8

9 Example: Fire shutter maintenance at FraPort (1) Maintenance orders are downloaded by mobile device assigned to the service technician Service technician goes to fire locker RFID tag on the fire locker is read and the equipment is identified Maintenance order for this equipment is automatically found and displayed. Service technician may enter a damage code. Ubiquitous Computing in Geschäftsprozessen / Lutz Heuser, Zoltan Nochta / Page 9 Source: SAP AG

10 Example: Fire shutter maintenance at FraPort (2) Service technician inspects and maintains the equipment After finishing his work, technician updates information on the RFID tag by adding inspection date and personal identification. The time between start and end of the work is automatically recorded as well. Orders with damage codes and times are synchronized with the enterprise backend system, later. Ubiquitous Computing in Geschäftsprozessen / Lutz Heuser, Zoltan Nochta / Page 10 Source: SAP AG

11 Project at FraPort: Costs and Monetary Benefits Main cost elements Hardware Mobile Devices Tags Tagging Software licenses Implementation and consulting Specific customer benefits Time savings Per day and technician Per year Avoidance of double orders (5% of orders before the project) Increased asset safety and compliance thanks to proven maintenance records Ubiquitous Computing in Geschäftsprozessen / Lutz Heuser, Zoltan Nochta / Page 11

12 Outline 3. RFID in Business Processes: Supply Chain Management

13 Supply Chain The Supply Chain - A complex puzzle! Where is my product? How will my partners gain visibility? Why is there a delay? What is causing the bottleneck? Am I compliant to regulations? When will my shipment arrive? How can my supply chain improve? How can I track my assets? How can I prove delivery to customer? How can I manage recall and returns? Is the product genuine? Ubiquitous Computing in Geschäftsprozessen / Lutz Heuser, Zoltan Nochta / Page 13 Source: SAP AG

14 RFID in Order Fulfillment Process Vendor Pick or Produce Build Handling Unit (HU) Issue Goods (Loading) Retailer Associate Boxes & Pallet Tags Scan IDs Middleware Post Goods Issue ERP Create HU WM Delivery Adv. Ship Notification Cust. Order Ubiquitous Computing in Geschäftsprozessen / Lutz Heuser, Zoltan Nochta / Page 14 Purchase Order Source: SAP AG

15 Let s have a look into the Factory! RFID in Discrete Manufacturing Process Vendor Pick or Produce Build Handling Unit (HU) Issue Goods (Loading) Retailer Associate Boxes & Pallet Tags Scan IDs Post Goods Issue Middleware ERP Create HU WM Delivery Adv. Ship Notification Cust. Order Ubiquitous Computing in Geschäftsprozessen / Lutz Heuser, Zoltan Nochta / Page 15 Purchase Order Source: SAP AG

16 RFID in Goods Receipt Process Vendor Check and Receive Goods Retailer Scan IDs Check consistency Feedback Middleware Register EPCs Post Goods Receipt ERP Source: SAP AG Adv. Ship Notification Delivery WM Ubiquitous Computing in Geschäftsprozessen / Lutz Heuser, Zoltan Nochta / Page 16

17 Outline 4. Open Urban Sensor-Data Platforms

18 18 Caloundra - Australia Southest city of the Sunshine Coast in Queensland Area: km 2 Population:

19 19

20 20

21 UrbanPulse - Frameworks Vert.x is a polyglot event-driven application framework that runs on the Java Virtual Machine Simple concurrency model. All code is single threaded, freeing from the hassle of multi-threaded programming. Simple, asynchronous programming model for writing truly scalable nonblocking applications.* Java EE is a widely used enterprise computing platform developed under the Java Community Process. 21 The platform provides an API and runtime environment for developing and running enterprise software, including network and web services, and other large-scale, multi-tiered, scalable, reliable, and secure network applications.* *en.wikipedia.org

22 UrbanPulse - Frameworks Vert.x Environment J2EE Environment Outbound Interfaces Outbound Interfaces UrbanPulse Data UrbanPulse Management Event Processing Event Processor Persistence Caching Storage Analytics Learning Models UrbanPulse Cluster Controller Data Catalog Entity Management 22 Inbound Interface Event Interfaces Connectors

23 UrbanPulse - Management UrbanPulse Management

24 UrbanPulse - Management Functions Management API Configuration and Management of Cluster-Nodes User Management Sensor data catalogue J2EE Environment UrbanPulse Management UrbanPulse Cluster Controller Data Catalog Entity Management 24

25 UrbanPulse ER Modell (vereinfacht) Data Consumer Data Consumer Data Consumer e.g. [ui!] Cockpit Listener Listener receives events, which are defined by statements. Data Consumer Data Consumer Statement EventType Statements select and combines events to business events Each Sensor detects events of a given Type (EventType) 25 Connector A connector wraps the API to the sensor data provider Sensor Each sensor has a definition and a universal unique ID.

26 UrbanPulse - Eventverarbeitung UrbanPulse Event Processing

27 UrbanPulse Event Processing Tasks Detect Analyse Store Distribute 27 urban Data in (near) real-time

28 UrbanPulse - Eventverarbeitung 28 Sensor Sources (examples)

29 UrbanPulse - Module UrbanPulse Modules

30 UrbanPulse - Connectors 30 Sensor Sources (examples)

31 UrbanPulse - Connectors Connectors allow to connect systems and sesnor nodes of different vendors, types, and domains: Energy Traffic Buildings Environmentt 31 Tasks Communicate with UrbanPulse API Authentication Transformation of raw data in sensor agnostic format

32 UrbanPulse - Connectors Connectors can be operated locally or in the cloud. Local Installation Supported communication protocols TCP/UDP HTTP(S) Web socket Amqp And if needed, more Benefits Cloud Solution 32 Easy Simple Scalable

33 UrbanPulse - Connectors public class ProcessingVerticle extends DefaultProcessingVerticle { /** event EnBW event type name mapped from 'sensortyp' field, null in case of null or invalid field public String geteventtypename(jsonobject event) { String sensortyp = event.getstring("sensortyp"); if (null == sensortyp) { container.logger().warn("null 'sensortyp' field!"); return null; } 33 } switch (sensortyp) { case "Dust detector": return "DustEventType"; case "Ambient Light V2": return "AmbientLightEventType"; case "Barometer": return "BarometerEventType"; case "Humidity": return "HumidityEventType"; case "Sound Intensity": return "SoundIntensityEventType"; case "Temperature": return "TemperatureEventType"; default: container.logger().warn("unsupported 'sensortyp' value: " + sensortyp); return null; }

34 UrbanPulse InboundInterfaces 34 Sensor Sources (examples)

35 UrbanPulse Inbound Interfaces High performance and scalable interface for Events. CEP - Modul Persistence - Modul Analytics- Modul Inbound Worker 35 Partitions Sensor Sources

36 UrbanPulse - Processing 36 Sensor Sources (examples)

37 UrbanPulse - Persistence High performance and scalable storage structure for events Partitions will be stored on different storage servers 37

38 UrbanPulse Complex Event Processing Complex Event Processing Module to select and aggregate events Ereignisdaten EPL - Statement Resultat Temperatur : 30 Temperatur : 20 Temperatur : 25 Select * from.. where Temperatur > 25 Temperatur : 30 38

39 UrbanPulse - Analytics Stream Processing und Machine Learning Raw data Transform Learn Validate 39 Raw data Transform Models Prediction

40 UrbanPulse - Integration 40 Sensor Sources (examples)

41 UrbanPulse Outbound Interfaces Worker of Outbound Interfaces distribute the Data to different consumers Data consumer 1 Data consumer 2 Data consumer N Worker Worker Worker Worker 41 CEP - Modul Persistence - Modul Analytics- Modul

42 UrbanPulse Use Cases Use Cases

43 UrbanPulse - Use Cases 43 Sensor Sources (examples)

44 UrbanPulse [ui!] COCKPIT [ui!] COCKPIT [ui!] INTEGRATION 44 [ui!] TRAFFIC clevercitiparking [ui!] CROSSFLEET

45 [ui!] TRAFFIC 45

46 UrbanPulse Data feed 46

47 Outline 5. Group Exercise

48 Group Exercise - Setting Goal: Develop a Smart City Service Business Case including PoC Team of 4-5 Exercise consists of two parts Build a business case for a Smart City Service Description of the Service Deployment and operation of the Service Business Plan using a business model canvas (see attached) Build a PoC using UrbanPulse and [ui!] COCKPIT Identify the smart data source and connect it via [ui!] CONNECTOR Visualize the Service using [ui!] COCKPIT (Build an App) Kick-off on November 17 th, 2017 with a tutorial on UrbanPulse and [ui!] COCKPIT (Review / Feedback opportunity on December 16 th, 2016) Jam Session on pitch on January 12 th, 2018 first two hours Successful presentations will influence result of exam Ubiquitous Computing in Geschäftsprozessen / Lutz Heuser, Zoltan Nochta / Page 48

49 Business Model Canvas Ubiquitous Computing in Geschäftsprozessen / Lutz Heuser, Zoltan Nochta / Page 49

50 Smart City Dashboard Shows the urban data of the city Ubiquitous Computing in Geschäftsprozessen / Lutz Heuser, Zoltan Nochta / Page 50

51 Smart City Dashboard - Sample Urban Sensor Data Example: Environmental Data Identify thresholds of air quality Stake holder: City Authorities Technical Solution: Multi-sensor nodes as smart items collect data and send them to a sensor data platform for evaluation.

52 Smart City Dashboard PoC Build your own Tile Team 1 This could be your service? Team 2 This could be your service? Team 3 This could be your service? Team 4 This could be your service? Team 5 This could be your service? Team 6 This could be your service?