Exploring the Standard SOW Workflow

Objectives
After completing this lesson, you will be able to:

After completing this lesson, you will be able to:

  • Contrast SOWs that are Buyer Defined, Supplier Defined, and Buyer/Supplier Collaboration.
  • Explain how redlining functionality supports collaborative SOW development.

Defined By and Collaboration

One of the initial decisions that the creator of an SOW must make relates specifically to how the scope of the SOW will be defined. SAP Fieldglass provides three options:

  1. Defined by the buyer,
  2. Defined by the supplier, or
  3. Collaboration between buyer and supplier.

If a Statement of Work is set up to support collaboration between buyer and supplier, the workflow will provide opportunities for both parties to provide input and review.

Comparing Versions of an SOW

When suppliers and/or buyers make changes to the SOW in a collaborative workflow, those changes are visible using redlining: a visual form of tracking changes seen on the SOW by both parties. Different versions of the SOW can be compared by selecting the View Versions option on the Action menu. Data from the original SOW will appear as strikethrough text, and the corrected data will appear below that.

Defined rules on the Statement of Work determine how changes can continue to be made if needed. For example, the Statement of Work becomes a living and ever-changing document as suppliers continue to add line items to support any unplanned work not identified initially, if the structure of the SOW allows and based on configured approval groups.

Log in to track your progress & complete quizzes