1 highly confidential – do not distribute 360°sims – in line system main components

1 Highly confidential – do not distribute

360°SIMS – In Line SystemMain Components


SUPERVISOR

Data Server

EVENT BUS

GATEWAY

Measurem. Component

ISA

Sequence Manager

Rules Manager

Notification Manager

PLC

Data Filter

API (Direct Connection)

System Event

BASIC MODULE

CORE MODULE

ANYBUS Connection

Fx.Sns MGR

System Modules Map (In Line 360°SIMS)

Field BUS

DEVICE-NET or TCP-IP

OPTIONAL MODULE


System Modules Std. Location (In Line 360°SIMS)

PC SPV

SUPERVISOR

GATEWAY

EVENT BUS

FIXED SENS.

MANAGER

ISA SQN MGR

RULES MGR

Data Server

They could be elsewhere

ROBOT 1 ROBOT 2

PC 1 PC 2

MEASUREMENT COMPONENT 1

MEASUREMENT COMPONENT 2

PLCPLC


GATEWAY (+Event Bus)

• The Gateway is a software layer that allows all the Modules to talk each other, even through a network.

• Each Module generates Events related to its responsibility. Gateway distributes the Events to all the other Modules.

• Each Module receives all the Events coming from Gateway and, depending by the Event type, will use or not the information carried into it.

• Gateway doesn’t have UI (User Interface), just a SPY utility.

EVENT BUS

GATEWAY


SUPERVISOR

• The SUPERVISOR (SPV) Module collects all the Events coming from Measurement Component, Data Server, Sequence Manager and talks to the PLC through a dedicated connection (ANYBUS).

• SPV shows the current Measurement Component status, the name of running program, Error messages and Warning messages.

• SPV has a UI.

SPV


MEASUREMENT COMPONENT

• The Measurement Component (MC) Module handles the Optical Heads (could be two or more), collects all the measured data (also coming from external sources), packs these data into a unique data set, sends the data to Data Server. Part programs creation is still done by CoreView Teach software.

• The handling of Optical Head means: Run measurement cycle and synchronize the Tile acquisition through the dedicated Robot

connection Control all the process of all the OH’s Handle OH calibration cycles as needed

• Measured data management means: Unify (combine) data coming from ALL sensor (some of them could be external) Send measured data

MC


RULES MANAGER

• The Rules Manager (Rls MGR) Module is designed to create rules, working on the results of measurement, that can override the tolerances defined in the Set up created in Measurement Component (through CoreView Teach). The combination of all the rules creates the Exit Status.

• The general condition of a complete cycle (Exit Status) can be either defined as a single or a combination of different status, determined by every single measurement result.

• The Exit Status (Good, Critical, Not Good, Not Measured, Reject, Stop the Line) is then sent to the SPV.

• Depending by Customer choice the action to take, related to the Exit Status, can be performed either at SPV or PLC level.

• Rls MGR has UI.

Rls MGR


ISA

ISA (In Line Station Application)

• The In Line Station Application (ISA) Module displays the measurement results in a graphic form. It’s the interactive link with the Line Operator, to show him what’s going on.

• ISA can show results of the last executed cycle as: Single drops (Features) Cross sections Colored map.

• ISA can also show trend charts that display the last “n” executed cycles.• ISA displays also the System Status, a progress bar of current cycle

execution, a self-updating mapping of Exit Status (in percentage), based on the last… cycles.

• ISA has a UI.


DATA SERVER

• The Data Server (DS) is the link to the Data Base. This Module collects all measured data from Measurement Component.

• DS shares the measured data with Rules Manager and ISA.• Form Rules Manager receives the Exit Status and send it to the SPV.• DS doesn’t have UI.

DS


Sqn MGR

SEQUENCE MANAGER

• The Sequence Manager (Sqn MGR) Module handles the execution order of different programs.

• This module can create several lists that contain the sequence of the program to be executed. Each list can be linked to a different part type.

• The use of the lists covers different application scenarios: In case of In Line installation for BIW inspection, is quite sure that one single program can’t

measure the whole part within the cycle time. The solution is to create more programs that measure only a section of the part (Splits) and populate the list with the desired execution sequence.

In case of In Line installation for Closures or subassemblies, Sqn MGR can be used to handle different part types coming into the cell. In this case each list may handle just one program but the System will be able to switch automatically the program execution, depending by the incoming part type.

• Sqn MGR as a UI


Ntf MGR

NOTIFICATION MANAGER

• The Notification Manager (Ntf MGR) Module has only one task: send notifications (like sms, email, what’s up, twitter…) to a predefined list of persons.

• The rule to send a notification is established in Rules Manager Module.• Ntf MGR doesn’t have UI.


FIXED SENSOR MANAGER

• The Fixed Sensors Manager (Fx.Sns MGR) should handle any type of Fixed sensor working into a cell.

• A Fixed Sensor has to be intended as “any external measurement data source that is not a WLS400 Optical Head”.

• At present there are two types of Fixed Sensor available: Optical (Camera + multiple laser stripe) Contact (Digital scales embedded into RPS_Device)

• In both cases the sensor must be driven by a software module.• The Fx.Sns MGR should be linked to the above mentioned software module

to perform the following functions: Synchronize the measurement event Gathering data from sensors Send measurer data to MC

• Fx.Sns MGR shouldn’t have UI (may have a Set up Interface)

Fx.Sns MGR

1 highly confidential – do not distribute 360°sims – in line system main components

Documents