1 / 21

Erik Danielsson Product Responsible - Proteus Quantum Solutions AS +47 97 06 85 42

Project Information vs. Project Control… “What is CONTROL anyway?”. Erik Danielsson Product Responsible - Proteus Quantum Solutions AS +47 97 06 85 42 erik@quantumsolutions.no 15 minutes – April 15, 2010. Quantum Solutions. Opening new doors and windows to the world of Project Management.

orea
Download Presentation

Erik Danielsson Product Responsible - Proteus Quantum Solutions AS +47 97 06 85 42

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. Project Information vs. Project Control… • “What is CONTROL anyway?” Erik Danielsson Product Responsible - Proteus Quantum Solutions AS • +47 97 06 85 42 • erik@quantumsolutions.no • 15 minutes – April 15, 2010

  2. Quantum Solutions Opening new doors and windows to the world of Project Management

  3. “It is funny that there’s no way to manufacture nutrition from carbon, phosphor, nitrogen, and a bunch of other atomic substances… They have totake the path thru the carrot in order to become nutrition!” Project Information vs. Project Control…? A philosophical introduction to this topic… Quote from a philosophical farmer friend: ..or paraphrased:

  4. Project Information vs. Project Control…? Transforming carbon (+ other atoms) into nutrition – it has to go through the plant!

  5. Project Information vs. Project Control…? Transforming “Project Information” into “Project Control” - it has to take the path through the human mind!

  6. “Project control can only exist if project data gets transformed through the human consciousness” Project Data vs. Project Control…? The philosophical conclusion… …Consequently:

  7. We are going to look into 3 specific areas where project control may be improved, and give some pointers and examples of how this may be achieved… How does this translate to the real world? Stepping down from the philosophical cloud… NOTE: This is not intended to be a sales presentation, but is a summary of the presenter’s observations after 12 years of working with project organizations … For practical reasons, all screenshots are taken from Proteus, but if you know of any other software system(s) that has the same (or better!) functionality in any of these areas – please use it!

  8. 3 major hurdles of “Project Control” The anatomy of control – It’s like “perfection”: you never reach it, but can only optimize the conditions for it happening… 1 #1 Overcome the curses of System boundaries! 10 jobs 100 Docs 1000 cables #2 Present data in a way that ”makes sense”! #3 Be adaptable to new requirements! - Ideally without dependency on external consultants!

  9. #1 - Overcome the Curses of System Boundaries The typical information topology in a large Project Organization • Network software embedded in ERP Ocean. • Each Network activity relates to ~10n ERP objects • Minor Network changes have major ripples in ERP ocean. R 1 E P 10 jobs 100 Docs 1000 cables 1 By the way: There are 10 types of people in the world: Those who understand binary - and those who don’t… Spools 10 jobs Pipetests Valves 100 Docs Welds 1000 cables

  10. #1 - Overcome the Curses of System Boundaries A few typical examples… • Related items between system A and B get out of sync. • Time is lost chasing related data between system A, B and C. • Users have to jump between 2,3,4.. or more systems instead of having all the necessary data shown hierarchically and updateable through ONE interface. • Data inconsistencies may be costly and difficult to find. • Limited and/or rigid reporting of data across systems. • Even within one system, you may have data distributed across various servers – difficult to consolidate into one overview. 1 10 jobs 100 Docs 1000 pipes

  11. #1 - Overcome the Curses of System Boundaries Make N systems appear as ONE system – not only for reporting, but also for updates. 1 10 jobs 100 Docs 1000 pipes

  12. #1 - Overcome the Curses of System Boundaries Typical example: Bridge the abyss between Safran (Level4) and IFS (Level 5 + 6)

  13. #2 – Present data in a way that ”makes sense” Map what YOU consider “important facts” to something you can see with your eyes. Progress bar is green if 100% Barisred if > 10 000 hours Show expected Range if Behind Schedule Blue box indicates child-range (min - max). Hatch=Outside parent range! The more negative the number, the more attention it should get: Score = Hours * Delta% / 100 This bar is more “yellow”, indicating it has more hours. Transparency controlled by hours – compare with topmost bar!

  14. #2 – Present data in a way that ”makes sense” A hint to your projects - This ”Completion Report” format is extremely useful: • Visualize material and design hold on jobs (in 6 week work-schedule). • MC and CP overviews • LCI (Life cycle information) • Progress overview for any type of planning/production data. • Piping / PipeSupport status from PDMS data (3D-Model).

  15. #2 – Present data in a way that ”makes sense” Make ad-hoc pivoting overviews on ANY data, showing the result in a graph.

  16. #3 – Be adaptable to new requirements Time-phase other thing than Manhours. Some cultures are more concerned with “Trackers” • Safran is really good at reporting manhours (and cost), but the main contractor for the Kashagan project (Agip) is not very interested in manhours, but have a set of so called “Trackers” that implies counting number of planned and installed “items” (spools, meters of cables, etc), and showing this data in a time-phased (weekly or monthly) overview. • Norwegian companies have to adapt to this type of requirement to stay in control of the competition…

  17. #3 – Be adaptable to new requirements Adapt logic to external (ever changing) government reporting standards. Example: The 14pt Assessment Test

  18. #3 – Be adaptable to new requirements • f(x) Set up Transformation of data from ANY format to ANY OTHER format • Example to avoid…: A project double punches all Job cards from MIPS to WorkMate…

  19. #3 – Be adaptable to new requirements Find new ways to present information… Example: Project/production info shown in Area topology • Easy customization of what to show in each “matrix”, typically: Manhours Level 4 & 5 for this and next week). • Possibility: Each area can be assigned attributes such as surface area, and since the manhours is known for this week in any given area, this could be converted into a “work density number”, which again could be shown in color for each area (where red is very high density). Neighboring areas with red would indicate higher risk of accidents, and proactive measures could be taken to reduce risk, etc, etc..

  20. #3 – Be adaptable to new requirements Soft wiring of user interfaces and business logic on top of existing table structure. Example: A complete custom CTR application… • Highly configurable user interface and business logic: • CTR-IDs can be generated differently from one project to another. • Many reporting options:Time phased overviews, Tender pdf, interactive Pivot Charts, and more… • Pressing a button can generate the network in e.g Safran and deliverable objects in e.g IFS. • Possibility to compare CTR with live plan in e.g Safran.

  21. Thanks for your attention! • Please visit our exhibiton stand • to see how Proteus can help you • bring control to your data Or learn more at our website: www.quantumsolutions.no

More Related