If you’ve spent any time around video security, you’ve heard the acronym soup: VMS, ONVIF, RTSP, IVA… and now “CPP.” In a recent discussion, Rick Bennett asked Tom Fontana and Brad Castillo the simple question many customers are thinking: what does CPP actually stand for?
CPP = Common Product Platform.
In Bosch camera terms, CPP is a way to categorize camera products into “platform generations,” primarily based on the chipset inside the camera. Think of it as a shorthand for which “engine” the camera is built on.
Brad summed it up in a way that’s easy to remember:
Higher CPP number = newer chipset
Newer chipset = more performance (“horsepower”)
More horsepower = more features, more streams, more analytic capability
So when you see references like CPP 3 up through CPP 16, that number is largely pointing to the processing platform generation and what the device is capable of.
CPP isn’t just about age. It also helps explain capability differences across product families. As mentioned in the discussion, some CPP generations lined up with certain product groupings (for example, fixed and PTZ families in one generation, encoders in another, panoramics evolving into later platforms as chipsets were updated).
What matters to you as a designer, integrator, or end user is this:
Older cameras can still:
deliver a solid image
record normally
show up in your VMS
But as Tom pointed out, when you start leaning into advanced analytics and higher-end functionality, older platforms may only support those features up to a point. That’s often the real reason to upgrade: not because the camera failed, but because your requirements changed.
A concrete example from the discussion: newer platforms can unlock more simultaneous video streams and allow you to configure them more independently. Where legacy devices might have supported fewer streams (plus a JPEG stream), newer platforms can support more streams with more options, because the processor can handle it.
This is where CPP confusion can cause unnecessary anxiety. The short answer from the discussion was essentially:
Yes, CPP 3 through current CPP 16 cameras are still supported in Bosch BVMS, and typically in other VMS platforms as well—often via:
a Bosch-specific plugin/driver
ONVIF
So if you have a CPP 4-era device in the field, it can still be perfectly usable in a modern system. The key is aligning expectations: it may not support every “newest” analytic or feature you’re planning to deploy now.
In the conversation, they framed it like this:
CPP 14 and higher are positioned as the current product lines
CPP 7.3 and older were referenced as legacy
CPP 14 and CPP 16 were called out as what they’re working with “currently”
Even if your environment includes multiple generations, CPP gives you a common language to plan upgrades and feature rollouts without guessing.
One of the best takeaways was this: don’t assume older cameras need to be thrown away. If an older camera still performs well for a basic coverage task, consider repurposing it in areas where you don’t need heavier analytics (like LPR/plate recognition or other advanced analytic use cases), and deploy newer CPP platforms where you do. That’s practical engineering: design around need, and future-proof where it counts.
CPP = Common Product Platform
Higher CPP number = newer chipset and more capability
Older CPP cameras can still work fine for video + recording
Advanced analytics and newer features may require newer CPP
BVMS and many other VMS platforms can still support older CPP cameras via plugin, ONVIF, etc.
Upgrade for requirements, not just for age—repurpose older cameras when it makes sense
Contact our team for system design assistance >>