Illustration 3.2
Schedule file name convention
for identification of schedule versions
- Alphanumeric Naming Convention is a convenient format to monitor the number of schedule submissions, schedule version history, and version control - as well as, to obtain a snapshot of the project’s performance for every schedule submission. As part of the schedule version history, the source of schedule submissions is also tracked.
- Every schedule submission (schedule version) is assigned a combination of a unique number (Month Identifier), and an alphabet (Baseline Series Identifier).
- The number in the schedule version refers to the progress as of the number of months from the project start. The number for the month is derived from the data date.
- The alphabet in the schedule version such as A, B, or J helps to differentiate schedule submissions.
- Major developments in the schedule version history, major schedule logic changes, and proposed baselines/ accepted baselines are identified with a unique alphabet which is called a baseline series identifier
- The alphabet is used to recognize the source of the schedule versions.
- The alphabet is also used to track schedule versions where major changes in logic, duration, or forecast dates might have happened.
- With the help of the alphabet identifier, schedule versions with similar attributes, functionality, logic, etc. (part of the same baseline) can be easily marked, and grouped, if needed.
- It is a best practice that also helps avoid confusion - a comparative analysis of a project’s schedule data may involve source data by the contractor, data from other sources in the project, and secondary data generated by third parties.
| Month | Month & Year | Schedule Version | Data Date | Print Date (Publish Date) | Substantial Completion (MS85) | Slippage | Note |
|---|---|---|---|---|---|---|---|
| 0 | Aug 2021 | 0-A Contractor’s Draft Schedule | 2021-09-13 (assumed data date) | 2021-09-07 | 2023-12-29 |
| |
| 0 | Aug 2021 | 0-B Contractor’s Draft Schedule | 2021-10-04 (assumed data date) | 2021-10-05 | 2023-12-29 |
| |
| 1 | Sep 2021 | ||||||
| 2 | Oct 2021 | ||||||
| 3 | Nov 2021 | 3-C Schedule Update | 2021-11-12 (assumed data date) | 2021-11-12 | 2024-02-14 | 🔺-48 cd 🔺-33 wd |
|
| 3 | Nov 2021 | 3-D Schedule Update | 2021-11-26 (assumed data date) | 2021-11-26 | 2024-02-23 | 🔺-57 cd 🔺-393 wd |
|
| 4 | Dec 2021 | ||||||
| 5 | Jan 2022 | ||||||
| 6 | Feb 2022 | 6-D Schedule Update | 2022-02-10 (assumed data date) | 2022-02-10 | 2024-04-08 | 🔺-102 cd 🔺-69 wd |
|
| 7 | March 2022 | ||||||
| 8 | April 2022 | 8-D Schedule Update | 2022-04-11 (assumed data date) | 2022-04-21 | 2024-05-03 | 🔺-127 cd 🔺-88 wd |
|
| 9 | May 2022 | ||||||
| 10 | June 2022 | 10-D Schedule Update | 2022-06-24 (assumed data date) | 2022-06-30 | 2024-07-04 | 🔺-189 cd 🔺-130 wd |
|
| 11 | July 2022 | ||||||
| 12 | Aug 2022 | ||||||
| 13 | Sep 2022 | ||||||
| 14 | Oct 2022 | ||||||
| 15 | Nov 2022 | 15-D Schedule Update | 2022-11-08 (assumed data date) | 2022-11-17 | 2024-08-27 | 🔺-243 cd 🔺-168 wd |
|
| 16 | Dec 2022 | ||||||
| 17 | Jan 2022 | 17-D Schedule Update | 2023-01-30 (assumed data date) | 2023-02-09 | 2024-07-24 | 🔺-209 cd 🔺-144 wd |
|
0 Comments
Trackbacks/Pingbacks