Following kinds of reports:

• Reports for single Cell
  • 1st_prio_reports_cellboard.pdf
• Reports for Department / Plant
  • 2nd_prio_reports_cic.pdf

For each location (cell / department) will be required following maximum thresholds:

• monthly OEE %
• daily OEE %
• monthly Setup %
• daily Setup Time (Minute)
• monthly Downtime %
• daily Downtime (Minute)
• monthly Scrap %
• daily Scrap %

Following Query for modifying ubicaz table:

ALTER TABLE ubicaz ADD COLUMN thmonoee FLOAT;
ALTER TABLE ubicaz ADD COLUMN thmonsetup FLOAT;
ALTER TABLE ubicaz ADD COLUMN thmondownt FLOAT;
ALTER TABLE ubicaz ADD COLUMN thmonscrap FLOAT;
 
ALTER TABLE ubicaz ADD COLUMN thdayoee FLOAT;
ALTER TABLE ubicaz ADD COLUMN thdaysetup FLOAT;
ALTER TABLE ubicaz ADD COLUMN thdaydownt FLOAT;
ALTER TABLE ubicaz ADD COLUMN thdayscrap FLOAT;

Retval is a Rec containing a field for each Output; each field is a JSon-Object as following:

• name: name of the output
• threshold: an array of values refers to limits (one threashold for each x value)
• xvalues: an array of values refers tp the X axis
• yvalues: an array of values refers to the Y axis (12 items for monthly, 31 items for daily)
• um: an array of string, the first element is the unite of measure of X axis(Month, Day), the second element is the unite of measure of Y axis (%, Min)

The Retval Rec will contain also following JSON-Object to define time interval:

• monthly: an array of two integer elements; the first is the begin of time interval for yearly horizon, second is the end of the same
• daily: an array of two integer elements; the first is the begin of time interval for monthly horizon, second is the end of the same

Example URL Preview:

http://localhost/isw/webapp/enel/proled/iaf/ask/vismng/cellreports/newrec(jsrec,51,1,codubi,year,month)/NULL/0/400791/2017/4?_cnt=17

Example Javascript Preview:

iaf({p1:{codubi:"400791",year:2017,month:4},ag:"vismng",req:"cellreports",nume:0}).ask(function(rv){})

AgentVisualManagement manages OEE-Overview.

Def: OEE-Overview is an OEE calculation over the hierarchy of the plants, follows the hierarchy

We define a central DB in which the hierarchy of location is stored; in particular this information is stored into ubicaz table.

Furthermore it's necessary that AgentDataOEE is able to connect specific database where are stored OEE data (fact/dimension). To do that we define into central database following table:

CREATE TABLE dbubi (codubi VARCHAR(51) NOT NULL PRIMARY KEY, agdbname VARCHAR(101) NOT NULL);

Following schema of software solution for Global OEE-Overview



AgentVisManager, AgentDataOEE, AgentCenterUbica for this topic was stored in a specific platform, in which are defined also all tpevodb agents.

Following the current version of this platform:

xnet_agents_oee_ovew.xml

Following an image rapresent current Plant Hierarchy defined by Simon Fretz



For each database we should define the related edge of hierarchy defining Area and Company, both defined as TIPOSET='A'