One of the first decisions to be made with P6 is how it will be set-up. Unlike most software, this one will not be the most intuitive. There are also different ways and combinations to deploy P6, but it will all depend on the business needs – both short term and long term. Project managers should look at the priority placed on planning and scheduling and how reliant they should be on these systems. As well, with more projects being added onto the workload, you will need a centralized solution for organizing all this data. Some questions to consider before deciding how the P6 infrastructure should look like:
- How many users will need access now and how many users will need to be added on in the future (if this can be forecasted)?
- Do the users need simultaneous and centralized access to the same projects, or will they be independently working on their own files?
- Will the users require off-site access to P6 for updates if they are often doing field work?
- Do I have a plan in place to accommodate the reconfiguration of P6 as its usage grows and expands further into my organization?
The main requirement for P6 is a database server. Depending on your answers to the question above, you might end up natively installing everything on one user’s laptop. Or, you may decide that it may be less hassle to set-up internal hosting on the company server now rather than later. Whatever the preference is, you want to make the fittest choice first as the installation can be lengthy.
We’ve made the process a little more visually comprehensive by providing a diagram of how the system would look like. Of course, not all sections of the diagram need to be deployed, but this document should help give you the bigger picture of what P6 should look like in your company, in IT terms:
The post THE P6 EPPM ARCHITECTURE: SIMPLIFIED appeared first on CPM Solutions.