Fortinet FortiCamera CD55 Premium 5MP Indoor/Outdoor IP Video Security Camera

The FortiCamera CD55 is a professional fixed-dome surveillance camera engineered for organizations that need high-resolution day/night monitoring, flexible lens adjustment, durable installation and integration with Fortinet video security infrastructure. For businesses, institutions and public-sector projects in Uganda, it provides a practical camera platform for monitoring entrances, corridors, compounds, reception areas, warehouses, campuses, parking zones and other operationally important spaces. The 5MP low-light CMOS sensor, motorized autofocus lens, 4x optical zoom, HDR, infrared illumination and H.265 compression combine to give security teams a versatile endpoint for modern IP surveillance deployments.

Unlike a basic fixed-lens camera, the CD55 uses a 2.7–13 mm motorized lens that lets installers tune the field of view to the actual scene. That flexibility matters when a procurement team knows the camera location but cannot determine the final viewing angle until installation. The camera can be configured for wider scene coverage or a narrower view of a gate, doorway, transaction point or protected asset. Its vandal-resistant dome format and environmental protection make it appropriate for demanding indoor and outdoor positions when installed according to manufacturer guidance.

Request FortiCamera CD55 Quote in Uganda

Procurement Fact Rail

For procurement, the most important distinction is that the CD55 is not simply a generic 5MP dome. Its motorized varifocal optics make it suitable for projects where camera positioning, target distance and required scene width vary across locations. Buyers should therefore evaluate the model as part of a complete surveillance design that includes PoE capacity, network switching, recording resources, retention requirements, mounting hardware and management architecture. Stock, lead time and warranty handling should be confirmed on the project quotation because these can vary by supply batch and commercial arrangement.

Operational Architecture and Camera Overview

At the imaging layer, the CD55 captures video through a 5-megapixel, 1/2.8-inch low-light CMOS sensor. The lens provides an aperture of F1.6 at the wide setting and F3.3 at telephoto, with a motorized 2.7–13 mm focal range. This combination allows the installer to adapt the camera to different monitoring objectives without physically replacing a lens. The published viewing range extends from approximately 29 to 99 degrees horizontally, 22 to 71 degrees vertically and 35 to 132 degrees diagonally, giving designers substantial flexibility when balancing scene coverage against target detail.

The camera supports 5MP video at up to 30 frames per second as well as lower resolution profiles including 4MP, 3MP, 1080p, 720p, 1024×768, 640×480 and 320×240. Multiple resolution choices are valuable in a real deployment because not every stream needs maximum resolution. A security architect may choose a high-resolution recording stream while using a lower-bandwidth secondary stream for remote viewing. H.264 and H.265 video compression help reduce bandwidth and storage demand compared with uncompressed video, but retention calculations should still be based on actual frame rate, resolution, scene activity, compression settings and recording policy.

Low-light performance is another important architectural consideration. The CD55 is specified to 0.03 lux in colour and 0.01 lux in black-and-white at F1.6, while HDR above 80 dB helps manage scenes containing bright and dark regions. Dimmable infrared illumination rated beyond 20 metres supports night monitoring where ambient lighting is limited. These capabilities can reduce dependence on continuous external lighting, although site lighting, reflective surfaces, mounting height and target distance remain important to final image quality.

For connectivity, the camera provides 10/100 Mbps Ethernet and supports RTSP. PoE allows data and power to share the Ethernet cable, simplifying installations where electrical outlets are unavailable at each camera point. The camera also includes a built-in microphone for one-way audio. The broader FortiCamera platform supports use with FortiRecorder, and supported camera variants can also participate in Fortinet’s camera management ecosystem. Before a large rollout, firmware compatibility between cameras, recorder software and management components should be validated as part of staging.

Enterprise Business Outcomes

Key Hardware and Software Highlights

The CD55 combines a 5MP imaging sensor with a motorized autofocus lens, making it suitable for projects that need adjustable coverage after mounting. The 4x optical zoom is especially useful where a fixed 2.8 mm lens would either capture too much background or fail to provide sufficient target detail. The DC iris adapts to changing illumination, while HDR helps preserve useful information in scenes with strong contrast such as doors opening to bright outdoor areas.

Infrared illumination extends beyond 20 metres under suitable conditions and can be dimmed. This is operationally useful because excessive IR intensity can wash out close subjects or reflect from nearby surfaces. 3D noise reduction assists with image quality in difficult lighting and can also reduce unnecessary compression load caused by image noise. H.265 support is valuable in storage-sensitive projects, though actual storage savings depend on the selected recording profile and scene complexity.

The camera uses RJ45 10/100 Ethernet and IEEE 802.3af Class 3 PoE. This allows the surveillance network to centralize electrical backup at PoE switches and UPS systems instead of providing a separate local power supply for each endpoint. The built-in microphone supports one-way audio capture where policy and local requirements permit its use. ONVIF profiles S, G and T are supported on the cloud-enabled CD55-C specification, strengthening standards-based integration options. Buyers should confirm the exact ordered variant and required firmware before relying on a particular integration feature.

Technical Specifications Ledger

Specification revisions can occur between hardware generations and regional stock. For formal tender responses or regulated deployments, the exact manufacturer part number and current datasheet should be matched to the quotation before purchase.

Configuration and Sizing Worksheet

1. Estimate Camera Workload and Scale

Begin with a site plan and count each monitoring objective rather than simply estimating camera quantity by floor area. Identify entrances, exits, gates, cash-handling points, server rooms, loading zones, corridors, parking areas and perimeter segments. For every location, document the required target detail, expected lighting, viewing distance and retention requirement. This prevents overbuying cameras while underestimating storage or network capacity.

2. Check Environment and Mounting

Confirm whether each unit is indoor, sheltered outdoor or fully exposed. Check ceiling or wall construction, conduit routing, mounting height and service access. Outdoor cameras should be positioned to reduce direct sunlight where possible and should use appropriate weatherproof cable entry and surge protection practices. Allow enough working clearance for installation and future maintenance.

3. Calculate PoE and Cabling

Use the maximum camera power requirement when calculating switch budgets. Multiply the camera count by the maximum draw, then add engineering margin and account for other PoE endpoints on the same switch. Verify cable distance, cable category and termination quality. For sites with unstable utility power, place surveillance switches and recording systems behind correctly sized UPS infrastructure.

4. Plan Recording, Storage and Management

Storage depends on resolution, frame rate, codec, recording schedule, motion policy, scene activity and retention period. A 30-day continuous recording requirement can produce a very different storage bill from event-based recording. Specify whether FortiRecorder or FortiCamera Cloud is intended and confirm any subscriptions, recorder capacity or management entitlements needed for the selected architecture.

5. Prepare the Quote Request

Provide camera quantity, exact site locations, desired retention days, expected recording mode, recorder requirements, PoE switch availability, mounting accessories, UPS requirements and installation scope. A detailed request allows the supplier to validate the bill of materials rather than quoting cameras in isolation.

Deployment Scenarios in Uganda

Large Enterprise and Multi-Site Networks

Enterprises with headquarters, branches, warehouses and distribution locations can standardize on the CD55 for positions requiring adjustable viewing angles. A multi-site design should define consistent IP addressing, VLAN policy, camera naming, time synchronization, administrator access, firmware baselines and recording retention. Centralized standards make it easier to expand the system and troubleshoot incidents across sites.

Financial and Banking Institutions

Banks, microfinance organizations and other financial environments often require clear coverage of controlled entrances, teller areas, corridors and restricted rooms. The motorized lens can be tuned to specific zones, while HDR is useful around entrances where strong backlighting can challenge conventional cameras. Recording retention, user permissions and audit requirements should be agreed before equipment sizing.

Educational and Campus Networks

Schools, universities and training campuses may deploy cameras across gates, administration buildings, libraries, laboratories, parking areas and circulation zones. Network segmentation and PoE switching can simplify campus expansion, but designers should ensure that uplinks and recording resources can absorb aggregate video traffic during peak conditions.

Government and Public-Sector Procurement

Government projects typically benefit from documented part numbers, approved bills of materials, warranty procedures, delivery schedules and configuration records. The CD55 can fit surveillance designs requiring rugged fixed-dome endpoints, but tender specifications should distinguish required image performance, environmental rating, lens range, recorder integration and storage retention rather than specifying camera count alone.

Technical Deep Dive: Imaging and Hardware Engine

The central strength of the CD55 is the relationship between its 5MP sensor and motorized varifocal optics. Resolution alone does not guarantee useful evidence. The number of pixels placed across a target depends heavily on field of view and distance. By allowing the installer to narrow the field of view optically, the CD55 can concentrate available sensor resolution on a smaller area without relying on post-capture digital enlargement. Conversely, the lens can be set wider where situational awareness is more important than fine target detail.

The DC iris and low-light sensor help the camera adapt to changing illumination. HDR above 80 dB is valuable where bright windows, doors, headlights or exterior sunlight coexist with darker interior regions. Infrared illumination provides another layer for nighttime operation. Because IR performance is affected by scene reflectivity, fog, rain, nearby walls and mounting geometry, a commissioning engineer should test the actual nighttime image rather than relying only on the nominal distance specification.

Technical Deep Dive: Software Ecosystem and Operational Control

The camera supports modern H.264 and H.265 video compression and RTSP streaming. In a Fortinet deployment, FortiRecorder provides the recording and video-management layer, while current FortiCamera documentation also identifies cloud-capable variants for FortiCamera Cloud. Operational control should include firmware governance, administrator credential management, restricted management access, network segmentation and documented change procedures. Camera firmware and recorder compatibility should be checked before upgrades, particularly in larger systems where an unplanned compatibility issue can affect many endpoints.

ONVIF support can help with interoperability, but procurement teams should treat standards support as a starting point rather than a guarantee that every advanced function will work identically on every third-party platform. Basic discovery, streaming and recording may work while specialized functions can vary. A proof-of-concept is recommended where third-party VMS integration is a mandatory project requirement.

Technical Deep Dive: Resilience and Recovery

Camera resilience is not only an endpoint characteristic. A robust surveillance system distributes resilience across PoE switching, UPS power, network paths, recording storage and configuration backup. The CD55’s PoE design makes centralized backup power practical: cameras can remain powered when their PoE switch and upstream recording infrastructure are protected by UPS systems. For critical sites, designers should also consider switch redundancy, recorder capacity, spare cameras, documented replacement procedures and configuration templates.

Local storage support on current cloud models can provide an additional operational tool, but the exact role of edge storage should be defined within the recording architecture. Disaster recovery planning should specify what happens during WAN loss, recorder failure, power interruption and device replacement. The objective is not merely to keep a camera powered; it is to preserve useful evidence and restore normal monitoring predictably after a fault.

Pre-Purchase Buyer Gap Checklist

Licensing and subscriptions: confirm whether the project uses FortiRecorder, FortiCamera Cloud or another supported management method. Cloud services and recording architectures can have different commercial requirements, so camera hardware price should not be treated as the complete system cost.

Hardware generation: confirm the exact FortiCam CD55 or CD55-C part number offered. Manufacturer documentation covers multiple generations and variants, and details such as environmental specifications, storage and wireless capabilities can differ. The quotation should map the ordered SKU to the current datasheet.

Physical installation: check wall or ceiling construction, junction boxes, conduit, cable entry and maintenance clearance. A camera can meet the environmental rating while the completed installation fails because connectors or penetrations were not protected correctly.

Power under full load: design PoE around maximum consumption, not an optimistic average. Infrared operation and environmental conditions can change consumption. Maintain switch power reserve and consider UPS runtime during extended utility interruptions.

Cross-vendor compatibility: validate required third-party VMS functions in a test environment. RTSP and ONVIF improve interoperability, but advanced events, configuration controls and firmware workflows can remain vendor-specific.

Storage: specify retention days and recording policy before buying the recorder. Storage is often one of the largest variables in a video surveillance project. Use a sizing calculation based on actual streams and include growth capacity.

Lifecycle support: establish the warranty route, replacement process, firmware support plan and spare-unit strategy. Critical locations may justify holding spare cameras so a failed endpoint can be replaced immediately while warranty processing continues.

Uganda Procurement and Delivery Logistics

FourTeck can structure FortiCamera CD55 quotations around the complete surveillance requirement rather than treating the camera as an isolated line item. A useful procurement request includes the number of camera points, expected installation environment, recording retention, management platform, available network infrastructure and required accessories. This allows technical validation of PoE switching, recording capacity and mounting requirements before purchase.

Order processing and delivery timing depend on confirmed stock position, quantity and the selected supply route. For project deployments, buyers should request a written quotation that identifies the exact model or manufacturer part number, commercial validity period, delivery terms and warranty basis. Where staging is requested, devices can be prepared against an agreed configuration plan before dispatch, reducing repetitive work at the installation site.

For installations outside central Kampala, project planning should also account for transport, installer travel, site access windows and commissioning time. Remote sites may benefit from pre-labeled devices, documented IP plans and configuration templates so local installation teams can work against a controlled deployment standard.

Coverage Across Uganda

FortiCamera CD55 procurement can support organizations operating in Kampala, Entebbe, Jinja, Mbarara and Gulu as well as projects in other Ugandan districts. Kampala deployments often involve corporate offices, commercial buildings, financial institutions and data or communications facilities. Entebbe projects may include hospitality, logistics, institutional and airport-adjacent environments. Jinja and Mbarara organizations can use standardized IP surveillance for manufacturing, education, healthcare, retail and distributed business operations, while Gulu projects can benefit from pre-staging and documented configurations when technical resources are centralized elsewhere.

For multi-branch organizations, the key benefit of standardized procurement is consistency. Using a common camera family, mounting practice, network design and recorder architecture reduces variation between locations. FourTeck can help consolidate requirements into a repeatable bill of materials while allowing each site to adjust camera quantity, lens positioning and storage capacity to its local risk profile.

Cross-Border and Regional Supply

Organizations operating across East Africa, the Gulf and broader African markets can coordinate related technology requirements through FourTeck regional resources. Visit FourTeck Uganda for Uganda requirements, FourTeck Kenya for Kenyan projects, and FourTeck Africa for wider African deployments. Gulf procurement can be coordinated through FourTeck UAE and FourTeck Kuwait.

Cross-border projects should standardize part numbers and technical baselines while allowing commercial terms, delivery routes and warranty procedures to reflect the destination country. For large rollouts, a master bill of materials can define camera models, PoE switches, recorders, storage, UPS systems and mounting accessories, with country-specific quantities and logistics handled separately.

Related Products and Infrastructure

A complete FortiCamera deployment normally requires more than cameras. Buyers can explore the Uganda enterprise technology catalogue for complementary infrastructure. Typical related requirements include FortiRecorder appliances or services for recording and management, managed PoE switches sized for the aggregate camera power budget, UPS systems for continuity during power interruptions, structured network cabling, mounting hardware and storage resources sized for the required retention period.

Where a project includes multiple camera types, fixed-lens dome cameras can cover wide general scenes while the CD55’s motorized lens can be reserved for positions requiring tighter framing. Indoor compact cameras may suit office or reception environments, while other specialized camera formats may be better for long-distance perimeter monitoring. Contact FourTeck Uganda sales and engineering with the site plan or camera schedule to build a matched bill of materials.

FourTeck Technical Service Capabilities

Technical procurement support can begin with bill-of-materials validation. This process checks whether the proposed camera quantities, recorder platform, PoE switch capacity, storage resources and accessories align with the stated surveillance requirement. For complex projects, engineers can review camera locations, expected viewing objectives and retention targets before the order is finalized.

Staging can include device labeling, firmware baseline checks, addressing plans and configuration preparation where agreed. Pre-shipment validation is especially valuable for distributed deployments because it reduces the number of configuration decisions that must be made at remote sites. Documentation can be structured around camera identifiers, physical locations, switch ports and management assignments so future maintenance teams inherit a usable system record.

Post-sales assistance can cover deployment questions, compatibility checks and troubleshooting within the agreed support scope. For warranty cases, maintaining the product serial numbers, invoice information and fault description helps accelerate diagnosis and replacement processing. Organizations with critical surveillance requirements should combine manufacturer warranty coverage with an operational spare strategy rather than relying solely on replacement lead time.

FortiCamera CD55 Technical FAQ

Is the FortiCamera CD55 suitable for outdoor installation in Uganda?

Yes. The CD55 is designed as an indoor/outdoor vandal-resistant fixed dome, and current Fortinet documentation lists strong environmental protection for the current cloud model. Outdoor performance still depends on correct installation. Cable entry points, conduit, junction boxes and network terminations must be protected from moisture, and the camera should be positioned to reduce direct sunlight where practical. Installers should also consider lightning and surge protection, mounting strength and service accessibility. For exposed locations, the complete installation method matters as much as the enclosure rating itself.

What image resolution does the CD55 provide?

The camera uses a 5MP low-light CMOS sensor and supports 5MP video at up to 30 frames per second. It also supports several lower resolutions, including 4MP, 3MP, 1080p and 720p. This gives designers flexibility to balance image detail, bandwidth and storage. Maximum resolution is not always necessary for every viewing stream. Many deployments use a higher-quality stream for recording and a lower-resolution stream for remote viewing. Storage sizing should be calculated from the actual recording profile rather than the sensor resolution alone.

Why choose the CD55 instead of a fixed-lens dome camera?

The main reason is optical flexibility. The CD55 provides a motorized 2.7–13 mm autofocus lens with 4x optical zoom. A fixed-lens camera has one field of view, so installers must select the lens correctly before installation or accept compromises in scene framing. With the CD55, the view can be adjusted after the camera is mounted. This is valuable for gates, entrances, corridors and other positions where target distance or required framing varies. Optical adjustment also preserves sensor detail better than simply enlarging a wide image digitally after recording.

Does the FortiCamera CD55 support night surveillance?

Yes. The camera provides low-light imaging and integrated dimmable infrared illumination extending beyond 20 metres under suitable conditions. It is specified down to 0.03 lux in colour and 0.01 lux in black-and-white at the wide F1.6 aperture. Actual nighttime results depend on the environment. Reflective walls, rain, dust, mounting angle and target reflectivity can affect IR performance. Commissioning should therefore include a nighttime test at each important camera position so the installer can adjust lens framing and infrared behaviour for the real scene.

Can the CD55 be powered directly from a network switch?

Yes. Current CD55 documentation specifies IEEE 802.3af Class 3 PoE, allowing power and network data to share the Ethernet connection. This simplifies cabling and makes centralized backup power possible. The PoE switch must have sufficient total power budget for all connected cameras and other powered devices. Designers should calculate using the maximum published camera draw and include reserve capacity. If cameras must continue recording during power failures, the PoE switches, recorders and relevant network infrastructure should be connected to correctly sized UPS systems.

Does FortiCamera CD55 work with FortiRecorder?

Yes. Fortinet documentation identifies FortiRecorder as a supported platform for the FortiCamera family. Compatibility should still be checked against the exact camera variant, recorder model and software release planned for the project. This is particularly important before firmware upgrades or large deployments. A staged pilot can verify camera discovery, recording profiles, playback, event behaviour and administrative workflows before the remaining cameras are commissioned. For cloud-enabled CD55-C deployments, FortiCamera Cloud is another management path and should be evaluated according to project requirements.

Can the camera integrate with third-party video systems?

The CD55 family supports RTSP, and current cloud documentation lists ONVIF profiles S, G and T. These standards can support interoperability with compatible third-party systems. However, buyers should not assume that every advanced feature will behave identically across all video-management platforms. Basic streaming may work while event handling, configuration, edge recording or device maintenance differs. Where third-party VMS compatibility is mandatory, test the exact camera firmware and VMS release before final procurement. Document which features are required and validate them in a proof-of-concept.

How much recording storage is required for a CD55 deployment?

There is no single storage figure because capacity depends on camera count, resolution, frame rate, codec, bit rate, recording schedule, scene complexity and retention period. A system recording continuously at 5MP and high frame rate will require substantially more storage than one using event-based recording or lower frame rates. H.265 can improve efficiency, but the design should still be calculated using realistic stream settings. For procurement, provide the number of cameras and required retention days so recorder and storage capacity can be sized with appropriate headroom for future growth.

What should be included in a FortiCamera CD55 quotation?

A useful quotation should identify the exact camera part number and quantity, required mounting accessories, recorder or cloud management requirements, PoE switching, storage, UPS protection, installation services and warranty basis. It should also state commercial validity and expected delivery terms. For larger projects, include a camera schedule showing each location and monitoring objective. This allows the proposed equipment to be checked against actual needs. Buying only the camera quantity without validating power, storage and recording architecture can create additional costs during installation.

What support information should be retained after deployment?

Keep a record of each camera serial number, physical location, IP address, switch and port assignment, firmware version, management platform and installation date. Also retain the invoice, warranty documentation, administrator ownership and configuration backup procedures. These records shorten troubleshooting time and simplify hardware replacement. For multi-site deployments, use a consistent naming convention so a camera shown in the management system can be quickly matched to its physical location. Critical sites should also maintain a tested spare camera and a documented replacement procedure.

Request a FortiCamera CD55 Uganda Project Quote

Send FourTeck your camera quantity, site locations, retention period, recorder requirements and existing network details. The project can then be reviewed for camera suitability, PoE capacity, storage sizing, accessories and deployment requirements. For tenders and multi-site rollouts, include the camera schedule or bill of quantities so the proposed part numbers can be validated before ordering.

Contact FourTeck Uganda