1. Documentation * MSL System Client - Content€¦ · 4 Introduction This document describes how to use the application MSL-Control and gives an overview of the structure of the

1

1. Documentation * MSL System Client - Content

2 Specification of Performance ...................................................................................................................................................................................................................... 3

3 Terms & Abbreviations................................................................................................................................................................................................................................ 4

3.1 Abbreviation......................................................................................................................................................................................................................................... 4

3.2 Terms ................................................................................................................................................................................................................................................... 4

4 Introduction ................................................................................................................................................................................................................................................ 5

5 System requirements .................................................................................................................................................................................................................................. 5

5.1 MSL Setup Center ................................................................................................................................................................................................................................ 5

5.2 MSL Control services (MSLCTL) ............................................................................................................................................................................................................ 6

5.3 MSL Client ............................................................................................................................................................................................................................................ 7

5.4 SQL Server 2012 SP1 ............................................................................................................................................................................................................................ 7

6 System overview ......................................................................................................................................................................................................................................... 8

7 MSL Client ................................................................................................................................................................................................................................................... 9

7.1 User login ............................................................................................................................................................................................................................................. 9

7.2 Change user password ......................................................................................................................................................................................................................... 9

7.3 Settings .............................................................................................................................................................................................................................................. 10

7.4 Store Material .................................................................................................................................................................................................................................... 11

7.4.1 Input fields .................................................................................................................................................................................................................................. 12

7.5 Take out Material ............................................................................................................................................................................................................................... 13

7.6 Report Batch Quantity ....................................................................................................................................................................................................................... 14

7.7 Report Empty Batch ........................................................................................................................................................................................................................... 15

7.8 Delete Batch Containers .................................................................................................................................................................................................................... 16

2

7.9 Material .............................................................................................................................................................................................................................................. 17

7.10 Storage Report ................................................................................................................................................................................................................................. 18

7.11 User Report ...................................................................................................................................................................................................................................... 19

7.12 Error Report ..................................................................................................................................................................................................................................... 20

8 Databases .................................................................................................................................................................................................................................................. 21

8.1 MSLSetupCenter ................................................................................................................................................................................................................................ 21

8.2 MSLControl ........................................................................................................................................................................................................................................ 21

8.3 MSLControl_Archiv ............................................................................................................................................................................................................................ 21

8.4 Support and Maintenance ................................................................................................................................................................................................................. 21

8.5 Login................................................................................................................................................................................................................................................... 21

9 Interfaces .................................................................................................................................................................................................................................................. 22

9.1 File interface ...................................................................................................................................................................................................................................... 22

9.2 SQL Server – Stored procedures ........................................................................................................................................................................................................ 22

9.2.1 getBarcodeType .......................................................................................................................................................................................................................... 22

3

2 Specification of Performance This program provides as a software solution of controlling material batches and MSL-Levels for the production equipment and its status during

processing and storage handling (In-Out), as well as the conditions of current processing. This application controls – and displays – each of any

material drying conditions as required for the proper equipment situation of current production orders.

The evaluation of drying states is based on the requirements of IPC/STD 033B1 rules, but may be adapted individually to customized options.

Acquisition of storages and the outsourcing (Store-In, Store-Out)

Calculation of the drying time, the hold time and the open time.

Display of the remaining open time.

Individual MSL-Levels can be defined

Deposit of the MSL JEDEC Level Policy

Tables of back-drying can be edited

Display of temperature and humidity, and dynamic calculation of the re-drying procedure (sensor required)

Configurable authorization concept for user groups and operators

Standardized interfaces to MES or ERP Systems.

Archive Database

Simple connections to the MSL-Databases with third-party applications are possible, e.g. by Microsoft Excel

A storage protocol that allows printing to issue incoming or outgoing storage operations with a variety of filtering options, as several export options to PDF and XLS file format.

Warning and alarm window for Batch-ID monitoring faded.

Operator Log-file with print function to output all user logins; export to PDF and XLS files possible.

Failure logging with printing function to issue alerts and warnings of climate data. Export to PDF and XLS possible.

Free storage space entry

Configuration of barcode definitions for the batch and/or material barcodes with prefix and separator

Program control, possible via barcode.

Programming of individual Barcode definitions, based on SQL-Server procedures; in that case, SQL knowledge is required.

Free configurable alarm and warning limits.

Multiple client programs can be installed on a corporate network

Low TCA (Total Cost of Administration) over other databases

Quantity or remaining quantity feedback for the material batch-container possible

Assistant to find and delete containers that have not been logged out - or that have been imported but not yet used.

Additional chargeable services: Remote database administrator

Individual interface options for MES or ERP systems

Special solutions to customer requirements

Note: If managing more than one cabinet it is recommended to install the databases on a separate SQL Server.

The MSLCTL service should always run on the database server. If only one cabinet is used, a full installation on a single PC may be sufficient.

4

3 Terms & Abbreviations

3.1 Abbreviation

MS Microsoft; products identified with "MS" are registered trademarks of Microsoft Corporation, Redmond.

3.2 Terms

Barcode scanner This term defines a barcode scanner that is connected via a serial port. If a USB scanner does not redirect its output to a virtual RS232 interface, the input is handled as input of keystrokes.

Input textbox

Entries in a textbox using the keyboard needs to be confirmed with the enter key

Scan Barcode via serial interface, refer also to Barcode scanner

Unique lot, Container, Batch Unique ID: identifies the material clearly. A double assignment is not allowed.

5

4 Introduction

This document describes how to use the application MSL-Control and gives an overview of the structure of the overall system.

All illustrations have to be viewed as examples.

5 System requirements

5.1 MSL Setup Center

Hardware

Processor speed 1-GHz-Processor or higher , 32 Bit (x86) or 64 Bit (x64)

Processor type x64-Processor: AMD Opteron, AMD Athlon 64, Intel Xeon mit Intel EM64T support, Intel Pentium IV with EM64T support

x86-Processor: Pentium III compatible processor or with higher speed

Free memory 10 MB RAM

Harddisk minimum 10 MB available hard disk space

Monitor Requires a Super VGA Graphic card, minimum resolution 1024x800

Network TCP/IP for the SQL Server connection UDP for the MSLCTL service control

Software

.NET Framework .NET 3.5 SP1 is required for starting the setup program “MSLSYSTEM_SetupStart.exe“, .NET 4.0 is required for the application and will be installed (if missing) while running the setup program.

Supported operating systems MS Windows XP SP 3 (32 Bit and 64 Bit) MS Windows 7 (32 Bit and 64 Bit) MS Windows Server 2008 R2 SP 1(64 Bit) MS Windows Server 2012 (64 Bit)

6

5.2 MSL Control services (MSLCTL)

Hardware

Processor speed 1,4-GHz-Processor or higher , 32 Bit (x86) or 64 Bit (x64)

Processor type x64-Processor: AMD Opteron, AMD Athlon 64, Intel Xeon with Intel EM64T support, Intel Pentium IV with EM64T support

x86-Processor: Pentium III compatible processor or or higher speed


Hard disk Minimum 1GB available hard disk space

Monitor Requires a Super VGA Graphic card, minimum resolution 800x400

Serial interface RS232 per sensor

Network TCP/IP for the sensor and SQL Server connections UDP for the MSLCTL service control

Software


Supported operating systems MS Windows 7 (32 Bit and 64 Bit) MS Windows Server 2008 R2 SP 1(64 Bit) MS Windows Server 2012 (64 Bit)

It is assumed that the service is installed on the same computer where the MS SQL Server is installed.

7

5.3 MSL Client

Hardware

Processor speed 1-GHz-Processor oder higher, 32 Bit (x86) or 64 Bit (x64)

Processor type x64-Processor: AMD Opteron, AMD Athlon 64, Intel Xeon with Intel EM64T-Support, Intel Pentium IV mit EM64T-Support

x86-Processor: Pentium III compatible or higher speed


Hard disk Minimum 500 MB available hard disk space

Monitor Requires a Super VGA Graphic card, minimum resolution 1920x1024 Pixel.

Serial interface RS232 for hand-held scanner (Option)

Network TCP/IP for the SQL Server data connection and UDP for the MSLCTL control connections

Software


Supported operating systems MS Windows XP SP 3 (32 Bit and 64 Bit) MS Windows 7 (32 Bit and 64 Bit) MS Windows Server 2008 R2 SP 1(64 Bit) MS Windows Server 2012 (64 Bit)

5.4 SQL Server 2012 SP1

Comprehensive information on the system requirements can be found in https://msdn.microsoft.com/library/ms143506%28v=SQL.110%29.aspx.

https://msdn.microsoft.com/library/ms143506%28v=SQL.110%29.aspx

8

6 System overview

MS SQL Server 2012

MS CTL (Dienst)

MSL Setup Center

MSL Client

Sensor Cabinets with sensor Picture 1 "System overview"

MSL Client MS Windows application, user interface for stock movements, display of measurements, material management, protocols. MSL Setup Center MS Windows application, user interface for the MSL-System configuration, MSL-Tables, cabinets, sensors, assigning access permissions, Barcode definitions, settings of Client stations, etc. MSLCTL MS Windows service. Logging of the measured sensor values (temperature and humidity). Calculation of remainder open times and the back-drying. Controlling optional LED strips. MS SQL Server 2012 SP1© Microsoft SQL Database Server, managing the MSL databases - Material (MSLControl) - Setup (MSLSetup) - Material (MSLControl_Archiv) The scope of delivery includes the free version of MS SQL Server Express 2012. The databases and the service MSLCTL can of course be installed in a virtual environment in your data center.

9

7 MSL Client

7.1 User login

The "User login" may be called either upon start of the application (as configured in MSL Setup Center) – or by the menu "User > Change user".

Picture 2 User login

For a new installation, the following default users exist :

Login name Password

Admin Admin

Operator Operator

User User

The login can be done by button "ENTER" in field "Password" – or with the "O.K." button.

7.2 Change user password

Picture 3 Change user password

With click on button "Change password", the login form will be extended.

Please enter your valid login data and the new password into the fields "New password" and "Repeat new password". You can then overwrite the current password by click on the button "Change password".

Each user is allowed to change the own password. If you have forgotten your password, you can rewrite the current password of the operator in the MSL Setup Center .

10

7.3 Settings

If any settings are modified, the application must be restarted.

Picture 4 Settings

Settings are stored separately for each Windows user

.

The file "user.config" is stored in the folder "C:\Documents and Settings\<username>

\[LocalSettings\]ApplicationData\<companyname>

\<appdomainname>_<id>_<hash>\<version>" Therefore it is possible to start the application multiple times

on a terminal server with different configurations.

If the application is started with different Windows user accounts, the settings for each user account must be set separately.

Setting Description

Database connectionstring Display only. To change the connection: close the application and start MSL Client -> „MSL Client after install“ from the start menu..

Output Station Nr. Store-Out location (only for DryTower )

Scanner COM port COM Port for serial Scanner (19.200 Baud, 8 Databits, 1 Stopbit, Parity even, suffix CRLF)

Sensor display Show the window of sensor measurements

Display Alarms/Warnings Show window of alarms and warnings

Language Language settings German/English

Logfile Drive:\Path\Filename. If necessary, the processing of scanned barcodes can be recorded. If a barcode does not function as desired during the storage or retrieval, the related processing flow may be tracked.

11

7.4 Store material

The form shown below (Picture 5) will open when called by the main menu via "Cabinet > Storage" or by the configured barcode. This form is used

to

create new batch-containers and to store them - or to store any outsourced packaging again. The container gets the storage status "in" (stored-in).

If

the selected cabinet is marked as "Re-drying", the re-drying and the calculation of the remaining open time will start at the time of storage.

If the cabinet is configured as "Dry Pack", no calculation of the re-drying is done.

In MSL Setup Center , the fields of "Quantity", "Expiration date" and "Material number" may be configured as "optional" input fields;

the fields of "Quantity" and "Expiration date" can also be preset with default values.

Picture 5 Store material

Required fields are marked with the symbol until they have been entered correctly > Manual field entries must be done with the <Enter> key.

The entry / selection of the fields can be done via the keyboard and a Barcode scanner . If all required fields have been filled, the button "Store" will be activated. The storage will be completed by scanning the storage location or by click on the "Store" button.

12

7.4.1 Input fields

Field Description Länge

Cabinet Selection of the cabinet to be just filled.

Unique Container ID After Input or after Scan , the material is verified to be known. In that case (see Picture 6), the fields are filled

automatically. The previous storage location is displayed and in the list next to it, all storage locations of this material will be displayed.

50

Material number After Input or after Scan , the list next to it shows all storage locations of the material that is stored in the selected cabinet.

30

Incoming Material ID The "Incoming Material ID" is an optional input field. 30

Quantity Number of components on the container

Open time (in hours) Residual open time; if entering -0.01 for a new container, the maximum of remaining open time will be set (100% re-drying).

Thickness Thickness of housing

MSL-Level MSL-Level

Expiration date The application does not operate according to a FIFO order. Outsourcing and sorting mainly depend on the expiration date.

Storage place In this example (see Picture 6) S1=Cabinet 1, B1 = Bottom 1, F1= Tray 1. Free input (max. 8 characters) 8

Picture 6 Store material (completely filled)

13

7.5 Take out Material

This form (Picture 7) is opened by the main menu via "Cabinet > Take out" – or by the configured barcode.

The field "Material" is used to search for stored material.

After Input or Scan of material number, the list next to it is filled with the current batch data, sorted by expiration date (ascending).

Picture 7 Take out material

After Input or Scan of the Container-ID (Batch) – and after successful verification – the status of that container is set as outsourced (out):

Upon taking-out and removal of the material, the re-drying is stopped and the open time of the container begins.

14

7.6 Report Batch Quantity

This form is called by menu "Cabinet > Report batch quantity".

Picture 8 Report batch quantity

After Input or Scan of Container-ID, the status field shows the container, material and quantity on taking-out (outsourcing). The operator can now choose between entering the quantity consumed

- or

entering the remaining current quantity amount. The quantity is updated by pressing the F5 key or by click on the button "Confirm quantity":

Picture 9 Status "Update quantity"

15

7.7 Report Empty Batch

This form is called by menu "Cabinet > Report empty batch".

Picture 10 Report empty batch

After Input or Scan of Container-ID, the Container-ID and the quantity of taking-out action will be displayed. By pressing F5 key or click on button "Confirm quantity", the container is moved to the "Archive Database" .

Picture 11 Report empty batch, Status "Container logged off"

16

7.8 Delete Batch Containers

This form is called by menu "Cabinet > Delete batch".

By means of various interfaces, it is possible to apply material data in the MSL database. In most cases, this is done automatically by a higher-level

MES or ERP system. The materials are held in the database with a status as "outsourced" or "closed" (out, closed).

In the case of first storage (see 7.4 page 11), the container data are automatically filled and do not have to be entered by the operator.

By using the following form (picture 13), those containers can be displayed and deleted for which no notification of an "Empty batch" (see 7.7 page

15) has been given – or to show imported data that never has been used.

Picture 12 Delete batch containers

By pressing F5 key or click on button "Display", the list shows all containers with status "outsourced" (out) where the date of last storing or the import

date is older than current date minus the specified number of days. The containers are selected by click on column "Marked for delete". By pressing

F9 key or click on button "Delete selection", the selected containers will be deleted.

If the reporting of "Empty batch" has been forgotten for a container, we recommend that the container is moved into the database archive by

completing the function "Report empty batch". All data of containers that are deleted using this form (picture 13) will be lost forever.

17

7.9 Material

This form is opened with menu "Application > Material". The form is used to view the list of containers; that data may be refreshed with click on

"Refresh" button.

Picture 13 Material

The container is deleted with click on button "Delete batch"; the data will not be archived.

The field "Filter" filters the columns material and containers. By means of the 3 combination-buttons you can set filters based on a cabinet, based on

warning and alarm limits or based on the status. The warning limit ensures reaches or falls below this limit to be displayed as colored background, e.g.

to verify the container's remaining open time.

18

7.10 Storage Report

This form is called by menu "Protocol > Storage report".

For each storing and removal action an entry is made in the protocol.

Picture 14 Storage report

All input and selection fields serve as filter conditions of the report to be calculated.

With click on button "Calculate report" the result data will be displayed. With click on button "Print preview" the data will be shown as print layout.

19

7.11 User Report

This form is called by menu "Protocol > User report".

For each user login an entry is made in the protocol.

Picture 15 User report

All input and selection fields serve as filter conditions of the log report to be calculated.

With click on button "Calculate Report" the result data will be displayed. With click on button "Peview" the data will be shown as print layout.

20

7.12 Error Report

The form is opened with menu "Protocol > Error report".

Upon reaching alarm or warning limits of a cabinet sensor, an entry is made in the log report.

Picture 16 Error report

All input and selection fields serve as filter conditions of the log report to be calculated.

With click on button "Calculate protocol" the result data will be displayed. With click on button "Preview", the data will be shown as print layout.

21

8 Databases

8.1 MSLSetupCenter

The database "MSLSetupCenter" stores system-wide configurations, MSL tables, cabinets, sensors, permission rules, barcode definitions, client station

settings, etc.

8.2 MSLControl

The database "MSLControl" contains all tables of the current containers and protocols.

8.3 MSLControl_Archiv

Upon "Report of empty batch", the container and log data will be moved to the archive.

You cannot have access to evaluation reports from within the MSL applications; you may use third-party tools, e.g. MS Excel © .

8.4 Support and Maintenance

The Microsoft SQL Server © used in this MSL-System has - compared with other database systems - by far a low TCA (Total cost of administration).

Creating maintenance scripts of database backups, the indexing management and optimization of journal files (Log) is the responsibility of the

customer.

If you do not have the qualified personnel in your IT, you can delegate that care also to our remote DBA.

All such services are to be paid.

8.5 Login

Login: sa

Password: saAdminR2

22

9 Interfaces

9.1 File interface

The XML-based file interface is described in the document. "MSLExchange_FileInterface".

9.2 SQL Server – Stored procedures

9.2.1 getBarcodeType

Each serially scanned barcode is handled by this procedure. If the return value of barcode type is "unknown", the barcode is compared to the setup

configuration. At the state of software delivery the return value is always = "unknown".

Input parameter

Parameter name Data type Description

BarcodeToCheck varchar(50) Scanned barcode

Returns

SELECT @BarcodeType AS BarcodeType ,@BarcodeValue AS BarcodeValue, @Barcode AS Barcode

Parameter name Data type Description

BarcodeType int Barcode type, for description see refer to comments in the stored procedure

BarcodeValue varchar(50) Esp. For a combined barcode, part of barcode without prefix, suffix etc. This value is saved. If the barcode is not combined, return is equal to "Barcode".

Barcode varchar(50) Scanned barcode, same as input parameter "BarcodeToCheck"