C·CURE 9000

Technical Training

Company Confidential
 Housekeeping

• The training starts 9 am and ends 5 pm.

• Bathrooms
• Breaks will be every 90 minutes
• Lunch
• Coffee, Water and other drinks…
• Please switch all mobile devices off
• Email access…
• Smoking
• Emergency
 Objectives

• Upon successful completion of this training you must be

capable to install, configure and troubleshoot a basic
C·CURE 9000 system. Among other you must be able of:
− Understanding the C·CURE 9000 system architecture from the
Software and Hardware point of view
− Know how to install the C·CURE 9000 Server and Clients
− Know how to install all the Hardware: Controllers, Readers and
Additional Modules
− Configure Readers, Inputs, Outputs, Doors, Personnel, Basic
events, Maps, Areas with AntiPassback, basic Reports, backup the
system databases and the basic Maintenance task
(Upgrade/Repair).
C·CURE 9000
System Overview

Company Confidential
 Objectives

• By the end of this module delegates will be able to:

− Have an understanding on the Features available on the C·CURE
9000 Security Management Software
− Know how the Server – Client architecture works
− Have a basic understanding on what the Client Applications are
used for
− Know the different Model Series available and their capacities
− Describe the recommended hardware, software and capacities for
a C•CURE 9000 installation.
− Know the Hardware components available for the C·CURE 9000
Security and Event Management System
With Integration in Mind

New feature in 2.4 version

(license based)

New feature in 2.4 version

(license based)
 Powerful and Flexible Security Management

• C•CURE 9000 is one of the industry’s most powerful and flexible

security management systems.
• Monitor events, manage personnel, create reports, display
dynamic views, and monitor system activity anywhere in the
world directly from your PC using the full C•CURE client, the web
client, or on the move with C•CURE Go mobile app (from v2.3).
• Area Control and Occupancy Management allow you to enforce
global anti-passback, define occupancy restrictions and lock
down procedures in sensitive or classified areas
• Intrusion Zones and Keypad Commands provide additional
verification requirements and duress triggers
• Dynamic Views and Editable Maps serve up critical information
in a customizable way, all while allowing you to find, manage,
and acknowledge significant incidents on user-defined floor plans
• Intuitive Badging and Smart Card Enrollment
 The C·CURE 9000 System
Server and Client

• The C·CURE 9000 Server:

− The Server software is based on Services that provide the
resources used by the Client Applications, Controllers and any
Integration to communicate with the server and opens the
communication path to the Databases.
− It uses Microsoft SQL as the Database Engine which can be in the
same PC as the C·CURE 9000 Server Services or in a Remote
computer connected using TCP/IP. The SQL holds the C·CURE
9000 databases.
The C·CURE 9000 System
The Server Services
C•CURE 9000 Server
SQL Database Scenarios
 The C·CURE 9000 System
Server and Client

• The C·CURE 9000 Client has two main Applications:

− One is the Administration Client that is used to enter cardholders,
clearances and to configure and administer the system. Example
functions:
 Configure the Hardware and Security Objects
 Import/Export of Cardholder Database
 Reports – configurable and pre-defined
 Journal and Audit Trail
 Personnel Screen Customization
 Configuration of Badges, etc.
The C·CURE 9000 System
Administration Application
The C·CURE 9000 System
Server and Client

− The Monitoring Client application allows the operator to perform

many functions such as:
 Monitors the status of system objects and devices.
 Manually open and close doors.
 Manually activate objects such as events, outputs, CCTV actions, etc.
 Display cardholder accesses with badge images displayed.
 Display Live Video
 Monitor all the Integrated systems
The C·CURE 9000 System
Monitoring Station
 The C·CURE 9000 System
Server and Client

• The C•CURE 9000

Server and its
Clients are usually
separate computers
connected via the
TCP/IP networking
protocol. You can
run the Client and
Server functions on
the same computer.

The C•CURE 9000 Operator is tied to the Windows login. When users start any client application,
they are queried as to which Windows User/ Principal they are.
 C·CURE 9000 Model Series

• C·CURE 9000 has Seven Models (Series) which are scalable and
upgradeable to the next level. Additional input/output capacity and
additional clients and badging clients may be added to a system
license.

Note: Simultaneous client connections are tabulated by C•CURE 9000

Administration, Alarm Monitoring, and Web Client connections.

*Series L systems can’t be upgraded to any other level

C·CURE 9000
Features and
options

Company Confidential
 Essential Features Included with All C•CURE 9000 Series

• Activity Journal • Multiple Card Support

• Anti-passback (cluster-based, • Multiple Guard Station GUIs
with iSTARs) • Multiple Time Zones
• Automated Import • NetVue Integration with Intellex
• CCTV Integration (analogue DVMS and VideoEdge NVR
Matrices) • Notification by Email
• Clearance Filters • Occupancy Rules
• Configuration Templates • Partitioning
• Double Swipe • Personnel Views
• Elevator Support • Push Install of Clients
• Field Level Auditing • Single Sign-On Authentication
• Graphical Maps • Smart Card Program / Enrolment
• Keypad Commands • System Backup of Database and
• Intrusion Zones Journals
• Localized versions available • User-defined Personnel Fields
• Manual Action Challenge • WebStation Client
 Some new Features

• At v2.20 • At v2.30
− apC Time Zones − Advanced Door
− Card Disabled by Monitoring
Inactivity − Dual Phase
− Individual Card Access Acknowledgement
Events − Guard Tour
− First Last Card Read − Maps Enhancement
Report − Migrating Standalone
− Custom Clearances C•CURE 9000 systems to
− Latch/Unlatch/Toggle/Puls a SAS. You can now
e Event migrate multiple
− Journal Triggers Standalone to SAS.
− Recurring Schedule
Support
− C•CURE GO
 New Features in 2.4 Version

• ISO image with all the files in the original DVD

• Added ICU in the “Options & Tools” Menu
• “Maintenance Mode” for the Objects
• Carpool function into the Areas
• New “Visit” menu for Visitors Management
• New “Credential” Menu for Temporary Issuance
• UI settings based on different colors
• iStar Diagnostic Password (“System Variables” Menu)
• New Events Actions (“E-mail reminder for unreturned
temporary credential” – “Check Visitors Out” – “Pre-Admit”
Event Trigger)
• Perform Full Controller Download (for all the iStars)
• “Show Associations” & “Monitor” Menus for the “children”
Hardware Objects and the Software Objects (like Events)
 New Features in 2.4 Version

• “Add & Remove Card Format” quick menu for Readers

• New “Create Personnel from Template” Menu
• Improved “Swipe & Show” Application Layout for multiple
photos
• Portrait: “Image Capture and Import Choice”, both enabling
together
• New Operators Privileges
• Basic Operators (non Window based)
• “Copy-Paste-Rename” function for all the hardware objects
• New “User Defined Fields”
• Support for Schlage Wireless Locks via PIM connectivity on
iSTAR Ultra GCM RS-485 ports.
 Enterprise Architecture

• The C•CURE 9000 Enterprise architecture supports one

master application server (MAS) and up to 20 satellite
application servers (SAS) for enterprise scalability.
• Each SAS may be located close to its relevant field
hardware limiting traffic to the MAS and optimizing
performance.
• Each facility maintains a local SQL database which is
synchronized with the MAS for global control and reporting.
The MAS distributes these changes globally from each
independent SAS, which ensures all servers are equipped
and operating with up-to-date information.
C•CURE 9000 Enterprise Architecture Diagram
 Victor Unification

• As an option, you
can take a holistic
video perspective of
managing access
control, video, and
intrusion with a
deeply embedded
victor unifying
client.
 EverRun Fault Tolerant Solutions for C•CURE

• Stratus Technologies’ everRun

MX® and SplitSite provide a high-
availability, fault tolerant business
continuity solution for C•CURE
systems.
• Fault tolerant platform adds around-
the-clock access control protection
• Zero downtime ensures no data
loss while a system is offline
• Significantly reduces costs and
operational risks caused by server
failure
• Scalable system grows with
changing business requirements NOTE: everRun MX doesn’t
• everRun MX is a software-only supports Windows Server 2012
solution that is easy to deploy and deployments, only Windows
use, for organizations with limited
IT resources Server 2008 R2 is supported.
 C•CURE 9000 SiteServer V2

• SiteServer – a compact, high-performance network

appliance delivering C·CURE 9000 out of the box
− Pre-installed with Windows Embedded 7
− Pre-installed with C·CURE 9000
− Pre-installed with C·CURE 9000 Web Client
− Pre-installed with 32-door starter database
• SiteServer – Enterprise Ready!
− Can be promoted to a SAS starting with v2.30 (not supported for
previous versions)
− Allows customers with numerous smaller sites to consolidate into
one system, one master database
− Up to 20 Satellite servers is currently the max
− With v2.40, you are able to easily “promote” SAS 2 through 20
− SAS license option will be needed per unit, SITESVR-SAS
C•CURE 9000 SiteServer
System Diagram
C•CURE 9000 SiteServer v2.30 or above
Enterprise Architecture Diagram
C·CURE 9000 SiteServer Series Capabilities
victor Unified
SiteServer

Company Confidential
 Victor Unified SiteServer – The Power of ONE !

The new VUSS provides a single GUI for the end user, with
many pre loaded features
victor Unified
Client System monitoring, video administration, and forensics
v4.5

C•CURE 9000 v2.30 Card access administration

VideoEdge v4.5 Video recording

DSC PowerSeries Intrusion integration

Embedded OS Windows 7
 victor Unified SiteServer Specifications
Specification SWHVUSS-08 SWHVUSS-16 SWHVUSS-32
Solid State Windows OS drive 240 GB 240 GB 240 GB
Online Readers 8 16 32
Online Inputs 128/1000 256/1000 512/1000
Online Outputs 128/1000 256/1000 512/1000

Credentials 7,000 7,000 12,000

Simultaneous CCURE 9000 Clients 5/10 5/10 5/10
Standard Badging Clients 1/5 1/5 1/5
IP Cameras 4/32 4/32 4/32

victor Unified Clients 2/3 2/3 2/3

Video Analytics Channels 0/2 0/2 0/2
NVR HDD 3TB; 3TB; 3TB;
1TB Linux OS partition 1TB Linux OS partition 1TB Linux OS partition
2TB video partition 2TB video partition 2TB video partition
 Bandwidth and Storage Capacity
Video Bandwidth Storage Capacity
40 MBps streaming input 2 TB

40 MBps video display output No additional storage options at this time

2x2 video on local client

For deeply information about your bandwidth needs, please

refer to the AD calculator

http://www.americandynamics.net/Calculators/IP-Bandwidth-Storage-
Calc.htm
C·CURE 9000
Integrations and
Connected
Program

Company Confidential
 The Software House Connected Partner Program
How to integrate with C·CURE

• Direct Interface, Hardware, Wiegand

− For Example, Biometric, ANPR, RFID asset tracking
− Via industry standard Wiegand connection all kind of applications can
be linked to C·CURE9000.
• Using Import, Export facilities, LDAP, ODBC, XML, CSV
− A possibility to update the C·CURE9000 database by importing
records from a human resources (HR) or other external database.
• Using the GPI (general purpose interface)
− Examples: Intercom, Intrusion system, Dome control, EAS,
Elevators, HVAC, Lighting, Process Control Equipment, etc..
• Connected program, Tyco SDK
− Provides the most flexible means of integrating, requires extensive
process working with the Connected Team
− Visit the web site:
http://www.swhouse.com/support/SWH_Connected.aspx
C·CURE 9000
Server and Client
Requirements

Company Confidential
 Microsoft OS for Version 2.40 Standalone Series

Standalone Series L/M/N Memory Supported Version Node

Windows Server 2012 R2 Standard 8 GB 64-bit server or client Recommended
Windows Server 2012 Standard 8 GB 64-bit server or client
Windows 8.1 Professional, Enterprise 8 GB 64-bit server or client
Windows 7 Professional, Enterprise 8 GB 64-bit, SP1 or later server or client
Windows Server 2008 R2 Standard, Enterprise 8 GB 64-bit, SP1 or later server or client
Windows 8.1 Professional 4 GB 32-bit server or client Supported
Windows 7 Enterprise 4 GB 32-bit, SP1 or later server or client
Standalone Series P/Q/R/R+/S Supported Version Node
Windows Server 2012 R2 Standard 16 GB 64-bit server or client
Windows Server 2012 Standard 16 GB 64-bit server or client Recommended
Windows 8.1 Professional, Enterprise 16 GB 64-bit server or client
Windows 7 Professional, Enterprise 16 GB 64-bit, SP1 or later server or client
Windows Server 2008 R2 Standard 16 GB 64-bit, SP1 or later server or client
Windows Server 2008 R2 Enterprise 16 GB 64-bit, SP1 or later server or client

Notes:
1. 32 bit OS types are supported for Series L/M/N, but they are not the 1st choice for Servers. There
are concerns of performance and security, compared to the 64 bit versions. 32 bit OS types are
sometimes required for Clients because of 3rd party option support.
2. Windows Server 2012 R2 is preferable over Windows Server 2012.
3. Windows Server 2008 (Vista base) is not supported, only Windows Server 2008 R2.
 Microsoft OS for SAS (2.40 Version)

SAS Series L/M/N Memory Supported Version Node

Windows Server 2012 R2 Standard 16 GB 64-bit server or client
Windows Server 2012 Standard 16 GB 64-bit server or client
Windows 8.1 Professional, Enterprise 16 GB 64-bit server or client
Windows 7 Professional, Enterprise 16 GB 64-bit, SP1 or later server or client
Windows Server 2008 R2 Standard 16 GB 64-bit, SP1 or later server or client
Windows Server 2008 R2 Enterprise 16 GB 64-bit, SP1 or later server or client
Recommended

SAS Series P/Q/R/R+/S Supported Version Node

Windows Server 2012 R2 Standard 16 GB 64-bit server or client
Windows Server 2012 Standard 16 GB 64-bit server or client
Windows Server 2008 R2 Standard 16 GB 64-bit, SP1 or later server or client Supported
Windows Server 2008 R2 Enterprise 16 GB 64-bit, SP1 or later server or client

Notes:
1. 16 GB or more memory, dedicated to the C•CURE 9000.
2. Windows Server 2012 R2 is preferable over Windows Server 2012.
3. Windows Server 2008 (Vista base) is not supported, only Windows Server 2008 R2.
 Microsoft OS for MAS (2.40 Version)

MAS Server Memory Supported Node

Version
Windows Server 2012 R2 Standard 16 GB 64-bit server or client
Windows Server 2012 Standard 16 GB 64-bit server or client
Windows Server 2008 R2 Standard or Enterprise 16 GB 64-bit, SP1 or later server only

Client Memory Supported Node

Recommended
Version
Windows 7 Professional 8 GB 64-bit, SP1 or later client only
Windows 8.1 Professional 8 GB 64-bit client only
Windows Server 2012 R2 8 GB 64-bit client only
Windows Server 2012 8 GB 64-bit client only Supported
Windows Server 2008 R2 Standard 4 GB 64-bit, SP1 or later client only
Windows 8.1 Enterprise 4 GB 32-bit, SP1 or later client only
Windows 7 Professional 4 GB 32-bit, SP1 or later client only

Notes:
1. 16 GB minimum for MAS Servers, Clients either 8 GB (64 bit) or 4 GB (32 bit).
2. Windows Server 2012 R2 is preferable over Windows Server 2012.
3. Windows Server 2008 (Vista base) is not supported, only Windows Server 2008 R2.
 C•CURE 9000 v2.40 – SQL Server (Standalone Systems)

Server Series Standalone L/M/N Supported Version

SQL Server 2008 R2 Express 10.50.1600.1 RTM (64 and 32 bit)
SQL Server 2008 R2 Standard 10.50.1600.1 (64 and 32 bit) Supported
SQL Server 2008 R2 Enterprise 10.50.1600.1 (64 and 32 bit)
SQL Server 2012 Express SP1 or later (64 and 32 bit)
SQL Server 2012 Standard SP1 or later (64 and 32 bit) Recommended
SQL Server 2012 Enterprise SP1 or later (64 and 32 bit)
SQL Server 2014 Express (64 and 32 bit)
SQL Server 2014 Standard (64 and 32 bit) Supported
SQL Server 2014 Enterprise (64 and 32 bit)
Server Series Standalone P/Q/R/R+/S Supported Version*
and SAS Server Series L/M/N
SQL Server 2008 R2 Express * 10.50.1600.1 RTM (64 and 32 bit)
SQL Server 2008 R2 Standard 10.50.1600.1 (64 and 32 bit) Supported
SQL Server 2008 R2 Enterprise 10.50.1600.1 (64 and 32 bit)
SQL Server 2012 Express * SP1 or later (64 and 32 bit)
SQL Server 2012 Standard SP1 or later (64 and 32 bit) Recommended
SQL Server 2012 Enterprise SP1 or later (64 and 32 bit)
SQL Server 2014 Express * (64 and 32 bit)
SQL Server 2014 Standard (64 and 32 bit) Supported
SQL Server 2014 Enterprise (64 and 32 bit)
* SQL Server Express is supported for SAS Servers Series L/M/N. However, Software House recommends
using full SQL Server Standard/Enterprise with C•CURE 9000 v2.40 for the best performance.
 C•CURE 9000 v2.40– SQL Server (SAS and MAS
Servers)

SAS Server Series P/Q/R/R+/S Supported Version

SQL Server 2008 R2 Standard 10.50.1600.1 (64 and 32 bit)
Supported
SQL Server 2008 R2 Enterprise 10.50.1600.1 (64 and 32 bit)
SQL Server 2012 Standard SP1 or later (64 and 32 bit)
Recommended
SQL Server 2012 Enterprise SP1 or later (64 and 32 bit)
SQL Server 2014 Standard (64 and 32 bit)
Supported
SQL Server 2014 Enterprise (64 and 32 bit)
MAS Server Supported Version
SQL Server 2008 R2 Standard 10.50.1600.1 (64 bit)
Supported
SQL Server 2008 R2 Enterprise 10.50.1600.1 (64 bit)
SQL Server 2012 Standard SP1 or later (64 bit)
Recommended
SQL Server 2012 Enterprise (64-bit)
SQL Server 2014 Standard (64-bit)
Supported
SQL Server 2014 Enterprise (64-bit)

Note: For the PC Hardware Minimum Requirements, please refer to the Software House
web page, at the “System Specification Estimator” section.
www.swhouse.com/TSPEstimator/Default.aspx
C•CURE 9000 v2.40 – SQL Language Collations
Windows Locale Default Collation
Arabic (Saudi Arabia) Arabic_CI_AS
Chinese (PRC) Chinese_PRC_CI_AS
Chinese (Taiwan) Chinese_Taiwan_Stroke_CI_AS
Czech (Czech Republic) Czech_CI_AS
Danish (Denmark) Danish_Norwegian_CI_AS
Dutch (Netherlands) Latin1_General_CI_AS
English (United Kingdom) Latin1_General_CI_AS
French (France) French_CI_AS
German (Germany) Latin1_General_CI_AS
Hungarian (Hungary) Hungarian_CI_AS
Italian (Italy) Latin1_General_CI_AS
Japanese (Japan) Latin1_General_CI_AI
Korean (Korea Dictionary Sort) Korean_Wansung_CI_AS
Polish (Poland) Polish_CI_AS
Portuguese (Brazil) Latin1_General_CI_AS
Russian (Russia) Cyrillic_General_CI_AS
Spanish (Spain) Modern_Spanish_CI_AS
Swedish (Sweden) Finnish_Swedish_CI_AS
Turkish (Turkey) Turkish_CI_AS
 Supported Languages

• Arabic, Brazilian Portuguese, Czech, Danish, Dutch,

English, French, German, Hungarian, Italian, Japanese,
Korean, Polish, Russian, Simplified Chinese, Spanish,
Swedish, Traditional Chinese and Turkish
C·CURE 9000
Hardware

Company Confidential
 The Hardware

• The C·CURE 9000 supports apC Panels and iSTAR Controllers.

• iSTAR Controllers
− iSTAR Classic/Pro, iSTAR Edge and iSTAR Ultra are Ethernet-ready
controllers. C•CURE 9000 acts as a database and journal host, and
networks to the iSTAR controllers for initial set-up, managing
peripheral hardware, and generating activity reports.
− The host downloads personnel information, configuration information,
and event-directed actions to the iSTAR controllers, which enable
local management of events without host intervention.
• apC Panels
− The advanced processing Controller (apC) panel is an intelligent field
device that performs basic access control tasks. The apC/8X or apC/L
access control field panels coordinate communication between the
C•CURE 9000 server and the system security hardware, such as card
readers.
 The Hardware

• The available hardware is composed of:

− Door Controllers and Panels
 apC/L: 2 readers panel
 apC/8x: 8 readers panel
 iSTAR Pro: 8 or 16 readers controller
 iSTAR PRO 2U Rack: 8 or 16 readers controller
 iSTAR Edge 1 reader controller
 iSTAR Edge: 2 readers controller
 iSTAR Edge: 4 readers controller
 iSTAR Ultra: 8 or 16 Wired readers, plus 16 Wireless Lock sets.
− Personality Module
 RM-4 & RM-4E: Reader interface module
− Inputs and Outputs Modules
 I/8 and I/8 CSI (Custom Supervised Input Board): 8 Inputs expansion
module
 R/8: 8 Outputs expansion module
Controller and Panels

iSTAR PRO iSTAR Edge iSTAR Ultra

2U RACK iSTAR PRO apC/L apC/8X

General Reader Bus Boards

RM-4 RM-4E

R/8 I/8
 Software House Multi-Technology Readers

• Reads more than 10 different

types of proximity cards and
contactless smart cards1
• Card Technologies Supported
− HID proximity
− CASI® ProxLite®
− Deister proximity
− ISO 14443A serial number
− MIFARE® serial number
− DESFire serial number
− ISO 14443B serial number
− ISO 15693 serial number
− iCLASS® serial number
− MIFARE sectors
 Multi-Technology Reader with Indala Support (SWH-
4130)

• Triple-receiver design allows simultaneous

reading of HID® proximity cards, Indala®
proximity cards, and contactless smart cards
• Card Technologies Supported (Additional
ones can be programmed check DS )
− HID proximity
− Indala proximity
− MIFARE serial number
− DESFire® serial number
− ISO 14443A, 14443B, and 15693 serial
number
− iCLASS® serial number
− MIFARE sector read
• Communications
− Wiegand data stream to controller
− Flashable via local RS-485
 Software House RM Series Card Readers

• Full suite of RM readers that

includes proximity, smart card, ,
HID® iCLASS®, multi-
technology and magnetic stripe
technologies.
• Keypad and backlit LCD can be
utilized on select RM readers to
provide system status and
duress capabilities
• Each RM reader provides two
supervised inputs and two
control point outputs
• Three high-intensity LEDs (red,
amber, and green) and keypad
audio feature indicate system
conditions
 Summary

1. Name the Operating system supported by the current version for

C·CURE 9000 Server and Client
2. Name the Databases supported
3. What’s the Administration Application used for?
4. What’s the Monitoring Station main use?
5. Is it possible to open two or more Monitoring Application in the
same PC?
6. The Client number for each Series, what does it refers to, Client
Computers or open Applications?
7. Name the Controllers available and the doors each one supports
8. What’s and Enterprise system?
9. Name some of the new features at the current release