HEPHEX›MODULES

HEPHEX // MODULES · FULL REFERENCE

One core.
Nine modules, and whatever else.

Every Hephex system rests on a mandatory core and grows with the modules the company needs: the nine in the catalogue, and whatever else gets built for it, under the name the company gives it. They share one database and one logic, what is recorded once, at the source, feeds everything else. Each module sits in one of four complexity tiers.

MANDATORY BASE · DOES NOT COUNT AS A MODULE

Core

Configured from the ground up around your company's processes, and the foundation every other module builds on. Not optional: without a core there is no system.

  • Dashboard
  • Clients
  • Projects
  • Work items
  • Transitions · the movement of each work item between stages
  • Process stages
  • Member permissions · who sees what, and who may change it

The four tiers

Every module falls into one of these four tiers. The more a module touches the rest of the system, the higher the tier it lands in. The names follow the rising heat of a forge.

TIER I

Ember

Only stores data and information; performs no calculations and does not interfere with other modules.

TIER II

Flame

Has rules and menus of its own, performs simple isolated calculations or raises alerts.

TIER III

Furnace

Cross-references information from several modules and influences production.

TIER IV

Fusion

Connects to everything else, with fundamental calculations or deep functional logic.

A module commissioned after the first delivery means changing what is already running, and that comes at its own cost. Get in touch to see what applies to your case.

TIER IV · FUSION

Quotes

Cost, margin and proposal

The material and labour cost of every job, the margins applied explicitly, and a PDF ready to send to the client. The calculation is yours, and it is visible in full: you can always see where a figure came from, with no automatic quoting engine deciding for you.

  • Material cost and labour cost, job by job
  • Explicit margins, applied by you and open to audit
  • A quote PDF carrying your company's brand, ready to send
TIER IV · FUSION

Invoicing

Payment terms and real costs

The payment terms of each project and the real record of what was invoiced and what it cost, tied to the same data as the rest of the operation. What was quoted, what was delivered and what was billed stop living in separate files.

  • Payment terms per project, with a warning when the instalments do not add up
  • Real invoicing and cost records, beside the quote they came from
  • Integrates with the invoicing software you already use: Hephex does not issue certified invoices
TIER IV · FUSION

Machine Capacity

Real load and delay forecasts

The real load of every resource, week by week and month by month, and the delays forecast before they ever reach the client. Planning stops being a guess about what the operation can absorb and starts resting on hours that actually exist.

  • Load and availability per resource, by week and by month
  • Delay forecasts drawn from committed capacity
  • Maintenance stoppages appear where capacity is planned
TIER III · FURNACE

Timeline and Deadline Alerts

The operation seen over time

The operations timeline on the dashboard and the alerts for late work. One reading of deadlines serves both: seeing where everything stands today, and being warned about what will not arrive on time while there is still room to act.

  • An operations timeline at the front door of the system
  • Alerts for late work, with the count in plain sight
  • Delays surface early, not in next week's meeting
TIER III · FURNACE

Versions, Copies and Forecasts

Projects born from other projects

Creating a project from another one, in the three ways that actually happen: a version when the drawing changes, a copy when the work repeats, and a forecast when a client orders a quantity that will be delivered in instalments.

  • Versions of a project, with the history tied to the original
  • Copies for repeat work, without re-entering everything
  • Orders delivered in instalments, with the remainder always visible
TIER II · FLAME

Machine Maintenance

Calendar, costs and reports

The maintenance calendar for every piece of equipment, with the cost of each intervention and the technical reports attached. It gains a history, a date and a figure, instead of living in one person's head.

  • Interventions scheduled and recorded per piece of equipment
  • The cost of each intervention, added to the equipment's real cost
  • Technical reports stored where people look for them
TIER II · FLAME

Consumables

What gets used, and who supplies it

Consumable purchases itemised by type and by supplier. What goes out in tooling, in oil and in everything else production burns through gains an origin, instead of showing up as a round number at the end of the month.

  • Purchases recorded by type of consumable
  • History per supplier
  • Real consumption cost, alongside the cost of production
TIER I · EMBER

Activity

Who did what, and when

A record of every action tied to the user and to the time it happened. When someone needs to know why a figure changed or who closed a project, the answer is in the system instead of being reconstructed from memory.

  • Every action with its author and its timestamp
  • A record searchable by user and by date
  • An honest basis for any conversation about what happened
TIER I · EMBER

Suggestions

Errors and improvements, reported from inside

Users report errors and propose improvements without leaving the system. The people who use the software every day are the ones who know best what it is missing, and this is the shortest path between them and the next version.

  • Errors reported where and when they occur
  • Improvements proposed by the people doing the work
  • No email and no paper in between
TIER I TO IV · ACCORDING TO THE WORK

Other Modules

Whatever does not exist yet

Whatever you need that does not exist yet. Tell us and we build it. The new module is placed in one of the four tiers, according to how much it touches the rest of the system.

  • Placed in one of the four tiers, by complexity
  • Built on the same core and the same database
  • Never a patch bolted on beside the system
← Back