As MIT learned from evaluation of vendor products, MIT processes were not well matched to SAP R/3 in many areas, due to unique processes at MIT and within the DLCs. For example, most of DLCs had their own processes and policies, which they managed autonomously. This meant it was hard to forge a compromise among all DLCs wherein they agreed to use a single standardized process for a specific type of work. Moreover, MIT allowed so many exceptions to central administrative rules that it could not point to overarching processes that were in place. Also, the fundamental challenge for MIT was the lack of understanding of business functions of SAP. Moreover, the university used the legacy system and operating processes for at least two decades. Although the ERP system required a change of perspective and new training for staff, MIT wanted to retain familiarity in the system as much as it could. Although SAP implementation stemmed from a desire to reengineer the university’s management reporting system, project managers decided it was necessary to significantly customize the software to fit unique needs at the general.