Guide to different ways to capture data

Transcription

1 A B C D Manual input RS Blackbox PLC/OPC Integration server E Standard ERP-integration ERP 24V Web Services XML

2 A Manual input Mainly used to move knowledge from machine operators to RS Production s database Only a PC (see Guide to select PC for Operator tools ) + Low investment + Not depending on 3 rd party solutions - Manual input is never 100 % correct Depends on what you are collecting data for (se below) None Manual input can be made in; P100 (start/stop order, produced and rejected amount, stop cause etc) PK200, Standard Operation Procedures PK202, Maintenance support PK204, Track and Trace PK211, Andon & Alarm Escalation PK213, Labor & Competence

3 B RS Blackbox Mainly used to capture machine status and count machine cycles. Handles digital signals only. RS Blackbox (of course). It comes in different sizes with different number of inputs and outputs All you need is the P100 Elemental OEE + Low investment + Extremely high availability + Not depending on any third party software + Short lead time + For most type of production processes can connection be done by local machine electrician and no IT staff needs to be involved - Connecting via Ethernet to a central PC can cause problems when the network is unstable (using RS232 COM is no problem) - Building a parallel infrastructure when OPC or other data layer is available can be wrong way to go 24V None Connection to PC can be via RS232 COM-cable or Ethernet cable. See Guide to decide how much hardware you ll need for details here. Mainly supports functionality in P100 such as measure point status, cycle time, registration of rejects/scrap, automatic categorization of stop reason. Inputs can with configuration from RS Production specialist receive sets of binaries describing article number, station id and other larger number.

4 C PLC/OPC Capture anything from status and cycles to current order/article and process values/measures No RS Production hardware needed PT218 OPC Client is needed to connect to your OPC Server/Servers + Very cost efficient when OPC-infrastructure already is in place + Can capture all kinds of production data automatically + Flexible - Depends on third party software services and solutions There must be an OPC Server where you have published the tags that RS Production should capture. Besides supporting functionality in P100 such as measure point status, cycle counter, registration of rejects/scrap, automatic categorization of stop reason, current order/article etc the OPC connection is often used to collect process values and measures for PK203 Stable Processes. Can also be used to collect alarms for PK213 Andon and Alarm Escalation RS Production OPC client must be installed locally on the same net as the OPC Server. The absolutely most safe is to install it on the same Windows machine as the OPC Server. Machine 1 Machine 2 PLC mod A PLC mod B PC Machine network Windows PC RS Production OPC Client OPC Server of any brand Office network Windows Server PC RS Production Server Windows PC RS Production Office tools PC PC for Operator tools only

5 D Integration Server Capture anything from status and cycles to current order/article and process values/measures Web Services XML No RS Production hardware needed PS102 Integration Server is needed to connect to external data sources plus a separate support & subscription contract. None other than the other data source + Can capture all kinds of production data automatically - Needs a very good specification and documentation of the data source - Depends on third party software services and solutions - Third party s integration interface may change over time - Will always include a customer unique part in the delivery RS Production Integration Server client must be installed locally on have connection with the data source in real time. Besides supporting functionality in P100 such as measure point status, cycle counter, registration of rejects/scrap, automatic categorization of stop reason, current order/article etc the Integration Server is often used to collect process values and measures for PK203 Stable Processes. Can also be used to collect alarms for PK213 Andon and Alarm Escalation Datasource Customer unique Middleware RS Production DataModel Must be developed by a RS Production certified developer

6 D Standard ERP Integration Handle production plan including order/article start and stop and reporting to ERP ERP No RS Production hardware needed PINT205 Standard ERP Integration is needed. Normaly uses Web Services or a SQL database as interface area + support agreement + Standard surface area + Can be developed by any developer + No customer unique part in RS Production - Depends on third party software services and solutions - Third party s integration interface may change over time - Will always include a customer unique part in the delivery A middleware between RS Production and the ERP system needs to implement PINT205 s interface Helps reading production plan from ERP and also report times and amounts back to ERP (operation, order, material usage, move to stock) Ask for the PINT205 detail specification for full details RS Production Integration Server client must be installed locally on have connection with the middleware in realtime. ERP Datasource Customer unique Middleware PINT205 Integration surface RS Production DataModel Often developed by customers ERP consultant WebServices or SQL Server Standard available for many ERP-systems