Professional Documents
Culture Documents
Content
1.
Introduction .......................................................................................................................... 3
2.
Methodology ......................................................................................................................... 3
3.
1. Introduction
2. Methodology
ProjectCenter could be up and running in a few days, including the site definition and
any customization needed specifically in the project.
Our methodology consists on a 3 simple steps:
Activity Owner
Site activation
ProjectCenter
ProjectCenter
ProjectCenter
ProjectCenter
ProjectCenter
Enable
and
customize
communication templates
ProjectCenter
Review site
workflow
and
Client
2. Training Sessions
-
Prepare
project
procedure
manual
(ProjectCenter use under specific conditions
established by the Client)
Organize training
administrators
sessions
for
users
and
ProjectCenter
ProjectCenter/Client
ProjectCenter o Client
ProjectCenter/Client
ProjectCenter
serves as a visual information classification and at the same time allows for a more
straightforward document search.
-
Organizations:
Name*
Address
URL
Name*
Surname*
Email*
Project Logo or specific picture to be used for the main entry page of the project
(e.g.: project site picture, Client logo or the combination of all organizations logos).
This item is not mandatory but it can prove to be useful for those users
participating in several projects at the same time as they recognize immediately
the site they logged in.
Document status list (e.g.: For information, For approval, Approved, Approved with
Comments, Rejected, etc.). This list is available at the moment of publishing the
information and later on for edits purposes. Please see below an example:
Text
Date
Custom fields can be defined as mandatory which means the user will not be able
to finish the task without making the appropriate selection.
Project Workflows
Any process that needs to be tracked and monitored through online reports can be
enabled using the templates available in ProjectCenter. E.g.: RFIs, Change Orders,
Approvals, Inspections, Punch list, etc.
Please see below the templates available in ProjectCenter, they have different
actions, status and number of participants:
Examples:
o
Task assignment: it could use a simple workflow as the template and then
further customize adding the fields, reminders and assignees
ProjectCenter Project site set-up
Define which team members have the same Access level and group them
under one specific role. One person can belong to 1 role only. If users
cannot be grouped because they all have different access levels then an
individual permission setting is done.
N - No access: whoever is granted this role will not see the project
section, folder or subfolder where this right is selected
RO - Read Only: Users with this role will only view, print and markup through the online viewer
RD - Read Download: Users with this Role will be able to view and
download
RW - Read Write: Users with this role will be able to view,
download and upload
Folder Admin (FA): Users with this role will have full control over
the documents contained in the folder where this permission is
granted
Project Admin (PA): whoever is named project administrator can
act upon the project structure, its team, upgrade/downgrade
users, invite new team members. Moreover, these administrators
can enable/disable features across the project and enforce
workflow processes and specific rules. They are also the ones in
charge of sending the login credentials
The permission setting is easily captured and retrieved both for security
roles and individual users in the form of a matrix spreadsheet. Please see
below an example: