1.0 / 2026-10-12

Production restructuring and Integration Manual template application to the 2026-02-25 technical baseline; procedures and test coverage retained.

Production document with embedded integration test catalogue.

✓

IAS

Perimetry

FPS

Building

CCTV

Other

Combined Credentials

Card Learning

Lift

✓

Dynamic Upload

✓

Encrypted Communication

✓

Access Time Restrictions

Load Configuration

Holidays Support

Time Synchronization

✓

PIN Management

Time Zone Support

✓

Card Management

Live Video Streaming

Fingerprint Management

Recorded Video Streaming

Reserved Memory Zones

Video Records Downloading

Antipassback Forgiveness

Voice Transmitting

✓

Handicapped Flag

Audio Streaming

Alarm Suppression

PTZ

Fire Alarm Counter

Presets

✓

Device Audit Log Retrieval

Motion Detection

✓

Remote Device Control

Live Stream Snapshot

Wiegand Biometric Support

Record Stream Snapshot

Discovery

Multiple Stream Types

Sending Configuration

Person Data Read

✓

Migration to C4 Transformers

C4 framework

C4 FWK4

Document scope and title.

Manufacturer software

IQ Multi Access 27.10.x.x development baseline

DotNetConCtr.dll must match the installed IQ Multi Access version.

Panel firmware

MB-Secure firmware V04 or later

Required for the ISOM channel.

ISOM transport

Secure WebSocket on TCP 443; TLS 1.2 or higher

Remote MANAGEMENT-SOFTWARE client required.

IQMA transport

TCP 23757 to the IQ Multi Access server

IQ Server service, DotNetConCtr.dll and cacert.pem required.

Panel entitlement

Minimum OEM Level 2; OEM Level 3 for event-log access

Intrusion/access control and audit-log scope.

Enabled

Defines whether circuit usage is enabled

Yes

Time Zone

Device location time zone

System Time

IP Address

IP Address of the computer where IQ Multi Access is installed.

Port

Communication port used by IQ Multi Access.

23757

0 - 65535

Username

System operator account defined in IQ Net Edit.

Password

Password of the System operator account defined in IQ Net Edit.

FreeDrivenId

Login identifier of the IQ Multi Access node in IQ Net Edit (Hardware View).

Credential Upload enabled

Enables user synchronization for this panel.

Yes

Yes/No

Night Full Upload

Night Upload

Night Incremental Upload

None

Schedule Max Number

Maximum number of rooms/time zones the device can store; for example, 256 for MB-Secure 6000.

10000

0 - 65535

UserRecord Max Number

Maximum number of persons the device can store; for example, 1,024 for MB-Secure 6000.

10000

32-bit unsigned integer

Timeout

00:00:30

Original Device Name

Description parameter of the Controller/Terminal in IQ Net Edit. This is mandatory.

IP Address

IP address of the MB-Secure panel.

Port

MB Secure WebSocket communication port

443

0 - 65535

Username

Remote client account name

Password

Remote client password

Time Zone

Device location time zone

System Time

Time Zone

Timeout

WebSocket communication timeout

Time Synchronization Interval

Interval for periodic time synchronization between C4 and MB Secure Panel

Original Device Name

Description parameter of the Controller/Terminal in IQ Net Edit.

Address

OPIF ID of VirtualPeripheral

0 - 65535

Address

OPIF ID of Partition

0 - 65535

Original Device Name

Address

OPIF ID of VirtualDoor

0 - 65535

Original Device Name

Name parameter in IQ Multi Access. This is mandatory.

Address

OPIF ID of AccessPoint. This is mandatory only for card readers under MB Secure Panel.

0 - 65535

Access Direction

Reader movement direction

None

In

Out

None

Supported Credential Types

Credential types that this reader can enroll

Address

OPIF ID of DetectorGroup

0 - 65535

Address

OPIF ID of VirtualSmokeDetector

0 - 65535

Address

OPIF ID of VirtualPIR

0 - 65535

Address

OPIF ID of VirtualInput

0 - 65535

Event Level

Processing level for the Input Activated status

Info

Silent

Info

Warning

Alarm

Address

OPIF ID of VirtualOutput

0 - 65535

Partition

Partition

0x00100000

1048576

Detector Group

DetectorGroup

0x00300000

3145728

Card Reader

AccessPoint

0x00400000

4194304

Door

VirtualDoor

0x00120000

1179648

Input

VirtualInput

0x00140000

1310720

Output

VirtualOutput

0x00170000

1507328

Expander

VirtualPeripheral

0x00180000

1572864

Detector

VirtualPIR

0x00190000

1638400

Co Detector

VirtualSmokeDetector

0x001C0000

1835008

Full Upload

Cleans device memory and synchronizes the complete current access-right set.

Confirm completion, memory information and access with representative credentials.

Incremental Upload

Sends changes since the previous completed synchronization.

Confirm changed persons, credentials, schedules and access outcomes.

Selective Upload

Sends the selected person to the device.

Confirm that existing persons remain valid and the selected person receives the expected access.

Night upload

Runs the configured scheduled full or incremental upload.

Confirm configured schedule and the corresponding audit-log completion event.

Arm

Grants door-side arming rights

No

Yes/No

Disarm

Grants door-side disarming rights

No

Yes/No

Handicapped

Indicates whether the Handicapped flag is assigned to the person

No

Yes/No

Language

The language setting for this person

Default

IQMA network interruption

Bus Controller and IQMA-managed nodes can become Disconnected; the independent ISOM stream can remain operational.

Restore network access and verify reconnection, current states and audit events.

ISOM interruption

MB Secure Panel branch loses real-time intrusion/control communication; IQMA can remain operational.

Restore TCP 443 reachability and the remote-client session, then verify event subscriptions and current state.

Panel configuration change

OPIF entity mapping can become stale or incomplete.

Export and import a fresh OPIF file and restart panel communication.

Credential upload interruption

The upload fails and credentials may be only partially applied.

Restore communication, reconcile device state and repeat the required upload.

Session shutdown

Closing the WebSocket before logout can leave a panel session active and delay reconnection.

Send DELETE /ISOM/System/session and wait for the response before closing the WebSocket.

Bus Controller cannot connect to IQMA

TCP 23757, IQ Server service, IP/port, FreeDrivenId, matching DotNetConCtr.dll and cacert.pem.

Restore service/network reachability and use the DLL matching the installed IQ Multi Access version.

MB Secure Panel authentication fails

Active MANAGEMENT-SOFTWARE remote client, user name/password, TCP 443, firmware and OEM licence.

Correct the dedicated account and required panel settings; retry after the previous session is closed.

Upload fails for a panel or partition

Exact case-sensitive Original Device Name, existing partition in IQ Panel Control, aligned PIN-length settings.

Correct the source names/settings and repeat the required upload.

Imported entity has wrong or missing state

Current OPIF export, entity class, base offset and C4 Address.

Re-export OPIF, re-import the device tree and restart communication.

Card uploads as 0

Card number size.

Use a supported card number within the documented maximum 32-bit IQMA limit.

Immediate reconnect is blocked

Previous ISOM session logout sequence.

Ensure DELETE /ISOM/System/session completed before the WebSocket was closed; wait for the stale session to expire if necessary.

1

Create device tree with one licensed device node.

—

2

Check License bus controller.

When one licensed device node is present, one license is consumed for this driver.

1

Open the File Import panel on MB Secure Panel.

—

2

Find the OPIF file you want to import.

—

3

Import the device tree from the file.

The device tree is imported successfully. Only supported file formats are processed.

1

Enter the device DNS name in the IP Address field.

—

2

Start the endpoint.

The endpoint connects to the device successfully.

All device nodes under the endpoint are set to their real state.

1

Set the device time 60 minutes behind the C4 server time.

—

2

Start the endpoint

—

3

Wait until the driver is fully started.

—

4

Check the device time.

The device time is synchronized with the current C4 server time.

1

Set the value of property Time Synchronization Interval to 5 minutes.

—

2

Start the endpoint

—

3

Set the device time 60 minutes behind the C4 server time.

—

4

Wait 5 minutes

—

5

Check the device time.

The device time is synchronized with the current C4 server time.

1

Set the driver time zone to UTC+10 (Brisbane Time).

—

2

Start the endpoint.

—

3

Check that the device time corresponds to UTC+10 (Brisbane Time).

The panel time zone option is set to UTC+10 and time is synchronized if needed.

4

Make several operations that are audited to C4 audit log.

Events are stored in the audit log and displayed in the user’s time zone.

1

Stop the endpoint

—

2

Create an incomplete configuration tree with missing device.

—

3

Start the endpoint.

—

4

Generate some activity on the missing device.

Endpoint continues to work.

1

Set the property outside its allowed range or use an invalid format.

—

2

Start the endpoint.

When the driver implements regular-expression validation, the property with an invalid value is shown with a red frame.

1

Stop the endpoint

—

2

Create two addressable devices of the same type in the device configuration tree.

—

3

Set the same address value for both devices.

—

4

Start the endpoint.

Both items with the same address value have their status set to “ConfigurationFailure”.

The endpoint does not complete initialization and stops.

1

Download the plugin package (*.c4plugin).

—

2

Extract all files using 7-Zip or another suitable archive tool.

—

3

Under normal conditions, the driver package contains only required driver files, such as DLL, PDB and package files. Unnecessary files must not be distributed; any non-standard file requires a documented justification.

—

4

The developer must justify every non-standard file included in the driver package.

The plugin contains only the required files.

1

Start the endpoint

—

2

Wait for connection establishment.

—

3

Drop the connection on the switch or router, in such a way that the Windows system still detects the Ethernet connection.

—

4

Wait until the disconnection is signaled.

During a disconnection, all device nodes under the endpoint are set to "Disconnected" state.

5

After approximately 30 seconds, the driver attempts to reconnect. Wait for the attempt to finish.

—

6

Recover the connection.

—

7

Wait for connection reestablishment.

After the connection is recovered, all device nodes under the endpoint are set to their real state.

1

Start the endpoint.

—

2

Interrupt the connection between devices

—

3

Wait until the disconnection is signaled

During a disconnection, all device nodes under the endpoint are set to "Disconnected" state.

4

Recover the communication and wait until the driver states are recovered.

After the connection is recovered, all device nodes under the endpoint are set to their real state.

1

Execute the Door Unlock Permanently command on the door.

After the Door Unlock Permanently command is issued, the door status is set to Unlocked Permanently.

2

When a door contact is present, simulate physical door opening.

During real door opening, the door contact is activated and the door status is set to Opened.

3

Execute the Door Lock command on the door.

After the Door Lock command is issued while the door contact remains open, the door status remains Opened.

4

When a door contact is present, simulate physical door closing.

After the door is physically closed and the contact deactivates, or after the door-relay timer expires, the status returns to Locked (normal).

1

Activate the door contact while the door is locked.

The door status is set to Door Forcibly Opened.

1

Use the credential at the access point.

After successful credential authorization, the door status is set to Unlocked.

2

Activate the door contact.

Door status is set to Open when the door contact is activated.

3

Keep the contact active longer than the configured open-time limit.

After the configured open-time limit expires, the door status is set to Open Too Long.

1

Execute the Unlock command on the door.

After issuing the command "Unlock", the door status is set to Unlocked.

2

When a door contact is present, simulate physical door opening.

During real door opening, the door contact is activated and the door status is set to Opened.

3

When a door contact is present, simulate physical door closing.

After real door closing, the door contact is deactivated and the door status is set to Unlocked. If the door relay timer also expires, the door status returns to Locked (normal) state.

1

Execute the Door Manual Override command on the door.

While the override is active, the door status is DoorManualOverrideOn.

2

Attempt to open the door using a valid credential.

During door lockout, the door ignores attempts to open it with valid credentials.

3

Execute the Door Manual Override Off command on the door.

—

1

Trigger a tamper condition on the detector while its partition is disarmed.

—

2

Restore the tamper

The detector remains in Tamper status until the alarm is confirmed.

3

Confirm the alarm from C4 UI.

—

1

Stop the endpoint

—

2

Create a complete device tree and add one fictitious node of each applicable type.

—

3

Assign a fictitious address to each additional node.

—

4

Start the endpoint.

Driver starts.

5

Check the status of all nodes in device tree.

Nodes that are present on the device show their actual device status.

Nodes that are not present on the device show Unknown status (black).

1

Stop the endpoint

—

2

Configure an incorrect password, user name, encryption key or other connection-establishment property.

—

3

Start the endpoint.

The endpoint does not connect to the device.

All devices below the endpoint are set to Disconnected.

1

Arm the detector by arming its corresponding partition or area.

—

2

Trigger an alarm on the detector.

The detector status is set to Alarm.

The corresponding partition or area status is set to Alarm.

3

Restore the detector alarm condition.

—

4

Confirm the alarm from C4 UI

After alarm confirmation, the Alarm state is cleared.

1

Execute the Arm command on the group.

The group status is Armed after the Arm command is issued.

2

Execute the Disarm command on the group.

The group status is Idle after the Disarm command is issued.

1

Arm the group using the keypad or device panel.

—

2

Disarm the group using the keypad or device panel.

The group status is Idle when disarmed and Armed when armed.

1

Issue a duress alarm

The device and person associated with the duress alarm are logged.

1

Stop the endpoint

—

2

Wait for 1 minute

—

3

Perform an operation on the device that creates an audit-log entry.

—

4

Wait for 1 minute

—

5

Start the endpoint.

Events generated during the disconnection are stored in the C4 audit log with their original device timestamps, not the retrieval time.

1

Set the input Event Level property to Alarm.

—

2

Start the endpoint

—

3

Activate the input contact on the device.

When the contact is activated and Event Level is Alarm, its status is Alarm.

4

Deactivate the input contact on the device.

When the contact is deactivated and Event Level is Alarm, its status is Normal.

5

Set the input Event Level property to Information.

—

6

Start the endpoint.

—

7

Activate the input contact on the device.

When the contact is activated and Event Level is Information, its status is Open.

8

Deactivate the input contact on the device.

When the contact is deactivated and Event Level is Information, its status is Normal.

9

Set the input Event Level property to Silent.

—

10

Start the endpoint

—

11

Activate the input contact on the device.

When the contact is activated and Event Level is Silent, its status is Open.

12

Deactivate the input contact on the device.

When the contact is deactivated and Event Level is Silent, its status is Normal.

13

Set the input Event Level property to Warning.

—

14

Start the endpoint

—

15

Activate the input contact on the device.

When the contact is activated and Event Level is Warning, its status is Failure.

16

Deactivate the input contact on the device.

When the contact is deactivated and Event Level is Warning, its status is Normal.

1

Create new person.

—

2

Grant the person access to the access point

—

3

Assign a valid PIN to the person.

—

4

Send credentials to the device

—

5

Verify that the definitions were transferred correctly by reading device memory or validating operation at the device.

The person has the correct permissions on the device.

1

Create new person

—

2

Grant the person access to the access point

—

3

Assign a valid card to the person.

—

4

Send credentials to the device

—

5

Use the credential at the access point.

The person has the correct permissions on the device.

1

Create Persons A, B and C, each with a valid credential.

—

2

Add access to the device for person A.

—

3

Issue Full Upload.

—

4

Verify that Person A has access and Persons B and C do not.

—

5

Add access to the device for person B.

—

6

Execute Selective Upload for Person B.

—

7

Verify that Persons A and B have access and Person C does not.

—

8

Add access to the device for person C.

—

9

Execute Incremental Upload.

—

10

Verify that all persons A, B and C have access to the device.

All three persons have the correct permissions on the device.

1

Create Persons A and B, each with a valid credential.

—

2

Grant access to Persons A and B at the applicable door or area.

—

3

Issue Full Upload.

—

4

Assign Profile P to Person A.

—

5

Issue Incremental Upload.

Verify that upload finishes without errors.

Verify that Person A and Person B have access to the device.

Verify that Person A receives the functions defined by Profile P.

1

Create 2 Persons A and B with valid credential each.

—

2

Assign Profile P to Person A .

—

3

Grant access to Persons A and B at the applicable door or area.

—

4

Issue Full Upload.

Verify that Persons A and B have access and that Person A receives the functions defined by Profile P.

5

Unassign Profile P from Person A.

—

6

Issue Incremental Upload.

Verify that upload finishes without errors. Verify that Person A and Person B have access to the device.

Verify that Person A no longer receives the functions defined by Profile P.

1

Create Persons A and B, each with a valid credential.

—

2

Assign Profile P to Person A .

—

3

Grant access to Persons A and B at the applicable door or area.

—

4

Issue Full Upload.

Verify that Persons A and B have access and that Person A receives the functions defined by Profile P.

5

Change an option in Profile P.

—

6

Execute Incremental Upload.

Verify that upload finishes without errors. Verify that Person A and Person B have access to the device.

Verify that the changed profile option is applied to Person A.

1

Create Person A with valid credential.

—

2

Assign Profile P to Person A .

—

3

Grant time-restricted access at the applicable door or area and configure the restriction so that access is currently valid.

—

4

Issue Full Upload.

—

5

Change some option in profile P.

—

6

Issue Execute Incremental Upload.

Verify that upload finishes without errors. Verify that Person A has access to the device.

Verify that the changed Profile P option is applied to Person A.

1

Create new person

—

2

Grant the person access to the access point

—

3

Assign the person a valid credential

—

4

Create device profile with ‘Handicapped’ property

—

5

Configure the device profile to apply to the required entry point or device type.

—

6

Assign the device profile to the person.

—

7

Issue upload command

—

8

Verify that the definitions were transferred correctly and that the device responds to the Handicapped setting as configured.

Person has correctly defined permissions

The Handicapped flag is set for the person and the device responds accordingly.

1

Create new person

—

2

Grant the person access to the access point

—

3

Assign an invalid credential, for example a card number that exceeds the supported length.

—

4

Send credentials to the device

The upload fails and reports the invalid credential.

1

Create Persons A and B.

—

2

Grant both persons access to the access point

—

3

Assign all supported credential types to the persons.

—

4

Issue Full Upload command.

—

5

Issue upload command.

—

6

On the upload point in the device tree, open Memory Info and verify that all uploaded persons and credentials are shown with their device-memory positions.

Uploaded persons are correctly shown in Memory Info table.

Uploaded credentials of uploaded persons are shown in the Memory Info table.

The positions of uploaded persons are shown in the Memory Info table.

1

Create new person

—

2

Assign the person a valid credential

—

3

Grant the person access to the access point

—

4

Send credentials to the device

—

5

Use the credential at the access point.

The person is granted access at the specified access point.

The access point status is set to Unlocked.

1

Create new person

—

2

Assign the person a valid credential

—

3

Grant the person access to the access point

—

4

Deny the person access to another access point

—

5

Send credentials to the device

—

6

Use the credential to access another access point

The person is denied access at the specified access point.

1

Revoke all person access rights.

—

2

Issue Full Upload command

—

3

Present a card at the applicable reader.

The card is reported as an unknown credential.

1

Send credentials to the device

—

2

Interrupt the connection while credentials are being sent.

Communication is interrupted and the upload does not complete.

1

Create new person

—

2

Assign the person a valid credential

—

3

Grant the person access to the access point

—

4

Apply a time restriction to the access permission.

—

5

Send credentials to the device

—

6

Check whether the restriction is applied correctly

The assigned time restriction is correctly applied

When access is currently allowed, an Access Granted event is generated. When the time restriction denies access, an Access Denied event is generated.

1

Create new person

—

2

Assign the person a valid credential

—

3

Create a holiday set containing today’s date.

—

4

Send credentials to the device

—

5

Check whether the restriction is applied correctly

—

6

Modify the holiday set so that it no longer contains today’s date.

—

7

Send credentials to the device

—

8

Check whether the restriction is applied correctly

The assigned time restriction is correctly applied