Roshdy Building — Tender Programme

Company says who is responsible; Discipline says which team; Belmazad + GAT is joint work (split bar, task text names who leads). Tick tasks to select them (a bar appears with Delete selected); tick exactly two to link them, or type links in Comes after: 12 = after 12 finishes · 12SS+3 = 3 days after 12 starts · 12FF = finish with 12. A typed Start is pinned; clear it to return to automatic. Days are working days (Sunday–Thursday, minus the non-working dates in the header); WD = 0 makes a milestone. Rows marked edited or added were changed by the team and are kept when the standard plan is updated. Drag header edges to resize columns; drag the table's bottom-right corner to make it taller.

Company is the responsible party; Discipline the team; Belmazad + GAT is joint work (split bar). Milestones are diamonds; the last row of each project is held float. Hover a bar for its dates. Use the tabs to view each project or both together; the Sphinx launch after Roshdy launch box in the header lets you try other launch gaps (not saved). Red underline = critical path. Zoom with − / Fit / +, and export to Excel or PDF.

Sphinx runs on its own clock; its Day 1 is placed so that its launch (M3) falls the chosen number of weeks after Roshdy's launch. Hatched bars and the purple chip are Sphinx; solid bars are Roshdy. Tasks from both projects are listed in one sequence, ordered by start date and then end date, so you can see what both projects and the shared GAT / software teams are doing in the same week.

All durations are working days on a Sunday–Thursday week; calendar dates are shown. Egyptian public holidays are excluded (Islamic dates ±1–2 days for moon sighting; a holiday falling on a weekend is taken on the next working day); the four Thursdays of Ramadan 2027 are treated as non-working to reflect reduced working hours. Roshdy’s submission deadline is set before the late-December holiday period. MAD approvals are 4 working days; the complete tender package 8 (Sphinx 12, Board-level); one shortlist decision covers financial opening and negotiation, and MAD’s acceptance of the evaluation report confirms the negotiation mandate proposed in it; a longer approval moves everything after it. Responsibilities follow the Belmazad–GAT–MAD responsibility matrix: GAT reviews available information and bidder-supplied investigations and does not undertake fieldwork; investigations MAD decides to procure are shown as client tasks feeding the data room. Each project's contractual period runs from its anchor milestone — Roshdy from Commencement (programme approved and documents received), Sphinx from MAD's launch instruction, with preparation done in parallel beforehand and postponement of up to two months permitted. Two negotiation rounds are planned per project (a round covers all shortlisted bidders and their revisions); one additional round where reasonably required extends the programme by up to two weeks without penalty. Evaluation durations assume 6–10 Roshdy bids and 4–8 Sphinx bids and are subject to GAT's confirmation of its named team and review methodology. Float is held before each completion milestone. Standing activities (progress reporting, GAT's parallel manual delivery) are drawn as thin bars and do not drive the dates. Stage 7 (MAD's award decision, final questions, closeout) is MAD's period and sits outside the consultant's commitment.