Hitachi Vantara

Pentaho IoT and Predictive Maintenance

Real time data streaming via MQTT message queues from remote devices or execute data collection on the edge; ingest data into an appropriate data store, Hadoop, NoSQL or RDBMS; execute data science machine learning models and create advanced analytics to improve efficiencies, reduce maintenance costs and avoid failures.


  • Simplify data ingestion using Metadata injection via templates
  • Data can come from streamed, batch or real time sources
  • Supports multiple message queues including MQTT, Kafka and JMS
  • Data Blending of Data Sources
  • Hadoop distribution and cloud vendor agnostic
  • Data Transformation natively inside Hadoop
  • Execution of data science models
  • Adaptive Execution Engine to select your execution platform
  • Multitenancy support for different groups of users
  • Users create data sets on demand via Self-Serve Advanced Analytics


  • Enable message ingest of varying length with dynamic ETL
  • Handle Historic, Static or Live Data
  • Ingest stream data from the most appropriate type of message
  • Blend IoT data with machine, historic service, and financial data
  • Switch between different Hadoop Distributions or Cloud vendors without re-engineering
  • Utilize the Hadoop compute environment natively
  • Take data science models and get them into productions quickly
  • Compute Engine Agnostic, i.e. PDI, Spark, Map Reduce
  • Provide users their own view of data
  • Extract data from Hadoop on demand to create interactive datasets


£3247 to £15648 per unit per year

Service documents


G-Cloud 11

Service ID

1 7 6 4 9 6 1 0 8 7 3 5 9 6 8


Hitachi Vantara

Jessica Chandler


Service scope

Software add-on or extension
Cloud deployment model
Hybrid cloud
Service constraints
Customers / partners are generally responsible for the software instance whether on-premise, cloud or hybrid; unless delivered as a managed service.
System requirements
  • Processors: Intel EM64T or AMD64 Dual-Core
  • RAM: 8 GB with 4 GB dedicated to Pentaho servers
  • Disk Space: 20 GB free after installation

User support

Email or online ticketing support
Email or online ticketing
Support response times
1 Hour 24/7 response time for severity 1 tickets, 2 business hours for severity 2 and 4 business hours for severity 3 and 4 tickets.
User can manage status and priority of support tickets
Online ticketing support accessibility
WCAG 2.1 AA or EN 301 549
Phone support
Phone support availability
24 hours, 7 days a week
Web chat support
Onsite support
Yes, at extra cost
Support levels
There is standard, premium and enterprise support depending on the support level requirements. Enterprise support comes with:
- An assigned Pentaho Architect for upto 4 hours per week
- One-on-one guidance, mentoring and best practice discussions
- Management of feature requests and support cases
- Scheduled technical sessions with Pentaho subject matter experts
- Internal VM replicated customer environment for faster resolution.
Details of all support levels can be found in the pricing document.
Support available to third parties

Onboarding and offboarding

Getting started
We provide services through our services organization to help customers architect and deliver solutions. Knowledge transfer and training can also be provided to help customers upskill their internal resources and become self sufficient.
Service documentation
Documentation formats
  • HTML
  • PDF
End-of-contract data extraction
Customers will hold data in their database platform / repository of choice, so all data is held and owned by the customer.
End-of-contract process
The CSM (Customer Success Manager) that is allocated to the account will contact the customer and work with them to renew their contract. In the event of not renewing the open source nature of our platform means that this is not a black box. The data will still be stored and accessible in whichever data repository was used to build the solution.

Using the service

Web browser interface
Supported browsers
  • Internet Explorer 11
  • Microsoft Edge
  • Firefox
  • Chrome
  • Safari 9+
Application to install
Compatible operating systems
  • Linux or Unix
  • MacOS
  • Windows
Designed for use on mobile devices
Differences between the mobile and desktop service
All BA Dashboard and Reports can be accessed via the desktop service; for mobile Advanced dashboards can be created specifically for interacting with dashboards and reports through mobile devices.
Service interface
Description of service interface
Users will logon to the support portal to raise and manage support tickets. This portal gives them access to knowledge base and Hitachi Vantara support teams.
Accessibility standards
WCAG 2.1 AA or EN 301 549
Accessibility testing
What users can and can't do using the API
All BA Server components can be controlled via the API's:
REST API - allows creation of custom applications that interact with Pentaho data.
Analyzer External JavaScript API - allows for more fine-grained interaction with the Pentaho Analyzer viewer, reports, and data.
JavaScript API - This API exposes key Pentaho platform information and services to JavaScript components.
Community Dashboard Framework (CDF) API - allows control of a Pentaho dashboard lifecycle without any Java coding.
API documentation
API documentation formats
API sandbox or test environment
Customisation available
Description of customisation
The Pentaho Platform is an end to end data engineering, data preparation and data analytic framework. This is used for a customer to build customized data analytics solutions. This may include connecting to almost any type of data source, ingesting and onboarding any type of data to carry out advanced analytics to answer any type of business question via the insights built into the solution. The front end can be a set of self serve dashboards, interactive reports, pixel perfect reports or advanced dashboards to provide a bespoke user experience.


Independence of resources
Pentaho software is easily scalable by adding more cores or more machines to build a Pentaho cluster. The demand on the service will be factored in when sizing the environment.


Service usage metrics
Metrics types
The BA server provides usage metrics including:
-Amount of time it takes a report to run
-File names of all content failures within a defined length of time
-Compare login metrics for days within a specified month
-Compare login metrics for a days in a week within a specified year
-List of content sorted by type, used within a defined length of time
-List of content usage within a defined length of time
-Compare login metrics by hour for a specified day
-Length of time for logins and the number of logins per user for specified length of time
Reporting types
  • API access
  • Real-time dashboards
  • Regular reports
  • Reports on request


Supplier type
Not a reseller

Staff security

Staff security clearance
Conforms to BS7858:2012
Government security clearance
Up to Developed Vetting (DV)

Asset protection

Knowledge of data storage and processing locations
Datacentre security standards
Complies with a recognised standard (for example CSA CCM version 3.0)
Penetration testing frequency
At least every 6 months
Penetration testing approach
‘IT Health Check’ performed by a CHECK service provider
Protecting data at rest
Other data at rest protection approach
We do not store data at rest within our system. We rely on the encryption services of the data store chosen by the customer that we connect to.
Data sanitisation process
Equipment disposal approach
Complying with a recognised standard, for example CSA CCM v.30, CAS (Sanitisation) or ISO/IEC 27001

Data importing and exporting

Data export approach
Within PDI transformations can easily be configured to export data from any data source, database or repository. From the BA server users have the ability to export underlying data into pdf, csv or Excel format.
Data export formats
  • CSV
  • ODF
  • Other
Other data export formats
  • Text File (PDI)
  • XML (PDI)
  • JSON (PDI)
  • RDBMS Table (PDI)
  • JMS Message Queue (PDI)
  • Kafka Message Queue (PDI)
  • MQTT Messgae Queue (PDI)
  • S3 Output (PDI)
  • Excel (PDI + BA)
  • PDF (BA)
Data import formats
  • CSV
  • ODF
  • Other
Other data import formats
  • Text
  • Excel
  • XML
  • JSON
  • RBBMS Table
  • HL7
  • S3
  • JMS Message Queue
  • Kafka Message Queue

Data-in-transit protection

Data protection between buyer and supplier networks
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
Data protection within supplier network
TLS (version 1.2 or above)

Availability and resilience

Guaranteed availability
The availability of the system is set by the hosting platform for the service.
Approach to resilience
Pentaho can be configure to run in High Availability mode. The result will be the user does not experience any down time. This is part of standard configuration.
Outage reporting
Can be monitored with SNMP. (Simple Network Management Protocol is an Internet Standard protocol for collecting and organizing information about managed devices on IP networks and for modifying that information to change device behavior.)

Identity and authentication

User authentication needed
User authentication
  • Public key authentication (including by TLS client certificate)
  • Username or password
  • Other
Other user authentication
Access, security and authentication can be configured and setup to support a number of different security protocols. The standard protocols include LDAP and Active Directory, Kerberos and Granular Roles Based Access Controls. Pentaho security is built upon Spring Security which is a Java/Java EE framework that provides authentication, authorization and other security features for enterprise applications.
Access restrictions in management interfaces and support channels
Role Based Access Control is used to restrict access to different users. This can be used for example to give management users the ability to add new users or change access controls and specific reports.
Access restriction testing frequency
At least every 6 months
Management access authentication
  • Public key authentication (including by TLS client certificate)
  • Username or password
  • Other
Description of management access authentication
Single Sign on integration i.e. LDAP or any other security framework using the SPRING framework.

Audit information for users

Access to user activity audit information
Users have access to real-time audit information
How long user audit data is stored for
Access to supplier activity audit information
Users have access to real-time audit information
How long supplier audit data is stored for
How long system logs are stored for

Standards and certifications

ISO/IEC 27001 certification
Who accredited the ISO/IEC 27001
Our certificate comes from BSI
ISO/IEC 27001 accreditation date
Original Registration Date 2012-04-18; Effective Date 2018-04-18; Last Revision Date 2018-04-17
What the ISO/IEC 27001 doesn’t cover
Hitachi Vantara is certified to ISO/IEC 27001:2013 for: 'The provision of remote managed services for solutions delivered by Hitachi Data Systems and supported by the Global Service Operations Centre (Hitachi Vantara SOC) in accordance with the Statement of Applicability Version 2.0 dated July 2015.' SOCs are located in the UK, Hong Kong and Malaysia.
ISO 28000:2007 certification
CSA STAR certification
PCI certification
Other security certifications

Security governance

Named board-level person responsible for service security
Security governance certified
Security governance standards
  • ISO/IEC 27001
  • Other
Other security governance standards
ISO/IEC27005:2011 provides guidelines for information security risk management. Supporting the general concepts specified in ISO/IEC27001, it assists the satisfactory implementation of information security based on a risk management approach.
We are aligned with ISO27005 Risk Management Methodologies’ for applicable risk assessment requirements of the Hitachi Vantara services business.
Information security policies and processes
Hitachi Vantara information Security Policy and controls requirements are aligned with ISO/IEC 27001/27002:2013.​
Hitachi Vantara Remote Managed Services Division is certified to ISO27001:2013

Operational security

Configuration and change management standard
Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Configuration and change management approach
Hitachi Vantara Change Management Process is established using ITSM best Practices. All changes are reviewed by the key stakeholder as part of CAB which is chaired by Change Manager.
All user impacted changes are communicated through weekly IT service bulletin.

The change management process is reviewed every year as part of the ITGC SOX Controls. ​Our change management process includes a weekly meeting where changes are presented to a board of members from various departments in IT to review, discuss, and approve the changes.  Information Security has a seat on the board.
Vulnerability management type
Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Vulnerability management approach
We are happy to get in contact with the customer and provide them with a walkthrough of our Threats & Incidents Response and Vulnerability management program. We have a program in place and we are working with multiple development and engineering to ensure immediate and timely response to disclosed vulnerabilities and we are coordinating with Hitachi Global incident response team in Japan. In fact, Eric Hibbard CTO of Security and Privacy in HDS is a lead consultant guiding and leading all these efforts and sits on a number of oversight committees within the industry, such as ISO.
Protective monitoring type
Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Protective monitoring approach
IPS/IDS and event Monitoring is provided using ActiveGuard solution. Monitored events and incidents are correlated against known threats and anomalies recognised in the security industry and based upon thresholds are actively alerted to Hitachi for immediate action.
Where necessary, Hitachi mat invoke the use of the SIRT to immediately act. The SIRT is made up from representatives of the whole Hitachi organisation and carries the skills identified as required to deal with such incidents.
Incident management type
Supplier-defined controls
Incident management approach
GEO Incident Management Team and Corporate Crisis Management Team is in-place to manage any major incidents. Hitachi Vantara has a robust Incident Management Team (IMT) Plan which includes Communications team members and should an incident occur that would impact customer, the account manager or IMT would notify the customer immediately. If there is a business need, we are happy to set up a specific escalation plan with the Customer.

Secure development

Approach to secure software development best practice
Independent review of processes (for example CESG CPA Build Standard, ISO/IEC 27034, ISO/IEC 27001 or CSA CCM v3.0)

Public sector networks

Connection to public sector networks
Connected networks
  • Public Services Network (PSN)
  • Police National Network (PNN)
  • NHS Network (N3)
  • Joint Academic Network (JANET)
  • Scottish Wide Area Network (SWAN)
  • Health and Social Care Network (HSCN)


£3247 to £15648 per unit per year
Discount for educational organisations
Free trial available
Description of free trial
We offer a 30 day demo key with a trial download.
Link to free trial

Service documents

Return to top ↑