IR WIKI

Inception Programming Guide

3 min read

Inception Programming Guide

Overview

This guide covers the core programming logic for the Inception system, focusing on user management, permission structures, and time-based automation. Unlike Integriti, Inception utilizes a simplified “What and When” structure for permissions and a built-in web-based scheduler for routine automation.

Technical Details

User Management

A user is defined as any entity that interacts with the system via access cards, PINs, remote fobs, or the web interface.

  • Unique Identifiers: Every user must have a unique name.
  • Security PINs: Default length is 2 to 8 digits. PINs are used for terminal access and can be used as a password alternative for the web interface (PIN entry mode).
  • Web Profiles: Assigned to users to determine which web pages are visible upon login and to define Dashboard Favourites.

Permission Logic (What and When)

Permissions in Inception follow a declarative “What and When” structure:

  • What: The target entity (Door, Area, Hardware Output) and the specific action allowed (Access, Arm/Disarm, Control).
  • When: The time-based constraint (Always or a specific Time Period).

Scheduling Architecture

Scheduling is the combination of Time Periods and Calendars:

  • Time Periods: Define recurring weekly time blocks (e.g., Mon-Fri 09:00-17:00).
  • Calendars: Provide exceptions to recurring time periods (Single Dates, Date Ranges, or Calculated Dates like “Second Tuesday of the month”).
  • Scheduler: A dedicated interface to link Time Periods to system actions (Auto-unlock doors, Auto-arm areas) without modifying core object configurations.

Configuration / Programming

1. User Setup

Path: [Configuration > Users > Manage Users]

  1. Click Add to create a new user.
  2. Assign a Security PIN (use ‘Generate’ for a unique unused code).
  3. Add Credentials:
    • To add a card, present it to a reader first, then click Add From Recent Card Reads.
    • To add a remote, click Add From Recent Fob Event.
  4. Configure Web Login Details if web access is required, selecting an appropriate Web Page Profile.

2. Permissions and Groups

Path: [Configuration > Users > Permission Groups]

  1. Define a Permission Group based on roles (e.g., “Warehouse Staff”).
  2. Add Permissions using the structure:
    • [Allowed/Deny] -> [What (Item)] -> [How (Action)] -> [When (Time Period)]
  3. Assign the group to the relevant users. Permissions can also reference other permission groups to create hierarchies.

3. Scheduling (Time Periods & Calendars)

Path: [Configuration > Scheduling > Time Periods]

  1. Define the Weekly Recurring blocks.
  2. Add Exceptions by linking a Calendar item.

Path: [Configuration > Scheduling > Calendars]

  1. Single Dates: Specific dates (optionally recurring annually).
  2. Date Ranges: Start and End dates for holidays or shutdowns.
  3. Calculated Dates: Logic-based dates (e.g., “Last Friday of every month”).

4. System Automation

Path: [Configuration > Scheduling > Scheduler]

  • Use this page to apply Time Periods to:
    • Doors: Set automatic unlock/relock times.
    • Areas: Set automatic arming/disarming schedules.
    • Lifts: Set free access schedules for floors.

Troubleshooting

Failed Arming from Web Interface

If an area fails to arm, a dialog will appear showing the specific unsealed inputs. Use the Isolate and Retry button to override faulty detectors if necessary (refer to Inception Maintenance for isolation policies).

Terminal Access Issues

  • Ensure the user’s PIN is correctly entered (up to 8 digits).
  • Terminals automatically log off after 1 minute of inactivity.
  • If “Menu” options are missing, verify the user’s Permission Group includes the “What” for that terminal’s associated items.

Graph View

Backlinks