What's Changing?

T

he F$M Project will change the way users perform financial management: from inputting proposals, to statusing purchasing requests, to closing out projects, to generating financial reports. The goal is to deliver a set of integrated, streamlined, and improved Financial service solutions.


What it Means for You | Get Engaged | Project Scope | Key Considerations

Note - some links below and at left will require LDAP login.

What Does it Mean for You?

| Download a printable version of What It Means for You |  Download the Brief Slide Presentation |

Reporting Buying & Paying Proposals LETS Travel TREX


Get Engaged:

User Engagement


Project Scope:

Service Areas:

The Service Areas addressed by F$M are depicted below. Click on a Service Area to learn more about what’s changing.

| Download a detailed description of F$M Service Areas |

F$M Service Areas DOE Funds & General Accounting Work for Others Buying & Paying Effort / Labor Accounting Travel & Conferences Reporting / Data Analysis

During the Analyze stage of the project, the F$M team collected a comprehensive list of requested functionalities for the new system. Not all of these requests are cost-effective to implement, so they were prioritized (High, Medium 1-2-3, or Low) based on impact, business criticality, and suitability of workarounds.

The majority of the requested functionalities were categorized as High and Medium 1, and are in scope for the project. Designs for these will be posted as available. In addition, the Medium 2 priority requests will be designed, and if budget allows, would be built in priority order, taking into account the rankings determined by the F$M Stakeholder Committee.

| Download a list of functionalities not in scope |


Key Considerations:

  • Adhering to the F$M Governance
  • Covering the end-to-end process where possible
  • Focusing on best practices and what’s best for Berkeley Lab as a whole
  • Aiming to meet short term needs, but including flexibility for longer-term viability
  • Eliminating the need for shadow systems and processes
  • Making adjustments/corrections in source systems
  • Capturing key information to support robust reporting and decision making