IBM United Kingdom Ltd

IBM Collaborative Lifecycle Management on Cloud

IBM® Collaborative Lifecycle Management is a solution that covers the entire software and systems development lifecycle from managing requirements though development and testing to raising, resolving and retesting of defects.


  • iteration Planning and Project Transparency
  • Work Item, Source Code and Build Management
  • Traceability between requirements and other lifecycle artifacts
  • Built on Jazz technology allowing integration with other lifecycle tools
  • Manage Test Plans, Cases, Scripts, Environments and Results
  • powerful self-service reporting
  • Built-in manual test capability, execute both online and offline
  • Integration with IBM, open source and comptitive automated test tools
  • Record, structure, manage and analyze requirements and traceability
  • A flexible, up-to-date, easy-to-use requirements traceability matrix


  • Improve collaboration across Systems and software engineering teams
  • Increase traceability and visibility of changes across the product lifecycle
  • Faster impact assessment of proposed requirements changes and better quality
  • Quickly identify gaps in test coverage
  • Easily demonstrate compliance
  • Enhances team collaboration with integrated features
  • Open and vibrant Jazz user community
  • Provides high visibility into project activities and team progress
  • Facilitates planning and execution of agile or formal projects
  • Helps improve productivity with advanced source control


£161 per user per month

Service documents

G-Cloud 9


IBM United Kingdom Ltd

Jason Dymott


Service scope

Service scope
Software add-on or extension Yes, but can also be used as a standalone service
What software services is the service an extension to IBM's Collaborative Lifecycle Management (CLM) solution can be extended to include our Continuous Engineering capabilities, allowing system models to be traced to other lifecycle assets such as requirements test cases, and development tasks.
Cloud deployment model Private cloud
Service constraints Upgrades will be applied within 45 days of equivalent on-premise product eGA. The SaaS operations team will test a number of test scenarios to ensure a smooth upgrade, before conducting production upgrades. Customers will be given 7 days notice for major upgrades. For minor releases, customers will be automatically upgraded. OS patches are applied weekly. If there are product security patch alerts,IBM will notify the customer and apply the patches as soon as the customer can accept the outage.
System requirements
  • Modern browsers including Chrome, Firefox, IE and Safari are supported
  • A list of supported browsers and their versions is available
  • RTC integrates into both Eclipse and Visual Studio IDEs
  • A list of supported IDEs and their versions are available.

User support

User support
Email or online ticketing support Email or online ticketing
Support response times For severity 1 issues, support is 24x7 with a response time of 2 hours
For severity 2 - 4 issues, support is local business hours with a response time of 2 hours
User can manage status and priority of support tickets Yes
Online ticketing support accessibility None or don’t know
Phone support Yes
Phone support availability 9 to 5 (UK time), Monday to Friday
Web chat support No
Onsite support No
Support levels Product and service support are included in the SaaS offering, depending on the severity of the issue raised, support will be 24x7 for severity 1 or local business hours for severities 2 - 4.
Support available to third parties No

Onboarding and offboarding

Onboarding and offboarding
Getting started A welcome pack is provided instructing the customer how to access the system, create new users and report issues to support. User documentation is available online. The account team selling the solution would always recommend services days are taken to cover user training, this can be onsite, online or classroom based. Services will be chargable.
Service documentation Yes
Documentation formats HTML
End-of-contract data extraction IBM will return the Client Data within a reasonable period in a reasonable and common format upon receiving written instructions from the Client prior to termination or expiration.
End-of-contract process The infrastructure is based on the VMWare images and once a customer terminates contract and transfers data, IBM decommission the images and data is gone at that point.
The SaaS offering consists of a Collaborative Lifecycle Management environment accessed via the cloud for an agreed number of users. The charging metric is based on the number of unique logins per month. The contract includes 2 upgrades per year and technical support.

Using the service

Using the service
Web browser interface Yes
Supported browsers
  • Internet Explorer 9
  • Internet Explorer 10+
  • Firefox
  • Chrome
  • Safari 9+
Application to install No
Designed for use on mobile devices No
Accessibility standards None or don’t know
Description of accessibility The service is accessible via most modern web browsers across various devices however the user interface hasn't been optimised for mobile devices.
Accessibility testing Unknown
What users can and can't do using the API IBM's Collaborative Lifecycle Management solution consists of Requirements, Quality, and Development capabilities. Each of these has an one or more APIs. These are either REST or code based.
API documentation Yes
API documentation formats HTML
API sandbox or test environment No
Customisation available Yes
Description of customisation IBM's Collaborative Lifecycle Management solution consists of 3 capabilities, Requirements, Test and Development. Each capability allows customisation.

Users are able to create custom requirement types and attributes, these attributes can consist of standard types or can be user defined. Users can also define the work flow used by these requirement types, ensuring requirements are reviewed prior to being approved. The relationship (link type) between requirement types can also be user defined to ensure only certain links are allowed.

Rational Quality Manager includes industry recognised test assets such as Test Plans, Test Cases and Test Scripts, these and other assets can be customised by adding user defined sections, attributes or categories. These could be standard types or user defined lists. These are typically incorporated into templates used by the test team. Users can also define the work flow used by these assets, ensuring tests are approved before being executed.

Users are able to create custom work item types (ie. tasks and defects) including attributes, these can consist of standard types or user defined lists. Users can also define the work flow used by these work items.

These and other changes are performed in the projects properties by a project administrator.


Independence of resources The architecture of IBM cloud services maintains logical separation of client data. Internal rules and measures separate data processing, such as inserting, modifying, deleting, and transferring data, according to the contracted purposes.


Service usage metrics Yes
Metrics types Available on request
- Unique user logins per month
- Concurrent peak users per month
Reporting types
  • Real-time dashboards
  • Reports on request


Supplier type Not a reseller

Staff security

Staff security
Staff security clearance Other security clearance
Government security clearance Up to Developed Vetting (DV)

Asset protection

Asset protection
Knowledge of data storage and processing locations Yes
Data storage and processing locations
  • United Kingdom
  • European Economic Area (EEA)
  • EU-US Privacy Shield agreement locations
User control over data storage and processing locations Yes
Datacentre security standards Complies with a recognised standard (for example CSA CCM version 3.0)
Penetration testing frequency At least once a year
Penetration testing approach ‘IT Health Check’ performed by a Tigerscheme qualified provider or a CREST-approved service provider
Protecting data at rest
  • Physical access control, complying with CSA CCM v3.0
  • Physical access control, complying with SSAE-16 / ISAE 3402
  • Physical access control, complying with another standard
  • Encryption of all physical media
  • Scale, obfuscating techniques, or data storage sharding
Data sanitisation process Yes
Data sanitisation type Explicit overwriting of storage before reallocation
Equipment disposal approach Complying with a recognised standard, for example CSA CCM v.30, CAS (Sanitisation) or ISO/IEC 27001

Data importing and exporting

Data importing and exporting
Data export approach IBM's Collaborative Lifecycle Management solution consists of 3 capabilities, Requirements, Test and Development. Each capability provides various reporting and export options from the user interface. These include exporting to CSV, XLS or XLSX or reporting using PDF, Word, HTML or XSL-FO formats. Depending on the content being exported, the available options will vary.
Data export formats
  • CSV
  • Other
Other data export formats
  • PDF
  • Word
  • HTML
  • XSL-FO
  • Excel
Data import formats
  • CSV
  • ODF
  • Other
Other data import formats
  • CSV, Excel or Open Office
  • RTF, Word or Open Office
  • ReqIf
  • CSV for Work Items
  • File system for source code/files

Data-in-transit protection

Data-in-transit protection
Data protection between buyer and supplier networks
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Other
Other protection between networks IBM will encrypt content not intended for public or unauthenticated viewing when transferring content over public networks. Further, unless excluded by a TD, IBM will enable use of a cryptographic protocol, such as HTTPS, SFTP, and FTPS, for Client’s secure transfer of content to and from the Cloud Service over public networks.
Data protection within supplier network
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway

Availability and resilience

Availability and resilience
Guaranteed availability IBM Service Level Objectives (SLO) is 99.9%
Approach to resilience Available on Request
Outage reporting Email notification of planned outages.

Identity and authentication

Identity and authentication
User authentication needed Yes
User authentication Username or password
Access restrictions in management interfaces and support channels IBM maintains individual role-based authorization of privileged accounts that is subject to regular validation. A privileged account is a duly authorized IBM user identity with administrative access to a Cloud Service, including associated infrastructure, networks, systems, applications, databases and file systems.
Access restriction testing frequency At least every 6 months
Management access authentication 2-factor authentication

Audit information for users

Audit information for users
Access to user activity audit information Users contact the support team to get audit information
How long user audit data is stored for Between 1 month and 6 months
Access to supplier activity audit information Users contact the support team to get audit information
How long supplier audit data is stored for Between 1 month and 6 months
How long system logs are stored for Between 1 month and 6 months

Standards and certifications

Standards and certifications
ISO/IEC 27001 certification Yes
Who accredited the ISO/IEC 27001 Bureau Veritas
ISO/IEC 27001 accreditation date 30/11/2015
What the ISO/IEC 27001 doesn’t cover The infrastructure and platform this offering is run on is ISO/IEC 27001 compliant. The current SaaS application is not compliant, but does have an ISO 27001 Attestation.
ISO 28000:2007 certification No
CSA STAR certification Yes
CSA STAR accreditation date 20/04/2016
CSA STAR certification level Level 1: CSA STAR Self-Assessment
What the CSA STAR doesn’t cover The infrastructure and platform this offering is run on has a CSA STAR Self-Assessment certificate. The SaaS side of this offering currently does not have this. The IBM CSA Star Self-Assessment can be viewed here
PCI certification No
Other security accreditations Yes
Any other security accreditations ISO 27001 Attestation

Security governance

Security governance
Named board-level person responsible for service security Yes
Security governance accreditation Yes
Security governance standards ISO/IEC 27001
Information security policies and processes IBM has an Information Technology (IT) Security policy that establishes the requirements for the protection of IBM's worldwide IT systems and the information assets they contain, including networks and computing devices such as servers, workstations, host computers, application programs, web services, and telephone systems within the IBM infrastructure. IBM’s IT Security policy is supplemented by standards and guidelines, such as the Security Standards for IBM's Infrastructure, the Security and Use Standards for IBM Employees and the Security Guidelines for Outsourced Business Services. Such are reviewed by a cross-company team led by the IT Risk organization every six months.

IBM has a dedicated Vice President of IT Security who leads a team responsible for IBM's own enterprise data security standards and practices. Responsibility and accountability for executing internal security programs is established through formal documented policies. IBM Services teams also have dedicated executives and teams who are responsible for information and physical security in the delivery of our client services.

Operational security

Operational security
Configuration and change management standard Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Configuration and change management approach IBM maintains policies and procedures to manage risks associated with the application of changes to its Cloud Services. Prior to implementation, all changes to a Cloud Service, including its systems, networks and underlying components, will be documented in a registered change request that includes a description and reason for the change, implementation details and schedule, a risk statement addressing impact to the Cloud Service and its clients, expected outcome, rollback plan, and documented approval by IBM management or its authorized delegate.
Vulnerability management type Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Vulnerability management approach With each Cloud Service, as applicable and commercially reasonable, IBM will a) perform penetration testing and vulnerability assessments before production release and routinely thereafter, b) enlist a qualified and reputable independent third-party to perform penetration testing and ethical hacking at least annually, c) perform automated management and routine verification of underlying components’ compliance with security configuration requirements, and d) remediate any identified vulnerability or noncompliance with its security configuration requirements based on associated risk, exploitability, and impact. IBM takes reasonable care to avoid Cloud Service disruption when performing its tests, assessments, scans, and execution of remediation activities.
Protective monitoring type Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Protective monitoring approach IBM maintains and follows policies requiring administrative access and activity in its Cloud Services’ computing environments to be logged and monitored, and the logs to be archived and retained in compliance with IBM’s worldwide records management plan. IBM monitors privileged account use and maintain security information and event management policies and measures designed to a) identify unauthorized administrative access and activity, b) facilitate a timely and appropriate response, and c) enable internal and independent third party audits of compliance with such policies. IBM systematically monitors the health and availability of production Cloud Service systems and infrastructure at all times.
Incident management type Conforms to a recognised standard, for example, CSA CCM v3.0 or ISO/IEC 27035:2011 or SSAE-16 / ISAE 3402
Incident management approach IBM:
- maintains and follows incident response policies aligned with NIST guidelines for computer security incident handling, will comply with data breach notification requirements under applicable law.

- investigates incidents, including unauthorised access, use of content or the Cloud Service, of which IBM becomes aware, and, if warranted, define and execute an appropriate response plan.

- promptly notifies Client upon determining that a security incident known or reasonably suspected by IBM to affect Client has occurred.

- provides Client with reasonably requested information about such security incident and status of applicable remediation and restoration activities performed or directed by IBM.

Secure development

Secure development
Approach to secure software development best practice Supplier-defined process

Public sector networks

Public sector networks
Connection to public sector networks No


Price £161 per user per month
Discount for educational organisations No
Free trial available Yes
Description of free trial A fully functional trial of the Collaborative Lifecycle Management product is available. The time period for the evaluation can be discussed with the the IBM account team.
Link to free trial Trials are available from


Pricing document View uploaded document
Terms and conditions document View uploaded document
Return to top ↑