About the Schedule of Values (SOV)
An SOV sheet streamlines the process of invoicing for completed phases of a project. It works in conjunction with commit types of business processes, such as a purchase order. The Commit-types of business processes can be designed to automatically create an SOV sheet when they reach a designated step in a workflow.
Users can define one SOV sheet per Commit-type business process (such as a purchase order). The rows on the SOV sheet are automatically populated by the CBS or account codes in the Commit BP.
For SOV creation in Unifier, the user must set up the correct column structure for the SOV sheet so that the required columns and formulas are included for validating Summary Commitments (by CBS) and a Remaining Commits Balance. In the SOV structure, the user must define a formula for Remaining Commits Balance that reflects the amount of Commits, minus Spends. This column ensures the Spend BP line items are not overdrawn from SOV breakdown amounts.
The following lists the types of Schedule of Values (SOV):
- General Spends
- Payment Applications
- Summary Payment Applications
General Spends
Use the General Spends SOV type for any Commit Business Process and associated Change Commits and Spends/Invoices.
Payment Applications
Use the Payment Applications SOV type:
- In association with Commit and Spends Business Processes that are designed for payment applications. This allows direct entry of values in an SOV sheet, which are automatically added to a payment application.
- For invoicing at the CBS or breakdown level. Payment Applications auto-populate data to and from the SOV to manage balance-forward formulas. The breakdown is similar to the General Spends SOV sheet.
The General Spends and Payment Applications SOV types can show CBS information either by grouping CBS codes (CBS mode) or as individual line items from commits (Base Commits and Change Commits together). The information that SOVs display is dependent upon the design of the Base Commits.
Summary Payment Applications
The Summary Payment Applications SOV allows users to allocate cost to line items based on the line item type (Lump Sum or Unit Cost).
Use the Summary Payment Applications SOV type in association with Commit and Spends Business Processes (BPs) that are designed for Summary Payment Applications SOV type.
The Summary Payment Applications sub-node will be available under the Schedule of Values node (Project/Shell > Cost Manager node > Schedule of Values node) only if a Base Commits, or Change Commits, of SOV type Summary Payment Applications is deployed in uDesigner.
Note: An error will occur after clicking Unit Cost if you do not the Item Unit Cost and Item Quantity (uuu_unit_price and uuu_Quantity) fields in the Detail form design.
Last Published Monday, June 3, 2024