Operations Center's architecture
Mastering Operations Center: Key Principles and Integration Strategies
Learning the principles of Operations Center helps you best understand how the system is designed and to present the unique points of value to your customers. Understanding how Operations Center can be integrated into other Genetec™ services or systems in the customer's environment is critical to successfully delivering a solution.
This module will give you an understanding of the details, but additional technical training is available beyond the scope of this.
Overview of the Genetec™ Operations Center solution
1. Born in the cloud: Offered as a service, with intuitive web and mobile apps, providing an always connected and up to date experience
2. Unified & open: Native connectivity with the Genetec™ security ecosystem, also allowing integration with the end user’s ecosystem
3. Advanced & Scalable: Enterprise-grade work management platform allowing organizations to manage large amounts of resources
Adapted to your needs: Monitoring, management, and reporting experiences can be fully customized to your business requirements
Event-Driven Architecture and API-First Design in Operations Center
Event driven architecture
Any input in the system is an event: Events are stored in patent-pending immutable block chains for tamper proof audits
API-first
Operations Center is built API-first. EVERY function is exposed in the APIs: API information is available in the product documentation
Overview of Operations Center architecture concepts and benefits.
Accessible Anywhere, Anytime
Operations Center is built to be used by both web browser (Windows, Mac, Linux and mobile apps (Apple and Android, phones and tablets). This means we don’t have to worry about installing client station software and maintaining it. Customers can also benefit from being able to work from almost anywhere in the world with an internet connection.
SaaS Benefits: No Hosting, Backup, or Maintenance Required
Additional benefits of a SaaS product which are popular with many IT departments is that they have no software to host, backup, or maintain. The customer simply uses the system.
Managed System Advantage: Centralized Maintenance Without Truck Rolls
Plus, as Operations Center is built as managed system, operated by Genetec™. Your technical teams can maintain all of your customer systems from the same pane of glass without having to roll a truck.
How do our solution(s) specifically help address the customer challenges?
- Information can be brought into or pulled out of Operations Center through our APIs, and to make this happen, we make the APIs available to every user with our in-app documentation section.
- Additionally, we want to make connecting to common business systems simple for everyone. Our in-app documentation section explains how to configure our Microsoft Power Automate Custom Connector. This can allow for parsing documents for bulk creation, adding additional automation, and utilizing existing tools like web forms with our system.
Overview of technical benefits from Genetec integrations
Security Center
1. Automated work requests triggered by system events
2. Manual work requests triggered by Security Desk users
Security Center SaaS Premium
1. Preconfigured work ticketing solution
2. Manual work requests triggered users
Getting Started with Sales: Target Audience, Discovery Questions, and Key Points
1. Skills needed
Understand the Customer’s Environment:
Technology Overview: Determine what technology the customer uses both in the office and in the field. For example, command centers may have operator workstations with multiple monitors, radios, VoIP phones, and various software systems, while field officers might only have radios and lack access to software.
2. Integration Needs:
External Tools:
Identify if the customer needs to integrate external tools like Slack, Teams, email, or ticketing systems with Operations Center.
3. Integration with Security Center:
System Connectivity & Configuration
System Connectivity: Check if Operations Center will be connected to a Security Center system and ensure both server and client workstations have internet access.
Configuration: Determine who will configure Automation or Event-to-Action rules.
4. Database Connections:
Necessary Databases:
Identify which databases need to be connected for Operations Center, such as Active Directory for user management and identity management systems for resource management.