Skip to main content
PhoenixNet by PRCD Pty Ltd

HomeHow it thinks

How it thinks

The PhoenixNet brain.

Every screen, form and report in PhoenixNet runs through one system. This map is drawn from that system's own code: 1,494 working parts, 6,328 connections and 14 areas of the business.

Drag to turn the map. Click on it, then scroll or pinch to zoom. Select a point to see what it connects to.

How a request is handled

Six layers, top to bottom.

A supervisor logs a weld, an estimator prices a job, a client opens their dashboard. Each request passes down through the same six layers, and every layer works from the same records.

  1. 01

    Entry points

    Every address a person or another system can reach, grouped by the part of the business it serves. There are 1,388 of them.

  2. 02

    Gatekeepers

    Permissions and validation check who is asking and whether the request makes sense before anything changes.

  3. 03

    Decision makers

    They work out what a request is for and which parts of the business need to know about it.

  4. 04

    Working knowledge

    Pricing rules, compliance checks, numbering and scheduling: the rules that decide prices, due dates and what happens next.

  5. 05

    Automation

    Work that runs on its own: reminders, reports, emails and the overnight checks nobody should have to remember.

  6. 06

    Memory

    Jobs, people, equipment, materials, money and evidence, kept as one set of records that every layer above reads and updates.

One set of records

Enter it once, use it everywhere.

"Brain" is just a way of picturing the system. It isn't artificial intelligence. The value comes from every area working from the same records, so anything entered in one place is there wherever else it's needed.

  • Entered once

    A weld recorded on site feeds the quality pack, the progress claim, the client's view and the next estimate. Nobody types it twice.

  • Priced against actual

    Estimating, delivery, people and finance share the same records, so you can compare what a job was priced at with what it actually cost in one report.

  • A record of the work

    Every change goes through the same checks and is logged the same way, so the evidence of what was done builds up as the work happens.

The map is generated from PhoenixNet's own code. Class and file names are left out on purpose, but the structure shown is accurate.