ERP Business Analyst in Mecca

A service company's group, written as requirements

Companies that organize pilgrims' stays sit between many parties. They contract with agents abroad, reserve rooms with hotels, book buses and meals, and answer for the whole arrangement once the group arrives. Parts of this work run through official platforms and are governed by licensing rules set by the authorities, which your advisors confirm. The company's own commercial records still need a system, and that is where requirements matter.

I map the cycle from the agent's contract to the final settlement:

• The group record: the agent, the agreed services, the price and the payment schedule
• Bookings with each hotel, transport operator and caterer, linked back to the group
• Changes on arrival, such as fewer travelers, late flights or a swapped room type, and who approves each one
• Costs as delivered, compared with costs as booked
• Supplier invoices matched against confirmed services before payment
• The agent's final statement, in the agreed currency and with any deductions the contract allows

Each line becomes a numbered requirement with an owner and a test case. The aim is to know, for every group, what was promised, what was delivered and what was paid, rather than piecing it together from spreadsheets once the season is over. The hotel, catering and transport side of the city is described on my Mecca ERP consultant page.

Performance requirements for the busiest days

Functional requirements describe what a system must do. In Mecca, the requirements that cause the most trouble describe how well it must do it on the busiest days. A shop till that is slow to issue an e-invoice creates a queue. A catering store that cannot post issues quickly falls behind its production plan. A finance team that cannot run reports while transactions pour in loses its daily view of cash.

I write these as non-functional requirements with acceptance criteria that can be tested:

• Expected transaction volumes per process, estimated from past peak records
• Response times for the screens and documents used most at counters and tills
• How many users work at once, temporary staff included
• Behavior of the ZATCA e-invoicing connection under load, and what happens when submissions queue or fail
• Support response during peak periods, and who is on call
• Backup and recovery expectations if a server or hosting service goes down

Vendors and implementers answer each criterion in writing and demonstrate the critical ones in a load test before go-live. The e-invoicing obligations themselves are for your tax advisor to confirm. Requirement work on Kingdom-wide topics such as VAT scenarios and Arabic documents is covered on my ERP business analyst for Saudi Arabia page.

Contractors on crowded central sites

Construction near the central area is shaped by space and access. Sites are tight, the surrounding streets are busy, and the rules on when heavy vehicles may enter and which works may proceed are set by the authorities and can tighten around the busiest periods. Contractors and their suppliers adapt by staging materials in yards outside the center and calling them forward in small, timed loads.

Standard purchasing and project modules assume goods arrive at a site and are used there. On these projects the real flow is longer, so I capture requirements such as:

• Staging yard stock held per project, separate from main warehouse stock
• Call-off requests from the site, approved and scheduled against delivery windows
• Delivery booking records, including permits or passes where your team confirms they apply
• Lifting and hoist schedules linked to the materials they move
• Waste and demolition removal tracked as a cost per project
• Planned pauses around peak periods, reflected in costs and progress claims

Requirements like these protect margin, because idle crews and refused deliveries are expensive. The contracting industry page covers progress billing and subcontractor claims, which complete the picture.

Seasonal staff from hiring to final settlement

Many Mecca employers add people for the busiest periods: hotels, caterers, cleaning contractors, shops and service companies alike. Some are hired directly on short contracts, others come through manpower suppliers, and many need housing, transport and meals while they work. Each arrangement creates records that the ERP and payroll must hold correctly.

The requirements for this area cover:

• Contract type and source, direct or through a supplier, with the documents each needs
• Housing, transport and meal allocations, costed to the department or contract using the worker
• Uniforms and equipment issued and returned
• Attendance from each site, approved by a named supervisor
• Supplier invoices for agency staff matched against approved hours
• System accounts created with the right role and closed automatically when the contract ends
• Final pay and any end-of-service amounts, calculated as your HR advisor confirms

Labor rules, visa matters and payroll obligations are decided with your HR and legal advisors, and the requirements then specify how their conclusions are recorded. Closing access on time matters as much as granting it, because temporary accounts left open are an avoidable audit finding. My ERP requirements gathering page explains how sections like these fit into a full BRD.

Gathering evidence during the peak, writing requirements after it

The people who know how a Mecca business really works are busiest exactly when the most revealing things happen. Asking them in a quiet period how they handled a rush produces tidy answers that miss the exceptions. Asking them during the rush is unfair. A peak diary closes that gap.

Before a busy period, we agree a short list of processes to observe and a simple routine for supervisors. When something unusual happens, such as a group arriving early, a delivery refused at a hotel dock or a till falling back to paper, they photograph the document and record a voice note of a few sentences. A coordinator on your side files everything in a shared folder by process.

Once the pressure eases, I review the diary with each supervisor in short remote sessions, turn the exceptions into process variants and requirements, and link every requirement to the evidence behind it. Vendors then see real cases, not generic descriptions. Because the engagement runs in English, notes recorded in Arabic are summarized by a bilingual coordinator, and Arabic wording in the final documents is checked by your staff or a local partner. If the analysis points toward a platform decision, my Mecca freelance ERP consultant page covers independent selection support, and the Saudi Arabia hub lists other services.