Your SlideShare is downloading. ×
Sierra Access and Door Control with InduSoft
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Sierra Access and Door Control with InduSoft


Published on

Presentation by Sierra Detention Systems for Access and Door Control Webinar with InduSoft Web Studio

Presentation by Sierra Detention Systems for Access and Door Control Webinar with InduSoft Web Studio

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. [ Company [ Products Security electronics |Founded in detention equipment | custom Market High-security and Territory Nationwide and UL panel shop, clean1995 in Colorado metal products | building correctional facilities international coverage manufacturer automation | fire alarm
  • 2. [Expertise: Detention Equipment [ Sierra furnishes and installs:  Detention hollow metal doors and frames  Detention furniture  Pre-fabricated cells  Specialty locks  Wire mesh and grating  Glass and glazing  Perimeter security fencing
  • 3. [Expertise: Security Electronics [Sierra furnishes, integrates, and installs the followingsystems: Touch screen control systems Tablet & PDA systems Utilities control/ Building Automation System (BAS) Controlled access Multi-tasking CCTV Fire alarm/detection Video visitation IP addressable equipment Digital and analog equipment Industrial networking Remote access secure LAN Man-down, duress systems Intercoms Facility specific, requested systems
  • 4. INDUSOFTWEBINARAccess ControlBy Sierra Detention SystemsPaul Miracle, ControlsEngineering
  • 5. DETENTION INDUSTRYCONSIDERATIONS Physical Security  General Public  Facility Staff  Inmates System Stability / Redundancy / Failover Required  Each HMI capable of standalone operation  Prioritized sequence of failover System activity mainly user driven, not automated/process driven  Emphasis on “human” part of HMI
  • 6. HMI COMPUTER SECURITY Physical  InduSoft Hardkeys are secured to the HMI to prevent removal  HMIs secured in locked cabinets  Keyboard / mouse removed on touchscreen based systems  Auto-Run features of the Operating System disabled
  • 7. HMI COMPUTER SECURITY InduSoft  Project runs automatically on HMI startup  Security System used to prevent access to the Operating System  Close Project disabled  Task Switch (Alt-Tab) disabled  Task Manager disabled  Security System used to prevent Engineering Access by application users  Auto-Logoff enabled for all groups with Engineering Access
  • 9. HMI COMPUTER SECURITY Application  InduSoft startup screen prevents access to the system without a valid logon  Once logged in, navigation is restricted based on HMI station and user  Device icon commands are disabled by default and must be enabled by the PLC in order for them to operate  Some devices have additional security restrictions (interlocks, exterior doors, etc.)  Some functions have additional restrictions (Group Release, Emergency Release, etc.)  HMIs can be remotely disabled in the event of a security breach
  • 10. SYMBOL LEVEL SECURITY Position Properties Command Disable Field User / Group Level Checks
  • 11. DOOR CONTROL ARCHITECTURE Class based  All doors have identical capabilities  Individual door functionality based on the parameters assigned to the class members  Provides flexibility to modify functionality without modifying code
  • 12. DOOR CONTROL ARCHITECTURE Database back end  Used for loading / storing device parameters  Provides flexibility (device names, etc.)  Retentive tags allow offline operation
  • 13. DOOR CONTROL ARCHITECTURE Communication  PLC Communication accomplished primarily Standard Driver Sheets  Allows enabling/disabling of individual sheets to optimize efficiency Scripting  Extensive use of global procedures to centralize code  Extensive use of VBScript within global procedures to enhance built-in functionality Graphics  Symbols created for all devices to make modifications easy  Symbols primarily indicate device status only and contain minimal logic