SCHEDULE DATA

International Football Tournament Stadium & Digital Ticketing Project

1. Document Information

• Project Manager: Alex
• Version: 1.0
• Date: 10 December 2025
• Status: Supporting Schedule Artifact
• Related Documents:
  • Activity List
  • Network Diagram
  • Schedule Management Plan
  • Assumption Log

2. Purpose

Schedule Data provides the supporting information required to develop, analyze, and control the schedule model.

It documents:

• Assumptions
• Constraints
• Leads & lags
• Calendars
• Activity attributes
• Contingency reserves
• Risk-based duration ranges

It ensures schedule transparency and auditability.

3. Activity Attributes (Key Examples)

Below are representative attributes for critical activities.

A-603 – Lay Turf Surface

• WBS ID: 2.6
• Responsible: Turf Subcontractor
• Activity Type: External specialized installation
• Predecessor: A-602 (Install drainage) – FS
• Constraint: Cannot begin before enclosure weather-tight
• Assumption: Weather conditions within seasonal norms
• Risk Link: R-12 (Weather delay risk)
• Duration Basis: Expert judgment + historical stadium data
• Float Sensitivity: Near-critical

A-803 – Gate Functional Testing

• WBS ID: 2.8
• Responsible: Construction Seller
• Dependency: Utilities commissioned (A-903) – FS
• Assumption: Firmware version stable
• Interface Risk: Requires digital identity module for integration
• Risk Link: R-18 (Hardware–software incompatibility)

A-1201 – Gate ↔ App Integration

• WBS ID: 4.1
• Responsible: Integration Lead
• Predecessors:
  • A-803 (Gate testing) – FS
  • A-1103 (Identity verification) – FS
  • A-1104 (Ticket issuance) – FS
• Activity Type: Hybrid cross-domain
• Assumption: API specifications frozen
• Risk Link: R-22 (Interface misalignment)
• Float Sensitivity: Critical path candidate

4. Schedule Assumptions

1. Turf installation window is seasonally feasible.
2. Construction seller resource availability is stable.
3. Identity verification vendor API will not change.
4. Regulatory inspections occur within statutory timelines.
5. Integration testing environment available on schedule.

All assumptions are cross-referenced in the Assumption Log.

5. Schedule Constraints

6. Project Calendars

Construction Calendar

• 6 working days/week
• No work during severe weather alerts
• National holidays excluded

Digital Team Calendar

• 5-day sprint cycle
• 2-week sprint duration
• Fixed sprint cadence

Integration Calendar

• Shared access windows for physical site
• Restricted nighttime testing allowed

7. Leads and Lags

• No leads permitted on safety-critical path.
• Turf curing period represented as explicit lag between A-603 and A-604.
• Regulatory inspection buffer represented as contingency reserve, not lag.

Lag Example:

• A-603 → A-604: FS + 14 days (turf conditioning period)

8. Contingency Reserves

Contingency time is allocated based on risk exposure:

Reserves are visible and tracked.
They are not hidden inside activity durations.

9. Risk-Based Duration Ranges (for Monte Carlo)

Example:

Used for quantitative schedule risk analysis.

10. Critical Path Sensitivity Notes

Current near-critical chain:

Turf certification → Integrated stadium testing → Occupancy permit → Handover

Hybrid critical chain:

Gate testing + Identity verification + Ticket issuance
→ Gate ↔ App integration
→ End-to-End test
→ UAT
→ Handover

These are monitored as cross-stream sensitivity paths.

11. Schedule Data Control

• Updated at each schedule review cycle
• Changes require PM approval
• Linked to risk register updates
• Historical versions archived for audit