The following is an overview of the steps needed to set up funding for use in projects and shells, plus the steps needed to set up the optional commitment level funding. Details for each step are in the sections that follow, unless otherwise noted.
Setting up company and project/shell funding
Before you begin. The fund attribute form can be designed in uDesigner. This will be used as the Fund Details window when adding new funds to the company funding sheet, or viewing fund properties. If your company does not design a fund attribute form, a simple default form is used.
Import and set up fund business processes. You can use business processes for fund allocations, fund assignment (also known as consumption; enabled on spends type business processes), and fund credits (also enabled on spends business processes). This step can be done at any point in this general procedure. Be sure you know which funding business processes you will be using for the project or shell before defining funding rules on the project or shell funding sheet.
Step 1: Import and deploy the fund attribute form. Once imported, the fund attribute form becomes the Fund Details window in Unifier, used to create and manage fund codes in the company funding sheet. When designing the form, you can also design the fund picker, which is used to add funds to business processes and project/shell funding sheets, as well as "Find" on the picker. This is an optional step. If you do not create a fund attribute form, a default fund code form and fund picker will be used.
Step 2: Create and set up the Company Funding Sheet (User Mode). You define the funds in the company funding sheet, which can then be used for funding project or shells. Only one company-level funding may be created per company. All project or shell funding sheets refer to the company funding sheet.
Step 3: Create and set up Project/Shell Funding Template (Administration Mode). The funding template is used to create project or shell funding sheets.
Step 4: Create and set up the Project/Shell Funding Sheet (User Mode). The project or shell funding sheet is based on the funding template. (You can also define the project/shell funding sheet in a project or shell template.) The funding sources available for the project or shell are defined in the company funding sheet.
Step 5: Define funding assignment rules. Funding assignment rules can be defined in the project/shell funding sheet or the funding template (or both). You can also determine the order in which to consume funds if you will be using automatic fund assignment from business processes. (This step can be done any time after creating the funding template. If you define assignment rules in a template, they will be carried over to the sheets created from them.)
Additional steps: Create funding rules in the rules engine. You can create funding rules in the rules engine that can help you manage your funds and fund balances. The most common rule is to keep your company fund balances from becoming less than zero. Configure permissions. As you create funding sheets and set up funding business processes, remember to configure the permissions to go with them. Refer to the Unifier Reference Guide for funding permissions.
Setting up commitment level funding
Commitment level funding is optional. To set it up, first set up funding in the project or shell, then follow these additional steps.
Commitment funding works in conjunction with general spends and payment applications SOV sheets.
Before you begin. Be sure that the project/shell funding has been set up, with funds allocated and available on the project/shell funding sheet. Data sources are available for project/shell funding sheets (and company funding sheets) to track funding that is assigned for specific base commits. Also, be sure you have added the data source "Scheduled Value" to the SOV structure for the project or shell. Commitment funding uses the SOV to track base commit and change commit amounts, and uses the Scheduled Value column to track remaining balances.
Import and set up business processes for commitment funding. In addition to business processes that are used for project/shell funding, you can design business processes for use with commitment funding. In uDesigner, commitment funding is enabled on the base commit (and linked change commit); automatic generation of an SOV must also be enabled. Then, the ability to create (and later access) the commitment funding sheet can be enabled on the form. Be sure the spends business process that is linked to the base commit has been enabled to consume funding.
Step 1: Create and set up Commitment Funding Template (Administration Mode). This template is used to create a commitment funding structures in the project or shell, which in turn is used to create the individual commitment funding sheets for each base commit record. You can add columns to the template, but not rows.
Step 2: Define funding assignment rules. This is done in the Assignment tab of the Properties window. Assignment rules can be defined in the commitment funding template, structure or sheets. (This step can be done any time after creating the funding or commitment funding template. If you define assignment rules in a template, they will be carried over to the structure and sheets created from them.)
Step 3: Create Commitment Funding Sheet Structure (User Mode). Structures are created at the project level in user mode from a commitment funding template. When commitment funding sheets are created from base commit records, this default structure is used. You can also create a commitment funding structure in a project or shell template.
Step 4: Create individual commitment funding sheets. This is done automatically the first time you click the Funding button on a base commit business process form (this button becomes available on specific steps as designed in uDesigner). After creation, the commitment funding sheet is available for viewing or modification by clicking the Funding button on the base commit or associated change commits, or from the Commitment Funding log itself.
Additional steps: Configure permissions. Module permissions must be granted to the commitment funding template, to the commitment funding sheet in a project or shell template (if using), to commitment funding sheet in a project or shell (in order for the node to be visible). In addition, record level permission must be granted to individual commitment funding sheets. By default, the owner of the base commit will have permissions to the sheet. Additional users must be granted view or edit permissions. Refer to the Unifier Reference Guide for general funding permissions. Sheet permissions are granted User mode. Additional assignment details. After the commitment funding sheet and SOV sheet are created, additional funding assignment details can be defined on the Fund Assignment window (accessed from the SOV sheet or commitment funding sheet).