Data model
Off-the-shelf software often does not fit because its data model describes a way of working that is similar to yours, but not the same. Every difference then ends up in a custom field or a spreadsheet on the side. In nexxcite, you build your own data model in the editor. If you wish, the AI produces a first draft.
The foundation
The difference
Incident, contract or work order: everything follows the same schema and is adapted with custom fields.
A contract has a term, a notice period and amendments, as well as relationships to supplier, cost centre and assets.
The basics
A record type describes a business object: an incident, a contract, an asset, a purchase request, a person. You define its fields and describe its lifecycle.
In ticket-based systems, everything is a ticket with different fields. In nexxcite, a contract has its own structure, with a term, a notice period, amendments and relationships to the supplier, the cost centre and the assets it covers.
You add new fields and record types in the editor. If you wish, the AI produces a draft for you to review. There is no need to adjust the database by hand, and no maintenance window to book.
Create once
A new field is available everywhere at once
In forms, lists, reports, flows, permission rules and for the AI assistant. You do not need to declare it in several places.
The biggest difference
In many tools, a link is just a field holding an ID. In nexxcite, it is a definition with its own properties. That determines what reports, permissions and flows can do later on.
It describes how two record types connect, in which direction, with what cardinality and under which conditions.
Because the platform knows the connections, reports, permissions and automation work across several record types.
Optional: with AI
"We manage supplier contracts with a term, notice period and amendments. Each contract belongs to a cost centre and covers one or more assets."
Record types, fields, pick lists and relationships are collected in a draft where you can see each change on its own. Nothing is published yet.
In the editor or with another request: rename a field, make something required, filter a relationship.
From now on, the model is available in forms, lists, reports and flows. If something is not right, you can return to the previous state.
In production
Because changes are easy, it is tempting to start without a plan. A well-considered model at the start saves time later. We support you with this on your first process.
For bulk data from measurements, logs or sensors, a specialised system is the better choice. nexxcite can connect to it and use its results, but it is not a time-series store.
FAQ
Yes. Excel and CSV files can be processed in flows, including line by line. Data from other systems can be brought in through the interface or by fetching it directly from those systems.
It is kept. Model changes take effect immediately, without rebuilding the database or a maintenance window.
Large data sets are handled with indexes and paged queries. For bulk data from measurements or sensors, a specialised system is the better choice. nexxcite can connect to it.
For reading, yes, as the database structure is documented. Writing goes through the interface so that rules and checks apply.
Live demo
It usually takes about twenty minutes to see whether the structure holds. Feel free to bring the spreadsheet you work with today.