Solution · Example scenario: Custom Enterprise Platforms

A platform built around one process gives every role involved a shared place to work, when the process is specific to your organization.

Definition: What a custom enterprise platform is

Custom enterprise platform

A custom enterprise platform is software built around one of an organization's own processes that gives the roles involved a shared place to do the work and connects to the systems around it.

  • Built around a single process, from its first step to its last.
  • Used by every role that takes part in the process.
  • Connected to the ERP and other systems already in place.

This page is an example scenario: it describes a typical situation and how Logevon approaches it.

A custom enterprise platform is part of Custom Software Engineering.

Situation: When one process runs on spreadsheets, email and several systems

Example scenario

No system owns the process.

Each system holds a fragment, and the process as a whole exists only in how people work.

Status lives with people.

To learn where an item stands, someone has to ask the person handling it.

Every role uses a different tool.

Work is handed over by email and re-entered at each step.

Changes wait on a vendor.

Adapting a product to the process depends on someone else's roadmap.

Approach: How Logevon would approach it

  1. Map the process and roles

    In Understand and Assess, we work with the people in each role and record the process as it runs, including every handoff and workaround.

  2. Design the smallest usable scope

    In Design, we define the data model and the first scope that people can do real work in.

  3. Build and connect in increments

    In Build & Integrate, your team and ours build in the same codebase and connect each increment to the systems around it.

  4. Hand over and extend

    In Enable & Transfer and Improve, documentation and maintenance pass to your team, which extends the platform as the process changes.

Logevon delivers this work through the Forward Deployed Engineering (FDE) model.

Architecture: What the solution could look like

The components below are typical; which ones a platform needs depends on the process.

User interfaces

  • A view for each role, showing the work that role has to do.

Process and business rules

  • The steps, conditions and approvals of the process, in one place.

Data model

  • The records the process creates, and their links to records held elsewhere.

Integrations

Authorization and audit trail

  • Who may see and do what, and a record of what was done.

Operations

  • Monitoring and releases your team can run.

Handover: What stays with you

A working platform

In your environment, connected to the systems around it.

Documentation

Process model, architecture and operating procedures, written down.

A team that can extend it

Your engineers, ready to maintain and extend the codebase they helped build.

Ownership

Your code and data, per the agreed terms.

Limits: Limits and prerequisites

What the approach depends on

  • A platform is a maintenance responsibility. It needs a team that will own it.
  • Risk grows with scope. Starting small is a design decision.
  • For a standard process, a product can be the better answer; the criteria are on the Custom Software Engineering page.
  • The outcome depends on your team taking part.

FAQ: Questions about custom platforms

How is a platform different from a single application?

A platform carries a whole process for every role involved and connects to the systems around it. A single application does one job for one group of users.

Does it replace our ERP?

No. The ERP stays the system of record; the platform carries the process the ERP does not cover and connects to it. What is kept where is decided in the design.

Can our team extend the platform itself?

That is the aim. Your team works in the codebase during the build, and documentation and knowledge transfer are in scope. How far it can go alone depends on the time and skills it can commit.

How is this different from low-code tools?

Low-code tools suit standard, simple flows. As a process becomes more complex or needs deeper integration, custom development can fit better. The two can also be used together.