BB Configuration Guidesapidp/... · Web viewThe Configuration Guide: Getting Started guide is...

SAP HANA 1.0

June 2015

English

Signal Intelligence Configuration for Monitoring and Predictive Maintenance (EZ6)

SAP SEDietmar-Hopp-Allee 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best Practice Signal Configuration for Monitoring and Predictive Maintenance (EZ6)

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 http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark 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 of 24

http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

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 Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT 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.

Example text 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 Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© SAP SE of 24


ContentSignal Intelligence configuration for Monitoring and Predictive Maintenance...........................51 Purpose............................................................................................................................. 5

1.1 Audience..................................................................................................................52 Preparation........................................................................................................................ 6

2.1 Prerequisites............................................................................................................62.2 Assumptions............................................................................................................6

3 Configuration.....................................................................................................................73.1 Install and Configure provided SAP Content for Signal Intelligence........................7

3.1.1 Deploy the foundation delivery unit.....................................................................73.1.2 Execute Signal Intelligence seeding procedure...................................................83.1.3 Deploy the business layer delivery unit...............................................................83.1.4 [Optional] Deploy the Smart Factory configuration delivery unit..........................9

4 Creating Operational and Administrative Users...............................................................114.1 Creating a Solution Admin User............................................................................114.2 Creating an Integration User..................................................................................124.3 Creating a Solution Business User........................................................................13

5 Configuring Operations Scheduler Jobs..........................................................................146 Configuring Preferences..................................................................................................15

6.1 Configuring Signal Intelligence for Monitoring and Predictive Maintenance..........156.1.1 Signal Intelligence Configuration Settings.........................................................15

7 Appendix: Data Load Specification..................................................................................187.1 Master Data...........................................................................................................18

7.1.1 Signal Entity......................................................................................................187.1.2 Entity Type........................................................................................................197.1.3 Measurement Point...........................................................................................197.1.4 Location.............................................................................................................207.1.5 Signal Tag Entity Association............................................................................217.1.6 Location.............................................................................................................217.1.7 Alert................................................................................................................... 22

8 Appendix: Sample Data...................................................................................................228.1 Loading Sample Data (Optional)...........................................................................228.2 Unloading Sample Data.........................................................................................23

9 Appendix: Additional Solution-Specific References.........................................................249.1 Solution Tables......................................................................................................24

9.1.1 Delivered Solution Tables..................................................................................249.2 SAP HANA Global Naming Convention.................................................................24

10 Appendix: Documentation Resources..........................................................................2510.1 SAP HANA Guides................................................................................................2510.2 Important SAP HANA Security Notes....................................................................2510.3 SAP Event Stream Processor (SAP ESP).............................................................25

© SAP SE of 24

SAP Best Practices SAP HANA configuration for Signal Intelligence Monitoring & Predictive (EZ6)

Signal Intelligence configuration for Monitoring and Predictive Maintenance

1 PurposeThe purpose of this document is to describe the deployment steps required for SAP HANA® technical components (prebuilt components) within the system landscape for the signal intelligence scenario of SAP HANA Big Data Intelligence rapid-deployment solution.

1.1 AudienceThis guide is intended for the technical consultants responsible for the deployment of the solution. It is assumed that they have been trained in SAP HANA administration and configuration.

© SAP SE of 24


2 Preparation2.1 PrerequisitesPerform the steps within the prerequisite building blocks before you start setting up SAP HANA technical components for signal intelligence for monitoring and predictive maintenance. For more information, see the SAP Note 1956985.The Configuration Guide: Getting Started guide is attached to the SAP Note for this solution, and the Prerequisite Matrix document is available from the Service Marketplace.

2.2 AssumptionsThe following statements are the configuration assumptions for setting up SAP HANA technical components for this solution; the following configuration must be fulfilled for this solution to be implemented.

1) SAP HANA software (both server and studio) are installed within the system landscape. For more information about the specific software versions required, see the Software Requirements document for this solution.

2) SYSTEM access with full system privileges for the SAP HANA environment.

For more information about required software and versions for this solution, see the Software Requirements guide for this rapid-deployment solution.

© SAP SE of 24


3ConfigurationSetting up SAP HANA technical components for the solution require the following high-level processes:

1. Install and Configure provided SAP HANA content for Signal Intelligence2. Creating Operational and Administrative Users 3. Loading sample data for Jump-start (Optional)

The following subsections describe detail steps required and performed using SAP HANA studio. After configuration and user creation, you can optionally load sample data, as described in Appendix: Sample Data.

3.1 Install and Configure provided SAP Content for Signal Intelligence

To implement the Signal Intelligence scope item, you must perform the following steps: 1. Deploy the Signal Intelligence foundation delivery unit2. Execute the seeding procedure3. Deploy the Signal Intelligence business layer delivery unit4. Deploy the Smart Factory configuration

3.1.1 Deploy the foundation delivery unitUseThe following steps are used to load the signal intelligence monitoring and predictive maintenance foundation delivery unit.

The signal intelligence foundation delivery unit can be imported using either Server or Client as source of delivery unit file location. If an import from the server is required, contact your system administrator for the server path. This step must be executed using SYSTEM account.

Procedure1. Ensure the signal intelligence foundation delivery unit (HCO_RDS_BDI_MFG_SI_FND) is

downloaded into desired location. If it is not available, contact your system administrator.2. Logon to SAP HANA studio with the deployment user that you previously created. 3. Choose the Quick Launch window and select the SAP HANA deployment instance and

select Import Option.4. Choose Delivery Unit and select Next.5. In the Select file section, choose the import location (Server or Client) and specify the

location of HCO_RDS_BDI_MFG_SI_FND.tgz6. Choose Finish to import the content of the delivery unit.

ResultThe HCO_RDS_BDI_MFG_SI_FND is successfully deployed. The Job Log shows the status of the package as it loads. If the load is successful, then the status displays Success. Navigate in the SAP HANA studio to the Catalog section and ensure SAP_RDS_BDI_MFG_SIGNAL is visible.

© SAP SE of 24


3.1.2 Execute Signal Intelligence seeding procedureUseExecute the following steps to ensure that the solution is configured to work with the SAP HANA predictive libraries (PAL):

Procedure1. Open SQL Console2. Execute the following SQL call statements in the order given.

CALL "_SYS_REPO"."GRANT_SCHEMA_PRIVILEGE_ON_ACTIVATED_CONTENT"('EXECUTE','SAP_RDS_BDI_MFG_SIGNAL','SYSTEM');CALL "_SYS_REPO"."GRANT_SCHEMA_PRIVILEGE_ON_ACTIVATED_CONTENT"('SELECT','SAP_RDS_BDI_MFG_SIGNAL','SYSTEM');CALL "_SYS_REPO"."GRANT_SCHEMA_PRIVILEGE_ON_ACTIVATED_CONTENT"('INSERT','SAP_RDS_BDI_MFG_SIGNAL','SYSTEM');CALL "_SYS_REPO"."GRANT_SCHEMA_PRIVILEGE_ON_ACTIVATED_CONTENT"('UPDATE','SAP_RDS_BDI_MFG_SIGNAL','SYSTEM');CALL "_SYS_REPO"."GRANT_SCHEMA_PRIVILEGE_ON_ACTIVATED_CONTENT"('DELETE','SAP_RDS_BDI_MFG_SIGNAL','SYSTEM');CALL "SAP_RDS_BDI_MFG_SIGNAL"."sap.rds-bdi.mfg.signal.seeders::GENERATE_SEED"();

Result

The SIGNAL_MAINTENANCE_FORECAST_SMOOTHING procedure is created in the SAP_RDS_BDI_SIGNAL catalog area.

3.1.3 Deploy the business layer delivery unitUseThe signal intelligence business layer delivery unit deploys the SAP HANA views, procedures, and roles. Perform the following steps to load the signal intelligence business layer delivery unit for the solution.

The signal intelligence configuration delivery unit can be imported using either Server or Client as source of delivery unit file location. If an import from the server is required, contact your system administrator for the server path. This step must be executed using SYSTEM account.

Procedure1. Ensure that the signal intelligence business layer delivery unit (HCO_RDS_BDI_MFG_SI)

is downloaded into desired location. If it is not available, contact your system administrator.

2. Logon to SAP HANA studio with deployment user that you previously created.3. Choose the Quick Launch window and select the SAP HANA deployment instance (for

SYSTEM user) and select Import Option.

© SAP SE of 24


4. Choose Delivery Unit and select next.5. In the Select file section, choose the import location (Server or Client) and specify the

location of HCO_RDS_BDI_MFG_SI.tgz6. Choose Finish to import the content of the delivery unit.

ResultThe signal intelligence business layer delivery unit (HCO_RDS_BDI_MFG_SI) should have successfully deployed as indicated by the status in the status window for this job.

This completes your deployment of signal intelligence delivery units. To use the solution, you must create the required administrative and operational users. You also must modify the configuration settings, as required, for your business needs.

3.1.4 [Optional] Deploy the Smart Factory configuration delivery unit

UseThe following steps are required when using Smart Factory to load the SAP HANA Big Data Intelligence configuration delivery unit for the solution. Execute the following steps to ensure that base configuration is introduced to the solution.

The SAP HANA configuration delivery unit can be imported using either Server or Client as source of delivery unit file location. If an import from the server is required, contact your system administrator for the server path. This step must be executed using SYSTEM account.

Procedure1. Ensure the delivery unit HCO_RDS_BDI_MFG_SI_SF_CFG is downloaded into desired

location. If it is not available, contact your system administrator.

For more information about acquiring the provided preconfigured content, see the Quick Guide for Signal Intelligence attached to the SAP Note 1956985.

2. Logon to the SAP HANA studio with deployment user that you previously created.

For more information, see the Quick Guide for Signal Intelligence attached to the SAP Note 1956985.

3. Choose the Quick Launch window and select the SAP HANA deployment instance and select Import Option.

4. Choose Delivery Unit and select next.5. In the Select file section, choose the import location (Server or Client) and specify the

location of HCO_RDS_BDI_MFG_SI_SF_CFG.tgz6. Choose Finish to import the content of the delivery unit.

ResultThe HCO_RDS_BDI_MFG_SI_SF_CFG delivery unit is deployed. Review the catalog section to ensure that the RDS_SAP_BDI_CONFIG schema is visible.

© SAP SE of 24


The following parameters (MP_ID) are available in the sap.rds.bdi.signal::tables.MP:

MP_ID CommentsRCREADY Controller power ON ready. Must be 1

(true), otherwise the machine is not running; set to 0 for maintenance every 3 months.

AUTOENA Outputs the automatic operation enabled state. Must be 1 (true), otherwise, the machine is not running; set to 0 (false) for maintenance every 3 months.

START Operating output. Machine is active, set to 1 (true); machine program start.

STOP Pausing output. Machine is not active, set to 1; machine program stop.

ERRRESET Error occurring output signal. Error message, move down.

HLVLERR Output that a high-level error is occurring.

LLVLERR Output that a low-level error is occurring.

CLVLERR Output that a warning level error is occurring.

EMGERR Emergency stop output signal. Set to 1 (true) AUTOENA, START, PRGOUT, STOP set to 0 (false) and RCREADY and HLVERR set to 1 (true).

BATERR Battery voltage drop. Target value 3.6V, tolerance +/- 0.2V; in-between +/- 0.1V, set CLVLERR to 1 (true). Over +/- 0.2V, then set HLVERR to 1 (true).

AIRERRn Outputs that a pneumatic error is occurring. No compressed air available, then set AIRERR to 1 (true)

TMPOUT The “temperature output in progress” status is output to the numerical output. Target value is 40º Celsius, tolerance +5,-10 º Celsius; above 45º C., then set HLVERR; below 42º C., then set CLVERR.

© SAP SE of 24


4Creating Operational and Administrative Users

In this section, you create operational and administrative roles for users of this solution. The functional roles must be created for specific operational purposes. The designated roles are assigned different operational and access permissions that we recommend.

Functional roles required for operating and administering this solution:1. Business User for access and operations of the solution.2. Solution Admin User for full administrative control in managing the solution.3. Integration Admin User manages SAP HANA content development and deployment.

The SYSTEM user does not have permission to perform all operations for this solution. Create the following role accounts described to perform specific operations.

Perform the following steps with the SQL Editor window opened under SYSTEM account. Ensure that the appropriate Client session is set to the following user accounts you create.

4.1 Creating a Solution Admin UserUseThis section must be performed using the SYSTEM user account.The Signal Admin user has permission to manage this solution, and can perform all administrative tasks for this solution within SAP HANA. The following roles are required to perform all administrative tasks for this solution:

sap.rds-bdi.mfg.signal.roles::RDS_BDI_MFG_SIGNAL_ADMIN

ProcedureTo configure the Signal Admin user account, follow these steps.

Replace {SIGNAL_ADMIN} and {Password} with your values.

CREATE USER {SIGNAL_ADMIN} PASSWORD {Password};CALL "_SYS_REPO"."GRANT_ACTIVATED_ROLE"('sap.rds-bdi.mfg.signal.roles::RDS_BDI_MFG_SIGNAL_ADMIN','{SIGNAL_ADMIN}');

The output window of the SQL Editor notifies when the command successfully runs.

The initial password established for this user has a change password requirement at first logon.

Verify the creation by opening a SQL Window using your Signal Admin account created previously.

© SAP SE of 24


SAP_RDS_BDI_MFG_SIGNAL schema is visible in the catalog area of the Signal Admin user name

ResultThe Signal Admin user account is created with the administrative roles associated with this user.

4.2 Creating an Integration UserUseThis section must be performed using SYSTEM user account.The Integration Admin user for the signal intelligence scope item of SAP HANA Big Data Intelligence has permission to read and write from SAP ESP to the solution event tables.To configure the user to perform all administrative tasks related to this solution, follow these steps.

ProcedureReplace {INTEGRATION_ADMIN} and {Password} with your values.

CREATE USER {INTEGRATION_ADMIN} PASSWORD {Password};CALL "_SYS_REPO"."GRANT_ACTIVATED_ROLE"('sap.rds-bdi.mfg.signal.roles::RDS_BDI_MFG_SIGNAL_ESP_INTEGRATION','{INTEGRATION_ADMIN}');CALL "_SYS_REPO"."GRANT_ACTIVATED_ROLE"('sap.hana.admin.roles::Monitoring','{INTEGRATION_ADMIN}');CALL "_SYS_REPO"."GRANT_ACTIVATED_ROLE"('sap.hana.xs.admin.roles::HTTPDestAdministrator','{INTEGRATION_ADMIN}');CALL "_SYS_REPO"."GRANT_ACTIVATED_ROLE"('sap.hana.xs.admin.roles::JobAdministrator','{INTEGRATION_ADMIN}');CALL "_SYS_REPO"."GRANT_ACTIVATED_ROLE"('sap.hana.xs.admin.roles::TrustStoreAdministrator','{INTEGRATION_ADMIN}');


The initial password established for the user has a change password requirement at first logon.

Verify the creation by opening a SQL Window using your data scientist account. SAP_RDS_BDI_MFG_SIGNAL schema is visible in the catalog area of that user

name

ResultThe Integration Admin user account is created and required roles are associated with this user.

© SAP SE of 24


4.3 Creating a Solution Business UserUseThis section must be performed using SYSTEM user account.The Signal Viewer user is a solution business user and consumer of information provided by this solution. The business user has permission to use the signal intelligence scope item of SAP HANA Big Data Intelligence. The business user your create has only the permission to view the solution using the user interface.The following role is required for business users to use this solution:

sap.rds-bdi.mfg.signal.roles::RDS_BDI_MFG_SIGNAL_VIEWER

ProcedureExecute these steps to establish a Signal Viewer user account. Replace {SIGNAL_VIEWER} and {Password} with your values:

CREATE USER {SIGNAL_VIEWER} PASSWORD {Password};CALL "_SYS_REPO"."GRANT_ACTIVATED_ROLE"('sap.rds-bdi.mfg.signal.roles::RDS_BDI_MFG_SIGNAL_VIEWER','{SIGNAL_VIEWER}');


The initial password established for the created business user has a change password requirement at first logon.

Verify the role creation by opening a SQL Window using the Business User account. The SAP_RDS_BDI_MFG_SIGNAL schema is visible in catalog area of your created

business user

ResultThe business user is created.

© SAP SE of 24


5 Configuring Operations Scheduler JobsFor effective operation of this solution, entity and their relationship are resolved whenever changes are made to the ENTITY table. The solution provides a default of 60 seconds as trigger frequency criteria for the scheduler. Using the default, any changes effected to the ENTITY table would be resolved for their relationship in around 60 seconds. This solution does not provide the mechanism for altering the scheduler trigger frequency. Other jobs for managing maintenance schedules and predictive maintenance must be configured as described as follows for effective operation of this solution.

This step must be executed using SYSTEM account and must use user account that is enabled for the sap.rds-bdi.mfg.signal.roles::RDS_BDI_MFG_SIGNAL_ADMIN role for setting up the job configuration. For more information, see the previous section Creating a Solution Admin User.

To configure the scheduler, perform the following steps.1. Navigate to http://SERVER:80XX/sap/hana/xs/admin, where SERVER refers to the

hostname or IP address of the SAP HANA server, and XX refers to SAP HANA instance where this solution is implemented.

2. Logon as SYSTEM user.3. Navigate to Application Folder: sap/rds-bdi/mfg/signal/jobs. Select an

entry and apply steps 3, 4, and 5, repeat for each additional entry:a. SCHEDULER_EVENT_MONITOR.xsjobb. SCHEDULER_MAINTENANCE.xsjobc. SCHEDULER_MAINTENANCE_PREDICTIVE_CACHE.xsjob

4. Add the Solution Admin user to the User edit control and set the locale to EN-US.5. Select the Active option.6. Choose Save.

Results:Choose the Refresh button and observe the status pane for following:

1. Initial Status must indicate SCHEDULED2. Review the progression of jobs at the Planned Time for each of the configured jobs

as indicated on successful saving of a job; and ensure that the Status indicates SUCCESS for at least one execution of a job.

The frequency is preset on delivery and cannot be altered using the existinghttp://SERVER:80XX/sap/hana/xs/admin link. You manually modify in the SAP HANA development studio by following the path to sap/rds-bdi/mfg/signal/jobs. For more information about configuring xsjob, see the SAP HANA development guide

© SAP SE of 24


6Configuring PreferencesIn this section, you configure preferences for the signal intelligence monitoring and predictive analytics. Multiple values can be configured per table and the entire preferences table can be updated or revised at any time during operation of this solution.

6.1 Configuring Signal Intelligence for Monitoring and Predictive Maintenance

Signal intelligence for monitoring and predictive maintenance scope item includes configurable tables, which can be modified to customize the solution based on your specific business requirements. The following tables include listings of all configurable settings. Modifying the default values is described in the sections.

6.1.1 Signal Intelligence Configuration SettingsUseDeployment specific configuration parameters can be revised during implementation using the link http(s)://SERVER:80XX/sap/rds-bdi/mfg/signal/config.html, where XX refers to the SAP HANA instance number and SERVER – server IP or DNS address. Editable values are modified by choosing the Settings button. The News Feed Settings section (where news feeds are displayed on the News Feed tile) can be added, edited, or deleted.

This step must be performed by the Solution Admin user account created in the previous section Creating a Solution Admin User.

ProcedureReview each of the categories on the left panel of the rendered page with access to the URL link.

Functional areas described in the following table refer to various configuration categories with some being op

Functional Area Parameter Name Parameter Value (default)

Signal Near-Line Storage SAP IQ Admin User <SAP IQ admin user>

SAP IQ Password <IQ Admin Password>

SAP IQ On FALSEChange to TRUE if SAP IQ is required for Near-Line Storage.

SAP IQ Hostname <SAP IQ Hostname>

SAP IQ Port <SAP IP Port>

Hadoop Admin User <Hadoop admin user>

Hadoop Password <Hadoop admin password>

Hadoop On FALSEIf Hadoop is opted as Near line

© SAP SE of 24


storage set this value as TRUE

Hadoop Batch Size 10000 (default)Modify this value to based on your requirements. When the data ingest rate increases, the batch size should be increased to be larger than the ingest rate.

HDFS Path URI <HDFS path URI>

HDFS Filename <HDFS filename>

SAP ESP Cache refresh period in seconds

1800This solution delivers with default value of 1800 seconds, 30 minutes, but can be revised as needed to enable the changes to master data in solution realized in the SAP ESP or SDS cache in the set period

SAP HANA SAP HANA Signal Admin User

<SAP HANA Signal Admin Role user>

SAP HANA Password <SAP HANA password>

SAP HANA Host Server Address

<SAP HANA host IP address>

SAP HANA Instance <SAP HANA instance>

SAP EPS or SDS SAP ESP or SDS Server Address

<SAP ESP or SDS Server address>

SAP ESP or SDS Port <SAP ESP or SDS Server Port>

SAP ESP or SDS Protocol (for SDS, “esps” is required)

<SAP ESP or SDS protocol>

SAP ESP or SDS Admin User

<SAP or SDS admin user>

SAP ESP or SDS Password

<password>

News Feed Name Name of news feed to display on News Feed tile.

Value URL for news feed.

© SAP SE of 24


7 Appendix: Data Load SpecificationFollowing section describes load specification for the tables that are managed during productive use. The following specifications describe the data definition for the master data. You must insure that master data is loaded and the signal entity, location, Measurement point, and signal entity and measure point association is configured before opening the traffic from the signaling device to SAP ESP integration engine.

7.1 Master Data

The following tables are in the sap.rds-bdi.mfg.signal.model::tables path location.

7.1.1 Signal Entity

7.1.1.1 ENTITYName Data Type Comment

ENTITY_ID NVARCHAR (256) Unique identifier for the entity

ETYPE_ID NVARCHAR (256) ID that refers to the assigned entity type

PARENT_ENTITY_ID NVARCHAR (256) ID of the parent entity

BASE_UOM NVARCHAR (256) Unit of measurement that is necessary for this entity

WEIGHT INTEGER Factor to adjust the importance of the entity; default value is 1

LOCATION_ID INTEGER Surrogate key for the functional location

LASTMODIFIED TIMESTAMP Last modified time for this record

IS_EQUIPMENT NVARCHAR(1) Identifies whether an entity represents equipment or a component.

SHORT_ID NVARCHAR(6) Shown as the short form of ENTITY_ID in the user interface

SOURCE NVARCHAR(10) Default is UM.

CLIENT NVARCHAR*16) Default is 000.

7.1.1.2 ENTITY_TName Data Type Comment

ENTITY_ID NVARCHAR (256) Unique identifier for an entity

SPRAS NVARCHAR (2) Language key

DESCRIPTION NVARCHAR (128) Description of the entity


© SAP SE of 24


7.1.2 Entity Type

7.1.2.1 ENTITY_TYPEName Data Type Comment

ENTITY_TYPE_ID NVARCHAR (256) Unique identifier of the entity type

PARENT_ENTITY_TYPE_ID NVARCHAR (256) ID that refers to the parent entity type

7.1.2.2 ENTITY_TYPE_TName Data Type Comment

ENTITY_TYPE_ID NVARCHAR (256) Unique identifier for an entity type


DESCRIPTION NVARCHAR (128) Description of the entity


7.1.3 Measurement Point

7.1.3.1 MPName Data Type Comment

MP_ID NVARCHAR (256)

ID for the measurement point

MP_TYPE NVARCHAR (256)

Unique ID that refers to the type of the measurement point, for example, temperature

MEASUREMENT_TYPE INTEGER Unique ID that refers to the data type a measurement point delivers

LT DOUBLE Lower specification limit associated with the measurement point

UT DOUBLE Upper specification limit associated with the measurement point

UOM NVARCHAR (256)

ID for unit of measurement table that can either be a local one as well as the ERP_UOM table

WEIGHT DOUBLE Weight factor for the measurement point to configure its importance for an entity

AGG_PERIOD INTEGER Aggregation time window assigned to a measurement point (value in seconds)

GREEN DOUBLE To be a green (OK) event the measurement values must lie between LT and UT at least (for example, 90) percent of the time

© SAP SE of 24


YELLOW DOUBLE To be a yellow (WARNING) event the measurement must lie between LT and UT at least (for example, 70) percent of the time

RED DOUBLE To be a red (ERROR) event the measurement values must lie above UT or below LT XX percent of the time

LASTMODIFIED TIMESTAMP last modified time for this record same as creation_timestamp when inserted first time

7.1.3.2 MP_TName Data Type Comment

MP_ID NVARCHAR (256) Unique identifier for a measurement point


DESCRIPTION NVARCHAR (256) Description of the measurement point

LASTMODIFIED TIMESTAMP last modified time for this record

7.1.4 Location

7.1.4.1 LOCATIONName Data Type Comment

LOCATION_ID INTEGER Unique identifier for a location

GEO_LATTITUDE DOUBLE Latitude of location

GEO_LONGITUDE DOUBLE Longitude of location

LASTMODIFIED TIMESTAMP Date last modified

7.1.4.2 LOCATION_TName Data Type Comment

LOCATION_ID INTEGER Unique identifier for a location

SPRAS NVARCHAR(2) Language key

COUNTRY NVARCHAR(64) Country

STATE NVARCHAR(64) State

CITY NVARCHAR(64) City

ZIP_CODE NVARCHAR(16) Zip Code

STREET NVARCHAR(32) Street address

HOUSE_NUMBER NVARCHAR(32) House number

DESCRIPTION NVARCHAR(256) Description


© SAP SE of 24


7.1.5 Signal Tag Entity Association

7.1.5.1 TAG_ENTITY_ASSOCIATIONName Data Type Comment

SENSOR_TAG NVARCHAR (55) Sensor tag

MP_ID NVARCHAR(256) Unique identifier of measurement point

ENTITY_ID NVARCHAR(256) Entity identifier

ACTIVE INTEGER Active status


7.1.6 Location

7.1.6.1 LOCATIONName Data Type Comment

LOCATION_ID NVARCHAR (256) Unique identifier for a location

GEO_LATITUDE DOUBLE Latitude geo-coordinate for the functional location

GEO_LONGITUDE DOUBLE Longitude geo-coordinates for the functional location

LASTMODIFIED TIMESTAMP Last modified time for this record same as creation_timestamp when inserted first time

GEO_COORDINATE ST_POINT

7.1.6.2 LOCATION_TName SQL Data Type Comment

LOCATION_ID NVARCHAR (256) Unique identifier for a location

SPRAS NVARCHAR (2) Language Key

COUNTRY NVARCHAR(64) Country

STATE NVARCHAR(64) State

CITY NVARCHAR(64) City

ZIP_CODE NVARCHAR(16) Zip Code

STREET NVARCHAR(32) Street address

HOUSE_NUMBER NVARCHAR(32) House number

DESCRIPTION NVARCHAR (64) Description of the location


© SAP SE of 24


7.1.7 Alert

7.1.7.1 ALERT

Name Data Type Comment

ID INTEGER

VALUE INTEGER Placeholder for scoring purposes; intended for future extensions.

LASTMODIFIED TIMESTAMP Last modified time for this record same as creation_timestamp when inserted first time

7.1.7.2 ALERT_T

Name SQL Data Type Comment

ID INTEGER

SPRAS NVARCHAR (2) Language Key

DESCRIPTION NVARCHAR (32) Description of the location


8 Appendix: Sample Data

8.1 Loading Sample Data (Optional)UseIf during the implementation you want to preview the solution, the rapid-deployment solution has the option of loading provided sample data. To deploy the sample data, the HCO_SAP_RDS_BDI_SI_SAMPLE delivery unit is imported as follows:

The following steps are used to load the Signal Intelligence sample data delivery unit.

The Signal Intelligence sample data delivery unit can be imported using either Server or Client as source of delivery unit file location. If an import from the server is required, contact your system administrator for the server path. This step must be executed using SYSTEM account.

Procedure1. Ensure the Signal Intelligence sample data delivery unit (of

HCO_RDS_BDI_MFG_SI_SAMPLE) is downloaded into desired location. If it is not available, contact your system administrator.

© SAP SE of 24


For more information about downloading the sample data delivery unit, see the Signal Intelligence Quick Guide attached to the SAP Note 1956985

2. Choose the Quick Launch window and select the SAP HANA deployment instance (SYSTEM) and select Import Option.

3. Choose Delivery Unit and select Next.4. In the Select file section, choose the import location (Server or Client) and specify the

location of HCO_RDS_BDI_MFG_SI_SAMPLE.tgz5. Choose Finish to import the content of the delivery unit.After the delivery unit has successfully deployed, execute the following SQL call statement to advance dates in the sample data (to display sample data based on current and recent dates):

call "SAP_RDS_BDI_MFG_SIGNAL"."sap.rds-bdi.mfg.signal.samples.utility::normalize"();

To view current and recent dates at a later time, execute this SQL statement again as needed.

ResultThe HCO_RDS_BDI_MFG_SI_SAMPLE should have been successfully deployed. The Job Log shows the status of the package as it loads. If the load is successful, then the status displays Success. Once the sample data is successfully loaded, navigate to following the link:Replace {SERVER} and XX in the following URL with your SAP HANA implementation instance number using either the SYSTEM or Solution administrator user or Solution business user. http://{SERVER}:80XX/sap/rds-bdi/mfg/signal/index.html

8.2 Unloading Sample DataUseThe following SQL call statement can be used to unload the sample data..

Must be executed using the Signal Admin role account.

THE FOLLOWING SQL STATEMENT PURGES ALL SAMPLE DATA. Executing the following SQL call statement purges all sample data.

call "SAP_RDS_BDI_MFG_SIGNAL"."sap.rds-bdi.mfg.signal.samples.utility::retract"();

ResultAfter executing the script, remove the sample data from your system. Sample data can be reloaded by performing the steps in the previous section, “Loading Sample Data (Optional).”

© SAP SE of 24


9 Appendix: Additional Solution-Specific References

9.1 Solution Tables 9.1.1 Delivered Solution Tables

Following tables are delivered as part of solution schema in the sap.rds-bdi.mfg.signal.model::tables.<table_name> tables:

a. ENTITYb. ENTITY_Tc. ENTITY_TYPEd. ENTITY_TYPE_Te. EVENTf. EVENT_TYPEg. EVENT_TYPE_Th. FACTi. LOCATIONj. LOCATIONSk. LOCATIONS_Tl. LOCATION_Tm. ALERTSn. ALERTS_To. MAINTENANCE_COSTSp. MAINTENANCE_COSTS_SIMPLEq. MAINTENANCE_STATISTICSr. MAINTENANCE_STATISTICS_SIMPLEs. MEASURE_TYPE_Tt. MPu. MP_Tv. MP_TYPEw. MP_TYPE_Tx. MTy. MT_Tz. UOMaa. UOM_T

9.2 SAP HANA Global Naming ConventionTo distinguish the type of objects the following naming standards for prefixes are used.

Attribute View: AT_ Analytical View: AN_ Calculation View: CA_ Calculated Attribute: CAT_ Calculated Measure: CM_ Restricted Measure: RM_ Sequence: SEQ_ Type Table: TT_ Stored Procedure SP_

© SAP SE of 24


10Appendix: Documentation ResourcesThe following reference manuals support the core product stack and are available on the SAP Help Portal http://help.sap.com

10.1 SAP HANA GuidesFor information about SAP HANA landscape, deployment, installation, administration, and security, see the resources listed in the table:Topic Guide/Tool Quick LinkSAP HANA Landscape, Deployment & Installation

SAP HANA Knowledge Center of SAP Service Marketplace

http://help.sap.com/hanaSAP HANA Master Guide SAP HANA Overall Installation Guide SAP HANA Automated Update Guide

SAP HANA Security

SAP HANA Knowledge Center on SAP Help Portal

http://help.sap.com/hana_platformSAP HANA Security Guide

SAP HANA Installation and Administration

SAP HANA Knowledge Center on SAP Help Portal

http://help.sap.com/hana_platformSAP HANA Technical Operations ManualSAP HANA database Studio InstallationSAP HANA Trigger-based Replication (SLT) Installation Guide

SAP HANA Sizing SAP Service Marketplace

http://service.sap.com/quicksizer

For a complete list of the available SAP Security Guides, see https://service.sap.com/securityguide on the SAP Service Marketplace.

10.2 Important SAP HANA Security NotesThe most important SAP Notes that apply to SAP HANA appliance software and SAP HANA database security are shown in the table:

SAP Note Title1598623 SAP HANA appliance - Security

1514967 SAP HANA appliance – Central Note

10.3 SAP Event Stream Processor (SAP ESP)For information about installing, configuring, and optimizing SAP ESP, see the resource listed in the table:Topic Guide/Tool Quick LinkSAP Event Steam Processor SAP Help Portal http://help.sap.com/esp

Product documentation is based on version and SP level

© SAP SE of 24

http://help.sap.com/esp

https://service.sap.com/sap/support/notes/1514967

https://service.sap.com/sap/support/notes/1598623

https://service.sap.com/securityguide

http://service.sap.com/quicksizer

http://help.sap.com/hana_platform

http://help.sap.com/hana_platform

http://help.sap.com/hana

http://help.sap.com/

BB Configuration Guidesapidp/... · Web viewThe Configuration Guide: Getting Started guide is...

Documents

Transcript of BB Configuration Guidesapidp/... · Web viewThe Configuration Guide: Getting Started guide is...