EKA > 5 Keys to Successful CTRM Software Implementation
August 07, 2015

5 Keys to Successful CTRM Software Implementation

CTRM software partnership

Undertaking an enterprise software implementation can be fraught with difficulty and obstacles. A failed implementation is extremely costly to the business. Even a less-than-perfect implementation can cause ongoing struggles for the business. (Learn more in "Warning Signs that It's Time to Replace Your ETRM or CTRM Software.")

Eka has developed a partnership approach to deliver successful implementations, as our customers can attest. The keys to a successful CTRM software or ETRM software implementation project include:

1) Clearly Defined Goals & Success Criteria

With any enterprise software implementation project, it is important to have clearly defined and realistically achievable business goals. The presence of success criteria will help to define the scope of the project, establish the appropriate milestones, and guide the decision making process during project execution.

quote_open The Eka team demonstrated an impressive depth of knowledge of the grain business and a willingness to work with us to meet our objectives. quote_close

— Klaus Pamminger, General Manager Marketing, GrainCorp

The presence of success criteria and metrics before the start of the implementation project will ensure that the project will focus on the desired results. In addition, clear objectives will help the team in managing the scope and avoiding unintended scope creep. It also provides an objective means to determine when the implementation project is complete and the software is ready to go-live.

2) Participation of Knowledgeable Business Users

Any significant enterprise software implementation project will involve changes to the client's business processes and perhaps changes in certain job roles. Change management will be a significant factor to the success of the project.

Users will need to commit time to the implementation project. It is critical to have knowledgeable business users participate from the inception of the project. Their buy-in and commitment to effect the needed changes is critical in the success of the implementation. Given their domain and operation expertise, these key users are invaluable in mapping the requirements against what the software has to offer to maximize the benefits.

Oftentimes, there are natural tendencies for the end users to resist changes. Their inclinations may be to make the software conform to existing processes and practices. These tendencies, if not managed properly, will lead to a sub-optimal implementation or, worse, a failed implementation. Without support of key users, the success of an implementation is severely hampered.

A best practice is to dedicate a resource to serve as the change manager. This will ensure changes are implemented smoothly not only technically, but operationally.

3) Dedicated Team and Partnership Approach

The composition of the project team is another critical element in the success of an enterprise software implementation. It is important to dedicate key members on the project team to clear roles and responsibilities. Frequently, not enough investment is made to dedicate the appropriate resources to the project. Expecting key members to devote time to the project while continuing to do their day job is not a realistic model.

Equally important, a partnership culture needs to be developed between the software vendor and customer members. Once the project is initiated, the members must feel equally committed to the success of the project regardless of whether they are from the vendor or the customer. The executive sponsors from both the vendor and customer can help foster such relationships through expectation setting and mentoring.

4) Continuous Successes

Given the complexity and challenges of enterprise implementations, it is best to avoid a big bang approach. Instead, it is advisable to divide the project into logical phases so successes and incremental benefits can be realized on a continuous basis.

By introducing the changes in an incremental manner, the team members can reap the benefits and see the fruits of their efforts on a continuous basis. This will help minimize the project fatigue symptoms that are typically associated with long and complex projects.

With the phased approach, it also allows the project team to evaluate and continually optimize the execution. Equally important, it will provide opportunities for the project team and the sponsors to assess how well the project is meeting the project objectives and success criteria so appropriate adjustments can be made as needed. 

5) Understanding of the Impact to Existing Systems

Enterprise software implementation projects generally involve integration of systems. For successful project completion, all integration requirements should be clearly documented and there should be an integration architect assigned to the team.

All integration touch points and data definition/data conversions between systems should be clearly understood. One of the most critical elements in a successful integration is to determine the proper level of details that need to be integrated. Unnecessary data redundancy in multiple systems should be avoided if at all possible to minimize any performance and maintenance impacts.

Eka's Partnership Approach to Successful Implementations

Eka understands the significance and value of your investment when you undertake a CTRM software implementation project. Not only does Eka have the best commodity trading solutions, we also have a world class project management and support staff that works closely with our customers during all stages of the relationship. Time and time again, we hear from our customers how positive their experience is working with Eka.

GrainCorp agribusiness trading and risk software