Support retainers
Three shapes of support, each with a written scope. Pick the one that matches where the estate is: steady state, mid-move, or overdue a proper look.
Standing retainer
Drawn down for patches, break-fix, small changes and advice. You get a monthly statement of days used and days remaining. Unused days roll forward within the term.
For an estate in steady state that needs a named engineer on call, not a project.
Talk to an engineerUpgrade window
Assessment, plan, execution support and validation, scoped to the one move. The window closes when the estate is on the new release and signed off.
For the estate that has decided to move and wants the move run properly.
Talk to an engineerEstate review
Versions, components, customisations, integrations and patch levels, inspected and written up. You get a findings and roadmap document you can plan and budget from.
For the estate that has not been looked at as a whole for a while.
Talk to an engineer01
Versions, components, integrations, what hurts. A short call or a written note — either works.
02
Standing retainer, upgrade window or estate review. Scope and term in writing, one page.
03
A named engineer, a shared ticket list, and access arranged on your terms.
04
Monthly: days used, days remaining, what was done and what is queued. No surprises.
A field runbook for the WebCenter Content Batch Loader: the batch load file format, staging, the load run, the error-file loop, and validating the result.
7 min read
Sizing Oracle WebCenter Content: node roles, vCPU and memory per role, four environments, storage in tiers, and the two lines that wait for a content profile.
9 min read
How we read an existing WebCenter Forms Recognition project — Designer rules, supplier templates, learnt data — and keep it running into the 14c window.
10 min read
How ECMWorks engages on Oracle WebCenter modernization: four engagement tiers, two delivery modes, and the four forward paths off Fusion Middleware 12c.
8 min read
After December 2027, WebCenter 12c's Oracle options are Sustaining Support or Market Driven Support. What each includes, when waiting works, and when it breaks.
9 min read
An engineer day of work on your estate — patching, break-fix, a small change, or written advice. Days are logged as they are used and shown on the monthly statement.
Unused days roll forward within the term of the retainer. They do not carry past the end of the term.
Small upgrades, sometimes. A full 12c → 14c programme is better run as an upgrade window: a fixed engagement with assessment, plan, execution support and validation, so the retainer days stay free for day-to-day support.
A written findings and roadmap document covering versions, components, customisations, integrations and patch levels, with the order of work recommended and the reasons for it.
On your terms — your VPN, your bastion, your ticketing. Credentials are never stored on our side; access is arranged per engagement.
Tell us the versions, the components and the integrations. You get a straight answer on what the estate needs, what it does not, and what order to do it in.