Digifort Integration
The ACCELERO integration with the Digifort CCTV system allows access events to be automatically sent to Digifort in the form of bookmarks, making it easier to search for videos related to access attempts.
This feature requires the integration module enabled in the license. Contact IONGRADE for availability.
Overviewβ
The Digifort integration offers:
| Feature | Description |
|---|---|
| Automatic Bookmarks | ACCELERO access events automatically create bookmarks in Digifort |
| Camera Γ Controller Association | Configure which cameras are filming which barriers |
| Colored Bookmarks | Different event types generate bookmarks of different colors |
| Easier Search | Quickly find videos of specific events in Digifort |
The integration eliminates the need to manually search for videos by date/time. Just look for the bookmark of the access event in Digifort and the video will already be marked at the exact moment.
Architectureβ
Required Componentsβ
- Digifort Server with the API enabled
- ACCELERO/Digifort Gateway (IONGRADE product)
- ACCELERO Server with the module enabled
- Communication network between gateway and servers
The gateway receives configurations/events from the ACCELERO server and communicates with the Digifort server to automatically create the bookmarks according to the configured parameters.
Network Topologyβ
Recommendation: The gateway should be on the same physical network as the Digifort server.
[Access Event in ACCELERO]
β
[ACCELERO Server]
β
[Gateway]
β
[Digifort Server]
β
[Bookmark Created]
Configuration in ACCELEROβ
General Data of the Digifort Serverβ
Path: Advanced > System > Integrations - Digifort > General
Configure the basic access data for the Digifort server:
| Field | Description |
|---|---|
| IP Address | IP address of the Digifort server |
| API communication port | TCP port of the Digifort API (usually 80 or a custom port) |
| User | User for authentication in the Digifort API |
| Password | Authentication password |
Make sure the Digifort API is enabled and accessible. Consult the Digifort documentation on how to enable and configure the API.
Include a screenshot of the general data configuration screen showing the connection fields with the Digifort server.
Gateway Registrationβ
Path: Advanced > System > Integrations - Digifort > Gateways
Configure the communication gateways present in the installation.
| Field | Description |
|---|---|
| Serial number | Serial number of the gateway (obtain it from the physical equipment) |
| Description | Name/description of the gateway |
Monitoring:
- Gateway communication status with ACCELERO
- Gateway communication status with the Digifort server
In general, a single gateway is needed for the entire installation, regardless of the number of cameras or controllers.
On this tab you can check the communication status of the gateway and of the Digifort server for maintenance and tracking purposes.
Include a screenshot of the gateways screen showing communication status.
Controller/Camera Associationβ
Path: Advanced > System > Integrations - Digifort > Controllers/cameras
This configuration is essential for the integration to work: it defines which cameras are filming which controller.
How It Worksβ
When an access event happens at a barrier, the system creates bookmarks in the cameras associated with that barrier.
Example:
Controller NEON-01, Channel 1 (Reception Turnstile)
β Camera 1 (Front View)
β Camera 2 (Side View)
Event: Access authorized on Channel 1
Result: Bookmarks created in Camera 1 AND Camera 2
Configurationβ
Association options:
| Configuration | Description |
|---|---|
| One camera β Multiple controllers | One camera can be associated with several controllers (e.g., a panoramic camera filming 3 turnstiles) |
| Multiple cameras β One controller | One controller can have multiple associated cameras (e.g., front view + side view) |
| Any combination | Configure freely according to the physical topology |
Get the List of Cameras from Digifortβ
Useful resource: After configuring the communication gateway, use the "Update camera list" button to automatically obtain the list of all cameras available in Digifort.
Benefit:
- Avoids typos
- Ensures correct camera names
- Makes configuration easier
Before configuring, make a physical mapping:
- List all barriers/controllers
- Identify which cameras film each barrier
- Note the camera names in Digifort
- Configure the associations
Include a screenshot of the controller/camera association screen showing the "Update camera list" button and the configuration interface.
Bookmark Configurationβ
Path: Advanced > System > Integrations - Digifort > Bookmarks
Configure which events from access control should create bookmarks and what color each bookmark has.
Event Typesβ
ACCELERO generates several types of access events. For each type, you can configure:
| Configuration | Options |
|---|---|
| Create bookmark? | Yes / No |
| Bookmark color | Red, Yellow, Green, Blue, etc. (colors supported by Digifort) |
Configuration Examplesβ
Recommended configuration for security:
| Event Type | Create Bookmark? | Color |
|---|---|---|
| Access performed | β No | - |
| Access denied | β Yes | π΄ Red |
| Access denied by APB | β Yes | π‘ Yellow |
| Forced access | β Yes | π΄ Red |
| Door held open | β Yes | π Orange |
| Duress | β Yes | π΄ Red |
Configuration for complete auditing:
| Event Type | Create Bookmark? | Color |
|---|---|---|
| Access performed | β Yes | π’ Green |
| Access denied | β Yes | π΄ Red |
| All events | β Yes | Varied colors by type |
- Security: Mark only abnormal events (denials, alarms)
- Auditing: Mark all events
- Performance: The fewer bookmarks, the lower the load on Digifort
General recommendation: Mark only relevant events to avoid overloading the system with bookmarks.
Check which colors are supported by the installed version of Digifort. Colors may vary depending on the version.
Include a screenshot of the bookmark configuration screen showing the list of events and color options.
How the Integration Worksβ
Complete Flowβ
-
An access event occurs in ACCELERO:
- Person presents a card at the reader
- System authorizes or denies access
- Event is recorded in the log
-
System checks the configuration:
- Should the event type create a bookmark? (check the bookmark configuration)
- If NO β Process ends
- If YES β Continues
-
Camera identification:
- System identifies the controller/channel where the event occurred
- Checks the controller/camera association
- Identifies the cameras that film that location
-
Gateway receives the command:
- ACCELERO sends to the gateway:
- Event timestamp
- Cameras that should receive the bookmark
- Bookmark color
- Event description
- ACCELERO sends to the gateway:
-
Gateway communicates with Digifort:
- Gateway connects to the Digifort API
- Creates a bookmark in each associated camera
- Uses the exact event timestamp
- Applies the configured color
-
Bookmark created:
- Bookmark appears in Digifort
- Operator can search by bookmarks
- Video already positioned at the exact moment of the event
Practical Exampleβ
Scenario: Access attempt denied due to schedule
- JoΓ£o tries to access at 22:00 (outside the allowed schedule)
- ACCELERO denies access β "Access denied due to schedule" event
- Configuration defines: "Access denied" = RED bookmark
- Controller: NEON-01, Channel 2
- Associated cameras: CAM-03 (front), CAM-04 (side)
- Gateway creates 2 red bookmarks:
- CAM-03: 22:00:15 - "Access denied - JoΓ£o Silva"
- CAM-04: 22:00:15 - "Access denied - JoΓ£o Silva"
- Security opens Digifort and sees red bookmarks at 22:00
- Clicks the bookmark β video already positioned at the exact moment
Without integration: security would have to manually search Digifort by date/time/camera.
With integration: just click the red bookmark and watch the video.
Use Casesβ
Security - Incident Investigationβ
Challenge: Investigate all denied access attempts in a period.
Solution:
- Configure "Access denied" events with a red bookmark
- In Digifort, filter by red bookmarks
- View all videos of denied accesses
Benefit: Fast and efficient investigation.
Auditing - Complianceβ
Challenge: Prove accesses performed in a restricted area.
Solution:
- Configure "Access performed" events with a green bookmark for specific areas
- In Digifort, filter by green bookmarks
- Export videos for auditing
Benefit: Automatic visual evidence.
Emergency - Alarm Monitoringβ
Challenge: Quickly identify duress or forced-door events.
Solution:
- Configure alarm events with a red bookmark
- Monitor Digifort in real time
- Red bookmarks = immediate attention
Benefit: Quick response to critical situations.
Best Practicesβ
Planningβ
-
Map cameras and barriers:
- Survey the installation physically
- Identify coverage angles
- Document associations
-
Define a bookmark policy:
- Which events are relevant?
- Which colors to use?
- Consider the event volume
-
Check Digifort resources:
- API enabled?
- Compatible version?
- Supported colors?
Operationβ
-
Configure only relevant events:
- Avoid creating bookmarks for all events
- Focus on exceptions and alarms
- Reduce "noise" in Digifort
-
Use consistent colors:
- Define a color standard
- Document the meaning of each color
- Train the team
-
Test the associations:
- After configuring, generate a test event
- Check whether the bookmark appears in Digifort
- Confirm that the correct camera received the bookmark
Maintenanceβ
-
Check communication:
- Gateway β ACCELERO
- Gateway β Digifort
- Digifort API active
-
Update associations:
- When cameras are moved
- When barriers are added/removed
- After physical changes to the installation
-
Monitor performance:
- Volume of bookmarks created
- Digifort performance
- Adjust the configuration if necessary
-
Configuration backup:
- Document camera/controller associations
- Save the bookmark configuration
- Makes restoration easier
Troubleshootingβ
Bookmarks are not createdβ
Possible causes:
- Gateway without communication
- Digifort API inactive or inaccessible
- Event not configured to create a bookmark
- Incorrect credentials
Solution:
- Check the gateway communication status
- Test access to the Digifort API manually
- Confirm that the event type is configured to create a bookmark
- Check the API user/password
- Consult the gateway logs
Bookmarks created in the wrong cameraβ
Possible cause:
- Incorrect controller/camera association
Solution:
- Check the association in the configuration
- Confirm that the correct controller/channel is associated
- Use the "Update camera list" button to verify names
- Fix the association
- Test again
Bookmarks appear with the wrong colorβ
Possible cause:
- Incorrect event color configuration
Solution:
- Check the bookmark configuration
- Confirm the color configured for that event type
- Change if necessary
- Test with a new event
Gateway shows offlineβ
Possible causes:
- Network problem
- Gateway turned off
- ACCELERO server without communication
Solution:
- Check whether the gateway is on and on the network
- Test a ping to the gateway
- Check network connectivity
- Restart the gateway if necessary
- Check the firewall configuration
The Digifort API does not respondβ
Possible causes:
- API disabled
- Firewall blocking
- Incorrect credentials
- Incompatible version
Solution:
- Check whether the API is enabled in Digifort
- Test API access via browser or Postman
- Confirm the correct port
- Check firewall rules
- Consult the Digifort documentation about the API
Integration with Other Modulesβ
Event Logβ
Relationship: Events recorded in the log generate bookmarks
Important:
- Configure the Event Log to capture the desired events
- See Logs and Monitoring
Controllersβ
Relationship: Events occur in specific controllers/channels
Important:
- The association depends on controllers being registered correctly
- See Controllers
Areasβ
Relationship: Areas can have associated cameras and barriers
Important:
- Plan the topology of areas and cameras
- See Areas
Next Stepsβ
- Logs and Monitoring - Understand event types
- Controllers - Configure controllers
- Areas - Organize access areas
- Licensing - Check the available module