Conigma™ CCM

- Overview -

Change and Transport Management

for SAP® made easy

Josef Huber

General Manager

Industry Drivers for improved Change Management

• IT Governance and Compliance

• Regulatory requirements – SOX, Basel II, KontraG, EuroSOX, IKS

• Coverage of more business processes and higher integration within an

organization

• Optimized sourcing strategies – employee, partner, software factory, follow-

the-sun development …

• IT as a Business

• Transparent cost control and cost allocation

• Performance monitoring of IT processes and services

• Optimized usage of resources

• Recognize, evaluate and manage IT risk

Trends in SAP Customers

• Increasing Usage of newer SAP modules

• More parallel SAP landscapes, i.e. ERP, BI, HCM and CRM + Learning systems, ......

• Leveraging new Technologies

• More than 30% of SAP installations will use SAP Netweaver as technology platform*1 by

end of 2008

• ABAP, JAVA, XI (business process integration), BI

• SAP Templates

• Rates for SAP consultants and developers sharply increasing since 2006

Complex Change Requests impacting more than one SAP line

Complex Change Requests combining different technologies

Highly complex release and transport management (costly, error prone)

Growing cost-of-ownership of SAP

*1 Source: RM Consult – September 2007

Status Quo - Development/Change process for SAP

• Manual, Slow, Expensive and Error-prone

• Tracking Changes at Transport Object level (Transport object means a piece of

ABAP or JAVA code, a change in a table, a new table or any other change, which shall be

deployed on a SAP system)

• Hundreds up to thousands of transport objects per month

• Management of Changes and Releases

• Phone, Email, Paper forms, Spreadsheets, MS-Access

• Management of related documentation out-of-sync

• Functional specification, Technical specification, Effort estimation, Tests to be

used, Test results, Approvals associated with a change

• Compliance

• Audits are time consuming and 70% are failing during first pass

Conigma™ CCM

(Change and Transport

Management for SAP)

Conigma™ CCM – Benefits

• Save up to 80% of the Change and Transport Management related

Communication and Coordination effort

– This is about 5-10% of the overall effort of a complex SAP project

• Achieve up to 30% faster development time

– Less rework, no delays due to miscommunication and manual tracking of

progress

– parallel work, i.e. development of software and development of test cases

• Save up to 80% of reporting time to prove compliance

– Siemens has saved nearly 100%

• Avoid up to 90% of change management related mistakes

– Transporting incomplete CR’s

– Transporting untested CR’s, …

– Transporting CR’s without completion of Non-SAP development tasks

• Gain a 50% higher chance to identify and prevent critical risks

Conigma™ CCM

SAP certified software solution managing the CHANGE and TRANSPORT

PROCESS of configurations and customizations for all kinds of SAP systems in

almost every version (4.6C up to 7.0)

– Enables implementation and enforcement of highly sophisticated development

workflows for complex, parallel SAP landscapes

– Enables efficient cooperation of virtual global teams

– Allows tracking back every change in a SAP system to a business requirement

– Enables automatical deployment of right object with the correct version on the right

SAP system

– Leads to full audit compliance according to Sarbanes-Oxley-Act or other regulatory

requirements, i.e FDA, ESHA, Basel II, J-SOX and others

– Supports ITIL service support and service delivery requirements

Conigma™ CCM – Covering the Life Cycle of a SAP

Change

Planning ImplementationQuality

AssuranceOperations andMaintenance

Phase-Out

Conigma™ CCM

Transport

Service Desk

Release planning

Development

Transport

Conigma™ CCM vs. SAP Solution Manager

Differences

• Conigma™ CCM integration with enterprise wide Service Desk applications is easily possible

(SAP Solution Manager may be used as Service desk for SAP tickets)

• Conigma™ CCM has been developed to manage change across mulitple SAP lines (i.e. a CR

requires changes within ERP and BI) – SAP Solution Manager can not handle this

• Conigma™ CCM allows feature-oriented development (i.e. parallel development of several

releases on one SAP development system) and release-orientend development - SAP

Solution Manager allows only for release/project-oriented development

• Conigma™ CCM controls the overall development cycle for ABAP and Java, even for CR‘s

requiring the use of both technologies – SAP Solution Manager does not support the

development workflow for Java

• Conigma™ CCM allows to control the transport of ABAP and Java out of one solution – with

SAP tools only, SAP Solution Manager and OTO are needed and are not yet integrated

Conigma™ CCM – when to start with ?

• Optimal

– Start of a new project – managing already the initial development process

• Introduction of SAP

• SAP release upgrade

• Major functionality upgrade, i.e. new SAP modules, organizational change, new

processes

– Benefits

• Improve productivity and transparency of initial development process - reducing

cost, time and risk (SI and SAP customer)

• Ready-to-go „SAP Change management“ process in place with going-live

• Complete documentation of all customizations developed before initial go-live

• Full compliance

• Suboptimal

– After going-live of a major SAP project

– Benefits

• Improve productivity and transparency of SAP change process - reducing cost,

time and risk (SAP customer)

• Complete documentation of all customizations after go-live

Conigma™ CCM – comprehensive Support for SAP

Templates

TtDt

Dc1 Tc1 Pc1

Dc2 Tc2 Pc2

Dcn Tcn Pcn

D T T‘ P

D T T‘ P

D‘

D T P

D‘ T‘

Local dev. 1

Local dev. 2

Global dev. 1

Local dev. n

Conigma™ CCM – Structuring Tasks

Project

Change Request

CTS Project CTS Change Request

CTS Task

Logical Release Project Structure

Technical Release Project Structure Element

Conigma™ CCM allows to arrange projects

according to their project structure after their

release. A logical release can contain several

technical releases. The project structure

elements can hereby be nested into each other

as deeply as needed.

Change requests are always subordinated to a

technical release and there is the option to also

be assigned to one or several project structure

elements.

Conigma™ CCM – Release Management

Explanation

In the example on the left, the project consists of

release 2.00 and release 1.00. The technical releases

1.00 - 25.08.2006 and 1.00 – 26.08.2006 are

subordinated to the logical release 1.00. The release

1.00 shows the project structure‘s requester and

module. The project structure elements CO and FI are

further subdivided into the project structure. The

change request 1089 is assigned to release 1.00 and

to the project structure element CO. It would be

possible to also assign it to project structure element

FI. However, this can not be seen on this screen shot.

In addition, it is also possible to assign it to the

requester. In this way, you can customize as many

hierarchical project structures as needed with any

structure elements.

Conigma™ CCM - Creating Structure Elements

Explanation

You can create and assign new project

structures, releases and Conigma™

change requests in the context menu.

Conigma™ CCM - Access rights and Security

Explanation

Depending on the role of a specific

Conigma user, the user interface of

Conigma automatically displays only the

objects, this specific user should have

access to.

Conigma™ CCM - Hierarchy and Workflow

Presentation

Explanation

Change requests can either be shown

according to their hierarchy or according

to their status in the workflow. You can

assign Conigma™ change requests to

project structure elements by dragging

and dropping them.

Conigma™ CCM – Integrating Development and

Transport Management

Explanation

Depending on the status of the Conigma

change requests, it is possible to create

and assign SAP CTS elements. This

behaviour can be freely configured.

Conigma™ CCM - Status Change in a Workflow

Explanation

Depending on the status of the

Conigma™ change request, you can

trigger status changes. This behaviour

can be freely configured. In the same

way it is also possible to trigger status

changes on a higher hierarchical level for

group processing (e.g. on release level).

Conigma™ CCM - Approvals in a Workflow

Explanation

Depending on customizing, you can

define approval steps for status

changes. Approvals have to take place

before the status of a Conigma change

request can be changed. Approvals and

changes are shown in the workflow.

They can be required on both the

individual user level and the group user

level.

Conigma™ CCM - Integration of Testing

Explanation

For each CR a test scenario may be

defined during the development period ,

which then may be executed

automatically. Used test configurations

as well as test results are stored in

Conigma. Depending on test results

further workflow steps may be executed

automatically.

Conigma™ CCM - Audit Trail

Explanation

All details of status changes and

approvals are recorded in the workflow

log to be used as audit-trail with respect

to Compliance initiatives.

Conigma™ - Report Manager

Explanation

Conigma ReportManager allows the

user to define comprehensive reports .

The report output can be exported to

HTML or to Excel spreadsheets.

Moreover it is possible to apply grouping

and accumulation functions and to

report into Excel diagrams.

Conigma™ - Delivery Management Workbench)

Explanation

The Delivery Management Workbench

includes several plug-ins, which analyze

the requested import order and adjust

the import queues if necessary.

Of course system and client copies are

also supported by the delivery

management workbench. The

sequencing of the imports is tracked

automatically, so that any import errors

due to sequence problems don’t occur.

The transport object analyzer optimizes

on an object level and enhances SAP’s

CTS+/ OTO.

In standard, the actions done in the

Delivery Management Workbench are

scripted, so that the can be automated

by jobs.

Audit Proof Archiving via SAP Archivelink

Explanation

Conigma offers with Archive Manager an

integrated functionality to archive, search and

retrieve all CR related metadata, i.e.

documentation, approvals, audit-trail, etc. via

SAP ArchiveLink. The SAP archiving solution

used by the customer does not matter.

Conigma™ CCM - Summary

• Enabling IT Governance and Compliance for complex SAP environments

• Enforcing standards for the SAP change process

• Supporting IT cost reduction and optimal resource allocation

• Improving quality and reliability of SAP changes

• Allowing distribution of SAP development and operation

Thank you for your attention

Questions, please