Connect the sources
Capture the order by upload or manual entry. Assign the components actually installed, matching manufacturer documents and references you are authorised to use.
HEEP Loop · For pump and fire protection system manufacturers
From your sources
to the manual at the equipment.
Connect order data, datasheets and your company knowledge in one workflow. Review technical details, approve a manual and deliver it through a QR code. Knowledge explicitly cleared for reuse helps with the next order.
Operating manuals and CE evidence in one connected workflow.
Everything in one order.
Manufacturer documentsconnect
VdS · NFPA · DINapply
Version & approvaltrace
A value needs a source.
Datasheet + page reference
or clearly flagged: [WERT FEHLT]
Approved manual → QR at the equipment
Values with sourcesControlled knowledge reuseDocumented expert reviewQR access at the equipment
How your documents become an approved version.
Develop the manual
Edit chapters and text blocks with or without AI. Add CE evidence and check technical details against the sources.
Review and deliver
A named reviewer checks the document, makes corrections or returns feedback. Following expert approval, you explicitly publish the version as a PDF and through the equipment link.
Check sources and reuse approved knowledge.
Technical values need sources.
Pressure, torque and temperature belong to a specific component. Loop links technical details to matching sources and flags missing values. Your reviewer checks the value, unit and source reference.
Your knowledge helps with the next order.
You explicitly clear suitable wording and house style for reuse within the same company. Loop checks provenance and all original rights, including content reused again. Technical values still need matching sources for the new equipment.
Three specialised review paths.
VdS, NFPA and DIN have dedicated specialists for the equipment and task. They support review questions and use standards excerpts cleared for processing. Your experts check the edition, applicability and results. How Loop handles standards.
Approval and delivery
Keep the right manual accessible at the equipment.
The equipment link opens the latest approved manual. A version link identifies a specific PDF. This lets you deliver current information and refer to earlier editions precisely.
A QR code to the current manual.
Operators can open the latest approved manual without signing in. Before publication, you review which content will be public. Individual PDF versions can be linked directly.
Trace approvals and company details.
Version history, reviewer and approval time identify the document state. Your logo, contact and service details belong in your manual; company details are saved with the approved version.
Verify a PDF version independently.
OpenTimestamps links the file fingerprint to a Bitcoin timestamp proof. You can retrieve and upgrade the proof, then check its anchoring. A completed proof establishes the prior existence of that file version.
Choose data processing, AI and deployment for your company.
Provider selection, your own AI keys and an isolated workflow are available in the software. Models and deployment mode are configured and checked for your installation and documents. A turnkey customer installation package is still pending.
Set up your deployment together.
Your own server, cloud and domain form part of the agreed deployment model. Setup, updates, backups and support access are scoped and accepted individually. Sensitive documents can be handled in an isolated workflow with local AI or human review.
Select AI by task.
Assign suitable models to different tasks and disable external tasks selectively. Anthropic and local Ollama models are connected. The prepared OpenAI integration still requires a live connection test and activation.
Direct contracts. Clear costs.
You pay your AI providers directly. HEEP does not resell tokens, add a token markup or impose extra token quotas. Provider limits and your own budgets still apply.
More tasks in the same workflow.
Connect the CE file and operating manual.
Record the legal framework, standards references, risks, protective measures and evidence with the order. The technical file and declaration remain linked to documented review states. Responsible experts provide the assessments and verified safety evidence.
Keep translations linked to the original.
Develop a translation draft with a glossary and expert review. An approved language version refers to its original version. Changes to the original make the need for another review visible.
Record maintenance by your own employees.
Your team records the date, task and details for each asset in the internal maintenance log. Corrections preserve the original entry. When needed, link the approved manual that applied at the time. External technician access and spare-parts orders are outside the current scope.
How the knowledge loop closes.
A fictional example: your reviewer improves a pump system’s installation instructions. Once explicitly cleared for reuse, that wording can be suggested for the next suitable order. Loop preserves its provenance; different components and their technical values are checked again.
Your experts make the technical decisions.
AI supports editorial work; the responsible people assess technical accuracy and conformity. Missing sources and review findings are resolved professionally before approval. Timestamp proofs document a file version and do not replace that review.
Your next step
Evaluate Loop with a defined product family.
For the pilot, bring order data, component documents and a technical contact. Together we agree the scope, price and review process before starting. The example produces an edited manual, an overview of missing sources and the agreed approval workflow. We compare editing time and rework with your existing process.