We believe that JD Edwards EnterpriseOne customers need to adopt a new way of thinking when it comes to upgrading their systems. Adopting a code-current strategy means maintaining your E1 solution at the latest code base level. Given Oracle’s commitment to support Release 9.2 until at least 2030, this strategy makes more sense than ever.
Smaller, more frequent updates will become the new standard for Oracle JD Edwards over the coming years. Moving to 9.2 sooner rather than later will enable digital businesses to make the most of the latest advances; including social collaboration, global revenue recognition, project forecasting and enhanced mobility applications.
Firstly, code-current is about mitigating risk. Older system components are no longer certified or supported and can lead to systems vulnerabilities, exposing your organisation to unnecessary risks. Updated system components such as databases, operating systems, Internet browsers, language compilers and enterprise security applications are all addressed in the most recent releases.
Code-current also means taking advantage of hundreds of enhancements that have been driven by industry SIGs and developed in partnership with current EnterpriseOne customers.
Our tools allow us to adopt what we call Best Upgrade Approach (BUA), which enables us to upgrade our customers’ modifications in the most optimal way – saving time and money.
If Oracle has not modified the standard object then no upgrade work is required.
By keeping code-current you will become more agile and able to take advantage of the constant developments from Oracle; ultimately achieving a much higher ROI on your annual maintenance costs.
You will accelerate the time between upgrades as the impact on mods will be smaller and lessen the impact of upgrades because you have remained close to the Vendor’s code level; effectively spreading the cost of your next major mods upgrade over a longer period of time and avoiding a significant spend when the next major release arrives.
Each time you perform a code-current exercise you will be starting from an improved position, so your upgrade costs will reduce, you will be able to benefit from the latest (lowest cost) technologies and reduced maintenance effort. These all combine to continually reduce your on-going Total Cost of Ownership.
Contact us now for more information on how Dimension Tempo™ can make code-current a practical proposition for you.
DWS aims to reduce the cost and complexity associated with running, maintaining and evolving customer implementations of JD Edwards EnterpriseOne.
For customers interested in staying code-current, DWS offers a managed service that we call Dimension Tempo™.
Our Tempo service takes advantage of, and leverages, our Dimension Analyze™ and Dimension Professional™ tools. With Dimension Tempo™ we agree a cadence (or rhythm) with our customer. We then regularly analyze the customer’s environment and any and all updates available from Oracle. We do this annually or bi-annually with a view to delivering very manageable code-current change event projects. Each code-current change event project ultimately includes the retrofitting or uplifting of any customer-modified objects impacted by updates made available by Oracle. The objectives of each of these projects are:
Dimension Tempo™ taps into the concept of “getting code-current, and staying code-current”. By design, Dimension Tempo™ will help customers committed to JDE E1 get the most from the continuous-delivery regime adopted by Oracle JD Edwards from release 9.2. Dimension Tempo™ moves customers away from the large infrequent capital expenditure (CAPEX) upgrade projects of days-gone-by, to an operating expense (OPEX) based run, maintain, and evolve model. With Dimension Tempo™ the operating expenses associated with JD Edwards can be smoothed and made more predictable.
Abbey Barn Road
UK: +44 (0) 1494 896 600
US: +1 888 769 3248
ANZ: +64 (0) 9427 99 56