Equipment and spare partsBrowse manufacturers Search by manufacturerVideo management and security integration
Specify an Arteco installation or expand an existing system with video management, recording equipment, licences and modules. Send a camera list, equipment specification or description of the project.
Start with the intended result: managing video, recording, analytics, number plate reading or linking security events. The following sections identify the project information needed for a useful enquiry.
OMNIA brings video and security events into a shared operator interface. For an existing installation, identify the edition and software version before defining an expansion. Separate additional camera connections from changes to the functions operators actually need.
uSee provides browser-based video management. The manufacturer describes on-premise and hybrid deployments with subscription or perpetual licensing. A project enquiry should identify how the system will be used and where its recording infrastructure will sit.
ARTECO 7000 is a 19-inch rack surveillance server. The published design accommodates up to 8 HDDs, with camera licences selected separately. Define recording requirements before requesting a configured server or a replacement component.
LPR Server 2.0 performs number plate reading on a Windows server. Start with the entrance layout and expected operating conditions. Camera placement, lighting and the intended response to a recognised vehicle belong in the same project brief.
VCA analyses objects and movement in video streams. The manufacturer describes a separate application on a Windows workstation. Define the events that matter to operators before selecting analytics capacity or the supporting computer.
Arteco Security Connector extends OMNIA with external security-system integration, including Modbus devices. Describe the connected panel, its software and the events to exchange. A protocol name alone does not define a complete integration.
For a working installation, describe the change rather than treating every item as a new system. List added cameras, extra operator stations and any new site. Keep existing entitlement information separate from the requested additions so the quotation can distinguish expansion from replacement.
A hardware replacement starts with the actual component identifier. A photograph of the server front panel can help establish the family, but a power supply, drive or board requires its own label. Include connector photographs and describe how the installed unit is used.
Archive sizing depends on stream parameters and the recording schedule. Provide the current disk configuration and retention requirements for each camera group. A useful brief distinguishes continuous recording from event recording and identifies any plans to increase the camera count.
Assess the exact camera model and firmware against the requested workflow. Live viewing, recording, audio, movement control and event handling are different requirements. Record the functions you actually use so an enquiry does not reduce compatibility to the presence of a video picture.
Specify operator work by task: routine monitoring, archive review and incident handling. Include the number of displays and the views opened at the same time. A workstation request should also describe concurrent use of other applications and any restrictions on the operating environment.
Use a site table for a distributed project. Record cameras, servers, archive location and available connectivity for every location. Then define what the central control room must receive.
This makes local requirements visible without assuming that all locations have identical network capacity or operating procedures.
Document the installed software and hardware before requesting an upgrade. Separate software changes, server replacement and added analytics into their own lines.
Ask the system operator to identify essential daily functions and the information that must remain accessible during the planned transition.
Separate hardware, licences, optional modules and services in the purchasing specification. Give each line a description, quantity and intended use. Existing documents can help identify a product, but remove unrelated information before attaching them.
Note whether each line is a replacement, an expansion or part of a new installation.
Compare delivered items with the agreed specification, including model identifiers, quantities and supporting documents. For software, review the licence description and intended deployment with the person responsible for the installation.
Keep hardware receipt and software entitlement checks as distinct acceptance steps.
Begin with the desired result and a clear equipment photograph. For software, attach a version-information image with activation keys and unrelated information removed.
Explain whether you need a component replacement, a capacity increase or a new installation, and identify the technical contact who can clarify the configuration.
Provide site and camera counts, stream settings, archive retention and operator tasks. Add a network diagram or equipment table. Separate installed equipment from requested additions and identify planned expansion. For analytics, describe the event and attach a representative image of the monitored zone. Include the delivery destination and a technical contact.
List the designation, quantity and purpose. Hardware requests need component identification and connection photographs; software requests need the installed version and project configuration. If the ordering code is unknown, describe what works now and the result required after the change. Separate a failed component from a planned capacity upgrade.
Availability, price, lead time, configuration, compatibility and permission to use the software in the destination country are confirmed for each enquiry before order agreement. We do not claim authorised dealer status. Send the technical list and delivery location for assessment.
English-speaking contact