Case Study
Capital Expenditure Request Solution
Customer Overview
Their existing Capital Expenditure Request (CER) process had a number of shortcomings. The level at which a CER must be approved varies based on the associated dollar amount, and some CERs were being approved at improper levels. Since the process was not self-contained, CERs were exchanged via email or hard copy. As a result, the process was opaque, inefficient, and slow, with approval times dragging into months. Due to the process’s isolation, CERs could not be tied back to the yearly budgets with which they were associated, nor was there a way to track actual expenditures relative to the approved amount or to flag over-budget projects.
Their existing Capital Expenditure Request (CER) process had a number of shortcomings. The level at which a CER must be approved varies based on the associated dollar amount, and some CERs were being approved at improper levels. Since the process was not self-contained, CERs were exchanged via email or hard copy. As a result, the process was opaque, inefficient, and slow, with approval times dragging into months. Due to the process’s isolation, CERs could not be tied back to the yearly budgets with which they were associated, nor was there a way to track actual expenditures relative to the approved amount or to flag over-budget projects.
Download Case Study
"*" indicates required fields
A Sneak Peak in the Case Study
We created an automated approval process that specifies approval requirements according to business rules and disallows improper approval attempts. By automating it within a single system, we created a streamlined, cohesive process that we anticipated would reduce approval times from months to days. Because the client is a holding company with three separate lines of business, certain process steps are required across all three lines, while others are unique to a particular line. We designed and implemented the system accordingly: common requirements are “baked in” while the system’s flexibility accommodates both LOB-specific process features and future process modifications.
