InTech

MAR-APR 2018

Issue link: http://intechdigitalxp.isa.org/i/959322

Contents of this Issue

Navigation

Page 31 of 57

32 INTECH MARCH/APRIL 2018 WWW.ISA.ORG AUTOMATION IT service layers of EdgeX Foundry are: l core services layer l supporting services layer l export services layer l device services layer The two underlying system services of EdgeX Foundry are: l security l system management Core services layer The core services (CS) layer separates the north side and south side layers at the edge. Core services include the fol lowing components: l Core data: a persistence repository and associated management service for data collected from the south side objects. l Command: a service that facilitates and controls actuation requests from the north side to the south side. l Metadata: a repository and associ ated management service of metadata about the objects that are connected to EdgeX Foundry. It has the capability to provision new devices and pair them with their owning device services. l Registry and configuration: provides other EdgeX Foundry microservices with information about associated ser vices within EdgeX Foundry and micro services configuration properties (i.e., a repository of initialization values). Supporting services layer The supporting services (SS) layer en compasses a wide range of microser vices that provide the edge analytics and intelligence and provide service to EdgeX Foundry itself. Normal software application duties, such as logging, scheduling, and data clean up (scrub bing), are performed by microservices in the SS layer. The rules engines and alerting and notification microservices are within the SS layer, because they operate on top of the core services layer. The local ana lytics capability (implemented today as a simple rules engine) is also located in this layer. At this time, the EdgeX Found ry supporting services layer includes the following microservices: l architecture – supporting services – alerts and notifications l architecture – supporting services – logging l architecture – supporting services – scheduling l architecture – supporting services – rules engine Export services layer EdgeX Foundry operates independently of other systems w hen necessary. Gate ways often operate in isolated and sometimes disconnected environments and monitor and manage a collection of sensors and devices that have little or no outside monitoring or control. There fore, EdgeX Foundry can operate and sustain itself over long periods without connection to the "north side" systems. The data and intelligence that is created at the edge should be collected often and transported to enterprise (cloud) systems. The transporting is done by the export services (ES) layer. The ES layer has a set of microservices that performs the following activities: l enables off gateway clients to regis ter for data that interests them, com ing from the south side objects l informs where and when the data is to be delivered l informs the format and shape in which that data is to be delivered For example, the "where and when" could be sending temperature data to a REST address every hour, and the for mat and shape could be to supply JSON data in compressed form. At this time, the export services layer Client registration Loosely coupled microservices framework Security Security services Rules engine Device services (any combination of standard and proprietary protocols via SDK) "Southbound" devices, sensors, actuators Core data Core services Rest OPC-UA Modbus Bacnet Zigbee BLE MQTT SNMP Virtual Additional device services Scheduling Logging Additional services Container development Device + system management Local mgmt. console Alerts and notifications Additional services Distribution Required interoperability foundation Replaceable reference services "Northbound" infrastructure and applications Additional services Command All microservices intercommunicate via APIs Metadata Registry config Choice of protocol SDK Supporting services Export services

Articles in this issue

Links on this page

Archives of this issue

view archives of InTech - MAR-APR 2018