Productive in 8 weeks, without a large-scale project.

The target timeframe to productive use of the first use case is eight weeks. For straightforward starting conditions, six weeks are possible; for integration into leading systems or complex use cases, 12–14 weeks.

Yes, and it is often the better time to start. Operations1 does not draw on ERP resources because the initial setup works without integration. Processes that are cleanly digitized before the ERP go-live are significantly easier to connect later than paper and PDF-based content. We define the concrete starting scope in the kickoff.

Five phases over eight weeks: kickoff with goal-setting and definition of the first use case, platform setup including users, permissions, and plant structure, creation of the first documents followed by a live test on the shopfloor, refinement based on user feedback, and a closing review with go-live. You will find the detailed process further up on this page.

The rhythm is a weekly standing meeting with your core team and your Customer Success Manager. In addition, there are fixed milestones: kickoff, an interim review after the live test, and the closing review. The project sponsor should be present at the kickoff, interim review, and closing review.

The majority runs virtually, which is sufficient for setup, training, and reviews. On-site is useful when the process itself needs to be captured, for example during a complex as-is analysis. At Zünd Systemtechnik, the Operations1 team captured the as-is processes on-site and developed the to-be process together with the specialist department. What your situation requires will be decided in the kickoff.

As many as necessary, as few as possible. There is no fixed number, as it depends on the scope of the first use case. What matters most is the selection: key users should have solid process expertise and be respected within their area, because they will maintain the content themselves after go-live and drive adoption on the shopfloor. In addition, a project sponsor is needed to take ownership of scope and completion. Who specifically to assign will be determined in the kickoff based on the starting scope.

Plan for 2 to 5 working days per key user, spread across the eight weeks. That corresponds to roughly 15 to 40 hours. For a key user taking on all tasks, the effort breaks down as follows:

• Around 10 hours building and revising documents, using the AI Document Automator

• Around 8 hours preparing for and attending the weekly standing meetings

• Around 10 hours of testing on the shopfloor

• Around 10 hours of internal alignment and change management in manufacturing

In practice, rarely does one person take on all four areas. Some key users work intensively on the documents, others not at all and instead focus on building buy-in in manufacturing. That is where the range comes from. How large the document share turns out to be depends primarily on your existing work instructions: how complex they are, how consistent their format is, and how up to date they are.

This breakdown refers to a typical starting scope of around 20 documents in a clearly defined manufacturing area, such as the pre-assembly of one product family. The project sponsor is involved at key milestones only: kickoff, interim review, and closing review. Your IT team has no further involvement after single sign-on is set up. A reliable estimate for your specific situation will be developed in the kickoff.

Small enough to go fully live within eight weeks, and relevant enough to matter internally. A proven approach is to focus on one area, one machine, or one process. Quantum Systems started with assembly instructions, ABB Motion with quality inspections. A scope that is too broad extends the timeline without increasing the value of the outcome.

No, subject-matter responsibility stays with you, and that is intentional: your key users need to be able to develop the content independently after go-live. We handle setup and configuration, training, AI-supported migration of your existing documents via the AI Document Automator, and guidance during the creation of the first documents.

At the start, typically the setup of single sign-on. Integrations with ERP or MES systems are possible but are not a prerequisite for the first use case.

For the first use case, they are selectively migrated and structured in a modular format, not copied one-to-one. Many companies use this moment to sharpen content from a subject-matter perspective.

No. Instructions are created by your subject-matter experts, without any programming.

Intuitive usability and early involvement of end users support adoption. Feedback from the live test flows directly into the further development of the content.

Operations1 documents process execution, not individual performance. Reports can be configured so that no individual performance evaluation is possible. Experience shows that early involvement of the works council at the kickoff is the faster path. We provide the necessary documentation for this.

Your specialist departments. After onboarding, your key users are able to create, edit, and approve documents independently. Thanks to modular documents, a change to one module automatically takes effect in all instructions that use it.

All content, versions, and approvals are stored centrally in the platform, not with any individual. New key users can onboard themselves using the existing documents. That is precisely the core of the knowledge retention use case.

Once implementation and onboarding are complete, the Customer Success team takes over ongoing support.

No. One plant, one process, then scale. The first use case creates the structure and content that additional sites can build on. Moving to the second plant is, in practice, significantly faster than the initial setup.