|
Security
|
 |

|
Users |
| |
|
Each Member Company manages and configures its own Users from this module. ProjectVillage™ is licensed on concurrent usage, not configured seats. So a Member Company can add and remove Users independent of licensing liability and without a phone call to us. |
 |

|
Groups |
| |
|
The Groups module is used to create collections of Users from both within and outside one's Member Company. Security permissions can then be granted to a Group and the Users contained by the Group inherit those permissions. |
|
Administration
|
 |

|
Companies |
| |
|
The Companies module serves as a master directory of Companies for lookup, reference or assignment to project teams and documents. Each Company supports any number of Locations (each with its own street and mailing address), any number of Contacts and any number of Phones.
In addition, each Company provides a compliance section that integrates with the Subcontracts module to provide an overview of workers compensation and general liability coverage on a project-by-project basis. |
 |

|
Projects |
| |
|
Projects are created and their basic properties are managed in the Projects module.
From this module, a Project can be linked to a Super-Project. When multiple Member Companies each link a Project to the same Super-Project, permissions for modules and documents can be granted to Users across those Member Companies. This forms the basis of the patent pending Enterprise Community™™. |
 |

|
Workflow |
| |
|
The Workflow module contains all of the workflow Paths, by document type, that have been created within a Member Company. This module provides a user interface from which Paths and their components can be created and modified allowing a Member Company to design and enforce business process.
For more information on workflow design and how it works in ProjectVillage™, see Solutions>Workflow Design. |
 |

|
Reports |
| |
|
The Reports module is used to manage Crystal Reports templates. Templates can be downloaded for customization and uploaded again for deployment.
ProjectVillage™ provides a generic template for each report type that provides administrators with a starting point. From the generic template, a Member Company can do as little as add a logo or go as far as adding complex formulas, conditional formatting or grouping and aggregate summaries. |
 |

|
Time Cards |
| |
|
Timecards are workflow documents that include line items to distribute time spent across Projects and Cost Codes.
The Timecards module provides access to a single user's Timecards or, security permitting, all user's Timecards. From this module, Individuals can create and submit Timecards while administrators can aggregate company wide time data by Project, Cost Code, User, weekending, etc. |
 |

|
Lists |
| |
|
In the process of working in ProjectVillage™, users encounter a number of choices in the form of drop down lists or collections of checkboxes and option buttons. The values found in the majority of these lists are customizable from this module.
For instance, Transmittals in ProjectVillage™ have a property called Ship Method in which users choose from a number of items on a drop-down list. The items that appear on this list can be added, modified and deleted from the Lists module. |
 |

|
Account |
| |
|
The Account module provides an interface for a Member Company to manage its account with ProjectVillage™ including setting a maximum concurrent user limit and viewing currently active users within its account. |
 |

|
Cost Codes |
| |
|
The Cost Codes module provides a customizable master list of job cost codes for assignment to a variety of documents and cost distributions. |
 |

|
General Ledger |
| |

|
The General Ledger module provides a customizable chart of accounts for non-job cost distributions. |