00900045-01_ID_OIS_SIS_14.0_R16-2_DE_EN - 第8页

ASM OIS/SIS Databases 14.0 ( R16 - 2) / Interface De scription 12/2016 Edition 8 2 Data Interface All data that can be ret rieved from the OIS/SIS dat abase is supplied in t he form of database vi ews. This ensures t hat…

ASM OIS/SIS Databases 14.0 (R16-2) / Interface Description 12/2016 Edition

1 General

This document describes the ASM OIS Version 14.0 (Release-Tag: R16-2) software. The

Release-Tag displays in which ASM Release the current product has been released.

Example: (R16-2) –> 2. Release, 2016.

The ASM OIS/SIS software (Operator Information System/Setup Information System) handles

production data acquisition for the SIPLACE

placement machines. The data is saved in a

database. In order that 3

party users/applications can retrieve and process this data, this

document provides a description of the functionality of the ASM OIS/SIS software and the database

format for the data supplied.

ASM OIS/SIS Databases 14.0 (R16-2) / Interface Description 12/2016 Edition

2 Data Interface

All data that can be retrieved from the OIS/SIS 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.

ASM OIS/SIS Databases 14.0 (R16-2) / Interface Description 12/2016 Edition

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 ASM OIS and ASM SIS

software and only then the 3

-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

-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.

Additional Restrictions for OIS

There is a clustered index on the BOARD, EVENT, USEREVENT, PICKUPERROR und

USEDCOMPONENTS tables for the identification of the station and date/time when the event

occured.

This means that queries for one station and one time span are executed very fast.Im Gegensatz

dazu werden Abfragen für ein Zeitintervall für mehrere Stationen langsam abgearbeitet.

But this also means that queries for one time span for any stations are executed slowly.

It is preferred to make station-wise queries.

There is also a normal index on the tables BOARD, EVENT, USEREVENT, PICKUPERROR und

USEDCOMPONENTS tables.

This means that queries for all stations for one time span are executed quickly.

Example for fast and slow queries

Fast query for huge data with dtTime:

FOREACH (station x in line) { SELECT all boards WHERE station = x AND

dtTime = 12.03.2007 }

Fast query reading all stations for huge data with dtCreated:

SELECT all boards AND dtCreated = 12.03.2007

Slow query for huge data with dtTime:

SELECT all boards WHERE (station = line.station1 OR station =

line.station2 …) AND dtTime = 12.03.2007

Slow query for huge data dtCreated:

FOREACH (station x in line) { SELECT all boards WHERE station = x AND

dtCreated = 12.03.2007 }