Articles on: Modules

Shematix – What is this module and when do I need it?

Shematix (Planning & Concept) — Basics

Shematix is where everything starts. Before we build, automate, install, or optimize anything, we sit down with you and turn your idea into a clear, realistic plan—technically and organizationally.

The goal is simple: remove uncertainty early, so implementation later is fast, clean, and predictable.

If you want the official module context: see our Services overview and the Shematix module rules in our GTC.

1) What is Shematix?

Shematix is our concept and planning phase before actual implementation. It includes (depending on your project):

Current-state analysis (what exists today, what’s broken, what’s missing)
Feasibility checks (what is technically/organizationally possible and what’s risky)
Goal definition (what “done” means, measurable outcomes)
Requirements engineering (must-haves vs. nice-to-haves, constraints, dependencies)
Resource and time planning (budget/timeframe/roles/tools)

Think of it as your project’s blueprint: not vague slides, but a structured concept you can actually execute—either with us (via the next module) or, in some cases, externally (see rights/usage notes below).

2) What you get at the end (deliverables)

The output of Shematix is a detailed, structured concept / planning document (“Shematix concept”), usually delivered digitally (typically as a PDF).

Depending on the project, that concept can look like:

a technical specification (scope, modules, requirements, acceptance criteria)
a system sketch / architecture overview (components, interfaces, data flows, responsibilities)
a digital wireframe or structured UX outline (when it’s a product/app/system)
a process blueprint (workflows, automations, roles, handoffs, failure cases)

What it always includes in spirit:

Discovery → Blueprinting → Roadmap → Output (our standard Shematix flow)
a plan that breaks your project into functional units, defines measurable goals, and maps the path from idea to execution.

3) What we need from you (inputs)

Shematix is collaborative. The more precise your inputs, the cleaner the concept. The specifics (number of meetings/workshops, comms channels, formats, etc.) are defined via an individual project briefing / questionnaire and become part of the agreement.

What we typically ask for:

A) Goal & context

What are you trying to achieve—and why now?
What does “success” look like (KPIs, time savings, error reduction, rollout target, etc.)?

B) Current system / environment

What’s already in place (software stack, devices, network, tools, workflows)?
Known pain points, incidents, bottlenecks, recurring manual work.

C) Scope & constraints

Must-haves vs. nice-to-haves
Compliance/security requirements (if relevant)
Budget/time constraints, internal deadlines, team availability.

D) Access & materials (only if needed)

If the concept requires looking into existing systems, we may request limited access, screenshots, exports, or documentation—always aligned with confidentiality and data protection.

Our privacy policy explains how we handle data and what happens when you use forms/chat on our site.

4) What kinds of projects Shematix is for (digital + physical)

Shematix is designed for both digital and physical projects—anything where “just start building” would be expensive chaos.

Typical fits:

Digital systems: software tools, integrations, automations, internal platforms, workflows.
Physical/technical setups: devices, installations, network setups, system rollouts—especially when digital + physical touch each other.
Hybrid projects: “we need a system + a real-world setup + a clean operating process.”

In Shematix we plan processes, interfaces, architecture and implementation steps—whether digital or physical—and then build a roadmap that specifies tools, components, skills, time, and budget realistically.

Practical notes (good to know before you start)

These points aren’t “extra”—they prevent misunderstandings later:

Delivery & workshops: Usually digital (PDF). Workshops/presentations can be remote (video conference) or on-site, depending on agreement.
Decision window: After delivery, you typically have 4 weeks to decide whether implementation should be done by VICRONIX or (if contractually allowed) a third party. If no response is received, the concept is deemed accepted.
Validity: The concept remains technically/economically valid for 4 weeks after delivery. After that, we may need to adjust details (prices/timelines/resources) based on reality at that time.
Nature of service: Shematix is planning/consulting. We don’t promise “guaranteed business outcomes” inside the concept itself—implementation results depend on execution and real-world constraints.
Rights & usage: The concept remains our property until paid in full; after full payment you get a simple, non-transferable right of use. Third-party implementation is only permitted with prior written consent, unless explicitly agreed otherwise.
Confidentiality & data protection: Both sides treat shared information as confidential; privacy policy applies.

If anything above doesn’t match how you want Shematix positioned (scope, tone, or what you want to allow for third-party implementation), tell me what to change and I’ll adjust the article accordingly.

Updated on: 06/01/2026

Was this article helpful?

Thank you!