![]() |
Day Sixty Eight by Dustin Diaz (CC@Flickr.Com) |
The second, the standard is not institution-side or one-side approach, which mean that every stakeholder needs is negotiated during the standard development process. The other concept that i love to hear that there are a structured mechanism how to update the content of standard, which lead the standard to be more flexible for the change in industry.
The GRAPATEL standard is a very thin document, it is only 18 pages. It is easy to read, and I hope that the reader will find it is easy to understand and to implement in real world. That are the real challenges, how to make a standard work. The one of reasons is that every company have their own state of implementing Revenue Assurance. So it should be clearly decide how to adopt the standard into their environment.
The other things that i learn from the standard it self, that it can't stand alone. It will give you a good references but it need other reference to make it works in reality. I got the other two references, which are the practices and the body of knowledge. The practices is a collection of the activity that should be done to make revenue assurance work. The knowledge, of how activity of revenue assurance is done by the company, should be documented and well managed. So some improvements can be applied.
The same thing also for body of knowledge, where the knowledge that needed in doing revenue assurance is documented. Not only cover for technology aspect, but i should also cover about ethics issues, the management of human resource, knowledge management and much more.
The three references create a better and stronger framework in doing revenue assurance in real activities. They complete each others.