The Business Process Alignment (BPA) sessions start up again this afternoon (following a weeklong break) and many SMEs out there have been hearing the acronym “CEMLI” tossed around by the Ciber and ctcLink project team members throughout the sessions.
What is it? Well, it’s not an electric company in Seattle (you’re going to Google that, aren’t you?). It certainly doesn’t stand for “Can Every Monday Last Indefinitely?” And, sadly, it’s not a beach in North Wales.
CEMLI is an acronym that loosely translates to “additional work” (you’ll see why below). Any requirement to our new system that cannot be met by the Out of the Box (OOTB) functionality is being tracked and referred to as a CEMLI.
C = Conversion
For conversions, the vendor comes to the table with a stock set of processes that pick up data values from a template and convert it into the proper values, in the proper order. This portion of the work is largely a technology effort.
E = Extension
These are a higher cost work effort to ‘develop/design’ custom code to support business processes, but these are typically large coding and testing efforts. While these do not involve digging into the PeopleSoft code itself, it is a long-term commitment to support custom code. Often these are called ‘bolt-ons’ in the Oracle vernacular.
M = Modification
These are the most costly and highest risk changes. These are changes being made directly in the PeopleSoft code. They have the greatest long-term cost. Our aim is to avoid these types of changes if possible.
L = Localization (not used)
Localizations are related to making the PeopleSoft application work for a specific country. We will not need this for ctcLink.
I = Interface
These are all the interfaces cited in our RFP that will be needed moving forward. We will be evaluating these to ensure they are still needed given the new functionality in PeopleSoft that might replace this need with PeopleSoft out-of-the-box processes.
Reporting is also included in the list of items that warrant a CEMLI, though it does not have a letter in the acronym, all work associated with changes needed to develop reports that are not delivered out of the box will also be tracked as a CEMLI.
Any time within the project a CEMLI is identified it translates directly into hours. Those hours within the project are to generate Functional Design Documents, Technical Design Documents and testing processes. The ctcLink_Principles tell us that we are to limit changes to the system to only those most critical for our success. As the team works through the CEMLI lists, both current and long-term costs will be evaluated for each one on the list.