Job orders
Service and supply jobs from request to closure, each with its device, parts, reports and money attached.
MOSAIC is not a general business suite with a maintenance module attached. Every screen below exists in the current release and is used daily by real teams. The operational screens are grouped first; the platform core that makes them one system follows.
Grouped the way work actually flows: a job enters, a device is diagnosed, parts move, reports are sealed, money is settled.
Service and supply jobs from request to closure, each with its device, parts, reports and money attached.
Customer requests become priced quotations with revisions, approvals and a printed sheet that matches the screen.
Confirmed work and supply, with proforma invoices issued before delivery where the customer needs them.
Invoices with their currency, payments and receipts recorded against them, and the balance always visible.
Every customer device with serial, ownership, actions, photos and status, grouped under the customer's systems.
Receipt and delivery reports, numbered and sealed electronically, with the scanned original attached.
The parts catalogue with suppliers, units, internal codes, and kits assembled from parts.
Multi-store stock moved only by sealed vouchers: receipt, issue, transfer, loan, return, scrap, shortage, count.
Parts reserved against a device and work order, or requested above stock, with an expiry and a release trail.
From internal request to supplier order, supplier invoice and receipt into stock.
Service contracts with their types, and operation plans that schedule recurring work.
Indicators defined once, planned per period, and reported for management review.
Designed approval paths, runs you can follow step by step, and a backlog of what waits on whom.
Tasks assigned to people, an inbox that moves work along, and notes attached where they belong.
Controlled sharing of records between two organizations, requested by one and approved by both.
Who changed what and when, with the value before and after; and a coverage view of every permission.
Every screen with the name and icon you'll work with — each connected to what's around it, not an island.
A full people register with five built-in lenses: customers, suppliers, logistics, employees, and technicians.
The platform's tenants, each one's data isolated from the rest.
Define the roles granted to people, governing what they see and do.
A permission tree of sections, objects, and verbs — existence and effect controlled separately.
Your own profile details, photo, and password.
Sign-in permission, kept separate from a person's existence and their effect.
The countries reference — owned by the platform, shared read-only across every tenant.
Platform languages and the writing direction of each.
Currency definitions and symbols in both languages, calculated on a dollar base.
Rates fetched from an external provider at one click, or entered by hand.
The payment methods approved for your center's transactions.
The approved classification of contracts.
How organizations are classified — customer, supplier, carrier, and others.
The approved units of quantity, weight, and volume.
Shipping ports, each linked to its country.
One unified table, seen through customer, supplier, and carrier lenses — not a table per type.
Addresses for organizations and their branches, including the invoicing address.
Warehouse classification, linked to their locations.
The geographic locations that stores and organizations belong to.
The platform's entry point: each user picks their own cards and orders them by drag and drop.
Three inheriting layers — platform, then tenant, then user; each overrides the one above or inherits it.
A card's name, icon from a gallery, destination from the app's own routes, and its two counters — all without a line of code.
A stored filter with a base, two conditions, and twenty-eight operators — built from dropdowns with a live preview.
Navigation sections — name, icon, and order are rows in the database, not code to redeploy.
Many small tiles making one picture
The names, icons and order of these screens are data in the platform, not code, so your administrator shapes the workspace without a developer.
Most systems ship a fixed idea of how a service center works and ask you to adapt. MOSAIC ships the mechanisms and leaves the design to you: processes, approval paths, asset structure, cost rules and pricing policies are all configuration, changed by your administrator without a developer.
Job types, statuses, document numbering and the fields on each screen are defined by your organization, not by us. Two centers can run very different operations on the same platform.
Who approves a quotation above a threshold, who releases a part, who may seal a report: each path is designed as steps and conditions, and every run is followed step by step.
Devices sit under customers' systems and sites in the hierarchy you choose, with the attributes you need per device type, and lenses that give each role its own view of the same registry.
Parts, labour, logistics and contract allowances are costed by rules you set per job type or customer, so margin is visible before a quotation leaves the center.
List prices, customer-specific terms, intermediary rates and warranty billing are policies in the platform, applied automatically and changed in one place when the market changes.
Your data is yours: export at any time, read access to the platform's interface on Professional and full access on Enterprise, and sharing of records with partner organizations under both parties' approval.
A free workspace comes pre-loaded with sample devices, parts and reports, and your administrator can replace them with yours in an afternoon.