Each location must maintain their product (for specific campus reporting solution through example, a needs) upgrades, patches and data implementations. Campuses have warehouse)) used nVision, sqr reports or developed their own homegrown data warehouse to deliver reports to their campus community. Maintenance of these reports may be costly and require campus personnel and consultants to spend many hours reviewing results. Inherent to PeopleSoft are many X X available products and processes (if the costs (costs (i.e. additional available associated with associated PeopleSoft functionality) that are the upgrade/ with ongoing not included in the CMS baseline enhancement maintenance product version pushed out by meet the activities) SOSS. While not supported by capitalization SOSS, such products/ processes criteria may present a solution for a described in campus that negates the need for Section third party software or services (for example, generating ACH files from PeopleSoft Accounts Payable). Therefore, the campus may elect to further modify (customize) the baseline product version to include certain of these available products/ processes. These modifications result in additional functionality for the campus and are considered an upgrade or enhancement of the baseline product version. Maintenance costs associated with such modifications to the baseline product version are considered ongoing application maintenance activities and should be expenses as incurred.
Each location must maintain their campus reporting solution through upgrades, patches and implementations. Campuses have used nVision, sqr reports or developed their own homegrown data warehouse to deliver reports to their campus community. Maintenance of these reports may be costly and require campus personnel and consultants to spend many hours reviewing results. product (for example, a data warehouse)) specific needs) Inherent to PeopleSoft are many available products and processes (i.e. additional available PeopleSoft functionality) that are not included in the CMS baseline product version pushed out by SOSS. While not supported by SOSS, such products/ processes may present a solution for a campus that negates the need for third party software or services (for example, generating ACH files from PeopleSoft Accounts Payable). Therefore, the campus may elect to further modify (customize) the baseline product version to include certain of these available products/ processes. These modifications result in additional functionality for the campus and are considered an upgrade or enhancement of the baseline product version. Maintenance costs associated with such modifications to the baseline product version are considered ongoing application maintenance activities and should be expenses as incurred. X (if the costs associated with the upgrade/ enhancement meet the capitalization criteria described in Section X (costs associated with ongoing maintenance activities)
CH_13.00_Capital_Assets_Guide_Final.docx