The GFMS (Global Facilities Management System) by Key Systems, Inc. is a high-security software platform designed to manage and monitor electronic key cabinets and assets in real-time.
Below is a draft guide overviewing the essential operational and administrative functions typically found in the GFMS Key Systems Manual. 1. System Architecture & Requirements
The GFMS software is browser-based, eliminating the need for local client installations. It can be hosted on a local PC, a server, or via the GFMS Cloud Service.
Hardware Compatibility: Manages all Security Asset Manager (SAM) cabinets and electronic lockers.
Server Support: Compatible with Windows Server (2016-2025) and Windows 11.
Database: Supports SQL Server 2019/2022 and can integrate with existing HR or access control databases via the GFMS Sync Tool. 2. Administrative Setup & User Management
Administrators use a single dashboard to control the entire facility's asset network.
User Enrollment: Users can be added manually or synchronized from external databases. Fast enrollment is possible using barcode readers or card credentials.
Custom Roles: You can delegate control by creating administrative groups with specific permissions.
Default Credentials: Crucial Security Tip: Change the default administrator username and PIN immediately upon setup to prevent unauthorized remote access. 3. Rule Configuration & Security Policies gfms key systems manual
The GFMS rules engine allows for granular control over how and when keys are released.
Multi-User Rules: Configure "Dual" or "Triple" PIN requirements, ensuring a high-security key can only be pulled when two or three authorized personnel are present.
Time Zone Management: Synchronize time zones across global installations to ensure accurate reporting and restricted access based on local business hours.
Asset Assignment: Link specific keys to unique user IDs or job titles. 4. Real-Time Monitoring & Reporting
Event Logging: Every transaction (key pull, return, or cabinet access) is logged 24/7.
Automated Alerts: Configure the system to send SMS or email alerts for critical events, such as a key not being returned on time or an unauthorized access attempt.
Site Maps: Use interactive facility maps to view the live status and location of every SAM cabinet in your network. 5. Troubleshooting & Maintenance Global Facilities Management Software™ (GFMS™)
GFMS Key Systems Manual: A Comprehensive Guide to Key Control
The Global Facilities Management System (GFMS™), developed by Key Systems, Inc. (KSI), is a web-enabled asset management platform designed to control, monitor, and audit high-security electronic cabinets and key boxes. This guide serves as a manual for understanding the system's architecture, core features, and operational requirements. 1. System Overview The GFMS (Global Facilities Management System) by Key
Unlike standard software, GFMS™ is a comprehensive ecosystem that bridges security hardware and real-time management software. It acts as the "backbone" for various KSI devices, including Security Asset Managers (SAM), electronic lockers, and emergency entry devices. Key Deployment Options:
Local Install: Hosted on an organization’s server or PC using Microsoft SQL Server and IIS.
GFMS™ Cloud Services: A turn-key, IT-less solution where KSI manages the server, updates, and backups. 2. Core Operational Features
Administrators can manage the entire facility’s key and asset inventory from a single, browser-based screen.
Multi-User Rule Engine: Create "Dual" or "Triple PIN" rules for high-security assets. For example, a master key might only release if both a Security Guard and a Supervisor enter their PINs.
Real-Time Alerts: Programmable notifications for breaches or overdue keys are sent via email or SMS.
Interactive Site Map: View real-time status and exact locations of SAM units through interactive facility maps.
Integration Tools: The GFMS™ Sync Tool allows automated synchronization with existing HR or access control databases (SQL, Oracle, CSV). It also integrates with systems like LenelS2 OnGuard. 3. User Authentication Methods
GFMS™ supports a wide array of User ID options to suit different security levels: Global Facilities Management Software™ (GFMS™) What is the GFMS Key Systems Manual
You can use this as a cover page/introduction or the opening section of the manual.
The GFMS Key Systems Manual is a standardized operational document that governs the lifecycle, hierarchy, and control of mechanical keys and electronic access credentials within a facility. Unlike a simple key log, the GFMS manual is a comprehensive governance tool. It outlines the "Grand Master," "Master," and "Change" key levels, defines who holds which keys, establishes rekeying schedules, and sets the protocol for lost keys or security breaches.
While "GFMS" can refer to internal industry standards, in this context, it represents the best-practice framework for facility security management. The manual removes guesswork, ensuring that a contractor, a new hire, or an external auditor can understand your key hierarchy within minutes.
The GFMS Key Systems Manual is a formal, controlled document that defines the operational, technical, and security parameters of a financial management system. It serves as the authoritative reference for:
Unlike a user guide (which teaches “how to click buttons”) or a technical specification (which details code libraries), the Key Systems Manual bridges governance and execution. It answers: “Under what rules does the system operate?”
This is the "org chart" of your physical security.
The manual must visually map these relationships. Without this chart, a change key is just a piece of metal.
The manual is a book; it needs a home. Purchase a heavy-duty, lockable key cabinet. The GFMS Key Systems Manual should sit next to the cabinet, not inside it. The manual holds the log; the cabinet holds the metal. Install a check-out/in card system that syncs with the manual.
The GFMS Key Systems Manual is structured like a seasoned technician’s brain:
Maya flipped to the "Conflict Resolution" chapter — it outlined a stepwise approach: isolate affected controllers, revert to last known-good configuration, reissue temporary keys, and document each action for audits.