Implementation
How KMK takes RA-Core from the first workshop to a running system — and what your team does at each step.
How we work
Six phases from kickoff to go-live and beyond
Every project is different, so the durations below are indicative only. The KMK team confirms a timeline for your project once the scope is agreed.
Step 1: Discovery and scope
Duration: 1–2 weeks (indicative)
We meet the people who run each department, walk through how work is done today and confirm, in detail, the modules, companies, branches and sites covered by your proposal. The result is a written scope and an indicative plan.
Your team
Nominate a project owner and key users, and share your current forms, reports and pain points.
Step 2: Design of the setup
Duration: 1–3 weeks (indicative)
We turn the agreed scope into a setup design: chart of accounts, cost centres, warehouses, approval paths, user roles and — for facility management — the structure of sites, buildings and assets.
Your team
Review the design with your department heads and confirm the decisions it records.
Step 3: Data preparation and migration
Duration: 2–4 weeks (indicative), depending on data volume
We provide templates for master data and opening balances, check what you prepare and load it into RA-Core. Problems found at this stage are far easier to fix than after go-live.
Your team
Gather and clean your customers, suppliers, items, employees, assets and balances, then sign off the loaded data.
Step 4: Configuration and testing
Duration: 2–6 weeks (indicative)
We configure the modules, roles, approval steps, reports and printed documents, then run your real scenarios end to end — from a purchase request to payment, or from a fault report to a closed, costed work order.
Your team
Key users test their daily scenarios and report anything that does not match how you work.
Step 5: Training and go-live
Duration: 1–2 weeks (indicative)
We train administrators, key users and field teams by role, in Arabic or English, then agree a go-live date and switch over with the KMK team on hand.
Your team
Make time for training sessions, and confirm the cut-over date and final opening balances.
Step 6: Support after go-live
Duration: Ongoing, as set out in your proposal
In the first weeks we stay close, answer questions and fine-tune settings as real volumes arrive. After that, the KMK support team in Cairo remains your point of contact and helps you add modules as you grow.
Your team
Report issues through the agreed support channel, and keep your key users as the first point of help for colleagues.
Before configuration
Decisions to settle early
Three choices shape almost everything that follows. Settling them during the design phase keeps the project on schedule.
Chart of accounts and cost centres
Decide how finance wants to report — by department, branch, project or site — and design the accounts and cost centres around it. Every module posts to this structure, so it is worth getting right first.
Numbering and approval rules
Agree how documents are numbered across companies and branches, and who approves purchase requests, payments and leave. Clear rules from day one avoid rework after go-live.
Master data ownership
Name who creates and maintains customers, suppliers, items, employees and assets. With one owner for each type of record, the shared database stays clean as the business grows.
Questions
Implementation questions
Can we go live with some modules first?
Yes. You can start with the modules that matter most and add others in later phases. Because every module shares one database, each phase builds on the data you already have.
Who owns the project plan?
KMK prepares and maintains the plan, and your project owner agrees it, including the dates that depend on your team. Both sides review progress together at the end of each phase.
What if our data is not ready?
Data preparation often sets the pace of a project. If records need more cleaning than expected, KMK will discuss options with you — such as loading the essential master data first — and adjust the plan together.