Software and Delivery Requirements

Size: px
Start display at page:

Download "Software and Delivery Requirements"

Transcription

1 SAP Predictive Analytics Content Adoption rapiddeployment solution August 2015 English Content Adoption rapiddeployment solution: Software and Delivery Requirements SAP SE Dietmar-Hopp-Allee Walldorf Germany Document Revisions Date 0 Release of version 1 August 16, Release of version 2 March 21, Release of version 3 July 14, Release of version 4 February 23, Release of version 5 August 10, 2015

2 Copyright 2015 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE s or its affiliated companies strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions. SAP SE Public Page 2 of 15

3 Icons Icon Meaning Caution Example Note Recommendation Syntax External Process Business Process Alternative/Decision Choice Typographic Conventions Type Style Description Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options. Cross-references to other documentation. Example text EXAMPLE TEXT Example text Emphasized words or phrases in body text, titles of graphics and tables. Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE. Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools. EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key. Example text <Example text> Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries. SAP SE Public Page 3 of 15

4 Table of Contents Contents 1 Purpose of the Document General Project Prerequisites Technical Requirements Banking Consumer Products Finance Insurance Manufacturing Portfolio & Project Management Retail Sales & Marketing Telco Software Product Versions SAP Solution Manager SAP Note Software Landscape Diagram SAP SE Public Page 4 of 15

5 1 Purpose of the Document This document contains all information to: Validate that key prerequisites such as software products and versions match the customer situation Check that all prerequisites for a customer implementation are in place Check that correct content, tools and skills are in place before the project starts The document lists different kinds of requirements on package level if they are valid for all scope items included in the package. For requirements valid for certain scope items only, these scope items are mentioned. The document contains pre-requisites only, not the procedures to meet them. For how-to information (that is, how to find the download area) please refer to the configuration guides. 2 General Project Prerequisites The following prerequisites need to be in place before an implementation project can start. Prerequisite Kick off and workshop dates, location and attendees agreed team allocated with correct skills and training in place Project sponsors and stakeholder identified Hardware fully commissioned Software licenses in place Infrastructure team can respond to requests quickly enough, to CSS notes, BW content, patches, user requests, authorization changes and transports User interfaces and visualizations agreed upon. Remote access is in place for SAP consultants and SAP Active Global Support Decision made whether pre-assembled delivery will be used Decision made whether SAP Best Practices Solution Builder will be used to activate content. Decision made whether Solution Manager will be used. Solution Manager set-up with any relevant templates. Tool for project repository and collaboration agreed Test management tool agreed Responsibility SAP SE Public Page 5 of 15

6 3 Technical Requirements This section contains technical requirements in different areas. For each requirement, the relevance for scope items of the package is provided. 3.1 Banking attrition analysis 3.2 Consumer Products Demand data analysis SAP Demand Signal Management (DSiM) OR DSiM Product fulfillment and optimization Demand Signal Management (DSiM) OR DSiM Brand sentiment and sales analysis SAP SE Public Page 6 of 15

7 3.3 Finance Profitability analysis with financial trends SAP HANA Live for SAP Company performance analysis Late-payment management SAP HANA Live for SAP cash collection analysis 3.4 Insurance Fraudulent claims analysis SAP HANA Live for Insurance Loss forecasting SAP HANA Live for Insurance SAP SE Public Page 7 of 15

8 3.5 Manufacturing Asset breakdown analysis SAP SAP Landscape Transformation (LT) --- OR --- SAP SAP Landscape Transformation (LT) SAP HANA Live for Manufacturing Maintenance cost analysis SAP SAP Landscape Transformation (LT) --- OR --- SAP SAP Landscape Transformation (LT) SAP HANA Live for Manufacturing demand and inventory requirements Overall equipment effectiveness SAP HANA Live for Manufacturing Stock analysis for asset utilization SAP SAP Landscape Transformation (LT) SAP SE Public Page 8 of 15

9 3.6 Portfolio & Project Management Project profitability analysis 3.7 Retail loyalty programs SAP Activity Repository (CAR) Activity Reporting OR Market basket opportunities Short-term checkout prediction SAP Activity Repository (CAR) Flat File Activity Reporting OR Flat File Store clustering Activity Repository (CAR) Activity Reporting OR Flat File SAP SE Public Page 9 of 15

10 3.8 Sales & Marketing segmentation SAP HANA Live SAP HANA Live Market campaign success Market segmentation SAP HANA Live SAP HANA Live Pipeline and revenue forecasting SAP HANA Live SAP HANA Live Product recommendation 3.9 Telco Churn modeling and offer recommendation Rotational churn detection Multi-SIM detection Post-paid analysis SAP SE Public Page 10 of 15

11 4 Software Product Versions The following software products and versions are required: Product Product Version Comments SAP 6.0 SP 06 or higher Only required for certain scenarios. SAP HANA Live for SAP 1.0 or higher Only required for certain scenarios. SAP Landscape Transformation (SAP LT) 2.0 SP 05 or higher Only required for certain scenarios. 1.0 SP 09 or higher Only required for certain scenarios. SAP HANA studio 1.0 SP 09 or higher Only required for certain scenarios. Desktop Server SAP BusinessObjects BI Platform SAP BusinessObjects Explorer SAP BusinessObjects Mobile 2.0 SP 02 or higher Only required for certain scenarios. 2.0 SP 02 or higher Optional. Provides scheduling, automation of training of the model, user activity monitoring. 4.1 SP 06 or higher Only required for certain scenarios. 4.1 SP 06 or higher Only required for certain scenarios. 4.1 SP 06 or higher Optional for any scenario that uses SAP BusinessObjects Explorer. SAP Lumira Server 1.0 SP 22 or higher Optional. Provides browser and mobilebased experiences. SAP Activity Repository (CAR) SAP Demand Signal Management (DSiM) 1.0 or higher Only required for certain scenarios. 1.0 or higher Only required for certain scenarios. SAP SE Public Page 11 of 15

12 5 SAP Solution Manager For the implementation of the solution package, SAP Solution Manager is recommended. Product Product Version Comments SAP Solution Manager SAP Solution Manager 7.0 Enhancement Package 1 SP18 or higher - Or - SAP Solution Manager 7.1 SP01 or higher - Or - SAP Solution Manager 7.1 on SAP HANA (ST 712) SP00 or higher If using SAP Solution Manager 7.0 with SP below 24, see SAP Note For SAP Rapid Deployment solutions, implementation content is available in SAP Solution Manager templates. The SAP Solution Manager template for this solution package is in the ST-RDS 100 content add-on. You can download the latest available ST-RDS 100 content add-on from SAP Software Download Center on SAP Service Marketplace at service.sap.com/swdc. For more information about downloading and installing ST-RDS 100 content add-ons, see SAP Note and SAP Note respectively. In the ST-RDS 100 content add-on, access the template in the following way: If you have SAP Solution Manager 7.1 SP04 or lower, select the template ID and template name in the table below. If you have SAP Solution Manager 7.1 SP05 or higher, select the solution package name(s) in the table below. Template ID and Template Name Solution Package Name RDS_PRE_ANA_HANA10V5 - Content Adoption RDS_V5 Content Adoption RDS_V5 SAP SE Public Page 12 of 15

13 6 SAP Note The following SAP Note needs to be considered: SAP Note Comments Relevance This SAP Note contains critical information for implementing the Content Adoption rapid-deployment solution. Before you start the activation of the related SAP Best Practices scope, check the latest versions of this SAP Note. All Scope Items SAP SE Public Page 13 of 15

14 7 Software Landscape Diagram SAP HANA Mobile SAP BusinessObjects SAP Lumira Server Info Models Data Model SAP Demand Signal Management (DSiM) SAP Activity Repository (CAR) SAP HANA Predictive Analysis Library (PAL) SAP HANA Live Automated Analytics Expert Analytics Import SAP Landscape Transformation External Files SAP Overview of Architecture The system landscape above displays the entire range of the systems for the landscape with this solution. Different scenarios require less landscape than displayed. The previous tables outline the landscape necessary for individual scenarios. Here are the areas of the total landscape: Data Sources: This rapid-deployment solution uses data from flat files or SAP. If the data comes from SAP, SAP Landscape Transformation (SAP LT) is employed to move the data into SAP HANA. When the data source is a flat file, depending on the scenario, data is loaded into SAP HANA or loaded directly into SAP Predictive Analysis. For more information about what data sources are used for what scenarios, see the Data Source by Scenario section of this document. SAP HANA: All of the domains use SAP HANA. Some scenarios provide predictive analytics through the SAP HANA Predictive Analysis Library (PAL) that includes predictive algorithms used in calculating results. SAP HANA is the staging area for the data sources as well as a model schema supporting the visualization of data and accessibility by mobile devices. Optionally, this rapid-deployment solution uses SAP HANA to integrate with additional, separate rapid-deployment packages. : For scenarios using, Automated Analytics provide metadata repository for data management and automated algorithm and Expert Analytics provides preconfigured documents in the LUMS file format for the basis for predictive analytics. Depending on the scenario, uses data from SAP HANA or in certain cases data loaded directly in as flat files. For certain scenarios, provides the visualizations for the predicted results. : For scenarios using SAP HANA PAL to provide predictive analytics, is used to provide visualizations for the predicted results. 1 SAP SE Public Page 14 of 15

15 SAP Mobile: When is used to provide visualizations for the predictive results, SAP Mobile is used to allow these results to be shared with supported mobile devices using an SAP Mobile App. For more information, see the related configuration guides for this solution. SAP BusinessObjects Business Intelligence (BI) platform: SAP Explorer and SAP Mobile require the SAP BusinessObjects BI platform. In some scenarios for this rapid-deployment solution, the BI platform, Explorer, and Mobile options are not required. For more information, see the Software by Scenario section of this document. Your system landscape is dependent on the choices you make deploying individual, or combinations of, scenarios. Review the entire document to understand the requirements and landscape for your implementation. SAP SE Public Page 15 of 15