The thing about IT systems is that people have to use them. No matter the on-time, on budget performance of the development, the success of your install will be judged on how you move the needle on the metrics that the system was designed to affect. And to move the needle, users have to use your system effectively.
Getting users to use it takes two things. It takes buy-in, which you no doubt facilitated by involving users early to define their requirements. It was at this stage that you investigated and communicated to users the underlying core process that would be automated by your system. You got on the same page with users at the very beginning that the right work is in fact being automated.

Getting people to use your system requires their buy-in from the start, and bite-sized, context-sensitive training and communications after your system launches. Copyright, Bizmanualz, Inc. © 2009.
The second thing that you need to get users to use the system is communications and training, aka: a roll-out. Roll-out is when you remind users that they defined the requirements in the first place, and at that time you all agreed that by automating the core process, their lives would be easier, and the enterprise would benefit through improved metrics.
Remember, your million-dollar technology investment is at risk if people don’t use it. Your IT development was certainly serious. So your roll-out needs to be serious too, not a Band-Aid slapped on to try and recover.
Deployment: Who needs to know what, and when do they need to know it?
A serious roll-out reflects your understanding of how your system will actually be used. Remember those use-cases? OK, dig those up and consult them when planning your training and communications.

Develop a training plan that is consistent with the use-cases that you captured when you gathered user requirements. Copyright, Bizmanualz, Inc. © 2009.
Develop training from the point of view of your users. Think about the context in which the information will be used. That is, deploy training in formats appropriate for the setting. For example, field-delivery workers will have their hands full, literally. They may not have the time to attend live training for extended periods. Instead, break up the information into bit-size nuggets, and deliver it digitally to their mobile devices in visual or video format.

Deliver training in bit-sized nuggets as it is needed. Use formats that work in the situation. Make it as easy as possible or people to know what they need to know to use your system effectively. Copyright, Bizmanualz, Inc. © 2009.
Close the loop by updating standards, policies and procedures.
Remember how, early on, you and your users got on the same page about the core processes that you would be affecting? Ultimately, you need to close the loop. You need to update company standards, policies and procedures to reflect any changes that you have made in the work flow, compliance or standard practices.
It’s too easy to focus on the project management metrics and forget that ultimately it’s the impact of automation that matters. Do users remember that they set the requirements? Do they know how to use the system to do their job? Are people making the connection of improving metrics back to the technology causing it? Take a good look at your roll-out plans, and make sure that you get payback for your technology investments.