An ERP project that stays plannable.
Introducing publishing software is not a software purchase but a project – with dates, budgets and people who have to keep working while the changeover happens. We have accompanied such projects for 25 years: with a fixed process, clear roles and a project plan you can look into at any time.
Analyse first, then build – in verifiable steps.
ERP projects rarely fail on the technology. They fail because everyone involved waits too long for the first visible result and decisions get lost along the way. That is why we work in short, verifiable sections.
In cycles, not in one go
The build runs in sections of two to three weeks. At the end of each one there is a working system your key users can look at and judge – not a status report.
To the buildOne plan both sides can see
The project plan is not an internal document. What we see, you see too – at any time and without asking.
To the project planKey users instead of lecture training
From every department you name one person who works along early, tests and helps decide. These people carry the changeover inside the house later – that works better than any training on go-live day.
To the rolesMilestones that get signed off
What is not signed off does not count as done – not even for us. You release each phase before the next begins.
To the controlsNo date without analysis
In principle open.junixx is provisioned within a few days. How long your project takes, though, is decided by your processes, your legacy data and your interfaces. That is why an analysis comes first – and not a date nobody can keep.
To the design phaseOne house, one contact
Advice, design, migration, interfaces, training and support all come from us – as a systems house specialised in publishing. You do not coordinate three providers.
Arrange an initial consultationFrom the first consultation to regular operation.
Nine steps, each with a described result. At every point you see what happens next, what we need from you and how completion is measured.
- 01 Free of charge · up to 3 hours
Free initial consultation
Arrange an appointment through the contact form. We show you open.junixx live – not as a standard demo but along your questions – and tell you what is possible in your house and what is not.
Learn more- Live demonstration along your processes
- A first estimate of effort, sequence and risks
- Clarifying which existing systems stay and which are replaced
Result A sound assessment of whether and how to proceed.
- 02 1 to 4 weeks, depending on scope
Design and quotation
Depending on the effort involved, a detailed design phase is needed. In workshops we record your processes as they are today and describe how they should run in future. Only then does a quotation emerge that fits your publishing house.
Learn more- Process mapping per department: current state and target state
- Workshops on migration, interfaces and permissions
- Requirements prioritised: what must be ready for go-live, what comes after
- An outline schedule with milestones and dependencies
Result A quotation with scope, dates and budget framework.
- 03
Confirmation of the quotation
Open questions are settled and you return the signed quotation. In parallel we handle the formalities so that they do not hold up the project start later.
Learn more- Data processing agreement under the GDPR
- Decision on the operating model: your own server in-house or a cloud server
- A named project lead on both sides
Result Order placed and a binding project start date.
- 04 1 day
Kickoff and project setup
Before anything is configured, everyone involved meets once in full. Here it is settled who decides, who delivers and how communication works – the points where projects later lose weeks.
Learn more- Kickoff with project leads, key users and decision-makers
- The project is set up in bryve: tasks, milestones, time budgets – with access for you
- A regular meeting and an escalation path agreed
- Risks and assumptions recorded in writing
Result Project plan, access and dates – visible to everyone.
- 05 Cycles of 2 to 3 weeks
Build
Our engineers set up your open.junixx instance, connect it to your existing systems and import your legacy data. In this phase we work closely with your staff – at the end of each cycle your key users see the current state.
Learn more- Setting up the instance and providing the server
- Setup: users, roles and permissions, standard forms, number ranges
- Interfaces to distribution, web shop and accounting
- Trial migration of your legacy data, then reconciliation and correction
- A review at the end of each cycle, documented in bryve
Result A configured system that mirrors your processes.
- 06
Test and sign-off
What gets tested is not whether the software works – but whether your work works with it. Testing therefore uses real cases and the people who will work with it later.
Learn more- Test cases along end-to-end processes – from the title to the invoice
- Acceptance test by your key users with your own data
- Bugs prioritised: what blocks the go-live and what comes after
- An acceptance record with your sign-off
Result Documented sign-off for the go-live.
- 07
Onboarding and training
In person or online we go through how cooperation works in live operation and how the ticket system is used. Training follows roles – not everyone needs everything.
Learn more- Basic training for everyone, power user training for key users
- Online manual and ticket system introduced
- Settled who decides what in-house and who reports how
Result Staff who can work from day one.
- 08
Go-live
Off we go. The switchover is a date, not a period – and it is talked through beforehand, with sequence, time window and fallback.
Learn more- A cut-over plan with sequence, time window and owners
- Data freeze in the legacy system, delta migration, release
- Fallback: the legacy system stays readable until everything runs
- Hypercare: extended availability in the first weeks
Result Your publishing house works productively with open.junixx.
- 09
Support and regular operation
In day-to-day operation too we stand by you with advice and help – to maintain your systems and step in when something goes wrong. After the go-live the project ends, not the cooperation.
Learn more- A ticket system with agreed response times
- Regular releases – you choose the moment
- Regular meeting or quarterly review: what runs, what is missing, what is next
- Extensions are run like small projects – with a quotation and sign-off
Result A system that grows with your publishing house.
The project plan is not in a drawer at our office.
We run every implementation project in – the project and time platform from our own house. You get an account and see exactly what we see: tasks, dependencies, milestones and the hours booked to your project. No weekly report that is out of date the moment it is sent.
- Gantt with real dependencies. If one task moves, the rest moves visibly – instead of only at the next meeting.
- milestones and time budgets. Plan and actual per work package – not first on the invoice.
- Tasks with owners. Yours too: who delivers which data by when is in the same plan.
- Comments on the task. Decisions sit where they belong – not in an e-mail thread that three people are missing.
- Capacity planning. We see early when a cycle is overloaded – and say so before the date slips.
- Traceable time recording. Every hour booked belongs to a task, with a change log.
- Hosted in Germany. Servers in Germany, GDPR-compliant, two-factor login – hosted in-house on request.
- For your own projects too. bryve is a product in its own right – many customers keep using it after the roll-out for programme planning, production and holiday management.
Who has which role in the project.
Most delays do not arise during the build but while waiting for a decision. That is why we settle at the kickoff who decides what – on both sides.
| Role | In your publishing house | At juni.com |
|---|---|---|
| Project management | One person with a mandate: plans dates and resources in-house, keeps contact with the departments. | Keeps the plan in bryve, owns dates, budget and quality. |
| Decision on scope | Management or steering committee: decides on changes that affect dates or budget. | Effort estimate, alternatives, recommendation – with effect on the plan. |
| Departments | Key users per area – title data, production, sales, accounting. They provide process knowledge and test. | Expert advice from 25 years of publishing projects. |
| Technology | IT or IT service provider: network, workstations, access, printers. | Setting up the instance, server, interfaces and backup. |
| Data | Owners per data set: they decide what gets cleaned up and what gets carried over. | Analysis, field mapping, programming of the migration. |
Dates, budget, risks, changes.
A project stays on track not because it is planned well, but because deviations show up early.
-
Milestones with sign-off
Every phase ends with a result described in advance and your sign-off. At any point it is therefore beyond dispute what is done.
-
Changes in order
New requirements are normal – projects get wiser as they run. Every change comes with effort, an effect on dates and a decision. Nobody is surprised at the end.
-
Risks, named early
Missing data, tight resources over the summer, a third-party system without an interface: we keep a list, assess it and work through it – instead of hoping.
-
Plan and actual, ongoing
Hours booked against budget, dates against plan – visible in bryve at any time and discussed at the regular meeting.
-
Permissions and data protection
The role and permission concept is created during the project, not afterwards: data processing agreement, two-factor login, logged access.
-
Knowledge that stays
Decisions, field mappings and special cases are documented during the project. You are therefore not dependent on individual memories – on neither side.
Legacy data comes over in stages, not all at once.
A migration in a single run almost never works – because only the real data shows what is missing, duplicated or never maintained. That is why we split it up.
Defining field by field what goes where and what is dropped.
A complete run – with your real data.
Duplicate addresses, incomplete title data, old terms: You decide what comes along. We show beforehand what each option costs. Then the migration runs again – hence the second lane.
Only what has changed since the trial migration is transferred.
On request we train your staff so that you can run the migration yourselves – with advice and support from us in the background.
Additional services.
You book these services optionally on top of the open.junixx licence – depending on what your house handles itself and what we should carry.
Data migration
Do you already have databases or use different publishing software?
Learn more- Advice and analysis of existing systems
- Design and programming of migration interfaces
- Training so that you can run the migration yourselves
- Support during trial and delta migration
Interfaces
We connect open.junixx to your existing system landscape.
Learn more- Ready-made interfaces to the leading book distributors
- Web shops, accounting, payment providers
- Adapting existing interfaces to individual requirements
- New interfaces: advice, design, implementation
Training
open.junixx can do more than daily work makes use of. Tap that potential with well-trained staff.
Learn more- Beginner training: the basics for all staff
- Power user training for key users and department leads
- Module training: production, sales, billing, media cockpit
- Refreshers after major releases
It starts with a conversation.
Before budget and dates come up, we look together at how you work today: processes, legacy data, interfaces. Afterwards you know what a changeover would mean for your house and in which order it would make sense.
Let us talk about your project.
The free initial consultation is a phone or in-person conversation of up to three hours – with an honest assessment at the end, even if it speaks against a project. The offer is aimed at business customers.
juni.com GmbH
Münchener Straße 41 · 60329 Frankfurt am Main
+49 69 5077 5780 · info@juni.com