Fortinet FortiCamera CD55-C 5MP Cloud-Enabled Enterprise Surveillance Camera

The FortiCamera CD55-C is a fixed-dome, day/night network security camera created for organizations that need dependable high-resolution video coverage with flexible cloud-native or hybrid management. For Ugandan enterprises, institutions, campuses, financial facilities, government offices, warehouses and distributed sites, it provides a practical combination of 5MP imaging, motorized optical adjustment, low-light performance, infrared illumination, local storage and rugged environmental protection. Its role is straightforward: capture clear evidence-quality video at important physical-security points while giving administrators a manageable path for recording, monitoring and retention.

The CD55-C uses a 1/2.8-inch low-light CMOS sensor and supports 5MP video at up to 30 frames per second. A motorized 2.7–13 mm autofocus lens provides 4x optical zoom, allowing installers to adjust framing after mounting rather than relying on a single fixed field of view. The viewing range spans approximately 29° to 99° horizontally, 22° to 71° vertically and 35° to 132° diagonally. This makes the same camera useful for comparatively wide observation points as well as tighter views of doors, gates, counters and controlled corridors.

For procurement teams, the model is especially useful when the project requires an outdoor-capable vandal-resistant dome with straightforward PoE deployment. IP67 weather protection and IK10 impact resistance make it suitable for exposed or accessible mounting locations. IEEE 802.3af Class 3 PoE reduces separate electrical work at the camera position, while maximum consumption of 12.95W allows planners to calculate PoE-switch budgets accurately.

Request FortiCamera CD55-C Quote

Instant Procurement Facts

Availability, warranty entitlement, subscription requirements and lead time should be confirmed against the final bill of materials. FourTeck can validate camera quantity, storage expectations, PoE capacity, mounting accessories and management architecture before quotation so that the commercial offer reflects the complete deployment rather than the camera hardware alone.

Operational Architecture and Camera Design

At the imaging layer, CD55-C combines a 5-megapixel low-light CMOS sensor with a DC iris and motorized autofocus optics. The F1.6 wide aperture supports challenging lighting conditions, with published minimum illumination of 0.03 lux in colour and 0.01 lux in black-and-white operation. HDR above 80 dB assists when a scene contains simultaneous bright and dark regions, such as reception entrances facing daylight, covered loading bays, glazed office fronts or gates illuminated from behind.

The motorized 2.7–13 mm focal range is valuable during commissioning because physical mounting position and the final identification objective rarely align perfectly on the first attempt. A wide setting can cover a larger room or approach, while the telephoto end narrows the scene toward a doorway, transaction point or perimeter target. Autofocus reduces the manual effort associated with achieving a usable image after focal adjustment.

Night coverage is supported by dimmable infrared illumination rated beyond 20 metres. This gives project designers an integrated option for dark corridors, compounds and perimeter approaches without automatically requiring a separate illuminator at every position. Actual identification distance still depends on scene geometry, ambient light, target movement, mounting height and lens setting, so security designs should distinguish between detection, observation and identification requirements.

For video transport and storage efficiency, the camera supports H.264 and H.265 compression together with RTSP streaming. Multiple resolution choices, including 5MP, 4MP, 3MP, 1080p, 720p and lower formats, give administrators flexibility when balancing image detail, bandwidth and retention. Onboard storage capacity is listed at 512 GB, providing local video storage within the cloud-native architecture and additional resilience in distributed deployments.

Connectivity includes 10/100 Mbps RJ-45 Ethernet plus wireless capabilities including 2.4 GHz and 5 GHz Wi-Fi and Bluetooth Low Energy 5.0. Bluetooth is particularly useful during supported local onboarding and commissioning workflows. In a structured enterprise installation, wired PoE is normally attractive because power and network transport can be centrally controlled and backed by UPS infrastructure.

Enterprise Business Outcomes

Key Hardware and Software Highlights

The core hardware advantage of CD55-C is not a single specification but the way its components work together. The low-light sensor supports usable capture in difficult illumination; the motorized DC-iris lens lets the commissioning engineer adapt framing; infrared extends coverage after dark; the rugged enclosure protects the optical system; and PoE simplifies field cabling. The built-in microphone adds one-way audio capture where policy and local regulations permit its use.

From a video-system perspective, H.265 can reduce storage and transport requirements compared with older compression approaches when the surrounding recorder and viewing environment are configured compatibly. RTSP provides a standard streaming mechanism, while ONVIF Profiles S, G and T broaden interoperability possibilities. Buyers should nevertheless validate any third-party VMS requirement in advance because standards support does not guarantee that every vendor exposes every camera function identically.

The cloud-native “-C” designation is important. CD55-C can connect directly to FortiCamera Cloud, which can remove the requirement for an on-premises NVR at a new branch. It can also participate in a hybrid architecture through FortiRecorder. Hybrid deployment is useful where an organization wants longer local retention, mixed generations of FortiCamera devices, or a gradual transition from traditional LAN recording to cloud-oriented operations.

Technical Specifications Ledger

Specification values should be checked against the current regional datasheet and final manufacturer ordering information when a tender requires formally certified values. Camera performance in the field also depends on mounting position, network design, lighting, firmware, storage configuration and management platform.

Configuration and Sizing Worksheet

1. Define the surveillance objective

List every camera position and classify the objective as general observation, activity recognition or detailed identification. A camera overlooking a warehouse aisle has a different lens and retention requirement from a camera intended to identify people at a controlled entrance. Use the CD55-C motorized focal range to validate whether each proposed position can achieve the required scene width.

2. Calculate network and PoE capacity

Reserve an 802.3af-capable switch port for every wired camera and budget up to 12.95W per CD55-C. Do not size a PoE switch only by port count; check the total available PoE wattage. Add design margin for future cameras and verify UPS runtime if surveillance must remain active during mains interruptions.

3. Plan retention and storage

Determine how many days of footage the organization must retain, the expected recording schedule, chosen resolution, frame rate and compression. Onboard storage can support distributed recording, while a FortiRecorder-based hybrid architecture can extend retention. Regulatory, insurance and internal security policies may impose different retention requirements.

4. Confirm management and licensing

Decide whether the site will be cloud native or hybrid. Fortinet documentation states that cloud-native cameras can connect directly to FortiCamera Cloud. Hybrid deployment through FortiRecorder is also supported and may require applicable FortiRecorder feature licensing. Subscription and support terms should be confirmed in the quote because requirements can change by deployment architecture and service term.

5. Prepare the quote package

Provide camera quantity, site count, required retention, mounting environment, PoE-switch availability, desired management method, installation scope and any required accessories. For projects with several branches, include the WAN connectivity available at each site and whether centralized viewing is required.

Deployment Scenarios and Industry Use Cases

Large Enterprise and Multi-Site Networks

A distributed organization can position CD55-C cameras at reception areas, staff entrances, loading points and exterior approaches. Cloud-native operation is particularly relevant where individual branches do not justify a dedicated local recorder. Central administration can simplify operational oversight while onboard storage supports recording at the camera. Larger headquarters can use hybrid architecture where local retention and recorder-based workflows are preferred.

Financial and Banking Institutions

Banks and financial offices often require tightly framed coverage of entrances, service areas, corridors and controlled rooms. The motorized lens helps installers tune scene width, while HDR is useful near glass entrances and high-contrast lobby areas. The rugged dome format also suits publicly accessible positions where resistance to physical interference is important. Final deployments should follow the institution’s security, privacy and retention policies.

Educational and Campus Networks

Universities, schools and training campuses can deploy cameras across gates, administrative buildings, libraries, laboratories, parking areas and circulation routes. PoE supports structured cabling and centralized UPS protection. Multi-site management can be valuable where campuses include separate buildings or remote learning centres.

Government and Public-Sector Procurement

Government projects typically require clear bills of materials, documented environmental ratings, predictable power requirements and supportable lifecycle planning. CD55-C offers published IP67/IK10 protection, PoE power parameters and standards information that can be incorporated into technical schedules. FourTeck can assist with model validation and commercial documentation for procurement review.

Technical Deep Dive: Imaging, Optics and Video Processing

Surveillance quality depends on the entire optical chain. CD55-C starts with a 1/2.8-inch 5MP low-light CMOS sensor, but the motorized lens and aperture are equally important. At the wide end, F1.6 permits more light to reach the sensor than a smaller aperture, which supports colour performance in dim scenes. The camera can transition to black-and-white operation as light falls further, with a published minimum of 0.01 lux at F1.6. Integrated infrared then provides active illumination for dark environments.

HDR above 80 dB is useful where a conventional exposure would either wash out a bright entrance or lose detail in a darker interior. 3D noise reduction assists with image cleanliness in low-light scenes, which can also help compression efficiency by reducing random visual noise. H.264 and H.265 encoding lets designers balance compatibility and storage efficiency. For any critical evidence application, validate actual image quality at the intended mounting height and target distance before standardizing a large rollout.

Technical Deep Dive: Cloud, Firmware and Operational Control

The cloud-native architecture is one of the most consequential characteristics of CD55-C. Fortinet identifies “-C” cameras as cloud-native models that can connect directly to FortiCamera Cloud and therefore do not inherently require a local NVR. This changes branch design: a small office can deploy cameras, network connectivity and appropriate cloud service without maintaining a recorder appliance at every site.

Hybrid operation remains available when local recording, mixed camera generations or gradual migration is required. In a hybrid topology, FortiRecorder connects cameras into FortiCamera Cloud. Fortinet’s current documentation specifies supported FortiRecorder versions and notes that hybrid deployments require an applicable feature license. Firmware and compatibility should therefore be treated as part of lifecycle governance, not as a one-time installation detail.

Technical Deep Dive: Resilience, Redundancy and Recovery

Camera resilience begins with power, network and storage design. PoE allows the surveillance edge to inherit the resilience of the access switch and UPS. If the PoE switch is backed by appropriately sized battery power, cameras can remain operational during shorter mains outages. Network segmentation and redundant uplinks can reduce the impact of a single access-path failure in larger facilities.

Onboard storage adds an important distributed element to the architecture. For cloud-native deployments, video storage at the camera reduces dependence on a conventional local NVR. Where organizations need extended retention, FortiRecorder can be incorporated in a hybrid design. Disaster-recovery planning should document how operators access footage during WAN loss, how configuration is restored after replacement, what spare hardware is held, and how camera credentials and cloud inventory are controlled.

Pre-Purchase Buyer Gap Checklist

Is the cloud service included with the camera? Treat hardware and service entitlement as separate commercial line items unless the quotation explicitly states otherwise. Confirm the FortiCamera Cloud term, support coverage and renewal model before issuing a purchase order.

Do I need a FortiRecorder? Not necessarily. CD55-C is cloud native and can connect directly to FortiCamera Cloud. A recorder becomes relevant when the project requires a hybrid topology, additional local retention, mixed camera support or other recorder-based functions.

Will existing PoE switches work? The camera uses IEEE 802.3af Class 3 PoE and consumes up to 12.95W. Verify both per-port compatibility and total switch PoE budget. Also check VLAN design, uplink capacity and UPS sizing.

Can it withstand outdoor deployment? The published IP67 and IK10 ratings support outdoor and vandal-resistant use, but mounting accessories, cable glands, conduit and installation workmanship must preserve the environmental integrity of the deployment.

Is 512 GB enough storage? Storage adequacy depends on resolution, frame rate, codec, scene complexity, recording schedule and retention target. Define the retention policy first, then size storage and architecture accordingly.

Will it integrate with another video platform? The camera supports RTSP and ONVIF Profiles S, G and T. These standards improve interoperability, but buyers should validate the exact third-party VMS and required functions before procurement.

What physical clearance is required? The camera body measures approximately 97 × 120 × 120 mm and weighs about 498 g. Allow additional space for mounting hardware, conduit routing, service access and lens positioning.

Uganda Procurement, Delivery and Project Logistics

FourTeck Uganda can structure FortiCamera CD55-C supply around single-site purchases, multi-camera upgrades and larger surveillance projects. A useful quotation begins with the number of cameras and locations, but enterprise deployments should also identify mounting conditions, retention expectations, network readiness, PoE availability, management architecture and support requirements. This prevents accessory, subscription or infrastructure gaps from appearing after the hardware arrives.

Order processing and delivery timelines depend on quantity, current regional stock, manufacturer supply and any project-specific accessories. For planned rollouts, procurement teams should request lead-time confirmation before fixing installation dates. Where staging is required, configuration information can be agreed before shipment so engineering teams have a defined deployment plan.

Projects can also be reviewed for compatible PoE switching, FortiRecorder requirements, storage strategy and cloud management. For tenders, customers should provide mandatory compliance schedules early so model specifications and commercial terms can be aligned with the tender response.

Uganda Coverage Matrix

Organizations in Kampala can source CD55-C for offices, commercial buildings, financial facilities, campuses, hospitality sites and enterprise compounds. Entebbe deployments may include offices, logistics locations, hospitality facilities and controlled access points where rugged outdoor cameras are needed. Jinja projects can cover industrial, education, warehousing and branch environments. Mbarara organizations can plan centralized surveillance for regional offices, institutions and commercial facilities, while Gulu customers can use the same model for distributed northern Uganda deployments. For every location, delivery feasibility, quantity and project schedule should be confirmed during quotation.

Cross-Border and Regional Supply

Multi-country organizations can coordinate surveillance procurement across East Africa, the Gulf and broader African markets through FourTeck regional operations. Uganda requirements can be initiated at FourTeck Uganda, Kenya projects through FourTeck Kenya, wider continental requirements through FourTeck Africa, UAE sourcing through FourTeck UAE, and Kuwait requirements through FourTeck Kuwait. Cross-border projects should standardize camera models, subscription terms, firmware policy, mounting accessories and spare strategy while accounting for local delivery and warranty processes.

Related Infrastructure and Accessories

A complete CD55-C deployment normally extends beyond the camera itself. Review compatible Fortinet surveillance solutions, suitable PoE network switches, FortiRecorder solutions, camera mounting accessories, UPS power protection and structured network cabling. For outdoor cameras, pay particular attention to mounting surface, junction arrangements, cable protection and surge-risk planning. For multi-site systems, include WAN connectivity and central viewing workstations in the architecture review.

FourTeck Technical Service Capabilities

FourTeck can assist customers before purchase by validating the bill of materials against the intended deployment. This may include checking camera model suitability, lens coverage assumptions, PoE switch capacity, storage architecture, cloud or hybrid management choice and accessory requirements. A structured validation process is valuable on larger projects because a missing mount, insufficient PoE budget or incorrect retention assumption can delay commissioning even when the cameras themselves are correct.

Where agreed for a project, staging can include inventory verification, firmware planning, configuration preparation and labeling before shipment. Pre-shipment firmware work should follow the approved compatibility baseline rather than automatically loading an unvalidated release. Post-sales assistance can support deployment troubleshooting, configuration review and coordination around manufacturer support processes, subject to the purchased support scope.

Frequently Asked Technical Questions

Is FortiCamera CD55-C suitable for outdoor use in Uganda?

Yes. CD55-C is specified as an indoor/outdoor fixed-dome camera with IP67 environmental protection and IK10 impact resistance. The operating temperature range is -40°C to 50°C with 5% to 90% non-condensing humidity. These specifications make it appropriate for many exterior locations, but installation quality remains critical. Correct mounting, cable sealing, conduit routing and surge planning help preserve reliability. Sites exposed to unusual heat concentration, direct weather, corrosive environments or electrical disturbances should receive an installation-specific assessment before rollout.

Does the CD55-C require a local NVR?

No local NVR is inherently required for a cloud-native deployment. Fortinet identifies CD55-C as a cloud-native model capable of connecting directly to FortiCamera Cloud with onboard video storage. A FortiRecorder can still be used in a supported hybrid topology. Hybrid design can make sense when an organization needs extended local retention, has a mixture of cloud-native and traditional FortiCamera models, or wants to migrate gradually from local recording toward cloud management. Confirm current FortiRecorder compatibility and licensing before purchasing a hybrid bill of materials.

What image quality does the camera provide?

The camera uses a 5MP low-light CMOS sensor and supports 5MP video at up to 30 frames per second. It also supports lower resolutions including 4MP, 3MP, 1080p and 720p. The motorized 2.7–13 mm autofocus lens provides 4x optical zoom, allowing the field of view to be adjusted to suit the scene. Image quality in practice depends on target distance, lighting, movement, mounting height, focal setting, compression configuration and viewing requirements, so critical identification points should be validated on site.

How does CD55-C perform at night?

The published minimum illumination is 0.03 lux in colour and 0.01 lux in black-and-white mode at F1.6. The camera also includes dimmable infrared illumination rated beyond 20 metres. This combination supports day/night surveillance in areas where ambient light becomes limited. The usable distance for identifying a person or object can differ from the nominal IR illumination range because scene reflectivity, lens angle, movement and mounting position all influence captured detail. For high-security perimeter designs, assess the actual scene rather than relying on IR distance alone.

What network and power connection is required?

CD55-C provides a 10/100 Mbps RJ-45 Ethernet interface and supports IEEE 802.3af Class 3 PoE. Maximum published power consumption is 12.95W. A compatible PoE switch can therefore carry both network traffic and power over one Ethernet cable. During project sizing, verify that the switch has enough total PoE budget for all connected cameras and sufficient UPS capacity for the desired outage runtime. VLAN segmentation, uplink capacity and cybersecurity policy should also be considered in the final network design.

Does the camera support local storage?

Yes. Fortinet lists 512 GB of storage for the CD55-C cloud model, and the quick-start technical information identifies a 512 GB SD card. Local storage is important in the cloud-native architecture because video can be retained at the camera while the platform provides centralized management. The number of retention days cannot be determined from capacity alone; it depends on codec, resolution, frame rate, scene activity and recording policy. FourTeck can help translate a retention target into a practical architecture.

Can CD55-C work with third-party systems?

The camera supports RTSP and ONVIF Profiles S, G and T, which provide common mechanisms used by network-video systems. That gives the model a foundation for interoperability, but procurement teams should not assume every advanced function will operate identically in every third-party platform. Before a large purchase, confirm that the intended VMS recognizes the model, supports the required stream profiles and exposes the necessary recording, audio and configuration functions. A proof-of-concept is advisable where third-party integration is a mandatory requirement.

What should be checked before ordering multiple cameras?

Start with camera locations, target scenes and retention requirements. Then confirm mounting accessories, PoE port count and wattage, network topology, WAN connectivity for cloud-managed sites, UPS capacity, management platform, licensing and support terms. Determine whether the project is fully cloud native or hybrid with FortiRecorder. Also document spare-camera strategy and replacement procedures. Providing these details with the request for quotation helps ensure the proposed bill of materials covers the operational system rather than only the camera quantity.

How are warranty and replacement cases handled?

Warranty and replacement handling depends on the manufacturer entitlement, support package, regional terms and the commercial supply arrangement. Buyers should request the applicable warranty baseline and any optional support coverage in the quotation. Keep serial-number records and deployment locations after installation because these simplify fault identification and replacement administration. When a camera fails, technical diagnosis should distinguish device failure from PoE, cabling, network, storage or configuration issues before an RMA is initiated. FourTeck can assist with support coordination according to the purchased service scope.

Can FourTeck help with configuration and deployment planning?

Yes, project support can include architecture review, bill-of-materials validation, PoE and storage planning, cloud-versus-hybrid design, staging requirements and deployment guidance according to the agreed scope. For larger rollouts, it is useful to establish a standard camera configuration, naming convention, VLAN policy, firmware baseline and documentation template before the first site is commissioned. This reduces variation between branches and makes ongoing support easier for the customer’s security and IT teams.

Request a FortiCamera CD55-C Uganda Procurement Quote

Send FourTeck your required quantity, installation locations, retention period, cloud or hybrid preference and target project schedule. The team can review camera suitability, PoE requirements, storage, FortiRecorder needs, service entitlement and accessories before preparing the commercial offer. For multi-site projects, include the number of branches and any centralized monitoring requirements so the proposed architecture can be evaluated as a complete surveillance platform.

Contact FourTeck Uganda