ProjectTeam Training Resources

When you create a new record, by default you are the only user that has access to that record. You can create drafts and keep them private until you are ready for them to be shared.

Share Groups and/or Users that are a part of a workflow will automatically be shared forms as they are assigned a step in the workflow.

Once a record is shared, it can no longer be deleted but can be obsoleted and a user or share group can be halted from seeing any future changes.

Project Additions, Deductions and Allocations are managed by the Change Notice Process in Budget Amendments. Project team members from SSR have access to start a Budget Amendment by filling out the Origination Section and starting the Change Notice workflow.

The workflow steps send the Change Notice to the Estimator, Scheduler, and Cost Controller for input. Each of these roles has a section to complete in the form. Once the Cost Controller passes their workflow step, the workflow continues to the approval phase. The PC Manager, Commercial Manager, Engineering Manager, and Project Manager each pass their workflow step as approval of the change.

The Purchase Request (PR), Recommendation for Award (RFA) and the Limited Notice to Proceed (LNTP) approval processes are all managed in the Contracts form. The Procurement Team will create the form, enter the applicable data in one or more of the process sections and then start the corresponding workflow(s).

The workflow follows the same steps for each of the approval processes. The first step sends the record to the Project Manager (PM) for approval. When the PM passes the workflow, the SAP Administrator is notified with instructions to run the applicable Merge Template to submit to SAP. If approved, the SAP Administrator will pass the workflow which notifies the Procurement Team.

Once you've established Contracts in ProjectTeam.com, you can start creating Change Orders against those Contracts. The workflow follows the steps for the Change Order approval processes. The first step sends the record to the Project Manager (PM) for approval. When the PM passes the workflow, the SAP Administrator is notified with instructions to run the applicable Merge Template to submit to SAP. If approved, the SAP Administrator will pass the workflow which notifies the Procurement Team.

This guide provides steps for how to manually create a new drawing, view the drawings log, edit a drawing form, manually create a new drawing package, create a new drawing package using text extraction, edit a drawing package record, and download or upload drawing documents from a drawing package.

Revisions are made to an individual Drawing. If a new Drawing Revision should be a part of an existing Package that the previous revision is linked to, the revision can be switched out in the Package.

Drawings that you added or have been shared with you can be viewed from the Drawings logged.

Document Control starts the applicable Engineering Review Workflow(s) which sends an email notification to the Engineer. The Engineer will review the Request for Information and provide the Response and then Pass the workflow.

This guide provides steps for how to create a new indirect cost record and edit an existing indirect cost record.

ProjectTeam.com allows you to easily create and manage all of your Payment Applications in one system. The first step in creating a new Payment Application is to choose an existing Contract, and therefore, can only be created after a contract has been established. Payment applications allow you to bill against Schedule of Value items in your Contract and Change Orders associated with that contract.

RFIs are processed via the Request for Information Workflow. External users and SSR users have access to start the workflow. Step 1 of the workflow goes to Document Control for review. The passed step keeps the workflow (Step 2) in Document Control’s court with instructions to start the applicable Engineering Review workflow(s) and wait for response(s) before passing Step 2. Step 3 returns the RFI back to the workflow Initiator. The initiator of the workflow must pass the step to confirm receipt and mark the workflow complete.

Document Control starts the applicable Engineering Review Workflow(s) which sends an email notification to the Engineer. The Engineer will review the Request for Information and provide the Response and then Pass the workflow.

Step 1 of the Request for Information (RFI) workflow goes to Document Control for review. The passed step keeps the workflow (Step 2) in Document Control’s court with instructions to start the applicable Engineering Review workflow(s) and wait for response(s) before passing Step 2. Step 3 returns the RFI to the workflow Initiator. The Initiator must pass the step to confirm receipt and mark the workflow complete.

In ProjectTeam, submittals are separated into two form types; Items and Packages. Both form types are accessed from the same “Submittals” form.

A Submittal Registry can be set up in Submittal Items or you can add each one individually. After the record is created, the Submittal document should be uploaded to the Attachment panel of the Item record.

Items are grouped into a Package and submitted for review. External users and SSR users have access to start the Submittal Package Review Workflow. Step 1 of the workflow goes to Document Control for review. The passed step keeps the workflow (Step 2) in Document Control’s court with instructions to start the applicable Engineering Review workflow(s) and wait for response(s) before passing Step 2. Step 3 returns the Package back to the workflow Initiator. The initiator must pass the step to confirm receipt and mark the workflow complete.

Document Control starts the applicable Engineering Review Workflow(s) which sends an email notification to the Engineer. The Engineer will review the Submittal Package and each Item in the package and provide the Reviewer Action, Action Notes, and check the Closed checkbox, if applicable, before they Pass the workflow.

Submittal Items are grouped into a Package and submitted via workflow. External users and SSR users have access to start the Submittal Package Review Workflow. Step 1 of the workflow goes to Document Control for review. The passed step keeps the workflow (Step 2) in Document Control’s court with instructions to start the applicable Engineering Review workflow(s) and wait for response(s) before passing Step 2. Step 3 returns the Package back to the workflow Initiator. The Initiator must pass the step to confirm receipt and
mark the workflow complete.