Cookie preferences

Choose which optional cookies we may use. Your choice applies to this browser for 12 months, and you can change it at any time.

Needed for the site to work and to remember your cookie choice. These are always on.

Cookies used (1)
  • motio_consent · Motio · 12 months
    Remembers your cookie choices and the consent ID used to record them.

Google Analytics tells us which pages people visit and how they use them, so we can improve the site.

Cookies used (2)
  • _ga · Google Analytics · 2 years
    Distinguishes visitors.
  • _ga_<id> · Google Analytics · 2 years
    Keeps session state.

LinkedIn, Google Ads and Salesloft measure which campaigns bring people here, show our ads to people who have visited before, and identify which companies visit.

Cookies used (5)
  • _gcl_au, _gcl_aw · Google Ads · 90 days
    Measures ad clicks and conversions.
  • li_fat_id · LinkedIn · 30 days
    Conversion tracking, retargeting and analytics.
  • li_giant · LinkedIn · 7 days
    Conversion tracking for groups of members.
  • bcookie, lidc, li_sugr, UserMatchHistory, AnalyticsSyncHistory · LinkedIn (linkedin.com) · 1 day – 1 year
    Identify the browser and match visits to LinkedIn members for ads.
  • sliguid, slireg · Salesloft Scout (salesloft.com) · 7 days – 1 year
    Identifies visiting companies for sales follow-up.
Skip to content
Case study · Cognos

Agile BI, without losing control.

How the steward of Canada's .CA domain moved to a three-environment, self-service Cognos pipeline.

Steward of the .CA top-level domain on behalf of all Canadians
Jon Coote
Jon Coote
Information Management Team Lead, CIRA
1 → 3
Cognos environments, properly separated
Self-service
governed deployments, no admin bottleneck
Daily
service requests expedited to production
The challenge

As CIRA shifted to an agile methodology, its old Cognos setup couldn't keep up. A single environment handled development, testing, and production, and version control meant duplicating reports named “v1, v2…” with the “final” copy moved to a production folder. That approach bloated the content store, tracked neither author nor changes, covered only reports (not packages or models), and let just one developer work on a version at a time.

The solution

Moving to three environments on Cognos 10.2, CIRA used Motio for deployment and version control with pre-defined change-control procedures. Crucially, BI developers were empowered to deploy from Dev to QA themselves, no more waiting on an admin. Every deployment carried an audit trail of who, what, where, and when, and content could be compared across environments to ensure the right version shipped.

“Without a tool like MotioCI, our process using Cognos deployment was cumbersome. To effectively follow our agile methodology, using MotioCI is definitely, definitely a big plus.”

Jon Coote · Information Management Team Lead, CIRA
The results
✓Supported CIRA's agile goals with much quicker response to service requests
✓Greatly reduced development cycle times through governed self-service deployments
✓BI content delivered to business users far faster than before
✓One-click rollback when an issue slipped through testing

“After we deploy to production, if something was missed in testing or we have an issue, we can very easily roll back to a previous version using MotioCI.”

Jon Coote · Information Management Team Lead, CIRA

See what Motio can do for your Cognos team.