Documentation and ERP

Documentation and ERP

Points to consider
Consultants don’t like doing documentation.
The volume of documentation on a project can be vast and with the modular nature of ERP systems no single consultant will have a handle on the whole documentation project.
Project managers often have their hands full dealing with day to day decisions
Documentation is often thought of as an afterthought and this approach can lead to disastrous consequences.
Employing qualified ERP consultants or project managers to perform what is often an administrative function is wasteful of valuable and expensive ERP resources.
ERP implementation is often as much a process of change management within an organisation as it is software configuration and installation. Taking a communicative approach, with appropriate documentation support, can be of great value when helping the culture develop to the point where employees see the change as a career development rather than a threat.
Documentation is understood by Technical Authors who are capable of taking on these responsibilities.
Three levels of documentation
1. Low level configuration specific to the project – only qualified consultants have the knowledge or information to do this.
2. User manuals – often developed from standard vendor manuals with amendments specific to your implementation.
3. Training materials – developed from vendor training materials, possibly amended by your consultants.