MES “CHECK-ON” Software Informational System for the Management of Labour Resources

How MES works within the context of Company Informational System.

The MES (Manufacturing Execution System) allows the management of production events at the closest level of detail, which is to say at each individual phase of work.

Normally, the ERP (Enterprise Resource Planning), the global management system for company activities, upon execution of production in the factory, issues work orders which organizes data revolving around the actual product, the batch lot, the work cycle to use, the quantity to produce, and the planning dates corresponding to material planning.

In the case of just-in-time production flows, which are characterized by its daily pace or routine with reasonably brief flow times, it is sufficient to know the launched quantity and stored quantity in order to obtain significant indications both in terms of progress as well as performance.

Rather when dealing with productions characterized by many phases of work, which in general are performed across multiple work centres and/or departments, the global flow time may involve many work days. In this case, in addition to requiring ERP to know how much is being requested by the factory “on the whole” (which is to say by warehouse rather than the declaration of stored quantity by production performed), it becomes important to know “at what point we are”, since the ability to meet the quantity requirements and the date deadlines change notably from the first to the last operation in the cycle!

In this context, it is necessary to delve into the state of progress and the use of resources in further detail; a more appropriate manager is necessary to handle this known as a MES.

Check-on is therefore configured like the MES module integrated with the Si5 ERP, in particular the subsystem Sigip dedicated to the management of production.

System detail

In order to perform the above-mentioned operation, Check-on is structured in the following manner:

Basic data

This section defines the configuration of the clock-in interface, which is relative to the Si5 release in use and the organizational module which it is intended to adopt. In particular:

  • levels of authorization, such as user-program, user groups, etc…
  • system parameters, such as language, existence of a clock-in interface, the use of the badge, etc…
  • operational parameters, such as the labour type, the jobcard type, work in shifts.
  • static data, such as the labour and machine serial number archive, the reasons for work, the cost centres, the work orders.
  • Dictionary. The possibility to intervene on the transaction declarataions and reports both in order to translate into other languages as well as introduce new notes in the company language.
  • Language. Currently the following are available: Italian, English, Spanish, French, Polish
  • User Guide, Available in italian and in english.
  • Access through function key “?”, which allows direct access to the user manual in all management transactions.

Operational Procedures

These are procedures which must be performed by the operators in the field in order to provide basic information required by the system. Generally, they are activities which normally require paper and pencil, each writing his or her own consumed on the work documents. These procedures, which therefore can be seen as alternatives to those inserted manually, have been designed in such a way as to make the process as simple as possible, both in the number of steps to take as well as the use of a barcode or magnetic bar. The following are a part of the procedures:

  • Activity changes
  • Declaration of production
  • Declaration of formal production
  • Accumulative declaration
  • Change of machine activities
  • Package composition
  • Team composition
  • Attendence
  • Additional assignments

Operational observations

The basic concept is that the time dedicated is always determined by the interval of time in “activity changes” beginning a new activity and ending the previous: the time passed between the two activity start times corresponds to the time dedicated in order to perform the first of the two activities indicated.
In addition: the operativity of the personnel must be reduced to the essential.
Thus ensues:
Someone, always of labour (save for situations of direct interface with macvhines, etc.), must provide the system with information of activity changes.
In the case of the definition of a machine as a factor in the time dedicated, the machine resource must be expressed (automatically or interactively).
The job time will be determined by the presence which the resource effectively requires to perform the task in the interval mentioned above (the two timestamps).
The dedicated labour time, in the case of overlapping intervals relative to machine resources performed by the same worker, will result in the repartioning proportional to the number of machines managed for each individual interval.

Brief description of operational procedures:

Activity changes

The operator passes his or herown identification badge and reads the Jobcard that identifies the activity to perform.

Declaration of production

The operator passes his or her own identification badge and reads the Jobcard that identifies the activity performed. It may also declare the amount of good or discarded parts produced.

Declaration of formal production

The operator passes his or her own identification badge and reads the Jobcard that identifies the activity performed. It does not declare quantity. The system adopts the quantity as identical to that originally defined.

Accumulative declaration

The activities in the previous points are executed sequentially, with devices which change on the basis of the type of labour which is being handled.

Activity combinations (Package)

Reading the first Jobcard, defined as the top, and, iteratively the following, linked.
The declaration of production is performed for each individual Jobcard.
The formal declaration is also forseen through the top. In that case, the system asks if they are Jobcards relative to discards and then proceeds with the written global declaration of all the Jobcards, simplifying notably the operational efficiency.

Machine combinations (Stop & Go):

The same operator uses several machines contemporarily. Activity change with indication of work end or work continuation of the work in progress on another machine.

Team management

Registration of a serial number of a certain team, which corresponds to the serial number which performs the work.


clocking in / out, for internal applications on the basis of production direction, therefore without HR interface
Note: all transactions allow the possibility to insert notes.


The dynamic data originating from the operating procedures may be monitored through the appropriate handling transactions, described as follows:


The possibility to view / maintain activities, with a filter on those “in progress”. This allows one to know if a certain work has begun, at which time, on which labour/machine resource is involved.
It is also in this site where one can intervene in order to perform corrections for commision errors on the operating site at the moment in which excessive checks have been chosen to be avoided through setting properties of the department, hence avoiding loss of time due to indecision by the operator on what to do when he or she finds himself in the situation in which the system stops.

Declarations of production

Same as above, since the possibility to perform direct declarations or maintain those results from the procedures.


Access to jobs performed, with also the possibility of a direct input, similar to that used in the processing of presence.

Job Card

Heart of the system, the jobcards are the platforms for transmitting basic information, both in input as well as in consumed data collection. This locates the product, the work phase, the estimated cycle times, the quantities, and the dates. Normally, these are simply the job cards originating from the ERP, but the system allows, for “outside production lines” jobs, the insertion of jobcard specifics.
Through the jobcard, one can find all activities, both direct and indirect, the commission, and the production program. Also the numbering is very flexible and subject to parameterization.
A standard layout is assumed for the jobcard report, with alphanumeric barcode, in 128 standard.
The values consumed on the jobcard are replenished upon update of the job card of the work order, allowing a precise and updated progress check and an accurate calculation of the workload in Sigip.

Id Card

The possibility to admit material identification cards, both in the site of declaration of production as well as in the site through which the transaction is performed.


Management of clocking in / out, obtained from the specific interface or through the alternative procedure contemplated in CK.


Master file of specializations achieved by operators, through professional training courses. Each certification can then be associated to the operator serial number with a valid until date. This allows the professional classification of the workforce, useful both for internal management as well as for external audits.


Management of the jobcard combinations, as an alternative or in maintaining those products through the specific procedure.


and grouping of comissions. Master file management of commissions and of information / states.


Management of team composition, as an alternative or in maintaining those originated through the specific procedure.


Presence on jobs: for applications in the area of R&D, Technical U., and in general, services, in order to match jobs-comissions on the basis of its presence.

Processes and computations

  • TI computation. Calculation of the time dedicated starting from the badging timestamps in the department, for each Jobcard/operator code, on the basis of presence.
  • Automatic presence generation. Useful for replacing the actual presence in the case of lack of presence interface or lack of management of “machine presence”.
  • Internal orders generation.
  • Through the generation of the jobcard insertions for item code of the product drawing automatically from the jobcards of type CI (cycle).
    Note: the feature available in the absence of integration with the ERP, and for the management of “off the production lines”.
  • Jobcard consumption. Update of the produced quantities and job times on the jobcards closed in the period.
  • Disassociation package. Repartioning of the job time on the top jobcard on all jobcards which belong to the package.
  • Job time analysis and work cycle generation: allows the generation or update of work cycles on the basis of the analysis history of the dedicated consumed time in a given period, by product / phase / machine.
  • Appointed losses. Procedure used in the case of reduced workforce./li>
  • ERP interface. Whenever the ERP system is not Si5. In particular, interfaces are allowed, interactive or batch, which concerns work orders, cycle operations, job cards.
  • Presence interface: to perform every now and again on the basis of the software used in the company. The standard CK expects an interface with Timecard.


The main output are presented below in report format.
In particular, progress monitoring reports are proposed as well as performance evaluation.
The report of work documents for Jobcard and Idcard are part of this section.

Summary description of the reports:

Declaration of production

for the date and operator code, the jobcard, machine used, quantity of good or discarded parts, hours for good product, and hours for discarded product are shown.

Production progress

  • (jobcard registered between dates) with organizational data by comission / work order / phase, it is possible to have estimated and produced quantities, assigned and developed times, and job times.
  • (closed jobcards closed between dates) with organizational data by comission / work order / phase, it is possible to have estimated and produced quantities, job times, relation between assigned themes both produced and estimated, relation between produced appointed times and job times.

Daily production

ideal report for measuring the daily production performed rather than the hourly production possible, by work shift.

Production assignment

the production, selected by work order, is assigned on the basis of the cost indices relative to the involved cost centres.

Job times analysis

Report aimed at evaluating the time utilized to make productions not covered by the work cycles, for which it is appropriate to have some initial consumptions of.


With various input possibilities, such as period, commission or commission group, reason of work, it is possible to have a detailed report by labour serial number.

Jobs by matrix

Jobs, for reason or cost centre / production line, are expressed in such a way as to be read easily. In addition, in the case of jobs relative to indirect performance, which for example maintenance, it is possible to obtain the relation between job times and debit cost centre for which it has been performed.

Hours lost/gained

Between dates, on the x-axis the production unit which receives hours, and ordered by hours lost.

Monthly report

  • rolling: every 12 months they are checked, with interval available for display. Generally at the end of every month, with shift on the first month and inclusion of the last, a work analysis report is obtained with summary by plant / department / production line / production unit, and beginning from the first presence, corrected with hours lost and gained, purified of the lost hours, evaluated on the basis of the relation between TA (assigned time) and TI (job time) on the closed jobcards, it allows the computation of efficiency and output.
  • periodically: the contents are similar to the rolling report, but with detail for plant / department / production line / production unit.
  • OEE Index (Overall Equipment Effectiveness)

Global metric of measurement of performance grouping three fundamental elements:

  • Availability
  • Efficiency
  • Quality

Note: all reports may be generated in pdf format, and exported in excel (the reports where the layouts are particularly developed, then necessitating the adjustment of the excel worksheet of the destination file).


Server hardware prerequisites

  • Processor Intel Pentium IV or better
  • Memory RAM 2 GB or better
  • Disk space 100 GB or better

Server software prerequisites

  • Operating System MS Windows 2003 R2 SP2, MS Windows XP PRO SP3, or better
  • MS .NET Framework 2.0 with relative updates
  • MS .NET Framework 3.5 with relative updates
  • MS Internet Information Server 6.0 or better

Client hardware prerequisites

  • Processor Intel Pentium IV or better
  • Memory RAM 2 GB or better
  • Disk space 100 GB or better

Client software prerequisites

  • Operating System MS Windows XP PRO SP3 or better
  • MS .NET Framework 2.0 with relative updates
  • MS .NET Framework 3.5 with relative updates

In the case of server on the network with iSeries (AS400), it is also necessary to install Client Access R.5.2 or better.