Solving the Computer Application Documentation Dilemma
For over 30 years working with financial and business computer applications as a user, consultant and supplier I have observed the ‘computer application documentation dilemma’ many many times. Having spent significant resources and money configuring and implementing a solution, organisations are then faced with committing more money and resources to documenting what they have. Whilst all is going well and they are being pressed to get on with the next project the temptation is to put it off or to do a less than optimum job. Documentation gets even less attention when it comes to those little fixes and changes that inevitably take place after the original implementation.
If you want a full list of software documentation issues then take a look at Table 1 of the 2016 research report: ‘Software Documentation Management Issues and Practices: A Survey’ HERE where the authors have collated research done on the subject.
Cutting this corner can seem like a good decision until something significant goes wrong with the application and then there isn’t a good source of information to help the support team trying to solve it! Getting a solution is delayed whilst they try to work out what the application is doing or they think they know and the fix they deploy makes things even worse. This is also the case when it comes to making other changes to ‘improve’ the application or implement upgrades.
Some will claim with SaaS applications this is not the case as they are configured not customised like those old legacy applications we used to work with. This is not true. The documentation supplied with SaaS applications cannot, and does not, take full account of all the configuration you have done! This is especially true for Enterprise Performance Management (EPM) applications where configuration is used extensively to meet information structure and process specifics required by each organisation.
We have grappled with this dilemma whilst working with our clients at Brovanture and in 2021 our team decided to look for a solution. With encouragement and support across from our entire team the solution took shape, was tried and tested and has finally reached the point that we can release it to the world!
The Brovanture Documentation Service
It works for ALL Oracle Cloud EPM Financial Close and Planning applications (all versions including PBCS, EPBCS, FCCS and later) plus NetSuite Planning and Budgeting. It does not matter who configured or implemented the application. To be clear, you don’t have to be a Brovanture customer or have had your application implemented by us.
For extraordinarily great value for money – a single fixed price of just £1000, Brovanture will produce a standardised documentation set for your Oracle / NetSuite Cloud EPM application no matter how large or complex it is. It is guaranteed to be correct and better still if you make changes to the structure or configuration of your application Brovanture will produce a new set of documentation with a 25% discount off the current first-time price.
It sounds too good to be true! Well, I felt the same way when the team told me what they have achieved and what they believed we should charge for the service. Then I saw what they had done, and I was blown away. You can check it out for yourself by visiting our website HERE. There are full details, plus you can download the full set of documentation we have produced for the sample application shipped with Oracle Cloud EPM Planning – Vision. I am sure you will be impressed. You can contact us via the website or please feel free to contact me via LinkedIn.
I nearly forgot – A Happy and Healthy 2022 to you all. Maybe 2022 will be the year you resolve to get you Oracle / NetSuite Cloud EPM applications fully documented?
Until next time