A Growing Cognos Environment Without a Safety Net
CEWE runs one of the larger Cognos environments in its space: roughly 550 users, a BI team of 10 developers, and a reporting footprint that has grown larger every year since the company adopted Cognos in 2002. What started with PowerPlay moved to the web in 2008, then progressed through Cognos 8, 10, and 11. Today, the team runs Cognos 12.04 and is already piloting 12.13.
“We had no versioning in Cognos, so we needed to do something.”
The problem was structural, not cosmetic. Cognos never shipped with native versioning. For a team of 10 developers working concurrently across 50 to 60 dashboards, that's not a minor gap; it's a daily operational risk.
Without versioning, a handful of predictable problems kept surfacing. Developers would overwrite each other's work when two people edited the same report object simultaneously. A deleted dashboard or report meant either rebuilding it from scratch or reconstructing it from deployment files and the content store, neither of which is fast or reliable. And moving changes from development into production had no clean, auditable path.
Usage patterns made the stakes higher. During Christmas, CEWE's peak season as a photo products company, they see around 150 concurrent users hitting dashboards and reports daily. A broken object or an accidental deletion during that window isn't just an inconvenience. It's a support ticket that needs to be resolved fast, with real usage sitting on top of it.
The team also maintains an active license management discipline, reviewing and removing unused licenses monthly to keep costs under control. That's a team that already runs a tight operation. The missing piece was a safety net under the actual development work.
Motio Became the Versioning Layer Cognos Was Missing
CEWE evaluated the market and landed on Motio. As Grunewald put it, Motio was effectively the only viable provider capable of addressing Cognos's versioning gap when they needed it. That's not a crowded field of competitors vying to be the best option. It's a case of being the answer.
Recovery and restore
This is the clearest, most immediate value driver. When a service ticket comes in along the lines of “I accidentally deleted something, could you restore it?”, Motio gives the team a direct path back, rather than having them dig through deployment files or wrestle with the content store. The same restore capability also covers rolling back a report or dashboard after a development change breaks something.
Versioning
This remains the core reason CEWE stays with Motio. Grunewald called it “the valid option” for continuing with the tool, and it's the feature their entire workflow is built around.
Check-in, check-out, and locking
With 10 developers working on the same set of report specifications, the risk of collisions increases as the team grows. Locking prevents two people from stepping on each other's work at the same time, something Grunewald flagged as increasingly necessary simply because of team size.
Environmental movement
CEWE runs one development environment and one production environment. Motio handles pulling and transporting changes between the two, giving them a controlled, repeatable path to deployment instead of an ad hoc one.
On top of the functional wins, Grunewald pointed to something simpler: Motio is easy to live with. “It's easy to update, easy to maintain,” he said, and developers can access it without friction. For a lean team supporting 550 users, operational simplicity matters as much as any single feature.
“We are much safer.”
That single line captures what changed. A 10-person team working concurrently across dozens of dashboards now has a functioning safety net, rather than hoping nothing breaks.
Faster incident recovery
Restore requests that previously required manual reconstruction from deployment files or the content store now resolve directly through Motio. Grunewald called the recovery function CEWE's “major point” of value, the single feature that justifies the tool on its own.
Reduced collision risk across a growing dev team
Check-in, check-out, and locking enable CEWE's 10 developers to work on the same 50 to 60 dashboards without overwriting each other. As the team scales, this kind of concurrency control becomes less of a nice-to-have and more of a requirement, which is exactly how Grunewald framed it.
Lower operational overhead for maintenance and deployment
Between the ease of updating the tool and the structured dev-to-production transport process, CEWE's BI team spends less time on the mechanics of change management and more time on actual development. That's a direct efficiency gain for a team that also has to manage 550 user licenses on a monthly cadence.
Improved resilience during peak season
With roughly 150 concurrent users active during Christmas, CEWE's highest-stakes window, having a fast restore path reduces the business risk of an accidental deletion or a broken dashboard becoming a prolonged outage during the busiest time of year.
“If you need versioning, if you need safety, it's a good thing.”