Custom MJOP integration
A multi-year maintenance plan (MJOP) states, per building, which maintenance is needed when and what it costs. But the plan is often disconnected from the accounts, the budget and the work orders for contractors. Appfront builds the integration between your MJOP and the rest: the budget and reserve fund based on the plan, maintenance passed to the schedule as work orders, and completed work fed back into the plan.
What is an MJOP integration?
An MJOP, short for multi-year maintenance plan, describes per building which components there are, what condition they are in and when they need maintenance or replacement, with the costs per year over a long period. The condition is often recorded using a condition assessment in line with NEN 2767. For an owners' association (VvE), the plan is also the basis for reserves: since 2018, every VvE must have a reserve fund.
The plan is created in an MJOP package or in a module of the property system. After that, the retyping begins. The budget for the members' meeting is put together in a spreadsheet. A maintenance year is converted into work orders by hand. And what the contractor has done doesn't make its way back into the plan, so the next plan starts from outdated data.
We build custom because every property manager has different packages and ways of working. Which package the plan comes from, which accounts system, which planning tool and which overviews you want determines how the integration works. Many MJOP packages can export and some have an API. We'll look at which route your package offers in the first step.
Plan and budget
Based on the same figures.
From plan to work order
The maintenance year scheduled.
Execution fed back
The plan stays up to date.
How we build your MJOP integration
We start with how you work: where the plan is now, who prepares the budget, how work orders are issued and what happens to the data after the work is done. Then we look at which export or API your MJOP package offers and which systems need to be connected. We often begin with the budget and reserves based on the plan, because that's where most of the calculation work lies. Work orders to the schedule and execution fed back into the plan follow once that runs well. After that, we maintain the integration as your packages change.
Plan, budget, work order and execution.
Export or API of the MJOP.
Budget, planning and feedback.
Go-live, monitoring, and maintenance when things change.
What an MJOP integration actually does
The components below appear in almost every MJOP integration. Which ones you need depends on your property and your packages.
Importing the plan
Per complex and component.
Budget
Reserves based on the plan.
Jobs
From maintenance year to schedule.
Execution fed back
Completed work in the plan.
Statements
Per complex and per year.
Log
Every change recorded.
Who we build an MJOP integration for
The integration is intended for organisations that have a multi-year maintenance plan (MJOP) and want to use it in their administration and scheduling. The more buildings and components you have, the more it delivers.
OHA managers
Budget and reserve fund.
Housing associations
Plan to work order.
Property managers
Costs per property.
Public-sector real estate
Schools, healthcare and municipalities.
Technology and integrations
This page is about integrations with the multi-year maintenance plan. For the measurement itself, see our page on the inspection app for condition assessment under NEN 2767, for VvE management our page on VvE software, and for housing associations our page on housing association software. You can read about our approach on custom software development.
Why Appfront for your MJOP integration?
A budget copied by hand from the plan, a maintenance year that falls apart into separate work orders, and completed work that never makes it back into the plan all cost a manager time and make the next plan unreliable. That is what we build on: plan and budget using the same figures, the plan as the source for work orders, and completed work fed back into the plan.
One set of figures
Plan and budget match.
Less manual work
Work orders from the plan.
Up-to-date plan
Completed work feeds back.
Security and privacy in an MJOP integration
The integration mainly processes data about buildings, maintenance and costs. For a VvE (homeowners' association) or housing association, data on owners or tenants is included too, and that is personal data. We only use what is necessary, access is set up per role, and every change is logged.
The integration runs in a European data centre, with encrypted storage and daily backups. We record the processing in a data processing agreement.
Frequently asked questions about an MJOP integration
Questions managers ask before getting started.
A multi-year maintenance plan. For each building, it describes which components there are, what condition they are in and when they need maintenance or replacement, with the expected costs per year. The condition is often determined with a condition assessment under NEN 2767.
Since 2018, a reserve fund has been mandatory for every VvE. The annual contribution is at least 0.5 per cent of the reconstruction value, unless the VvE saves on the basis of a multi-year maintenance plan. That is why most VvEs work with an MJOP, and why it helps if the budget comes straight from it.
From MJOP packages and from property systems with an MJOP module. Many packages can export to a file, and some have an API. We look at which route your package offers, and how up to date the data is, in the first step.
Yes. The integration sets up the work for a maintenance year as work orders in your planning or property system, per complex and per component. You decide what goes ahead, what is combined and what is pushed back a year.
Yes, as long as the work is recorded somewhere. What the contractor did and what it cost goes back into the plan, as do new condition assessments. That way, the next update starts from the actual situation rather than old assumptions.
The integration reports it and records what went wrong. The message is retried or queued for review, so no budget is built on partial data.
For VvE managers with many complexes, housing associations, property managers and investors, and organisations with public-sector real estate such as schools and care providers. If you have a single building and a plan that is updated every few years, a spreadsheet is often still enough.
Want your MJOP connected to everything else?
Tell us where your maintenance plan currently lives and what is still done by hand. We will show you how the integration works.