Case Studies.
Add Case Study
Our Case Study database tracks 18,927 case studies in the global enterprise technology ecosystem.
Filters allow you to explore case studies quickly and efficiently.
Download Excel
Filters
-
(3)
- (3)
-
(1)
- (1)
-
(1)
- (1)
- (1)
- (1)
- (1)
- (1)
- (1)
- (1)
- (3)
- (1)
- (3)
Selected Filters
|
Pulaski Bank's Efficient Issue Tracking System: A Case Study
Pulaski Bank, a customer-centric financial institution, was facing challenges in tracking and resolving issues that arose during the pre-close, pre-shipping, or suspense load processes. The bank had phased out its existing issue tracking system and was in need of a new, efficient system that would provide visibility and ownership to each issue, ensuring timely resolution. The bank required a system that was tailored to their specific needs and could streamline the process of issue tracking and resolution. The absence of an efficient system was potentially affecting the bank's customer service and overall operational efficiency.
|
|
|
BEMAS Software's Transition to SaaS Architecture: A Case Study
BEMAS Software, a leading provider of technology solutions for benefits administrators, was faced with the challenge of migrating their product line to a Software as a Service (SaaS) architecture. The existing technology solution was written in Visual Basic with a SQL Server database, which was not compatible with the SaaS model they aimed to adopt. The company needed a new technical architecture that could support the SaaS model for their software product line. The transition was crucial for the company to increase revenue and acquire new customers. However, defining the goals for the SaaS model and performing a gap analysis was a complex task that required expert intervention.
|
|
|
Enhancing Business Operations through Server Redundancy: A Case Study on MECS
MECS, an environmental engineering process technology company, was facing a significant challenge with their critical production server. The server was running software that could no longer be maintained, and there was no one left on staff who understood how the software was built or how to perform a restoration in case of failure. This situation posed a significant risk to the company's operations as the business users had a high dependency on this server. A critical application that was essential for the business operations would not be available if the server failed. The company needed a reliable server and available application to operate the business effectively and efficiently.
|
|