Presentation on theme: "GBA 573 Final Presentation Jonathan Stone Summer 2003."— Presentation transcript:
GBA 573 Final Presentation Jonathan Stone Summer 2003
Overview This project focuses on implementation of a new database and network for Web Laundry. Web Service Company, is known as the nation's most successful provider of laundry service for apartments, military bases, college residence halls & other multifamily locations. This is an established company which has been around since This project seeks to continue Webs long history of innovations, which has been backed by integrity and a commitment to service, and as a result Web has both enjoyed great success and laid the foundation for a successful future. This presentation will discuss the main challenge(s) that prompted the project from problem statement through final analysis.
Problem Statement Company has grown significantly without accurate tracking mechanisms. Tracking mechanisms are necessary to monitor washer machine usage, coin retrieval, and maintenance Different levels of access are necessary for contract review and location performance. Annual reports to clients are necessary and currently cumbersome to produce.
Project Objective To provide an internal database and intranet access mechanism to allow communication of information amongst company personnel. Elimination of duplicate mechanical visits to locations. Quicker service in terms of coin retrieval and updates of old machinery.
Project Scope Phase I will consist of creation of interface and database to allow for documentation, maintenance, and tracking utilities. Phase II will consist of implementation of wireless devices on equipment to warn of impending coin retrieval duties.
Project Justification Costs saved from elimination of duplication of efforts. Better service to current customers. Quicker return of monetary funds.
Return on Investment Costs –Server $2000 –Software $2000 –Development $15000 Benefits –Accelerated monetary collection ($500 per month) –Elimination of duplicate communication ($200 per month) –More expedient maintenance repairs (estimated $200 per month) Breakeven estimated at 21 months Not includedintangibles such as better customer service, happier customers, and market advantage
Costs ItemAmount Server2000 Software2000 Development (on contract)15000 Total19000 Benefits ItemAmount Increased Collection500 Elimination of Communication200 Maintenance repair savings200 Total (per month)900
Measures of Success Use of System End User Satisfaction Increased revenue per month Increased contracts Increased satisfaction reported from current clients
Feasibility Analysis Technical –Current technology exists for immediate implementation –San Diego houses a large supply of IT workers who can create database and intranet Economic –Web has enough resources and upper management is willing to commit to project and innovation. Operational –This project has been requested and desired by current employees –Also due to technical capabilities by either in house personnel or hired contractors, likelihood of project success is increased.
Risk Analysis There is no choice with implementation, system is required. Major Risk Factors –Project will not work as anticipated –Project will run over budget –Project will not produce anticipated revenues –Product will not be used Risk Management Strategy –Require updates by design team to ensure project works and comes in under budget –Ensure that project is connected properly with leases to ensure that revenue increases –Ensure that product anticipation is heavily expected via communication so that employees are anxious to use system
Project Characteristics and Requirements Project Deliverables will require: –One Server –Database creation –Web Interaction pages –Documentation Manual Project will be accessible by –Three different levels of personnel –Will allow for remote access with security authentication
Project Communication Plan End Users will receive bi-weekly report of project status Management will receive weekly report of project status. Accounts will receive marketing blitz starting up to two months prior to system release. Most communication will be conducted via and paper newsletter
Project Implementation Project Team will consist of: –One Team Leader –Two Programmers –Three Installers (for Phase II) Project (Phase I) will have four main stages –Stage One – inquiry from end users to report type and frequency of documentation –Stage Two – building of prototype –Stage Three – testing of prototype –Stage Four – phased implementation of actual system Project (Phase II) will only have one stage as it will be considered an upgrade feature
Project Implementation Stage One Questionnaire will be created and sent out to all sales agents. Results will be quantified and analyzed and incorporated into initial design.
Project Implementation Stage Two Prototype of system will be created from input received from end users. Technical testing will be implemented to ensure system works according to end user expectations.
Project Implementation Stage Three One specific region will be selected as first testing site. Testing duration to last one month. Specific elements of investigation to include –Usage of system –System savings –Query of clients
Project Implementation Stage Four Upon satisfactory responses from previous stages project will be implemented throughout entire company. Different levels of security will be implemented.
Documentation Development Team to create separate training manuals –For end users (sales agents) –For management/administrative personnel –For client
Project Duration Stage One – one month Stage Two – three months Stage Three – one month Stage Four – two months Total time for project 7 months
Final Analysis/Method of Evaluation Revenue analysis to be conducted for up to 1 year and measured quarterly and compared to previous company history records. Follow up questionnaire to be created and sent to clients and sales agents System usage to be determined automatically.
Project Wrap Up Official commencement of project complement and written newsletters to follow Party for project team
Conclusion Any Questions? Thanks for your time!