Site survey, purpose and coverage design
Required scenes, entries, exits, assets, public areas, blind spots, camera purpose, site constraints and expansion priorities.
CCTV & VIDEO SURVEILLANCE
Capture the right views, retain usable footage and retrieve it when it matters.
MiCiS designs, installs and supports commercial CCTV across your sites. We plan network connectivity and supported access-control integrations alongside camera coverage. One team coordinates site survey, cameras and lenses, cabling, network and PoE, recording and storage, remote access, maintenance and integrations so coverage, retention and responsibilities remain clear.
Australian-based coordination, site-specific coverage planning and one
support path across cameras, networks, recording, storage and access.
Coverage
Views mapped
Camera purpose, field of view, lighting and blind spots documented by area.
Recording
Retention defined
Recording mode, storage, time and export expectations documented.
Access
Users controlled
Onsite and remote access roles, devices and escalation paths kept visible.
Lifecycle
Maintenance scoped
Camera, recorder, storage, network and power checks aligned to scope.
WHAT WE MANAGE
The cameras, network, recording, storage and access layers behind usable video.
A CCTV system is more than a camera count. The purpose of each view, lighting and scene conditions, lens selection, mounting, cabling, PoE, network capacity, recording mode, storage, time synchronisation, user access, export and maintenance all affect whether the system produces useful footage. MiCiS brings those layers into one documented service path.
Coverage and identification outcomes depend on the scene
Results depend on the purpose of the view, object distance and angle,
lighting, motion, obstructions, mounting height, lens, resolution,
compression, weather and maintenance. Camera placement is therefore
confirmed against the required scene rather than a generic camera count.
CCTV and video surveillance coverage
Cameras, lenses, lighting and environment
Camera form factor, field of view, focal length, day/night behaviour, exposure, weather, impact and mounting conditions.
Mounting, cabling, PoE, network and power
Mounting locations, pathways, structured cabling, switching, PoE budgets, VLANs, bandwidth, uplinks and UPS dependencies.
Recording platform, storage, retention and time
NVR or VMS configuration, recording schedules, event recording, storage model, retention target, time sync and export.
User access, remote viewing and export
User roles, supported clients, secure remote access, mobile viewing, evidence export, audit context and authorised handover.
Maintenance, health checks and lifecycle
Agreed camera and recorder checks, storage condition, firmware, cleaning, focus, time, access, fault follow-up and lifecycle planning.
VIDEO EVIDENCE BUILT IN
Cameras only help when the right scene is captured, recorded and retrievable.
A live picture is not the same as a dependable video record. Field of view, lighting, image settings, time synchronisation, network and power, recording health, storage, retention, user access and export all affect whether footage can be found and understood when it is needed. MiCiS designs and tests those controls as one evidence path.
- Purpose and scene requirements defined Each view has an agreed purpose, subject area, lighting assumption, obstruction check and expected level of visible detail.
- Recording and retention tested Recording mode, time, playback, storage state, retention assumptions and representative export are validated to the agreed scope.
- Access and export responsibilities controlled Authorised users, remote access, password and authentication ownership, export handling, incident contacts and support boundaries are documented.
Video evidence control path
From scene conditions to usable, retrievable footage
Scene, lighting and field of view
Purpose, distance, angle, obstructions, day/night conditions,
moving subjects and required visible detail
Verified
Camera, lens and image settings
Lens and focus, exposure, shutter, frame rate, resolution,
compression, infrared and image orientation
Tuned
Network, PoE, power and time
Cabling, PoE budgets, switching, VLANs, uplinks, bandwidth,
UPS dependencies and time synchronisation
Prepared
Recorder, storage and retention
Camera registration, recording schedule, event triggers,
storage state, retention assumptions, playback and export
Checked
Access, export and maintenance
User roles, remote clients, export process, representative checks,
cleaning, focus, firmware and lifecycle
Documented
HOW THE SERVICE IS DELIVERED
A controlled path from site survey and camera design to commissioned recording and documented handover.
CCTV delivery crosses site access, mounting, cabling, power, PoE, network capacity, camera placement, recording and storage design, user access and operational policy. MiCiS defines the required views, coordinates the delivery dependencies, installs and commissions the system, validates representative recording and export, and retains the records needed for maintenance and controlled change.
CCTV delivery path
From required views to an operational, documented video system
-
Survey and define outcomes
Review site risks, required scenes, existing equipment, lighting, access, mounting, pathways, power, network, users, retention and integration requirements.
Output Coverage + dependency baseline -
Design and prepare
Select cameras and lenses, confirm views and mounting, size network, PoE, recorder and storage, define recording, access and cutover, and coordinate site dependencies.
Output Approved camera + recording design -
Install, configure and commission
Install agreed equipment, configure cameras, network and recording, tune representative scenes, test playback, time, retention assumptions, remote access and export.
Output Commissioned system + handover -
Maintain, review and improve
Retain camera and system records, perform agreed checks and maintenance, coordinate faults, review storage and access, and plan expansion and lifecycle actions.
Output Support context + lifecycle plan
END-TO-END VIDEO EVIDENCE PATH
A live camera does not guarantee usable footage.
A usable video record depends on the scene and lighting, camera and lens, mounting and cabling, PoE and power, switching and bandwidth, time synchronisation, recording software, storage, retention, user access and export. MiCiS maps that chain so faults and changes can be tested beyond a green camera-status icon.
- Trace the image from scene to exported clip Scene conditions, camera image, network transport, recording, storage, playback, user access and export are considered as one path.
- Separate optical, power, network and recording faults Lighting, focus, obstruction, cabling, PoE, switching, bandwidth, time, recorder, storage and client behaviour are tested at the appropriate layer.
- Keep retention, access and integrations visible Remote viewing, export, mobile clients, analytics, access control, alarms and other third-party dependencies are documented before change.
VIDEO EVIDENCE PATH
From scene conditions to reviewed and exported video
CORE VIDEO OUTCOME
Usable video evidence
Required scene, dependable recording, correct time, controlled access
and retrievable export.
Documented
Scene, lighting and camera view
Purpose, distance, angle, obstructions, day/night conditions,
motion and required visible detail
Observed
Mounting, cabling, PoE and power
Mounting surface, pathways, copper or fibre, PoE budget,
local power, UPS and physical environment
Powered
Switching, VLANs, bandwidth and time
Camera network, PoE switching, uplinks, segmentation, bandwidth,
remote sites, addressing and time synchronisation
Connected
Recorder/VMS, storage and retention
Camera registration, streams, schedules, events, storage state,
retention assumptions, playback and export
Recorded
Client access, export, analytics and integrations
User roles, desktop and mobile clients, remote access, export,
alerts, analytics and connected site systems
Available
MiCiS can trace or coordinate a fault or change across scene, camera, cabling, power, network, recording, storage and client-access layers while retaining one documented escalation context. Product vendors, platform providers, property stakeholders and other third parties retain their own responsibilities.
FREQUENTLY ASKED QUESTIONS
Questions to settle before cameras are installed or an existing system is expanded.
A CCTV proposal should make camera purpose, site coverage, lighting, recording and retention, network and power dependencies, remote access, maintenance, integrations and operating responsibilities clear before work begins. These questions most often affect design, cost, usefulness and ongoing support.
Purpose, access, retention and responsibilities documented
Required scenes, camera purpose, recording mode, retention assumptions,
authorised users, remote access, export handling, health checks,
maintenance, live-monitoring expectations and third-party responsibilities
are confirmed for the engagement.
CCTV & Video Surveillance FAQ
Answers before camera, recording or access decisions
How are camera positions and coverage determined?
The process begins with the purpose of each view: general overview, entry or exit activity, asset protection, movement through a space or another defined operational need. MiCiS then considers distance, angle, mounting height, lighting, motion, obstructions, day and night conditions, environmental exposure, network and power pathways and the level of visible detail required. The resulting plan is site-specific rather than based only on a camera count.
How much storage and recording retention do we need?
Storage depends on camera count, resolution, frame rate, compression, recording schedule, motion or event activity, scene complexity, retention target and any redundancy requirement. The design should state the assumptions used rather than presenting retention as an unconditional guarantee. MiCiS sizes and documents the proposed storage model and validates the configured recording and playback path during commissioning.
Can existing cameras, cabling, switches or recorders be reused?
Sometimes. Reuse depends on physical condition, image quality, credentials, supported protocols, firmware, power requirements, cabling performance, PoE capacity, network design, recorder or VMS compatibility, channel and feature licences, storage condition and vendor support. MiCiS can assess the existing environment and identify what can remain, what introduces risk and what should be replaced or separated from the new design.
What image quality is required for overview, recognition or identification?
The required image depends on what the organisation needs to see and the conditions in which it must be seen. Distance, field of view, lens, resolution, lighting, motion, shutter, exposure, compression and viewing angle all affect visible detail. A high-resolution camera alone does not guarantee a useful result. MiCiS defines the purpose of the view and tests representative scenes against the agreed expectation.
How is remote viewing and user access managed?
Access should be limited to authorised users and supported devices, with named accounts, appropriate roles, strong authentication where the platform supports it, controlled administrator access and a documented offboarding process. Remote access may use a vendor service, secure application, VPN or another agreed path. The design should also identify who owns account recovery, mobile devices, exports and access review.
What happens if power, network, a camera or the recorder fails?
Different failures require different controls. Design options may include UPS-backed switching and recording, redundant storage or recording components, local camera storage, network-path resilience, health checks, alerts and documented restoration procedures. These controls must be explicitly scoped and tested; a camera appearing online does not prove that video is being retained correctly or that every failure mode is covered.
Can the system include audio, analytics, number-plate recognition or integrations?
Availability depends on the selected cameras, recorder or VMS, feature licences, processing location, scene conditions and the connected systems. Before audio, biometric or facial functions, number-plate recognition or automated alerts are enabled, the organisation should define the operational purpose and obtain appropriate privacy, workplace, legal and policy advice. MiCiS can configure the agreed technical scope but does not determine the organisation’s lawful basis or operating policy.
Is live monitoring included, and who supports a fault across the full system?
Live monitoring, after-hours response, alarm verification and incident response are not assumed unless they are specifically contracted and documented. Where the relevant components are within the MiCiS scope, MiCiS can retain one technical context and trace or coordinate faults across camera, cabling, power, network, recorder, storage, remote client and integration layers. Other providers may retain their own monitoring, property, platform or response responsibilities.
Ready for a CCTV system designed around the scenes, retention and access your organisation actually needs?
Start with a practical review of your sites, required views, lighting, existing cameras and cabling, network and power, recording platform, retention, remote access, maintenance and integration requirements. MiCiS will identify coverage gaps, infrastructure and lifecycle dependencies, and the right next step for a documented commercial video system.