In a live project where schemas are progressively changing due to new design and vendor requirements, we need to have a document guide list of all possible schema changes with each effects when provisioning the schemas.
With a published documentation, this can help mitigate possible critical issues specially in dealing with large scale projects. Example. Deleting the Property, changing the UOM, Adding Parent/Child Class.
| How frequently will feature be used? | Once a month or longer |
| How much time will you save? | This will reduce troubleshooting time in testing and fixing possible issues. |
| Your Industry | Water & Waste Water |
| Other Industry | Energy, Power Generation, Oil and gas, Industrial Plants |
