Specialism · Built by an engineer from the supply industry
One view of each project while it is running: estimate vs actual, subcontractors, documentation and service in one place, built around the accounting or ERP system you already have. For companies with 10–200 employees that design, build, install or engineer technical equipment and installations.
Estimates in Excel, hours logged too late, and the documentation package put together the night before handover?
Fixed price per phase · Full source code, owned by you · Reply within one business day
Adrian Wollum, CEO and developer · adrian@wollums.no
Who this is for
If you recognise one of the lines below, that is where the solution starts.
Who builds it
CEO and developer
I worked as a consulting engineer and automation engineer at a company that designed and built wireline equipment, with some operator and service work. The company had its own assembly workshop, with welding and machining done by subcontractors. That is the kind of company I build for now. So we start on site with you, in the assembly workshop and the project office, and build the first version there.
WOLLUM is the software house I run at Forus. We build and run our own product, Jobbkontroll, for paying customers in building and construction, and we have built a two-sided B2B platform for a startup and a website for a marketing agency.
Adrian has worked under these requirements himself, as an engineer at an equipment supplier. That is why we build our solutions for them from day one.
| Requirement | Glossary | How we solve it |
|---|---|---|
| Supplier documentation to NORSOK Z-018 and the customer's SDRL | Supplier Document Requirements List | The document list is the register; the status of each document follows the project, not a separate binder. |
| MRB / documentation package per delivery | Manufacturing Record Book | The package is generated from the register, with a table of contents, when the delivery is ready, not the night before. |
| Traceability of 3.1 material certificates and heat numbers | Material certificate 3.1 | The 3.1 certificate is linked to the heat and serial number on receipt and goes into the package automatically. |
| FAT/SAT protocols and as-built per serial number | FAT/SATAs-built documentation | FAT is signed in the workshop with the customer's representative and SAT on site, both on a phone, and both are filed against the serial number. |
| ISO 9001 traceability of non-conformances and changes | Non-conformances and change orders are logged on the project with their cost impact, not in email threads. |
Sound familiar?
The same pattern shows up whatever the company builds: the numbers exist, but they meet too late.
The common thread is not untidy people. The numbers and documents exist, but each in its own place, and nobody sees them together until it is too late to act on them. That is what we fix: one view of the project while it is running, not afterwards.
What we build
You keep your ERP and accounting system. We build the missing layer between quote, assembly workshop, subcontractors and final invoice, and connect it to the systems you already use.
See estimate vs actual per project while the project is running, not in the post-project costing. Hours and purchases are booked against the estimate per work package, in your own assembly workshop and at subcontractors. Change orders are logged with their cost impact, so the estimate is updated when the customer changes something, not when the invoice is disputed. The weekly status report is generated, not written, in a dashboard in the same solution.
One list of what has been ordered, what has been delivered and which certificates are missing, without chasing by hand. The order is created where you create it today, in the accounting system or ERP, and pulled in automatically with the agreed delivery date, drawing revision and document requirements. The welding shop, machine shop or surface treatment supplier confirms delivery and uploads the 3.1 certificate, welding documentation or NDT report through an email link, with no login. The system chases missing dates and certificates on its own.
The documentation package is ready when the equipment is, so the final invoice can go out the same week as the delivery. Every document is linked to project, PO, heat number and serial number, with an SDRL checklist per contract, and certificate PDFs are read automatically on receipt. The package is generated as an indexed PDF, and expiring certificates are flagged before they lapse. If you keep your own project system, we build just the document flow, as an integration.
Estimate vs actual, billable utilisation and contribution margin per project while the project is running, in a dashboard you own. Office and workshop hours are logged against the same project and work package, approved by the project manager and sent as invoicing data straight to the accounting system you use, whether that is Tripletex, Visma, PowerOffice Go or Xledger. We build the integration in the same project.
The service report is ready as a PDF the same day, and the invoicing data is built from what the technician has already recorded. The technician scans the QR code or picks the serial number, works through the checklist, takes photos, logs parts and hours and signs, even without mobile coverage. The history on the serial number decides whether the job is a warranty claim or billable. Your customers see their own equipment, certificates with expiry dates and the next service in a portal, without having to phone. If you want to sell the equipment register as a service of its own, we build it as your product, owned by you.
You enter POs, hours and invoices once. We connect your line-of-business system to RamBase, Monitor, Visma.net, Tripletex, PowerOffice Go, Xledger or Unimicro through the vendors' own APIs, so the project number and drawing number are the same in every system.
How we start
We start in the assembly workshop and the project office, find what costs you most today, and build a first working version there instead of delivering a report. The method is called forward deployed engineering (FDE).
Pricing is set after the scoping phase, as a fixed price per phase. You get a fixed price for each phase before it starts.
| Step | What happens | Typical company | Time | What you walk away with |
|---|---|---|---|---|
| 0First meeting | 60–90 minutes at your site or at Forus. We look at the projects, the spreadsheets and the binders, and tell you plainly whether we are the right fit, or whether off-the-shelf software suits you better. | Any size | 60–90 minutes | An outline of the solution and a fixed price for the scoping |
| 1On-site scoping | A developer works on site with you, follows the projects from quote to final invoice and builds a first working version of the flow that costs you most today, on your own data. You set aside one contact person and some hours with your people, spread over the period; we do the rest. | Any size | Fixed duration, agreed before we start | A first working version, a basis for decisions and a fixed price for the next phase |
| 2Phase by phase | One integration with accounting or ERP | Typically 10–30 employees | 2–6 weeks | The solution live, and you own the full source code |
| Time tracking and project accounting, or document flow, as an integration project | Typically 10–60 employees | 4–8 weeks | The solution live, and you own the full source code | |
| Customer portal | Typically 15–60 employees | 8–12 weeks | The solution live, and you own the full source code | |
| Field and service app | Typically 15–60 employees | 10–16 weeks | The solution live, and you own the full source code | |
| Delivery Control, first version | Typically 15–60 employees | 8–14 weeks | The solution live, and you own the full source code |
The durations are our estimate for a first version of this type. Time and price for your project are set during scoping.
Scenario, not a customer case
The ERP or accounting system sits at the bottom and knows what has been bought and invoiced. Above it sits the project layer: work packages in your own assembly workshop and at subcontractors, with hours and purchases against the estimate. The subcontractor gets a link per order, confirms delivery and uploads the certificate without logging in. When the last certificate is in, the documentation package is generated and the final invoice can go. For marine and aquaculture suppliers it is the same layer, built around class requirements and service history per site.
Starts with on-site scoping, at a fixed price.
See for yourself
An engineer who knows the requirements from the inside, our own product live with paying customers, and open status on every ERP and accounting integration we build.
NORSOK Z-018, SDRL, MRB, 3.1 material certificates and FAT/SAT: the requirements Adrian has worked under as an engineer at an equipment supplier. They are what the solutions are built for.
See the documentation requirementsJobbkontroll, our own product for contractors in building and construction, is live with paying customers. We build and run it: one-tap clock-in and clock-out from a phone, budget vs incurred cost per project in real time, approved hours that become invoicing data, and a Fiken integration with a synchronisation log. It shows that we run and develop software with paying users every day, not just deliver it.
See JobbkontrollSee the status of every integration in the table on the system integration page: what is live and where, and which ERP and accounting systems have a documented API.
System integration with ERP and accountingETO, MRB, SDRL, FAT/SAT, as-built, 3.1 material certificate, post-project costing and service history by serial number, explained the way they are used in the workshop, not the way they read in the standard.
Open the glossaryIndustry and engineering is our specialism. We also build for trade contractors, startups and agencies, with the same method.
Meet us at your site or at Forus
The first meeting takes 60–90 minutes, at your site or at Forus, and after the meeting you get an outline and a fixed price for the on-site scoping. The scoping ends in a first working version and a fixed price for the next phase. After that we build phase by phase, each with a fixed price and a delivery you put to use.
Pricing is set after a scoping phase, as a fixed price per phase.
A first meeting
60–90 minutesAt your site or at Forus. We go through how you work today and where it grinds. You get a sketch of the solution and a fixed price for the scoping phase.
On-site scoping
Fixed price. The developer follows the work where it happens and builds a first working version. You come away with that version, a basis for decisions and a fixed price for the next phase.
A fixed price per phase
Every phase has an agreed scope and a fixed price before we start. The source code is yours.
We are based at Forus, less than half an hour from the supplier communities on Jæren, around Sola and Tananger and in Dusavik. We hold meetings at your site, in the workshop or the project office, or at ours. We meet companies in the rest of Norway by video.
WOLLUM AS · Grenseveien 21, 4313 Sandnes (Forus), Norway · adrian@wollums.no
Articles and checklist
Articles and glossary entries on project accounting, document control and service for industrial and engineering companies. No forms, no sign-up.
What digitalisation means for industrial and engineering companies that build to order: estimate versus actual while the project runs, documentation packages that are ready at delivery, service history per serial number and integration with the ERP you already have.
Questions we get
No. We build the business systems around them: project tracking, document control, hours and service history, integrated with ERP and accounting. The automation supplier keeps the PLC work, and we pull data from it where there is an interface. If you want to sell a service on top of your installations, such as an inspection portal or an equipment register, we build it with the source code in your hands.
Pricing is set after the scoping phase, as a fixed price per phase. An ERP integration typically takes 2–6 weeks, a first Delivery Control version 8–14 weeks. You get a fixed price for each phase before it starts. Book 30 minutes to plan a meeting at your site or at Forus; after the meeting you get an outline and a fixed price for the scoping.
Forward deployed engineering: the scoping happens in your assembly workshop and project office, not a meeting room. The developer follows a project from quote to final invoice with your workshop manager and purchasing, and builds a first version of what costs you most. You provide a contact person and some of your people's time; we do the rest, at a fixed price. See a first version on your own data.
By making logging quicker than not logging. We build the field app with few taps, a QR code on the machine or work package, and storage on the device where coverage is poor. We set the requirements with the people in the workshop during scoping, because they know what gets done and what gets left.
No. The welding shop or machine shop gets an email link per order, confirms delivery and uploads the certificate there, with no account and no password. You see the status and the document on the work package straight away.
We do, for a fixed monthly price agreed during scoping, including updates and monitoring. Prefer to run it yourselves? The source code is yours.
Yes, we build that in. The documentation package can be exported as a PDF with a table of contents, as an Excel list or via an API where the customer's system has one, in the structure the customer's SDRL requires. The register is yours, and the same register can deliver to several customers with different requirements.
Yes. All three have documented APIs, and we build the layer that moves POs, hours and invoices between the ERP and your line-of-business system. The status of each integration is in the table on the system integration page.
Yes, if you have 60 or more employees and need MRP and inventory management: an ERP is the right tool, and we can build the layer around it. No, if you are 15–60 people and lack project, document and subcontractor control around your accounting system; that is what we build. If your technicians use the ERP's service module on site, keep it. You will know which at the first meeting.
Often not, and then we say so. If you only need hours, billable utilisation and project accounting, we recommend Moment, Severa or Tripletex Prosjekt; they are mature and built for exactly that. We build when office, workshop or field work must share one budget, or when subcontractor costs and document deliveries must go into the same project.
Yes: time tracking and project accounting integrated with the accounting system you already have, built as a separate project with a fixed price per phase. An office and project edition of Jobbkontroll is being explored; if you want to help shape it, have a chat with us.
The office edition is being explored. You see what we are considering before anything is built, and tell us what is missing.
No. You own the full source code and documentation, on well-known technology (Next.js and PostgreSQL) that other development companies can take over. If you want to run it yourselves or switch supplier, you take everything with you.
No. Industry and engineering is our specialism, because it is the sector we know from the inside. We also build for trade contractors and project-based businesses with our own product Jobbkontroll, for startups and platform companies, and for agencies and service companies. Whatever the sector, new projects start the same way: on-site scoping, a fixed price per phase and the source code in your ownership.
First meeting at your site or at Forus, then on-site scoping at a fixed price, ending in a first working version and a fixed price for the next phase.
Tell us where things are getting stuck, and we will come prepared.
Or email adrian@wollums.no directly
We reply within one business day.