20 24.10 Multiple Base Commits with Payment Applications and SOVs

Administrators can now include more than one Base Commit BP with Payment Applications and Schedule of Values (SOVs) in projects/shells. Multiple Base Commit BPs can be added:

• Manually in an specific project/shell
• Using shell templates

  In this case, the Payment Applications node displays when you go to: [Shell Template], select Cost Manager, select Schedule of Values, and then select Payment Applications

• From a shell template to a shell

  In this case, a new <Base Commit BP name> - SOV node displays in when you go to: Access Control under Schedule of Values, and select the Payment Applications node in the shell when user permissions are provided to display the existing SOV log to Create/Update Structure.

Users can now:

• Create multiple Base Commit records that create different payment application SOVs
• Create multiple Change Commit records that update different payment application SOVs
• Create multiple payment application records that update different payment application SOVs
• Create multiple payment application SOV structures
• View new SOV nodes that display the log of the Base Commit records that creates payment application SOV structure

  In the User Mode Navigator for shells, an additional node, <Base Commit BP name> - SOV, displays.

  For example, both nodes display:

  • Schedule of Values followed by Payment Applications
  • <Base Commit> - SOV (in the User Mode Navigator for project/shell)

  If User Mode Navigator is not deployed, a new node, <Base Commit BP name> - SOV, displays under the Access Control node.

  For example, both nodes display:

  • Schedule of Values followed by Payment Applications
  • Schedule of Values followed by Payment Applications followed by <Base Commit> - SOV

Both the logs show the same SOV structure and commit records if there is only one active Base Commit BP that creates a PSOV in the shell.