In the Services module, buyers use what are called Statements of Work, or SOWs, to define the projects scope, timeline, deliverables and costs for necessary services to be completed. SOWs ensure payments are made upon completion of certain project milestones, such as when products are delivered, and can include SOW Workers across different roles and tasks within the project.
There are 3 methods for defining a statement of work in SAP Fieldglass:
- buyer-defined,
- supplier-defined, or
- through collaboration between both parties.
WorkingNet chooses the collaborative approach, with both WorkingNet and their supplier providing input and reviewing the scope and terms outlined in the SOW.
Here’s how a Statement of Work for a typical project at WorkingNet would flow through SAP Fieldglass using the collaborative approach.
Procure
| Create SOW | Mavis initiates the creation of the statement of work. She will input the details of the project, including the tasks (called Characteristics in SAP Fieldglass), timeline, number of workers needed, deliverables, and costs, among other details. |
| Review/Accept SOW | Sheila, from re:CrewIT, would acknowledge receipt of the SOW. Further negotiation of the SOW terms and rates could occur with Mavis until an agreement is reached. |
| Accept & Submit SOW | When an agreement is reached, Mavis accepts the SOW and submits it to the PMO for review and approval. |
| Approve SOW | Brian, from WorkingNet’s PMO, evaluates the SOW prior to the SOW being sent to the supplier for their final acceptance. If further negotiation is required, the PMO would assist. |
| Add Workers | When the SOW is fully approved, Sheila adds workers to the defined SOW Worker Roles on the project and accepts the SOW. |
Engage
| Approve Workers | Mavis and/or Brian approves the workers and, if necessary, any onboarding activity items associated with SOW workers are completed. |
| Register in SAP Fieldglass | When the SOW workers are approved and cleared to start, they are invited to register in SAP Fieldglass. |
Now work on the project can begin. And from this point forward, both WorkingNet and re:CrewIT—the Buyer and Supplier—will use SAP Fieldglass to monitor and track progress and approve agreed upon milestones for payment once the work is completed.
Pay
| Mark Characteristics as Complete | As re:CrewIT completes the work for the various aspects of the project, Sheila marks the line item characteristics as complete on the SOW. |
| Submit Time and Expenses | During this time the worker(s) would submit time and expenses for the work done to that point. |
| Approve Completed Characteristics | When Mavis receives the notice that a characteristic line item has been marked complete, she reviews the details to confirm the work has been done, and then approves it. |
| Approve Time and Expenses | Time sheets and Expense sheets (and other project/worker characteristics) are also evaluated and approved by Mavis as well. |
| Invoices Auto-generated | Since WorkingNet has auto-invoicing enabled, SAP Fieldglass automatically generates and submits an invoice for each fully approved characteristic and/or time and expense sheet. If auto-invoicing was not enabled, Sheila would have to manually generate the invoices based on each approved line item. |
Once the invoice is processed, WorkingNet pays re:CrewIT (who pays the workers). The invoicing process can continue until all characteristics are marked complete on the SOW and re:CrewIT receives the final payment.
When all terms of the project are satisfied, the project is marked as completed.
