|
Common Configuration and transactions
There are a number of processes and associated transactions in T&E that should be used in specific situations. For example the "Firmly book "transaction should be executed at a specific stage in the training cycle and so should the "follow-up" action. Each organization has to decide when these transactions should be executed, especially if they serve as triggering activities for workflow, correspondence or billing. If a large user community uses these transactions at will or chooses not to use them at all, it will negatively affect your reporting and you will not get the most out of your T&E system. Standards and common procedures will need to be implemented to make sure that training organizations across the globe use their shared system following the same set of rules.
It often is difficult to implement such rules and not all users will be happy but this re-engineering is necessary. There are a number of "switches" you can set in configuration to determine the system's triggering activities, messages or output but there only is one "switch" that once implemented, will be valid for the entire user community.
The global rollout team will have to communicate this to the users when they are getting ready to go live. With multiple sites, you should opt for a phased rollout rather than a "big bang" go-live for all. It is a good idea to send a team to one or a few selected sites at the time prior and until after go-live to help with outstanding data conversions or training questions. The lessons learnt at each site will reduce errors and issues at the next site and give you a chance to fix problems in between go-lives. You might want to keep your most challenging site until the end.
|