Figure 1 - uploaded by Cheng Hsu
Content may be subject to copyright.
Source publication
Integration has become a self-evident goal in today's manufacturing enterprises. Since the late 1970's, numerous major efforts have been launched worldwide to develop, employ, and deploy information technology for integration as a strategic weapon to compete in the global marketplace. This paper discusses a unique approach to the integration proble...
Contexts in source publication
Context 1
... integrated information system will provide access to the organization's information resources and will use this information to assist in designing, implementing and controlling the enterprise [7]. As shown in Figure 1, this information includes an enterprise information model describing the data resources of the local subsystems and their control strategy and tactics in the form of rules. The information model also includes knowledge about the dynamics of information transfer such as what and how information is shared among local systems and under what circumstances it is used [8]. ...
Context 2
... this screen, for instance, its description and format are shown. Figure 10 illustrates other information resources in the enterprise that are related to "part". Note that the same object "part" has three different names and two implementation formats. ...
Context 3
... user interface provides pop-up menus whose items are generated dynamically from the contents of the metadatabase (Figure 11). The user needs only to choose the appropriate data items in order to formulate the query. ...
Context 4
... data items may later be deleted or may have conditions placed on them. Figure 12 illustrates a path through the data items that could be followed to generate the sample query. This figure does not depict the user interface but rather shows how related tables are traversed to identify the various data items. ...
Context 5
... move to the bottom half of our user interface and attach conditions on CUSTOMER_NAME and DATE_DESIRED. Since this terminates our query, we indicate so by selecting the DO QUERY button on the upper right corner of the screen (Figure 11). Then, after waiting for requests over the network to be satisfied and then joined together, we have the answer to our query ( Figure 13). ...
Context 6
... this terminates our query, we indicate so by selecting the DO QUERY button on the upper right corner of the screen (Figure 11). Then, after waiting for requests over the network to be satisfied and then joined together, we have the answer to our query ( Figure 13). ...
Context 7
... integration efforts focus on integrating systems at the data-level; that is, determining what pieces of data are used at what systems and writing the code to move shared data between applications. If the task is to transfer information between a Shop Floor Control System and an Order Processing System, many programmers would choose to obtain the requirements from each and hardcode the data extraction and upload between these systems (Figure 14a). ...
Context 8
... metadatabase approach incorporates the control logic through a model based methodology. Instead of hard-coding the data links between systems, knowledge of information interaction is derived from the model, and rules are generated for moving information ( Figure 14b). This rule based architecture is adaptive since a change in the model can automatically change the rules. ...
Context 9
... then get to the GLOBAL DATA MANAGEMENT MENU FOR APPLICATION : SHOP_FLOOR ( Figure 15). The active-mode menu shows three groups of selections. ...
Context 10
... show the generation of a Data Integration Rule, we will go into the Active Mode Main Menu and pick GENERATE RULES FOR EQUIVALENT DATA ITEMS (Figure 15). Shown in Figure 16 is the rule representation of equivalent data ORDER_ID and CUSTOMER_ORDER_ID involving Shop Floor Control and Order Processing System respectively. ...
Context 11
... show the generation of a Data Integration Rule, we will go into the Active Mode Main Menu and pick GENERATE RULES FOR EQUIVALENT DATA ITEMS (Figure 15). Shown in Figure 16 is the rule representation of equivalent data ORDER_ID and CUSTOMER_ORDER_ID involving Shop Floor Control and Order Processing System respectively. This rule is derived from the knowledge embedded in the model. ...
Context 12
... GLOBAL DATA MANAGEMENT MENU FOR APPLICATION : SHOP_FLOOR ******************************************************** (Figure 7). By loading part of the CIM model as displayed on the left side of the screen, rules can be entered in the INPUT KNOWLEDGE WINDOW (Figure 17). As an example, the rule entered will update the status of all orders in the Order Processing System, for all the completed work orders in the Shop Floor Control System at 2:00pm. ...
Context 13
... implement these rules, we choose IMPLEMENT RULES TO LOCAL SYSTEM SHELLS from the Active Mode Facility Main Menu (Figure 15). This will extract the data management rules for each local application system and send them over a network to the local operating shells from which they will be automatically put into effect. ...
Context 14
... is important to note that the rules we refer to are responsible for linking systems together, as in our user defined rule for sending order status from Shop Floor to Order Processing System at a predetermined time. In Figure 18, we see that at 2:00pm, the information flow from Shop Floor to Order Processing contains needed information on order status. Furthermore, no centralized data manager is involved in this integration strategy, which leads us to be able to have many such interactions operating simultaneously. ...
