What are the common problems in industrial IoT design?

Whether it's good or bad, the Internet of Things (IoT) has happened in our daily lives; it's still in the toddler stage, but the development model is setting up quickly, if we don't think about the way the Internet of Things is designed, we might Encountered a lot of trouble, especially in the industrial field.

The Internet of Things market has undoubtedly taken off, and wearable devices, sensors, predicTIve maintenance, line analysis, connected cars, asset tracking, smart meters, smart homes, smart cities, smart buildings, etc. can be seen everywhere. But the design behind these programs is often not so "smart."

Perhaps those IoT designs are sensible and innovative, but they are often too piecemeal and rushed to the market; systems created in systems are not focused on system-level design issues.

In order to correct the development of the Internet of Things - at least for industry and other key systems, the Object Management Group (OMG) is active; OMG is a technical standards organization established in 1989, assisting for more than 30 years A variety of different networking systems are combined, and the originally established CORBA (common object request broker) standard allows networked software objects to communicate.

In addition, OMG has also set the DDS (data distribuTIon service) and UML (unified modeling language) standards, but now it focuses on the Industrial Internet of Things (IIoT) and undertakes the management of the Industrial Internet Consortium (IIC). Responsibility to assist in defining shared IoT architecture and interoperability standards for industrial applications.

The definition of the Industrial IoT standard draws on OMG's mission-critical defense system standard UPDM, through which the extension to the more general system, UAF (Unified Architecture Framework); UPDM group co-chairs Matthew Hause and Graham Bleakly, recently with the author I talked about the current IoT design methods and their suggestions on how to improve.

"We are trying to keep people away from the Internet of Things that will be hacked," Bleakley said. "This is what is happening, because the way the Internet of Things is being promoted is based on the fact that you can link anything to anything else, And such a good concept; but the problem is that for other systems such as safety, medical, industrial, etc., if you hold this idea, you will have a lot of trouble."

Hause and Bleakly stated that their idea was to consider IoT design from a system-wide perspective, using model-based systems engineering to define systems and design requirements, and how to put those bytes together.

“The method uses a mathematical notation (notaTIon) to describe the system, which produces more accurate specifications and standards for system design;” Bleakly said: “This avoids the discrepancies that can occur only with text.” Once the system Models are defined so that developers can use simulation tools to test and refine models and requirements.

Hause points out that one of the advantages of this approach is that it provides a level of abstraction that separates "What" from "How", using a layered approach such as defining an IoT design. Enterprise goals such as expected revenue, performance indicators, and ensure that goals are achieved; the model layer is separate from the implementation details, allowing requirements testing to be independent of the solution.

Other levels may include how to deal with the data generated by the system, how the system interacts with the user, and product support; Hause explains: “You can start by defining what you need to do and then decide which things to go in.”

Another benefit of this approach is the ability to handle a full-scale industrial Internet of Things; Bleakley points out that this is: “Let the IoT operate at the enterprise level, rather than just small tasks; this system can become too complex It is no longer a single designer can conceive."

But Bleakley emphasizes that not all things in the Internet of Things can support this formal and well-conceived design process: "This is for systems that are absolutely operational," such as cars, power generation/distribution systems, and medical systems. For the Industrial Internet of Things, it is very meaningful to use a model-based systematic approach to design.

Rechargable Battries

In most cases, today you're better off using rechargeable batteries over disposable ones. ... And you wouldn't lose much performance: The best rechargeables can power your devices on a single charge for just as long as most high-quality single-use batteries can, but at a fraction of the cost over time.

Proper care and maintenance will prolong the life of any product, including your rechargeable batteries. With appropriate care and use, you should expect 2-7 years from most rechargeable batteries. Rechargeable cordless phone batteries can last 1-2 years with the right use and care.

Choose between nickel and lithium batteries. Watch for the memory effect with your NiCd batteries. The battery life decreases when you recharge the battery before it is fully depleted. ...Choose a lithium-ion (Li-ion) battery if you want to be able to charge it at any time.


Rechargeable Battery,Ups Inverter Battery,Rechargable Battries,Rechargeable 900Mah 3.7V Lithium

Shenzhen Glida Electronics Co., Ltd. , https://www.szglida.com

This entry was posted in on