SUPPORT CENTER, INC. LUKE LINDQUIST BUS550. COMPANY OVERVIEW Call Center with $400M annual revenue 190 Employees Created from the merger of 3 other call.

Slides:



Advertisements
Similar presentations
Enterprise Resource Planning It is not the end, it is just the beginning Mary Avery Finance Manager Nebraska Auditor of Public Accounts 2006 Joint NSAA/NASC.
Advertisements

Chapter 12 The Revenue Cycle: Sales to Cash Collections Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 12-1.
Visualize Success 2011 Ed White Professional Services Visual South, Inc. Credit Card Sales Processing Options.
1 iCaller A Call Center Solutions. Why a Call Center Solution is required ?
The Human Resources Management and Payroll Cycle
The Database Environment
DEPARTMENT OBJECTIVES 1. To Identify and deploy information technology to meet business objective at CKPL. 2.To Provide support to users for systems usage.
ICASAS305A Provide Advice to Clients
The Human Resources Management and Payroll Cycle
GAJAH ANNUAL REPORT 2015 | 1 Business Process Management Meghan Atkins Lohith Bangalore Omprakash John Doyle Rebecca Mazur.
RFID Shelving ADD Presentation: 19 Mar 2007 Guy Shtub Idit Gershoni.
Chapter 12 The Revenue Cycle: Sales to Cash Collections Copyright © 2012 Pearson Education 12-1.
SE 464: Industrial Information systems Systems Engineering Department Industrial Information System LAB 02: Introduction to SAP.
E-Commerce: The Second Wave Fifth Annual Edition Chapter 12: Planning for Electronic Commerce.
© 2007 by Prentice Hall 1 Chapter 1: The Database Environment Modern Database Management 8 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred R. McFadden.
Computer Security: Principles and Practice
Introduction to SAP R/3.
Enterprise Resource Planning, 1st Edition by Mary Sumner
CRM Ahmed Khadr February 14, 2002 OISM 470 W. Agenda The CRM hype! What is CRM? A Definitive Definition The Five Views of CRM A CRM Brainstorm Let’s Talk.
Brian Bradley.  Data is any type of stored digital information.  Security is about the protection of assets.  Prevention: measures taken to protect.
Development and Quality Plans
Overview of Transaction Processing and Enterprise Resource Planning Systems Chapter 2.
DBMS1 Database Management System (DBMS) Introductory Concepts Week-1.
Chapter 1: The Database Environment
Barracuda Networks Confidential1 Barracuda Backup Service Integrated Local & Offsite Data Backup.
Introduction to Databases Transparencies 1. ©Pearson Education 2009 Objectives Common uses of database systems. Meaning of the term database. Meaning.
Compliance System Validation - An Audit Based Approach December 2012 Uday Gulvadi, CPA, CIA, CISA, CAMS Director - Internal Audit, Risk and Compliance.
Database Systems: Design, Implementation, and Management Ninth Edition
Chapter 1 Database Systems. Good decisions require good information derived from raw facts Data is managed most efficiently when stored in a database.
Understanding Back-End Systems Chapter 9. Front-End Systems Front- end systems are those processes with which a user interfaces, and over which a customer.
BUFU Enterprise The Future Is NOW!! Company Overview Team – > – Systems Analyst – >– Business Consultant – Chris Vance – Network Analyst – >– Project.
Lesson 8-Information Security Process. Overview Introducing information security process. Conducting an assessment. Developing a policy. Implementing.
Commercial Database Applications Testing. Test Plan Testing Strategy Testing Planning Testing Design (covered in other modules) Unit Testing (covered.
McGraw-Hill/Irwin Copyright © 2011 The McGraw-Hill Companies, All Rights Reserved Chapter 14 Enterprise Resource Planning Systems.
Computers & Employment By Andrew Attard and Stephen Calleja.
Elliott eOrders.Net Edward M. Kwang, President Rachel R. Locklair, Project Lead.
Transaction Processing System
GBA IT Project Management Final Project – “ FoodMart Corp - Making use of Business Intelligence” July 12, 2004 N.Khuda.
Maintaining a Mirrored Database Tips and Tricks by Paul G. Hiles.
Enterprise Resource Planning ERP Systems
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
CUONG NGUYEN PRIYA PAKHANAVAR RUSSELL ROBINSON RPC Hotels.
Electronic data collection system eSTAT in Statistics Estonia: functionality, authentication and further developments issues 4th June 2007 Maia Ennok,
Ali Pabrai, CISSP, CSCS ecfirst, chairman & ceo Preparing for a HIPAA Security Audit.
Chapter 1 Chapter 1: The Database Environment Modern Database Management 8 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred R. McFadden © 2007 by Prentice.
BEST GROUP CONSULTANTS Lesson Department Information System.
9 January 2006 MIS for CarRes User Group Meeting 1 Peter Havskov Christensen, M.Sc.
Support Center Inc. Mohammad Borhanpour 6/1/2014 BUS 550.
SECURITY OF DATA By: ADRIAN PERHAM. Issues of privacy; Threats to IT systems; Data integrity; Standard clerical procedures; Security measures taken to.
1 Database Systems Instructor: Nasir Minhas Assistant Professor UIIT PMAS-AAUR
Lesson 19-E-Commerce Security Needs. Overview Understand e-commerce services. Understand the importance of availability. Implement client-side security.
Database Systems. Role and Advantages of the DBMS Improved data sharing Improved data security Better data integration Minimized data inconsistency Improved.
Support Center, Inc. Author: Sue Conger University of Dallas Presented by: Christopher Murphy.
Disaster Recovery 2015 Indiana Statewide Payroll Conference Michael Ievoli-Client Support Specialist IV, Major Accounts September 16, 2015 Copyright ©
Electronic Design Change Process Paul Tobin Jr.- PKMJ Technical Services.
Thrdplace Social Networking Team #7 1. TRR Outline Operational Concept Overview System benefits to Customer 1.Introduction Demo of System Operational.
Chapter 15 The Human Resources Management and Payroll Cycle 15-1.
TM Asia & RHB Banka IT Blueprint Concept and Methodology of an IT Platform to Support an Exclusive Bankassurance Draft Version 1.0.
The Database Approach Muhammad Nasir
Identify & Prevent Duplicate Payments Presenter: Daniel Kimpton.
Introduction To DBMS.
Sales & Marketing Funnels
Audit Findings: SQL Database
Customer Relationship Management
Overview of Business Processes
Understanding Back-End Systems
IT OPERATIONS Session 7.
Enterprise Resource Planning, 1st Edition by Mary Sumner
The Database Environment
Enterprise Resource Planning Systems
Presentation transcript:

SUPPORT CENTER, INC. LUKE LINDQUIST BUS550

COMPANY OVERVIEW Call Center with $400M annual revenue 190 Employees Created from the merger of 3 other call center type companies Somerfield, Inc Specialized in 1 st party collections Charleston & Associates Specialized in 3 rd party collections Telecomm Sales, Inc Specialized in 1 st party telemarketing of various products SCI has since discontinued this part of their operations

COMPANY ORGANIZATION No formal organization No formal reporting requirements No data standardization No continuity plans

IT ORGANIZATION

ISSUES Frequent System “Outages” in the listed peripherals: Davox (Predictive Dialer) Siemens switch Website/FTP AS/400 (Client/collections information system) General data mismanagement Payment systems between 1 st and 3 rd party collection methodologies Poor database usage for financial/accounting reporting Lack of a continuity plan Nightly back up of “critical files” relevant only to the Davox

SYSTEM “OUTAGES” 6-10 outages per year, at least 1 lasting a week long. Has cost the company several major clients Purported Reasons Hardware (Davox and AS/400) is severely aging No supporting documentation for either exists anymore Manufacturer support is slow to respond One server for client interface It’s not reported whether or not IT staff have skills to maintain hardware

DATA MISMANAGEMENT Standard protocol sees the Dialer Administrator (DA) manually transmit campaign data from FTP site and import it into the Davox. Frequent errors occur as a result of this manual transmission Results in data for previously closed account being lost Purported Reasons DA mistakenly overwrites previous campaign IDs with redundant and/or new data No documentation for job responsibilities Training is lacking

PAYMENT SYSTEM CONFUSION 1 st party payment systems are controlled by automated interface between Davox and Lyricall script application. Forces agents to use a specific set of data elements to process payment 3 rd party collections agents are more autonomous 3 rd party collections agents process payments outside of company/contract policies Results in partial payment postings and inconsistencies in systems that manage payments Purported Reasons 3 rd party agents get lazy, bypass some of the screens that 1 st party agents are forced to use

FINANCIAL/ACCOUNTING USE OF DB Accounting staff typically conduct their work from data extracts taken at one point in the month Therefore, data being used is not “current”. Clear reconciliation of data from the several managements systems is almost impossible Purported Reasons Reports generated from all systems use inconsistent data elements Makes for manually intensive data manipulation

LACK OF A CONTINUITY PLAN No continuity plan exists IT has no disaster recovery protocols Several outages annually make this recipe for disaster

RECOMMENDATIONS Using a model based in Enterprise Application Software solutions, SCI should completely reexamine their hardware/software configurations, update their identity management system and integrate all of their systems into one database. System outages can be mitigated by implementing one hardware solution that handles all of the major benefits of the Davox and the Siemens switch. Data mismanagement can be mitigated if IT developed an automated transmission protocol for campaign data (i.e. SCI website interfaces directly with SQL database). Also, sufficient training and documentation of duties in this department is essential Payment system confusion would be lessened if IT developed a separate UI for agents handling 3 rd party accounts. IT must hire competent database/query managers to supplement accounting’s needs A continuity plan must be developed.

REFERENCES 1.The History of the Predictive Dialer. 2.Sue Conger. S UPPORT C ENTER, I NC. (A). University of Dallas 3.Enterprise software.

QUESTIONS 1.One main reason for campaign (new customer account info) data loss is: a)FTP site is not backed up b)The data is not transmitted in the correct format c)Dialer administrator user error d)Flat files are not supported in the current DB environment 2.Why is a continuity plan important? a)So business operations are not severely damaged during system outages b)Data recovery is seamless c)Mitigates loss of client relationship due to IT related problems d)All of the above 3.What is the problem caused by the difference in payment systems between 1 st and 3 rd party agents? a)3 rd party agents don’t get their commission checks b)1 st party agents don’t have access to credit card machines c)3 rd party agents skip steps, potentially creating violations of company and contract policy d)Automated payments systems are untrustworthy.