• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
101713 Primavera P6 Database Resource Management
 

101713 Primavera P6 Database Resource Management

on

  • 1,790 views

This is a critical presentation to show Primavera scheduling tool Users how to clean and improve a cluttered and disorganized Database, to demonstrate that structured resource structure helps to ...

This is a critical presentation to show Primavera scheduling tool Users how to clean and improve a cluttered and disorganized Database, to demonstrate that structured resource structure helps to effectively manage resources, to improve Global Resource security, to help Users create and maintain a robust resource dictionary that is in aligned to the existing Enterprise Project Structure (EPS), to prevent Users from accidentally deleting global codes through better understanding of how they affect other projects and other Users, to illustrate the adverse consequence of intentionally or inadvertently modifying and/or deleting global codes and structure, To highlight the importance of scrubbing external project files before importing into the company’s P6 database, to clean and improve a cluttered and disorganized Primavera Database using an acceptable Resource Structure which is aligned to the EPS and the OBS, to improve the database Global Resource security, and to avoid the grief, the unproductive & costly codes restoration that can run for days, weeks or even months not to mention lost opportunities, to prevent contractual disputes with contractors.

Statistics

Views

Total Views
1,790
Views on SlideShare
1,788
Embed Views
2

Actions

Likes
3
Downloads
0
Comments
1

1 Embed 2

http://www.linkedin.com 2

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

11 of 1 previous next

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    101713 Primavera P6 Database Resource Management 101713 Primavera P6 Database Resource Management Presentation Transcript

    • PRIMAVERA SCHEDULING TOOL P6 DATABASE RESOURCE MANAGEMENT How to manage your Primavera Resources Administrator’s Overview Author: Rufran C. Frago, P.Eng, PMP®, CCP, PMI-RMP® Revision: 17-Oct-2013 0
    • 1
    • OBJECTIVES To show Users how to clean and improve a cluttered and disorganized Primavera Database. To demonstrate that structured resource structure helps to effectively manage resources. To improve Global Resource security. To help Users create and maintain a robust resource dictionary that is in aligned to the existing Enterprise Project Structure (EPS). To prevent Users from accidentally deleting global codes through better understanding of how they affect other projects and other Users. To illustrate the adverse consequence of intentionally or inadvertently modifying and/or deleting global codes and structure. P6 Database Resource Management 2
    • OBJECTIVES … (continuation) To highlight the importance of scrubbing external project files before importing into the company’s P6 database. To clean and improve a cluttered and disorganized Primavera Database using an acceptable Resource Structure which is aligned to the EPS and the OBS. To improve the database Global Resource security. Avoid the grief, the unproductive & costly codes restoration that can run for days, weeks or even months not to mention lost opportunities. Prevent contractual disputes with contractors. P6 Database Resource Management 3
    • Acronyms EPS OBS GDM DB User Admin PC Enterprise Project structure Organizational Business Structure Global Data Management Database (Databases)3 One who have access to the P6 DB and usually the Schedule Owner P6 DB Administrator/Coordinator Project Controls P6 Database Resource Management 4
    • What are P6 Resources? P6 Resources include the personnel and equipment that perform work on activities across all projects. In the Project Management module, the Owner of the Schedule can create a resource pool that reflects the User’s organization's resource structure and supports the assignment of resources to activities (1). The Project Management module also enables the User to distinguish between labor, material, and non-labor resources. Labor and non-labor resources are always time-based, and material resources, such as consumable items, use a unit of measure you can specify (1). Users can create and assign resource calendars and define a resource's roles, contact information, and timevarying prices. All P6 resource codes are global codes. P6 Database Resource Management 5
    • Related Tools & Applications Project Management (Primavera 6.1 SP1, 6.2, 6.7 SP1, 6.7 SP2 & SP4) Oracle Primavera Risk analysis V8, V8.7 (previously called PertMaster) P6 Database Resource Management 6
    • How to properly and effectively Set-up Global Resources & Structure  Projects shall create a coding structure that aligns with the existing EPS and OBS.  Resources belonging to the same portfolio should be able to roll up.  Global resources should have unique identifiers; e.g. unique prefixes or suffixes.  First and second resource hierarchy shall be managed by the Primavera DB Administrator.  The lower resource hierarchies are best set by the projects. These are project-specific codes.  Resource security setting allows the administrator to restrict Users access to a specific resource root in the hierarchy.  Once assigned, a User have access only to that resource root and all of its children. P6 Database Resource Management 7
    • Example of Resource Hierarchy Resource Structure EPS/OBS Level 1 Level 2 Level 3 Level 4 Level 2 Level 3 Level 4 Note the close alignment between the resource structure and the EPS/OBS. The EPS and OBS structure in this DB security design uses the exact same structure for simplicity and manageability. P6 Database Resource Management 8
    • The DOs of P6 Resource Management Do call the P6 Administrator before creating a new resource root. Do make sure that the resources created and/or assigned belongs to the correct hierarchy. Do regular review & clean ups of resources. Do report to the P6 Administrator any User who found access beyond what was agreed to. Do understand that Enterprise standard resources (or common resources) are owned by the P6 Administrator & the Central Project Controls Team of each project portfolio. P6 Database Resource Management 9
    • The Don’ts of P6 Resource Management  Do not add, modify or delete any resource without informing the P6 Administrator and the Central PC team first.  Never create new resources which do not belong to any resource root or they will be deleted during clean ups as rogue codes.  Never use another project’s resources unless there is previous agreement to share.  Do not delete or change the name/code ID of any resource. Ask first for advice if not sure & exercise due diligence. Any change or deletion can adversely affect other Users and their projects P6 Database Resource Management 10
    • Moving resources around but within the P6 DB Dictionary will not affect how it was originally assigned Example: Given the two resource roots A1 and B1 below located under one overall global resource structure. These two resource roots caters to two completely different project portfolios A1 and B1. As shown below, the resource called APT was currently assigned to Project A1X, A1Y and A1Z (2). B1 Resource Root A1 Resource Root Project A1X Project A1Y Project A1Z P6 Database Resource Management 11
    • Moving resources around but within the P6 DB Dictionary … (continuation) Let us say that someone with access inadvertently moved the A1 resource APT into another resource root or branch called B1 within the overall Resource Structure (5). Result: resource APT will remain assigned to all the projects it was assigned to previously. Nothing has changed except that we might have a resource located in the wrong resource group that needs to be corrected. A1 Resource Root Project A1X B1 Resource Root Project A1Y Project A1Z P6 Database Resource Management 12
    • DEMONSTRATION: ANIMATION A1 Resource Root Project A1X B1 Resource Root Project A1Y Project A1Z P6 Database Resource Management 13
    • CAUTION! Moving resource/s to another resource root within the resource structure will not change the project assignment of that resource/s… BUT Do not use cut-paste or copy-paste when organizing or moving resource/s because you will lose the resource’s project assignments completely and vice versa. P6 Database Resource Management 14
    • Demonstration of the Adverse Effects of modifying and deleting resources without proper coordination Given the Resource Hierarchy below - ABC Enterprise - Codes Definition A-Resource Root - A1 Resource Root A11 E&P SENIC00 SENEL00 SENME00 SENPP00 SENPR00 P6 Database Resource Management 15
    • Demonstration of the Adverse Effects of modifying… (continuation) One User in a concurrent work environment of 150 Users renamed a few codes for UNKNOWN REASON! - ABC Enterprise - Original Codes Definition A-Resource Root - A1 Resource Root A11 E&P SENIC00 SENEL00 Renamed Electrical code to SENME00 Renamed Mechanical code to STEEL MULTI-DISCIPLINE SENPP00 SENCV00 P6 Database Resource Management Renamed Civil code to 16 MECHANICAL
    • The changes made by another User will affect another User/s and Another Project/s using the previous Codes….see below P6 Database Resource Management 17
    • …and see now. It will be quite unfortunate that everyone who flew in today from overseas will have to postpone their resource review meeting... P6 Database Resource Management 18
    • DEMO ANIMATION P6 Database Resource Management 19
    • PROJECT A1X STEEL MULTI-DISCIPLINE MECHANICAL STEEL MULTI-DISCIPLINE MECHANICAL
    • Lessons Learned  If Resource Codes and/or Resource Descriptions are renamed or modified without proper coordination, it will adversely affect other Users and all resource-related reports will be flawed.  It follows that if Resources are deleted from the Resource Structure, the corresponding resource assignment will also disappear.  All P6 Resources are global and can usually be accessed by several Lead Users. There is no absolute security to this except knowledge, skills and ethics; the capacity to understand that there are other Users in the common work environment that might be affected.  Moving resource/s to another resource root will not change the assignment of that resource/s. Do not use cut-paste or copy-paste when organizing or moving resource/s because of the risk of losing the resource’s project assignments & vice versa.  Deleting the project will delete all the resource assignments to that project.  Do not be afraid to ask other Users. Call you DB Admin. P6 Database Resource Management 21
    • BIBLIOGRAPHY 1. Primavera Help File (2011/2012).Resources.Intool Help Menu 2. Reference Manual P6 V7 (1999-2009).Setting Users PreferencesResource & Roles Assignment.P54.Retrieved from http://docs.oracle.com/cd/E16281_01/Product_Manuals/PMRefMan.pdf 3. Reference Manual P6 V7 (1999-2009).Defining Resources and Roles.P97-115.Retrieved from http://docs.oracle.com/cd/E16281_01/Product_Manuals/PMRefMan.pdf 4. TheP6Pro (2011).P6-Assigning Resources From a Large Pool.Tensix Consulting.Retrieved from http://www.tensixconsulting.com/2011/03/primavera-p6-assigningresources-from-a-large-pool/ 5. Frago, R. (2013).Improving DB Security by Managing the RMC Field.Retrieved from http://www.slideshare.net/rfrago/070313primavera-scheduling-tips-tricks-0413-rmc P6 Database Resource Management 22
    • END OF PRESENTATION P6 Database Resource Management 23