Bosch BIS 2.3 Installation Manual
  1. Manuals
  2. Brands
  3. Bosch Manuals
  4. Security System
  5. BIS 2.3
  6. Installation manual
Bosch BIS 2.3 Installation Manual

Bosch BIS 2.3 Installation Manual

Access engine
Hide thumbs
Table of Contents

Advertisement

Quick Links

BIS 2.3 - Access Engine
en
Installation manual

Advertisement

Table of Contents
loading

Related Manuals for Bosch BIS 2.3

Summary of Contents for Bosch BIS 2.3

  • Page 1 BIS 2.3 - Access Engine Installation manual...

  • Page 3: Table Of Contents

    BIS 2.3 - Access Engine Table of Contents | en Table of Contents Introduction Upgrade Upgrade matrix BIS upgrade since version 2.1 or higher Updating Controller (LAC) Software Server installation Standalone system Distributed system 3.2.1 Login server 3.2.2 Remote server 3.2.3...
  • Page 4 | Table of Contents BIS 2.3 - Access Engine 5.1.3 Configuring Internet Explorer 5.1.4 Connecting a dialog reader Setting up Card Personalization 5.2.1 Software 5.2.2 Hardware 5.2.3 Creating Badge Layouts 5.2.4 Printing Badges 5.2.5 Creating card layouts 5.2.6 Creating cards...

  • Page 5: Bis 2.3 - Access Engine Table Of Contents | En

    BIS 2.3 - Access Engine Table of Contents | en 8.2.1 Printout of the configuration data 8.2.2 Installation documentation Setting System Parameters with SPEdit Starting the SPEdit Display the Last Access in the Status Bar Listbox or Search Dialog for Companies...
  • Page 6 | Table of Contents BIS 2.3 - Access Engine MAC - Main Access Controller 11.1 Functions 11.1.1 Basic functions 11.1.2 Access Control functions 11.2 Data defintions 11.3 Operating the MAC 11.3.1 Startup 11.3.2 Shutdown 11.3.3 Warm start 11.3.4 Cold start 11.4...

  • Page 7: Table Of Contents

    BIS 2.3 - Access Engine Table of Contents | en 14.2.1 Change the timezone 14.2.2 Regional and Language Options 14.3 Date and time formats Index Bosch Sicherheitssysteme GmbH Installation manual F.01U.028.713 | V 2.3.0.1 | 2009.11...

  • Page 8: Introduction

    | Introduction BIS 2.3 - Access Engine Introduction Starting with a rough overview of the system the following chapters will describe the installation of the access control system Access Engine, with its possible variations. This will enable the installer of the system to install and configure the system components according to his/her own needs and wishes.
  • Page 9 BIS 2.3 - Access Engine Introduction | en Bosch Sicherheitssysteme GmbH Installation manual F.01U.028.713 | V 2.3.0.1 | 2009.11...

  • Page 10: Upgrade

    | Upgrade BIS 2.3 - Access Engine Upgrade Upgrade matrix BIS-Software without Access Engine: BIS 1.4.8 BIS 2.0 BIS 2.1 BIS 2.2 BIS 2.3 from BIS 1.4.1 BIS 1.4.8 BIS 2.0 BIS 2.1 BIS 2.2 Table 2.1 Upgrade matrix BIS without Access Engine BIS-Software with Access Engine: BIS 1.4.8...
  • Page 11 BIS 2.3 - Access Engine Upgrade | en Select the functions you wish to install as if you were installing from scratch. In this upgrade you may also add components which were not previously installed. The databases for the logs and access engine with their corresponding user data are located and displayed.
  • Page 12 | Upgrade BIS 2.3 - Access Engine The chosen settings are summarized for confirmation. F.01U.028.713 | V 2.3.0.1 | 2009.11 Installation manual Bosch Sicherheitssysteme GmbH...
  • Page 13 BIS 2.3 - Access Engine Upgrade | en Clicking Next will start the upgrade. The Access Engine Database is also updated, as shown in the next screenshot Bosch Sicherheitssysteme GmbH Installation manual F.01U.028.713 | V 2.3.0.1 | 2009.11...
  • Page 14 | Upgrade BIS 2.3 - Access Engine When you receive confirmation of a successful upgrade click Finish to end the process. A text file is shown detailing a number of mandatory post installation steps, including a reboot. Please print the file and carry out all steps as instructed.

  • Page 15: Updating Controller (Lac) Software

    BIS 2.3 - Access Engine Upgrade | en All configuration and access control data are preserved. Upon starting the BIS Configuration browser and loading your configuration the access Engine database will have to be synchronized. Affirm the synchronization dialog in order to use your accustomed data and settings.
  • Page 16 | Upgrade BIS 2.3 - Access Engine The system manager can now decide whether, when and which LACs should be included in the new installation. To do this simply check the box Connection to MAC active on the first tab/page of each controller in the Device Editor, and then save the changes by clicking Apply.

  • Page 17: Server Installation

    BIS 2.3 - Access Engine Server installation | en Server installation Figure 3.1 System configuration - Management view The Building Integration System (BIS) with its modules (Engines) is generally installed on one computer. When Access Engine is installed on the same computer as the BIS manager, this is termed a standalone system.

  • Page 18: Standalone System

    | Server installation BIS 2.3 - Access Engine NOTICE! The Access Engine (ACE 2.3) does not run with SP3 of Microsoft SQL-Server 2005. Standalone system The installation of a standalone system is described in the BIS installation manual. There you will find a detailed explanation of the setup of the computer and the inclusion/exclusion of the components to be installed.

  • Page 19: Distributed System

    BIS 2.3 - Access Engine Server installation | en Distributed system In order to install BIS with Access Engine on a distrubuted system it is necessary for all computers involved to be networked together. For instructions on setting up the network please consult the notes in the BIS installation manual.

  • Page 20: Login Server

    | Server installation BIS 2.3 - Access Engine 3.2.1 Login server The Login Server is installed from the same CD as the standalone server. In the feature selection box however only the following features are selected. Figure 3.3 Selection of features for the Login Servers If no other engines are to be installed besides the Access Engine then this is the only selected node under Login Server.

  • Page 21: Remote Server

    BIS 2.3 - Access Engine Server installation | en 3.2.2 Remote server The installation of the Remote Server too is the same as that of other systems. The feature selection however is somewhat different. Figure 3.4 Feature selection for a Remote Server Here it is essential that Door Controller be selected under the Connections node.

  • Page 22: Configuring A Distributed System

    | Server installation BIS 2.3 - Access Engine 3.2.3 Configuring a distributed system In the Configuration Browser, which runs on the login server, the remote server is entered in the appropriate list in the Server Structure dialog. This entry will appear subsequently in the menu Connections. If Access Engine is not listed underneath the remote server then it will need to be added here.

  • Page 23: Server Workstation

    BIS 2.3 - Access Engine Server installation | en Server workstation The installation of the BIS system turns the server into a workstation where all applications and dialogs can be executed from the same computer, and where configuration of the system software can be undertaken cf.

  • Page 24: System Configuration

    | System configuration BIS 2.3 - Access Engine System configuration The installed BIS software and its integrated engines cannot be used until the system has been configured. Configuration means adapting the system to a particular client’s environment individual requirements.

  • Page 25: Setting Up A Configuration

    BIS 2.3 - Access Engine System configuration | en The Configuration Browser is started and can be used as far as the user’s authorization allows, to edit or view the current configuration. Setting up a configuration With Access Engine there is a difference between the creation of an initial configuration and adding additional configurations.
  • Page 26 | System configuration BIS 2.3 - Access Engine yet contain any entries - therefore select the New configuration entry in the Configuration management field. Another dialog is opened offering a choice of pre-installed default configurations. – Select the Access Engine entry in the Group field and confirm with OK.

  • Page 27: Creating Additional Configurations

    BIS 2.3 - Access Engine System configuration | en Check the license file contents in the License dialog are correct. – If these do not match the file imported in the BIS Manager, you can copy the imported file for the configuration using the Read button.
  • Page 28 | System configuration BIS 2.3 - Access Engine Figure 4.1 Error message when the configuration is not loaded Confirm both this message and the message that follows regarding the creation of placeholders with OK. A placeholder is a dummy configuration which supports connections but can not be edited.

  • Page 29: Loading A Configuration

    BIS 2.3 - Access Engine System configuration | en Switch to the Connections menu and select the Access Engine placeholder entry in the Explorer. – Remove the Access Engine placeholder entry using the x button or the Remove command in the context menu (right-click on Access Engine).

  • Page 30: Copying Configuration Changes

    | System configuration BIS 2.3 - Access Engine In the BIS Manager switch to the Load/Save configuration page. – In the Load new configuration field click the ellipsis button (…) and select the directory with the new configuration. –...

  • Page 31: Setting Up Bis User

    BIS 2.3 - Access Engine System configuration | en Setting up BIS user During the system installation, the users Administrator and BIS are created. Both users automatically receive full privileges for the BIS platform, the Access Engine dialogs and the server workstation.

  • Page 32: Pin Code Settings

    | System configuration BIS 2.3 - Access Engine 4.6.2 PIN Code Settings These configuration settings refer to the permitted number of mistyped attempts. the minimum length of the PIN 4.6.3 Card encoding The reader parameter Check membership only values can be set in the device editor.

  • Page 33: Setting Up Additional Workstations

    BIS 2.3 - Access Engine Setting up additional workstations | en Setting up additional workstations In addition to the preinstalled server workstation (login server) further workstations can be installed on which it will be possible to run the BIS platform and the Access Engine . These can be any computers in the network (for distributed systems see Section 3.2 Distributed system), or the remote server.

  • Page 34: Setting Up The Configuration Browser

    | Setting up additional workstations BIS 2.3 - Access Engine Figure 5.1 System overview with additional workstations If you wish to install this workstation for special tasks (e.g. card personalization), please see the instructions in Section 5.2 Setting up Card Personalization.

  • Page 35: Configuring Internet Explorer

    BIS 2.3 - Access Engine Setting up additional workstations | en In the Administration menu switch to the ACE Workstations dialog. – Select the node DMS in the explorer of this dialog. – Add a new entry by clicking the + button above the list field.
  • Page 36 | Setting up additional workstations BIS 2.3 - Access Engine Figure 5.2 Internet Explorer - Properties: General tab Enter the name of the login server as home page. F.01U.028.713 | V 2.3.0.1 | 2009.11 Installation manual Bosch Sicherheitssysteme GmbH...
  • Page 37 BIS 2.3 - Access Engine Setting up additional workstations | en Figure 5.3 Internet Explorer - Properties Security Change to the Security tab. In the upper window click Trusted Sites and then the Sites button. Figure 5.4 Internet Explorer - Properties: Trusted Sites...

  • Page 38: Connecting A Dialog Reader

    | Setting up additional workstations BIS 2.3 - Access Engine Uncheck the box Require Server verification for all sites in this Zone ... amd create the following entries using the upper text box: http://<Name of the Login Server> http://localhost Save each entry from the upper text box by clicking Add and finally confirm your entries by clicking OK.
  • Page 39 BIS 2.3 - Access Engine Setting up additional workstations | en Readers with serial interface Dialog readers are generally special readers with an RS232 interface meaning they can be connected to any workstation as follows: Connect the dialog reader to a free COM port on the workstation using an RS232 cable.
  • Page 40 | Setting up additional workstations BIS 2.3 - Access Engine appropriate reader. The same button is also vailable in other Personnel Data dialogs such as Print Badge, Cards, PIN Code, Blocking, Blacklist and Areas. NOTICE! As reader-based data searches require the physical presence of...

  • Page 41: Setting Up Card Personalization

    BIS 2.3 - Access Engine Setting up additional workstations | en Setting up Card Personalization 5.2.1 Software Install the Card Personalization program from the BIS installation CD. This need be done only on those individual computers which you intend to use for creating ID cards.

  • Page 42: Hardware

    | Setting up additional workstations BIS 2.3 - Access Engine 5.2.2 Hardware Before they can be used for creating ID cards, cameras and badge printers need to be installed with their respective drivers as provided by the manufacturers. After thus installing and connecting the devices they should be configured using the Card Personalization dialog.

  • Page 43: Printing Badges

    BIS 2.3 - Access Engine Setting up additional workstations | en Release Card). This process copies the layouts to the directory <InstallDrive>:\MgtS\AccessEngine\CP\Layouts NOTICE! The strict separation between saving a layout and releasing it for general use enables you safely to store half-finished or prototype layouts for later editing, without fear that they will inadvertently be used.
  • Page 44 | Setting up additional workstations BIS 2.3 - Access Engine has started, the console window will be closed and a systray icon appears. Via the context menu (right mouse click) of this icon the console window can be opened again.
  • Page 45 BIS 2.3 - Access Engine Setting up additional workstations | en have to start it manually. Therefore you can double clicking on the SfmApp-4.exe entry in the folder: \\runtime-drive\MgtS\Access Engine\CP\BIN If the program isn't up, you cannot execute any function of the Print Badges dialog in the Access Engine System.

  • Page 46: Creating Card Layouts

    | Setting up additional workstations BIS 2.3 - Access Engine – Double clicking on the SfmCfgApp.exe entry in the folder \\runtime-drive\MgtS\Access Engine\CP\BIN 5.2.5 Creating card layouts Card layouts can only be created using the relevant application in the Configuration Browser on the server. These are available at all workstations that can execute the Access Engine Print card dialog.

  • Page 47: Creating Cards

    BIS 2.3 - Access Engine Setting up additional workstations | en – Save the created layouts using names that everyone will understand - your colleagues should be able to work with these names too. – In order for the layouts to be available on the workstations, they must be released.

  • Page 48: User Administration

    | User administration BIS 2.3 - Access Engine User administration User administration for the Access Engine controls the access rights of the workstation users via profiles that define the use of certain dialogs and programs as well as the scope of data processing.

  • Page 49: Standard Users

    BIS 2.3 - Access Engine User administration | en Standard users The installation process creates standard users Administrator and BIS. These have full editing rights for the Building Integration System and Access Engine and can log in at any of the workstations (even at those added later) as long as the standard settings governing this have not been changed cf.
  • Page 50 | User administration BIS 2.3 - Access Engine – To move to the next column while keeping the same selection use the right arrow key. NOTICE! The individual column entries have the following meaning: View: The dialog is displayed and the data can be selected.

  • Page 51: Setting Up Workstation Profiles

    BIS 2.3 - Access Engine User administration | en User profile B: Contains the rights for the personal data dialogs that are required for card personalization: – Persons – Companies – Print card – Cards – PIN code User profile C: Contains the rights for the visitor dialogs.
  • Page 52 | User administration BIS 2.3 - Access Engine Create a new profile by ... – ... giving the profile a unique name - try to describe the rights or restrictions contained in the name or use the Description field.
  • Page 53 BIS 2.3 - Access Engine User administration | en Examples: WP-Administrator : Contains all rights for all Access Engine dialogs and applications. WP-Server: Preinstalled workstation profile with no viewing rights. NOTICE! The workstation profiles WP-Administrator and WP-Server are preinstalled. The UP-Administrator user profile is already assigned to the WP-Administrator;...

  • Page 54: How Profiles Work

    | User administration BIS 2.3 - Access Engine Workstation profiles and possible user profile assignments 6.2.3 How profiles work Each user can be assigned one or more user profiles. Similarly each workstation can be assigned any number of workstation F.01U.028.713 | V 2.3.0.1 | 2009.11...
  • Page 55 BIS 2.3 - Access Engine User administration | en profiles. The rights in user profiles are cumulative, and the rights in workstation profiles are also cumulative. However when a user sits at a workstation he has only those of his user rights which are also allowed by the workstation’s profiles.
  • Page 56 | User administration BIS 2.3 - Access Engine Assignment of the default profiles to workstations Workstation profile XXX: (cf. Figure ) All users with user profiles B, C or D (or combination) receive the execution rights for dialogs in accordance with their profiles.
  • Page 57 BIS 2.3 - Access Engine User administration | en Workstation profile YYY: (cf. Figure ) Users with user profiles B and D will not see any dialogs on workstations with this workstation profile, since the rights of their user profiles and the workstation profile do not overlap.

  • Page 58: Creating New Access Engine Users

    | User administration BIS 2.3 - Access Engine Overview of the assignment options for workstation profiles Creating new Access Engine users The Configuration Browser is used to create new users for any workstations. To do this, the steps are as follows: F.01U.028.713 | V 2.3.0.1 | 2009.11...
  • Page 59 BIS 2.3 - Access Engine User administration | en Start the Configuration Browser as described in Section 4.1 Starting the Configuration Browser, Page 24. In the Configuration Browser select the Operators entry in the Administration menu. – Create a new entry in the left-hand list field by clicking the + symbol above the list.

  • Page 60: Users Of A Server Workstation

    | User administration BIS 2.3 - Access Engine Users of a server workstation 6.4.1 User with Administrator profile Due to the preinstalled setup and assignment of the UP- and WP-Administrator profiles to the server workstation, new users can only access the Access Engine dialogs and applications if they are assigned the UP-Administrator profile.

  • Page 61: User With New Profile

    BIS 2.3 - Access Engine User administration | en 6.4.2 User with new profile If you do not want users to be able to execute all dialogs and applications on the server workstation, this can be achieved by assigning new user profiles with reduced rights to the modifiable WP-Server workstation profile.

  • Page 62: Users Of Other Workstations

    | User administration BIS 2.3 - Access Engine New user with new user profile for the server workstation Users of other workstations 6.5.1 Existing user on new workstation To create a new workstation, proceed as described in Section 5.1.2 Setting up the Configuration Browser, Page 34.

  • Page 63: New User On Existing Workstation

    BIS 2.3 - Access Engine User administration | en Assignment of workstation profiles to a new workstation 6.5.2 New user on existing workstation To create a new user, proceed as described in Section 6.3 Creating new Access Engine users. In the Configuration Browser dialogs ACE workstation...
  • Page 64 | User administration BIS 2.3 - Access Engine To create a new workstation, proceed as described in Section 5.1.2 Setting up the Configuration Browser, Page 34. Make sure that at least one of the user profiles that belongs to the new workstation via the workstation profiles is assigned to the new user - to do so, check the settings in the ACE workstation profile dialog.

  • Page 65: Connecting The Controllers

    BIS 2.3 - Access Engine Connecting the controllers | en Connecting the controllers This chapter describes the connection variants for controllers. With distributed systems (see Section 3.2 Distributed system), the controller is connected to the remote or connection server. General The AMC2 4W controller will be connected to the host system via Ethernet, only.

  • Page 66: Creating The Controllers In The Device Editor

    | Connecting the controllers BIS 2.3 - Access Engine 7.1.1 Creating the controllers in the device editor Configuration is performed in the Configuration Browser. Start the Configuration Browser as described in Section 4.1 Starting the Configuration Browser, Page 24.

  • Page 67: Ethernet

    BIS 2.3 - Access Engine Connecting the controllers | en Ethernet Set up the the AMC as described in Section 7.1.1 Creating the controllers in the device editor. Select UDP as the interface type. Enter the IP address of the AMC as the host name.
  • Page 68 | Connecting the controllers BIS 2.3 - Access Engine In the device data editor (Configuration Browser > Connections > Access Engine) select the respective AMC in the explorer (left). – Open the context menu (right mouse button) and select the New Object entry.

  • Page 69: Connecting Readers And Doors

    BIS 2.3 - Access Engine Connecting readers and doors | en Connecting readers and doors Readers for AMC2 Up to four readers with Wiegand interface can be connected to an AMC2. However, it is possible that when selecting certain door models or installing additional signals some reader slots remain unused, as they cannot be technically configured any more.

  • Page 70: Interface Allocations

    | Connecting readers and doors BIS 2.3 - Access Engine The following table provides an overview of the readers that can currently be connected and their possible combinations. Catalog description Selection in the device data editor ARD-ProxPointPlus WIE1 ARD-MiniProx...
  • Page 71 BIS 2.3 - Access Engine Connecting readers and doors | en Controller – Name, description – Interface type – Set connection parameter Reader – Designation for the reader interface – Reader name – Entrance to which the reader belongs Signals –...

  • Page 72: Installation Documentation

    | Connecting readers and doors BIS 2.3 - Access Engine 8.2.2 Installation documentation If the devices are installed first, however, which will normally be the case, the wiring carried out must be documented and communicated to the system configurator. The following plan can be used for the declaration of the selected interfaces - use the S-identifications, which uniquely identify the connectors.

  • Page 73: Setting System Parameters With Spedit

    BIS 2.3 - Access Engine Setting System Parameters with SPEdit | en Setting System Parameters with SPEdit The default Access Engine system settings will satisfy most customer requirements. Nevertheless it may be desirable in some cases to change the default settings above and beyond that which can be customized in the BIS Configuration Browser.

  • Page 74: Display The Last Access In The Status Bar

    | Setting System Parameters with SPEdit BIS 2.3 - Access Engine Load the registry file for the workstation of your choice: File > Load... There follows a list of some of the settings which can be made in this editor. Full descriptions are available SPEdit’s online help function.

  • Page 75: Making Company A Required Field

    BIS 2.3 - Access Engine Setting System Parameters with SPEdit | en Making Company a required field Depending on customer demands the assigning of a company to a person can be made required. The field description will marked accordingly with an underlined label.

  • Page 76: Valid-From Date For Authorizations

    | Setting System Parameters with SPEdit BIS 2.3 - Access Engine Parameter Description HasPrintButton activates the button to print the preview - HasPrintSetupButton activates the button to choose an other printer - HasProgressControls shows the number of the selected data –...

  • Page 77: Valid-From Date For Lockouts

    BIS 2.3 - Access Engine Setting System Parameters with SPEdit | en future date, but the standard installation does not allow an authorization to be backdated (i.e. to start in the past). This default can be overriden by changing the system parameter AuthorizeValidFromInPast in the topic CardData.

  • Page 78: Dms - Data Management System

    | DMS - Data Management System BIS 2.3 - Access Engine DMS - Data Management System 10.1 System operation 10.1.1 Starting The master process is set up and installed as an XP/W2000 service and is controlled by the operating system's Service Control Manager (SCM).
  • Page 79 BIS 2.3 - Access Engine DMS - Data Management System | en Possible named parameters are described in table 2-1. The block concludes with the command 'add', which adds the process characteristics to the process table. The following example illustrates the structure of a block: define Loggifier set /description="Logging and Notification"...
  • Page 80 | DMS - Data Management System BIS 2.3 - Access Engine Named Parameter Description type Process type: BASE: Base Process - the process is essential. If such a process fails then the BIS system as a whole will crash.

  • Page 81: Closing

    BIS 2.3 - Access Engine DMS - Data Management System | en Special delays such as the start delay, the restart delay, idle times before terminating a process, etc. are specified by the system parameters that are saved in the registry.
  • Page 82 | DMS - Data Management System BIS 2.3 - Access Engine In order to protect the console window and the process control window against unauthorized access, a separate authentication dialog appears when you call up one of these functions, which asks once more for the authentication data of an operating system administrator user.

  • Page 83: Function Overview

    BIS 2.3 - Access Engine DMS - Data Management System | en The corresponding messages also appear when shutting down the system: Figure 10.4 Messages on system shutdown The start and end of batch processes can also be controlled: Figure 10.5 Messages for batch processes However, the console window displays only messages that appeared since the last start of the master.
  • Page 84 | DMS - Data Management System BIS 2.3 - Access Engine To obtain a summary of the possible command entries, enter the command “help” in the console window: Figure 10.6 Master console: list of commands To execute the commands, you need only to enter their abbreviations (shown in capitals).
  • Page 85 BIS 2.3 - Access Engine DMS - Data Management System | en Examples of diagnosis pages Bosch Sicherheitssysteme GmbH Installation manual F.01U.028.713 | V 2.3.0.1 | 2009.11...

  • Page 86: Process Control

    | DMS - Data Management System BIS 2.3 - Access Engine Using the master console, information about all other processes can also be displayed. The list below corresponds to the information displayed in the process control window - see the next section.
  • Page 87 BIS 2.3 - Access Engine DMS - Data Management System | en Processes List of the processes from the process description file. The corresponding information is displayed in the fields for the selected process. Executable Name of the executable file.
  • Page 88 | DMS - Data Management System BIS 2.3 - Access Engine Exit state The exit state can assume the following values: NORMAL: The process has been terminated normally and all resources used have been garbage-collected and released. CRASHED: The process was not closed normally.
  • Page 89 BIS 2.3 - Access Engine DMS - Data Management System | en Restart counter If an error causes a process to be terminated, the restart counter increases by 1 and the process restarted. Restarts are attempted until the maximum permitted number of restarts (restart limit) has been reached.

  • Page 90: Server Processes

    | DMS - Data Management System BIS 2.3 - Access Engine Generally, all core system processes (except batch programs) run with the master. If for particular reasons individual processes were terminated, a restart of all master-dependent processes can be initiated using the “Auto start” function. This avoids having to restart the entire system.
  • Page 91 BIS 2.3 - Access Engine DMS - Data Management System | en These processes are controlled and monitored by the master process. Process Features LOGGIFIER Responsible for log messages ACSP-n Responsible for communication with the MAC - there is an ACSP process for each MAC.

  • Page 92: Loggifier

    | DMS - Data Management System BIS 2.3 - Access Engine set /type=batch Specifies that this is a batch process set /batchStart=00:02.00 Specifies that the process should be started 2 minutes after midnight set /batchPeriod=daily Specifies that the process start should be repeated daily Table 10.4 Start time parameters...

  • Page 93: Acsp - Process For Access Control

    BIS 2.3 - Access Engine DMS - Data Management System | en 10.2.3 ACSP - process for access control The various functional areas are connected to the DMS as self- sufficient subsystems via interface processes. The interface processes comprise various interfaces: –...
  • Page 94 | DMS - Data Management System BIS 2.3 - Access Engine The ACSP (Access Control Subsystem Process) is responsible for the connection of the access control system. Its individual tasks are: – The initialization of the access control system.This is carried out by loading all relevant data onto the responsible MAC after a cold start.
  • Page 95 BIS 2.3 - Access Engine DMS - Data Management System | en A query of a location, for example, would be acknowledged by a data telegram, the changing of the location by an event telegram. Data changes Each data change in the DMS triggers an event message to the Loggifier.

  • Page 96: Transactors

    | DMS - Data Management System BIS 2.3 - Access Engine transmitted and buffered in the meantime, and logged accordingly by the ACSP. Locations In the access control system there is only one place where the current location of a person is known with sufficient certainty, and this is the MAC.
  • Page 97 BIS 2.3 - Access Engine DMS - Data Management System | en Transactor are inserted into each application module, e.g. one for access control, one for configuration data management, etc. The client dialogs never execute the updates directly in the database;...
  • Page 98 | DMS - Data Management System BIS 2.3 - Access Engine for access control. The abbreviation ACTA stands for Access Control Transactor. The transactor receives the update requests from the dialogs and executes all necessary actions in the database. It then creates a corresponding logbook message and sends it to the loggifier.
  • Page 99 BIS 2.3 - Access Engine DMS - Data Management System | en – End/cancellation of work on the request and sent to the loggifier. Calendar library The calendar library is based on Julian dates, including the corresponding conversion functions. This time format makes the applications independent of the special time form of the relevant system.
  • Page 100 100 en | DMS - Data Management System BIS 2.3 - Access Engine – Loading of day models (all or according to a selection scheme) – Update and deletion of day models – Creation of a special day and check as to whether two special days coincide with one another –...

  • Page 101: Aeopc

    BIS 2.3 - Access Engine DMS - Data Management System | en 101 The following figures show information pages using the example of the ACTA transactor. These can be invoked with the corresponding commands. 10.2.5 AEOPC The AEOPC server is a process that is provided by the DMS but can only be started from the BIS.

  • Page 102: Report Server (Reps)

    102 en | DMS - Data Management System BIS 2.3 - Access Engine connection in the Access Engine system between the clients and the server. 10.2.7 Report Server (REPS) The REPS creates all requested reports centrally on the server. It receives a corresponding request from the client via http. The REPS checks these and creates the report.

  • Page 103: State Information Process (Sipserver)

    BIS 2.3 - Access Engine DMS - Data Management System | en 103 10.2.8 State Information Process (SIPServer) All device and personal/card status information is collected and stored here and can be called up via the OPC connection and displayed as event messages.

  • Page 104: Time Attendant Account Exchange (Taccexc)

    104 en | DMS - Data Management System BIS 2.3 - Access Engine 10.2.9 Time Attendant Account Exchange (TAccEXC) When using the door model 06, where only two readers are configured for the recording of booking times, the TAccEXC sends the collected bookings to these readers at predefined times and forwards them to an external time management system.

  • Page 105: Lock-Out Process (Lop)

    BIS 2.3 - Access Engine DMS - Data Management System | en 105 In addition to the type designation, these entries distinguish themselves from the other processes by the additional parameters batchStart and batchPeriod, which determine the time of day and the intervals at which this process is started by the master.

  • Page 106: Cleanup Utility (Clu)

    106 en | DMS - Data Management System BIS 2.3 - Access Engine the visitor data is deleted. The cleanup utility searches the Visitors table periodically and deletes the expired data records in all relevant tables including Persons, AuthPerVisitor, etc.

  • Page 107: Backup

    BIS 2.3 - Access Engine DMS - Data Management System | en 107 10.3.6 Backup This batch process creates an up-to-date database extract and backs up the system parameters of the MICOS branch in the registry. These backups are saved in the C:\MgtS\Access Engine\AC\Backup (standard installation path) directory.

  • Page 108: Mac - Main Access Controller

    108 en | MAC - Main Access Controller BIS 2.3 - Access Engine MAC - Main Access Controller 11.1 Functions The MAC has many functions which are absolutley essential to access control at entrances. 11.1.1 Basic functions – Download of reader programs from the DMS above it.

  • Page 109: Data Defintions

    BIS 2.3 - Access Engine MAC - Main Access Controller | en 109 Tracking how often a PIN code has been incorrectly entered. – Interfacing with alarm systems (e.g. UGM) and alarm suppression. – Counting how many personnel are in a certain area.
  • Page 110 110 en | MAC - Main Access Controller BIS 2.3 - Access Engine Table-Nr. Name Description MESSAGETEXTS Definition of message numbers and event texts MESSAGEACTIONS Definition of Actions AREAS Definition of Areas DEVICES Definitionof devices Definition of entrances (Registration and...

  • Page 111: Operating The Mac

    BIS 2.3 - Access Engine MAC - Main Access Controller | en 111 These tables are present on e very MAC system, but may be empty depending on the configuration. The master controller of all data is always the superior system, i.e. in general the Access Engine DMS.

  • Page 112: Warm Start

    112 en | MAC - Main Access Controller BIS 2.3 - Access Engine then the MAC will be restarted. Not until the MAC has been shut down completely will its corresponding service be terminated. Terminating the service "AUTO_MAC". With this option the safety check and termination message are not displayed.

  • Page 113: Process Control

    BIS 2.3 - Access Engine MAC - Main Access Controller | en 113 NOTICE! Depending on the amount of data, but particularly if there are many personnel and badge data, loading the database can take some hours. During this period those access control functions which are exclusively MAC-based (e.g.
  • Page 114 114 en | MAC - Main Access Controller BIS 2.3 - Access Engine Reset restart count Resets the restart count to "0". Start task Starts the selected process (only active if the process is not running already). Restart task Halts and restarts the selected process (only active if the process is already running ).

  • Page 115: The Processes Of The Mac

    BIS 2.3 - Access Engine MAC - Main Access Controller | en 115 start. The trace-level, which governs how many messages are generated, can be set on-the-fly here also. After a restart the process will resume with the default level.

  • Page 116: Mac-Process: Master

    116 en | MAC - Main Access Controller BIS 2.3 - Access Engine 11.5.1 MAC-Process: Master Starts, stops and controls the run-time of all processes in the process table and their subprocesses. The MAC startup process consists of the following phases: Phase 1 Initialization of all internal data.

  • Page 117: Mac-Process: System

    BIS 2.3 - Access Engine MAC - Main Access Controller | en 117 Figure 11.3 Console of the Messenger process 11.5.3 MAC-Process: System This process is responsible for all MAC-database changes coming, for example, from the DMS. Device statuses (e.g from LACs or readers) are entered in the database by this process.

  • Page 118: Mac-Process: Dms

    118 en | MAC - Main Access Controller BIS 2.3 - Access Engine Figure 11.5 Console of the AC process 11.5.5 MAC-Process: DMS The DMS process on the MAC forms the interface to the Access Engine DMS. All communication between the systems passes through this interface (DMS - ACSP).

  • Page 119: Mac-Process: Lac

    BIS 2.3 - Access Engine MAC - Main Access Controller | en 119 Figure 11.6 Console of the DMS-Process 11.5.6 MAC-Process: LAC This process displays on its console the message telegrams to and from connected LACs. At the same time it fowards important information from the DMS and MAC to the LACs, so that these are capable of making basic access control decisions on their own.

  • Page 120: Mac-Process: Info

    120 en | MAC - Main Access Controller BIS 2.3 - Access Engine Figure 11.7 Console of the LAC process This dialog can be used for deactivating the communication to individual LACs. This setting should be used with care and only for test purposes as every device-message from the Access Engine System will overwrite the setting.

  • Page 121: Setting Up Video Verification

    BIS 2.3 - Access Engine Setting up Video Verification | en 121 Setting up Video Verification Setting up Video Verification BIS can be configured so as to display a cctv image of the relevant area whenever someone checks in at a particular reader.
  • Page 122 122 en | Setting up Video Verification BIS 2.3 - Access Engine – Depending on the type of camera you wish to use, uncomment the appropriate line by removing the slashes // at the beginning of it, and change the IP- Address in the file to that of the camera you wish to use.
  • Page 123 BIS 2.3 - Access Engine Setting up Video Verification | en 123 – Save the settings by clicking Apply. Change to the menu Locations and start the dialog Tree Structure. – Create a new node in the tree called e.g. Video and select it.
  • Page 124 124 en | Setting up Video Verification BIS 2.3 - Access Engine – Click the New button to choose a document. – Select the list entry Action plan and then click Select. – Open the file VideoVerificationACE.htm, where you previously modified the URLs F.01U.028.713 | V 2.3.0.1 | 2009.11...
  • Page 125 BIS 2.3 - Access Engine Setting up Video Verification | en 125 – Accept the selection by clicking OK. – Save your settings with the Apply button. In the same menu (Locations) switch to the dialog Detector placement. – Here you will find a similar structure view to that in Tree structure.
  • Page 126 126 en | Setting up Video Verification BIS 2.3 - Access Engine – In the Devices field select the entry <ComputerName>/ AccessEngine/Devices. F.01U.028.713 | V 2.3.0.1 | 2009.11 Installation manual Bosch Sicherheitssysteme GmbH...
  • Page 127 BIS 2.3 - Access Engine Setting up Video Verification | en 127 – The Groups field now lists all the readers in Access Engine. Select the reader which you have configured for video verification Bosch Sicherheitssysteme GmbH Installation manual F.01U.028.713 | V 2.3.0.1 | 2009.11...
  • Page 128 128 en | Setting up Video Verification BIS 2.3 - Access Engine – Drag the reader and drop it in the left hand explorer window (location tree). The detectors for this reader now appear in the list field Detectors directly at Location F.01U.028.713 | V 2.3.0.1 | 2009.11...
  • Page 129 BIS 2.3 - Access Engine Setting up Video Verification | en 129 – After this you can delete detectors for which you do not require video verification. Select the readers in the list field Detectors directly at Location and remove them with the button Delete mapping.
  • Page 130 130 en | Setting up Video Verification BIS 2.3 - Access Engine – Right click on the new job and select the option Create Trigger. – In the dialog Create a new Trigger select Address and confirm with OK. F.01U.028.713 | V 2.3.0.1 | 2009.11...
  • Page 131 BIS 2.3 - Access Engine Setting up Video Verification | en 131 – The dialog Address Selection is opened. Select the reader you wish to configure for video verification by clicking Devices in the Devices field then the chosen reader in the Groups field.
  • Page 132 132 en | Setting up Video Verification BIS 2.3 - Access Engine – Right-click the trigger in the left hand list field and select the option Create THEN Control. – A Dialog Create new “THEN” Control. is opened. For object choose Message from the combo box and enter (if you wish) a comment as a label for the control.
  • Page 133 BIS 2.3 - Access Engine Setting up Video Verification | en 133 – Confirm your choice with OK and make sure that the option Use alarm address is activated for the control. Save all changes and load the configuration via the BIS Manager.
  • Page 134 134 en | Setting up Video Verification BIS 2.3 - Access Engine – ... accept it by double-clicking in the Status column of the appropriate row. – The Action plan tab is opened showing the html page with a live picture from the entrance and the database archive photo of the badge owner for comparison.

  • Page 135: Backup And Restore

    BIS 2.3 - Access Engine Backup and Restore | en 135 Backup and Restore 13.1 Standalone-Server 13.1.1 Backup Daily configuration backups are made automatically by the system. In addition, a manual configuration backup is recommended after significant changes to the configuration have been made.

  • Page 136: Restore

    136 en | Backup and Restore BIS 2.3 - Access Engine Depending on the systems components, which have to be saved, the backup process creates a folder structure, which includes the folder CardholderImages (with the pictures from the persons of the access control system) and Layouts (with the layouts created by the badge designer), as follow.
  • Page 137 BIS 2.3 - Access Engine Backup and Restore | en 137 Now click Restore and confirm the next message. The next dialog will inform you about the progress of the action. After the configuration has to be restored the system can be started immediately confirming the finish message.

  • Page 138: Remote- And Login-Server

    138 en | Backup and Restore BIS 2.3 - Access Engine 13.2 Remote- and Login-Server 13.2.1 Backup The Backup can be started using the BIS manager running on the Login Server and is the same like described for the Standalone Server.
  • Page 139 BIS 2.3 - Access Engine Backup and Restore | en 139 – Start the tool BackupAndRestore.exe in the folder C:\MgtS\Access Engine\AC\Bin (= default installation path) with a double click. – In the dialog choose the option Restore from. – Search for the backup file using the –...
  • Page 140 140 en | Backup and Restore BIS 2.3 - Access Engine – The restore steps will be displayed in the lower field. In detail there are the following steps to restore the system: stopping MAC stopping ACE import registry import database...

  • Page 141: Troubleshooting

    BIS 2.3 - Access Engine Troubleshooting | en 141 Troubleshooting 14.1 User administration 14.1.1 Dialog system of the Access Engine does not start When the Access Engine is called, an empty Internet Explorer is displayed. Reason: The workstation is not set up as an Access Engine workstation.

  • Page 142: Empty Access Engine Internet Explorer

    142 en | Troubleshooting BIS 2.3 - Access Engine No workstation profile or an invalid profile was assigned to the workstation: – In the ACE workstation rights Configuration Browser dialog, check whether the correct workstation profile has been assigned to the respective workstation.

  • Page 143: System Settings

    BIS 2.3 - Access Engine Troubleshooting | en 143 14.2 System settings 14.2.1 Change the timezone If the timezone of the BIS server will be changed, messages coming from the access system have a wrong time stamp as long as the system is restarted.

  • Page 144: Date And Time Formats

    144 en | Troubleshooting BIS 2.3 - Access Engine After these changes a reboot is required. 14.3 Date and time formats To the supported languages of the access control system the following date and time formats are used. German dd.MM.yyyy HH:mm:ss...
  • Page 145 BIS 2.3 - Access Engine Troubleshooting | en 145 d=day, M=month, y=year, H=hour(24), if h=hour(12) then tt specifies AM or PM, m=minute, s=second NOTICE! The week day list of the Access Engine dialog Holidays is determined by the regional settings of the operating system.
  • Page 146 146 en | Index BIS 2.3 - Access Engine Index Loggifier 92 F.01U.028.713 | V 2.3.0.1 | 2009.11 Installation manual Bosch Sicherheitssysteme GmbH...
  • Page 148 Bosch Sicherheitssysteme GmbH Robert-Koch-Straße 100 D-85521 Ottobrunn Germany Telefon +49 89 6290-0 +49 89 6290-1020 www.boschsecurity.com © Bosch Sicherheitssysteme GmbH, 2009...

Table of Contents