Sepasoft MES Module Suite
Resource Object | Personnel Objects
In the Sepasoft MES system, tracking personnel is optional. Personnel can be automatically selected based on the Ignition login or other support methods within Ignition.
There are two Object Types in the Personnel Objects Group, Person and PersonnelClass. Person and PersonnelClass objects have a corresponding ResponsePerson and ResponsePersonnelClass, which is an internal versioning schema created to maintain historical production data whenever changes are made to the properties or settings of the Person and PersonnelClass objects.
All of these objects inherit the AbstractMESObject properties and methods. The Person and ResponsePerson further extend the parent object with the properties and methods found further down in this section.
PersonnelClass and ResponsePersonnelClass Objects
Defining production tasks for each specific person, is very tedious. A better method would be to organize the people into categories, or class using ISA-95 terms. An example will make this clearer with fewer words. Consider unloading vinegar at a unloading pump station. If there are ten operators who are qualified to unload vinegar, then creating a Vinegar Unload Operator class containing the ten qualified operators, only will require one unload vinegar task definition. Adding an eleventh operator is as simple as adding that person to the Vinegar Unload Operator class.
This object inherits the AbstractMESObject properties and methods, but does not extend them.
Person and ResponsePerson Objects
An object used to define people and cannot have children. The MES Person objects are automatically generated from the Ignition users that have first and last names defined. This prevents the default "admin" user from being created in the MES system and showing up in selection lists. When the Sepasoft MES modules first start, the MES Person objects are synchronized and then will be synchronized on a hourly basis thereafter. They can also be synchronized on demand using a script function.
Object Versions
Every time a Person or PersonnelClass Object is modified, i.e. adding custom properties, changing a setting etc., the version number of that equipment object will be updated in the background. When an operation is scheduled, it will check for a corresponding Response Object version. If one does not exist, it will automatically create a new Response object.
This versioning is not part of ISA-95, however, without it, analysis of historical data would lose the original configuration of equipment, personnel and materials.
For all intents and purposes, MES Person objects will be created and configured in the MES Management screen and through scripting. Response Objects are automatically created by Operations and will be used for any kind of traceability analysis.
Although these are called Response Objects, they are in fact Version objects of the Person Objects. They are not Response Segment objects as defined by ISA-95 .
Object Creation
The Person object is created using Ignition's User Management component and the Personnel Class object is created using the MES Object Editor component. The scripting functions system.mes.synchronizeMESPersonnel() and system.mes.synchronizeMESPersonnelForRemoteGateways() are used to read users from the Ignition user source profile and synchronize with the MES Person objects.
Object Properties
This object has the following properties that affect how this object operates.
|
Name
|
Scripting
|
Description
|
|---|---|---|
|
Person User Name |
PersonUserName | The user name that the user logs in with. This must be unique across all gateways in the entire Enterprise, to avoid having duplicates continue to toggle the saved PersonFirstName and or PersonLastName value(s) back and forth as each one of the PersonUserName duplicates is synchronized hourly. |
| Person First Name | PersonFirstName | The users first name that is configured in the Ignition user profile. |
| Person Last Name | PersonLastName | The users last name that is configured in the Ignition user profile. |
| Name | Name | This is the name of the MES object. This name is used when referencing the object. This no longer needs to be a unique name, since PersonUserName must be unique across all gateways in the Enterprise. |
| Description | Description | An optional settings to give more details for a MES object. |
This object inherits the AbstractMESObject properties...
Object Functions
This object provides the following function:
getUUID()
This object inherits the AbstractMESObject functions.
Object Events
Objects have events associated with them that allow for custom scripts to be added whenever the event occurs. Refer to MES Object Events for more information.
This object inherits the AbstractMESObject events.
Sepasoft MES Module Suite