SlideServe
Menu
Préférences
© SlideServe · v2026

Data Analysis through SAP HANA

nash avatar
12 diapositives · 276 Views · Jul 13, 2014

Data Analysis through SAP HANA. TEAM4Solutions Capstone Presentation. Michael Chepkwony , Julio Silveira , Mark Ryan Talabis, Hung Tran, Greg Zheng. As - Is. Problems. Recalls and patches. E.g. GL3000 recall. Unscheduled product maintenance .

Data Analysis through SAP HANA - slide 1
01 / 12Data Analysis through SAP HANA
1 / 17

Télécharger la présentation

Data Analysis through SAP HANA
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation
  1. Data Analysis through SAP HANA TEAM4Solutions Capstone Presentation Michael Chepkwony, Julio Silveira, Mark Ryan Talabis, Hung Tran, Greg Zheng

  2. As-Is

  3. Problems Recalls and patches. E.g. GL3000 recall. Unscheduled product maintenance. Expertise required for help desk and internal sales personnel. Help desk on-call time. Executive reports from complaint, product problems and user feedback analysis. Enhance product development with information from complaint management and user feedback. Sales and marketing teams visibility on customers complaints , product maintenance and customer feedback

  4. Resolutions A better analysis of user complaints would have minimized recall impact. Analysis of data by the danger probability would help with proactive maintenance. Technicians would be able to resolve problems in the field much faster with real time correlated information. Help desk and sales expertise would not be necessary if answer for requests could be easily searchable. Data from internal sales and field technicians, would help with development of new products and existing products. Voice messages and online complaints could be analyzed and correlated. Sales would have full visibility of customer problems, complaints and suggestions and how it correlates with product development.

  5. Software Architecture

  6. Technology SAP HANA Database: • Hybrid structure with two engines within the same DBMS (column based and row based store) • High data compression • Parallel processing • Calculation engine • Text engine • R integration • ACID requirements SAP HANA appliance SAP HANA studio for modeling and monitoring

  7. HANA Appliance

  8. Roles

  9. Project Milestones

  10. Project Risks • Detailed assessment of business and IT requirements • Vetted by GLOCO stakeholders • Thorough analysis of hardware, software, personnel costs • Estimates considering cost contingency principles • Clearly defined project schedule • Methodology based on iterations of demo/feedback • Daily project tracking and weekly status reports • Close coordination with GLOCO PMO RISKS • Outsourcing to Team 4 partner developers. • Strong capabilities of project foundational technologies • Legal contracts and escrow arrangements • Relevant BU represented in project initiation • BU representatives with experience in source systems in project team • Targeted users included in application demos and testing

  11. Operation readiness Change Management Application Support and Hardware Maintenance

  12. Solution DEMO