Event-driven graphical representative schema for job-shop-type material flows and data computing usingautomatic identification of radio frequency identification tags

Abstract

In order to track material flow in job shops more accurately and effectively, this paper presents an 'event-triggering time-state' graphical schema-based operation model for describing and formalizing material flow. At the same time, the operation model is associated with valid radio frequency identification (RFID) tags. Then judgement rules are proposed for identifying and picking out valid ones from all found RFID tags. In this way, material flow can be tracked effectively and in real time through use of the multi-view technique. Finally, a case is studied for demonstrating the feasibility and availability of the proposed model and method.

An RFID-Driven Graphical Formalized Deduction for Describing the Time-Sensitive State and Position Changes of Work-in-Progress Material Flows in a Job-Shop Floor

“…(2) Many researchers are focused on the fully-cover layout problems and precise localization algorithms of RFID in order to know the accurate position of an object so as to realize trackability and traceability. But actually, the nature of RFID technology is not to locate the accurate position but to monitor the state of an object changed by time [33]. Considered from this point of view, these two topics are deviated from the nature of RFID technology, which is not correct in some sense.…”

Real-Time Shop-Floor Production Performance Analysis Method for the Internet of Manufacturing Things

“…The extraction process from primitive event to basic event can be described by the pseudo code shown in Algorithm 1. / / represent the material number (4) if the object was first read by reader 1 at 1 //Reader 1 represent the entrance reader of the process line (5) then Create event BE 0,1 = ( .ID, 0 , 1(ts), launch) //New product launch (6) else if the object was last read by reader at 2 //Reader represent the exit reader of the process line (7) then Create event BE ,4 = ( .ID, , 2(te), finish) //The product is finished (8) else the object was read by reader at 3 //The reader in the process line (9) if first read (10) then Create event BE ,1 = ( .ID, , 3(ts), infield) //The infield event (11) and BE ,2 = ( .ID, −1 , 1(ts), 3(te), stay) //The stay event (12) and BE ,3 = ( .ID, −1 , 3(te), outfield) //The outfield event (13) Else Create event BE ,2 = ( .ID, −1 , 1(ts), 3( now), stay) //The stay event Algorithm 1: The extraction process from primitive event to basic event.…”

“…. ., attr , //Calculation based on the different complex event rule (9) Ts as ts, (10) Te as te (11) From CE, Calculation Process (12) Where CE.process.ID = CrE.process.ID (13) or CE.WIP.ID = part of product.ID Algorithm 3: The extraction process from complex event to critical event.…”

“…But how to easily apply the concept design into real-life manufacturing plants should be further investigated. For the real-time manufacturing information processing, the event model has been widely adopted as seen in [9][10][11][12]. References [13][14][15][16] describe some predicted models for manufacturing exceptions.…”

“…In the field of real-time manufacturing information capturing, Zang and Fan [9] implemented an event processing mechanism in enterprise information systems based on RFID, including the architecture, data structures, optimization strategies, and algorithm to address the challenges posed by the fast moving market. Jiang et al [10] presented an "event-triggering timestate" graphical schema-based operation model for describing and formalizing material flow. Fang et al [11] presented an event-driven shop-floor work in progress (WIP) management platform for creating a ubiquitous manufacturing (UM) environment to process the huge amount of RFID data into useful information for managerial uses.…”