PackOS Deployment Process - Checklist

Task

Description

Status
& add info

Client

Ilabo

Objective

Files
&
information

KB article
link

C - consulted
(provides information)

R - responsible
(performs actions)

R - responsible
(performs actions)

I - informed
(informed by the client)

Stage 1

Pre-implementation tasks

1

Determining the number of lines (or sets of machines constituting a production unit for one production/process order), the number of machines in a line, the way of working with data collection

R

I

Determining the number of required licenses and license costs

 

 

  1. Data/signals collected automatically

 

 

 

2. Data entered into PackOS manually (order progress, downtimes, process parameters)

 

 

 

2

Expected scope of implementation:

R

I

 

 

  1. Performance, downtime and OEE live monitoring [yes/no]

 

 

 

2. Process parameters monitoring (pressure, temperature, etc.) [yes/no

 

 

 

3. Energy monitoring:

 

 

Energy monitoring

a. consumed [yes/no]

 

 

 

b. temporary consumption for anomaly detection [yes/no]

 

 

 

4. Downtimes video monitoring [yes/no]

 

 

 

5. Predictive functions (estimation of the condition of machine elements, failure prediction, anomaly detection) [yes/no]

 

 

 

6. People performance management [yes/no]

 

 

 

3

Determining the method of supplying the system with source data for automatic supply:

R

I

Valuation of the costs of connecting machines

 

 

  1. Whether the drivers provide data in the OPC format and are available over a specific IP [yes/no/not applicable] (we require the client to adjust the drivers to the OPC standard)

 

 

 

2. Is there an OPC Server in the organization collecting signals from machines [yes/no]

 

 

 

3. Is there an industrial computer/pc on which OPCServer and/or LogiXGate can be installed [yes/no/not applicable]

 

 

 

4. Expected delivery of an external controller by ILABO to which the CLIENT will connect sensors (eg. photocells) (LogiX DataCollectorBox)

 

 

 

a. version for mounting in an existing cabinet - on a DIN rail

 

 

 

b. full cabinet with power supply and fuses

 

 

 

*in special cases, we can adapt to the existing method of issuing data by drivers other than the OPC standard

 

 

 

4

Determining the method of entering orders and the SKU (Material Master) file - see points 8 and 9

 

 

 

 

 

SKU IMPORT

Stage 2

Implementation

1

Providing information about the line topology (topology diagram including machines to be mapped in PackOS) and units for machine counters.

 

C

R

Configure areas, lines, and machines in PackOS. Indication of machines acting as Base (availability, performance, quantity, set production units for area & plant

 

Flow article

2

Analysis and preparation of the network to collect data from machines and make them available to PackOS (unblocking ports if necessary)

 

R

C

Readiness of the infrastructure in the factory

 

 

3

Determining the access path to the OPC Server and making the computer available for LogixGate installation (and optionally OPCServer)

 

C

R

Installation of LogiXGate for data collection on the factory side, OPCServer configuration if not configured by the client

 

 

4

If the LogiX DataCollectorBox delivery option has been selected, installation of the delivered LogiX DataCollectorBox by the customer

 

R

C

LogiX DataCollector Box installation

 

 

5

Providing a list of tags/variables in OPC with a description of the meaning (or source data from drivers if ILABO configures OPCServer)

 

C

R

Configuration of counters and process parameters

 

Working with signals

6

Defining downtimes list & assigment to the specific OEE loss class

 

C

R

Configuration of downtimes list

 

Adding new Problem

7

Defining rules for downtimes

 

C

R

Configuration of downtime rules in PackOS

 

Defining rules for downtimes

8

Determining how to enter the production order plan:

stage 1 - p. 4 needs to be answered first

C

R

Preparation of import rules in FlexibleImporter if p.1a is selected

 

 

  1. Via Excel file

 

 

 

a. providing sample files

 

 

 

b. using ready-made PackOS templates

 

 

Order Template

2. By integration with the PackOS API

 

 

 

3. Manually

 

 

 

9

Determination of the MaterialMaster file - SKU lists along with:

  • line assignment

  • nominal line speeds

  • packing structures (unit conversion)

  • flow (topology) specific to a given SKU

  • [assigned materials - BOM]

Providing data to PackOS:

stage 1 - p. 4 needs to be answered first

C

R

Preparation of import rules in FlexibleImporter if p.1a is selected

 

SKU Import Template

  1. Via Excel file

 

 

 

a. providing sample files

 

 

 

b. using ready-made PackOS templates

 

 

 

2. Manually

 

 

 

10

Defining shifts pattern (list of shifts, shifts calendar)

 

C

R

Defining shifts in PackOS

 

Shifts

11

Defining automation rules: automatic start of orders from the plan, management of changeovers, defining time classification outside shifts & orders

 

C

R

Defining automation rules in PackOS

 

 

12

System admins list

 

C

R

Define system administrator accounts

 

 

13

Users list & permissions

 

R

I

Defining system user accounts

 

User Import Template And Description

14

Training of key people and starting to use the system.

 

C

R