00194923-01_OIS_DB.pdf - 第7页

OIS Datenbank Version 4.1 Schnittstellenbeschreibung OIS Database Version 4.1 Interface Description 7 von 47 4 Dat abase The only database system supported is the Micro soft SQ L-Server product, version V8.0 (SQL-Server …

100%1 / 47
Schnittstellenbeschreibung OIS Datenbank Version 4.1
Interface Description OIS Database Version 4.1
6 von 47
1 General
The OIS software (Operator Information System) handles production data acquisition for the SIPLACE
placement machines. The data is saved in a database. In order that third-party users/applications can
retrieve and process this data, this document provides a description of the functionality of the OIS software
and the database format for the data supplied.
2 Data interface
All data that can be retrieved from the OIS database is supplied in the form of database views. This ensures
that the database format is not (forcibly) modified even if changes are made to the database format. All
views are read-only; write access is not possible. When strings are transferred, no length restriction is
applied. This means that the transferred values always correspond to the actual format in the database,
because the ODBC interface permits variable access. If string lengths are changed within the database, the
data is thus always forwarded correctly via ODBC.
3 Restrictions
The programs implemented are subject to specific limits and priorities based on the hardware used and the
available data storage. To ensure an unrestricted placement sequence, the SIPLACE Pro software must
always be assigned highest priority, followed by the SIPLACE OIS software and only then the 3
rd
-party
products used. It may be necessary to impose this type of restriction by means of appropriate configuration
within Windows. In addition, the size of a 3
rd
-party database schema must not overstretch the limits of the
existing system configuration, i.e. it may be necessary to impose a restriction on the maximum size
proportional to the available data storage.
There is a clustered index on the tables BOARD, EVENT, USEREVENT, PICKUPERROR and
USEDCOMPONENTS, for the identification of the station and date/time when the event occured. This means
that queries for a station and a timespan are executed fast. This also meanss that timespan queries for a
group of stations are executed slowly. It is preferred to make station-wise queries.
Example for fast and slow queries:
Fast query for huge data:
FOREACH (station x in line) { SELECT all boards WHERE station = x AND day = 17.08.2006 }
Slow query for huge data:
SELECT all boards WHERE (station = line.station1 OR station = line.station2 …) AND day = 17.08.2006
OIS Datenbank Version 4.1 Schnittstellenbeschreibung
OIS Database Version 4.1 Interface Description
7 von 47
4 Database
The only database system supported is the Microsoft SQL-Server product, version V8.0 (SQL-Server 2000).
4.1 Name of the database
SiplaceOis
4.2 Version of the database schema
The Version entry in the DATAMODEL table supplies the version number of the database schema in the
lLong column. The current version is 207.
4.3 Users
The following users are needed to access the database:
• 3
rd
-party user
− Name: SiplaceMonUser3P
− Password: <NULL>
• 3
rd
-party user
− Name: SiplaceOisUser3P
− Password: <NULL>
Note
The user SiplaceMonUser3P has been set up globally in the master database and permits access to all
monitoring databases (OIS and SIS). In the medium term, SiplaceMonUser3P will replace the user
SiplaceOisUser3P.
4.4 Tables
The layout of the individual tables is illustrated below. The specified data types correspond to the naming
scheme in the MS-SQL-Server.
Note: The sole purpose of the following tables is to clarify the views. No write access is permitted to these
tables.
Legend for tables: CI = Clustered index
I = Index
P = Primary key
Schnittstellenbeschreibung OIS Datenbank Version 4.1
Interface Description OIS Database Version 4.1
8 von 47
4.4.1 BOARD table
BOARD OIS name Data type Byte CI P
Identification number of the Station (Reference to
Table STATION)
lId int 4
9
End date/time of PCB manufacture dtTime datetime 8
9
Manufactured production batch strRecipe nvarchar(100) 200
Name of the set-up strSetup nvarchar(50) 100
Name of the PCB strBoard nvarchar(50) 100
Serial number of manufactured PCB lBoardNumber int 4
Conveyor belt 1 / 2 ucConveyor tinyint 1
Cycle time of PCB sDuration smallint 2
Starting time since production batch manufactured dtRecipeStart datetime 8
Starting time since set-up used for manufacture dtSetupStart datetime 8
PCB barcode strBarcode nvarchar(40) 80
PCB status (0 = OK; 1 = aborted; 2 = continued) ucStatus tinyint 1
4.4.2 EVENT table
EVENT OIS name Data type Byte CI P
Identification number of the Station (Reference to
Table STATION)
lId int 4
9
Date/time at which this event occurred dtTime datetime 8
9
Serial number of manufactured PCB lBoardNumber int 4
Conveyor belt 1 / 2 ucConveyor tinyint 1
Processing area 1 / 2 ucProcessingArea tinyint 1
Event number sEvent smallint 2
4.4.3 USEREVENT table
USEREVENT OIS name Data type Byte CI P
Identification number of the Station (Reference to
Table STATION)
lId int 4
9
Date/time at which this event occurred dtTime datetime 8
9
Serial number of manufactured PCB lBoardNumber int 4
Conveyor belt 1 / 2 ucConveyor tinyint 1
Processing area 1 / 2 ucProcessingArea tinyint 1
User event number sEvent smallint 2