Once the optimum list has been agreed, we generate the raw estimate within DWSDimension. One of our senior analysts interprets the estimation results and writes a comprehensive report of our findings along with an object-by-object estimate at a minute’s level of detail.
Dimension is, we believe, the most accurate identifier & measurer of JDE E1 enhancements available in the market place today. It uses precise algorithms to calculate the original development time of all modifications to each object, splits each object into one of four categories (mod-to-standard, copy-of-standard, custom or "pure custom") and calculates the effort needed to upgrade each object on an "as is" basis. It uses detailed analysis calculations, employing layers of factoring to allow for the complexity of your specific jump in release-level steps and the complexity of your code.
This is achieved quickly and efficiently, taking into account ALL your code and modified objects.
The questions to ask yourself are:
- "How confident am I that my modification documentation is complete and 100% accurate?"
- "Can I get hold of all the developers and consultants originally involved in my JDE implementation to help me work out what all the mods are or should be?"
- "In cases of incomplete documentation how confident am I in the memories of those people originally involved in my JDE implementation to give me an accurate and 100% complete list of mods?"
- "How certain am I that no mistakes have been made – and that undocumented modified objects don’t exist in my system?"
Factoring Explained
The level of complexity to upgrade from, say, Xe to Release 9.0 is higher than upgrading from, say, E811 to Release 9.0. This is owing to the difference in levels of net change in standard JDE E1 between releases. We have used Dimension to record exact net change between every combination of "from" and "to" release, which is used to create a "factor hierarchy". As well as taking into consideration the change in release-level, we also account for net change to System Codes, Object Types and even individual objects. For instance, we know precisely the level of standard net change P4210 has undergone between releases. The "factor hierarchy" also takes into consideration whether net change to every object in JDE is to code, layout or a combination of both.
Value Proposition
- Caters for releases B7333 to 9.0.1
- Provides and estimate in days/hours/minutes for every single modified object to get it from the current release to the target release of choice
- Automatically calculates the original effort to create your existing modifications
- Although you are not tied to DWS for the upgrade, we are so confident in our service, we are willing to fix price the actual upgrade should you wish us to pitch for the work
- The estimate can be broken down as per your requirements. Examples could be to split by functional area, system code or by unit of time. That is, show all objects < 1 hour, < 1 day, < 5 days, < 10 days etc
- We provide a detailed report of our findings along with recommendations and risk factors
- We walk through the results with the customer either via a virtual workshop or a face to face visit, which ever is agreed
- The estimate will automatically take into account the base object level differences between the standard source and target releases
- Service can be delivered remotely – no requirement for on-site visit