1 / 20

PRA 8.7 Enhancement Requests 2012

PRA 8.7 Enhancement Requests 2012. 2012 OPSIG Survey Results and descriptions. Categories. New Features (or returning old features) Enhancement to existing features Fixing existing features Technical Issues with PRA. Category 1. New Features Or Returning of Old Features.

ady
Download Presentation

PRA 8.7 Enhancement Requests 2012

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PRA 8.7 Enhancement Requests 2012 2012 OPSIG Survey Results and descriptions

  2. Categories New Features (or returning old features) Enhancement to existing features Fixing existing features Technical Issues with PRA

  3. Category 1 New Features Or Returning of Old Features

  4. Category 1: New Features Conditional Branching: We should bring back the capability to perform conditional branching. It is a valuable, very sophisticated modeling tool for schedule risk assessment.

  5. Category 2 Enhancement of Existing Features

  6. Category 2: Enhancement to Existing Features Automate Risk Prioritization – Risk Factors, Risk Register, Existence Risks: This can only be done by (a) turning off a risk, (b) running the analysis, and (c) comparing the new date (at some %) to the model before the risk was removed. This will tell you the days of impact that a risk adds to the schedule.

  7. Category 2: Enhancement to Existing Features Allow Risk Factors’ impacts to vary by the activities they influence Some other software (e.g., Risky Project) allow the risk factor to vary depending on the activity it is influencing. This is useful if some risk affects long-duration activities and short-duration activities.

  8. Category 3 Fixing Existing Features

  9. Category 3: Fixing Existing Features Fix the Risk Factors Tornado Diagram Currently the Risk Factors Tornado diagram seems to be broken. In the previous slide, the risks are all threats but the Tornado shows negative correlation with the finish milestone.

  10. Category 3: Fixing Existing Features Allow schedule Risk Factors to appear on the cost tornado graph Now this tornado only considers the risks to cost The cost tornado should also look at and prioritize all risks to cost, including those risk to time that affect the cost of time dependent resources.

  11. Category 3: Fixing Existing Features • Weather Modelling function bugs and crashes a lot when dealing with multiple Weather calendars. Sometimes this can result in loss of all assignment of the weather calendar (resource) against activities in PRA.

  12. Category 3: Fixing Existing Features Improve import/export of the risk register Provide the possibility to export/import the risk register of a project between P6 and PRA and Excel, besides doing it through UDFs

  13. Category 4 Technical Issues with PRA

  14. Category 4: Technical Issues with PRA Links Window does not remember column widths in the Links Details window.(Enhancement Request 8951737) Every time PRA is started and you wish to review dependencies, you have to resize the columns in the Links window so you can read the ID-Description field. This column is equal with all other column widths on startup and it is impossible to read the predecessors or successors.

  15. Category 4: Technical Issues with PRA Sequencing in PRA PRA does not handle lack of leading zeros on multiple digit numbering, but P6 does. (Covered by Enhancement Request 8963592). The WBS sequence 1,2,3,4,5,6,7,8,9,10,11,12... will appear in the right order in P6, but not in PRA, where it appears as 1,10,11,12,2,3,etc. It is very time-consuming to match P6 sequence!

  16. Category 4: Technical Issues with PRA Risk Factors for costs The Risk Factors Module does not work properly for costs: Risk Factors should moderate existing ranges on activities. This is what they do for durations, but for costs, the risk factors overwrite what was there.

  17. Category 4: Technical Issues with PRA Format Organize wipes out code values If you use the Plan/Organize dialog you can find that PRA erases your code values.

  18. Category 4: Technical Issues with PRA Float calculations during iterations are not updated and predecessor and successor dependencies are treated differently The problem can be described thus: • For predecessor links, the ‘driving’ status is permanently set to ‘No’ and is not updated between iterations. • For successor links, the relative float is always calculated to be ‘0’, even when the relationship is not driving. • For successor links, the ‘driving’ status is permanently set to ‘Yes’ and is not updated between iterations.

  19. Thank You! David T. Hulett, Ph.D., Hulett & Associates, LLC Project Management Consultants www.projectrisk.com / david.hulett@projectrisk.com / (310) 476-7699

More Related