KR101644219B1 - System and Method for Managing Factory - Google Patents

System and Method for Managing Factory Download PDF

Info

Publication number
KR101644219B1
KR101644219B1 KR1020130146862A KR20130146862A KR101644219B1 KR 101644219 B1 KR101644219 B1 KR 101644219B1 KR 1020130146862 A KR1020130146862 A KR 1020130146862A KR 20130146862 A KR20130146862 A KR 20130146862A KR 101644219 B1 KR101644219 B1 KR 101644219B1
Authority
KR
South Korea
Prior art keywords
event data
type
type event
queue
application server
Prior art date
Application number
KR1020130146862A
Other languages
Korean (ko)
Other versions
KR20150063185A (en
Inventor
정경주
허두녕
강길섭
최종기
Original Assignee
주식회사 포스코아이씨티
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 주식회사 포스코아이씨티 filed Critical 주식회사 포스코아이씨티
Priority to KR1020130146862A priority Critical patent/KR101644219B1/en
Publication of KR20150063185A publication Critical patent/KR20150063185A/en
Application granted granted Critical
Publication of KR101644219B1 publication Critical patent/KR101644219B1/en

Links

Images

Classifications

    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/30—Computing systems specially adapted for manufacturing

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Manufacturing & Machinery (AREA)
  • Business, Economics & Management (AREA)
  • Quality & Reliability (AREA)
  • General Engineering & Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • General Factory Administration (AREA)
  • General Health & Medical Sciences (AREA)
  • Economics (AREA)
  • Health & Medical Sciences (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Primary Health Care (AREA)
  • Strategic Management (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)

Abstract

A factory management system according to one aspect of the present invention, which integrates a process control system and a production management system into one by processing a large amount of event data generated in a production process in real time, An interface server, which is to be processed in real time among a plurality of event data generated in production control and process control, and selects first type event data to be processed according to the order in which events are generated; And processing the first type event data prior to the other event data and monitoring whether or not event data identical to the first type event data are being executed when processing the first type event data, And an application server for storing the event data when the same event data as the type event data is being executed and for processing the first type event data when the same event as the first type event data is not being executed .

Figure R1020130146862

Description

System and Method for Managing Factory < RTI ID = 0.0 >

The present invention relates to a factory management system, and more particularly, to a plant management system and method capable of performing a process control function and a production management function.

A typical plant management system consists of a process control system (PC) and a production management system (BC).

The production management system 120 provides the user with the performance data tailored to the production plan and performs the function of establishing the overall production schedule from the work order to the schedule management, inventory management, and logistics management.

The process control system 110 precisely controls the production process in real time. The process control system 110 directly controls the unit facilities and sensors based on the contents of the work instruction received from the production management system 120, Width, length, thickness, etc. to meet customers' requirements.

In this way, in order to precisely control the production process in real time, the process control system 110 must process a large amount of data generated in the production process in real time or in sequence according to the generation order, The general factory management system manages the production control system 120 and the process control system 110 at different levels as shown in FIG. 1, Of the system.

Since the process control system 110 and the production management system 120 are separated from each other in the case of a general plant management system, data that the process control system 110 and the production management system 120 must share , DCS 140, or the measurement device 150, based on actual data acquired from a PLC (Programmable Logic Controller) 130, a DCS (Distributed Control System) 140, or an instrument 150, (Work instruction) data) are redundantly existed, thereby wasting system resources.

In addition, in the case of a general factory management system, a separate EAI (Enterprise Application Integration (not shown)) server must be used for data sharing between the process control system 110 and the production management system 120, There is a problem in that not only the time difference exists but also the data consistency is lowered and the complexity of the system is increased.

In addition, in the case of a general factory management system, the process control system 110 has a restriction that only one process belonging to the user can be confirmed, and the implementation of the production control system 120 and the process control system 110 The maintenance cost of the system is increased because the developers who are fluent in the programming language used in each system are required to maintain these systems.

SUMMARY OF THE INVENTION It is an object of the present invention to provide a factory management system and method that integrates a process control system and a production management system into one by processing a large amount of event data generated in a production process in real time, We will do it.

It is another object of the present invention to provide a factory management system capable of efficiently processing event data to be sequentially processed among event data generated in a production process in accordance with processing order.

Another object of the present invention is to provide a plant management system and method that can confirm not only one process to which an administrator belongs but also all data of all processes.

According to an aspect of the present invention, there is provided a factory management system for managing production management and process control in a unified manner. The factory management system includes a plurality of event data generated during production control and process control, An interface server to process the first type event data to be processed according to the order in which the events are generated; And processing the first type event data prior to the other event data and monitoring whether or not event data identical to the first type event data are being executed when processing the first type event data, And an application server for storing the event data when the same event data as the type event data is being executed and for processing the first type event data when the same event as the first type event data is not being executed .

According to another aspect of the present invention, there is provided a factory management method comprising: receiving event data generated during production control and process control; Storing the first type event data to be processed in the real time among the received event data in accordance with the order in which the events are generated in the waiting queue; Determining whether or not there is the same event data as the first type event data stored in the waiting queue among the event data being executed in the execution queue; As a result of the determination, if the same event data as the first type event data stored in the wait queue exists in the execution queue, processing of the first type event data is suspended. If not, the first type event data stored in the wait queue Moving to an execution queue and processing to generate setting information; And providing the setting information to the equipment that has transmitted the event data corresponding to the setting information.

According to another aspect of the present invention, there is provided a factory management method including: receiving event data generated during production control and process control; Assigning the received event data to one of a plurality of application servers; Storing first type event data to be processed in real time among the allocated event data, the first type event data to be processed according to an order in which an event is generated, in a waiting queue and a database; Determining whether or not there is the same event data as the first type event data stored in the waiting queue among the event data being executed in the execution queue and the event data previously stored in the database; As a result of the determination, if the same event data as the first type event data stored in the wait queue exists in the execution queue and the database, processing of the first type event data is suspended. If not, Moving data to the run queue and processing to generate configuration information; And providing the setting information to the equipment that has transmitted the event data corresponding to the setting information.

According to the present invention, it is possible to perform high-speed processing of event data requiring real-time processing through marking according to classification and classification of event data generated in the field, and to process event data requiring sequential processing, And the setting information for each event data can be provided again to the process according to the order so that the factory control system and the production management system can be implemented as a single system.

In addition, according to the present invention, since the process control system and the production management system are integrally implemented as a single system, the time difference caused by data synchronization between the process control system and the production management system can be fundamentally blocked, .

In addition, according to the present invention, since the process control system and the production management system are integrated into a single system, data conversion through the EAI server is not required for data sharing between the two systems. Therefore, There is an effect that it can be reduced.

In addition, according to the present invention, since the process control system and the production management system are integrally implemented as a single system, not only system resources are wasted due to redundant storage and duplication processing of the same data, but also human resources for system maintenance are reduced. There is an effect that the cost can be reduced.

In addition, according to the present invention, since not only one process belonging to the user but also all the data of all the processes can be confirmed and the post-process can be predicted, the efficiency of the work can be maximized.

1 is a block diagram schematically showing the configuration of a general factory management system;
2 is a block diagram showing a configuration of a factory management system according to a first embodiment of the present invention;
3 is a block diagram showing a configuration of a factory management system according to a second embodiment of the present invention;
4 is a block diagram specifically showing a configuration of the interface server shown in FIG.
FIG. 5 is a block diagram specifically showing the configuration of the application server shown in FIG. 3. FIG.
FIG. 6 is a block diagram showing a configuration of a factory management system according to a third embodiment of the present invention; FIG.
7 is a flowchart showing a factory management method according to the first embodiment of the present invention.
8 is a flowchart showing a factory management method according to a second embodiment of the present invention.

The meaning of the terms described herein should be understood as follows.

The word " first, "" second," and the like, used to distinguish one element from another, are to be understood to include plural representations unless the context clearly dictates otherwise. The scope of the right should not be limited by these terms.

It should be understood that the terms "comprises" or "having" does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or combinations thereof.

It should be understood that the term "at least one" includes all possible combinations from one or more related items. For example, the meaning of "at least one of the first item, the second item and the third item" means not only the first item, the second item or the third item, but also the second item and the second item among the first item, Means any combination of items that can be presented from more than one.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

Factory management system

First Embodiment

2 is a block diagram showing the configuration of a factory management system according to the first embodiment of the present invention.

The factory management system 200 according to the first embodiment shown in FIG. 2 is implemented by integrally integrating the process control system 110 and the production management system 120 as shown in FIG. 1, 110 and the production management system 120, it is necessary to classify event data that requires real-time processing and sequential processing among generated event data, and to process the data in real time and sequentially without user intervention.

In one embodiment, such event data may be provided from a PLC (Programmable Logic Controller) 230, a DCS (Distributed Control System) 240, and an instrument 250 disposed in the field.

That is, the factory management system 200 according to the first embodiment classifies event data provided from the PLC 230, the DCS 240, and the meter 250, So that the setting information of each event data can be provided to the process again, thereby enabling the integrated implementation of the process control system and the production management system.

The factory management system 200 according to the first embodiment includes an interface server 210 and an application server 220, as shown in FIG.

First, the interface server 210 receives event data from at least one of PLC (Programmable Logic Controller) 230, DCS (Distributed Control System) 240 and instrument 250 disposed in the factory, To the application server 220.

The interface server 210 includes an interface unit 212, a determination unit 214, and a marking unit 216, as shown in FIG.

First, the interface unit 212 interfaces with the interface server 210, the PLC 230, the DCS 240, and the measuring instrument 250, and receives information from at least one of the PLC 230, the DCS 240, and the measuring instrument 250 Receives event data generated by the PLC 230, the DCS 240, and the instrument 250. In one embodiment, the event data received by the interface unit 212 from at least one of the PLC 230, the DCS 240, and the instrument 250 may include movement data of a logistics such as a steel product, And may include operational result data performed by each of the unit facilities of the system.

Next, the determination unit 214 classifies event data received through the interface unit 212 into one of a first type and a second type according to a predetermined processing strategy.

In one embodiment, the determination unit 214 classifies event data to be processed at high speed according to an event generation order among event data received through the interface unit 212 as first type event data, And classifies the processable event data into the second type event data.

For example, in the case of movement data of a logistics such as a steel product generated at a factory, since each position of the steel product is to be sequentially processed, it is classified as the first type event data, and the operation result data Are not to be processed in the order of occurrence, they are classified as second type event data.

Next, the marking unit 216 marks the identifier indicating the priority processing request to the corresponding event data so that the first type event data to be processed at a high speed can be processed first according to the event occurrence order. In one embodiment, the marking unit 216 marks the header of the first type event data classified by the determination unit 214 as "H" so that the corresponding event data is processed at a high speed So that it can be easily recognized.

The reason why the marking unit 216 marks the identifier in the header of the first type event data is that the application server 220 inspects only the header of the event data and quickly checks whether the event data is event data to be processed first So that a large amount of event data can be processed in real time.

In one embodiment, the marking unit 216 marks "L" in the header of the event data for the second event data which is event data that need not be processed at high speed, so that the application server 220 It is also possible to select only event data at a faster rate.

Next, the application server 220 receives event data from the interface server 210, processes the received event data according to predetermined business logic, and generates setting information corresponding to the event data. The application server 220 returns the generated setting information to the interface server 210 so that the interface server 210 can provide the setting information to the PLC 230, the DCS 240, or the measuring instrument 250.

In particular, the application server 220 according to the present invention checks the type of the event data received from the interface server 210 and schedules the processing method according to the confirmed type. Hereinafter, the configuration of the application server 220 will be described in more detail.

2, the application server 220 according to the first embodiment of the present invention includes a dispatcher 222, a scheduler 224, a wait queue 226, an execution queue 228, and a life cycle manager (229).

The dispatcher 222 receives the event data to be processed from the interface server 210 and provides the event data to the scheduler 224. The dispatcher 222 receives the setting information generated according to each event process from the scheduler 224, (210).

Next, when the event data is received from the dispatcher 222, the scheduler 224 confirms the identifier included in the header of the event data, and processes the corresponding event data according to the identified identifier.

Specifically, when "H" is marked in the header of the event data, the scheduler 224 determines that the event data is the first type event data requiring priority processing, and if the header of the event data indicates "L" It is determined that priority is given to the event data to be marked and the first type event data is recorded in the waiting queue 226. [ Thereafter, the scheduler 224 monitors whether the same event data as the first type event data recorded in the wait queue 226 is being executed in the run queue 228 and notifies the wait queue 226 of the run queue 228, Type event data recorded in the wait queue 226 to the execution queue 228 when it is determined that the same event data as the first type event data recorded in the execution queue 228 is not being executed, .

In this manner, when the event data is the first type event data, the corresponding event data is to be sequentially processed according to the order in which they are generated. Therefore, the scheduler 224, before processing the first type event data, Is recorded in the waiting queue 226, and then it is monitored whether or not the same event data is being executed in the execution queue 228. When the event data is not being executed, the corresponding event data is processed so that the corresponding event data is sequentially processed.

On the other hand, when the header of the event data received from the dispatcher 222 is marked "L", the scheduler 224 determines that the event data is the second type event data, (228) and processes it according to predetermined business logic. If the event data is the second type event data, the corresponding event data is event data that need not be sequentially processed. Accordingly, the scheduler 224 directly moves the second type event data to the execution queue 228 Allowing event data to be processed faster.

The scheduler 224 provides configuration information, which is generated according to the processing of each event data, to the interface server 210 through the dispatcher 222 each time processing of event data is completed.

The wait queue 226 indicates a queue in which event data is recorded before execution of event data requiring processing, and the execution queue 228 indicates a queue in which event data to be processed is actually executed.

The life cycle manager 229 deletes the event data from the execution queue 228 when the processing of the event data is completed by the scheduler 224. [ In one embodiment, the lifecycle manager 229 may delete the event data from the wait queue 226 if there is event data waiting for a predetermined period of time or longer in the wait queue 226.

Second Embodiment

3 is a block diagram showing the configuration of a factory management system according to a second embodiment of the present invention.

The factory management system 300 according to the second embodiment shown in FIG. 3 includes an interface server 310, a plurality of application servers 320, and a database 330. That is, the factory management system 300 according to the second embodiment as shown in FIG. 3 is different from the factory management system 200 according to the first embodiment shown in FIG. 2 in that a plurality of application servers 320 And a database 330 is additionally provided for efficient interoperability between a plurality of application servers 320. [

The factory management system 300 according to the second embodiment of the present invention includes a plurality of application servers 320 for processing event data as shown in FIG. The processing speed of the event data can be improved.

Hereinafter, the configuration of the factory management system according to the second embodiment will be described in more detail with reference to Figs. 3 to 5. Fig.

First, the interface server 310 receives event data from at least one of the PLC 340, the DCS 350, and the instrument 360 disposed in the factory, and transmits the received event data to a plurality of application servers 220. [ . The configuration of the interface server 310 will be described in more detail with reference to FIG.

4 is a block diagram illustrating a configuration of an interface server according to a second embodiment of the present invention. 4, the interface server 310 according to the second embodiment of the present invention includes an interface unit 312, a determination unit 314, a marking unit 316, and an allocation unit 318 .

The functions of the interface unit 312, the determination unit 314 and the marking unit 316 are the same as those of the interface unit 212, the determination unit 214, and the marking unit 216 shown in FIG. And thus a detailed description thereof will be omitted.

The assigning unit 318 selects the application server 320 to which the marked data is to be transmitted by the marking unit 316 among the plurality of application servers 320 and transmits the event data marked with the selected application server 320 .

In one embodiment, the assigning unit 318 may select an application server 320 to send the marked event data according to a round robin method. Accordingly, the allocating unit 318 sequentially transmits the event data to the plurality of application servers 320. [

Referring again to FIG. 3, each of the plurality of application servers 320 receives event data from the interface server 310, processes the received event data according to predetermined business logic, and generates setting information corresponding to the event data do. Each of the plurality of application servers 320 returns the generated configuration information to the interface server 310 so that the interface server 310 provides the configuration information to the PLC 340, the DCS 350, or the measuring device 360 .

In particular, in the case of the second embodiment, since a plurality of application servers 320 are implemented, each of the application servers 320 can process event data in consideration of the progress status of event data being executed in another application server 320 ≪ / RTI > Hereinafter, the configuration of the application server 320 will be described in more detail with reference to FIG.

5 is a block diagram illustrating a configuration of an application server according to a second embodiment of the present invention. 5, the application server 320 according to the second embodiment of the present invention includes a dispatcher 322, a scheduler 324, a buffering queue 325, a wait queue 326, an execution queue 327 A watch dog 328, and a life cycle manager 329. [

The function of the dispatcher 322 is similar to the dispatcher 222 shown in FIG. 2, and receives event data to be processed from the interface server 310 and provides the event data to the scheduler 324, And receives the setting information from the scheduler 324 and transfers it to the interface server 310. [

Next, when the event data is received from the dispatcher 322, the scheduler 324 confirms the identifier included in the header of the event data, and processes the corresponding event data according to the identified identifier.

Specifically, when the header of the event data is marked with "H ", the scheduler 324 determines that the event data is the first type event data to be preferentially processed according to the generated order, Writes the data to the buffering queue 325, and provides the watchdog 328 with the recording of the first type event data.

The scheduler 324 then moves the first type event data recorded in the buffering queue 325 to the wait queue 326 when the result of the determination that the database 330 operates normally from the watchdog 328 is received And inserts the first type event into the database 330 at the same time.

Thereafter, it is monitored whether or not the same event data as the first type event data recorded in the wait queue 326 is being executed in the execution queue 327, and the event data stored in the wait queue 326 If it is determined that the same event data as the first type event data is not being executed, the scheduler 324 determines whether the same event data as the first type event data recorded in the wait queue 326 is already stored in the database 330 ≪ / RTI >

If the event data identical to the first type event data recorded in the wait queue 326 is not already stored in the database 330 as a result of the monitoring, the scheduler 324 notifies the first type The event data is moved to the execution queue 327 and processed according to predetermined business logic.

As a result of monitoring, when the same event data as the first type event data recorded in the wait queue 326 is being executed in the execution queue 327, it means that the same event data is already being processed in the application server 320 The scheduler 324 waits for the processing of the corresponding event data until the processing of the event data already in process is completed. If the same event data as the first type event data recorded in the waiting queue 326 is already stored in the database 330 even though the event data is not being executed in the execution queue 327, It means that the event data is already being processed. Therefore, the scheduler 324 waits for the processing of the event data until the processing of the event data already being processed by the other application server 320 is completed.

On the other hand, when the header of the event data received from the dispatcher 322 is marked "L", the scheduler 324 determines that the event data is the second type event data, (327) and processes it according to predetermined business logic. If the event data is the second type event data, the corresponding event data is event data that need not be sequentially processed. Accordingly, the scheduler 324 directly moves the second type event data to the execution queue 327 Allowing event data to be processed faster.

The scheduler 324 provides configuration information generated according to the processing of each event data to the interface server 310 through the dispatcher 322 each time processing of event data is completed.

The buffering queue 325 is a queue in which event data requiring processing is recorded before the normal operation of the database 330 is confirmed and the waiting queue 326 is a queue in which the database 330 is confirmed to be operating normally Means a queue in which event data is recorded before execution of event data requiring processing, and an execution queue 327 means a queue in which event data to be processed is actually executed.

The watchdog 328 determines whether the database 330 is operating normally when the fact that the event data to be processed has been written to the buffering queue 325 from the scheduler 324 is determined, And feed back the result to the scheduler 324. [ On the other hand, if it is determined that the database 330 is not operating normally, the result is transmitted to the interface server 310 through the dispatcher 322 so that the interface server 310 does not transmit new event data to the application server 320 . In this case, the interface server 310 stores new event data.

Next, the life cycle manager 329 deletes the event data from the execution queue 327 and the database 330 when the processing of the event data is completed by the scheduler 324. The lifecycle manager 329 may store the event data in the buffering queue 325 or the wait queue 326 for a predetermined period of time or longer, Can be deleted in the wait queue 326. [

Referring again to FIG. 3, the database 330 records event data to be processed by each application server 320. In one embodiment, since the first type event data must be processed in real time and returned to the process, a maximum fast response speed is required. Since the physical database (DB), which is a general data storage place, In the present invention, a main memory database (MMDB) can be used as the database 330 for improving the processing speed and response speed of event data.

In the second embodiment, the factory management system 300 includes a plurality of application servers 320 and a plurality of application servers 320 together. . 6, the factory management system 600 according to the third embodiment includes a plurality of clusters 320a and 320b configured by clustering a plurality of application servers, and a plurality of clusters 320a and 320b interworking with the respective clusters 320a and 320b. And a plurality of databases 330a and 330b. That is, a plurality of application servers included in the first cluster 320a use the first database 330a together, and a plurality of application servers included in the second cluster 320b use the second database 330b together . The factory management system 600 according to the third embodiment can further improve the processing speed as compared with the factory management system 300 according to the second embodiment.

How to manage the factory

Hereinafter, a factory management method according to the present invention will be described with reference to FIGS. 7 and 8. FIG.

First Embodiment

7 is a flowchart showing a factory management method according to the first embodiment of the present invention.

The factory management method shown in Fig. 7 can be performed by a factory management system having a configuration as shown in Fig.

First, the interface server receives event data from at least one of a PLC, a DCS, and an instrument disposed in the factory (S700). In one embodiment, the event data received by the interface unit from at least one of the PLC, the DCS, and the instrument may include movement data of the logistics such as steel products generated in the factory, and operation result data performed by each unit facility of the factory .

Thereafter, the interface server classifies received event data into one of a first type and a second type according to a predetermined processing strategy (S710). In one embodiment, the interface server classifies event data to be processed at a high speed according to an event generation order among received event data into first type event data, and event data that can be processed regardless of an event generation order, Type event data.

For example, in the case of movement data of a logistics such as a steel product generated at a factory, since each position of the steel product is to be sequentially processed, it is classified as the first type event data, and the operation result data Are not to be processed in the order of occurrence, they are classified as second type event data.

Next, the interface server marks an identifier indicating the type of the event data in the event data according to the classification result (S720). In one embodiment, if the event data is classified as the first type, the interface server additionally marks the header of the corresponding event data as " H "to indicate that the corresponding event data is the first type event data, Type, it is possible to indicate that the corresponding event data is the second type event data by additionally marking "L" in the header of the event data.

Thereafter, the interface server transmits the event data marked with the identifier to the application server (S730).

When the application server receives the event data from the interface server, the application server determines the type of the received event data (S740). In one embodiment, the application server can determine the type of event data by checking the identifier included in the header of the received event data. For example, when "H" is marked in the header of the event data received as a result of the identification, it is determined that the event data is the first type event data, and if the header of the received event data is marked "L" It can be determined that the corresponding event data is the second type event data.

If the received event data is the first type, the application server writes the first type event data to the waiting queue (S750). Thereafter, the application server determines whether the same event data as the first type event data recorded in the waiting queue is being executed in the execution queue (S760). As a result of the determination, when it is determined that the same event data as the first type event data recorded in the waiting queue in the execution queue is not being executed, the application server moves the first type event data recorded in the waiting queue to the execution queue Processing is performed according to predetermined business logic to generate setting information corresponding to the event data (S770).

If it is determined in S760 that the same event data as the first type event data recorded in the waiting queue in the execution queue is being executed, the application server waits for the corresponding event data until the event data in the execution queue is processed Queue.

On the other hand, if it is determined in step S740 that the received event data is of the second type, the application server moves the second type event data to the execution queue and processes it according to predetermined business logic to generate setting information corresponding to the event data S780). If the event data is the second type event data, since the event data is not required to be sequentially processed, the application server directly moves the second type event data to the execution queue, Allow the data to be processed.

Thereafter, the application server provides the configuration information generated in S770 and S780 to the interface server (S790).

7, when the event data is completely processed, the application server deletes the corresponding event data from the execution queue, and if there is event data waiting for a predetermined time or longer in the wait queue, It can also be deleted from the waiting queue.

Second Embodiment

8 is a flowchart showing a factory management method according to a second embodiment of the present invention.

The factory management method shown in Fig. 8 can be performed by a factory management system having a configuration as shown in Fig. 3 or Fig.

Since the process of S800 to S820 is the same as the process of S700 to S720 shown in Fig. 7, a detailed description will be omitted.

After step S820, the interface server selects an application server to which the marked event data is to be transmitted through the S820 among the plurality of application servers (step S825). In one embodiment, the application server may select an application server to send the marked event data according to a round robin method.

Thereafter, the interface server transmits the marked event data to the selected application server in step S825 (S830). In a case where the application server to transmit the marked event data in step S825 is determined according to the round robin method, the interface server sequentially transmits the event data to the plurality of application servers.

After receiving the event data from the interface server, the application server determines the type of the received event data (S840). In one embodiment, the application server can determine the type of event data by checking the identifier included in the header of the received event data. For example, when "H" is marked in the header of the event data received as a result of the identification, it is determined that the event data is the first type event data, and if the header of the received event data is marked "L" It can be determined that the corresponding event data is the second type event data.

If the received event data is the first type, the application server writes the first type event data to the buffering queue (S842). Then, the application server determines whether the database is operating normally (S844). If it is determined that the database is operating normally, the application server moves the first type event data recorded in the buffering queue to the waiting queue, (S850). Thereafter, the application server determines whether the same event data as the first type event data recorded in the waiting queue is being executed in the execution queue (S860). If it is determined that the same event data as the first type event data recorded in the waiting queue in the execution queue is not being executed, the application server stores the same event data as the first type event data recorded in the waiting queue in the database It is determined whether it is already stored (S862). As a result of the determination, if the same event data as the first type event data recorded in the waiting queue is not already stored in the database, the application server moves the first type event data recorded in the waiting queue to the execution queue, And generates setting information corresponding to the event data (S870).

On the other hand, if it is determined in step S860 that the same event data as the first type event data recorded in the waiting queue is being executed in the execution queue, it means that the same event data is already being processed in the application server. If the same event data as the first type event data recorded in the queue is already stored in the database, it means that the same event data is already being processed by another application server. Therefore, The corresponding event data is queued in the waiting queue.

If it is determined in step S844 that the database is not operating normally, the application server provides the determination result to the interface server so that the interface server does not transmit new event data to the application server in step S846.

On the other hand, if it is determined in step S840 that the received event data is of the second type, the application server moves the second type event data to the execution queue and processes it according to predetermined business logic to generate setting information corresponding to the event data S880). If the event data is the second type event data, since the event data is not required to be sequentially processed, the application server directly moves the second type event data to the execution queue, Allow the data to be processed.

Thereafter, the application server provides the configuration information generated in steps S870 and S880 to the interface server (S890).

8, when the event data is completely processed, the application server deletes the event data from the execution queue and the database, and when there is event data waiting for a predetermined time or longer in the wait queue, The event data may be deleted from the wait queue.

The factory management method may be implemented in a form of a program that can be executed using various computer means. The program for performing the factory management method may be a hard disk, a CD-ROM, a DVD, a ROM, , Or a computer-readable recording medium such as a flash memory.

Those skilled in the art will appreciate that the invention described above may be embodied in other specific forms without departing from the spirit or essential characteristics thereof.

It is therefore to be understood that the above-described embodiments are illustrative in all aspects and not restrictive. The scope of the present invention is defined by the appended claims rather than the detailed description and all changes or modifications derived from the meaning and scope of the claims and their equivalents are to be construed as being included within the scope of the present invention do.

200, 300, 600: factory management system 210, 310: interface server
220, 320: Application server 212, 312:
214, 314: Judgment section 216, 316: Marking section
218: Assignment section 222, 322: Dispatcher
224, 324: scheduler 229, 329: life cycle manager
328: Watchdog 330: Database

Claims (17)

The first type event data to be processed in real time in the order of occurrence of the events, and the real-time processing and the sequential processing, which are to be sequentially processed according to the order in which the events are generated, An interface server which is unnecessary and distinguishes into second type event data that requires processing in the production control and process control; And
And an application server for processing the first type event data and the second type event data,
The application server comprises:
If the first type event data stored in the waiting queue is not identical to the first type event data stored in the waiting queue among the event data being processed in the executing queue after storing the first type event data in the waiting queue, And a scheduler for processing the first type event data by moving to the queue and moving the second type event data directly to the execution queue. The method according to claim 1,
Wherein the interface server receives the event data from at least one of a PLC (Programmable Logic Controller), a DCS (Distributed Control System), and an instrument. The method according to claim 1,
Further comprising a database storing first type event data transmitted from a plurality of application servers,
The application server comprises:
The waiting queue storing first type event data received from the interface server; And
Further comprising: an execution queue for processing the second type event data and the first type event data stored in the wait queue,
Wherein the scheduler stores the first type event data in the wait queue and the database, and updates the first event data stored in the wait queue among the event data being processed in the execute queue and the event data previously stored in the database And if there is no event data identical to the type event data, moves the first type event stored in the wait queue to the execution queue and processes the first type event. The method of claim 3,
The application server comprises:
A buffering queue in which the first type event data is temporarily stored; And
Further comprising a watchdog to monitor whether the database is operating normally,
The scheduler includes:
And storing the first type event data in the buffering queue and moving the first type event data stored in the buffering queue to the waiting queue and the database if it is determined by the watchdog that the database is operating normally Factory management system. The method of claim 3,
The application server comprises:
And a lifecycle manager for deleting the first type event data from the execution queue and the database when the processing of the first type event data is completed. The method of claim 3,
Wherein the interface server provides the event data to the plurality of application servers according to a round robin method. The method according to claim 1,
The application server
The waiting queue storing the first type event data received from the interface server; And
Further comprising: an execution queue for processing the second type event data and the first type event data stored in the wait queue. delete The method according to claim 1,
Wherein the first type event data includes movement data of the logistics, and the second type data includes operation result data. The method according to claim 1,
The application server includes a plurality of application servers,
The first application server further monitors whether or not the same event data as the first type event data is being processed by the first application server different from the first application server in processing the first type event data, Type event data when the same event data as the first type event data is being processed, and to process the first type event data when the same event as the first type event data is not being processed. The method according to claim 1,
The application server processes the first type event data and the second type event data according to a predetermined business logic to generate setting information corresponding to the event data,
Wherein the interface server transmits the setting information generated by the application server to the PLC, the DCS, and the instrument that have transmitted the event information corresponding to the setting information. Receiving, by the interface server, event data generated during production control and process control;
The application server determines whether the received event data is first type event data to be processed in real time but must be processed according to the order in which the event is generated or real time processing and sequential processing are unnecessary and processing is required in the production management and process control Determining whether the event is a second type event;
If the received event data is the first type event data, the application server stores the first type event data in the wait queue, and then, among the event data being processed in the execute queue, Type event data, if the same event data exists, and if the event data does not exist, if the event data does not exist, moving the first type event data stored in the wait queue to an execution queue and processing the generated first type event data to generate setting information;
If the received event data is the second type event data, the application server directly moves the second type event data to the execution queue and processes the generated second type event data to generate setting information; And
And the application server providing the setting information through the interface server to the equipment that has transmitted the event data corresponding to the setting information. Receiving, by the interface server, event data generated during production control and process control;
The interface server assigning the received event data to one of a plurality of application servers;
The application server determines whether the assigned event data is first type event data to be processed in real time but according to the order in which the event is generated, or real time processing and sequential processing are not necessary, Determining whether the event is a required second type event;
If the received event data is the first type event data, the application server stores the first type event data in the waiting queue and the database, and then stores the event data being processed in the execution queue and the event data If there is the same event data as the first type event data stored in the waiting queue among the data, processing of the first type event data is suspended. If not, the first type event data stored in the waiting queue is moved to the execution queue And generating setting information;
If the received event data is the second type event data, the application server directly moves the second type event data to the execution queue and processes the generated second type event data to generate setting information; And
And the application server providing the setting information through the interface server to the equipment that has transmitted the event data corresponding to the setting information. 14. The method of claim 13,
The step of moving the first type event data stored in the wait queue to the execution queue to process the configuration information,
Storing the first type event data in a buffering queue;
Monitoring whether the database is operating normally; And
And storing the first type event data stored in the buffering queue in the waiting queue and the database when the database operates normally. 14. The method of claim 13,
Wherein the generating of the first type event data deletes the first type event data from the execution queue and the database when the processing of the first type event data is completed. delete A computer-readable recording medium on which a program for carrying out the factory management method according to any one of claims 12 to 15 is recorded.
KR1020130146862A 2013-11-29 2013-11-29 System and Method for Managing Factory KR101644219B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020130146862A KR101644219B1 (en) 2013-11-29 2013-11-29 System and Method for Managing Factory

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020130146862A KR101644219B1 (en) 2013-11-29 2013-11-29 System and Method for Managing Factory

Publications (2)

Publication Number Publication Date
KR20150063185A KR20150063185A (en) 2015-06-09
KR101644219B1 true KR101644219B1 (en) 2016-08-01

Family

ID=53503773

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020130146862A KR101644219B1 (en) 2013-11-29 2013-11-29 System and Method for Managing Factory

Country Status (1)

Country Link
KR (1) KR101644219B1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10780583B2 (en) 2015-10-26 2020-09-22 Hanwha Precision Machinery Co., Ltd. System and method of controlling robot

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002229606A (en) * 2001-01-31 2002-08-16 Nec Corp State transition model executing device, state transition model executing method and program

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9047144B2 (en) * 2009-11-04 2015-06-02 International Business Machines Corporation System and method for providing Quality-of-Services in a multi-event processing environment

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002229606A (en) * 2001-01-31 2002-08-16 Nec Corp State transition model executing device, state transition model executing method and program

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10780583B2 (en) 2015-10-26 2020-09-22 Hanwha Precision Machinery Co., Ltd. System and method of controlling robot

Also Published As

Publication number Publication date
KR20150063185A (en) 2015-06-09

Similar Documents

Publication Publication Date Title
JP4532423B2 (en) Server system
US20140364987A1 (en) Operating plan formulation support system and method
WO2016078008A1 (en) Method and apparatus for scheduling data flow task
US9430285B2 (en) Dividing and parallel processing record sets using a plurality of sub-tasks executing across different computers
US10979505B1 (en) Distributed storage system and data migration method
US20200174844A1 (en) System and method for resource partitioning in distributed computing
US9552567B2 (en) Computer-implemented methods and systems for determining fleet conditions and operational management thereof
JPWO2012026034A1 (en) Scheduler, multi-core processor system, and scheduling method
US11100437B2 (en) Method for improving semiconductor back-end factories
US10346784B1 (en) Near-term delivery system performance simulation
US9244718B2 (en) Virtual machine resource allocation based on connection time coverage exceeding a minimum threshold
CN104407926A (en) Scheduling method of cloud computing resources
Pongsakorn et al. Container rebalancing: Towards proactive linux containers placement optimization in a data center
US10210284B2 (en) Method and system for managing data in a manufacturing execution system
JP2014228983A (en) Work management apparatus, and work management method, and computer program
WO2014136302A1 (en) Task management device and task management method
WO2018097058A1 (en) Analysis node, method for managing resources, and program recording medium
Borangiu et al. Smart manufacturing control with cloud-embedded digital twins
KR101644219B1 (en) System and Method for Managing Factory
US20170024245A1 (en) Workload-aware shared processing of map-reduce jobs
CN107528871A (en) Data analysis in storage system
US20230155958A1 (en) Method for optimal resource selection based on available gpu resource analysis in large-scale container platform
JP5776813B2 (en) Multi-core processor system, control method and control program for multi-core processor system
JP6753521B2 (en) Computational resource management equipment, computational resource management methods, and programs
US10852908B2 (en) Method and system for controlling a display screen based upon a prediction of compliance of a service request with a service level agreement (SLA)

Legal Events

Date Code Title Description
A201 Request for examination
E902 Notification of reason for refusal
E701 Decision to grant or registration of patent right
GRNT Written decision to grant