Overview of the Integrated Production Information Analysis Platform (miias V1.0)

I haven't written a blog for a long time. Some time ago, the company was busy developing software platforms. Although a project was successfully implemented using the platform, there are still many improvements in the future. To celebrate the successful implementation of an Enterprise Energy Management project using the platform, I will write a few articles laterArticleTo consolidate the results and sort out the ideas. After all, it is better to look at the problem in a different mood. Another reason is that I want to exchange ideas with you to get better ideas. According to my understanding, there is no similar software development platform in China that closely integrates Production Information Collection with upper-layer portals. If anyone knows a similar platform, they also want to discuss it together. (PS: some time ago, many people asked me why I suddenly did not write "study every day. Sorry, I will complete it later. I would like to thank many of my friends for their comments and suggestions)

I 've talked a lot of nonsense about the above. Now, let's get into the subject. The name of the Integrated Production Information Analysis Platform (miias) is very big and abstract, you still don't know what this platform can do. In this article, I will give a rough introduction to the functions of the platform. The Energy Management System in is a solution package customized based on this platform. The physical architecture shows that the platform is related to data collection. We can use the OPC Data Collection service to extract data and store the data to the data storage server on the platform. Then, the data is cleaned, analyzed, and computed through the computing service interface of the platform, and finally displayed in the SharePoint Portal.

We will not talk about the technical architecture and implementation details. We will look at this platform from the implementation perspective. The upper layer of the platform is fully based on SharePoint 2010 (fully compatible with foundation, standard, and replicises versions ),

After the platform is installed, "miias Infrastructure" will be added to the website set settings ".

After the feature is activated, we will see it on the website's operation interface:

For "platform model management", it should be the most used page in the implementation process. The red box on the left of the figure shows the model nodes and the buttons related to these nodes. Because this is the first time the page is loaded, only two root nodes are configured for the platform and business model. The description will be expanded one by one, and the configuration information of the selected node will be displayed on the right.

For the "model type management" page, the type of each node in the model is configured through this page.

It is part of my "platform configuration". It can be seen that the basic platform layer includes scheduled task execution, OPC Data Collection Service, computing and dumping, based on energy management

Choose "platform configuration"> "Data Source"> "energy collection group"> "collection point 1" and click "edit. The Edit node Attributes dialog box is displayed.

For related nodes in the "Business Configuration Model:

Displays the collected data after computation.

 

In the future, I will use the following five articles to introduce the platform Functions and design concepts,

1. Production Information Integrated analysis platform-Overview

2. Integrated Production Information Analysis Platform-type and attribute of model nodes

3. Integrated Production Information Analysis Platform-underlying data collection and dump Service

4. Integrated Production Information Analysis Platform-scalability of the platform

5. Integrated Production Information Analysis Platform-miias-based enterprise energy management solution package

I will also discuss the difficulties encountered in the development and implementation process:

• Solution to Ajax cross-origin access problems
• Changes in Platform service hosting
• System performance problems
• Tangle of data cache service
• Planning of collected data storage
• Query and compression of real-time data curves and historical dataAlgorithm
• Scalability of scheduled tasks
• Implementation of frontend computing script Functions
• Time Difference between natural third-shift and production third-shift
• OPC collection service from scratch

------------- End -------------------