{"id":1331,"date":"2019-12-22T21:33:47","date_gmt":"2019-12-23T02:33:47","guid":{"rendered":"http:\/\/www.foxquestsystems.net\/foxblog\/?p=1331"},"modified":"2020-01-07T09:32:15","modified_gmt":"2020-01-07T14:32:15","slug":"keep-global-calendars-to-yourself","status":"publish","type":"post","link":"https:\/\/www.foxquestsystems.net\/foxblog\/2019\/12\/22\/keep-global-calendars-to-yourself\/","title":{"rendered":"Keep Global Calendars to Yourself!"},"content":{"rendered":"\n

Many construction project\nspecifications state that Global Calendars and Global Activity Codes (Global\nActivity Codes will be discussed in a separate article) are not to be included\nin the Project Schedule. The reason is that the Owner or Agency wants to control\nthe number of Global Calendars in their P6 Schedule Network.<\/p>\n\n\n\n

Imagine a large agency such as a State Department of Transportation that receives Project schedules from scores of Contractors. If the Global Calendars are not properly managed, the Department can easily wind up with literally hundreds of Global Calendars of which many may not be easily attributable to a source Project or Contractor. Also, imported Global Calendars probably do not have a typical convention structure or time configuration which may inadvertently be used as the source of another Project Calendar. Additionally, existing Global Calendars could be overwritten if Global Calendars are imported with the same Calendar name.<\/p>\n\n\n\n

In general, Global Calendars are\nintended to be used only for creating Project or Resource Calendars. Therefore,\nGlobal Calendars should never be transferred from one party to another. <\/p>\n\n\n\n

For those submitting Project\nSchedules to other parties, the submitter should make sure that Global\nCalendars are not included in the export file (typically the .XER file). Submitting\nGlobal Calendars to other parties not only populates other P6 Users with\nsuperfluous Global Calendars but is bad form and should be avoided.<\/p>\n\n\n\n

For those who receive Project Schedule from other parties, the recipient should make sure that the import file (typically the .XER file) does not contain Global Calendar. Otherwise, before long, the recipient’s Global Calendar list will contain scores of unrecognized, duplicate and unassigned Global Calendars. <\/p>\n\n\n\n

At this point, you may consider attempting to purge and delete unused Global Calendars. However, this task can be more difficult than what may appear at first. <\/p>\n\n\n\n

The following step-by-step procedure provides a guideline for cleaning up the Global Calendars List.<\/p>\n\n\n\n

1. Create a Global Calendar naming convention that clearly distinguishes your Global Calendars from all other Global Calendars.<\/strong> <\/p>\n\n\n\n

In the illustration below, the 8 highlighted Global Calendars names are preceded by a \u201c*\u201d then coded by \u201cGC\u201d prefix and a unique 2 digit number. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The \u201c*\u201d prefix helps to make sure\nthat when sorting by Calendar Name, the Global Calendars to keep are sorted to\nthe top of the grouping. The \u201cGC\u201d prefix identifies the Calendar as a Global\nCalendar.<\/p>\n\n\n\n

Using this type of convention allows P6 Users to easily spot authentic Global Calendar usage within a P6 Project and to identify those Global Calendars that are candidates for deletion. In addition, clearly identified Global Calendars facilitates stepping through the remaining checks & procedures. <\/p>\n\n\n\n

2. Create a Global Calendar naming convention that clearly distinguishes other Global Calendars, from Project and Resource Calendars. These Global Calendars are candidates for deletion.<\/strong><\/p>\n\n\n\n

In the illustration below, note that the other listed Global Calendar names are preceded by a \u201cGC\u201d then coded with a unique 2 digit number and continue with a Calendar Name.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

3. Attempt to remove all Global Calendars that are candidates for deletion<\/strong>.<\/p>\n\n\n\n

Starting with the first Global\nCalendar candidate for deletion, click on the Delete button shown above.<\/p>\n\n\n\n

Case 1: Confirmation with \u201cAre you sure\u2026\u201d window.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

If the confirmation window\nappears above and you are sure the Global Calendar can be deleted, the select \u201cYes\u201d\nand proceed to the next Global Calendar candidate for deletion.<\/p>\n\n\n\n

Case 2: Error Message appears \u2013 Calendar [Calendar Name] cannot be deleted because it is used by activities in other projects.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

If the error message window above\nappears above, then click OK. Proceed through the next steps to be able to delete\nthe selected Global Calendar.<\/p>\n\n\n\n

Click on the Used By\u2026 command button to display the Projects and\/or Resources that are using the selected Global Calendar.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

For each listed Project ID, open\nthe Project ID, then filter the Project to display all activities. <\/p>\n\n\n\n

If the Project ID is not listed\nin the EPS nodes, then the Project ID is embedded as Baseline in one of the\nProjects residing at the EPS Level. This may be a time consuming effort is the\nEPS Level Project ID is not immediately known. Once found, restore the Project\nID, then follow the Steps above to remove Global Calendars embedded in a\nBaseline Project.<\/p>\n\n\n\n

Next, Group and Sort the activity\nlist by Calendar with the Indent Checkbox selected as shown below.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Next, collapse the list so that all the activities are not shown as shown below:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Collapse the activity list so that only the Groups appear. In the illustration below, the activities are collapsed. Note that Project Activity ST03 \u2013 6 Day Standard Workweek, is indented under \u201c*GC-06 \u2013 6 Day Standard \u2013 no Holidays\u201d. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

If a Calendar Level 2 exists,\nthen the Project contains Project Calendars that are inheriting from Global\nCalendars. Follow Step 5 to change the Inherited Global Calendar setting to\n<none>.<\/p>\n\n\n\n

Continue assigning re-activities\nfrom a Global Calendar to a Project Calendar. If a Project Calendar does not\nexist for the activity, then create a new Project Calendar from a Global\nCalendar (making sure that inheritance is set to <none>. Complete this\nprocess until all activities are assigned to a Project Calendar.<\/p>\n\n\n\n

Next Group by Resource, then\nfollow Step 7 to assign Resource Calendar to the Resources used in the Project.\nComplete this process until all activities are assigned to Resources that are\nassigned to a Resource Calendar.<\/p>\n\n\n\n

Finally, close the Project then\ndelete the unwanted Global Calendar. Continue this process until all unwanted\nGlobal Calendar candidates are deleted. The remaining Global Calendars are\nvalid and should remaining in the Project Network.<\/p>\n\n\n\n

4. Unassign all remaining valid Global Calendars. <\/strong><\/p>\n\n\n\n

Next, for each valid Global\nCalendar attempt to the delete the specific Calendar. Since the Default Global\nCalendar cannot be deleted, temporarily assign another Global Calendar as the\nDefault. If the confirmation textbox appears to delete the Calendar, select No,\nthen continue to the next Global Calendar.<\/p>\n\n\n\n

If P6 cannot delete the selected\nGlobal Calendar, then follow the instructions found in Step 3, Case 2 above.<\/p>\n\n\n\n

Continue this process until all\nvalid Global Calendars are not assigned to P6 Projects.<\/p>\n\n\n\n

The next steps below ensure that exported Project files do not contain any Global Calendars. Even though Projects do not contain activities or resources assigned to Global Calendars, you can still wind up with Global Calendars contained in the export Project file.<\/p>\n\n\n\n

5. Ensure that no Project Calendars are inheriting from Global Calendars.<\/strong><\/p>\n\n\n\n

When a Project Calendar is created from a Global Calendar,\nthe Project Calendar automatically inherits its properties from the selected\nGlobal Calendar. In the sample below, the Project Calendar \u201cPC-01 \u2013 7 Day WrkWk\n\u2013 No Holidays\u201d is inheriting from the Global Calendar \u201c*GC-01 \u2013 7 Day WrkWk \u2013\nNo Holidays \u201d.<\/p>\n\n\n\n

Left this way, the inherited Global Calendar is\nautomatically brought in when an .XER file is created.<\/p>\n\n\n\n

For each Project Calendar ensure that the Project Calendars are not inheriting from a Global Calendar by selecting the Modify\u2026 command button as shown below.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Next scroll through the Global Calendar list, then select <none> from the pull-down menu as shown below.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

To prevent a Global Calendar from making its way into the .XER as a result of Inheritance,  set all Project Calendar\u2019s inheritance to \u201c<none>\u201d. In the illustration above, the pull-down menu is expanded to display the \u201c<none>\u201d option from the list of Global Calendars.<\/p>\n\n\n\n

6. Ensure that Projects do not Default to a Global Calendar. <\/strong><\/p>\n\n\n\n

Every Project has an assigned Default Calendar. The setting for the Default Calendar for a Project can be seen in the Project\u2019s Default Page in the Project\u2019s Detail window as shown below. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

When a new Project is created from scratch, P6\u2019s designated\nDefault Project Calendar is automatically assigned as the Default Calendar for\nthe Project. When a Project has a Global Calendar as the Default Project\nCalendar, then that Global Calendar will be saved in the exported .XER file.  <\/p>\n\n\n\n

To prevent a Global Calendar from making its way into the .XER as a result of Default Calendar settings, first, open the Project, then select a Project Calendar as the Default Calendar.<\/p>\n\n\n\n

7. Ensure that Resources assigned to activities do not have a Calendar Profile referencing to a Global Calendar.<\/strong><\/p>\n\n\n\n

All Resources are assigned a Calendar which can be viewed in the Details ->Profile selection window. When a new Resource is created from scratch, P6\u2019s designated Default Project Global Calendar is automatically assigned as the Default Calendar for the Resource. In the illustration below, the Carpenter resource Calendar Profile is assigned to a Global Calendar.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Resources can either be assigned\nto a Personal Calendar or be assigned to a previously created Shared Resource\nCalendar. <\/p>\n\n\n\n

To prevent a Global Calendar from making its way into the .XER file, all Resources that are assigned to the Project\u2019s activities must be assigned to either a Shared Resource Calendar or a Personal Calendar. Furthermore, whether a Shared Resource or Personal Calendar is used, the assigned Calendar must not be inheriting from a Global Calendar (See Step 5 above). <\/p>\n\n\n\n

8. Final QA\/QC .XER visual inspection.<\/strong><\/p>\n\n\n\n

Checking an .XER for Global Calendars is easy. Simply open the file using a text editor such as Notepad then scroll down to the Calendar Table (%T) section as shown below:  <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Below that line, now look for a Record line starting with (%R). Reading to the right, the 7th<\/sup> field, which displays the Record value for field name (%F) \u201cclndr_type\u201d is displayed. The three possible Record values for the Field \u201cclndr_type\u201d (Calendar Type) is:<\/p>\n\n\n\n

  1. CA_Base:\nIdentifying a Global Calendar;<\/li>
  2. CA_Project:\nIdentifying a Project Calendar;<\/li>
  3. CA_Rsrc:\nIdentifying a Resource Calendar.<\/li><\/ol>\n\n\n\n

    If \u201cCA_Base\u201d exists as a Calendar Type, then a Global\nCalendar exist for the Project contained in the .XER File.<\/p>\n\n\n\n

    If you submit schedules in .XER\nformat and \u201cCA_Base\u201d is contained in the .XER file, then go back and follow the\nsteps above to remove any reference to a Global Calendar.<\/p>\n\n\n\n

    If you receive schedules in .XER format and \u201cCA_Base\u201d is contained in the .XER file, then return the .XER file to the submitting party for correction. <\/p>\n\n\n\n

    Keeping a \u201cLean & Mean\u201d Global Calendar list helps stop the proliferation of redundant and superfluous Global Calendars. <\/p>\n\n\n\n

    Copyright \u00a92019 FoxQuest Systems, Inc. – All Rights Reserved<\/p>\n","protected":false},"excerpt":{"rendered":"

    Stop the Proliferation of Global Calendars – a Step-by-Step Guide<\/p>\n","protected":false},"author":2,"featured_media":1352,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"nf_dc_page":"","om_disable_all_campaigns":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[12],"tags":[],"class_list":["post-1331","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tips"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"https:\/\/i0.wp.com\/www.foxquestsystems.net\/foxblog\/wp-content\/uploads\/2019\/12\/1a-Keep-Global-Calendar-to-yourself.jpg?fit=541%2C403&ssl=1","_links":{"self":[{"href":"https:\/\/www.foxquestsystems.net\/foxblog\/wp-json\/wp\/v2\/posts\/1331","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.foxquestsystems.net\/foxblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.foxquestsystems.net\/foxblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.foxquestsystems.net\/foxblog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.foxquestsystems.net\/foxblog\/wp-json\/wp\/v2\/comments?post=1331"}],"version-history":[{"count":7,"href":"https:\/\/www.foxquestsystems.net\/foxblog\/wp-json\/wp\/v2\/posts\/1331\/revisions"}],"predecessor-version":[{"id":1444,"href":"https:\/\/www.foxquestsystems.net\/foxblog\/wp-json\/wp\/v2\/posts\/1331\/revisions\/1444"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.foxquestsystems.net\/foxblog\/wp-json\/wp\/v2\/media\/1352"}],"wp:attachment":[{"href":"https:\/\/www.foxquestsystems.net\/foxblog\/wp-json\/wp\/v2\/media?parent=1331"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.foxquestsystems.net\/foxblog\/wp-json\/wp\/v2\/categories?post=1331"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.foxquestsystems.net\/foxblog\/wp-json\/wp\/v2\/tags?post=1331"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}