Scenario 8.0 Budget & Performance Tables

1. Scenario 8.0 Budget & Performance Tables “Demonstrate the tool’s ability to produce a variety of budget and performance tables/exhibits.”

2. 8.1 Demonstrate that the tool can generate various budget and performance tables/exhibits and how changes to data ripple through the database to the tables/exhibits in real time. BFEM Methods • Apply PMM measures to BFEM allocations within same table. Customers using Method • Treasury • State • Forest Service Demonstration • Treasury: 2014 Treasury CJ Bureau Performance and Budget Table (Section 3.1.1) • Forest Service: 2014 Forest Service Performance and Budget Table

3. 8.1 Demonstrate that the tool can generate various budget and performance tables/exhibits and how changes to data ripple through the database to the tables/exhibits in real time. Example: Treasury Performance Plan Table by Budget Activity (OIG)

4. 8.1 Demonstrate that the tool can generate various budget and performance tables/exhibits and how changes to data ripple through the database to the tables/exhibits in real time. Example: Forest Service Performance Plan Table by Budget Activity (OIG)

5. 8.2 Demonstrate the tool's ability to flag which measures should be displayed in the budget document's (Greenbook) performance tables/exhibits. BFEM Methods • Apply PMM Usages Customers using Method • Treasury • Energy Demonstration • Treasury: Show Measure Usage for one Measure, Change in CJ

6. 8.2 Demonstrate the tool's ability to flag which measures should be displayed in the budget document's (Greenbook) performance tables/exhibits. From PMM, assign a usage to the measure (budget).

7. 8.3 Demonstrate that the tool can support calculated columns (totals) and calculated rows (both subtotals and totals) within the generated tables/exhibits. BFEM Methods • Currently: • Crosstab Reports • Java Reports • Will be: XML Reports Customers using Method • All BFEM Customers, when applicable Demonstration • Treasury: C-1 Report • CNCS: Budget Summary Table

8. 8.3 Demonstrate that the tool can support calculated columns (totals) and calculated rows (both subtotals and totals) within the generated tables/exhibits. Example: Treasury OIG C-1, Budget Adjustments Table

9. 8.3 Demonstrate that the tool can support calculated columns (totals) and calculated rows (both subtotals and totals) within the generated tables/exhibits. Example: CNCS Budget Summary Table

10. 8.4 Demonstrate that the tool can support complex table/exhibit formatting requirements (e.g., table orientation, format as number or percent, bolding/italicizing specified text, use of + and – symbols for delta/change columns, use of brackets around numbers where specified, inclusion of spark lines, etc.). BFEM Methods • Currently: • Crosstab Reports • Java Reports • Will be: XML Reports Customers using Method • All BFEM Customers Demonstration • State: Instant Rack Up Report • Treasury: President’s Budget by Function Table for the BIB

11. 8.4 Demonstrate that the tool can support complex table/exhibit formatting requirements (e.g., table orientation, format as number or percent, bolding/italicizing specified text, use of + and – symbols for delta/change columns, use of brackets around numbers where specified, inclusion of spark lines, etc.). Example: State Instant Rack Up Report: color, multiple fonts, parentheses

12. 8.4 Demonstrate that the tool can support complex table/exhibit formatting requirements (e.g., table orientation, format as number or percent, bolding/italicizing specified text, use of + and – symbols for delta/change columns, use of brackets around numbers where specified, inclusion of spark lines, etc.). Example: Treasury President’s Budget by Function: color, shading, %, parenthesis

13. 8.5 Demonstrate that the tool can support the inclusion of footnotes tied to a specific number within a table/exhibit. BFEM Methods • Currently: • Crosstab Reports • Java Reports • Will be: XML Reports Customers using Method • State Demonstration • State: Use of footnotes in table.

14. 8.5 Demonstrate that the tool can support the inclusion of footnotes tied to a specific number within a table/exhibit. Example: Footnotes used in State table.

15. 8.6 Given that columns may change from submission to submission, demonstrate and/or discuss how tables/exhibits are managed to handle last minute requirement changes. BFEM Methods By Customer or through Jira Process: • Currently: • Crosstab Reports • Java Reports • Will be: XML Reports Customers using Method • All BFEM Customers, when applicable Demonstration • CNCS: Change a Column Heading via Report Hierarchies • Treasury: JIRA for Java Report

16. 8.6 Given that columns may change from submission to submission, demonstrate and/or discuss how tables/exhibits are managed to handle last minute requirement changes. Example of a Jira Ticket: Jira Tickets track requested client changes for developers. They are managed by the client’s Customer Manager. Jiras are used to manage development expectations as part of the implementation project plan and maintenance (weekly status meetings, etc).

17. 8.6 Given that columns may change from submission to submission, demonstrate and/or discuss how tables/exhibits are managed to handle last minute requirement changes. Example: CNCS Budget Summary Table: Change column heading/budget set references using Report Hierarchies.

18. 8.7 Demonstrate and/or discuss how the tool supports the addition of a new table/exhibit not previously defined in the Greenbook, Budget-in-Brief (BIB), or Annual Performance Plan & Report (APP&R). BFEM Methods • Insert table tag Customers using Method • Treasury • State • DHS • ACF • CNCS • House of Reps • USAID Demonstration • Treasury: Add tag into doc template and run.

19. 8.7 Demonstrate and/or discuss how the tool supports the addition of a new table/exhibit not previously defined in the Greenbook, Budget-in-Brief (BIB), or Annual Performance Plan & Report (APP&R). Example: The table tags below reference two versions of Treasury’s 1.1 Appropriations Detail Table (one including an Above Guidance Request column). The analyst formatted the doc template so that the appropriate table would run based on the Bureau’s need to include or exclude the Above Guidance Request information.