Schneider Electric

March 2019
Legal Information
The Schneider Electric brand and any registered trademarks of Schneider Electric Industries
SAS referred to in this guide are the sole property of Schneider Electric SA and its
subsidiaries. They may not be used for any purpose without the owner's permission, given in
writing. This guide and its content are protected, within the meaning of the French intellectual
property code (Code de la propriété intellectuelle français, referred to hereafter as "the
Code"), under the laws of copyright covering texts, drawings and models, as well as by
trademark law. You agree not to reproduce, other than for your own personal, noncommercial
use as defined in the Code, all or part of this guide on any medium whatsoever without
Schneider Electric's permission, given in writing. You also agree not to establish any hypertext
links to this guide or its content. Schneider Electric does not grant any right or license for the
personal and noncommercial use of the guide or its content, except for a non-exclusive
license to consult it on an "as is" basis, at your own risk. All other rights are reserved.

Electrical equipment should be installed, operated, serviced and maintained only by qualified
personnel. No responsibility is assumed by Schneider Electric for any consequences arising
out of the use of this material.

As standards, specifications and designs change from time to time, please ask for
confirmation of the information given in this publication.
Trademarks and registered trademarks are the property of their respective owners.
Table of Contents
Introduction .................................................................................................... 5
Record Types ..................................................................................................................... 5
Release History .............................................................................................. 6
Version 1.0.0.0 .................................................................................................................... 6
Version 1.0.1.0 .................................................................................................................... 6
Version 1.0.2.0 .................................................................................................................... 6
Version 1.0.3.0 .................................................................................................................... 7
Version 1.0.4.0 .................................................................................................................... 7
Version 1.0.5.0 .................................................................................................................... 8
Version 1.0.6.0 .................................................................................................................... 8
Version 1.1.0.0 .................................................................................................................... 9
Version 1.1.2.7 .................................................................................................................. 10
Version 1.2.1.0 .................................................................................................................. 11
Version 1.2.1.5 .................................................................................................................. 12
Prerequisites ................................................................................................ 13
INet Device Support .......................................................................................................... 13
Applications....................................................................................................................... 13
Licensing ........................................................................................................................... 13
Programming .................................................................................................................... 14
Software Installation ..................................................................................... 15
INet Database Transition Tool .......................................................................................... 15
Security Expert Data Sync Service ................................................................................... 15
Transition Overview ..................................................................................... 15
Before the Transition ........................................................................................................ 16
PIN Duplication ........................................................................................................... 16
After the Transition ........................................................................................................... 16
Attach the DCU Save Files ......................................................................................... 17
Software Configuration ................................................................................. 18
Export Settings ................................................................................................................. 18
Export Type ................................................................................................................ 20
Record Types ................................................................................................................... 20
Users .......................................................................................................................... 20
Programming .............................................................................................................. 21
Data Sync Service ............................................................................................................ 21
Event Logs .................................................................................................................. 21
Running the Transition ................................................................................. 21
A Single Sync of All Record Types Then a Continuous Sync of Users Only ................... 22
Run a One-Off Transition of All Records .................................................................... 22

| March 2019 3
 Running a Periodic Transition of Users ...................................................................... 23
A Single Sync of All Record Types ................................................................................... 23
A Continuous Sync of All Record Types ........................................................................... 24
Field Mapping and Programming ................................................................. 25
INet Operators to Security Expert Operators.................................................................... 25
INet DCUs to Security Expert Controllers......................................................................... 26
INet Schedules to Security Expert Schedules .................................................................. 26
INet MCUs to Security Expert Reader Expanders............................................................ 27
INet Zones to Security Expert Areas ................................................................................ 28
INet Points to Security Expert Inputs ................................................................................ 28
INet Points to Security Expert Outputs ............................................................................. 29
INet Door ATS as Security Expert Door Types ................................................................ 31
INet Doors to Security Expert Doors ................................................................................ 32
Security Expert Smart Readers ........................................................................................ 33
INet SCU 1284 Reader Configuration ........................................................................ 34
INet DPU 7920 Reader Configuration ........................................................................ 35
INet DPU 7910 Reader Configuration ........................................................................ 35
INet Groups to Security Expert Access Levels ................................................................. 36
INet Individuals to Security Expert Users ......................................................................... 36
Known Issues, Limitations and Future Releases.......................................... 38
Technical Reference .................................................................................... 39
Records............................................................................................................................. 39
Operators .................................................................................................................... 39
Controllers .................................................................................................................. 39
Schedules ................................................................................................................... 39
Reader Expanders ...................................................................................................... 41
Areas .......................................................................................................................... 42
Inputs .......................................................................................................................... 42
Outputs ....................................................................................................................... 43
Door Types ................................................................................................................. 44
Doors .......................................................................................................................... 45
Smart Readers............................................................................................................ 46
Access Levels ............................................................................................................. 47
Users .......................................................................................................................... 47
Calculations ...................................................................................................................... 48

4 | March 2019
Introduction Schneider Electric INet Database Transition Guide

Introduction
The INet Database Transition Tool exports existing data and programming from an INet
database and formats it for import into Security Expert.
How it Works

The INet Database Transition Tool retrieves data such as DCUs, doors and individuals from
an INet database and exports it to CSV. In the process, the CSV files get formatted in a way
that allows the equivalent INet programming to be achieved in Security Expert.

The Security Expert Data Sync Service then reads the data in these CSV files and uses the
Security Expert SOAP Service to import the records into Security Expert. The entire transition
process can be configured and controlled from the INet Database Transition Tool despite it
being two services that run the transition process.

Both the INet Database Transition Tool and the Security Expert Data Sync Service can be set
to run periodically, allowing the service to run in the background and transition any changes
made in INet to the corresponding records and programming in Security Expert.

Record Types
The following records are currently supported by the transition process:

Operators Operators

DCUs Controllers

Personnel Schedules

Door Schedules Schedules

Door ATS

MCUs Reader Expanders

Zones Areas

DI & DA Points Inputs

DO Points Outputs

Door ATS Door Types

Doors Doors

Doors Smart Readers

Door Groups Access Levels

Individuals Users

See Field Mapping and Programming (see page 25) for more details.

| March 2019 5
Schneider Electric INet Database Transition Guide Release History

Release History
This section includes information on the changes and enhancements made in each version.

Version 1.0.0.0
This build was created for demonstration and testing purposes only and exported the following
INet records to CSV:
 INet DCUs to Security Expert Controllers
 INet MCUs to Security Expert Doors
 Security Expert Smart Readers
 INet Personnel Schedules to Security Expert Schedules
 INet Groups to Security Expert Access Levels
 INet Individuals to Security Expert Users

Version 1.0.1.0
New Features:
 Added the option to connect to the INet Database by either Windows Authentication, or
SQL Server Authentication.
 All local SQL Server Instances are now listed in a drop down making it simpler to locate
the SQL Instance that contains the INet Database.
 All databases on the selected SQL Server Instance are now listed in a drop down making
it simpler to locate the INet Database.
 Event logging has been added to the Schneider Electric Security Expert log in the
Event Viewer.

Version 1.0.2.0
New Features:
 Added Security Expert smart reader records to support 4 doors per controller as the case
for the INet SCU1284.
 Added the requirement that a credential type named Hex Card Number with the Format
set to Hexadecimal exist in Security Expert prior to the transition process.

Feature Enhancements:
 Individual card numbers are exported in a hexadecimal format to be assigned to the Hex
Card Number credential type.
 Assigned the Hex Card Number credential type to all smart readers.

6 | March 2019
Release History Schneider Electric INet Database Transition Guide

Version 1.0.3.0
New Features
 Added the ability to specify a TCP port number in the SQL Server Instance field of the
transition tool in order to allow connection to a server that sits behind a
router/modem/firewall.
 Added a help button for the Authentication Mode and SQL Server Instance fields.

Issues Resolved
 Resolved an issue related to retrieving databases on the selected SQL Server Instance.
 Resolved an issue with some card numbers not being exported from the INet database.
 Resolved an issue with the application icon not displaying correctly.
 Resolved an issue with the start/stop button incorrectly displaying the status of the
service.

Version 1.0.4.0
New Features
 Placeholder Door Position and REX Inputs are imported to Security Expert.
 Door types of Card and Card and PIN are now assigned to the door according to the
Door ATS Action in INet.
 Implemented the Unlock Schedule functionality on doors in Security Expert to handle
cases where the Door ATS Action in INet changes from Lock to Unlock to Lock. There
are remaining limitations of the handling of the INet Door ATS feature, see Known Issues
and Limitations (see page 38).
 The Unlock Door on REX option is now enabled in Security Expert according to the Door
ATS Action in INet.

Feature Enhancements
 Modified naming conventions of records retrieved from the INet database to form a
uniform and user-friendly Security Expert system.
Issues Resolved
 Resolved an issue related to missing smart reader records.
 Fixed an issue of being unable to retrieve and list the local SQL Server Instances on a
machine with a 32-bit Operating System.
 Fixed an issue related to the SQL Server Instance Name and Database Name fields not
populating upon opening the transition tool.

| March 2019 7
Schneider Electric INet Database Transition Guide Release History

Version 1.0.5.0
New Features
 Placeholder Lock Outputs are now imported to Security Expert.
 Added Command I/NET = 1 to all controllers in Security Expert.
 In Security Expert, a reader expander record is created per DPU 7910A in INet, as well as
the associated records such as Doors and I/O.

Feature Enhancements
 Modified naming conventions of records retrieved from the INet database to create a
uniform and user-friendly Security Expert system.
 Modified Module Input values for inputs in Security Expert where an INet 1284 DPU is
supported in both single or double addressing mode.
 Modified naming convention on Security Expert Inputs.
 Added a default file directory to the CSV Output Directory field which matches the
default File Directory in the provided Data Sync settings.xml file.

Version 1.0.6.0
New Features
 Added support for the INet SCU 1200 where one reader expander record is created in
Security Expert per 1200 as well as the associated inputs.
 Added a log file named ManualChanges.txt to the install directory (C:\Program Files
(x86)\Schneider Electric\Database Transition Tool if you accept the defaults during
installation) which logs any issues during the transition process that will need to be
addressed once the records are imported to Security Expert.
 Added a System Area per controller in Security Expert.

Feature Enhancements
 Modified naming conventions on to make it simpler for the operator to find which record in
Security Expert corresponds to which record in INet.
 Replaced placeholder inputs and outputs with I/O Points retrieved from the INet database.
 Assigned the System Areas to Inputs.
 Door Position and REX Inputs are now assigned to doors in Security Expert based on
the Sense Switch and Exit Push Button in INet.
 A Lock Output is now assigned to doors in Security Expert based on the Strike in INet.

Issues Resolved
 Resolved an issue related to the Module Input and Module Output addresses being
incorrectly retrieved from INet.
 Resolved an issue related to missing input and output records for the INet 1284 DPU in
the situation where there is a single door on the DPU while in double-addressing mode.
 Resolved an issue where doors with no Unlock Schedule were not being imported into
Security Expert.
 Resolved an issue where incorrect doors and schedules were being assigned to access
levels in Security Expert.
 Resolved an issue where users with no access levels were not being imported into
Security Expert.
 Resolved an issue where some users were being assigned an incorrect End date and
time in Security Expert.

8 | March 2019
Release History Schneider Electric INet Database Transition Guide

Version 1.1.0.0
New Features
 The antipassback programming in INet is retrieved from the save files implemented in
Security Expert.
 The Door Code functionality in INet is now implemented in Security Expert.
 INet DPU 7920s are now transitioned to Security Expert along with their associated
records and programming.
 INet SCU 1280s are now transitioned to Security Expert along with their associated
records and programming.
 INet DIU 7930s are now transitioned to Security Expert along with their associated
records and programming.
 INet DIU 7940s are now transitioned to Security Expert along with their associated
records and programming.
 Added the option to Enable Event Logging thus if required, logging to the Windows
Event Viewer can be disabled.
 Error messages related to setting up the tool are now displayed in bottom left corner of
the main window prior to starting the service.

Feature Enhancements
 More door programming is being transitioned, where configuration from the INet DCU
save files are programmed on the doors used to populate further door related options in
Security Expert.
 The Exit Reader setting for a door in INet is retrieved from the save files and used to
configure the Reader One Mode for smart reader records in Security Expert.
 More areas are being transitioned, where the antipassback Entry Zone and Exit Zone on
a Door are retrieved from the INet DCU save files and added as areas in Security Expert.
 Internal I/O Points are now being transitioned to Security Expert.
 Optimized the time it takes to establish a connection to the INet database
 Improved events being logged in the Windows Event Viewer such as more specific error
messages and further information on the data being exported from the INet database.
 Added further logging to the ManualChanges.txt log in the install directory which identify
missing programming.

Issues Resolved
 Resolved an issue of doors not being transitioned to Security Expert if they were assigned
only internal I/O Points in INet.
 Resolved an issue of smart readers not having the correct Expander Address for devices
in double-addressing mode starting at address one.

| March 2019 9
Schneider Electric INet Database Transition Guide Release History

Version 1.1.2.7
New Features

The Door ATS Schedules in INet are now used to generate the following records in the
transition process:
 Door Type records in Security Expert where one or more door types is created for
each door.
 Operating Schedule records that are assigned to the door types.
 Antipassback can now be reset by schedule where the data is retrieved from the APB
Reset ATS Action.
 The Sec/Code ATS Action is now supported as a door type with the Reading Mode
set to Card or PIN in Security Expert.
 The Lock ATS Action is now supported as a door type with the Reading Mode set to
Reserved 3 with the Door REX Enabled option disabled.
 Doors without any ATS schedules are assigned the default Door Type of Card in
Security Expert.
Feature Enhancements
  The Unlock Schedule on a door and Access Level Door Schedule on an access
level now handle up to eight periods when transitioned to Security Expert.

Issues Resolved
 Resolved an issue of incorrect assignment of outputs to doors for the INet DPU 7920.
 Resolved an issue with how antipassback programming in INet was being was being
implemented in Security Expert.
 Resolved an issue of duplicate antipassback areas being created from the INet DCU save
files as the Entry Zone and Exit Zone can be duplicated across different controllers in
INet. The ID of the door is now included in the area name to ensure every record is
unique as required by the Data Sync Service.
 Resolved an issue of duplicate doors being exported from the INet database as the name
of a door is not necessarily unique across controllers in INet. The ID of the door is now
included in the door name to ensure every record is unique as required by the Data Sync
Service.
 Resolved an issue where doors with no I/O Points were not being retrieved from the INet
database.

10 | March 2019
Release History Schneider Electric INet Database Transition Guide

Version 1.2.1.0
New Features
 The Security Expert Data Sync Service can now be configured and run directly from the
INet Database Transition Tool.
 Partial synchronization is now available with the Export Type option which allows the
export of either very record type or users only on each sync.
 A live (rolling) event log has been added to display events generated by the INet
Database Transition Service and the Security Expert Data Sync Service Operators.

Feature Enhancements
 The SQL Server Authentication Password and Security Expert Operator Password
are now encrypted in the settings.xml file. This is backwards compatible, where builds
without encryption will have the existing password encrypted password upon opening the
INet Database Transition Tool window or starting the service from the Windows Service
Manager.
 The DCU Save Files are checked against the controllers in the INet database and a
warning is issued if there is a mismatch in the DCU records.
 The transition of antipassback programming is now optional with the Include
Antipassback Programming checkbox available in the transition tool and for sites not
using antipassback, leaving this option disabled will reduce the transition time as
particular data checks are skipped. This option can also be used to reduce transition time
on sites where antipassback has been programmed in INet but it is not a requirement that
it be transitioned to Security Expert.
 The transition of the INet Door Code programming is now optional with the Include Door
Code checkbox available in the transition tool.
 Modified the way antipassback programming is resolved where these changes make the
Security Expert Door Type export process significantly faster.
 Modified formatting during the export of Groups from INet which make the Data Sync
import process faster.
 Modified formatting during the export of Individuals from INet which make the Data Sync
import process faster.
 Existing Schedules and Door ATS in INet that run 24/7 are no longer being transitioned
and any records that reference these schedules are assigned the Security Expert built-in
default value of Always. This significantly reduces the number of schedule records being
imported into Security Expert making transition process faster and providing a cleaner
solution long term.

Issues Resolved
 Resolved an issue where Smart Readers were failing to export if the number of INet DCU
Save Files did not match the DCU records in the database one-for-one.
 Resolved an issue with the transition of INet MCUs to Security Expert Reader Expanders
where duplicate names were causing records to get overwritten during the sync process.
 Resolved an issue where breaks in the Individual data exported from the INet database
were causing the Data Sync Service to halt operation.
 Resolved an issue where some I/O points were being retrieved incorrectly from the DCU
Save Files.
 Resolved an issue where SQL Server Authentication was not allowing connection to the
INet database.
 Resolved an issue where, when using SQL Server Authentication, the Password to
connect to the instance was not being saved.
 Resolved an issue where, if the Enable Logging option was disabled events were still
being logged.

| March 2019 11
Schneider Electric INet Database Transition Guide Release History

Version 1.2.1.5
New Features
 More than one card can now be transitioned to a User in Security Expert.
 Doors assigned directly to Individuals are now being transitioned to Security Expert
where one Access Level is created for each Door and the Schedule on the Door in INet
is transitioned to the User Access Level Schedule in Security Expert.
 There is an Allow PIN Duplication option now available on the Record Types tab in the
INet Database Transition Tool window and enabling this option allows Individuals that
have the same PIN in INet to be imported to Security Expert. In order for this to function
the Site Security Enhancements must be setup in Security Expert prior to beginning the
transition. See PIN Duplication (see page 16) for more details.
 When the First Key Mode is set to Unlock in INet the Schedule Operates Late to Open
option is enabled on the Door in Security Expert with the relevant Unlock Schedule
assigned.
Feature Enhancements
 The Doors created in Security Expert now have the same Name as seen on the Doors
page in INet. Previously, the Name of the Resident I/O Point was being used which was
causing a discrepancy across systems for sites where the Resident I/O Point for the
door was named differently to the Door record itself.
 Many unassigned Door Types are no longer transitioned to Security Expert and where
possible the default Door Types are assigned to Doors instead, reducing the amount of
time it takes to transition a site.
 Schedules with duplicate days and time periods are no longer being transitioned to
Security Expert where instead, a single instance of that schedule is created and
referenced by multiple records if required. In addition, many unassigned Schedules are
no longer transitioned to Security Expert which reduces the amount of time it takes to
transition a site.
Issues Resolved
 Resolved an issue where Doors on Access Levels were incorrectly being assigned
Always as the Schedule in Security Expert instead of applying the Schedule assigned to
the Group Door in INet.
 Resolved an issue where Individuals that had their Record Type set to Permanent in
INet were incorrectly being assigned a Start and Expiry on the User record in Security
Expert. This has been resolved by continuing to transition the Begin Date and End Date,
however in Security Expert the Start and Expiry checkboxes are only enabled if the
Record Type is set to Temporary in INet.
 Resolved an issue where User Access Levels were set to expire in Security Expert even
if the Record Type on the Group was set to Permanent in INet.
 Resolved an issue where, if there were two Groups by the same name across different
Tenants in INet, the Access Levels were not transitioning correctly to Security Expert.
This has been resolved by appending the Tenant ID to the beginning of the Name of the
Group to create a unique Name for the Access Level to be transitioned. This fix also
resolves an issue where some Users in Security Expert were missing Access Levels.
 Resolved an issue where some Door ATS records in INet were generating incorrect Start
and Expiry times on Schedules transitioned to Security Expert.
 Resolved an issue where some Doors were being transitioned to Security Expert with
<not set> as the Door Type.

12 | March 2019
Prerequisites Schneider Electric INet Database Transition Guide

Prerequisites
This section includes information on licensing requirements and record prerequisites. Take a
moment to read the material in this section before proceeding with the installation.

INet Device Support

The following Distributed Control Units (DCUs) are supported by the INet Database
Transition:
 7793 MCI (Micro Control Interface)
 7798 MCI (I/Site LAN)
The following Micro Control Unit (MCUs) are supported by the INet Database Transition:
 SCU 1284 (Security Control Unit)
 SCU 1280 (Security Control Unit)
 SCU 1200 (Security Control Unit)
 DPU 7910 (Door Processing Unit)
 DPU 7920 (Door Processing Unit)
 DIU 7930 (Door Input Unit)
 DIO 7940 (Door Input Output)

Applications
The following applications will need to be installed:
 An operational Security Expert system with software version 4.2.251.15 or higher. For
more information, refer to the Security Expert Installation Guide.
 An installation of the Security Expert SOAP Integration Service version 1.2.0.19 or higher.
For more information, refer to the Security Expert SOAP Installation Guide.
 An installation of the Security Expert Data Sync Service version 2.0.5.7 or higher. For
more information refer to the Security Expert Data Sync Service Integration Guide.

Licensing
The following licensed features will need to be applied to your SSN.
 A Data Sync Service license.
 A Security Expert SOAP Interface license.
 A Client Connection available for use by the Data Sync Service. The base license
includes a single client connection to allow access to the Security Expert client. Additional
client licenses are added automatically when SOAP and/or the Data Sync Service are
enabled on the SSN.
 The required number of Doors (base license includes 50).
 The required number of Third Party Readers (base license does not include any). One of
these license items is required for each door for each direction that is in use in INet.

| March 2019 13
Schneider Electric INet Database Transition Guide Prerequisites

Programming
It is strongly recommended that the programming in INet be cleaned up before running the
transition. This may include:
 Correcting invalid programming
 Deleting obsolete records
 Ensuring records are not empty (such as a schedule with a name but no days/times)
Doing this beforehand will reduce the chance of warnings or errors being presented during the
transition process and ensure that the Security Expert system is clean, easy to understand
and reflective of the functionality that is in use on the site.

14 | March 2019
Software Installation Schneider Electric INet Database Transition Guide

Software Installation
The following section outlines the applications you must install in order to get the Database
Transition process up and running.
Ensure all prerequisites (see page 13) have been met before proceeding.

INet Database Transition Tool

To install the INet Database Transition Tool:
1. Run the supplied INetDatabaseTransitionTool.msi file to launch the install wizard.
2. Click Next to continue.
3. Select whether it is installed for everyone who uses the PC, or just your user and click
next to install to the default location (C:\Program Files (x86)\Schneider Electric\INet
Database Transition Tool).
4. If you are required to install the service in a different location, click Browse and navigate
to the required file path.
5. Click Next to begin installation.
6. Once the installation is complete, click Close.

Security Expert Data Sync Service

To install the Security Expert Data Sync Service:
1. Run the supplied SecurityExpertDataSyncService.msi file to launch the install wizard.
2. Click Next to continue.
3. Select whether it is installed for everyone who uses the PC, or just your user and click
next to install to the default location (C:\Program Files (x86)\Schneider Electric\Data Sync
Service).
4. If you are required to install the service in a different location, click Browse and navigate
to the required file path.
5. Click Next to begin installation.
6. Once the installation is complete, click Close.

For more information refer to the Security Expert Data Sync Service Integration Guide.

Transition Overview
This section outlines the manual configuration that is required in Security Expert both before
and after the transition.

| March 2019 15
Schneider Electric INet Database Transition Guide Transition Overview

Before the Transition

The points below outline the prerequisites that must be setup in Security Expert prior to
beginning the transition process.

Existing Records
The following records will need to exist in Security Expert before proceeding with the transition
process:
 A Site (under Programming | Sites) that is solely for use in the INet transition process.
 A Credential Type (under Sites | Credential Types) named Hex Card Number with the
Format set to Hexadecimal to store card numbers retrieved from INet.
Settings

It is a highly recommended that the default Admin operator is used for the transition process.
This operator must have the Show PIN numbers for Users option (under Global |
Operators) enabled for the sync process to be successful.

PIN Duplication
Security Expert does not allow more than one User to have the same PIN (on a single site)
without enabling Site Security Enhancement.

When the Site Security Enhancement functionality is enabled User PINs cannot be viewed
(they are replaced with stars) even if an Operator has the Show PIN numbers for Users
option enabled.

To enable PIN duplication in Security Expert:

1. Navigate to Global | Sites.
2. Select the Site which will be used in the transition.
3. Click on the Site Defaults tab.
4. Enable the Require Dual Credential for Keypad Access option. This will enable the
Allow PIN Duplicate option automatically.
5. Click Save.

The Site Security Enhancement requires that a unique User ID is populated for every User
on the site and in the case of the INet transition, this is assigned automatically. When the
Allow PIN Duplication option is enabled in the INet Database Transition Tool, the User ID
credential in Security Expert is populated with a unique ID (Individual ID and the Individual
Tenant ID separated by a dash) during the transition process.

After the Transition

The following must be configured in Security Expert after the transition process:
 Every Operator (under Global | Operators) transitioned from INet will by default have
their Password set to blank and their Role set to No Access. An existing Security Expert
operator with the Administrator Role will need to set both of the aforementioned settings
before the transitioned INet Operators can access Security Expert.
 The DCU Controllers transitioned from INet will not have the following details that are
required to get the Controller online:
 IP Address
 Serial Number
 Download Server

16 | March 2019
Transition Overview Schneider Electric INet Database Transition Guide

Attach the DCU Save Files

One Controller is created in Security Expert for each DCU that has been programmed in INet
and the DCU .SAV file for each of these controllers must be added directly to Security Expert.

To load save files into Security Expert:

1. Navigate to Sites | Controllers.
2. Select a Controller and scroll down to the Download Binary Blob section.
3. Click on the Browse button beside the Set the download binary blob from a file field.
4. Navigate to the relevant .SAV file and click Open. The name of the file must match the
DCU address provided in the Name of the transitioned Controller for correct operation of
the firmware.
5. Click Save.
Repeat the steps above for every Controller.

| March 2019 17
Schneider Electric INet Database Transition Guide Software Configuration

Software Configuration
Launch the INet Database Transition Tool (a shortcut is available on the desktop) and setup
the details as outlined in this section.

Export Settings
Click on the Export Settings tab and provide the following:

To configure the Database Transition Tool to export CSV files from the INet database, the
following information must be provided:
 Run This Application Every <value><units> which defines how often the service is to
retrieve records from the INet database.
 Enable Event Logging: When enabled, events are logged in both Windows Event Viewer
(Application and Services Logs | Schneider Electric Security Expert) and the built in
live event log.
When clicking on the Start button for either the INet Database Transition Service or
Security Expert Data Sync Service a message saying, "Do you want to open the live
event log?" will appear. Click Yes to open the live event log, No to continue to start the
service without or Cancel to about the service start process. The live event log can be

18 | March 2019
Software Configuration Schneider Electric INet Database Transition Guide

opened at any time by navigating to the Data Sync Service tab and clicking Open
Live Event Log or alternatively, see the Windows Event Viewer.

It is strongly recommended that the events be reviewed during the import process as
there is important feedback on the setup of the transition tool, the programming in INet and
the status of the transition to Security Expert.
 Authentication Mode: Defines the type of authentication used to access the database.
 Windows Authentication: SQL Server uses the Windows user account to validate
the account name and password.
 SQL Server Authentication: SQL Server uses the login created in the SQL Server
Management Studio. You must enter the Username and Password created for the
login in order to access the database.
 SQL Server Instance Name: From the dropdown, select the name of the local SQL
Server Instance that contains the INet Database. If the SQL Server Instance required is
not available in the dropdown it can be entered into this field manually and must be in the
format <Server Name>\<Instance Name>. Depending on the scenario this field may be
formatted as follows:
 Default Local Instance: <Period Character>
 Named Local Instance: localhost\<Instance Name>
 SQL Server Express Instance: .\SQLEXPRESS
 Remote Instance: <IP Address>\<Instance Name>
Where a firewall is used, the SQL Server TCP Port Number must be provided
preceded by a comma following the instance name, for example,
192.168.1.75\MySQLInstance,1433 where default port used by SQL Server is 1433.

 Database Name: From the dropdown, select the INet Database. By default this is set to
INetDb, however all of the databases on the selected SQL Server Instance will be
available for selection in the dropdown.
 INet Save File Directory: Select the file directory in which the INet DCU save files are
stored. If you accepted the defaults during the installation of INet, this will be C:\INET
Seven Data\Sav and the transition tool automatically populates this field out with the
aforementioned file path.

| March 2019 19
Schneider Electric INet Database Transition Guide Software Configuration

Export Type
There are two options as to how the data from INet can to be exported and synced to Security
Expert:
 Users Only on Every Sync: Only Personnel records are exported to from INet.
 Every Record on Every Sync: All record types supported by the transition are exported
from INet.
Choosing an Export Type

To complete a full transition of records supported by the transition tool, select Every Record
on Every Sync. When the Data Sync Service restarts periodically, every record type will be
resynced which results in the following:
 Changes made to any of the record types supported are synced to security expert.
 If manual changes have been made in Security Expert to any of the of records supported
by the transition, those changes will be overwritten.

If manual changes have been made in Security Expert such as setting the Download Server
on the Controller or changing Password and Role of an Operator and you do not want
these changes to be overwritten on resync, the Export Type can be changed to Users Only
on Every Sync from the second sync onward.
Select Users Only on Every Sync to transition only Individual records from INet. Any
changes made to a Individuals in INet will be transitioned to Security Expert when the Data
Sync Service restarts. Again, manual changes made to Users in Security Expert will be
overwritten.

For further details see Running the Transition (see page 21).

Record Types
Click on the Record Types tab to view options related to the record types to be transitioned.

Users
Allow PIN Duplication

Enabling this option allows Individuals that have the same PIN in INet to be imported to
Security Expert. If the transition has not been setup to allow this, when the Data Sync Service
gets to the User import an Error Code 1 will be thrown and that particular user will not be
imported.
For more information see PIN Duplication (see page 16).

Include Custom Data in Transition

To be implemented in a future release.

Include User Images in Transition

To be implemented in a future release.

20 | March 2019
Running the Transition Schneider Electric INet Database Transition Guide

Programming
Antipassback

The transition of antipassback programming is optional and enabling this checkbox will:
 Retrieve all zones from the INet DCU save files where one area record is created for each
Entry Zone and Exit Zone on a door.
 Retrieve all the Antipassback Reset Time values assigned to each door in the INet DCU
save files.
 Build Door Type records for import into Security Expert where the Passback Mode is set
to Hard Passback, Soft Passback or None based on the Individual data in the INet
database. See INet Door ATS as Security Expert Door Types (see page 31) for more
information.
 Build antipassback reset schedules based on the APB Reset Door ATS which are
assigned to Doors in Security Expert.

In combination, it is these records that build the antipassback implementation in Security

Expert. For more information, see INet Zones to Security Expert Areas (see page 28).
Door Codes

The transition of the door code functionality is optional and enabling this checkbox will:
 Creating a designated 'Door Code' access level which contains only the single door with
this door code.
 Create a designated 'Door Code' user which has the Door Code as the PIN and is
assigned the access level mentioned above.

Data Sync Service

Click on the Data Sync Service tab and provide the following:
 SOAP Server Address: If the Security Expert SOAP Service was installed with the
default port numbers during installation the SOAP address provided can be used, if not,
the port number must be modified as per the installation.
 Security Expert Site ID: The database ID of the site being used for the transition. In
Security Expert navigate to Global | Sites and below the toolbar the Database ID is
displayed beside the Name of the site.
 Username: Set to Admin.
 Password: The password associated with the admin operator.
The operator being used for the transition must have their Role set to Administrator and
the Show PIN Numbers for Users option switched on.

Event Logs
To view the live event log, click Open Live Event Log. This log window displays live events
generated by both the INet Database Transition Service and the Security Expert Data Sync
Service. This log window is capped at 5000 events, when this number is exceeded the oldest
events will be deleted as new events are logged.

To view the Data Sync Service log file, click Open Data Sync Log File. This will open the
log.txt file which stores events generated by the service. These files provide a means to
review the events at a later date as there is no cap on the number of events being stored.

Running the Transition

| March 2019 21
Schneider Electric INet Database Transition Guide Running the Transition

This section outlines how to setup and run the transition process. There are three different
ways in which data may be synced to Security Expert.

The Security Expert Data Sync Service must be installed before proceeding, see Security
Expert Data Sync Service (see page 15) for installation instructions.

It is strongly recommended that the events be reviewed during the transition process as
there is important feedback on the setup of the export of data from INet and the status of the
import to Security Expert. The built in live event log can be used, alternatively, open the
Windows Event Viewer and navigate to Application and Services Logs | Schneider
Electric Security Expert.

A Single Sync of All Record Types Then a Continuous Sync of

Users Only
Running this process is ideal in the situation where a one-off transition of data from INet to
Security Expert is to take place with the exception of Individuals who may have their records
modified in INet after the initial transition has taken place.

This configuration would be used in the situation where the hardware and access related data
in INet is setup exactly as required in Security Expert. It allows Individual records to be
modified in INet and periodically updated in Security Expert while ensuring that every other
record type transitioned can be modified manually in Security Expert without being overwritten
with data from INet.

Run a One-Off Transition of All Records

1. Fill out the required details as per the Software Configuration section (see page
Software Configuration (see page 18)).
2. On the Export Settings tab, set the Export Type to Every Record Type on Every Sync.
3. If any of the optional programming is to be transitioned (see Record Types (see page 20))
configure this now.
4. Click Start on the INet Database Transition Service.
5. A prompt to open the live event log will be presented. Click Yes to view details of the
export.
6. Once an Export Complete event has been logged, click Stop on the INet Database
Transition Service button. Leave the live event log open as it will be required for the
steps that follow.
7. Select the Data Sync Service tab and fill out the requires details (see Data Sync Service
(see page 21)).
8. Click Create Data Sync Service Settings File. This will generate the required setup for
the Data Sync Service to add records to Security Expert.
9. Click Start on the Security Expert Data Sync Service.
10. To view details of the sync, process see the live event log.
11. Once the sync is complete (a Next sync will begin at message will be logged), click Stop
on the Security Expert Data Sync Service.
12. At this point, a sync of all of the supported record types have been transitioned to Security
Expert. Setting up an automatic periodic transition of users will allow Individuals to be
modified in INet and have their data updated automatically in Security Expert.

22 | March 2019
Running the Transition Schneider Electric INet Database Transition Guide

Running a Periodic Transition of Users

1. On the Export Settings tab change the Export Type to Users Only on Every Sync.
2. Click Start on the INet Database Transition Service.
3. If the live event log is not open, a prompt to open it will be presented. Click Yes to view
details of the export. Leave this service running.
4. Select the Data Sync Service tab and click Create Data Sync Service Settings File.
This will generate a new file with Data Sync Service settings required to sync only
Individual data to Security Expert.
5. Click Start on the Security Expert Data Sync Service.
Individual data INet will periodically be synced to Security Expert. For instance, if the transition
tool is set to Run This Application Every 1 Minutes (at the top right of the window),
Individual data will be retrieved from INet every minute and the Security Expert Data Sync
Service will restart one minute after the previous sync was completed, updating Security
Expert with the latest Individual data from INet.

A Single Sync of All Record Types

This option is ideal in the situation where a one-off transition of data from INet to Security
Expert is to take place. The intention is to move all of the data over and continue with the
programming in Security Expert.

This configuration would be used in the situation where the INet database being transitioned
is setup exactly as desired with no changes to be made in INet after the data is imported to
Security Expert. By doing a single sync (i.e. not letting the services run periodically in the
background) it ensures that any manual changes made in Security Expert after the transition
process do not get overwritten.
To setup a single sync of all record types:
1. Fill out the required details as per the Software Configuration section (see page
Software Configuration (see page 18)).
2. On the Export Settings tab, set the Export Type to Every Record Type on Every Sync.
3. If any of the optional programming is to be transitioned (see Record Types (see page 20))
configure this now.
4. Click Start on the INet Database Transition Service.
5. A prompt to open the live event log will be presented. Click Yes to view details of the
export.
6. Once an Export Complete event has been logged, click Stop on the INet Database
Transition Service button. Leave the live event log open as it will be required for the
steps that follow.
7. Select the Data Sync Service tab and fill out the requires details (see Data Sync Service
(see page 21)).
8. Click Create Data Sync Service Settings File. This will generate the required setup for
the Data Sync Service to add records to Security Expert.
9. Click Start on the Security Expert Data Sync Service.
10. To view details of the sync, process see the live event log.
11. Once the sync is complete (a Next sync will begin at message will be logged), click Stop
on the Security Expert Data Sync Service to prevent manual changes in Security Expert
being overwritten with obsolete details from INet.

| March 2019 23
Schneider Electric INet Database Transition Guide Running the Transition

A Continuous Sync of All Record Types

This configuration would be used in the situation where changes are being made in INet but
not in Security Expert. Any changes made in Security Expert will be overwritten by the details
for that record in INet.
To setup a continuous sync of all record types:
1. Fill out the required details as per the Software Configuration section (see page
Software Configuration (see page 18)).
2. On the Export Settings tab, set the Export Type to Every Record Type on Every Sync.
3. If any of the optional programming is to be transitioned (see the Record Types section on
page 17) configure this now.
4. Click Start on the INet Database Transition Service.
5. A prompt to open the live event log will be presented. Click Yes to view details of the
export.
6. Select the Data Sync Service tab and fill out the requires details as per the Data Sync
Service section (see Data Sync Service (see page 21)).
7. Click Create Data Sync Service Settings File. This will generate the required setup for
the Data Sync Service to add records to Security Expert.
8. Click Start on the Security Expert Data Sync Service.

The programming in INet will periodically be synced to Security Expert. For instance, if the
transition tool is set to Run This Application Every 1 Minutes (at the top of the transition tool
window) the Security Expert Data Sync Service will restart one minute after the previous sync
was completed, updating Security Expert with the latest programming in INet.

24 | March 2019
Field Mapping and Programming Schneider Electric INet Database Transition Guide

Field Mapping and Programming

This section contains information on how the data and programming in INet are transitioned to
implement the same programming in Security Expert.
Field Mapping

Any Security Expert Field Name that has the corresponding INet Field Name empty
represents fields for which the values are generated by the transition tool to meet Security
Expert requirements.

In INet the address of a point on a controller is in the form LLSSPPBB TP where:

 LL is the Link
 SS is the Station
 PP is the Point
 BB is the Bit Offset
 TP is the Type

These point addresses are used as part of the naming convention in Security Expert.
Programming

The address of any device or point that is transitioned will appear to be one address higher
than the address in INet as a result of zero not being a valid address in the Security Expert
client. The Security Expert database will contain the same address for the device or point as
seen in INet, hence it does not affect the operation of the system, however the client displays
this offset for the following fields:
 Reader Expander Physical Address
 Input Module Address
 Input Module Input
 Output Module Address
 Output Module Output
 Smart Reader Expander Address
 Smart Reader Configured Address

INet Operators to Security Expert Operators

Field Mapping

Navigate to Global | Operators in Security Expert to locate the INet Operator records that
have been transitioned.

Initials User Name

Operator Name Name

Programming

Every operator transitioned from INet will have their Password set to blank and their Role set
to No Access. An operator with Administrator Role will need to log in and set both of these
settings before the new operators can access Security Expert.

| March 2019 25
Schneider Electric INet Database Transition Guide Field Mapping and Programming

INet DCUs to Security Expert Controllers

Field Mapping

Navigate to Sites | Controller in Security Expert to locate the INet DCU records that have
been transitioned.

DCU Name <LLSS> Name

DCU Type Name (Second Language)

Commands

Programming
The IP Address and Serial Number are left blank during the transition process and must be
configured manually before the controllers will come online.

The Data Sync Service assigns the command I/NET=1 to all controllers and is used to store
firmware related settings which are loaded at start-up.

Only the 7793 and 7798 MCI units are supported by the transition. For reference, these units
have a TypeNdx of 14 and 15 respectively in the NetConDCU table in the INet. Any records
that do not have a NetConDCU.TypeNdx of 14 or 15 will not be transitioned to Security
Expert.

INet Schedules to Security Expert Schedules

Field Mapping
Navigate to Sites | Schedules in Security Expert to locate the schedule records that have
been transitioned.

Name

Begin Start Time

End End Time

Sunday Sun

Monday Mon

Tuesday Tue

Wednesday Wed

Thursday Thu

Friday Fri

Saturday Sat

26 | March 2019
Field Mapping and Programming Schneider Electric INet Database Transition Guide

Programming
Schedules are transitioned in the following scenarios:
 Access Level Door Schedules: These are retrieved from the INet Personnel Schedule
records and are assigned to the doors on an access level in Security Expert. The access
levels are then assigned to the users whom are allowed access to the assigned doors
within the hours of the corresponding schedule.
 Door Type Operating Schedule: The Door ATS Actions of Secure and Secure/PIN in
INet are used to create Operating Schedules for the Door Types that are transitioned to
Security Expert. This defines the time fame within which a particular type of credential
must be presented at the door in order to be granted access.
 Unlock Schedules: In the case of the Door ATS Action changing from Lock to Unlock to
Lock, or Secure to Unlock to Secure in INet, this schedule is assigned to a door and is
used to define the time frame within which credentials do not need to be presented at the
door to be granted access.
 Antipassback Reset Schedules: The Door ATS Action of APB Reset in INet are used
to create these schedules, where in Security Expert, they have a Start Time as specified
in INet and an End Time which is one minute after the start time.

Any schedules that are 24/7 are not transitioned to Security Expert and any records that
reference these schedules are assigned the Security Expert built-in default value Always.

INet MCUs to Security Expert Reader Expanders

Field Mapping

Navigate to Expanders | Reader Expanders in Security Expert to locate the INet MCU
records that have been transitioned.

MCU Type <LLSSPP> Name

MCU Point Address Physical Address

Port 1 Network Type

Port 2 Network Type

Commands

Programming
 The transition tool creates one reader expander record for each INet Micro Control Unit
(MCU). For a list of devices supported by the transition ().

Reader expanders are always configured with a default reader format, mode, location and
door due to the use of smart readers which display the reader programming for each door.

Every reader expander is assigned a Port 1 Network Type and Port 2 Network Type of
Third Party Generic as each reader expander is linked to up to four smart readers (see
Security Expert Smart Readers (see page 33)).

The Data Sync Service assigns the command PortOne=INET to every Smart Reader.

Smart reader records are only created for units that support doors.

| March 2019 27
Schneider Electric INet Database Transition Guide Field Mapping and Programming

INet Zones to Security Expert Areas

Field Mapping

Navigate to Programming | Areas in Security Expert to locate the records created in the
transition process.

Name

Programming
If the tool has been configured to transition antipassback programming (see Programming
(see page 21)) one area record is created for each Entry Zone and Exit Zone. The Entry
Zone is assigned as the Area Inside Door, while the area corresponding to the Exit Zone is
assigned as the Area Outside Door on doors that have antipassback enabled in INet. In
Security Expert these areas are named Zone X <DCU Name + LLSSPP> where X is the zone
number retrieved from the DCU save files. In addition to zones, one area named Unsecure
Area <LLSSPP> is created for each DCU record. If the value of the Entry Zone is not equal to
the Exit Zone in INet, the Area Outside Door is set to the unsecured area, indicating that the
door leads to an area where user movement is not being tracked (e.g. outside the building).
Finally, one System Area per DCU is created to be assigned as the Area on transitioned
inputs (DI/DA Points).

INet Points to Security Expert Inputs

Field Mapping

Navigate to Programming| Inputs in Security Expert to locate the INet Discrete Input (DI)
and Discrete Alarm (DA) Point records that have been transitioned.

Point Name <LLSSPPBB> Name

Point Type (Class) Name (Second Language)

Point Address Module Address

Bit Offset Module Input

Module Type

DCU Name "System Area" <LLSS> Area (First Assigned Area)

Input Type (First Assigned Area)

28 | March 2019
Field Mapping and Programming Schneider Electric INet Database Transition Guide

Programming
The INet SCU 12XX devices provide twelve discrete inputs, however only the first eight inputs
are available when the SCU is operating in single-address mode. In order to use the last four
inputs, the SCU must be operating in double-address mode where the SCU is assigned the
next consecutive subLAN address.

A single reader expander is created for each SCU, irrespective of whether it has one or two
subLAN addresses. Any inputs on the secondary subLAN address must be placed on the
primary address in order to assign all inputs to the same single reader expander.

In the INet database, an SCU in double-address mode is essentially the same as two devices
in single-address mode, where the inputs on the first subLAN address have bit offset 00 to 07
and those on the second address have bit offset 00 to 03. In the process of transitioning these
outputs to security expert, outputs on the second subLAN must have four added to the bit
offset address in order to retrieve the correct Module Input address.
No such calculations are needed for other units as they can only be configured to have a
single subLAN address.

For every input transitioned to Security Expert the Module Type is set to Reader (RD).

INet Points to Security Expert Outputs

Field Mapping
Navigate to Programming| Outputs in Security Expert to locate the INet Discrete Output
(DO) Point records that have been transitioned.

Point Name <LLSSPPBB> Name

Point Type (Class) Name (Second Language)

Point Address Module Address

Bit Offset Module Input

Module Type

| March 2019 29
Schneider Electric INet Database Transition Guide Field Mapping and Programming

Programming

The INet SCU 1284 and 1280 devices provide eight relay outputs divided across two
consecutive subLAN addresses. When the device is in single-address mode only the first four
outputs are operational and in double-address mode all eight outputs can be used.

As mentioned above, a single reader expander is created for each SCU, irrespective of
whether it has one or two subLAN addresses. Any outputs on the secondary subLAN address
must be placed on the primary address in order to assign all outputs to the same single reader
expander.
In the INet database, an SCU in double-address mode is essentially the same as two devices
in single-address mode and the outputs on both the first and second subLAN have bit offset
00 to 03. In the process of transitioning these outputs to security expert, outputs on the
second subLAN must have four added to the bit offset address in order to retrieve the correct
Module Output address.

No such calculations are needed for other units as they can only be configured to have a
single subLAN address.

30 | March 2019
Field Mapping and Programming Schneider Electric INet Database Transition Guide

INet Door ATS as Security Expert Door Types

Navigate to Programming| Door Types in Security Expert to locate the records created in
the transition process.

Name

Operating Schedule

Secondary Door Type

Entry Reading Mode

Exit Reading Mode

Entry Passback Mode

Exit Passback Mode

The Operating Schedule is determined by the time duration of the specific Action(s) on the
ATS schedule in INet. If there is more than one Action programmed a Secondary Door Type
is used, for example, if the following ATS schedule exists for a door in INet:

APB Reset 00:00

Sec/PIN 05:00

Secure 08:00

Sec/PIN 16:30

Lock 20:00

The following door programming will be implemented in Security Expert:

Card and PIN 05:00 - 08:00 Card

Card 08:00 - 16:30 Card and PIN

Card and PIN 16:30 - 20:00 Lock

Lock 20:00 - 05:00

| March 2019 31
Schneider Electric INet Database Transition Guide Field Mapping and Programming

The 'Lock' door type does not have a Secondary Door Type as the schedule will be valid
until the door type changes to Card and PIN at 05:00AM.

Note that the APB Reset Action will not generate a door type in the transition process as it
implemented as the Antipassback Reset Schedule option on a door in Security Expert, see
below.

Programming

Door types are assigned to doors to define the credentials that must be presented at the door
in order to be granted access and the antipassback configuration for the door.

The Reading Mode transitioned to Security Expert is determined by the Action on the Door
ATS.

1 APB Reset Implemented as Antipassback Reset Schedule

2 Lock Door REX Enabled is disabled

3 Unlock Implemented as Unlock Schedule

Secure Card

Sec/PIN Card and PIN

Sec/Code Card or PIN

1. The type of antipassback in INet is defined for each individual, however there is no perfect
implementation of the same functionality in Security Expert where the type of
antipassback is defined by door. Currently, the Passback Mode is determined by the
most secure level of antipassback for an individual who has access to that door in INet. In
addition, if the door has an ATS schedule with the Action set to APB Reset, this is
assigned as the Antipassback Reset Schedule in Security Expert.
2. If a door has an Action type set to Lock in INet, this is transitioned to a 'Lock' door type in
security expert which has the Entry Reading Mode and Exit Reading Mode set to
Reserved 3 which defines access to a user who presents their credential at the door.
Additionally, the Door REX Not Allowed option enabled to prevent users from gaining
access by triggering the REX input.

INet Doors to Security Expert Doors

Field Mapping
Navigate to Programming| Doors in Security Expert to locate the INet Door records that
have been transitioned.

Door Name <LLSSPPBB> Name

Door Type

Entry Zone Area Inside Door

Exit Zone Area Outside Door

Unlock Schedule

32 | March 2019
Field Mapping and Programming Schneider Electric INet Database Transition Guide

Door Open Too Long Door Left Open Alarm Time

Door Strike Lock Output

Strike Duration Lock Activation Time

Door Sense Switch Door Position Input

Door Release Switch REX Input

Anti-passback Enable Timed User Antipassback Reset

Antipassback Entry User Reset Time

Anti-passback reset time
Antipassback Exit User Reset Time

Reset Antipassback Status on Schedule

Antipassback Reset Schedule

Programming

The doors data is retrieved from the INet DCU save files except for the following:
 Lock Output, Door Position Input and REX Input retrieved from the database.
 Unlock Schedule and Antipassback Reset Schedule (determined by the Action type
on the Door ATS).

Security Expert Smart Readers

Field Mapping

Navigate to Expanders | Smart Readers in Security Expert to locate the records created in
the transition process.

DPU Type (PP) "Reader Port" Reader Input Name

LLSSPPBB <Door Name> Name (Second Language)

MCU Base Point Index Expander Address

Configured Address

Door Name <LLSSPPBB> Reader One Door

Exit Reader Reader One Location

Programming

The Expander Address on the smart reader is determined by the address of the MCU, or in
Security Expert, the Physical Address of the reader expander.

The Reader One Location in Security Expert is determined by the configuration of the Exit
Reader option on a door which is retrieved from the INet DCU save files. If the Exit Reader is
set to anything other than None, the reader is configured for both entry and exit. In this case,
the transition tool will generate two smart reader records, where one has the Reader One
Location set to Entry and the other has the Reader One Location set to Exit, both with the
same Reader One Door.

| March 2019 33
Schneider Electric INet Database Transition Guide Field Mapping and Programming

INet SCU 1284 Reader Configuration

The 1284 supports up to four doors with the reader inputs configured for entry only, or two
doors with the reader inputs configured for both entry and exit.

Irrespective of whether the SCU 1284 is configured in single or double addressing mode:
 If reader port one is configured for both entry and exit, reader port three becomes the exit
reader.
 If reader port two is configured for both entry and exit, reader port four becomes the exit
reader.

1 (TB2) 1 Entry

2 (TB3) 2 Entry

3 (TB4) 3 Entry

4 (TB5) 4 Entry

Number of Doors 4

Number of Smart Readers 4

1 (TB2) 1 Entry

2 (TB3) 2 Entry

3 (TB4) 1 Exit

4 (TB5) 4 Entry

Number of Doors 3

Number of Smart Readers 4

1 (TB2) 1 Entry

2 (TB3) 2 Entry

3 (TB4) 3 Entry

4 (TB5) 2 Exit

Number of Doors 3

Number of Smart Readers 4

1 (TB2) 1 Entry

2 (TB3) 2 Entry

3 (TB4) 1 Exit

4 (TB5) 2 Exit

Number of Doors 2

Number of Smart Readers 4

34 | March 2019
Field Mapping and Programming Schneider Electric INet Database Transition Guide

INet DPU 7920 Reader Configuration

The 7920 supports up to two doors with the reader inputs configured for entry only, or one
door with the reader input configured for both entry and exit.

1 (TB3) 1 Entry

2 (TB4) 2 Entry

Number of Doors 2

Number of Smart Readers 2

1 (TB3) 1 Entry

2 (TB4) 1 Exit

Number of Doors 1

Number of Smart Readers 2

INet DPU 7910 Reader Configuration

The 7910 supports up to two doors with the reader inputs configured for entry only or both
entry and exit.

1A 1 Entry

1B 1 Exit

2A 2 Entry

2B 2 Exit

Number of Doors 2

Number of Smart Readers 4

1 1 Entry

2 1 Entry

Number of Doors 1

Number of Smart Readers 2

| March 2019 35
Schneider Electric INet Database Transition Guide Field Mapping and Programming

INet Groups to Security Expert Access Levels

Field Mapping

Navigate to Users| Access Levels in Security Expert to locate the INet Groups records that
have been transitioned.

Group Name "Access Level" Name

Door Name <LLSSPPBB> Door

Personnel Schedule Name <LLSSPPBB> "Schedule" Schedule

Programming
Access levels are assigned to users and are used to define which users have access to which
doors at a particular time according to a schedule. One access level record is created for each
group record in INet and every door with its assigned schedule belonging to that group is
transitioned to Security Expert.

The INet Door Code functionality is implemented in Security Expert by creating a designated
access level for the door that contains the door code and is then assigned to a designated
'door code' user.

INet Individuals to Security Expert Users

Field Mapping

Navigate to Users | Users in Security Expert to locate the INet Individual records that have
been transitioned.

Individual Custom Field 1

First Name First Name

Last Name Last Name

Name

Groups Access Levels

Expiry Start

Expiry End

Access Level Expires

PIN PIN

Credential Type

Hex Number Credential

Disabled Disabled

Begin Date + Begin Time Start

36 | March 2019
Field Mapping and Programming Schneider Electric INet Database Transition Guide

End Date + End Time End

Record Type = Disabled Disable User

Programming
The Hex Number for an individual is stored in the Hex Card Number credential type created
by the transition tool. For more information, see Security Expert Credential Types.

The Door Code functionality is implemented in Security Expert by creating a designated user
with their PIN number set to the Door Code retrieved from the INet DCU save files. This user
is assigned then designated 'door code' access level (see INet Groups to Security Expert
Access Levels (see page 36)) granting them access to only the door that was assigned to that
access level.

| March 2019 37
Schneider Electric INet Database Transition Guide Known Issues, Limitations and Future Releases

Known Issues, Limitations and Future Releases

This section outlines known issues and limitations in the transition process that will be
resolved in a future release:
Limitations
 Controllers in Security Expert do not have the IP Address filled in from the DCU
Configuration.
 The Reader One Format on a Smart Reader is set to 26 Bit by default which affects the
display in Security Expert, however the reader format is retrieved and interpreted correctly
by the firmware.
 For Inputs that have a system area assigned, the Input Type is set to Instant irrespective
of what is assigned in INet.
 Security Expert doors do not have a shunt output.
 There is a limitation on the implementation of antipassback in Security Expert. See
Security Expert Areas (see page 28) for more information.

Future Releases
 Secondary Groups (Groups in Groups) will be transitioned to Security Expert as access
levels in a future release.
 Enclosure Tamper and Battery Status Points have not yet been added as inputs in
Security Expert.
 Allowing duplicate PINs for Individuals transitioned to users in Security Expert is to be
implemented in a future release.
 Custom data on Individuals being transitioned to Custom Fields in Security Expert is to
be implemented in a future release.
 Image ID for users is to be implemented in a future release.

Known Issues
There are multiple known issues around using the INet Door ATS to create Door Types and
Schedules in Security Expert.
 Door ATS records that start or end early (i.e. having consecutive Secure periods with the
same days but a different times) may not transition correctly and have periods missing
from the schedule in Security Expert.
 Door ATS records that have different consecutive Actions running over the same days
and times may cause the Door Type assigned to the Door in Security Expert to have an
incorrect Entry Reading Mode and/or Exit Reading Mode.
 Door Types that are used as a Secondary Door Type in Security Expert may incorrectly
have their Operating Schedule set to Always.

38 | March 2019
Technical Reference Schneider Electric INet Database Transition Guide

Technical Reference
This section contains technical information related to which records are retrieved from INet
and the calculations and processing that the transition tool executes before the records are
synced to Security Expert.

Records
Operators
Database Tables
SecurityExpert: Controllers

INetDb: NetConDCU

Conditions for Transition

Every Operator in INet is transitioned to Security Expert.

Controllers
Database Tables

SecurityExpert: Controllers

INetDb: NetConDCU
Conditions for Transition
1. NetConDCUType.TypeId = 14 OR NetConDCUType.TypeId = 15

Where TypeID = 14 is a 7793 MCI and TypeID = 15 is a 7798 MCI.

Only these two devices are supported by the transition process.

Schedules
Database Tables
SecurityExpert: Schedules

INetDb: PerScheds and DoorSchedules

Conditions for Transition

Any Schedules in INet that are valid 24/7 are not transitioned to Security Expert and any
record that references a 24/7 Schedule is set to 2147483647, the integer value for Always in
Security Expert.

| March 2019 39
Schneider Electric INet Database Transition Guide Technical Reference

1. Access Level Door Schedules

Every record in the PerScheds table is transitioned to Security Expert.

2. Door Type Operating Schedules

DoorSchedules.DoorNdx = NetConDoor.DoorId - The Schedule must be assigned at

least one Door.
3. Door Unlock Schedules
DoorSchedules.DoorNdx = NetConDoor.DoorId - The Schedule must be assigned to
at least one Door.
DoorSchedules.ActionTypeNdx != 0 - The Action on the Door ATS set to anything
other than APB Reset.
4. Antipassback Reset Schedules

DoorSchedules.DoorNdx = NetConDoor.DoorId - The Schedule must be assigned to

at least one Door.
DoorSchedules.ActionTypeNdx = 0 - The Action on the Door ATS is set to APB
Reset.

40 | March 2019
Technical Reference Schneider Electric INet Database Transition Guide

Reader Expanders
Database Tables

SecurityExpert: Reader Expanders

INetDb: NetConMCU
Conditions for Transition
1. NetConMCU.DPUType > 0

NetConMCU.DPUType = 0 is treated as invalid as it is impossible to determine which

type of device is programmed and what it should be transitioned to in Security Expert.
Devices in the INet database that have the DPUType set to zero are consequently
excluded from the transition.
2. NetConMCU.TypeNdx != 255

NetConMCU.TypeNdx = 255 indicates that the record is the second station on a two-
station device. Only the first station is required to be transitioned to Security Expert as
the entry/exit configuration is handled by the Smart Readers.
3. NetConMCU.LinkNdx = NetConDCU.LinkNdx

The MCU link address must match a valid DCU link address.
4. NetConMCU.StaNdx = NetConDCU.StaId

The MCU station address must match a valid DCU station address.
5. NetConDCU.TypeNdx = 14 OR NetConDCU.TypeNdx = 15

The controller the device is connected to must be a type that is supported by the
transition. See Controllers (see page 39) for more information.
Records

A combination of the NetConMCU.TypeNdx and NetConMCU.DPUType determines the

device type:

TypeNdx DPUType Type Device

5 5 DPU SCU 1200

5 4 DPU SCU 1280

5 3 DPU SCU 1284

5 2 DPU DPU 7920

5 1 DPU DPU 7910

6 5 DIO SCU 1200

6 4 DIO SCU 1280

6 1 DIO SCU 1284

7 5 DIU SCU 1200

7 1 DIU DPU 7930

| March 2019 41
Schneider Electric INet Database Transition Guide Technical Reference

Areas
All the required technical information can be found in INet Zones to Security Expert Areas
(see page 28).

Inputs
Database Tables

SecurityExpert: Zones
INetDb: Points

Conditions for Transition

For instructions on how to calculate addresses, see Calculations (see page 48).
1. Point Type = 1 OR Point Type = 2
A 1 indicates that the Point is a Discrete Input (DI) and a 2 indicates the Point is a DA
(Discrete Alarm).
2. Link = NetConMCU.LinkNdx
Where the Link is to be calculated from the Points.PointID
The Point link address must match a valid DCU link address.
3. Station = NetConMCU.StaNdx
Where the Station is to be calculated from the Points.PointID
The Point station address must match a valid DCU station address.
4. Point = NetConMCU.PointId
Where the Point is to be calculated from the Points.PointID
The Point point address must match a (valid) MCU point address.
5. NetConDCU.StaId = NetConMCU.StaNdx
The DCU station address must match a (valid) MCU station address.

6. NetConMCU.DPUType != 0
NetConMCU.DPUType = 0 indicates an invalid device. See Reader Expanders (see
page 41) for more information.

7. NetConDCU.TypeNdx = 14 OR NetConDCU.TypeNdx = 15
The controller the door is connected to must be a type that is supported by the
transition. See Controllers (see page 39) for more information.

42 | March 2019
Technical Reference Schneider Electric INet Database Transition Guide

Outputs
Database Tables

SecurityExpert: PGMs

INetDb: Points
Conditions for Transition

For instructions on how to calculate addresses, see Calculations (see page 48).

1. Point Type = 1
A 5 indicates that the Point is a Discrete Output (DO) Point.
2. Link = NetConMCU.LinkNdx
Where the Link is to be calculated from the Points.PointID
The Point link address must match a valid DCU link address.
3. Station = NetConMCU.StaNdx
Where the Station is to be calculated from the Points.PointID
The Point station address must match a valid DCU station address.
4. Point = NetConMCU.PointId
Where the Point is to be calculated from the Points.PointID
The Point point address must match a (valid) MCU point address.
5. NetConDCU.StaId = NetConMCU.StaNdx
The DCU station address must match a (valid) MCU station address.
6. NetConMCU.DPUType != 0
NetConMCU.DPUType = 0 indicates an invalid device. See Reader Expanders (see
page 41) for more information.
7. NetConDCU.TypeNdx = 14 OR NetConDCU.TypeNdx = 15
The controller the door is connected to must be a type that is supported by the
transition. See Controllers (see page 39) for more information.

| March 2019 43
Schneider Electric INet Database Transition Guide Technical Reference

Door Types
Door Types are only created for transition to Security Expert when the defaults cannot be
used such as when:
 Antipassback is enabled.
 An Operating Schedule applies.
Database Tables

SecurityExpert: DoorTypes

INetDb: DoorSchedules
Conditions for Transition
1. NetConDoor.LinkNdx = NetConDCU.LinkNdx

The Door link address must match a valid DCU link address.
2. NetConDoor.StaNdx = NetConDCU.StaId

The Door station address must match a valid DCU station address.
3. NetConDoor.PointNdx = NetConMCU.PointId

The Door point address must match a valid MCU point address.
4. NetConDCU.LinkNdx = NetConMCU.LinkNdx

The DCU link address must match a valid MCU link address.
5. NetConDCU.StaId = NetConMCU.StaNdx

The DCU station address must match a (valid) MCU station address.
6. NetConMCU.DPUType != 0
NetConMCU.DPUType = 0 is treated as invalid device. See Reader Expanders (see
page 41) for more information.
7. NetConDCU.TypeNdx = 14 OR NetConDCU.TypeNdx = 15

The controller the door is connected to must be a type that is supported by the
transition. See Controllers (see page 39) for more information.

Door Types are calculated from consecutive DoorSchedules.ActionTypeNdx records where:

ActionTypeNdx Action Security Expert Door Type

1 Lock Card

3 Secure Card

4 Sec/PIN Card and PIN

5 Sec/Code Card or PIN

DCU .SAV Files

When the First Key Mode is set to Sec/Code in INet an Operating Schedule will be defined
on the Door Type and this information is retrieved from the DCU save files.

44 | March 2019
Technical Reference Schneider Electric INet Database Transition Guide

Doors
Database Tables

SecurityExpert: Doors

INetDb: NetConDoor
Conditions for Transition
1. NetConDoor.LinkNdx = NetConDCU.LinkNdx

The Door link address must match a valid DCU link address.
2. NetConDoor.StaNdx = NetConDCU.StaId

The Door station address must match a valid DCU station address.
3. NetConDoor.PointNdx = NetConMCU.PointId

The Door point address must match a valid MCU point address.
4. NetConDCU.LinkNdx = NetConMCU.LinkNdx

The DCU link address must match a valid MCU link address.
5. NetConDCU.StaId = NetConMCU.StaNdx

The DCU station address must match a (valid) MCU station address.
6. NetConMCU.DPUType != 0
NetConMCU.DPUType = 0 is treated as invalid device. See Reader Expanders (see
page 41) for more information.
7. NetConDCU.TypeNdx = 14 OR NetConDCU.TypeNdx = 15

The controller the door is connected to must be a type that is supported by the
transition. See Controllers (see page 39) for more information.

DCU .SAV Files

The following fields are retrieved from the DCU .SAV Files:

INet Save File Field Security Expert Field

Strike Duration Lock Activation Time

Door Open Too Long Door Left Open Alarm Time

First Key Mode (Unlock) Schedule Operates Late to Open

| March 2019 45
Schneider Electric INet Database Transition Guide Technical Reference

Smart Readers
Database Tables

SecurityExpert: Reader Expanders

INetDb: NetConMCU
Conditions for Transition
1. NetConMCU.DPUType > 0

NetConMCU.DPUType = 0 is treated as invalid as it is impossible to determine which

type of device is programmed and what it should be transitioned to in Security Expert.
Devices in the INet database that have the DPUType set to zero are consequently
excluded from the transition.
2. NetConMCU.LinkNdx = NetConDCU.LinkNdx

The MCU link address must match a valid DCU link address.
3. NetConMCU.StaNdx = NetConDCU.StaId

The MCU station address must match a valid DCU station address.
4. NetConDCU.TypeNdx = 14 OR NetConDCU.TypeNdx = 15

The controller the device is connected to must be a type that is supported by the
transition. See Controllers (see page 39) for more information.
Records

The NetConMCU.DPUType determines the device type:

DPUType Device
3 SCU 1284

2 DPU 7920

1 DPU 7910

DCU .SAV Files

If the Exit Reader is set to Anytime or Scheduled in INet, the reader is configured for both
entry and exit. In this case, the transition tool will generate two smart reader records, where
one has the Reader One Location set to Entry and the other has the Reader One Location
set to Exit, both with the same Reader One Door. The Configured Address for the Smart
Reader created in Security Expert is:
 On an SCU 1284, the Configured Address of the Entry Reader + 2
 On a DPU 7920, the Configured Address of the Entry Reader + 1

46 | March 2019
Technical Reference Schneider Electric INet Database Transition Guide

Access Levels
Database Tables

SecurityExpert: AccessLevels

INetDb:
 Doors in Door Groups: XRefGroupDoor
 Doors on Individuals: XRefIndivGroupDoor
Conditions for Transition

Door Groups that have no doors are transitioned to Security Expert as an empty Access
Level. Doors in Door Groups that have the Schedule set to Unselect are not added as Access
Level Doors in Security Expert.

Doors in Door Groups

1. DoorsGroups.DoorGroupId = XRefGroupDoor.ParentGroupNdx
Gets Doors in the Doors Group.
2. DoorsGroups.DoorGroupId = Groups.DoorGroupNdx
Gets the TenantNdx of the Doors Group (which is appended to the Name of the Access
Level).
3. XRefGroupDoor.ChildGroupNdx = NetConDoor.DoorId
Links the Doors in Door Groups to a Door a Door record.
4. XRefGroupDoor.ChildGroupNdx = PerSchedNames.DoorNdx AND
XRefGroupDoor.DoorSchedule = PerSchedNames.SchedId
To get the Personnel Schedule assigned to the Door in the Doors Group. If there is no
Personnel Schedule (i.e. 'Unselect in the INet UI) the Door is not added to the Access
Level in Security Expert.

Doors on Individuals
1. XRefIndivGroupDoor.TenantNdx = Individuals.TenantNdx AND
XRefIndivGroupDoor.IndivNdx = Individuals.IndivId
Get Doors on the Individual by matching the Tenant ID and Individual ID
2. XRefIndivGroupDoor.DoorGroupNdx = NetConDoor.DoorId
Get the Door on the Individual

Users
Database Tables

SecurityExpert: Users
INetDb: Individuals

Conditions for Transition

Individuals that do not have any credentials assigned or access to doors will still be
transitioned to Security Expert.

| March 2019 47
Schneider Electric INet Database Transition Guide Technical Reference

1. Cards.IndivNdx = Individuals.IndivId AND Cards.TenantNdx = Individuals.TenantNdx

Gets the 'Hex Card Number' Credential for the User.

2. Individuals.IndivId = XRefIndivGroupDoor.IndivNdx AND Individuals.TenantNdx =
XRefIndivGroupDoor.TenantNdx

Gets the Access Levels (INet Door Groups) for the User.
3. XRefIndivGroupDoor.DoorGroupNdx = Groups.DoorGroupNdx AND
XRefIndivGroupDoor.TenantNdx = Groups.TenantNdx

Gets the Expiry Start and Expiry End on the Access Levels from the Begin and End
Date Time on the Door Group in INet.
4. XRefIndivGroupDoor.DoorGroupNdx = DoorsGroups.DoorGroupId

Gets the name of the Doors Group which is the name of the Access Level.

Calculations
This section contains instructions and examples of calculations that are referenced in topics in
the Technical Reference Section.
As an example, take an External Discrete Input at address 01010102 which has Point.PointId
= 532769 in the INet Database:

Formula: x & 15
Result:

Value Type
1 Input (DI)

2 Input (DA)

5 Output (DO)

48 | March 2019
Technical Reference Schneider Electric INet Database Transition Guide

Example: 572769 & 15

=1

= Input (DI)

Link
Formula: (x & 66584576)/(219)

Example: (532769 & 66584576)/(219)

=524288/524288
=1

Station

Formula: (x & 516096)/(213)

Example: (532769 & 516096)/(213)

= 256/256

=1
Point (Security Expert Module Address)

Formula: (x & 7936)/(28)

Example: (532769 & 7936)/(28)

= 256/256

=1

Bit
Formula: (x & 240) / (24)

Example: (532769 & 240)/(24)

= 32/16
=2

Point Class

Formula: (x & 768)/(28)

Result:

Value Type
0 External

1 Internal

2 Indirect

Example: (532769 & 240)/(28)

= 32/256

=0
= External

| March 2019 49
Schneider Electric

www.schneider-electric.com
© 2019 Schneider Electric. All rights reserved.

March 2019