
Approve a CCTV handover only after the intended operator has found a test incident, exported it and played the delivered copy on the receiving computer. A working live view proves one part of the system. It does not prove that the required channel was recorded, that the operator can locate the right interval, or that the recipient can use the file.
The practical acceptance question is: “Can this person deliver this incident to this recipient within the agreed time?” This guide turns that question into a repeatable test. It draws on Hector Weyl's supplied NVR manual, current ONVIF profile descriptions and an explicitly hypothetical transfer calculation. It reports no completed installation or hardware benchmark.
1. Write the acceptance task before ordering equipment
Describe a short incident the system must recover: a person crosses the loading entrance, moves to a collection point and leaves. Name the cameras, the detail needed at each position, the operator role and the receiving computer. Include audio only where it is authorized and actually required.
Agree how much footage before and after the action is needed. Set a delivery target for the whole workflow, including finding the interval, selecting channels, exporting, transferring and checking playback. “Export within ten minutes” is ambiguous if nobody has decided when the clock starts or whether copying the file is included.
Keep the acceptance record attached to the equipment schedule. Camera model and suffix, recorder model, firmware, recording settings, client version and intended export format belong there. For Hector Weyl procurement, MOQ: 100 units applies; confirm the actual order configuration and support scope before committing. A demonstration using another model does not close a requirement on the quoted system.

2. Verify the recording path separately from live view
The NVR manual separates the recording schedule from recording mode. In §5.8.1.1, PDF pages 96–100, a schedule defines channels, periods and recording types. In §5.8.1.3, PDF pages 101–102, Auto follows the schedule, Manual makes general recordings, and Off disables recording. Check both layers on the equipment being delivered.
A particularly misleading demonstration is a manually started recording played back during installation while the required automatic schedule remains unproven. Ask the installer to identify which mode created the test clip. Verify an interval produced under the intended operating configuration, including a relevant closing-time or holiday period where that requirement applies.
| Layer | Normal observation | If missing, check next |
|---|---|---|
| Channel and stream | The stored clip contains the intended view and agreed detail. | Camera-to-channel mapping and actual recording profile; avoid judging only the live-view stream. |
| Recording period | A recording exists in the required time window. | Schedule, recording type, day and any holiday override. |
| Recording mode | The clip was created under the intended automatic or agreed manual mode. | Mode selection and whether an installer temporarily forced recording. |
| Storage path | The target interval can be read back from the intended storage. | Storage status, recorded-file information and relevant fault logs. |
For event recording, test the actual event, recording linkage and surrounding footage. An alert in a mobile application does not establish that a corresponding clip exists on the recorder. A pre-record setting also needs a playback check; the configured number is not a substitute for observing the required approach in the stored video.
3. Establish the time reference before searching
Record the test date, time zone and a reference time. Compare that reference with the camera overlay, recorder search interface and delivered playback. Different displays may express time differently, so document the relationship rather than assuming every visible clock uses the same zone.
The manual's §5.15.1.2, PDF pages 223–224, describes date, time zone, daylight-saving and NTP controls. It also warns that changing system time carelessly can interfere with finding recorded video. Capture the observed offset first. Have the responsible administrator plan any correction and repeat the test afterward; do not casually change clocks while trying to recover an important existing incident.
During commissioning, agree a common time source and permitted error for the project. NTP being enabled is a configuration observation; successful synchronization must still be checked. Test the relevant network path and compare actual displayed times. No universal clock tolerance is proposed here: a single entrance review and reconstruction across several sites can require different precision.
4. Create one recognizable, repeatable test incident
Use a controlled walk-through by an authorized participant. Record the route, reference start time and an easily recognized action at each camera. Include the approach and departure, not only the moment at the center of the frame. Then wait until the incident is available in recorded playback before beginning the retrieval test.
Choose conditions that match the requirement. If the critical task occurs after closing, a daytime clip cannot close the night requirement. Use our night-lighting acceptance guide for the separate question of useful moving detail. Here, the focus is whether that recorded interval survives the whole delivery workflow.
Assign each clip a simple reference such as TEST-01, channel and interval. Keep a short observation log. This makes a retest comparable after a configuration change and prevents an attractive but unrelated demonstration clip from replacing the agreed acceptance scene.
5. Find the clip using the intended operator account
The manual's §5.8.2.1–2, PDF pages 103–106, describes date, channel, recording-type and playback selection. Use those distinctions when a search appears empty. The wrong date, channel or filter can hide a recording that exists. Conversely, a populated timeline cannot prove that the required interval contains the expected action.
Run this stage with the actual operator role. An administrator's successful demonstration does not establish the operator's search or export permissions. If the project includes Hector Weyl Security System (HSS) or Hector Weyl Mobile Security System (HMSS), record the selected application and version and test its own workflow; do not assume desktop and mobile functions are identical.
| Symptom | First distinction | Next action |
|---|---|---|
| No matching results | No recording, or a search mismatch? | Check date, zone, channel and type filter against the test log, then inspect recording status. |
| Administrator succeeds; operator fails | Access or workflow difference? | Compare assigned rights and permitted channels without sharing administrator credentials. |
| Clip opens but lacks context | Short export selection, or missing original footage? | Review a wider stored interval before changing the exported selection. |
| Analytics search misses the action | Missing metadata, or missing video? | Try ordinary time-and-channel playback; investigate the analytics path separately. |
ONVIF makes another useful distinction: Profile T concerns advanced streaming, while Profile G covers edge storage and retrieval. These descriptions do not establish a particular Hector Weyl model's conformity or an entire mixed-brand workflow. Obtain exact device/client and firmware evidence, then test the required operation.
6. Finish the export test on the recipient's computer
In §5.8.2.6–7, PDF pages 112–113, the NVR manual describes choosing clip start and stop points and backing selected recordings up to USB storage. Treat those as documented concepts for the manual's supported equipment. Confirm the actual device's export options, file format and current instructions before writing a model-specific procedure.
Check the completed file independently of the recorder. Open the delivered copy on the intended receiving computer with an approved, supported player. Inspect the beginning, key action and end, seek through the interval, and check required audio. For multiple cameras, confirm every requested view is present and that their timing can be understood.
Player choice matters. Axis's March 2026 Camera Station 5 troubleshooting guide distinguishes exported file formats and appropriate players. That is an Axis-specific example of the dependency, not a recommendation to use Axis software with Hector Weyl exports. Validate the recipient's actual format, codec and playback software.

Keep the original export alongside any separately converted viewing copy. Record filenames, channel references, selected interval, time-zone notes and required playback instructions. Where useful, compare a SHA-256 checksum before and after transfer to detect a changed copy. A matching checksum establishes byte equality between those copies; it does not prove camera origin, correct timestamps or legal admissibility.
7. Budget for transfer time, not only clip duration
A ten-minute incident can take longer than ten minutes to deliver. For a transparent planning example, assume four camera streams, each averaging 4 Mb/s, exported for 600 seconds without re-encoding. This is a hypothetical payload estimate; it excludes audio, metadata, packaging and protocol overhead.
The video payload is 4 × 4 × 600 ÷ 8 = 1,200 MB, or 1.2 GB, using decimal units. At a sustained payload transfer rate of 40 Mb/s, copying those bytes takes 240 seconds, or four minutes. At 8 Mb/s, it takes 1,200 seconds, or twenty minutes. These rates are assumptions about the actual transfer, not advertised network-port speeds.
| Hypothetical condition | Calculation | Result |
|---|---|---|
| Four streams, 4 Mb/s each, ten minutes | 4 × 4 × 600 ÷ 8 | 1,200 MB video payload |
| 40 Mb/s sustained payload transfer | 1,200 × 8 ÷ 40 | 240 seconds / 4 minutes |
| 8 Mb/s sustained payload transfer | 1,200 × 8 ÷ 8 | 1,200 seconds / 20 minutes |

Measure the complete path during acceptance. A USB export followed by a separate upload has more than one transfer stage; estimate and time each one. If the deadline fails, consider a tested faster route or an agreed smaller initial selection while preserving the full required material. Retention capacity is a different calculation, covered in our 30-day CCTV storage guide.
8. Sign off observations and keep exceptions open
Use a short acceptance sheet that another person can repeat. A checkbox saying “NVR working” conceals too many dependencies. Each row should identify the normal result, retained evidence and the owner of any unresolved issue. A failed requirement stays open until its retest succeeds or the customer explicitly agrees a revised scope.
| Acceptance item | Evidence to retain | Pass condition to agree |
|---|---|---|
| Required interval exists | Test reference, channel, mode and playback observation. | Approach, action and departure are present under the intended schedule. |
| Timing is understood | Reference time, zone and observed display offsets. | Within the project's agreed tolerance, with time interpretation documented. |
| Operator can retrieve | Role, client version, search steps and elapsed time. | The designated role finds the correct clip without administrator assistance. |
| Recipient can play | Delivered filenames, player/version and playback result. | Required views, interval, detail and authorized audio are usable. |
| Delivery target is met | Start/finish times and transfer route. | The complete workflow meets the agreed deadline. |

Keep configuration and version references with the result. If the recording profile, client, permissions or export route changes materially, repeat the affected checks. The retained sample proves what was observed in that test configuration; continued recording and storage health still require ongoing operational checks.
9. Frequently asked questions
Does a working live view prove recording works?
No. Recover a known incident from storage under the intended recording mode and schedule. Live viewing and recorded-file retrieval exercise different parts of the system.
Is a mobile alert enough to accept event recording?
No. Verify the recording linkage and stored interval independently, including the approach and departure required by the task. A notification is evidence of an alert, not of a complete exported clip.
Why can the installer export when the operator cannot?
The account, permitted channels, client or workflow may differ. Repeat the test using the intended operator role and have the administrator correct the specific access issue.
Does ONVIF support guarantee all playback and analytics?
No blanket conclusion follows. Check the relevant profiles, exact devices, client and firmware. Streaming, storage retrieval and analytics requirements need their own evidence and acceptance tests.
Can every exported file play in a standard video player?
Do not assume it. Confirm the selected container, codec and supported player, then open the delivered file on the recipient's actual computer. Keep any required player instructions with it.
Should I correct a recorder's clock during an incident search?
First preserve the observed offset and identify the relevant interval. The manual warns against arbitrary system-time changes. Arrange correction with the administrator and verify future recording separately.
Does a four-minute transfer mean four-minute delivery?
No. Finding the recording, export preparation, additional copying stages and recipient verification add time. The four-minute figure here covers only an assumed transfer of a specified video payload.
10. Sources and project preparation
Hector Weyl supplied Network Video Recorder User's Manual, V1.0.0, revision table July 2024: §5.8.1.1, PDF96–100; §5.8.1.3, PDF101–102; §5.8.2.1–2, PDF103–106; §5.8.2.6–7, PDF112–113; §5.15.1.2, PDF223–224. PDF page positions are used because printed numbering jumps. Its stated scope is NVR5X/NVR8XX; functions and interfaces remain model and firmware dependent.
Public references checked November 18, 2026: ONVIF's Profile T and Profile G pages linked above establish their different purposes; Axis's March 2026 Camera Station 5 troubleshooting guide supplies the separate format/player example. None establishes untested Hector Weyl compatibility. The checklist and transfer example are this article's proposed method and calculation.
Preparing a Hector Weyl project? Bring the camera and recorder list, recording requirement, intended operator/client, receiving environment and delivery deadline. Agree the acceptance task alongside the equipment and MOQ100units procurement requirements, so the final demonstration closes the workflow the customer will actually use.

Share:
IR vs Full-Color CCTV: Test Motion Before Choosing Light