Professional Documents
Culture Documents
15 Interface - EN
15 Interface - EN
15 Interface - EN
Content:
• Data Import from different Interfaces:
• WinCC
• OPC DA,HDA,UA
• File Import (supporting sFTP)
• S7
• Modbus/TCP
• OLE DB Connector
• ODBC Connector
Architecture
Driver
FTP Transfer
(Parser)
Database
ASCII Interface
B.Data V6.0 SP1 provides 7 different Interface for the acquisition of data:
Basic Information
Wizard
B.Data V6.0 provides a tool called “Wizard”, which supports the user to
establish a connection via the interfaces to the Energy Management
infrastructure with a few clicks.
Basic Information
Adding a new hardware
3
4
5
!
Note: Depending on the
configuration it might take some
6 Browse the PC from the time until the search has finished
network and select the name completely. When the name of the
7
7 Check the detected settings PC appears, the process can be
and click on “OK” stopped and the name can be
chosen from the list.
Restricted / © Siemens AG 2014. All Rights Reserved.
Page 9
WinCC Interface
6
4 Name the communication
channel
WinCC Interface
10
11
! Note: The typical cycle time in a real plant
is 15 min for average power and energy
values (in Europe).
For “non-electrical” tags a cycle time of 1 h
is typical (in Europe).
WinCC Interface
!
Note: After finishing the
Wizard, the Kernel has to be
restarted
OPC DA Interface
OPC DA Interface
8
8
10
11
OPC DA Interface
12
13
!
Note: After finishing the
Wizard, the Kernel has to be
restarted
OPC UA Interface
OPC UA Interface
10
11
OPC UA Interface
12
13
Hotfolder Manager
FTP and
sFTP If the FTP directory is on the same
PC than the acquisition component,
The FTP Import the Service “Hotfolder Manager”
Task can be can be used triggering FTP Import
Kernel cyclically
executed cyclically Task.
downloads the files
from FTP Directory
and imports this file.
FTP Import
Task
Kernel (Acquisition The FTP Import Task
FTP Transfer executes the FTP
component)
Transfer which
! downloads the files from
Note: Calculation the FTP Directory and
level 1 can be used. imports this files
!
Note: timestamp of
measurement B.Data Portal
values has to be
later than the last B.Data database
one
FTP and
sFTP
Directory Download of File Import into Saving of
the file parsing database file
(FTP Directory)
2 The „EXCELCSV“-folder is 2
waiting for a new file to start the
2
import of the new data
4
4
7
8
10
11
9 Click on “new Definition” to
create the tag, where data
should be stored
10 Type in the name of the B.Data
tag and its Address
12
2
1 Right click on the Hardware to
open the Wizard
S7 – Interface
7
7
8 8
S7 – Interface
12
10
11
11
13
S7 – Interface
1 S7 Interface
2
1 Right click on the Hardware to
open the Wizard
Modbus/TCP – Interface
5
3 Name the communication
channel
4 Select the initial state of the
communication channel” and
“Secure”
5 Click on the “Next>” Button
Modbus/TCP – Interface
10
1 Modbus/TCP Interface
OLE DB – Connector
1
1
2
1 Right click on the Hardware to
open the Wizard
OLE DB – Connector
8
6 Select the OLE DB Provider
!
Note: the status of a data point
9 can be used to define valid or
invalid values.
e.g.: 1 valid, 0 invalid
In order to recognize valid values
the statusmapping can be used.
10
11
OLE DB – Connector
12
13
13
14
15
ODBC Connector
Configuration (1/5)
Configuration (2/5)
ODBC Connector
Configuration (3/5)
Configuration (4/5)
8
10
10
9
ODBC Connector
Configuration (5/5)
11
!
Note: In the datasource (if like here Excel) a name field (tab
11 Click on “OK” formulas – name manager) has to be created for the area with
the values that shall be imported!
Restricted / © Siemens AG 2014. All Rights Reserved.
Page 60
ODBC Connector
ODBC Connector
1 1
2 3
1
1 Select the created connection
and import the data from the
Excel source with “Import
Selected”
Parameters
2
1
1
3
4 5
Plausibility check
Calculation Level I
• Data points for the incoming data as well as for the result
4
!
5
Calculation Level I
10
10
Use Cases
• Export to 3rd party products (e.g. facility management tools, maintenance tool,…)
• Thanks to the Stylesheet-technology the export-file (.xml) can be transferred to other formats.
•
• The Stylesheet can be adjusted by the System integrators or by the end customer.
!
Note: Not only Cost Center Relations can be exported with
XML. It is also possible to export data from tags
2
1
!
Note: The xml files are saved in the Bdata Archive folder:
1 Result G:\051_BData\GUI\BDATA_Archive\xml
2
1
Export a subproject
2
1
Export a subproject
2 2
Import a subproject
Basics
B.Data is based on the relational database system Oracle. In order to be equipped for a disc defect
or a similar case, the database must be backed-up regularly.
Recommended Backup Concept:
• Once a week (at night), a full online backup of the B.Data Database (during database is used)
• All other days, an incremental backup
The backup medium can be a separate data backup computer connected via a separate network
card (1Gbit/s) with sufficient disk capacity. The backup data is copied directly to a directory on this
backup computer. The backup data files are stored on the backup computer in compressed format.
!
Note: All scripts are stored on the B.Data database server in the
B.Data homedirectory under:
1 Run “install.cmd” after checking
the paths to set the database into %homedirectory%\DB\%B.Data instance name%\
backup mode. Admin\backup_scripts
(Example: D:\BData\DB\BDATA\Admin\backup_scripts)
1
2
3
4
1 Name of the BData database 5
(BDATA)
2 Directory where the Oracle
software is installed
!
3 Directory where the RMAN Note: By executing the script, Backup Mode of the data
(Oracle Backup and Recovery base is activated From that point Archive-Log-files are
Manager) scripts are stored written and saved.
4 Directory (on the backup Important at this stage is to set path properly.
computer) where all backup files
are saved
Could be a networkpath (UNC-
format) also
(for user & rights requirement –
see documentation!)
5 Is the directory on the B.Data
computer where the archive log-
files are stored
!
Note: Full Online Backup:
This Script assembles and compresses the
Archive-Log-files to backup files. This Backup files
have to be saved on the Backup computer
1 afterwards.
This involves a full backup of the database while
the database remains open and usable.
The script is executed at the set time, e.g. every
Saturday at 22:00 h, by the operating system's
task control.
1 The “full_backup.cmd” script is In this file too, the paths should be set first in the
needed for a full online backup header part.
!
Note: incremental Online Backup:
This script also assembles and compresses Archive-Log-files. The incremental
online backup involves a backup of only those Oracle blocks that have been
changed since the last full or incremental backup. For this reason, this type of
2
backup is much faster.
In case of a restoration it is necessary to load all incremental backup sets that have
been made since the last full backup in chronological order, which is done
automatically by RMAN during a database restore.
2 The “inc_backup.cmd” script is The script is called up every day at the defined time by the operating system’s task
needed for an incremental online control, except on the day where the full backup takes place.
backup In this file too, the paths should be set first in the header part.
!
Note:
The backup files must be placed afterwards in an other place (network
directory from customers IT) to prevent that after an hardware crash
the backup files will be also damaged.
If no Backup script is executed after starting the Backup mode
Archive-Log-files will be written and saved but no Backup files will be
created. Hence, the hard disk will be overcrowded with Archive-Log-
files until the hard disk is full.
1 Installed tasks in scheduler
!
Note: The “restore_all.cmd” script can restore the database after a
total failure. The database is restored into the same directories as
used before. Prior to that, however, it is necessary to install the Oracle
software to the same directory as before.
1
Where necessary, the paths have to be corrected in the header part of
the script.
Please bear in mind that the saved Backup files have to be
copied to the backup folder of B.Data after the new installation of
1 Restoring the database after a
total failure B.Data with the same settings and before the Restore.
siemens.com/answers