| Excerpt | ||
|---|---|---|
| ||
learn about engagements and the projects that they are made up of |
| Tip | ||
|---|---|---|
| ||
You can now create, edit, and delete engagements, contracts, and projects through Projector Web. See Create Engagement Contract and Project Wizard. |
| Tip | ||
|---|---|---|
| ||
Watch the Project Setup and Configuration Best Practices Webinar, where our implementation consultants walk through the project configuration process highlighting the key aspects of setting up a new project. |
| Info |
|---|
Many core features of Projector are driven by engagements and projects. Without these constructs employees would not be able to enter time, enter expenses, or be scheduled. And without any reported data Projector cannot compile analytical reports, project financials, or push accounting data. So understanding engagements and projects is fundamental to understanding Projector. In Projector an engagement represents a contract. A project represents work that must be done to fulfill that contract. Engagements are either non-billable or billable. As you can easily surmise, non-billable work will never be invoiced while billable can be. For each billable engagement you will also specify the contract terms via Contract Line Items (CLI). A (CLI) represents a deliverable piece of that contract. Each CLI has a contract type of Time & Materials, Not to Exceed, or Fixed Price. You can have multiple CLIs per engagement to model complex contracts. For example, with an initial fixed price portion and then ongoing support on a T&M basis. The contract terms (T&M, NTE, FP) determine a number of downstream actions by Projector. For instance, how revenue should be recognized and how the client should be invoiced. Each engagement has a minimum of one project - otherwise you would never have a way of fulfilling the contract! Optionally engagements can have multiple projects. These projects should represent work that needs to be done to fulfill the contract. How your organization chooses to structure their engagement/projects is highly dependent on how you run your business. For example, you might have a one engagement / one project configuration. This keeps things simple. Alternatively you might have three projects for each engagement. One project for scoping, one project for implementation, and one project for followup support. Each project is also associated with a CLI. So reusing our previous example, your T&M support would be modeled as one project mapped to the T&M CLI. You should work with your Projector consultant to determine the best Engagement/Project structure for your organization. |
...
Engagements
To view an engagement:
...
- Have the cost center permission View Projects
- Be the engagement manager. Your allowed changes are determined by the engagement stage settings.
- Have the cost center permission Maintain Projects and Engagements
To create an engagement:
- Have the cost center permission Create Projects and Engagements for at least one cost center AND
- At least one project stage is set to Users with Permissions can Create New Projects
...