PRISMAaudit Device Manager Version 3.00 Administrator’s...

PRISMAauditDevice ManagerVersion 3.00

Administrator’s Guide

November 2000 Edition

Copyright � Océ Printing Systems GmbH 2000

All rights reserved, including rights of translation, reprinting,reproduction by copying or any other method.

Offenders will be liable for damages. All rights, including rights createdby patent grant or registration of a utility model or design, are reserved.

Delivery subject to availability; right of technical modifications reserved.

U27459-J-Z247-3-7600

Contents

1 Overview........................................................................................................................... 11.1 PRISMAaudit .................................................................................................................. 11.2 PRISMAaudit Device Manager ....................................................................................... 21.3 About this Manual ........................................................................................................... 3

2 Hardware and Software .................................................................................................. 52.1 Software Concept ........................................................................................................... 6

3 First-time Installation of the Device Manager............................................................... 93.1 Installation Checklist..................................................................................................... 113.2 Installing MS SQL Server 7.0 (Phase 1)....................................................................... 123.3 Setting Up the PRISMAaudit Database........................................................................ 213.4 Settings in ODBC ......................................................................................................... 243.5 Installing the Device Manager (Phase 2)...................................................................... 31

3.5.1 Installing BDE ......................................................................................................... 363.5.2 Installing Intel DMI 2.0 ............................................................................................ 343.5.3 Installing the Device Manager ................................................................................ 37

3.6 Settings in the PRISMAaudit Database Assistant (Phase 3)........................................ 433.7 Configuring the Device Manager (Phase 4) ................................................................. 503.8 Deinstalling the Device Manager .................................................................................. 513.9 Visio Link ...................................................................................................................... 52

4 Starting and Operating the Device Manager............................................................... 534.1 Starting the System ...................................................................................................... 534.2 Logging On and Off ...................................................................................................... 54

5 User Administration ...................................................................................................... 575.1 Managing Profiles......................................................................................................... 58

5.1.1 Creating a Profile.................................................................................................... 585.1.2 Editing a Profile ...................................................................................................... 605.1.3 Deleting a Profile .................................................................................................... 60

5.2 Managing Groups ......................................................................................................... 615.2.1 Creating a Group .................................................................................................... 615.2.2 Editing a Group....................................................................................................... 63

U27459-J-Z247-3-7600

5.2.3 Deleting a Group .................................................................................................... 635.3 Managing Users ........................................................................................................... 64

5.3.1 Creating a User ...................................................................................................... 645.3.2 Changing User Data............................................................................................... 665.3.3 Deleting Users ........................................................................................................ 66

5.4 Settings following Installation ....................................................................................... 68

6 Device Manager Administrator .................................................................................... 696.1 Basic Considerations.................................................................................................... 69

6.1.1 The MIF File ........................................................................................................... 696.1.2 Terms Used............................................................................................................ 70

6.2 Device Manager Administrator Interface ...................................................................... 726.2.1 Device Manager Administrator Window ................................................................. 726.2.2 Device Manager Administrator Menus ................................................................... 736.2.3 Functions on the Tabs............................................................................................ 756.2.4 Description of Button Functions ............................................................................. 756.2.5 Online Manual ........................................................................................................ 77

7 Device Types and Devices ........................................................................................... 797.1 Creating a Device Type ................................................................................................ 79

7.1.1 Compiling the MIF File............................................................................................ 827.1.2 Assigning Attributes................................................................................................ 867.1.3 Defining Filters........................................................................................................ 897.1.4 Assigning Icons and Images .................................................................................. 907.1.5 Defining Physical States......................................................................................... 957.1.6 Mapping Physical States to Logical States............................................................. 967.1.7 Assigning the Service State.................................................................................... 997.1.8 Concluding the Process for Creating a Device Type.............................................. 99

7.2 Installing a New Device .............................................................................................. 1007.3 Configuring the DMI Converter................................................................................... 1027.4 Deleting Devices / Device Types................................................................................ 1047.5 Deleting the Attribute History...................................................................................... 105

8 Configuration............................................................................................................... 1078.1 Devices....................................................................................................................... 1078.2 Device Types.............................................................................................................. 109

8.2.1 Changing Icons..................................................................................................... 1108.2.2 Changing the Service State.................................................................................. 1118.2.3 Editing Physical States ......................................................................................... 1128.2.4 Making Mapping Assignments ............................................................................. 113

8.3 Logical States ............................................................................................................. 1178.4 Twin Mode .................................................................................................................. 1198.5 Service........................................................................................................................ 121

U27459-J-Z247-3-7600

8.6 Filter............................................................................................................................ 1228.7 Standard Attributes..................................................................................................... 1288.8 Nodes ......................................................................................................................... 1308.9 Device Configuration .................................................................................................. 1328.10 Visio Link .................................................................................................................. 134

9 Configuration Program ............................................................................................... 1419.1 Entering Parameters................................................................................................... 142

9.1.1 Database .............................................................................................................. 1449.1.2 Converter.............................................................................................................. 1459.1.3 Device Manager Explorer ..................................................................................... 1539.1.4 History Taker ........................................................................................................ 1549.1.5 Statistics ............................................................................................................... 1569.1.6 Traces................................................................................................................... 158

10 Instructions and Actions to take in Event of Errors .............................................. 163

Index ................................................................................................................................ 167

Overview

U27459-J-Z247-3-7600 1

1 Overview

1.1 PRISMAauditPRISMAaudit is a modular solution for managing and controlling the digital workflow and iscompatible with various makes of equipment.

The following figure shows the PRISMAaudit components:

This Administrator's Guide describes the PRISMAaudit Device Manager (DM).

Overview

2 U27459-J-Z247-3-7600

First, a brief word on the various components of Océ PRISMAaudit:

The Océ PRISMAaudit TM Systems Manager monitors the entire productionworkflow. It operates by means of predefined check points, which enable it totrack every single document.

The Océ PRISMAaudit TM Reprint Manager ensures that damaged or illegibledocuments are automatically reprinted.

The Océ PRISMAaudit TM Print Manager helps operators in their work with jobsand printers under MVS. There is a convenient GUI interface with point-and-clickfunctions, which helps prevent input errors.

The Océ PRISMAaudit TM Verification Manager monitors the print quality of thedocuments.

The Océ PRISMAaudit TM Enterprise Resource Manager is a production planningand material management utility for the production centre.

The Device Manager is a tool that you can use to detect technical weaknessesand flaws in the organisation of the production process. The data that is collectedrelating to capacity utilisation, the temporal distribution of the workload and thestates of devices is the basis for initiating targeted measures to correct the weakpoints.

1.2 PRISMAaudit Device Manager

The task of the Device Manager is to collect the machine data in the production centre. Itevaluates this data and provides statistics.

Functions− Modular and scalable system based on a shared SQL database. This provides a

central data repository, central evaluation, search and archiving of all the availablemachine data.

− Central MDA (machine data acquisition) for all the devices on the production lines inthe print and mailing centre.

− Central and decentral representation of current device states in views that can becustomised by users.

Overview

U27459-J-Z247-3-7600 3

− Standard evaluations such as utilisation statistics, error and performance statisticsrelating to all the devices being monitored.

− Possibility of exporting data and evaluations to external systems such as MS Excel.

1.3 About this ManualTarget Group

This manual is for all users of the Device Manager who wish to obtain an overview of thesystem in order to work with the Device Manager.

For your convenience, the following conventions and symbols are used in thismanual.

Convention/Symbol Description

Italics The names of tabs, dialog boxes, windows and fields areprinted in italics.

<Angle brackets> The names of buttons are preceded and followed by anglebrackets.

NoteNotes appear as displayed at left. You should always readthe notes because they contain important information.

1st step ”How to" instructions, for example, steps you have to takewhen filling out a tab, are shown as a numbered list.

The manual also includes a table of contents and an index.

You can also display this manual online when you are working with the Device Manager.For details, refer chapter 6.2.5 "Online Manual", page 77.

How the manual is organised

Chapter 1 contains a brief introduction to the Device Manager and explains the structureand contents of this manual.

Chapter 2 describes the required hardware and software.

Chapter 3 describes the installation procedure.It is important to check the requirements and have the requisite informationon hand before beginning work. See also Chapter 3.1 “Installation Checklist“,page 11.

Overview

4 U27459-J-Z247-3-7600

Chapter 4 explains the basic principles for launching and working with the DeviceManager.

Chapter 5 describes procedures for managing users.

Chapter 6 describes the user interface of the Device Manager Administrator, introducingthe basic elements of the interface.

Chapter 7 explains how to set up (install) new device types and devices.

Chapter 8 describes how to configure devices.This chapter describes the steps you need to complete in order to have theDevice Manager monitor your devices. Chapter 8 describes the commands inthe order they appear in the Device Manager Administrator menus, and ischiefly intended for reference. You should read Chapter 7 before you set up adevice for the first time.

Chapter 9 describes the configuration program, which you use to set parameters for theDevice Manager.

Chapter 10 contains notes on troubleshooting.

Hardware and Software

U27459-J-Z247-3-7600 5

2 Hardware and SoftwareThe figure below shows the architecture of the Device Manager:

The Device Manager enables you to monitor devices such as printers and inserters.

The Device Manager and the devices it monitors exchange information by way ofconverters.


6 U27459-J-Z247-3-7600

2.1 Software ConceptThe Device Manager is subdivided into

− Clients− Database− Processes− Components

The client is your desktop PC. You use this PC to work with the Device Manager.

The Device Manager is implemented as an SQL database application (type: MS-SQL).The database contains all the information relating to the Device Manager.

The Device Manager works with the two processes DMI Converter and History Taker.

DMI Converter

Devices monitored by the Device Manager deliver their information to the Device Managervia DMI (Desktop Management Interface). If a device does not support DMI, a converterhas to be connected between the device and the Device Manager to convert theinformation to DMI format.

History Taker

The History Taker is a utility installed in Windows NT. The main task of the History Takeris to collect information about the devices connected to the system. This information isstored in the PRISMAaudit database and can be used for evaluation.

Components of the Device Manager

The Device Manager consists of the following components:

− Device Manager Administrator− Device Manager Explorer− Device Manager Data Fetcher− Device Manager Configuration− DB Assistant


U27459-J-Z247-3-7600 7

Device Manager Administrator

The Device Manager Administrator serves to

− map physical states according to device type to logical states and colours,

− assign names to devices according to their configuration,

− define twin configurations,

− define device types and devices and

− delete data.

Device Manager Explorer

The Device Manager Explorer provides graphical user interfaces in order to

− configure devices with their respective properties in the Device Manager,

− display devices in colours that match their operating states,

− generate statistics and export them to other applications for further processing.

Device Manager Data Fetcher

The Device Manager Data Fetcher is a utility to collect statistical information about devicesand export this information to other applications for further processing.

Device Manager Configuration

Processing with the Device Manager can be controlled by parameters. The configurationprogram is a convenient way of creating, modifying and deleting these parameters.

DB Assistant

You use the Database Assistant to establish the connection with the PRISMAauditdatabase and to configure the tables for the Device Manager.

Installation

U27459-J-Z247-3-7600 9

3 First-time Installation of the Device ManagerThis chapter summarises the tasks you perform to install the Device Manager, and shouldbe read by every user who intends to perform a first-time installation.You will find the checklist in Chapter 3.1 useful in preparing for the installation.The installation of the Device Manager comprises four phases:– Phase 1: Install MS SQL Server 7.0– Phase 2: Install the Device Manager– Phase 3: Make entries in the Database Assistant– Phase 4: Make entries in the Device Manager configuration program

The figure below summarises the installation procedure.

Installation

10 U27459-J-Z247-3-7600

Phase 1

Phase 2

Phase 3

Phase 4

Requirements

The prerequisites for the installation are:

– The operating system is already installed– The network is configured

Procedures

As a rule, the installation is a four-phase process:

Phase 1:

The PRISMAaudit database requires the program MS SQL Server 7.0. You must installthis software if you have not already done so. The entries you have to make forPRISMAaudit are described in Chapter 3.2 “Installing MS SQL Server 7.0”,page 12.

Installation

SQL Server 7.0

PRISMAaudit DB ODBC

Intel DMI Device Manager BDE

DB Assistant

DM Configuration

DM Administrator DM DataFetcherDM Explorer

Installation

U27459-J-Z247-3-7600 11

Once you have installed MS SQL Server 7.0, you can set up the PRISMAaudit databasewith the SQL Enterprise Manager (see page 21), and make the appropriate entries inODBC (see page 24).

Phase 2:

This phase begins the actual installation of the Device Manager. It comprises three steps:– Installing Intel DMI 2.0 (see Chapter 3.5.1 “Installing Intel DMI 2.0”, page 34)– Installing BDE (see Chapter 3.5.2 “Installing BDE”, page 36)– Installing Device Manager (see Chapter 3.5.3 “Installing DeviceManager”, page 37)

Phase 3:

With the help of the database assistant, you establish the connection to the PRISMAauditdatabase and configure the tables for the base system and Device Manager (see Chapter3.6 “Settings in the PRISMAaudit Database Assistant”, page 43).

Phase 4:

In the last phase, you make your entries in the Device Manager configuration program(see Chapter 9 “Configuration Program”, page 141).

Phases 1 to 3 are described in detail in the sections that follow. Phase 4 is described inChapter 9.

3.1 Installation ChecklistYou should be prepared to answer a few questions during the installation process. Thechecklist gives the questions which the installation program will ask you. By filling in thetable before beginning the installation, you will have the correct entries on hand when theyare needed. One filled in, the list is also useful when re-installing or updating the program.

Checklist

Question Entry

SQL server − User name and password − Licensing mode

PRISMAaudit database − Database name

Installation

12 U27459-J-Z247-3-7600

Question Entry

ODBC − Name − Server − Login

Device Manager − Path − Components − Server − Database − Database authorisation

ID and password for all PCs in thePRISMAaudit system

Name and/or IP address for serversand converter PCs

ID and password for PRISMAaudituser

3.2 Installing MS SQL Server 7.0 (Phase 1)Phase 1 (see figure on page 10) involves installing MS SQL Server 7.0, setting up thePRISMAaudit database and making the requisite entries in ODBC.

Install MS SQL Server 7.0 from the supplied CD-ROM, referring to the Microsoft SQLServer 7.0 documentation. The following windows show the settings that are important forPRISMAaudit.

This is how you install MS SQL Server 7.0 on the Windows NT server:

1. Launch Windows NT and insert the installation CD in the CD-ROM drive.

Installation

U27459-J-Z247-3-7600 13

The system launches the CD-ROM and opens the following window.

2. Choose Install SQL Server 7.0 Components.

The system will display the window shown on the next page.

Installation

14 U27459-J-Z247-3-7600

3. In the above window, select Database Server - Standard Edition.


Installation

U27459-J-Z247-3-7600 15

4. Select the installation method Local Install - Install to the Local Machine and click<Next>.

The system searches for installed components and will then display the window on thefollowing page.

Installation

16 U27459-J-Z247-3-7600

5. Read and observe the information in the above window and click <Next>.

The system displays further windows about the license agreement and other items.

You do not need to make any further choices until the window shown on the followingpage appears.

Installation

U27459-J-Z247-3-7600 17

6. Select the Typical setup, read the other information and then click <Next>.


Installation

18 U27459-J-Z247-3-7600

7. Leave the settings selected in the window above and enter your password.

8. Click <Next>.

9. Confirm the next window with <OK>.


Installation

U27459-J-Z247-3-7600 19

10. Read and observe the information and click <Next>.


Installation

20 U27459-J-Z247-3-7600

You have to restart your PC in order to effect the changes that have been made due tothe installation.

11. Check Yes, I want to restart my computer now and click <Finish>.

The PC is restarted.

Installation

U27459-J-Z247-3-7600 21

3.3 Setting Up the PRISMAaudit DatabaseAn empty or operational PRISMAaudit database must exist in order for you to install theDevice Manager.

This is how you create the PRISMAaudit database:

1. Launch the SQL Enterprise Manager.

2. Select Databases and click the right mouse button.

3. Choose New Database from the shortcut menu.

The system will display the dialog box shown on the next page.

Installation

22 U27459-J-Z247-3-7600

4. Enter the database name in the Name field (for example domain).

5. Make the settings as shown in the figure above and confirm with <OK>.

The system will store the settings.

Installation

U27459-J-Z247-3-7600 23

6. The displayed configuration of the SQL Server is recommended. For details see SQLdocumentation.

Installation

24 U27459-J-Z247-3-7600

3.4 Settings in ODBCThe settings in ODBC establish the connection to an SQL server.

This is how you make the settings in ODBC:

1. Click the <Start> button and choose Settings → Control Panel → ODBC-DataSources.

The system opens the ODBC Data Source Administrator dialog box.

2. Click the tab labelled System DSN.

The system will display the options shown below:

3. Click <Add>.


Installation

U27459-J-Z247-3-7600 25

4. In this window, choose SQL Server and click <Finish>.


Installation

26 U27459-J-Z247-3-7600

5. Enter a name (DSN name) and choose the server you want to connect to.

Note: The entry you make here must be identical with the one in the DeviceManager configuration program (see also Chapter 9.1.1 “Database”, page144).

6. You can enter a brief text in the Description field.

7. Click <Next>.


Installation

U27459-J-Z247-3-7600 27

8. Leave the defaults as shown in the window above and enter the password for thedatabase.

9. Click <Next>.

The system will display the window shown on the following page.

Installation

28 U27459-J-Z247-3-7600

10. Check the Change the default database to option and choose Domain from the list.

11. Click <Next>.


Installation

U27459-J-Z247-3-7600 29

12. Check the settings in the above dialog box (none of the options should have a checkmark against them) and click <Finish>.


Installation

30 U27459-J-Z247-3-7600

13. Check the information shown in the dialog box, then click <Test Data Source> orconfirm right away by clicking <OK>.

The system will store these settings.

Installation

U27459-J-Z247-3-7600 31

3.5 Installing the Device Manager (Phase 2)Phase 2 (see figure on page 10) comprises the installation of the Device Managerincluding the programs BDE (Borland Database Engine) and Intel DMI 2.0 (ServiceProvider).

The Device Manager ships in the form of an installation package on CD-ROM. There is aspecial menu-driven installation utility. The utility prompts you to make the requisitesettings for the installation.

The package comprises the following programs:

– Intel DMI 2.0 (Service Provider)

– DMVmmmmmmDnnnnnn (Device Manager)

mmmmmm: Version number nnnnnn: Date

Note: The program Intel DMI 2.0 Service Provider is required for the DeviceManager, so you have to install these first.

The Device Manager consists of the following components:

– Converter– Server (History Taker)– Client– Database– VisioYou can choose to install some or all of these components.

Converter

Installation of the DMI Converter.

Server

Installation of the History Taker. This step also installs the SQL scripts and MIF files.

Client

Installation of the programs Device Manager Administrator, Device Manager Explorer andDevice Manager DataFetcher. The bitmaps (icons representing devices) are also installed.

Installation

32 U27459-J-Z247-3-7600

Database

Installation of the database assistant.

The following tasks are also installed:

– Clear HistoryThis task checks whether the database contains any entries that are more than a yearold. These entries are deleted. Name: clear history

– Update DM StatisticsThis task optimises the displays of the Device Manager statistics. With the defaultsetting, this task is launched every day, at eight hour intervals. You can change this timesetting if you wish. Name: update statistics

– Check DB FilesThis task checks that there is always at least 230 KB of memory free. If the freememory drops below this threshold, a message is written to the log file. With the defaultsetting, this task is launched every day, at eight hour intervals. You can change this timesetting if you wish. Name: check db size

Visio 2000

Installation of Visio 2000.

Installation

U27459-J-Z247-3-7600 33

The table below shows which components/programs have to be installed on the variouscomputer systems.

Used onComponentConverterPC

Processserver

Databaseserver

Client

MS SQL Server 7.0 xODBC 3.0 (3.5) x x x xBDE xIntel DMI 2.0 x xDM Converter (or third partyconverter)

x

DM History Taker xDevice Manager DM Administrator DM Explorer DM Data Fetcher

x

DM Configuration x x xDatabase x

Note: You can also choose to install the Device Manager on the process serverand/or database server. You then have the possibility of performing admintasks on these servers as well – recommended in the interest of backup andsecurity.

You can install all the components on the same computer system. The abovetable shows the maximum distribution.

For details on how to install MS SQL see Chapter 3.2 “Installing MS SQL Server 7.0(Phase 1)”, page 12.

The settings you have to make for ODBC are given in Chapter 3.4 “Settings in ODBC”,page 24.

For details on how to install BDE and Intel DMI see Chapters 3.5.2 “Installing BDE”, page36, and 3.5.1 “Installing Intel DMI 2.0”, page 34.

Information about the Converter, the Device Manager History Taker and the variousDevice Manager components is given in Chapter 3.5.3 “Installing the Device Manager”,page 37.

The database component is dealt with in Chapter 3.6 “Settings in the PRISMAauditDatabase Assistant (Phase 3)”, page 43.

Installation

34 U27459-J-Z247-3-7600

3.5.1 Installing Intel DMI 2.0

This is how you install Intel DMI 2.0 from the Device Manager installation CD:

1. Select Intel DMI 2.0 and then Dmtf.

2. Select SDK Intel and then Intel DMI 2.0 Service Provider SDK Version 1.10.

3. Double-click the program dmi2sdk.exe.

The system starts the installation and displays the following window:

4. Read and observe the information in the above window and then click <Next>.


Installation

U27459-J-Z247-3-7600 35

5. Leave the settings as they are and click <Next>.

This completes the installation of the Intel DMI 2.0 program.

The system has created a program group called Intel Installation. This is displayedwhen you click the <Start> button and choose Program Files → Intel DMI 2.0 SP SDKv1.10.

Installation

36 U27459-J-Z247-3-7600

6. Check that the window on your screen contains the line highlighted under Services inthe figure below.

Click the <Start> button and choose Settings → Control Panel and then Services.

The system will display the following window:

If the highlighted line is shown, the Intel DMI 2.0 Service Provider has been installedcorrectly.

3.5.2 Installing BDE

BDE will be installed automatically.

Installation

U27459-J-Z247-3-7600 37

3.5.3 Installing the Device Manager

When you have installed Intel DMI 2.0 Service Provider, the installation procedure showsthe following window:

The system proposes a folder for the installation of the Device Manager.

1. Either confirm the suggestion or select a different folder. Then click <Next>.


Installation

38 U27459-J-Z247-3-7600

When this window opens, all the Device Manager components are selected forinstallation (as shown above). You can install some or all of the components.

Note: See the table on page 33 for details about which components to install onwhich system.

2. Deselect the components you do not want to install and then click <Next>.

3. Click <Next>.


Installation

U27459-J-Z247-3-7600 39

4. Enter the names of the server and database.

You assigned the database name when you created the database (see Chapter 3.3“Setting Up the PRISMAaudit Database”, page 21).

5. Click <Next>.


Installation

40 U27459-J-Z247-3-7600

6. Enter the user ID and the password for the database.

7. Enter the password again in the Confirm field and then click <Next>.


Installation

U27459-J-Z247-3-7600 41

8. You do not have to make any entries in the above window. Click <Next> to continuethe installation.

The system completes the installation and then opens the window shown on the nextpage.

Installation

42 U27459-J-Z247-3-7600

You have to restart your PC to put the installation settings into effect.

9. Accept the default setting, Yes, I want to restart my computer now and click <Finish>.

This completes the installation procedure. However, before you can begin work withthe Device Manager, you have to make certain settings in the PRISMAaudit databaseassistant (see Chapter 3.6 “Settings in the PRISMAaudit Database Assistant”, page43).

Installation

U27459-J-Z247-3-7600 43

3.6 Settings in the PRISMAaudit Database Assistant (Phase 3)In phase 3 (see figure on page 10) you make the settings in the PRISMAaudit databaseassistant.

Use the database assistant to:

– establish the connection with the PRISMAaudit database and– configure tables for the base system and the Device Manager.

The base system contains the tables for user administration.

The database assistant is installed if you elected to install the Database component for theDevice Manager (see also page 38).

This is how you make the settings:

1. Double-click the database assistant icon.

The system will display the following dialog box:

2. Select the Device Manager component and click <OK>.


Installation

44 U27459-J-Z247-3-7600

The first step is to establish the connection with the PRISMAaudit database.

1. Click the tab labelled DB Connection and click <Connect to database>.


Note: If you have assigned a database name in the DM Configure, the connectionwill be established with the database. The following dialog box will notopened.

Installation

U27459-J-Z247-3-7600 45

2. On the tab labelled Machine Data Source, select the database configured forPRISMAaudit and click <OK>.


Installation

46 U27459-J-Z247-3-7600

3. Enter the database user ID in the Login ID field and enter the password in thePassword field.

4. Click <OK>.


This window shows the entries you have made so far. The display is for informationpurposes.

The next step is to configure the tables for the base system. The base system contains thetables for user administration.

1. In the database assistant, click the tab labelled Base System.


Installation

U27459-J-Z247-3-7600 47

2. If this is the first installation, check the Base System tables CREATE option and thenclick <Apply>.

The system notifies you that existing tables, even those of other PRISMAauditManagers, will be overwritten and creates the tables for the base system.

Installation

48 U27459-J-Z247-3-7600

Note: The installation procedure creates these default users:– administrator OPS Administrator profile– operator operator Operator profile– supervisor supervisor Super profile– gast gast Guest profile– manager manager Super profile

The passwords are case-sensitive.

Create a few users in the Device Manager Administrator (see Chapter 5"User Administration”, page 57).

Installation

U27459-J-Z247-3-7600 49

Finally, you have to create the tables for the Device Manager.

1. In the database assistant, click the tab labelled Device Manager.


2. If this is a new installation, check the Device Manager tables CREATE option and click<Apply>.

The system creates the tables.

This completes the entries in the database assistant.

Installation

50 U27459-J-Z247-3-7600

3.7 Configuring the Device Manager (Phase 4)Phase 4 (see figure on page 10) entails making entries in the Device Managerconfiguration program.

After completing phases 1 to 3 you can launch the Device Manager. The system will havecreated the following icons on your desktop:

– Device Manager Administrator– Device Manager Explorer– Device Manager DataFetcher– Device Manager Configuration– DBAssistant (if selected for installation)

The program group called Océ PRISMAaudit Device Manager has also been created.(<Start> button → Program Files → Océ PRISMAaudit Device Manager).

If you now launch the Device Manager Explorer, you will see that the evaluations areempty because you have not yet defined any devices. The procedure for defining devicesis described in Chapter 7 “Device Types and Devices”, page 79.

Installation

U27459-J-Z247-3-7600 51

3.8 Deinstalling the Device ManagerA deinstallation utility is always installed for the Device Manager, irrespective of whichcomponents you have chosen to install on the system. For example, you should deinstallthe Device Manager before installing a new version of the software.

How to Remove the Program

This is how you deinstall the Device Manager:

1. Click the <Start> button, choose Settings → Control Panel and then Add/RemovePrograms.


Installation

52 U27459-J-Z247-3-7600

2. Select the entry Océ PRISMAaudit Device Manager and click <Add/Remove>.

The system removes all the programs that are part of the Device Manager.

Note: The deinstallation process always removes all the components of the DeviceManager. It is not possible to remove individual components.

3.9 Visio LinkThe following entries are required in the registry for the Visio link, which enables Visio tolaunch from the Device Manager:

VisioEnabled: digit (1 enabled, 0 not enabled)

VisioFile Visio file, full path name (see page 153)

VisioMarker Additional text to be shown in the refresh window

The Visio shapes are identified by way of the device names as entered in the DeviceManager. These names have to be entered as properties in the Visio drawing object.

Visio and the Device Manager communicate via OLE automation.

Logging On and Off

U27459-J-Z247-3-7600 53

4 Starting and Operating the Device ManagerThis chapter describes what you have to do to make the Device Manager operational. Youneed special access rights to perform the tasks described in this chapter.

4.1 Starting the System

Starting the Database Server

This is how you start the database server:

1. Press the power switch on the PC (the green light comes on).

The computer boots up and loads the operating system. Loading can take severalminutes.

When the operating system is loaded, the Windows NT startup window displays. Adialog box requires you to log in.

2. Press the Ctrl+Alt+Del key combination.

The system displays a dialog box for entering a user name and password.

3. Enter the user name and password.

Starting the Process Server

The following process has to be running on the process server for the Device Manager tooperate:

− History Taker

This is how you start the process server:




Logging On and Off

54 U27459-J-Z247-3-7600




After you have successfully logged in, the processes of the Systems Manager appearas icons on the screen.

Database Connection

The first time you launch the Device Manager you may also have to configure thedatabase connection.

4.2 Logging On and Off

Starting the Operator PC (Device Manager client)

This is how you start the operator PC:




Logging On and Off

U27459-J-Z247-3-7600 55




After you have successfully logged in, the Device Manager Explorer and the DeviceManager Administrator appears on the screen as icons.

Double-click the icon to launch the Device Manager Explorer / Administrator.

The Device Manager Explorer / Administrator displays the interface foroperators/administrators.

This is how you log on the Device Manager:

1. Double-click the Device Manager program icon.


2. Enter your user ID (in the User Name field) and your password.

The system will display the main window of the Device Manager (see Chapter 6.2.1"Device Manager Administrator Window", page 72).

Note: The system issues a message if you make a mistake typing in your username or password. Confirm the message and enter the correct values.

Logging off from the Device Manager

This is how you log off from the Device Manager:

1. On the menu bar, choose File → Exit.


Logging On and Off

56 U27459-J-Z247-3-7600

2. Click the <Yes> button.

This closes the Device Manager on your PC.

User ID and Password

You need a user ID and password to work with the Device Manager. The systemadministrator assigns user IDs to the different users, and also the respective accessauthorisations (see Chapter 5 "User Administration", page 57). Refer to Chapter 5.4"Settings following Installation" for a list of the default access rights assignments.



Create a few users in the Device Manager Administrator (see Chapter 5“User Administration”, page 57).

User Administration

U27459-J-Z247-3-7600 57

5 User AdministrationThis chapter describes how to manage (administer) users with PRISMAaudit. Beforedefining new users, profiles or groups, you should read this chapter to familiarise yourselfwith the basic concept.

User administration is a component that is used by all the PRISMAaudit managers. Youuse this component to define which PRISMAaudit users have which access rights to whichPRISMAaudit managers. The access rights – or authorisations – are implemented by wayof profiles, groups and users. Your first step when you begin work with the useradministration is to create the profiles. You next define the groups and lastly the users.

The Device Manager is installed with the default profile NOPROFILE and the groupNOGROUP. This group is assigned the profile NOPROFILE. NOPROFILE does not haveany access authorisations when it is installed, so nor does NOGROUP. Consequently, ifyou create a new user directly after the installation and assign the user to NOGROUP, theuser will not have any access rights. If you launch the Device Manager with the new user’slogin, the program will start but none of the functions will be available. You can make thefunctions accessible for the new user either by modifying NOPROFILE, or by creating anew profile of your own. You then assign this profile to a group and change the groupaffiliation of the user.

This interrelation is the reason why you have to create the items in a certain order: first theprofile, then the group, then the user.



User Administration

58 U27459-J-Z247-3-7600

5.1 Managing ProfilesA profile is a definition of access rights for a PRISMAaudit manager, in this case theDevice Manager. In the profile, you define which access rights are valid for the selectedmanager. There are functions for creating, editing and deleting profiles.

5.1.1 Creating a Profile

This is how you create a profile:

1. On the menu bar, choose Configure → Users or click on the toolbar.

The system opens the following window:

2. Click the right mouse button in the Profiles list and choose New Profile from theshortcut menu.

The system opens the following dialog box:

User Administration

U27459-J-Z247-3-7600 59

3. Enter the name of the user profile.

4. Select the component for which these access privileges apply (here the DeviceManager).

The system displays the possible access privileges.

5. Select the privileges that you want to assign to the user profile.

6. If you wish to define access privileges for a further PRISMAaudit component, selectthis component and repeat steps 4 to 6.

7. Click <OK>.

The system closes the dialog box. The new user profile is now registered in thePRISMAaudit user administration.

User Administration

60 U27459-J-Z247-3-7600

5.1.2 Editing a Profile

You can change the assignment of access rights in an existing profile.

This is how you edit a profile:


The system will open the window depicted on page 58.

2. Select the profile you want to edit and press the right mouse button.

3. Choose Edit Profile from the shortcut menu.


4. Enter your changes.

You can change the access rights in this profile for all the PRISMAaudit managers.You can add rights and/or deactivate them.

5. Click <OK>.

The system stores the changed profile in the PRISMAaudit user administration.

5.1.3 Deleting a Profile

Note: You cannot delete a profile without first cancelling its assignments to groups.Check whether the assignments are still in use. If necessary, assign adifferent profile to the group concerned, and then delete the profile.

This is how you delete a profile:

1. On the menu bar, choose Configure → Users or click on the menu bar.


2. Select the profile you want to edit and press the right mouse button.

3. Choose Delete profile from the shortcut menu.


User Administration

U27459-J-Z247-3-7600 61

4. Click <OK> to delete the profile.

The system removes the profile from the PRISMAaudit user administration.

5.2 Managing GroupsA group creates the link between the users and the access authorisations. There must bea profile assigned to a group. This affiliation gives the group the access rights defined inthe profile. There are functions for creating, editing and deleting groups.

5.2.1 Creating a Group

This is how you create a group:



User Administration

62 U27459-J-Z247-3-7600

2. Click the right mouse button in the Groups list and choose New Group from theshortcut menu.


3. Enter the name of the user group.

4. Select the user profile that you want to assign to this group.

5. In the Other Users list select all the users whom you want to assign to this group.

6. Click <<Insert<<.

The selected users are assigned to the user group. They receive the access privilegesdefined by the user profile.

7. Click <OK>.

The system closes the dialog box. The user group is now registered in thePRISMAaudit user administration.

User Administration

U27459-J-Z247-3-7600 63

Note: Consider that a user can only belong to one user group. When you assign auser to a group using the <<Insert<< function, the system deletes the existingassignment of this user to another group. For example, if a user has up tonow belonged to the group AdmGroup and you assign the user to groupGuestGroup, the user will then only belong to GuestGroup. Accordingly, theuser will also only have the access rights of this group.

5.2.2 Editing a Group

This is how you edit a group:

1. On the menu bar, choose Configure → Users or click .


2. Select the group you want to edit and press the right mouse button.

3. Choose Edit Group from the shortcut menu.

The system will open the window depicted on the previous page.

4. Enter your changes.

You can assign a different profile to the group, and/or assign different users to thegroup.

5. Click <OK>.

The system stores the changed group in the PRISMAaudit user administration.

5.2.3 Deleting a Group

Note: You cannot delete a group if any users still belong to it. Check whether thegroup is still in use. If necessary, change the assignments, and then deletethe group.

This is how you delete a group:

1. On the menu bar, choose Configure → Users or click on the menu bar.


2. Select the group you want to edit and press the right mouse button.

User Administration

64 U27459-J-Z247-3-7600

3. Choose Delete Group from the shortcut menu.


4. Click <OK> to delete the group.

The system removes the group from the PRISMAaudit user administration.

5.3 Managing UsersA user is always assigned to a group. This affiliation gives the user the access rights of thegroup. The group, in turn, is assigned a profile in which each of the access authorisationsare defined, e.g. the authorisation to generate error statistics.

Note: Bear in mind that a user can only be assigned to one group at a time – if youchange the affiliation, the access rights of the user will also change.

5.3.1 Creating a User

This is how you configure settings for user administration:



User Administration

U27459-J-Z247-3-7600 65

2. Click the right mouse button in the Users section and choose New User.


3. Enter the name of the user.

Once you have saved the data with <OK> you will no longer be able to change thename.

4. Assign a password, and re-enter the password in the PWD Confirm field.

5. Select the group to which you want to assign the new user.

This group affiliation determines which access rights the user will have.

6. Click <OK>.

The system registers the new user in the PRISMAaudit user administration.

User Administration

66 U27459-J-Z247-3-7600

5.3.2 Changing User Data

This is how you change the data of a user:


The system will open the window depicted on the previous page.

2. Select the name of the user whose data you want to change and either double-clickthe right mouse button, or click once and choose Edit User.


3. Check all the user data displayed in the dialog box and make changes if necessary.

You can change the password and assign the user to a different group. Bear in mindthat by changing the group affiliation you will also assign the user a different set ofaccess rights.

4. Click <OK>.

The system registers the changes in the PRISMAaudit user administration.

5.3.3 Deleting Users

This is how you delete a user:



2. Select the user name. Click the right mouse button and choose Delete User.

The system asks you to confirm the delete operation:

User Administration

U27459-J-Z247-3-7600 67

3. Click <OK>.

The system removes the user from the user list and therefore also from the usergroup.

User Administration

68 U27459-J-Z247-3-7600

5.4 Settings following InstallationFollowing installation, the Device Manager access rights are allocated as shown in thetable below. The Administrator’s Guide explains how to adapt user administration settingsto specific requirements.

Access right Administrator Shift Manager Operator Guest ManagerConfigure device types X - - - -Configure devices X - - - -Launch statistics X X - - XLaunch error statistics X X - - XLaunch utilization statistics X X - - XDefine time periods for statistics X X - - XDetail view for devices X X X - XDefine device groups X X X - XSelect history attributes X - - - -Configure devices X - - - -Delete devices X - - - -Set up device types X - - - -Delete device types X - - - -Set TWIN mode X - - - -Create configuration table (“PRT41,PRT51, PRT61”)

X - - - -

Set/terminate service state X - - - -Set mapping of logical to physicalstates

X - - - -

Edit filters X - - - -Set refresh interval X X X - XAssign standard attributes X - - - -Set up converter PC nodes X - - - -Define users X - - - -Define profiles X - - - -Define user groups X - - - -Assign (user) names X - - - -Start Device Explorer X X X X XView device status X X X - XView device group X X X - XView device group – which devices arein group

X X X - -

Delete device groups X - - - -Create device group X - - - -

Administration

U27459-J-Z247-3-7600 69

6 Device Manager AdministratorThe Device Manager Administrator provides functions for defining device types anddevices in the Device Manager and for configuring your Device Manager system.

The terms explained in Chapter 6.1 are important for understanding Chapters 7 and 8.Chapter 6.2 explains the basic elements of the user interface.

6.1 Basic Considerations

6.1.1 The MIF File

What is a MIF file?

MIF stands for Management Information Format. A MIF file is an ASCII text file. This filecontains the description of the device properties. A MIF file specifies the device type. Thespecification is subdivided into groups, and each group is subdivided into attributes.

Basic configuration of a MIF file:

Device type

→ Attribute Groups

→ Attributes

There must be a MIF file for every device type installed. If you install a new device type inthe system, you have to assign a dedicated MIF file explicitly to this new device type (seeChapter 7.1 "Creating a Device Type", page 79).

Administration

70 U27459-J-Z247-3-7600

6.1.2 Terms Used

Physical State

Every device type can be in one of several physical states. You have to register thesestates in the Device Manager.

For Océ printers the following physical states are defined in the system:

Standby-ReadyReadyPaper InsertPreparationServiceClean StopPre/Post Device StopPrinter not readyTWIN StopOperational Stop

Logical State

Logical states are defined via physical states and filters. This reduces the amount ofinformation to an essential minimum. The operator can then see at a glance whether adevice is working, halted or not connected. It is also possible to collect data for statisticsfor predefined states or accumulated states.

The following logical states are defined in the system:

UnknownOperational StopPre/Post Proc.StopErrorReadyRunningService

You can include new physical and logical states and make new assignments (see Chapter8.3 “Logical States”, page 117, 8.2.3 “Editing Physical States”, page 112 and 8.2.4 “MakingAssignments”, page 113).

Administration

U27459-J-Z247-3-7600 71

Filters

Filters make it possible for you to consolidate errors in groups.

The following filters are defined by default for Océ printers, for example:

F01 Operator interventionF02 Error in pre/postprocessingF03 Device error

You can define new filters (see Chapter 8.6 "Filter", page 122).

When you evaluate the errors, you can define filters to determine which error statistics areobtained (Refer to Chapter 8.6 "Filter", page 122 for an example).

Attribute

The attributes are used as a means of defining which data is to be stored and evaluated.The most important attributes are defined as standard attributes. You have to edit thesestandard attributes, i.e. you have to assign them a DMI attribute (see Chapter 8.7“Standard Attributes”, page 128).

Administration

72 U27459-J-Z247-3-7600

6.2 Device Manager Administrator Interface

6.2.1 Device Manager Administrator Window

When you start the Device Manager Administrator, the system will display the followingwindow:

Administration

U27459-J-Z247-3-7600 73

Elements of the main window:

The window consists of a title bar, a menu bar, a toolbar, a data section and statusbar.

The title bar contains the program name – PRISMAaudit Device Manager – and yourlogon name.

The menu bar contains the Device Manager Administrator menus. These are described inChapter 6.2.2.

The buttons on the toolbar are an alternative way of accessing certain menu commands.The buttons are described in Chapter 6.2.4 "Description of Button Functions", page 75.

The data section contains nine tabs. You bring a tab to the front of the window by clickingits title (see Chapter 6.2.3 “Functions on the Tabs”, page 75).

The status bar displays information about the entries which are currently selected andindicates the proportion of the database that is already occupied by data.

6.2.2 Device Manager Administrator Menus

The menus are accessed from the menu bar. A menu contains commands that enable youto execute particular actions.

The Device Manager Administrator has the following menus:

• File

• Configure

• View

• ?

File

The File menu contains the command Exit, which you use to log off the Device ManagerAdministrator.

Configure

The Configure menu contains the following commands:

− Install new Device type− Install new Device− Clear Devices/Device types− Clear Attribute History− Users

Administration

74 U27459-J-Z247-3-7600

These menu commands, excepting for the User commands, are described in Chapter 8“Configuration”, page 107. The User menu is described in Chapter 5 “User Administration”,page 57.

View

The View menu contains the following commands:

− Toolbar− Status bar− Refresh

Toolbar

The toolbar gives you instant access to frequently used functions (see Chapter 6.2.4,“Description of Button Functions”, page 75). If you do not want to work with the buttons,you can turn the toolbar off. Normally, the toolbar is displayed (default setting). Thecommand in the menu then has a check mark preceding it.

Status bar

The next-to-last line on the screen is the status bar. The status bar indicates if there is aconnection to the PRISMAaudit database, for example. You can turn off the status bar ifyou want. Normally, the status bar is displayed (default setting). The command in themenu then has a check mark preceding it.

Refresh

If you load data and leave it for a period of time without doing any editing, you shouldrefresh the data before continuing work. This is to make sure you will be working with thelatest data.

?

This menu contains the following commands:

− About− Help

About

Choose this command to display the version number of your Device Manager installation.

Help

Use Help to open the Device Manager documentation.

Administration

U27459-J-Z247-3-7600 75

6.2.3 Functions on the Tabs

The Device Manager Administrator window contains nine tabs:

Devices Use this tab to define the device names.

Device Types Use this tab to edit the physical states and assignments.

Twin Mode Functions for configuring printers for twin mode.

Service Functions for entering service times.

Filter Functions for defining error filters.

Standard Attributes Use this tab to define the data that is to be evaluated.

Nodes Define the converter PC.

Logical States Use this tab to view and edit logical states.

Device Configuration Use this tab to make device configuration settings.

The tabs are described in detail in Chapter 8 “Configuration”, page 107.

6.2.4 Description of Button Functions

Some Device Manager Administrator dialog boxes include the following control buttons.Their function is the same in every dialog box.

Control buttons:

Insert one line

Delete one line

Edit line

Save

Delete

Refresh data

Administration

76 U27459-J-Z247-3-7600

The toolbar in the Device Manager Administrator contains the following icons:

Define a new device type

Define a new device

Delete devices or device types

Delete attribute history

User administration

Refresh data

Database symbol

The symbol on the right indicates whether or not there is a connection to the PRISMAauditdatabase.

When the symbol is green, a connection has been established to the PRISMAauditdatabase; when the symbol is red, there is no connection. If this happens, checkwhy this is the case or consult your system administrator if necessary. The systemre-establishes the connection automatically as soon as the database is runningagain.

Note: You must connect to the PRISMAaudit database in order to display up-to-datedata.

Always keep the status bar displayed – it shows important information.

Fill level for the PRISMAaudit database:A percentage figure is shown next to the database symbol. This tells you how much of thedatabase is already full.

Administration

U27459-J-Z247-3-7600 77

6.2.5 Online Manual

The documentation for the Device Manager Administrator component can be openedonline. You open the manual via the menu ? → Help. This gives you rapid, direct access tothe information you need.

The online documentation provides the following possibilities:

− You can display the table of contents (like in a printed manual) and browse through theonline text.

− You can proceed directly to a particular chapter by clicking an entry in the table ofcontents.

− You can also go via cross references and the index and go straight to the linkedinformation.

The help window has two panels. The left panel shows the table of contents or index(depending on what you choose); the right panel the selected text.

Use the following buttons to navigate in the online documentation:

Display next chapter.

Display previous chapter.

Display list of contents.

Display index.

Navigation buttons in the browser (depending which browser you are using):

After navigating to a chapter, you can click this button to return to the previous chapter.

After using the above button to move back one chapter, you can click this button to navigate forwards.

Device Types/Devices

U27459-J-Z247-3-7600 79

7 Device Types and DevicesThis chapter deals with device types and devices. Read this chapter before creating andconfiguring devices in the Device Manager. The chapter also explains how to delete devicetypes and devices and to remove data from the database.

The Device Manager differentiates between device types and devices. A device type canbe a particular set of printers or a particular type of inserter. Every device (e.g. everyprinter) has to be assigned a device type.

Before the Device Manager can monitor a device, you have to

− create a device type,

− configure the node (mandatory to be done to be able to create a device),

− configure the device,

− configure the DMI converter (Device Manager configuration program).

You need special access rights to perform these tasks.

7.1 Creating a Device TypeYou perform the following steps to create a new device type:

− Assign the MIF file and compile it into the database

The first step in creating a new device type is to assign the MIF file. The syntacticalcorrectness of the file is checked, and the file is then compiled into the database.

− Define attributes

The data of the default attributes is stored in the database for evaluation. The DeviceManager will not be able to monitor devices without this data.


80 U27459-J-Z247-3-7600

− Define error filters

You can assemble errors in groups – e.g. a group of all the errors that can occur in thepost-processing equipment. This gives you the possibility of restricting your evaluationsto particular sections of the processing line.

− Define device icons for the interface

The Device Manager Explorer can display the devices being monitored by the DeviceManager. You can choose to display devices in an icon and/or a list view. In the iconview, the devices are represented by large icons. The colour tells you at a glance whichstate the device is in. In the list view, the outer left column contains a small icon in thecolour indicating the state. All the devices of a particular type are represented by thesame icon. You choose which icon is to represent which device type.

− Define/enter the physical states

When you create a new device type, you have to define and store the physical stateswhich this type of device may have.

− Assign the physical to the logical states

A distinction is made between physical and logical states. The Device Manager workswith the logical states. You have to map the physical states to the logical states foreach device type. This process enables the wide range of states to be reduced to aminimum set of information.

− Assign service

You have to perform these steps in the order as given, so the actions you need tocomplete are all numbered in the description that follows. You are also guided by thesystem, i.e. the windows are displayed automatically, and brief texts are shown to explainwhat entries you need to make. After creating a device, you can modify the settings bygoing via the tabs (see Chapter 8 “Configuration", page 107.

This is how you create a new device type:

1. Launch the Device Manager Administrator by double-clicking the program icon andlog on.

2. Choose Configure → Install new Device Type on the menu bar.



U27459-J-Z247-3-7600 81

The following chapter describes how to compile the MIF file for the device type into thedatabase. The MIF file describes the device attributes.


82 U27459-J-Z247-3-7600

7.1.1 Compiling the MIF File

This is how you compile the MIF file:

3. Enter the path of the MIF file in the MIF file field, or browse for the file you want to use.Click to open a dialog box where you select a file:

4. Select the MIF file and click <Open>.



U27459-J-Z247-3-7600 83

5. Click <Parse>.

The system checks the MIF file. Once the check is complete, the messageSUCCESSFUL is shown (see next page) and the <Insert> button is made available forselection. The MIF file can then be integrated into the database.


84 U27459-J-Z247-3-7600

6. Click <Insert>.

The system inserts the data into the database. The message MIF InsertionSUCCESSFUL then appears in the dialog box (see following page).


U27459-J-Z247-3-7600 85

7. Click <Exit> to end the process.

The system will display the following message box:


86 U27459-J-Z247-3-7600

8. Click <Yes>.

The system closes the MIF parser dialog and displays the window for entering thedefault attributes.

7.1.2 Assigning Attributes

The system displays the following window:


U27459-J-Z247-3-7600 87

Note: You can create a new device type without assigning any attributes. However,the Device Manager will then not be able to evaluate any data. For example, ifyou do not assign a DMI attribute to the Error attribute, the Device Managerwill not have any list of errors. You will not be able to define error filters orgenerate error statistics.

This is how you assign attributes:

9. The Component field already contains the name of the device type you are creating.

In the left half of the window, the system shows all the DMI groups for the selecteddevice type.

10. Double-click one of the DMI groups.

The system will display all the DMI attributes belonging to this DMI group.

11. Assign your attributes now.Click the desired DMI attribute in the left half of the group box, hold down the leftmouse button and drag the attribute to the standard attribute to which you want toassign it (Button), or click the button of the selected attribute.

The system will display the values of the attributes in the corresponding DMI Groupand DMI Attribute fields.

Your assignment might look like this:


88 U27459-J-Z247-3-7600

12. Once you have assigned all the standard attributes, click the <Save> button.

The system will store the values you have entered.

13. Click <Next>, to continue with the creation of the device type.

The system then displays the window for entering error filters.

Undoing and deleting assignments

If you make a mistake assigning an attribute, you can cancel or delete the assignment(see Chapter 8.7 “Standard Attributes”, page 128).


U27459-J-Z247-3-7600 89

7.1.3 Defining Filters

After compiling the MIF file into the database and assigning the attributes, you can defineerror filters for the device type. These filters are optional. If you do not need any errorfilters for your production environment, click <Next> in the following window

This is the window for defining filters:

This is how you define a filter.

14. The Component field already contains the name of the device type you are creating.

15. Enter a filter name.


90 U27459-J-Z247-3-7600

16. Mark the errors you want the system to filter on the list on the right half of the window.

17. Click the <Save Filter> button.

The system will store the new filter.

18. To create another filter, click the <Create Filter> button and repeat steps 15 to 17.

19. Click <Next> to proceed to the next step.

The system then displays the window for you to assign the icons and images andenter the physical states.

7.1.4 Assigning Icons and Images

In the Device Manager Explorer you can have the devices presented as icons. You canchoose which icons will be used in the display. The Device Manager needs an icon topresent devices in the icon view and another element – an image – for the list view. Theimage is displayed in front of the line of text. The image colour indicates the state of thedevice concerned.

The system displays the following window:


U27459-J-Z247-3-7600 91

This is how you assign icons and images:

20. Click the Icon column in the line with the new device type.

A small button is then shown (see figure below).

21. Click this button.

The system opens the Load Icon for Component dialog box.


92 U27459-J-Z247-3-7600

22. Click <Load> in this dialog box.

The system opens a dialog box for you to select the file containing the icon bitmap.


U27459-J-Z247-3-7600 93

23. Select the file and click <Open>.

The selected icon is shown in the Load Icon for Component dialog box.

24. Click <Save> in this dialog box.

25. In the Device Types window, click to save the data.

The system registers your selection.


94 U27459-J-Z247-3-7600

26. Now assign an image to the device type.

The procedure is the same as for the icon.

In the foreground of the figure below, you can see the dialog box for loading theimage.

Note: The way the abbreviation Blob is written tells you whether or not you haveassigned an icon. If the text is in upper case characters, an icon has beenassigned.

The next step is to enter the physical states for the device type.


U27459-J-Z247-3-7600 95

7.1.5 Defining Physical States

This is how you define the physical states:

27. Click the Phys. States column in the line with the new device type.

A small button is then shown (see figure below).

28. Click the button.

The system opens the Physical States dialog box. This is empty the first time it isopened.


96 U27459-J-Z247-3-7600

29. Click in the dialog box to define a new physical state.

The system displays an empty line.

30. Enter the name of the physical state in the Physical State Name column, and its valuein the Value column.

31. When you have made your entries, click to save your data.

The system registers the data you have entered.

7.1.6 Mapping Physical States to Logical States

A distinction is made between physical and logical states. The Device Manager works withthe logical states. Therefore you have to map physical states to logical states, makingseparate definitions for each device type. This process greatly reduces the range ofdifferent states to a much smaller set of salient information.

Following the installation, the Device Manager knows these logical states:

− Unknown− Operational Stop− Pre/Post Proc. Stop− Error− Ready− Running− Service

You can enter other logical states. See Chapter 8.3 “Logical States”, page 117. The logicalstates are shown at the Device Manager interface.

This is how you make the assignments:

32. Click the column Logical States in the line you want to edit.

The system displays a small button (see below, window in background).




U27459-J-Z247-3-7600 97

34. Click in the dialog box to make a new assignment.

35. Select the name for the physical state and assign a logical state to the physical state.


98 U27459-J-Z247-3-7600

36. When you have finished entering the states, click in the dialog box to save yourentries.

The system will store the data you have entered.

37. When you click the display is updated and the data you have just entered isshown.

38. Click <Close> to continue processing.


U27459-J-Z247-3-7600 99

7.1.7 Assigning the Service State

Enter the value here that you have assigned for the physical state Service. For Océprinters, for example, the value is 5.

Proceed as follows:

39. In the standard window, enter the appropriate value in the Service State column.

40. Click in the standard window to save the data.

The system registers the data you have entered.

7.1.8 Concluding the Process for Creating a Device Type

The system now has all the data it needs to create a device type.

41. Click <Finish>.

The system concludes the process and displays a confirmation message:

42. Click <OK>.

You have now created the new device type with all the requisite data, i.e. you have

− compiled the attributes for this device type into the system via the MIF file,− assigned the standard attributes,− defined error filters (optional),− defined the icons that will represent devices of this type at the interface of the Device

Manager Explorer,− entered the physical states,− assigned the physical states to the logical states.

You can now installing the devices. The entries you have to make are described in thenext section.


100 U27459-J-Z247-3-7600

7.2 Installing a New Device

Note: Prerequisites for the installation of a new device, is to define a node (seepage 130).

This is how you install a new device:


2. On the menu bar, choose Configure → Install new Device.


3. Click <New>.


U27459-J-Z247-3-7600 101

The system again shows the dialog box depicted above. Excepting for Status, all thefields are empty. The entry Initial is preset in the Status field. You cannot change thisvalue when you are making a new definition.

As soon as the History Taker encounters a device with the Initial state, it sends theMIF file to DMI-SP (DMI Service Provider). DMI-SP logically initialises the device andthen returns a notification to the History Taker. The History Taker sets the device stateto Active. The new device is shown in the Device Manager Explorer with Active state.

4. Enter the device name.

5. Select the device type you want to assign to the device.

6. You can enter an explanatory text in the Description field. This text is shown with theproperties (which you display by double-clicking the device, for example).

7. Select the address. For more about creating addresses, see Chapter 8.8 “Nodes”,page 130.

8. Enter the performance and unit of measure.

9. Select the unit of time and the type.

10. Click <Save>.

The new device is configured in the system.

When you have completed the steps up to this point, the new device will be shown in theDevice Manager Explorer with the icon you have assigned:

The device is still in Unknown state. In order for data transfer to take place, you have toconfigure the DMI converter – this is the last step.


102 U27459-J-Z247-3-7600

7.3 Configuring the DMI ConverterYou enter the DMI Converter data in the configuration program. This is described inChapter 9 "Configuration Program", page 141.

Note: You have to enter the converter data on the computer system on which theDMI Converter is installed.

1. Launch the configuration program.

2. Double-click the Converter icon.

The system opens the dialog box shown on the next page.


U27459-J-Z247-3-7600 103

Note: The device name you enter here must be identical with the one you assignedin the Device Manager Explorer. See Chapter 7.2 "Installing a New Device",page 100.

1. Fill out all the fields.

The entries are described in Chapter 9.1.2 "Converter", page 145.

2. Click <Apply> and then <OK>.

The system registers your data.

You have now completed all the steps for having a device tracked by the Device Manager.


104 U27459-J-Z247-3-7600

7.4 Deleting Devices / Device TypesYou can delete the devices and device types you no longer need.

This is how you delete a device or device type:


2. On the menu bar, choose Configure → Clear Devices/Device types or click .


3. In the Item to clear section, indicate whether you want to delete devices or devicetypes; then select the device or device type you want to delete.

4. Click <Delete>.

You are prompted to confirm the delete operation.

5. Click <Yes> to delete the device or device type.

The system issues a message to confirm that the data has been deleted.

Note: By deleting a device type, you also delete all the devices that have beenassigned this type.


U27459-J-Z247-3-7600 105

7.5 Deleting the Attribute HistoryThe data relating to the devices being monitored is stored in the PRISMAaudit database. Ifyou are certain that you will not be needing the data of a particular device again, you canremove the data from the database. For instance, when a device is removed from theproduction line, you can delete the associated data from the database.

Proceed as follows:


2. On the menu bar, choose Configure → Clear Attribute History or click on thetoolbar.


3. Select the devices you want to delete the attributes.

4. Click <Delete>.

You are prompted to confirm the delete operation.

5. Click <Yes> to delete the attributes.

The system issues a message to confirm that the data has been deleted.

Configuration

U27459-J-Z247-3-7600 107

8 ConfigurationThis section describes how you

− define the device names for the different modes of the devices− edit device types− configure printers as twin printers− enter the service times for a device and terminate the service times− activate filters− assign standard attributes− configure nodes− configure devices− create a Visio drawingThis section overlaps partially with Chapter 7 "Device Types and Devices", page 79. If youare registering a new device for tracking with the Device Manager, follow the instructions inChapter 7. If you need help on a specific menu command, you should refer to this chapter.

8.1 DevicesThe Device Manager Explorer displays devices with their names. You can change thesenames. A printer can be configured to run in different modes, e.g. I mode or CE mode.The printer must have a unique name in each of the modes. By default, the system willadd the mode name (such as I or CE) to the device name. You can either keep thesenames for the devices or you can rename them if they do not fit your particular namingsystem.

This is how you rename a device:


2. Click the tab labelled Devices.


Configuration

108 U27459-J-Z247-3-7600

The top half of the window will display all the devices configured on the system. Fordetails on creating a device, see Chapter 7 “Device Types and Devices”, page 79.

3. If you mark a device, the bottom half of the window will display all the pertinent data ofthis device. You can change the displayed names.

4. Enter your changes and click the <Save> button.

The system will store the changes. The system will now display the changed names ofthe devices in the lists of the Device Manager Explorer.

Configuration

U27459-J-Z247-3-7600 109

Note: When you are creating a new device, you assign it a name, and you enterprecisely this name when you configure the DMI converter (see Chapter 7.3“Configuring the DMI Converter”, page 102). This enables the system toestablish its connection. The connection continues to exist under the originalname even if you have changed the name here.

8.2 Device TypesEvery device you want the Device Manager to monitor must be configured in the system(see also Chapter 7 “Device Types and Devices”, page 79). Every device must beassigned to a device type. You have to assign icons to the device type, enter the devicetype’s physical and logical states, etc. Chapter 7 describes in detail all the steps you needperform to have a device monitored by the Device Manager.

The Device Types tab provides functions for changing the assignment of icons, and forediting the physical states and other settings.

Proceed as follows:


2. Click the tab labelled Device Types.


Configuration

110 U27459-J-Z247-3-7600

8.2.1 Changing Icons

When you create a device type in the Device Manager, you have to assign it icons. Youcan change these assignments later.

This is how you assign a new icon (large or small) to a device type:


2. Click the column Image or Icon for the device type you want to assign a graphicsymbol.

The selected column will now have a small button.

Configuration

U27459-J-Z247-3-7600 111

3. Click the small button.

The system will now display the Load Image or Icon for Component dialog box.

4. Click the <Load> button in the dialog box.

The system will display a window in which you can select the file which contains thedesired icon/image.

5. Select the file which contains the desired icon/image and click the <Open> button.

The icon/image stored in the file is then displayed in the Load Icon for Component.

6. Click the <Save> button.

The system will now register the selected icon/image.

7. Click the button to save the data.

The system will now confirm the data.

8.2.2 Changing the Service State

If you change the value of the physical state Service, you must enter the changed valuehere.

This is how you change the service state:


2. In the Device Types window, click the Service State column and enter the desiredvalue.

3. Click the button to save the value.

The system confirms the value you entered.

Note: Bear in mind that the Service State field must always contain a value. If hereis no Service state defined for a device, you should enter a 0 (zero) here.

Configuration

112 U27459-J-Z247-3-7600

8.2.3 Editing Physical States

You enter the physical states when you create the device type.

The following physical states must be stored for Océ printers:

There are two more states in addition to the physical states shown in the window above:Operational Stop and TWIN Stop. You can enter additional states, modify existing states,and delete those which no longer exist.

This is how you edit the physical states:


2. Click the Phys. States column in the line with the device type whose states you wantto change.

The system will display a small button.


The system will display the Physical States dialog box shown on the preceding page.

4. Click to enter a new state; click to delete a state; and click to modify astate.

The system displays an empty line if you elect to define a new state.

Configuration

U27459-J-Z247-3-7600 113

5. Enter the name, then enter the value in the Value column, or change the values thatare already in the fields.

6. Once you have entered all the states, click the button to save the information andthen click <Close>.

The system confirms the values.

8.2.4 Making Mapping Assignments

The physical states have to be mapped to the logical states. You can also assign errorfilters to the logical states.

Example:If a red device icon is shown in the list view in the Device Manager, the device concernedis in error state. This logical state can represent a variety of physical errors. You yourselfhave to determine which physical errors will cause the device to enter the logical Errorstate.

This is how you make or modify mapping assignments:


2. Click the Map column in the line with the device type whose mapping you want tochange.



The system will display the Map Physical State to Logical State dialog box shown onthe following page, but without any entries. The dialog box shown on the next page isan example of mappings made for Océ printers.

Configuration

114 U27459-J-Z247-3-7600

4. Click in the Physical State Name column.



The system will display the physical states stored previously.

Configuration

U27459-J-Z247-3-7600 115

6. Select a physical state.

7. Accordingly, select the logical state you want the physical state to be mapped to.

The system will display the selected states, and in the Colour column, thecorresponding colour.

Configuration

116 U27459-J-Z247-3-7600

8. You can also map an error filter. You select this the same way you selected thepreceding columns. The system provides a range of filters you can select from, whichwere defined for this type of device (see Chapter 8.6 "Filter", page 122).

9. Click the button to create a new line and map the next state. Click to deletean assignment, and to edit an assignment.

10. Once you have mapped all the states, click the button to save the information.

The system confirms the data.

Configuration

U27459-J-Z247-3-7600 117

8.3 Logical StatesThe Device Manager provides seven default logical states for devices.

The logical states of Océ printers are assigned the following colours:

Unknown greyOperational Stop pinkPre/Post Proc. Stop whiteError redReady yellowRunning greenService blue

You can edit the default states and define new ones of your own.

This is how you edit/define a logical state and assign a colour to a state:


2. Click the tab labelled Logical States.

3. Click to define a new state; to delete a state; or to edit a state.

If you are defining a new state, you are shown an empty line.

4. Enter the name of the state and then the value in the Value column.



The system will display a dialog box in which you can select colours.

Configuration

118 U27459-J-Z247-3-7600

You are now looking at the windows shown below:

6. Select the desired colour and click the <OK> button.

7. Once you have defined all the logical states and assigned the colours, click the button to save the information.

The system confirms the values.

Configuration

U27459-J-Z247-3-7600 119

8.4 Twin ModeIf you want to use printers as twins, you will have to configure them accordingly. Thedevices list will always display devices configured as twins side by side (Refer to theDevice Manager Explorer manual).

This is how you define twin mode for devices:


2. Click the tab labelled Twin Mode.


Configuration

120 U27459-J-Z247-3-7600

The top half of the window displays the devices currently configured as twins.The bottom half of the window displays all the devices installed in the system whichare currently available as solo devices.

3. In the Device Name area, mark the first device you want to work as a twin and click

the button. The system will now display the selected device in the empty field to

the right of the .

4. In the Device Name area, mark the second device you want to work as a twin and

click the button.

The right half of the window will now display the two devices you have selected. If youhave not made the correct selection, you can cancel your selections by clicking the<Clear both> button.

5. If you have made the right selection, click the <Make Twin> button.

The system will now display the printers configured as twins in the upper half of thewindow. The Device Name area at the bottom half of the window will no longer displaythe devices, since they are no longer available as Solo devices.

This ensures that the devices you have configured here as a twin system will in fact bepresented side by side in the Device Manager Explorer.

This is how you remove a twin configuration:

1. Mark the twin you wish to remove in the upper half of the window.

2. Click the <Remove Twin> button.

This will remove the twin configuration and the two devices will again be displayed inthe bottom half of the window, in the Device name area. They are now available assolo devices again.

Configuration

U27459-J-Z247-3-7600 121

8.5 ServiceYou can set every device in the system to Service state. You can then monitor how long adevice was in Service state and show this in the utilisation statistics, for example. Theservice state can be set in both the Device Manager Explorer and Device ManagerAdministrator.

This is how you set a device to service state:


2. Click the tab labelled Service.


Configuration

122 U27459-J-Z247-3-7600

3. Select the device you want to be serviced and click the box in the Service column.

The box will now have a check mark.

4. Click the <Update> button.

The selected device is now in Service state. A coloured bar (default blue) is thenshown next to the check mark. The device icon is shown in this colour (blue) in theicon overview in the Explorer; "Yes" is entered in the Service column in the list view.You can also see the device state in the utilisation statistics.

Once the servicing is concluded for this device, you will have to deactivate the Servicestate.

This is how you deactivate the Service state:

1. Choose Configure → Service on the menu bar.

The system will display the Service window shown on the preceding page.

2. Remove the check mark in the Service column for this device and click the <Update>button.

The Service state is now deactivated.

8.6 FilterFilters give you the possibility of collecting errors in groups for use in evaluations. Forexample, you can define a filter to collect all the errors which have to be corrected by theoperator, or for which the operator is in some way responsible.

Example

Name of error Meaning Filter 1 Filter 2

Paper End Operator intervention required X

Paper flaps open Paper flaps were opened by operator toload paper

X

Front door open Door was opened by operator X

Not Ready Stop key was pressed X

Motor temp to high Service all needed X

... ...

Configuration

U27459-J-Z247-3-7600 123

Filter 1: All errors for which the operator is responsible or which can be corrected by operator interventionFilter 2: Errors triggered by the printer

This function is optional

This is how you create a new filter:


2. Click the tab labelled Filter.


The right half of the window displays all the possible errors for the selected devicetype.

Configuration

124 U27459-J-Z247-3-7600

3. Select a device type for which you want to create a filter.

4. Click the <New Filter> button.

The system will add an empty line in the Filter Name display area.

5. Enter a name and mark the errors you want the system to filter on the list on the righthalf of the window .

6. Click the <Save Filter> button.

The system will store the new filter.

If you are creating a filter and decide to change some of the settings you have made, youcan discard entries by clicking the <Reset Filter> button. This has the effect of deactivatingall the selected fields. However, you can only do this provided you have not yet saved thechanged filter. If you want to discard the entire filter you are creating, click the <CancelFilter> button. Again, this is only possible provided you have not yet saved the filter.

If you no longer need a filter stored in the system, you can delete it.

1. Mark the filter and click the <Delete Filter> button.

The system will display a dialog box:

2. Click the <Yes> button.

The system will then delete the filter.

Configuration

U27459-J-Z247-3-7600 125

Example

This example shows the error statistics for a device, obtained using different filters.

Filter: F01 Operational Stop F02 Pre/Post Proc. Stop F03 Error

Error statistics of device A_PS350-1 without a filter

All errors that occurred in the selected period are included in the statistics.

The two figures on the following page show the error statistics for the same device, butobtained using filters.

Configuration

126 U27459-J-Z247-3-7600

Error statistics for device A_PS350-1 with the F03 filter

If you select filter F03, only one error will be shown in this example.

Configuration

U27459-J-Z247-3-7600 127

Error statistics for device A_PS350-1 with the F01 filter

Configuration

128 U27459-J-Z247-3-7600

8.7 Standard AttributesThe following standard attributes are defined in the Device Manager:

− Error− Status− Pagecount− Manufacturer− Errortext− Mode− Config

These standard attributes must always be available in the system. You must assign thestandard attribute to the corresponding DMI attribute, which means that you must informthe Device Manager where it can find the required value in the database.

Example:

The value of the standard attribute named Manufacturer is stored in the DMI groupComponentId under the DMI attribute Manufacturer. The names of the standard attributeand the DMI attribute need not be the same.

This is how you assign the standard attributes to the DMI attributes:


2. Click the tab labelled Standard Attributes.

The system will display the window shown on the following page.

Configuration

U27459-J-Z247-3-7600 129

3. Select the appropriate device type In the Component field.

4. Double-click one of the DMI groups.

The system will display all the DMI attributes belonging to this DMI group.

5. Assign your attributes now.Click the desired DMI attribute in the left half of the group box, hold down the leftmouse button and drag the attribute to the standard attribute to which you want toassign it (Button), or click the button of the selected attribute.

The system will display the values of the attributes in the corresponding DMI Groupand DMI Attribute fields.

6. Once you have assigned all the standard attributes, click the <Save> button.

The system confirms the selected values.

Configuration

130 U27459-J-Z247-3-7600

If you want to cancel an assignment you have made, you have to delete it.

In the DMI Group or DMI Attribute column, select the field you want to delete, then click<Delete>. The system removes this assignment. If you inadvertently delete assignmentsyou can restore them by clicking <Reset>. The system restores the old state. Bear in mindthat the “undo” operation only works if you have not yet saved the changes.

Cancelling and Deleting Assigned Attributes

You can cancel assignments and also delete them when they are no longer needed. Youcan cancel assigned attributes as long as they have not yet been saved.

If you have made one or several attribute assignments but decide you do not want to usethem in the system, click the <Reset> button. The system will then restore the old state.Bear in mind that this is only possible if you have not yet saved the assignments. If youwant to remove a saved assignment, you will have to delete it.

8.8 NodesHere you can enter the name and address of the PC to be used as a converter.

Proceed as follows:


2. Click the tab labelled Nodes.


Configuration

U27459-J-Z247-3-7600 131

3. Click to insert a new line.

4. Fill out all the fields and click to save the data.

Configuration

132 U27459-J-Z247-3-7600

The system will display the dialog box shown on the following page.

5. Click <Yes> to save the record.

The system saves your data.

Modifying / Deleting

You can modify (with the button) or delete (with the button) the data for a definednode.

8.9 Device ConfigurationUse this tab to define the device data. You can create new devices in the system or modifythe data of existing ones. If you wish to create a new device, you can also go via the menubar, choosing Configure → Install new Device (see Chapter 7.2 “Installing a New Device”,page 100).

This is how you install a new device:


2. Click the tab labelled Device Configuration.


Configuration

U27459-J-Z247-3-7600 133

3. Enter your changes and click <Save>.

The system will store the changed data.

Configuration

134 U27459-J-Z247-3-7600

8.10 Visio LinkThe Visio link provides additional possibilities for presenting information. You can set upprocessing lines in the Device Manager Explorer and assign specific Visio drawings toeach line.

This is how you develop a drawing with Visio:

A folder called Visio 2000 is installed together with the Device Manager. This foldercontains the two files:

− BaseDraw.vsd

− CustomMenu.vsu

The file BaseDraw.vsd is the template for your Visio drawing; the file CustomMenu.vsu isrequired for communication between Visio and the Device Manager.

The first step in the design of a new Visio drawing is to open the file BaseDraw.vsd eitherdirectly in Visio or by double-clicking the file name in the Windows NT Explorer.

You will then see the following window:

Configuration

U27459-J-Z247-3-7600 135

The left panel shows the palette of shapes you can select to represent your devices. Theright panel is the workspace for your drawing. The sheet header gives brief instructions onhow to create the drawing.

Proceed as follows:

1. Open the file BaseDraw.vsd.

See the previous page for details on how to open this file. Once you have opened thefile, the system will display the window shown above.

2. Create your drawing.

You then have to group every device you have drawn, and call a macro for eachdevice.

Configuration

136 U27459-J-Z247-3-7600

3. Group every device you have drawn. Select the device and choose Shape →Grouping → Group in the menu bar.

You have to do this both for devices you have designed using several shapes and fordevices designed with only one shape. The grouping is what enables the shapes to beedited by way of the “Contextmenu” macro (shortcut menu). This macro provides youwith a shortcut menu of the functions you can also access in the Device Manager.Starting from your Visio drawing, you can then perform actions such as requestingstatistical information about a device, setting a device to service state, etc., in exactlythe same way as you would in the Device Manager.

4. Run the “Kontextmenu” macro for each device. Select the device and then chooseTools → Macros → Modul1 → CreateContextMenu in the menu bar.

After completing all the steps up to this point, you can open the following shortcutmenu for a device by clicking it with the right mouse button:

Configuration

U27459-J-Z247-3-7600 137

The menu provides Device Manager commands and commands for working on theVisio drawing.

The Visio view thus provides you with the same environment as in the DeviceManager view, and you can execute all the commands in the usual manner.

Configuration

138 U27459-J-Z247-3-7600

If the editing action failed (perhaps because you have forgotten to group a device), theshortcut menu will be Visio-specific, as shown below:

If you see this menu, check that you have completed all the steps as described above.

5. Assign a name to each device you have drawn. Select the device and click the rightmouse button. Choose Format → Special (Object Data) from the shortcut menu.


Configuration

U27459-J-Z247-3-7600 139

Enter the name of the device. Bear in mind that this must be the same name as in theDevice Manager. If the names are not the same, Visio and the PRISMAaudit databasewill not be able to exchange data.

You can now enter this name on your Visio drawing.

6. Complete your Visio drawing. Close the shape window and delete the instructions inthe header of your worksheet.

7. Save your Visio drawing.

You can now open the new Visio drawing in the Device Manager using the Explorer →Visio view command.

Note: Various entries have to be made in the registry to enable Visio drawings to beopened using the Device Manager. If this registry information is missing, thesystem issues a message to tell you so. See Chapter 3.9 "Visio Link", page52.

Configuration Program

U27459-J-Z247-3-7600 141

9 Configuration ProgramBefore users can work with the Device Manager, certain information has to be definedrelating to the system structure, current parameter settings on computers and theproperties of the Device Manager.

Processing with the Device Manager can be controlled by parameters.

We differentiate between two types of parameters:

− Parameters for the database connection and for diagnostic purposes, and

− Configuration parameters.

There is a GUI-based configuration program for entering parameters. You make entries indialog boxes, which makes it easier to enter, modify and delete values. The data is storedin the registry (see note on page 152).


142 U27459-J-Z247-3-7600

9.1 Entering ParametersThere is a configuration program for entering parameters.

This is how you launch the configuration program:

1. Click the <Start> button (in the taskbar).

2. Select Program Files → Océ PRISMAaudit Device Manager → PRISMAaudit DMConfigure or double-click the Configuration program icon.


You have to enter parameters for the following components:

− Converter− Device Manager Explorer− History Taker− Device Manager Statistics

You also use the configuration program to define database users and to choosewhether to keep traces (logs).

The entries for each computer are stored in the registry. The following table lists whichentries have to be made for each of the computer systems.


U27459-J-Z247-3-7600 143

ComputerComponent

Clients ProcessComputer

DMI Converter

Database X X

Converter X

Device Manager Explorer X

History Taker X

Device Manager Statistics X

Traces X X X

3. To launch a component, double-click its icon in the window.

The components are described in detail in the following sections.


144 U27459-J-Z247-3-7600

9.1.1 Database

For the database, you have to enter the database name, the user and a password.

This is how you make the database entries:

1. In the Device Manager – Configuration (Vn) window, double-click the Database icon.


2. Fill out these fields:

Field Description

Database Name Name under which the database was configured on thelocal system (Control Panel → ODBC).

User User ID for the database.

Password Password for the user ID of the database.

3. Click <OK>.

The system confirms the values you have entered.


U27459-J-Z247-3-7600 145

9.1.2 Converter

For the converter, you have set the parameters shown in the dialog box below.

The Device Manager - Converter dialog box contains two tabs:

− Devices− Monitor

Devices tab


146 U27459-J-Z247-3-7600

This is how you set the parameters for devices:

1. In the Device Manager – Configuration (Vn) window, double-click the Converter icon.

The system opens the dialog box shown above.

2. You can set the following parameters:

Field Description

Device Id The device Id is a sequential number.In this version, numbers 1 through 16 are available.

Device Type This Version works with the following device types:

Océ V24 = Océ Printer with V.24 interfaceOcé Type II = Océ Printer with Type II interface (not yet implemented)Pitney Bowes = Pitney Bowes inserterKern = Kern inserterBoewe = Böwe inserterESP = ESP devices (unwinder, rewinder,

cutter)Hunkeler PCSHunkeler DeviceBell+HowellIBM SNMP

Device Name The name you enter here must be identical with thename defined for the device (see Chapter 7.2 "Installing anew Device", page 100).

Reason: the History Taker loads the MIF file for a deviceinto the local DMI-SP (Service Provider) using the nameassigned in the Device Manager Explorer. Only if thenames match can the converter connect to the DMI-SPand, in turn, with the History Taker.

Note:The device name must be a valid file name, otherwise notrace file will be created. Observe the restrictions of youroperating system on the use of special characters in filenames! See also Chapter 9.1.6 "Traces", page 158.

Interface This parameter is relevant only for the device types OcéV24 and Océ Type II relevant. Enter the COM port towhich the printer will be connected. You can display thesettings for the selected port by clicking <COMM> (seedescription at the end of the table).


U27459-J-Z247-3-7600 147

Field Description

This button is not available for the other device types (i.e. itis disabled).

File This parameter is relevant only for the device types PitneyBowes, Kern, Böwe and ESP. Enter the interface file forthese device types.

Important! You cannot change the path once you havespecified it.

If the file you enter does not yet exist, the followingmessage box is displayed:

Remember that you will not be able to change the pathlater. Respond to the system prompt accordingly.

Notes for Kern device types:

The name of the event log file for these devices iscomposed as follows:

<Text><X><yyyymmdd><YZ>.<ext>

Explanation:

<Text> = Usually "Kern“<X> = CenterID, machine group<yyyymmdd> = Time in format year, month, day<YZ> = Sequential numbering (per day)<ext> = Extension, usually "log“

You can enter an original file name, select an existing filename, or create a scheme of your own. However, yourown scheme must contain the sections:<Text><CenterID>*.<ext> (observe the wildcard!)Example: "Kern1*.log“If you enter a name, the converter selects the requisitesections of the name itself.


148 U27459-J-Z247-3-7600

Field Description

Device Index The device index is relevant only for Pitney-Bowes, Kernand ESP device types. It enables the selection of aparticular device record from the interface file.

Pitney-Bowes and ESP devices:Device index = Record/line number of the device in the file (0-based index)

Kern devices:Device index = Inserter ID for selecting a particular event log in the event log file

IBM SNMP:Device index is used for Dual Simplex (in the other caseset it to "1"). The first printer of a Dual Simplex system hasthe device index "1" and the second printer has the index"2".

(IP) Adress For IBM SNMP.

CommunityName For IBM SNMP.

# Counters For Böwe.

# Comonents For Böwe.

Pagetick Counter This parameter is relevant only for the device types OcéV24 and Océ Type II. Enter the number of pages afterwhich status polling should be repeated.

Status (min) This parameter is relevant only for the device types OcéV24 and Océ Type II. Enter the interval betweenoperations to poll the printer status.

Characteristics (min) This parameter is relevant only for the device types OcéV24 and Océ Type II and for IBM SNMP. Enter the intervalbetween operations to poll the printer characteristics.

HouseKeeping (h) This parameter is not evaluated in this version.

It is relevant only for the device types Océ V24 and OcéType II. Enter the interval between globalstatus/characteristics updates.


U27459-J-Z247-3-7600 149

Field Description

Poll Cycle (sec) This parameter is relevant only for the device types Pitney-Bowes, Kern, Böwe, ESP and IBM SNMP. Enter theinterval at which the interface file should be polled. ForIBM SNMP determine the polling interval of the status.

ControllingActive/Inactive

You need this parameter if you want to be able to changethe values of devices while they are active. The converterreads the registry entries only when it starts a device(apart from the "Activation" value – the converter checksregularly whether the device is active).You can set an active device to inactive while theconverter is running. The converter polls the registryentries at 10-second intervals and reacts to any changes.To inform the converter of changes while it is running, setthe device to inactive. Make your changes to the device,and then set the device back to active state. This causesthe converter to read the registry entries for this deviceagain.

Note:Observe the 10-second interval: this ensures the converterhas a chance to recognise the inactive state before you setthe device back to active.


150 U27459-J-Z247-3-7600

Field Description

<COMM> This button is available only when you have selected OcéV24 or Océ Type II devices. When you click <COMM>,you are shown the following dialog box:

Use this dialog box to make the settings for the selectedCOM port.

Note:The settings are preconfigured for the printer. They mayonly be changed after agreement with service personnel.

3. When you have entered or modified the parameters, click <Apply> in the DeviceManager - Converter window.



U27459-J-Z247-3-7600 151

Note: The values you have entered are only registered if you confirm them with<Apply> or <OK>.

4. Set the parameters for the monitoring. Click the Monitor tab.

The system displays the following dialog box:


152 U27459-J-Z247-3-7600


Field Description

V24-Timeout (sec) Use this parameter to set the interval at which theconnection with the printer is to be polled. Since pollingintervals for the printer can be in terms of minutes orhours, the interval you set here ensures that theconnection with the printer is maintained in the interim.This is particularly important during idle periods whenthere are no page ticks (clicks) being logged.

Type-II-Timeout (sec) This parameter is not evaluated in this version.

File Timeout (min) This parameter is relevant only for the device types Pitney-Bowes, Kern, Böwe and ESP. Enter the time that is toelapse before the interface file is declared invalid – thishappens if the Device Management Information System(MIS) does not make any changes to the file within thespecified period of time. This parameter is particularlyimportant with files and devices that do not log updatecounters or time specifications in the file or records. Theparameter serves to monitor whether or not the MIS is infact still serving the interface file.

6. When you have entered or modified the parameters, click <Apply>.


7. Click <OK> to exit the component.

The system again displays the Device Manager – Configuration (Vn).

Note: All converter settings are stored in the registry under the generalPRISMAaudit pathHKEY_LOCAL_MACHINE/SOFTWARE/OPS/Oce PRISMAaudit, in thesection:Device Manager/Converter/Monitor

The values defined for the converter are read only when the DMI converter islaunched. You can change values while the converter is running, butremember that the changes do not take effect until you restart the converter.


U27459-J-Z247-3-7600 153

9.1.3 Device Manager Explorer

You can set the parameters shown below:

This is how you set the parameters:

1. In the Device Manager – Configuration (Vn) window, double-click the icon for theDevice Manager Explorer.



Field Description

ODBC Repeat Counter If there is a problem with the database connection, thesystem attempts to establish the connection again. In thisfield, enter the number of retries that are to be made. Yourentry here depends on the timeout value you enter in theODBC Timeout field.

ODBC Timeout Enter a value in seconds.Enter the interval of time between the database connectionbeing shut down due to a problem, and the first attempt toreconnect to the database (see also ODBC RepeatCounter field).

VISIO File To update Visiofile entry in the registry.


The system again displays the Device Manager – Configuration (Vn).


154 U27459-J-Z247-3-7600

9.1.4 History Taker

The History Taker collects information about the devices which are connected to theDevice Manager.

You can set these parameters for the History Taker:


1. In the Device Manager – Configuration (Vn) window, double-click the icon for theHistory Taker.



Field Description

DB Reconnect (Min) The connection to the database is shut down and re-established at regular intervals in order to free resourcesthat have not been released by the ODBC and to keep thedatabase connection free of errors. Use this parameter tospecify the interval of time between two consecutivereconnects.


U27459-J-Z247-3-7600 155

Field Description

DB TimeSynchronisation (hours)

If the times for the database and operating system aredifferent, the History Taker synchronises the times. Usethis parameter to specify how often the times are to besynchronised.

Daily Restart Yes/No Use this parameter to specify whether or not the HistoryTaker is to be restarted every day. Consider that this stateis recorded in the database, i.e. the connected deviceshave the state Unknown while the restart is in progress.You can, however, set a time for the restart to beperformed (see next field), so you will be able to identifythe restart action in the printer statistics.

Time (hh:mm) Enter the time of the daily restart of the History Taker.

Housekeeping (Min) The History Taker receives information regularly from theDMI. When you enter a value here, the History Taker itselfpolls for information at the specified interval.


The system again displays the Device Manager – Configuration (Vn) window.


156 U27459-J-Z247-3-7600

9.1.5 Statistics

Note: The following parameters are not evaluated in this version. Equivalentfunctionality is provided by the parameters for the Device Manager Explorer(see Chapter 9.1.3 "Device Manager Explorer", page 153).

You can set the parameters shown below:


1. In the Device Manager – Configuration (Vn) window, double-click the Statistics icon.



Field Description

ODBC Repeat Counter If there is a problem with the database connection, thesystem attempts to establish the connection again. In thisfield, enter the number of retries that are to be made. Yourentry here depends on the timeout value you enter in theODBC Timeout field.


U27459-J-Z247-3-7600 157

Field Description

ODBC Timeout Enter a value in seconds.Enter the interval of time between the database connectionbeing shut down due to a problem, and the first attempt toreconnect to the database (see also ODBC RepeatCounter field


The system again displays the Device Manager – Configuration (Vn) window.


158 U27459-J-Z247-3-7600

9.1.6 Traces

The behaviour of the converter and History Taker components can be monitored bykeeping traces. The information supplied by the trace files is helpful in identifying thecause of problems.

To make settings for traces, click the Traces icon in the configuration program window.The system opens the following dialog box:

Note: Trace functionality is also planned for the PRISMAaudit Explorer,PRISMAaudit Statistics and PRISMAaudit Administrator components. Thefields for these components are not evaluated in this version.

You can select from the following trace levels:

Error Trace = 1Warning Trace = 2Info Trace = 4Process Trace = 8

The info trace logs non-critical events. The process trace logs detailed information andconstitutes a debug mode.


U27459-J-Z247-3-7600 159

To keep multiple traces, simply add the values.

Example:You want to run all the traces for the converter. In the Level field, enter "15" (Error +Warning + Info + Process → 1 + 2 + 4 + 8).You want to run the error, warning and info traces for the History Taker. To do this, enter"7" in the Level field (1 + 2 + 4).

This is how you configure the trace settings:

1. In the Device Manager – Configuration (Vn) window, double-click the Traces icon.

The system opens the dialog box shown on the previous page.

2. You can run traces for the converter and History Taker components.

If the Level field is set to 0 (zero), no trace will be run.

3. Select either the User or Dev column.

There are no differences between these two options in this version. In future versions,it is planned to log additional internal information for the developer.

4. Click <OK>.

The system confirms the values you have entered and again displays the DeviceManager – Configuration (Vn) window.


160 U27459-J-Z247-3-7600

You have to state where you want to save the trace files.

1. Click the button next to the Trace Directory field.


2. Select the path and click <OK>.

The system creates the trace files in the path you have specified.The Device Manager – Configuration (Vn) window is then displayed again.

Note: The trace files have the same names as the devices (see Chapter 9.1.2"Converter ", Devices tab), followed by the extension trc or trb. The traces arewritten alternately to 500 KB files (extension trc or trb). When the first file isfull, the trace is written to the second file; when this is full, the first file isoverwritten.

The device name must be a valid file name, otherwise no trace file will becreated. Take care with special characters.


U27459-J-Z247-3-7600 161

Displaying and printing the trace file

In the event of errors, you can print out the trace file to make troubleshooting easier.

This is how you print a trace file:

1. The Trace Directory field indicates where the trace files are stored.

2. Change to this directory and double-click the name of the file to open it.

3. If you have a log printer connected to your system, you can print the file and fax theprintout to service for help in solving problems.

Note: The trace directory is the same for all the managers installed on the PC.

U27459-J-Z247-3-7600 163

10 Instructions and Actions to take in Event ofErrors

Error Actions

Interface programs are not getting a connectionwith the PRISMAaudit database

11 � 9 � 8 � 5

Devices do not appear in the PRISMAauditExplorer window following installation

11 � 1 � 2 � 3 � 4 � 6 � 7

Devices remain in "UNKNOWN“ state in theExplorer window

11 � 1 � 2 � 3 � 4 � 6 � 7

User administration is not working 10

ODBC driver error messages 8

Problems initialising interface programs 12

No state transitions on devices 3

Actions

1. Check the connection between the DMI 2.0 Converter and the devices

– Is the device physically connected to the DMI2 Converter PC

– Has the DMI2 Converter been started as a service in Win NT

– Have the devices been configured in the DMConfigure program

– Is the trace of the DMI2 Converter activated in the DMConfigure program

– Does the trace of the DMI2 Converter show that the converter is communicatingwith the devices

– Does the printer have the correct functional code

164 U27459-J-Z247-3-7600

2. Check the connection between the DMI2 Converter and the DMI 2.0 Service Provider

– Has the DMI 2.0 Service Provider been started as a service in Win NT

– Have the devices been declared to the DMI Service Provider (tool : DMI Explorer)

– Can the device data be viewed with the DMI Explorer

– Does the trace of the DMI2 Converter show that the converter is communicatingwith the DMI 2.0 Service Provider

3. Check the connection between the History Taker and the DMI 2.0 Service Provider

– Has the History Taker been started as a service in Win NT

– Does the trace of the History Taker show that it is communicating with the DMI 2.0Service Provider

4. Check the connection between the History Taker and the database

– Does the trace of the History Taker show that it is communicating with thePRISMAaudit database

– Is an ODBC System DSN for the PRISMAaudit database entered for the HistoryTaker

5. Check interface programs

– Has an ODBC user DSN been defined for the PRISMAaudit database

– Is the icon for the connection to the database active

– Are the devices known in the PRISMAaudit Explorer and activated

– Are the nodes (converter PCs) activated via which the devices can be accessed

6. Save trace (DMI2 Converter and History Taker)

– Set the maximum trace level using the DMConfigure program

– Save the trace for second level support

7. Save database

– Make a full database backup or copy the existing full backup plus the TA logbackup beyond the time the problem occurred, and send to second level support

8. Check whether the PRISMAaudit database is working

– Check in the NT Log to establish whether the database is full

– Start the SQL Server Enterprise Manager

– Check whether the database is active

U27459-J-Z247-3-7600 165

– Check whether the transaction log has overflowed

– Check whether deadlocks have to be cleared

9. Check the PRISMAaudit user password

– Launch the PRISMAaudit Administrator program and start user administration

– Re-assign the user password

10. Register the user administration

– Register the user administration as OCX in Win NT

11. Check the TCP/IP network

– Check whether LAN communication is working

U27459-J-Z247-3-7600 167

IndexA

AdministratorDevice Manager 7, 69

ArchitectureDevice Manager 5

Assigningicons for device types 110standard attributes 128

BBase system 43, 46Buttons, functions 75

CChanging

user data 66Client 6

starting 54COM port 146

settings 150Configuration parameters 141Configuration program 102, 141

launching 142Configure menu 73Configuring

device names 107twin system 119

Converterparameters 145

Creatingdevice types 80devices 100filters 122groups 61profiles 58Visio drawing 135

DData Fetcher 7Database 6

connecting 43making entries 144parameters 144status bar symbol 74

Database assistant 43Database server

starting 53Deactivating

service 122Deinstallation

Device Manager 51Deleting

groups 63profiles 60users 66

Deleting filters 124Device Manager 1

Administrator 7, 69architecture 5deinstallation 51Explorer 7general description 2logging off 55logging on 55

Device Manager Explorerparameters 153

Device names 103Device names, configuring 107Device states 101Device types

icons and images 92

168 U27459-J-Z247-3-7600

Devicescreating 79installing 100properties 101

DMI attribute 128DMI Converter 6, 102DMI group 87, 129

EEditing

groups 63physical states 112profiles 60

ExplorerDevice Manager 7

FFile menu 73Fill level 76Filter 71Filters

creating 122deleting 124

GGroups

creating 61deleting 63editing 63

HHelp 77

accessing 74History Taker 6

parameters 154

IIcons 75

assigning for device types 80Icons and images

assigning 91Icons for devices 91Images and icons

assigning 91

Installation 9ODBC 24prerequisites 10sequence 10

Installingdevices 100

LLinks 101Logging off

Device Manager 55Logging on

Device Manager 55Logical states 70

MMacro

for shortcut menu 136Menus 73

Device Manager Administrator73

MIF files 69, 79

NNodes 130

OODBC

installation 24ODBC Converter 6Online manual 77Operator PC

starting 54

PParameters 141

converter 146database 144Device Manager Explorer 153devices 145entering 142History Taker 154statistics 156Trace 158

Password 56

U27459-J-Z247-3-7600 169

Physical states 70, 80editing 112

PRISMAaudit 1Process server

starting 53Profiles 58

creating 58deleting 60editing 60

RRegistry 142, 152Removing a twin configuration

120Renaming

devices 107

SService 99

deactivating 122setting 121

Service stateassigning 111

SettingsODBC 24

Shortcut menumacro for 136

SQL database 6Standard attributes 128States

physical 95physical and logical 70

Statistics

parameters 156Symbols, functions 75

TTime synchronisation 155Toolbar 75Toolbar buttons

Explorer 75Trace 158

parameters 158printing 161setting directory for 160settings 159

Twinconfiguring 119mode 120removing 120

UUser administration 57User data

changing 66User ID 56Users 64

administrating 64deleting 66

VView menu 74Visio drawing

creating 135

Date post:	28-Mar-2018
Category:	Documents
Upload:	vongoc
View:	212 times
Download:	0 times

PRISMAaudit Device Manager Version 3.00 Administrator’s...

Documents