00197717-02_VB_Traceability4.1_DE_EN.pdf - 第30页
System Requirements and Software Components Configuration 30 SIPLACE Traceability 4.1

System Requirements and Software Components
System Requirements for SIPLACE Traceability
SIPLACE Traceability 4.1 29
4
4 System Requirements and Software Components
System Requirements and Software Components
4.1
4.1 System Requirements for SIPLACE Traceability
System Requirements for SIPLACE Traceability
4.2
4.2 Configuration
Configuration
In order to establish the connection to the station computer, you need to install SIPLACE Trace Server
in the SIPLACE LAN. The installation options vary according to your network configuration and are as
follows:
1. SIPLACE Trace Service on one computer
This option requires that all SIPLACE Pro computers are available in the same LAN segment.
2. SIPLACE Trace Service on each line server
This option needs to be selected if the SIPLACE Pro computers are in different line-specific LAN seg-
ments.
3. SIPLACE Trace Monitor
SIPLACE Trace Monitor is installed as part of SIPLACE Studio and opened as a module via SIPLACE
Studio.
The following requirements need to be fulfilled:
1. Each Trace Service configured at the factory with the export option Database must be able to access
the central SQL server, on which the traceability database is installed.
2. The SQL server with the database is on computers in the same LAN segment.
NOTICE
System requirements
The system requirements (supported operating system and database variants) and an over-
view of mutually compatible products can be found in the Assembly Instructions SIPLACE Sup-
port Media, item no [00197214-xx].
NOTICE
Station based traceability
For machine-based traceability, the SIPLACE placement machines must be equipped with the
options "Setup verification" and "Traceability".
NOTICE
System requirements
The system requirements (supported operating system and database variants) and an over-
view of mutually compatible products can be found in the Assembly Instructions SIPLACE Sup-
port Media, item no [00197214-xx].
NOTICE
SQL server
For a detailed description of how to install the SQL servers, refer to the Assembly Instructions
(item no. 00196824-xx (English)), on Support Media DVD 1. The SQL server itself is not part of
the Support Media DVDs.
System Requirements and Software Components
Configuration
30 SIPLACE Traceability 4.1

Existing Restrictions
Traceability
SIPLACE Traceability 4.1 31
5
5 Existing Restrictions
Existing Restrictions
5.1
5.1 Traceability
Traceability
▪ The Traceability OIB interface "OIB Interlocking Interface", has been discontinued and will no longer
be available in future versions. This interface will be replaced with the new "OIB Eventing Interface".
▪ Traceability 4.x does not support archiving. We recommend that you periodically create a new data-
base and manually archive older versions of Trace database. The Trace Service Manager has a
range of database operations for backing up a non-productive (to be archived) database in the file
system and to then delete this on the SQL server.
▪ Nonobservance of the restrictions specified in the SIPLACE Setup Center 7.x software version de-
scription can lead to incorrect traceability data.
▪ The following features of SIPLACE Setup Center 7.x are supported in station based traceability
mode only:
– Alternative components
– Random setup on feeder tables
▪ The component level indicator in connection with setup verification should always be run with acti-
vated stop thresholds.
▪ When downloading a new setup in line-based traceability, the conveyors must be empty. If this is not
the case, the traceability data may be incorrect.
▪ When using dual conveyors, the conveyor lane is unknown if the following requirements are present:
– The line has been configured for station-based traceability
– The traceability information is generated on stations with station software 40x/50x or 60x.
– The job in the LCGUI uses the same setup, recipe or board on the two lanes.
▪ Line-based traceability does not support station-wise downloads.
▪ Station software version 408 is not supported.
▪ If a track is not fitted with splice detection, the reliability of the traceability data depends on the ac-
curacy of the component levels. The packaging unit change is therefore logged according to the re-
spective component level.
▪ The logging of detected splice points for X feeders (so-called "Splice Events") in the traceability XML
files is no longer performed since SIPLACE Trace Service 3.3 in the default configuration. For further
information about this, contact your local SIPLACE customer support.
▪ The renaming or moving of lines within the programming system "Siplace Pro Desktop" during pro-
duction operations is not supported. To avoid data loss and/or faulty data, the following procedures
should be followed for renaming or moving the Siplace Pro line name:
– All conveyor lanes in the line must be run empty
– After this, rename the line on the SIPLACE Pro desktop
– Configure the new line name in Setup Center (delete old line, add new one)
– Configure the new line name in Trace Service (delete old line,
add new one, apply configuration)
– The production job to be produced needs to be reconfigured at the line, using the SIPLACE Pro
LineControl function.
▪ Traceability data of bulk case feeders, linear feeders and LED feeders can only be used if the oper-
ator makes sure that the feeder is completely empty before each refill.
▪ The following maximum lengths (characters) for the PCB barcode are available if the PCB barcode
is read in the SIPLACE machine:
Station software Single conveyor Synchronous dual convey-
or
Asynchronous dual convey-
or
407 / 505 / 605 / 70x 40 characters 40 characters / 40 charac-
ters
40 characters
From SiplacePro 11.2
and 707.1
255 characters 255 characters / 255 char-
acters
255 characters