Browse Prior Art Database

Generic custom objects for MES modeling

IP.com Disclosure Number: IPCOM000171809D
Published in the IP.com Journal: Volume 8 Issue 7A (2008-07-10)
Included in the Prior Art Database: 2008-Jul-10
Document File: 3 page(s) / 54K

Publishing Venue

Siemens

Related People

Juergen Carstens: CONTACT

Abstract

Manufacturing Execution Systems (MES) require a modeling number of physical and logical entities. Typical entities modeled by MES application are for example plant machines, work orders, personnel resources and tools. These entities are represented in MES software in terms of software objects which are characterized by attributes and behaviors. Specifically MES industry projects require custom objects for modeling peculiar plant entities and behaviors. Despite the bulk of possible entities modeled in MES software they are shared among the various represented entities. Each object is usually defined by the following basic elements: • Object Class: defines which entity the object models (e.g. Order) • Attributes: describe the object configuration (e.g. Name="Order 1", Customer="Company 1", Quantity="1000 units") • Attribute Status: specifies if there are valid values for attributes (e.g. not defined, value out of range, valid) • Status of the Object (e.g. to be confirmed, completed)

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 3

Generic custom objects for MES modeling

Idea: Andrea Gozzi, IT-Genoa

Manufacturing Execution Systems (MES) require a modeling number of physical and logical entities.

Typical entities modeled by MES application are for example plant machines, work orders, personnel

resources and tools. These entities are represented in MES software in terms of software objects

which are characterized by attributes and behaviors. Specifically MES industry projects require custom

objects for modeling peculiar plant entities and behaviors. Despite the bulk of possible entities

modeled in MES software they are shared among the various represented entities. Each object is

usually defined by the following basic elements:

• Object Class: defines which entity the object models (e.g. Order)
• Attributes: describe the object configuration (e.g. Name="Order 1", Customer="Company 1",

Quantity="1000 units")
• Attribute Status: specifies if there are valid values for attributes (e.g. not defined, value out of

range, valid)
• Status of the Object (e.g. to be confirmed, completed)
• Behaviors (e.g. confirm, release)
• State Machine: describes the possibility of state transitions applied to the object and pre/post

conditions which must be applied in order to execute the transition (e.g. Release: Confirmed

In Progress [Requires: all attributes are valid])
• Version of the Object
• Authorization for manipulating Objects (only authorized users can apply the release transition)
• Auditing: for tracking modifications of the objects by recording an action player and date-time

     of actions
These features require high development efforts because the applied models change quickly, version

by version. Moreover, when custom objects are included in an application the user will be confronted

with unified and coherent management of system and custom objects and the outcome of this is a

challenging task. Available MES software applications provide a set of modeled entities. Whenever

versioning, controlling and auditing is required at entities models management, specific built-in

software solutions are applied. Usually the user is allowed to modify the set of attributes which

describe the entity. It is not possible to define or customize pre and post conditions, a specific status

transition must be verified for applying. Furthermore, no MES software application allows defining

completely new custom objects that can benefit of the system provided management mechanism. In

these cases the application condition requires custom software to be developed in order to fulfill the

customer requirements.

In the following, the novel method provides a general purpose framework for modeling standard and

custom entities by all means of objects that are natively supported by versioning, controlling and

auditing features...