top of page

Oracle APEX consulting

For more than ten years we have built our applications on the Oracle Application Express platform - and few have built more business applications upon this platform than us.

​

So if your database platform is Oracle and you need to develop new applications, we can help. We have an extensive library of applications and functions - and examples - that could be part of your development and speed it up significantly. Like our system/organization administration platform with applications, users and roles.

​

A few examples of such custom builds (some of them later got included in our product portfolio) are

  • Class management applications for schools looking to prevent students and pupils from quitting school

  • Insurance case management with damage reporting, communications with all involved parties and cost/transaction handling

  • Team management for sports clubs - players, trainers, contact persons - handling training costs and invoicing for todays "complicated families" where the parents don't necessarily live together (or cooperate) and the kids attend to different teams/sports in the same club which the parents will pay separately for each.

  • Rotation planning, time management and absence handling for large construction projects - on the "Ormen lange" project (one of the biggest gas fields in the North sea) we handled 5000 scaffolders from 5 different companies and on 29 different rotation plans - working on 4 different sites - in one unified time management system based upon our time management systems

​

Even for the biggest projects we used our implementation blueprint - and it didn't just work - it enabled us to get the solutions in production ahead of plan and in record time. We made early prototypes based upon the workshops, then intense rounds of testing, change planning, implementations and new testing until the systems were "production certified". Then after production we continued the improvement process - and expectedly there were a lot of comments the firste 1 - 8 months and then it settled.

​

We are used to (we may even prefer to) work from rather vague ideas of applications and functionality that it should be possible to create, sketches on a whiteboard or a napkin - to early prototypes and productification.

​

When possible, we can even include such custom developed applications in our life cycle management supporting updates and chenges. In some cases we even can offer complete support services (1st and 2nd line).

​

Classic VW Bug
Classic VW Bug

Implementation blueprint

Our blueprint (or recommended process) for implementing our solutions to our customers is simple:

  1. Run a workshop to identify the full scope of the project, options and customer expectations and main facts for the setup.

  2. Set up a project group with covering the required knowledge - ERP systems/integrations, customers process manager/application owner, a small super user group (normally the accounting people).

  3. If needed, make a project plan for the implementation with the main variables identified (like ERP systems, integrations, users and roles and main setup options). We normally recommend to leave the practical details and advanced setup until after the system is in test (or production)

  4. Install and start testing, go live when it's good enough and the users have received the required training.

  5. After 3-4 weeks of use, meet again to find out how to improve the setup and workflow. It normally takes a few weeks to learn the system good enough - and it's always much easier to make a list of things to change after using the system for some weeks.

  6. Make the changes

  7. Meet again after 2-3 months and do the same - normally now it's optimizing and fine tuning that is on the table.

Lifecycle management

To make sure you get the most out of your investments, your IT systems should be part of a regular maintenance schedule like any production tools.

  • New technology offers new possibilities. New versions, functionality or framework technology like PEPPOL

  • Changes in the organization and how you work

  • New demands from authorities or customers

  • Changes in production, logistics, supplier and customers all should be part of the IT system review

  • New ideas and good questions asked - "Why do we need to enter the same values in both systems - and why do we need this on paper?" always are good question

​

​

Grafikk
bottom of page