Managing the Characteristics Libraries

Objectives

After completing this lesson, you will be able to:
  • Explain what Events and Management Events represent and describe how Schedules affect Invoices and payments in SAP Fieldglass.
  • Configure a Fee Library.

Characteristics

Adding characteristics is the fourth step in the creation of an SOW.

The bulk of an agreement between a buyer organization and the service provider is comprised of various activities that result in payment or event tracking. These activities are referred to as Characteristics, and they define the specifics of a project, such as costs, timelines, and milestones.

Characteristics can be added manually to an SOW during its creation, but to simplify the creation process a library of pre-configured characteristics can be added to an SAP Fieldgass tenant through the admin menu. This is an entirely optional step in the tenant configuration, but for fees or events that are regularly used, it can streamline the process for users creating an SOW. It can also facilitate more accurate reporting if the same characteristics are used across multiple projects, for organizations who include characteristic types in their analytics.

Within SAP Fieldglass, there are a variety of these activities:

Characteristics Libraries
1

Events - Milestones that incur costs, such as project deliverables. The Event Library allows Administrators to create and maintain a collection of commonly used events for use within the SOW module and SOW Bid module. Events may be created for items that require payments to be made upon the completion of specific milestones or the delivery of certain work products.

2Schedules - Predetermined dates or events that trigger invoices To review the details of a user role, select the link of the role in the Name column. The Schedule Library allows Administrators to create and maintain a list of schedules for use within the SOW module and SOW Bid module. Schedules may be created for items that require payments that will be made to the supplier according to predetermined dates Examples include monthly payments, a final payment, or set fees to be paid on specific dates.
3Fee Definitions - Items that require payments to be made on a recurring basis, such as equipment use costs The Fee Library allows Administrators to create and maintain a collection of commonly used fees for use within the SOW modules. Fees may be created for items that require structured payments to be made on a regular or recurring basis. Fees must be defined in the Fee Library before they can be added to SOW templates. They can be added when creating an SOW from a template, and they can be copied from the library.
4Management Events - Milestones that do not incur costs, such as status reports. The Management Event Library allows Administrators to create and maintain a list of management events for use within the SOW module.

Configure a Fee Library

While creating the SOW for WorkingNet’s data center expansion project, Patricia, the Director of Networking and Network Security for WorkingNet, manually added a fee to capture the costs of QA testing. After completing the SOW, she realized there were other fees she could add and that might be used across other projects.

She asks you, the SAP Fieldglass administrator for WorkingNet, to add a new fee to capture costs to be paid out at 75% completion of a project.

Log in to track your progress & complete quizzes