Quality
Sees recurrences before they become a case, with the evidence already linked and dated.
4Vision Platform · Method as a Service
Doing everything right is not enough. You have to be able to prove it.
For manufacturers of machinery, plants, components and connected products. For people working in Quality and Technical Service.
4Vision is intelligence on products in service. It links the structured data coming from connected machines (measurements, alarms, fault codes) with what people observe and write: diagnoses, service reports, field reports, conversations with customers. The result is a single reading that improves products, makes service more effective and, when needed, documents when you knew and what you did.
When you knew, in operational terms: when the information entered the organisation's body of information, through the channel and according to the criteria the company has defined.
It integrates and enhances. It works with the systems the company already uses and makes more of their data; where they are missing, it performs many of their functions.
Modular and sustainable. You start with one module and the archive you already have; each further step is added when it brings value.
Sectors
Industrial machineryAutomationMobility & componentsConnected equipmentEnergy equipmentLeisure marine
Where it operates
Where the product meets the field.
4Vision works in the processes that accompany the product after the sale and brings the functions responsible for them to the same table, starting with Quality and Technical Service.
From the field to the factory
- Field reports, from any channel: machine data, e-mail, phone, messages, tickets.
- Diagnosis and troubleshooting, with the history of similar cases at hand.
- Recurrences and corrective actions, from the first signal to closure.
- Lessons learned fed back to design, production and suppliers.
On the installed base
- Interventions on the installed base: updates, replacements, campaigns.
- Service contracts: maintenance, remote support, guaranteed availability.
- Spare parts and service network, where and when they are needed.
- Evidence of conduct, when someone asks for it.
The functions involved
Technical Service
Faster diagnoses, similar cases available, fewer repeated questions to the customer.
After-sales and spare parts
Knows where, when and with which parts to intervene on the installed base.
Design
Receives structured feedback from the field for the next versions of the product.
Management
Sees exposure, service quality and its value in a single picture.
The starting point
The signal is already there. It needs to be connected.
Three scenes every manufacturer will recognise. Information is not missing: it is spread across machines, people and different channels, waiting to be read together.
Four signals for the same fault
A technician writes "flickering" in a service report. A customer mentions a "hum" on the phone. Another sends a video and says "it vibrates". Meanwhile the machines log the same alarm code. Four signals, four channels: the component is the same.
The data and the diagnosis
The machine tells you what happened; the technician tells you why. Data without interpretation remains a number, a diagnosis without data remains an opinion. Read together, they become knowledge, ready for the next repair and the next version of the product.
The service contract
The customer buys availability, not just a machine. Guaranteeing it takes targeted maintenance, spare parts in the right place and first-time fixes: everything depends on how well the manufacturer knows the actual behaviour of the product in service.
The same question, in every sector
The same malfunction appears on drive systems, electrical systems or electronic components installed on different models. Is it a problem with the product, the component, the use or the operating conditions? This applies to a machine tool as much as to a leisure boat: the answer lies in reading together signals that today live apart.
How it works
Machine data and people's words, in a single reading.
4Vision is an intelligence system for products in service. It puts the structured data from connected machines on the same level as people's interpretations: diagnoses, written records, service reports, customer reports. It recognises when separate episodes belong to the same phenomenon, correlates them and keeps the full path that led to that reading.
Four modules, four questions
The "4" in the name stands for the four questions the system answers. The Platform is the common foundation: documented interfaces to the company's systems, users and permissions, activity log, notifications.
What is coming in from the field?
DeTech
Listening and correlation. It brings in machine data and alarms, e-mail, service reports, messages, tickets and historical archives. It recognises what a report is about, even in workshop jargon, and links it to the machine data, to components, batches and customers, and to other reports describing the same phenomenon in different words. Each unit receives an identifier and an integrity fingerprint on entry; the original is retained.
First releaseWhen did you know?
VeriPass
Attestation. VeriPass builds and maintains the evidence file with verifiable integrity and sequence. When a qualified time attestation is needed for third parties, the fingerprint of the data is submitted to a qualified trust service provider listed in the EU Trusted Lists: only the fingerprint leaves for the provider. The evidence file can be verified by a third party without access to the system. Time stamping is a deterministic process, separate from the analysis functions.
Qualified electronic time stamp available on requestHow exposed are you?
Risk Radar
Risk assessment. It measures how widespread a phenomenon is and how much it weighs, compares it with the thresholds the company has set for each product family and separates the signal from operational noise and external causes. Every assessment carries its own rationale, readable by people who did not build the system. It guides verification; it does not determine the cause.
First releaseHow do you coordinate the response?
Campaign Engine
Coordination. When action is needed on an installed base, it simulates the possible scenarios (repair, replacement, update), estimates their costs on real data, coordinates the service network and spare parts, tracks closure for each unit and helps allocate costs to the responsible parties.
On the roadmapGovernance
The system proposes, people decide.
Rules, written and versioned by the company, set out in a reproducible way how each case is handled. An authorised person validates or corrects, giving reasons. The artificial intelligence components read and propose, citing the evidence they rely on; in uncertain cases they ask a person. The causal link is established by people.
Observation, proposal, human validation. Then, on defined and validated case types, selective automation.
Decisions on relevant cases remain with people. The rules remain the company's, readable and exportable at any time; every judgement can be reviewed against the rules in force when it was made.
What it improves
Better products, better service, demonstrable conduct.
The value of 4Vision is measured first of all in the continuous improvement of product and service. The documentation of conduct comes from the same work, with no additional activity.
The product
Recurrences and cross-cutting cases. The same component across different customers and models, recognised as a single phenomenon. Earlier detection. Crossing of the configured thresholds emerges even when signals arrive through different channels and at different times. Structured lessons learned fed back to design and suppliers.
The service
Faster diagnoses, with similar cases and machine data at hand. Knowledge that builds up: validated readings join the shared body of knowledge and remain useful to those who come next. Signal and noise: unusual operating conditions, special installations and new products read for what they are.
Servitization
Selling availability, performance and maintenance requires knowing the actual behaviour of the installed base. 4Vision correlates measured use with interventions and their outcomes: the basis for sustainable service contracts, targeted maintenance and spare parts where they are needed.
Conduct
The moment of entry of every piece of information is recorded, with its provenance. Actions and decisions keep their date and the version of the rules in force. Verifiable by a third party, exportable outside the system too: data, evidence and rules in open formats.
The trail that helps you improve is the same one that documents. "When did you know, and what did you do?" becomes an ordinary answer.
Quality and Service
A tool for Quality and Service.
Quality and Service look at the same product from two sides: the factory and the field. 4Vision gives both the same base of facts, linked and dated, and turns the handover of information into shared work.
| The need | For whom | What 4Vision offers |
|---|---|---|
| Timely, recognisable reports | Quality | The moment the information enters the designated channel is recorded, with its provenance, and the signal already arrives in a readable form. |
| Sound diagnoses with any technician | Quality and Service | The technician is asked to describe what they see; the system links the description to the machine data and to similar cases. |
| A common language between field and factory | Quality and Service | Different expressions for the same phenomenon converge on the same point: the variety of the network's language becomes information. |
| The network's problems as a whole | Service | Links between cases far apart in time and across different customers, which one person alone cannot see. |
| Prompt answers to requests from the field | Service | Every request has its date and status: whoever asks knows where it stands, whoever answers has the full picture. |
With a shared sequence that can be reconstructed, everyone documents what they did and when, and meeting time goes back to solutions.
4Vision Laboratory
We tested the method on the past.
One year of the technical service archive of a manufacturer of complex machinery, read with the 4Vision method. The closure documents were used to establish when each case was closed.
Case 1
269DAYS
between reconstructed threshold and documented closure
One component, many independent customers
Reports came from different customers, at different times, in different words. In the archive they were separate cases.
Case 2
174DAYS
between reconstructed threshold and documented closure
Several reports on the same day
Separate reports arriving on the same day from different customers, then silence. Read together, they told the story of a single phenomenon.
Case 3
264DAYS
between reconstructed threshold and documented closure
Five words, nine customers
Five different expressions for the same phenomenon, across nine customers. Recognising them as one thing changes the nature of the case: from one customer's problem to a cross-cutting defect.
first signal in the archive
threshold reconstructed with the company's criteria
documented closure of the case
axis: one year of archive
Retrospective reconstruction of three historical cases. The figure measures the interval between the crossing of the threshold reconstructed with the company's criteria and the documented closure of the case: it describes the past and is not a forecast. The lead time observed grows with the frequency of the phenomenon.
How it is adopted
Simple to start, modular, sustainable.
4Vision comes in where the company already works. It does not ask you to replace systems, buy infrastructure or change the way people report: it connects to existing channels through standard interfaces and starts from the archive you have.
Modular
You start with DeTech, on the existing archive and channels. VeriPass, Risk Radar and Campaign Engine are added when needed, and each module brings value on its own.
Value from the start
The first reading is done on your history: cases, recurrences and links already emerge during the start-up phase, without waiting for new data.
Proportionate investment
Delivered as a service, with a start-up fee and a subscription that grow with the modules activated. No system to replace, no infrastructure to buy: the investment stays in proportion to the benefits.
Master data and history
You start from what exists: customers, machines, families, components, report types and the historical archive. The history is imported and re-read with better criteria, producing observations dated today.
Listening on existing channels
The system connects to e-mail, tickets, company systems and machine data through documented interfaces. People who report keep doing so as before; in the first phase 4Vision observes and proposes.
Company rules and validation
Categories and handling rules are those the company chooses, written and versioned. An authorised person validates the cases that matter and clarifies the ambiguous start-up cases with the system.
Attestation and evidence file
The evidence file builds up from day one. When an attestation for third parties is needed, the qualified electronic time stamp is activated; items that meet the configured conditions can be attested immediately.
The next step
Let's talk about your case.
An hour on your archive says more than any presentation: we take a real case, with Quality and Service at the same table, and re-read it together. Write to us at info@defactorysrl.com.
The European context
Three sets of rules, one common need.
Three sets of European rules converge on one operational need: being able to reconstruct over time what information was available, which criteria were applied and what actions were taken.
From 11 September 2026, the Cyber Resilience Act makes applicable the obligations to report actively exploited vulnerabilities and severe incidents having an impact on the security of products with digital elements, with an early warning within 24 hours and a notification within 72 hours. The Product Liability Directive (EU) 2024/2853 applies to products placed on the market or put into service from 9 December 2026: it treats software as a product and provides for full compensation of damage, with no upper limit; for products with software, liability can extend to modifications and updates that remain under the manufacturer's control. The Machinery Regulation (EU) 2023/1230, applicable from 20 January 2027, strengthens the requirements on technical documentation, risk assessment, conformity and documented management of relevant modifications.
The same trail that improves products and service makes it possible to reconstruct, long after the event, what was available, with which criteria and what followed.
Safeguards
An original method, data kept safe.
The method underlying 4Vision is the subject of a patent application filed with the Italian Patent and Trademark Office (UIBM) on 27 April 2026 (no. 102026000011680), exclusively licensed to DE Factory S.r.l. under a registered and recorded licence: a guarantee of innovation and reliability for those who adopt it.
Integrity from entry
Every unit of information receives an identifier and a cryptographic fingerprint on acquisition. Archives are append-only: corrections are recorded as new events and the history remains readable.
Qualified attestation
When requested, the time stamp is applied by qualified trust service providers under the eIDAS Regulation, listed in the EU Trusted Lists, with a legal presumption as to the date, time and integrity of the linked data. The evidence file can be verified by third parties without access to the system.
Data and access
Architecture planned on infrastructure in an EU region with a provider holding the certifications required by the project (ISO/IEC 27001, 27017, 27018). Project requirements: encryption in transit and at rest, segregated and logged access, a data processing agreement under the GDPR, full export in open formats. Dedicated deployment configurable according to agreed requirements.
Software security
Project requirements for the first release: an inventory of components for every release, vulnerability scans, immutable logs, versioning of rules and configurations. Designed in line with NIS2 requirements and with the practices required by the Cyber Resilience Act.
Optional tool
Seven questions to get to know each other
Seven questions to understand where to start. It is not a test and not a required step: it is a way to open a conversation about your organisation. Answer, prepare the message and send it to us; we will write back.
Would you rather talk directly? Write to us at info@defactorysrl.com
Let's talk about your case
4Vision Select
A programme for the first manufacturers
A limited number of manufacturing companies join 4Vision with configuration assisted by the team that developed the method, early access to platform developments as they are released and integration with the systems already in use. No system to replace. Progressive integration with what is already in use.
- The method is tailored to the company's operational reality, with its own categories and rules.
- You start from the existing archive: the first reading is on your history, not on an example.
- Those who join now help set the priorities for the next releases.