Industrial Internet of Things (IIoT) is when we apply the concepts of IoT to the manufacturing industry. The flexibility, availability, and speed at which IoT can provide data is revolutionalizing the Manufacturing industry. Predictive maintenance, scalability and access to all the data + analytics are ready to change the Industrial world and we at AfourTech are here to help you on this journey.
Some of the services we offer in IIOT
- Architect scalable clustered architecture for IIOT solution based on requirement.
- Develop and test analytics and visualization dashboard/Mobile apps to get more actionable insights with the data generated.
- Develop, Test & Automate different layers of IIoT – devices/sensors, Cloud, Analytics, Actuation etc
- Develop/Use traffic generator / Simulator for tests and data generation.
One of the key challenges in implementing solutions for IIoT would be testing them. It is virtually impossible to get all the possible devices and do testing on them before-hand but the good thing is that these devices all work based on standardized protocols. Our services in IIoT include the experience of working on a vast number of the most prevalent protocols in the market and providing ways to setup a virtual network of these devices with the ability to specify various protocols running on them.
Some of the most commonly used protocols in the IIoT sector that we have in-depth knowledge about are
Easy to use and reliable, this is a very commonly used Master/Slave architecture based protocol. Developed way back in 1979, this protocol is probably the de-facto for communicating between Industrial Electronic Devices. Modbus enables communication among many devices connected to the same network, for example, a system that measures temperature and humidity and communicates the results to a computer. Modbus is often used to connect a supervisory computer with a remote terminal unit (RTU) in supervisory control and data acquisition (SCADA) systems.
A MODBUS master/slave communication is very simple. The Master initiates a command with an ID of the slave machine. Only the slave will pick up and act on the command. The packet contains CRC check for enabling verification of packet at the slave end.
Our Simulator on Modbus enables us to mimic a network and devices on that network talking MODBUS, thus giving us the ability to test the entire communication end-to-end. Read more about our MODBUS simulator here
The Common Industrial Protocol (CIP) is a communications protocol for transferring automation data between two devices.
In the CIP Protocol, every network device represents itself as a series of objects. Each object is simply a grouping of the related data values in a device. For example, every CIP device is required to make an Identity object available to the network. The identity object contains related identity data values called attributes. Attributes for the identity object include the vendor ID, date of manufacture, device serial number, and other identity data. CIP does not specify at all how this object data is implemented, only what data values or attributes must be supported and that these attributes must be available to other CIP devices. CIP provides a unified communication architecture through-out the manufacturing enterprise. Our Simulator for CIP can mimic a typical manufacturing network and communicate using the CIP protocol to assist in real-time testing
IEC 61850 is a communication standard for electrical substation automation systems. IEC 61850 is a part of the International Electrotechnical Commission’s (IEC) Technical Committee 57 (TC57) reference architecture for electric power systems. The abstract data models defined in IEC 61850 can be mapped to a number of protocols. Current mappings in the standard are to MMS (Manufacturing Message Specification), GOOSE (Generic Object Oriented Substation Event) and some others.
These protocols can run over TCP/IP networks or substation LANs using high speed switched Ethernet,
GOOSE is a controlled model mechanism in which any format of data (status, value) is grouped into a data set and transmitted within a time period of 4 milliseconds. GOOSE data is directly embedded into Ethernet data packets and works on the publisher-subscriber mechanism on multicast or broadcast MAC addresses. GOOSE messages are designed to be brand independent. Some vendors offer intelligent electronic devices (IED) that fully support IEC 61850 for a truly interoperable approach within the substation network without requiring vendor specific cables or algorithms. We have the capability of designing customized GOOSE simulators based on all the parameters of the GOOSE packets that need to be parameterized and some of our implementations provide the capability to change parameters like the device ID, App ID etc.
The C37.118 (Synchrophasor Protocol) is the IEEE standard for using synchrophasors in power systems. The standard defines synchronized phasor measurements used in electric power systems and provides a method to quantify measurements and tests to be sure that the measurements conform to the definition. It also defines the Total Vector Error (TVE) limits for measurement accuracy as well as a data communications protocol, including message formats for communicating this data in a real-time system. The SYNCHROPHASOR protocol provided support for both TCP and UDP. We provide support for this protocol while emulating the network as well.
DNP3 was a comprehensive effort to achieve open, standards-based Interoperability between substation computers, RTU’s(Remote Terminal Unit), IED’s (Intelligent Electronic Devices) and Master stations. Communication between Master , RTU’s and IED devices.Said to be Layer-2 Protocol. It is based on the standards of the International Electrotechnical Commission (IEC) Technical Committee 57, Working Group 03 who have been working on an OSI 3 layer “Enhanced Performance Architecture” (EPA) protocol standard for telecontrol applications. DNP3 is an open and public protocol. DNP3 is a protocol used to communicate from Point A to Point B using serial and IP communication over TCP and UDP. DNP3 was originally designed based on three layers of the OSI seven-layer model: application layer, data link layer, and physical layer.