Industries
Technology and CDN
The system is old on purpose. The project is to move it without pretending the business logic was simple.
Past work at Akamai Technologies, from 2014 to 2015, was a Siebel upgrade from 7.8 to IP2014. Browser script had to be rebuilt for Open UI. Development environments and workstations were hosted on AWS so the upgrade could be built and tested before anyone treated production hardware as the sandbox. That engagement is over.
A technology firm’s Siebel problem is usually the same as anyone else’s, with less patience for a slide that says “cloud” and no environment behind it. The work is the version path, the Open UI behavior, the integrations, and a place for developers to run the system. It is not CDN configuration, and it is not a current role at Akamai.
Typical project shapes
An upgrade off a very old version
7.8 to a modern IP release is a project. The business logic in browser script does not come along by itself.
Open UI that matches the old screen
Presentation models and renderers for the applets users already know, including the ones that paint wrong on the first pass.
AWS-hosted Siebel environments
Development and test environments when the team cannot wait on a hardware order to start the upgrade.
Boundary
This practice does not operate a content-delivery network, tune edge configuration, or claim Akamai as a current client. Siebel work for a technology company is still Siebel work.
If the system matters and the team is small, start with a conversation.
A paragraph on the system, the constraint, and the timing is enough. Jon reads these. There is no intake desk.