Skip to Content
  • Solutions

    Your challenge

    By challenge

    Start from the problem you have today.

    Solving document chaosFind every document by what it isRemoving manual workLet the system file and forwardEliminating audit stressEvery file audit-ready, every dayPreparing data for AIThe right version for AIAI across all your systemsOne governed knowledge layer

    Your sector

    By sector

    Blueprints for regulated sectors where documents carry liability.

    Read client cases →
    Accountancy & audit firmsPermanent files to e-signatureFinancial servicesKYC, contracts and client filesLegalMatters and deadlinesConstruction & engineeringDocument control and transmittalsManufacturingSpecs, quality and supplier filesPublic sectorRecords and compliance

    Your process

    By process

    One process, end to end.

    See the process library →
    Contract managementFrom first draft to renewalQuality management (QHSE)ISO, procedures and auditsPersonnel files (HR)Right access, right retention

    Free advice call

    Not sure where to start?

    Thirty minutes with a process architect. No obligation.

    Audit scoreHow audit-ready are you?Contract risk scoreHow big is your risk?

    Book a free advice call

  • Platforms
    M-Files

    One search bar for all your business information, with AI on your own documents.

    Why M-Files →
    M-Files AIAI on your own documentsCompare editionsWhich edition fits youM-Files HubshareSecure client portalM-Files MentNo-code document generationCompare M-FilesAgainst SharePoint, DocuWare, OpenText and more
    SharePoint +MacroView

    Mail and documents in SharePoint, managed as real case files.

    MacroView overview →
    SharePoint with SoftAdviceMicrosoft 365 as your document platformFiling from OutlookE-mail in the right file, in one moveAutomatic e-mail filingRules that file by themselvesAll MacroView featuresEvery feature on one pageMacroView or M-Files?An honest comparison
    Mindbreeze

    AI answers across all your systems, from trusted sources.

    Mindbreeze overview →
    Use casesSeven scenarios to start fromMindbreeze Insight WorkplaceAI agents and governed workflowsAgentic AIThe right context for every agentDeployment and securityCloud, hybrid or on premises
    dox42

    Automate every document, from any system.

    dox42 overview →
    dox42 with M-FilesGenerate straight into M-FilesPlan a dox42 demoSee it on your documentsAll integrationsERP, CRM, e-signing and more

    See it live.

    One hour, online, on your real use case.

    Plan an AI readiness talkFor AI across all your systemsMicrosoft 365M-Files and Microsoft, together

    Plan a demo

  • Approach

    How we work

    Process first. Technology second.

    Five steps from analysis to a working system, with one team end to end.

    See our approach →
    1. DiscoveryHalf-day session, advice within 10 days2. Discovery & designMap your processes and information3. Implementation & configurationBuild and configure your platform4. Integrations & customisationConnect and tailor to your systems5. Success servicesAdoption, support and growth

    AI governance

    AI you can defend

    Policies, controls and oversight for AI on your data.

    Governance framework →
    Shadow AI under controlWhat it is and how to contain itIs your data ready for Copilot?Check it before you switch it on

    Price request

    What does it cost?

    Transparent pricing per platform and per service.

    Price calculatorEstimate your licence costROI calculatorCalculate your savings

    Request a price

  • Knowledge

    Learn

    Knowledge Hub

    Learning, proof and what changes.

    Open the Knowledge Hub →
    BlogLong reads on information architectureWebinarsLearn it in an hourAnalyst reportsGartner and Forrester, no paywallUpdatesProduct news, translated into impact

    Regulation

    What the rules mean

    What each rule means for your documents.

    Regulation overview →
    PeppolMandatory in Belgium since 2026NIS2Cybersecurity duties for the mid-marketeIDAS 2The EU digital identity walletEU AI ActWhich obligations apply whenRetention periodsBelgium, the Netherlands and Luxembourg

    Free tools

    Answers in minutes

    Quick checks you can run today.

    SharePoint or M-Files?Take the 8-question quizRetention period lookupHow long to keep what

    AI Readiness Scan

    Is your data ready for AI?

    7 questions, your score out of 100 and concrete next steps.

    NewsletterOnce a month, in your language

    Start the scan

  • Cases
  • Who we are
  • Client zone
SoftAdvice - Proces & information architects
  • Plan a demo
  • Nederlands Nederlands (BE) English (US) Français (BE)
SoftAdvice - Proces & information architects
      • Solutions
      • Platforms
      • Approach
      • Knowledge
      • Cases
      • Who we are
      • Client zone
    • Nederlands Nederlands (BE) English (US) Français (BE)
    • Plan a demo

    Home/Mindbreeze/Use cases/Technical knowledge

    Process library · Technical services

    Technical knowledge for service and engineering teams, across your systems

    A machine at a customer site shows an error. The manual is in the document system, earlier interventions in the service tool, the parts list in the ERP and the fix that worked last time in someone’s mailbox. The engineer gets one answer with links to each, and decides on the fix.

    Discuss this use case See an example

    M-Files Solution Partner100+ implementations since 2010Dutch, French, English
    Blueprint
    BP-17
    Sector
    Technical services
    Process
    Knowledge and answers
    Starts with
    Service question
    Result
    Verified solution
    Building blocks
    Mindbreeze · DMS · ERP
    Governance
    Audit trail · Permissions
    Discuss this processDownload PDF
    The flow at a glance
    runs by itself
    a person acts
    1
    Ask about the machine
    Service engineer
    →
    2
    Answer with sources
    Automatic
    →
    3
    Verify and fix
    Service engineer
    →
    4
    Record the solution
    Service engineer
    →
    ✓
    Verified solution
    In shortThe situationFlowExampleMeasuringFAQ

    In short

    In this proposed scenario, service engineers, support staff and engineers at a machine builder or industrial company ask a technical question and get one answer drawn from specifications and manuals, service history, parts and product data and earlier correspondence. Every statement links to its source, and each person sees only what they are allowed to see. The engineer checks the answer and decides on the fix. SoftAdvice sets this up with Mindbreeze on top of the systems the company already uses.

    The moment

    The answer exists, in five different places

    A technician stands at a broken machine. The fix exists, somewhere in the service history. They call a colleague.

    Service and engineering teams work with knowledge that grows with every machine sold: specifications, manuals, change notes, service reports, parts lists and the experience of a few senior colleagues. Each sits in its own system.

    So a technical question means searching system by system, or calling the one expert who remembers. That costs time on site, leads to repeat visits and makes the team dependent on a few people.

    • Specifications and manuals
    • Service history per machine
    • Parts and product data in the ERP
    • Earlier mails with customers and suppliers
    What changes for the team

    From calling the expert to checking one answer

    The engineer keeps the decision on the fix. What changes is how fast the right facts reach them.

    Today

    • Searching manuals, tickets and the ERP apart
    • Unsure which revision applies
    • Knowledge in the heads of a few experts
    • The same problem solved twice

    In this scenario

    • One question, one answer with sources
    • The revision for this machine first
    • Earlier fixes found, experts named
    • New fixes findable for the next case
    The flow

    From service question to a verified fix

    Mindbreeze does the finding and assembling. The engineer checks and decides.

    Ask about the machine

    The engineer asks in their own words, starting from the machine, the serial number or the error.

    Service engineer

    Answer with sources

    Mindbreeze brings together the relevant manual section, earlier service reports and parts data the engineer may see, with a link to each source.

    Automatic

    Verify and fix

    The engineer checks the sources, decides on the fix and contacts the named expert only when needed.

    Service engineer

    Record the solution

    The service report is recorded in the service system as usual, so the next question about this error finds it.

    Service engineer
    Example

    One question, the sources behind it

    An illustrative question from a service call on a packaging machine. The answer links the manual section for this revision, an earlier service report with the same error and the part that solved it.

    • Only documents the engineer is allowed to open
    • The revision that matches this machine
    • Every statement traceable to a source
    Service assistant
    Error E-214 on the sealing unit of this machine: what is known, and which part fixed it before?
    The manual for this revision links E-214 to the temperature sensor of the sealing unit. A service report from last spring describes the same error on a machine of this type; replacing the sensor solved it. The part is in stock in the ERP.
    ManualService reportERP

    Illustrative example

    Control

    The engineer decides, the sources stay visible

    An answer points the engineer to the right documents; the fix remains a professional decision. Because every statement links to its source, it is clear which manual, report or part list the answer used.

    Mindbreeze applies the permissions of each source system, so confidential engineering documents or customer data stay with the people allowed to see them. If access in a source is too broad today, that is fixed in the source; we check it before the start.

    • Answers support, engineers decide
    • Permissions of each source respected
    • Sources linked in every answer
    • Access checked before the start
    Measuring success

    What we measure on a first use case

    We agree the baseline with your team before the start, so the result is measured on your own questions.

    Time to the right document

    How long it takes to find the relevant manual section, report or part, before and after.

    Answer usefulness

    Engineers rate answers against an agreed set of real service questions.

    Expert interruptions

    How often senior colleagues are still needed for questions the sources can answer.

    Permission tests

    Test users confirm that nobody sees what they may not open.

    Prerequisites and limits

    What this scenario needs, and what it does not do

    The answer is only as good as the sources. Before the start we agree which documents are the valid revision, which systems are connected and which team owns the first use case. Connectors, configuration and licensing are confirmed per system.

    This is a proposed scenario. It is based on patterns in customer cases that Mindbreeze has published for manufacturing, service and maintenance, described here without names or figures. It is not a SoftAdvice implementation reference.

    • Agreed valid revisions
    • Connectors confirmed per system
    • No automatic repair decisions
    • One team, one use case first

    Questions about this use case

    Does the AI decide on the repair?

    No. The answer helps the engineer find the right documents and earlier fixes faster. The engineer checks the sources and decides, as today.

    Which systems can be connected?

    Typically the document system, the service or ticket tool, the ERP and mail. Which systems can be connected, and how, is confirmed per system before the start.

    Do we need to move our documents?

    No. The documents stay in the systems where they are today. Mindbreeze connects to them; which systems can be connected is confirmed per system before the start.

    Can customers or partners use it too?

    That is a possible next step, for example in a service portal. We start with the internal team, so sources and permissions are proven first.

    How do we start?

    With a conversation about one use case: the team, the typical questions and the systems involved. From there we propose a scoped first step.

    Related

    All use casesClaims and customer serviceDeployment and securityEngineeringProcess library
    Related blueprints

    More from the process library

    All blueprints
    Technical services
    BP-12
    Invoice
    Paid

    From invoice to paid

    An invoice has been open for weeks. Nobody knows if a reminder went out.
    Every sales invoice linked to its project, reminded when late and closed when the accounting sees the payment.
    M-Files
    Technical services
    BP-13
    Site visit
    Approved report

    From site visit to approved report

    The site visit report is done. Technical check, proofreading and translation still to come. It has sat on a desk for a week.
    Every report through technical check, language check and translation before approval, recorded with the project.
    Audit trail · Version control
    M-Files
    Insurance and financial services
    BP-16
    Customer question
    Answer with sources

    Claims and customer service across systems

    A customer calls about their claim. The handler opens four systems while the customer waits.
    Policy terms, claim file and correspondence brought together in one answer with sources; the handler verifies and decides.
    Version control · Permissions
    Mindbreeze
    DMS
    CRM

    Which technical questions take your team the longest today?

    Tell us about the team, the questions and the systems involved. We come back with a proposal for a scoped first step.

    Discuss this use case

    SoftAdvice
    Process library
    Blueprint BP-17
    Technical services
    Knowledge and answers
    Technical knowledge for service and engineering
    The moment
    A technician stands at a broken machine. The fix exists, somewhere in the service history. They call a colleague.
    Specifications, service history and parts data found in one place, so the engineer reaches a verified fix sooner.
    The flow
    1. 1
      Ask about the machine
      Service engineer
    2. 2
      Answer with sources
      Automatic
    3. 3
      Verify and fix
      Service engineer
    4. 4
      Record the solution
      Service engineer
    Blueprint BP-17
    Sector
    Technical services
    Process
    Knowledge and answers
    Starts with
    Service question
    Result
    Verified solution
    Building blocks
    Mindbreeze · DMS · ERP
    Audit trail
    Permissions
    Recognise this moment?
    Tell us about your own process. We look at it with you, without obligation.
    Discuss this processsoftadvice.eu/plan-a-callRead the full blueprintsoftadvice.eu/mindbreeze/use-cases/technical-knowledge
    Blueprint from the SoftAdvice process library. Real process, described anonymously.
    Only M-Files Solution Partner in the BeNeLux · 100+ implementations since 2010
    Discuss this use case

    SoftAdvice

    Process & information architects

    Partner of M-Files since 2010, and of MacroView and Mindbreeze, in Belgium, the Netherlands and Luxembourg.

    Otterstraat 199
    2300 Turnhout, Belgium
    info@softadvice.eu
    Belgium +32 2 895 06 00
    Netherlands +31 79 799 61 40
    Luxembourg +352 27 86 46 55

    LinkedIn

    Platforms

    • M-Files
    • SharePoint + MacroView
    • Mindbreeze

    Integrations

    • dox42
    • Penneo
    • Microsoft 365
    • All integrations

    Services

    • Discovery
    • Process consulting
    • Implementation
    • Integrations
    • Success services
    • AI governance

    Company

    • Who we are
    • Knowledge Hub
    • Newsletter
    • Contact

    Partners

    M-Files Solution PartnerSolution PartnerMacroViewMindbreezedox42

    Newsletter

    Once a month, in your language. Unsubscribe at any time.

    Subscribe

    Thank you. You will receive the next edition in your mailbox.

    © 2026 SoftAdvice BV. All rights reserved.

    PrivacyCookiesTerms

    We use cookies to provide you a better user experience on this website. Cookie Policy

    Only essentials I agree