Skip to end of metadata
Go to start of metadata

The contents of this page are extensive since the migration process is detailed and requires deep knowledge of the products. Please read through each section, understanding the implications prior to performing a migration. Please contact Sepasoft support at 800 207 5506 with any questions or concerns regarding this process. PERFORM THIS MIGRATION ON A DEVELOPMENT SYSTEM FIRST, as described below.

SPC and Recipe Data Migration

Currently, if you are migrating Recipe data as part of an OEE 1.0 to OEE 2.0 upgrade please contact us at 800 207 5506 for important information.
Instructions have been added for manually copying over SPC tables and modifying them to work in the migration steps below.

Background

 Product Background and Update Reasoning

In 2011 Sepasoft developed the OEE/Downtime Tracking module for the Ignition platform, extending the capabilities of this predominantly SCADA solution into the MES domain. Over the years since its introduction, our certified systems integrators, clients and our own team at Sepasoft learnt a great deal about how a company’s manufacturing base wants to use OEE to drive continuous improvement initiatives. With that in mind, the OEE module has evolved continuously to handle ever more complex production lines, analytical requirements and large scale enterprise architectures.

In 2014, our Track & Trace module was released following on the heels of the SPC, Instrument Interface and Recipe Management modules. Track & Trace heralded a new and significant chapter for us with the decision to base it on the ISA-95 standard and object model. This new framework provides a powerful and flexible platform that can be used to create custom MES solutions to manage every aspect of manufacturing operations and the required equipment, personnel and material resources.

With the growing popularity of the OEE module, the new requirements being sought and ever increasing OEE + Track & Trace implementations, the decision was made to completely revamp the OEE module to use the same ISA-95 object model as Track & Trace, providing a seamless integration between lot tracking, production control, scheduling, resource management and OEE analytics. Because of this, it was no longer possible to maintain backwards compatibility with OEE 1.0 as the differences were too great. This document intends to lay out the difference between OEE 1.0 and OEE 2.0 and to provide a path for migrating from OEE 1.0 to 2.0.

You will see references to MES 1.0 and MES 2.0 throughout the documentation. Changes were made to the underlying MES platform on which all modules run as part of the OEE 2.0 module development. Minor changes were made to existing Track & Trace, SPC and Recipe Management modules to account for the MES 2.0 platform changes and those modules will have a 2.x.x version. Instrument Interface, Web Services, Barcode scanner and the production simulator are not affected by the MES platform changes and 1.x.x versions can be used.

 Click here to see the new features of OEE 2.0...

Built on ISA-95

The OEE 2.0 module is built in compliance with the ISA-95 standard that provides a consistent terminology for supplier and manufacturer communications, information and operations models for clarifying application functionality and how information is to be used. It uses the same object model as the Track & Trace module to provide seamless integration between your lot tracking, production control and downtime tracking solution.

Refer to ISA-95 Overview for more information.




Enhanced Production Scheduling

Scheduler is now based on the same components as the Track and Trace module providing Work Order Drag and Drop capability, Auto-Delay feature, custom categories (hold schedule) and routes.

Refer to Production Scheduling & Dispatch for more information.



Shift Management

OEE 2.0 now provides support for using the Ignition Schedule Management component for creating complex and composite shift rotations. However if you need something different, you can simply provides us the shift information via a tag and we'll associate that piece of information along with the production data we capture.

Refer to Shift Configuration for more information.



Equipment Modes

OEE 2.0 module now provides support for creating Equipment Modes. You can now track production utilization, at any level of the Production Model up through Enterprise, by IDLE TIME, CHANGEOVER, PRODUCTION, MAINTENANCE, TRAINING, TESTING, even custom modes, and decide if they are to be considered in the OEE calculation.

Refer to Equipment Modes for more information.



Equipment States

Equipment States can now be grouped, allowing multiple states such as Loading, Heating, Molding all to be considered as Running by OEE. True equipment state is now captured and stored allowing for greater cycle time and TaKt time analysis. 

Machine State can now be configured to be Operator Selectable - REQUIRED when you require an operator to select the actual cause or add a note for a certain event. Downtime table component will flag the events that need to be over-ridden. User roles can also be configured on who can select operator selectable reasons.

 Refer to Equipment States for more information.




Downtime Detection Modes

Key Reason Detection now supports primary cells anywhere within a line. Select a process cell in your line that you consider the bottleneck or primary cell and set that to Key Cell. As long as your primary cell is running, OEE will consider the production line to be running, but if your primary cell goes down, OEE will determine which piece of equipment is blocking or starving your primary cell and record that as the cause of the line down.

Refer to Downtime Detection Mode for more information.



Data Capture and Runtime Monitoring

Equipment Mode, State, counts, shift and standard rate tags are always monitored and recorded. Never miss another production run because a run wasn’t scheduled. You can now create multiple ‘live’ OEE values for user defined time periods. How often these values are updated is now user configurable and uses an optimized cache to provide real-time values that can be displayed for run-time monitoring. Users will now be able to see real-time OEE metrics and production counts updated as often as they want.

Refer to Live Analysis for more information.




Work-Center and Sub-Line OEE Operation

Not all manufacturing processes fit perfectly into providing a Single Line OEE Metric, such as complex work-center type operations or production lines with multiple sub-lines feeding in or out to a main line. OEE 2.0 adds support to define sub-lines with their own downtime detection method, equipment modes and states. Sub-lines can inherit their schedule from the main line, but can also run independently.

Refer to Modelling the Production Line for more information.

Running Changeovers

OEE 2.0 now supports running changeovers in that multiple products can be processed on a production line at the same time.



Designer Enhancements

The following changes to the designer have been made:

  • The production model is now saved as individual project resources:
    • Allows multiple developers to modify production items at the same time
    • Results in much faster save times
    • Collects OEE data uninterrupted even while saving 
  • Production items can be moved between gateways without losing their identity
  • Equipment states and modes are now configured in the client
  • Production OPC Server is now replaced by the MES tag provider providing user configurable real-time analytics



Share OEE Analysis with the New Analysis Engine

New analysis engine is simplified and optimized to provide faster, more powerful analytics aggregating data from all MES sources as well as any custom value sources. OEE analysis now occurs on-the-fly and can be shared with other systems and web reporting tools using built-in system functions. Criteria can be changed to reflect the OEE based on your selection. Stored analysis now supports user security and ability to promote reports to the public domain.

The Impromptu Analysis components have been revamped to provide user security by stored analysis as well as the ability to promote user analysis reports to the Public Domain.

Built-in system functions will provide a scripting method for running a stored ad-hoc analysis and pushing that data out to a user configured database table. This can be done from a gateway timer, tag change event, etc. or through a web service call to allow the sharing of OEE analysis with other systems and Company Web Reporting tools.


Refer to Analysis and Reporting for more information.



Licensing and Migration

OEE 2.0 provides greatly enhanced production modelling and analytical capabilities that make a strong case when considering replacing an existing OEE 1.0 implementation. There is no additional license cost for using OEE 2.0 as long as you have a license for OEE 1.0 and upgrade protection is active on your license. We provide migration tools to help with porting over an existing OEE 1.0 implementation and bringing over historical production data. There are however significant changes that will need to be made to replace any screens that use legacy OEE 1.0 components and scripting functions which are outlined in the sections below.

Prior to beginning the migration process, please check that your license is correctly configured. It should reference "sites" and "machines", and not "nodes" and "limitednodes." Please expand the panel below for an example of a fully configured MES license with OEE, Recipe, SPC, Trace and Production on the license. If the MES modules on your License page in your Gateway Configuration do not look like this, please contact your Inductive representative and they will update your license if necessary.

 License Configuration Example

Need Help?

You won't be alone if you decide to migrate an existing application. Our tech support and design consulting group can help you review the steps necessary. We also offer a discounted design consulting rate if you want us to be more involved in the migration. Contact us at support@sepasoft.com or (800) 207-5506 for more details.



Understanding the Differences Between OEE 1.0 and OEE 2.0

The following table highlights the main differences between the two modules to provide an idea of what may need changing and how to do it.

 Click here to see the major difference between OEE 1.0 and OEE 2.0
FeatureOEE 1.0OEE 2.0
Shift ManagementConfigured in the Production model.Uses the Ignition Schedule Management component or tag path collector to manage and determine current shift.
Downtime reasonsConfigured in the Production Model.Configured in the OEE Equipment Manager component.
Real-time statusOPC Production Tags provided.OPC Production Tags replaced with MES Tag Provider and Live Analysis.
Data CaptureEquipment status, production counts and additional factors only stored during an active run.Equipment mode, status, production counts and additional factors only stored recorded continuously whether a run is active or not.
OEE AnalysisOEE Metrics calculated during run and stored in analysis tables.OEE Metrics are calculated on demand and not stored in database tables, only raw values are stored for status and counts.
Downtime DetectionKey Reason only valid when primary cell is at head or tail of a production line.

Key Reason detection available for a primary cell anywhere in the production line. The original Key Reason downtime detection method is not longer supported. Key Reason Cell Priority will be used in its place.

Remote Operator Reason Code SQL Tag is no longer used.

Cell GroupsCell groups can only consist of Parallel Cells.Cell Groups can be used to create sub-lines, use parallel cells, initial reason or key reason. Cell groups can be nested.
Production CountersInfeed, outfeed and waste counters configured at the line and cell level.MES counters used for all production counts.
Data storageRuntime data stored in tables in the runtime database and automatically purged. Final production data stored in analysis tables in the analysis database and is persistent.Runtime database no longer used. All production data is persistent and stored in the Analysis database.
Product CodesProduct codes created using ProductCode, ProductCodeLine and ProductCodeProperty table components.Product codes replaced with same Material Definition and Material Class objects as used by Track & Trace and created using the OEE Material Manager component.
OEE Production SettingsOEE production settings such as Schedule rate, Standard rate, package count, etc. configured in the outfeed counters and in the ProductCodeLineProperty table component.OEE production settings such as Schedule rate, Standard rate, package count, etc. configured in the OEE Material Manager component and can be overridden by passing values through the tag collectors.
SchedulingOEE Production runs scheduled using OEE Schedule View component.OEE Production runs scheduled using the same MES Schedule View component as used by Track & Trace.
Work Order ManagementWork Orders managed using the Work Order Table component.Work Orders managed using the same MES Work Order Table component as used by Track & Trace.
Production RunsRunUUIDs created for each production run.Production runs use operations segments and have their own OperationUUID. Operations segments are automatically created by the OEE Material Manager whenever a product code is associated to a production line. Operations segments can be modified through scripting and with the MES Object Editor component.
AnalysisAnalysis Selector and analysis controller components as well as scripting functions used to access OEE data.MES Analysis Selector and MES Analysis Controller components replace the legacy components. Security now available to prevent unauthorized changes to Stored Analysis settings. SQL like filters can be used to return specific production data.
ReportingAnalysis controller and scripting functions used to provide dataset to reports.New Analysis datasource available to report designer to access stored analysis settings.
Editing Production datasystem.production.adjustRunData() scripting function available to adjust production counts. No method provided to adjust OEE availability data other than downtime reason code. No good way to add production run data after the fact if production run was not active.MES Value Editor and scripting functions provided to add, edit and delete all production data.
Additional FactorsAdditional Factors are defined only at the Line production item level.Additional Factors can be defined at the Line and Cell production item level.


Equivalent Scripting Functions

As OEE 2.0 now uses the same object model as Track & Trace, any scripting using the system.oee, system.production, system.production.utils and system.schedule libraries will need to be replaced. OEE 2.0 uses the system.mes, system.mes.analysis and system.mes.workorder libraries and MES Objects functions. The following is a listing of removed MES 1.0 scripting functions and their equivalent in MES 2.0.

 

 Click here to see the MES 2.0 script functions that are equivalent to MES 1.0 script functions
MES 1.0 Scripting Functions for OEEEquivalent MES 2.0 Scripting functions for OEE 2.0

system.production.addProductCode / system.production.utils.addProductCode

 system.mes.createMESObject

system.production.addRunComment / system.production.utils.addRunComment

 Note Tag Path collector on OEE Downtime 2.0 tab now used to capture notes.

system.production.adjustRunData / system.production.utils.adjustRunData

system.production.adjustRunDataByShift / system.production.utils.adjustRunDataByShift

system.mes.getTagCollectorValue /  system.mes.updateTagCollectorValue / system.mes.removeTagCollectorValue

system.production.cancelRun / system.production.utils.cancelRun

 system.mes.oee.abortRun
system.production.clearAnalysisCache / system.production.utils.clearAnalysisCache system.mes.analysis.invalidateAnalysisCache
system.production.createAnalysisSettings / system.production.utils.createAnalysisSettings system.mes.analysis.createMESAnalysisSettings
system.production.displaySecondsInRunName n/a
system.production.endRun / system.production.utils.endRun system.mes.oee.endOEEChangeover / system.mes.oee.endOEEProduction
system.production.extractProductionItem / system.production.utils.extractProductionItem n/a
system.production.getAnalysisResults system.mes.analysis.executeAnalysis
system.production.getCellHierarchy / system.production.utils.getCellHierarchy n/a
system.production.getCellID / system.production.utils.getCellID n/a
system.production.getLineID / system.production.utils.getLineID n/a
system.production.getLinePath n/a
system.production.getLineProductCodeProperty / system.production.utils.getLineProductCodeProperty system.mes.oee.getMaterialOperationsSegments
system.production.utils.getProductCodeLineInfo system.mes.oee.getMaterialOperationsSegments
system.production.utils.getProductCodeLinePropertiesInfo system.mes.oee.getMaterialOperationsSegments
system.production.getRunContextValue n/a
system.production.isProductionModelRunning / system.production.utils.isProductionModelRunning n/a
system.production.resetRunData / system.production.utils.resetRunData n/a
system.production.resumeRun / system.production.utils.resumeRun n/a
system.production.setFirstDayOfWeek n/a Handled by Ignition Schedule Management component
system.production.setLineProductCode / system.production.utils.setLineProductCoden/a
system.production.setRunContextValue n/a
system.production.startRun / system.production.utils.startRun system.mes.oee.beginOEERun
system.production.startLineProductCode / system.production.utils.startLineProductCode system.mes.oee.beginOEERun
system.production.updateLineProductCodeProperty / system.production.utils.updateLineProductCodeProperty system.mes.oee.updateMaterialOperationSegments
system.production.updateProductCodeLineStatus / system.production.utils.updateProductCodeLineStatus system.mes.oee.updateMaterialOperationSegments
 system.schedule.addScheduleEntry system.mes.createSchedule / system.mes.scheduleOperations
system.schedule.addWorkOrderEntry

system.mes.workorder.createMESWorkOrder / system.mes.workorder.saveMESWorkOrder

system.schedule.deleteScheduleEntrysystem.mes.deleteSchedule
system.schedule.deleteWorkOrderEntrysystem.mes.workorder.deleteMESWorkOrder
system.schedule.editScheduleEntrysystem.mes.getScheduleOperations / system.mes.saveSchedule
system.schedule.estimateRunCompletionn/a
system.schedule.getScheduleDataByIDn/a
system.schedule.getSchedulingRateByProductCodesystem.mes.oee.getMaterialOperationsSegments
system.schedule.getWorkOrderIDsystem.mes.workorder.getMESWorkOrder
system.schedule.getWorkOrderInfosystem.mes.workorder.getMESWorkOrder
system.schedule.getWorkOrderListsystem.mes.workorder.getMESWorkOrders
system.schedule.resetScheduleCachen/a
system.schedule.setWorkOrderClosedMES Work Order object functions
system.schedule.updateWorkOrderEntryMES Work Order object functions
system.oee.addCustomScriptn/a
system.oee.removeCustomScriptn/a
system.oee.setOEEFactorCap?


Equivalent Components

  • Schedule component palette has been removed as OEE scheduling now uses the same components in the Production palette as Track & Trace.
  • OEE Downtime component palette has been replaced with the OEE Downtime 2.0 component palette.
  • Production component palette now includes scheduling components, new MES 2.0 components and product code components have been removed.

 Click here to see MES 2.0 components equivalent to MES 1.0 components
MES 1.0 OEE ComponentsMES 2.0 Equivalents
PaletteComponents removedPaletteComponents added
OEE DowntimeDown Time TableOEE Downtime 2.0OEE Downtime Table
OEE DowntimeLine Run SelectorOEE Downtime 2.0OEE Run Director
OEE DowntimePerformance Indicator
n/a
OEE DowntimeAnalysis Time ChartOEE Downtime 2.0OEE Time Chart
ScheduleLine Schedule SelectorProductionMES Schedule Selector
ScheduleLine Schedule ViewProductionMES Schedule View
ScheduleSchedule ControllerProductionMES Schedule View
ScheduleSchedule Date SelectorProductionMES Schedule View
ScheduleSchedule Day View
n/a
ScheduleSchedule Entry ControllerProductionMES Schedule View
ScheduleSchedule Month View
n/a
ScheduleSchedule Week View
n/a
ScheduleTime Selector
n/a
ScheduleWork Order ControllerProductionMES Work Order Table
ScheduleWork Order SelectorProductionMES Work Order Table
ScheduleWork Order TableProductionMES Work Order Table
ProductionProduct Code Controller
n/a
ProductionProduct Code Line TableOEE Downtime 2.0OEE Material Manager
ProductionProduct Code Properties TableOEE Downtime 2.0OEE Material Manager
ProductionProduct Code SelectorOEE Downtime 2.0OEE Run Director
ProductionProduct Code TableOEE Downtime 2.0OEE Material Manager
ProductionProduction Comments Panel
Note Tag Path collector on OEE Downtime 2.0 tab now used to capture notes
ProductionProduction Line SelectorProductionMES Object Selector
ProductionAnalysis ControllerProductionMES Analysis Controller. Note Analysis Controller has been moved to the Legacy Production palette as it is still used by Recipe.
ProductionProduction Pie ChartProductionProduction Pie Chart
ProductionProduction Bar ChartProductionProduction Bar Chart
ProductionProduction Analysis SelectorProductionMES Analysis Selector. Note Production Analysis Selector has been moved to the Legacy Production palette as it is still used by Recipe.
ProductionProduction Stored Analysis SelectorProductionMES Analysis Selector. Note Production Stored Analysis Selector has been moved to the Legacy Production palette as it is still used by Recipe.
ProductionAnalysis TableProductionAnalysis Table


Direct Database Queries

OEE 2.0 uses the same database schema as Track & Trace for configuration information and production data. Any direct SQL database queries to the OEE 1.0 Analysis or Runtime database tables must be replaced. All OEE 2.0 data can be accessed through Scripting Functions and MES Objects. There should be no reason to use direct SQL queries to the MES tables. Avoid doing so as much as possible to ensure future forward compatibility.




OPC Production Tags

OPC Production Tags for real-time OEE data have been replaced with the MES Tag Provider configured through Live Analysis settings. All OPC tags in the tag browser need to be removed and screens that bind to them will need to be modified. See Live Analysis Tags for more information.




How Configuration Data is Upgraded

 Data configuration details

Data is upgraded in three different areas:

  1. Production model settings are upgraded when the Platform 2.0 production model detects a production model is saved in serialization version 1. In MES 1.0, the entire production model is saved as one resource in the Ignition global project. In MES 2.0, each production item in stored as a separate resource in the Ignition global project. The OEE 1.0 settings that are transitioned over to the OEE 2.0, are first exported to temporary files. After the production model is converted, the OEE 2.0 values are added or updated based on the OEE 1.0 values saved in the temporary files. 
  2. In OEE 1.0 downtime reason settings are saved in the production model. In OEE 2.0 downtime reasons are replaced by Equipment States are saved in the MES database. When the production model is upgraded, the downtime reason settings are saved to the Downtime_Reasons.cnf file located in the Ignition data/MES_Upgrade folder. The user can then import the downtime reason settings using the MES Legacy Import page on the gateway. This will read from the temporary file and create the appropriate Equipment State Class and Equipment State MES objects. 
  3. Historical data from past OEE runs can be imported using the MES Legacy Import functions under MES Settings on the gateway.

The following configuration information will be automatically updated...

  • State Tag Path for lines and cells will be copied from the existing State SQLTag to the appropriate State Tag Path collector.
  • Downtime Detection Method will be created for the line only. 
    • Lines set to 'Key Reason' will be set to 'Key Reason Cell Priority'. All other detection methods will be translated directly. 
      (warning) 'Key Reason' had some unusual behavior in OEE 1.0 and was deprecated being replaced by 'Key Reason Cell Priority' and 'Key reason Neighbor Priority'. If your current application uses the 'Key Reason' detection method, validation of the new detection method on the line should be validated as part of the migration process.
    • All Cell Groups will default to 'Parallel Cells'.
  • Infeed, Outfeed and Reject Counters will be transferred over to MES Counters.
    • All Waste Counters will become Reject kind MES Counters.
    • Infeed Counters will become General kind Counters except for the one selected for Primary Infeed.
    • Outfeed Counters will become General kind Counters except for the one selected for Primary Outfeed.
      (warning)Units are no longer set in the counters and must be set using the OEE Material Manager.

    • All counters transitioned over will be set to Roll Over mode.
  • Downtime events are replaced with Equipment States. Because OEE 1.0 downtime reasons are duplicated for each line and OEE 2.0 Equipment states are consolidated into Equipment State Classes that can be assigned to multiple equipment items, during conversion identical downtime reason lists will be consolidated. The names will be in the Equipment State Class-x format. They can be renamed once converted. The Downtime Reason Description is not taken into consideration when checking for equality during consolidation. State mapping is as follows:
    • If Record Downtime = False and Planned Downtime = False, then Type = Blocked
    • If Record Downtime = True and Planned Downtime = False, then Type = Unplanned Donwtime
    • If Record Downtime = False and Planned Downtime = True, then Type = Planned Downtime
    • Record Downtime = True and Planned Downtime = True is invalid and not allowed in Platform 1.0


Modify Application to use new OEE Module Functions

 Design Considerations


Import Configuration Information and Checklist

Now that you understand the differences between OEE 1.0 and OEE 2.0 and have prepared your tags and screens for the data migration, you are ready to import your legacy configuration information.

The upgrade process from OEE 1.0 to OEE 2.0 involves many steps that must be successfully completed. See Migrating from OEE 1.0 to OEE 2.0 for details on the upgrade process. Incomplete steps or errors encountered during upgrade may cause undesirable results. It is STRONGLY RECOMMENDED to backup the Ignition Gateway and relevant databases (configured under MES Settings on the Ignition Gateway) prior to importing.

Using the Legacy Import Tools to Import MES 1.0 Data

The Legacy Import Tool helps to import Reason Codes, Product Codes and OEE Run History in three distinct steps. The following checklist is provided to ensure a successful OEE 1.0 to OEE 2.0 migration.

Migration Checklist
  • Understand the differences and document screens, scripts, tags and db queries that will need to be modified.
  • Assure that your license is correctly configured. It should reference "sites" and "machines", and not "nodes" and "limitednodes." Please expand the panel below for an example of a fully configured MES license with OEE, Recipe, SPC, Trace and Production on the license. If the MES modules on your License page in your Gateway Configuration do not look like this, please contact your Inductive representative and they will update your license if necessary.
 License Configuration Example

  • Create database backup of the production database(s). These will be databases created for analysis and runtime sources. Note that creating a database backup can cause the production gateway server to lose connection to the production database server. You should plan on creating the backup when not in production.
  • Create gateway backup of the Production Gateway.
  • Create a new Development Gateway Server with same version of Ignition and Sepasoft modules as on the production server.

If using a VM clone, you must de-activate the license of the new VM to prevent a licensing error on the production server.

On the new Development Gateway Server:

  • Restore Database Backup(s) to a development Database Server.
  • Restore Gateway Backup to a development Gateway Server.
  • Confirm database connections are valid.
  • Create new Databases/Schemas for use with the MES 2.0 modules.
    • As in OEE 1.0, you still retain the ability to have separate database connections for Analysis, Runtime, and Auxiliary.
  • Configure and connect new Database Connection(s).
  • Ensure Ignition revision is 7.9.4 or higher. If necessary, upgrade Ignition and the installed sepasoft modules to the latest 1.0 version.
  • Remove all OEE 1.0 components from windows.
  • Turn off Production Model by setting Production Model Enabled to false in the designer.
  • Save and publish your changes.
  • Close the Ignition Designer.
  • Uninstall the following MES 1.0 modules in the below order:
    1. All installer modules
    2. OEE
    3. Recipe
    4. SPC
    5. Trace
    6. Schedule
    7. Production
  • Install MES 2.0 modules in the below order:
    • OEE_Downtime_V2 module
    • Recipe, SPC and/or Trace modules
    • The Production module.
  • Configure Analysis, Runtime, and Auxiliary datasources in the MES Settings menu, pointing to the newly created databases for the MES 2.0 data.
  • Open the Ignition Designer and enable the Production Model by setting Production Model Enabled to True.
  • Save and publish your changes.
  • Restart the Production Module
 Click here if you are also migrating an SPC application
  • Copy over the data from the following runtime database tables to the new database created for 2.0:
    • SampleDef
    • SampleDefAttr
    • SampleDefLimit
    • SampleDefLoc
    • SampleDefSignal

As an example, in SQL Server, you can achieve this for the SampleDef table by deleting the SampleDef table in the new mes 2.0 database and then running the following SQL statement:

SELECT * INTO mes.[dbo].[SampleDef ] FROM [Runtime].[dbo].[SampleDef ]

  • Copy over the data from the following analysis database tables to the new database created for 2.0:
    • QUAL_Def
    • QUAL_DefAttr
    • QUAL_DefLimit
    • QUAL_DefSignal
    • QUAL_Sample
    • QUAL_SampleData
    • QUAL_SampleNote
    • QUAL_Stored_SPC
  • The SPC locations will likely have a different LocationID in the new database table. You will need to modify the SampleDefLoc table entries to change the LocationID accordingly. Compare the entries in the Location table between the old runtime database and the new mes database.
  • In the Gateway Configuration Page, under MES Modules, select Legacy Import.
  • Follow the onscreen instructions to import Reason Codes. (This step may take some time!)
  • Follow the onscreen instructions to import Product Codes. (This step may take some time!)
  • Follow the onscreen instructions to import the OEE Run History.

    Imports Take Time

    Importing OEE Run History can take several minutes, even hours. It is suggested that an initial import of a short time period (i.e. 1-3 days) be performed first to learn how long historical data import requires. You may perform multiple imports expanding the date as appropriate to the project.


  • Re-create your screens using the new OEE 2.0 components and scripting functions.





Import Considerations

  • The time it takes to import historical production run data depends on the amount of production runs, additional factors, downtime events, etc.
  • To import historical production run data, Running must be assigned the code of 1. This is how it was in OEE 1.0 by default.
  • During import of downtime reasons, product codes or historical production runs, the database tables may be locked preventing live MES functionality from occurring. 
  • Import of downtime reasons, product codes, or historical production runs is an "all or nothing" operation. If there is an error, all data associated with the current import will be rolled back.


Historical Production Data Mapping

Details of OEE 1.0 data formatting after legacy import.

 Production Data Map

The production data in the following tables is converted as shown in the table below.

OEE 1.0 TablesConversion Process
Run Summary
  • RunUUID will be converted to OperationsUUID for line and children
  • ActualStart is the timestamp for the mode being set to Changeover to line and children
  • ActualRunStart is the timestamp for the mode being set to Production to line and children
  • ActualFinish is the timestamp for the mode being set to Idle to line and children
  • (ScheduledFinish - ScheduleStart) -> Schedule Duration to line
  • (ScheduledRunStart - ScheduleStart) -> Target Changeover Time to line
  • Package Count -> Package Count to line and children are set to 1
  • Product Code -> Product Code to line and children. All set to blank at the end of the run.
  • Production Units -> Outfeed Units to line and children
  • Schedule Rate -> Schedule Rate to line
  • OEE Rate -> Standard Rate to line
  • Work Order -> Work Order to line and children. All will be set to blank at the end of the run.
Line Summary
  • Shift -> Shift to line
  • Infeed Count -> Material In MES counter
  • Line Infeed Counter Equipment UUID is set to the line UUID
  • Infeed Count Scale is set to 1
  • Production Count -> Material Out MES counter
  • Line Outfeed Counter Equipment UUID is set to the line UUID
  • Waste Count -> Material Reject MES counter. PROD_Line_Summary table only has a single Waste Count column and its values are transferred to a newly created Material Reject counter
  • Reject Count Scale is set to 1
Cell Summary
  • Infeed Count -> Material In MES counter
  • Production Count -> Material Out MES counter
  • Waste Count -> Material Reject MES counter. The PROD_Cell_Summary table only has a single WasteCount column and its values are transferred to a newly created Material Reject counter.
Downtime Detail
  • Downtime Reason Code -> Equipment State for line and children. If the Downtime Reason Code has been overridden, then the following will also be done:
    • If the original reason code was for the line, then the equipment state for the line will be updated.
    • If the original reason code was for a cell of the line, then a new entry will be added for the line. This replicates how overriding works in OEE 2.0.
Comment Summary
  • Comment -> Note.
  • In OEE 1.0 comments were only supported at the line level.
Additional Factors
  • Addition Factor -> Additional Factor

The configuration for additional factors in the Production Model is the same between OEE 1.0 and OEE 2.0. However, the history of additional factory values has changed from the horizontal table format to the vertical table format.



  • No labels