Based on the data only, you can see the ticket execution, status, and dashboards. Ignio does processing of raw data on ignio side and not SAP side. So data storage is required.
Based on the data only, you can see the ticket execution, status, and dashboards. Ignio does processing of raw data on ignio side and not SAP side. So data storage is required.
For the IDoc use cases , the following will be read and stored temporarily in ignio to be able to read and perform the use cases successfully.
IDoc no, Current status, Pre-processing no, Message no, Error type, Reprocessing status, Control records, Status records, Segment records.
The stored data can be removed after some retention period either manually or through script in case the need is over.
ignio would need limited authorizations to be able to fulfill the use cases identified for a customer. Other Master data or transactions of a customer are not impacted by ignio.
ignio platform 5.0.
Client Services/CBO/Account team/Customer Support team are our deployment partners.
It is in the roadmap.
Yes. ignio™ has audit or traceability capabilities. This is done by logging all the operational activities either in the database or in the filesystem in form of detailed logs.
Yes. ignio™ produces reports that are both executive and operational in nature.
Yes. Prioritization of incidents can be handled in the following two ways:
ignio™ Product Team recommends Option 1.
There is no dependency.
Please refer https://digitate.atlassian.net/wiki/spaces/ID/pages/3776644850/Eagle+AI.ERPOps+5.0+Catalogs
No. Custom use cases written in Cheetah or Dragon will work in Eagle.
Twenty-Nine (29) customers are live and others are in progress globally.
There are 50+ customers across all geographies
Yes, Eaton (PR on website); JnJ and Astellas (in HBR report), Coop Sweden, Woolworths
Refer the custom use cases maintained by the respective TAMs in Kendriya portal. The Kendriya portal link is https://digitate-iwt-kendriya-f1.onignio.com/iwt-kendriya/#/login
Please send an email to the product owner for access –
Contact AI.ERPOps environments team –
Sapphire is the demo environment for AI.ERPOps. Refer to Eagle | AI.ERPOps 5.0 | Sapphire Good Clicks for use case coverage.
ignio™ AI.ERPOps high level architecture document is located at Eagle | AI.ERPOps 5.0 | Understanding Architecture
There is a good click ticket under “basis admin” which has SHC, Web UI, and HANA DB in a single ticket. You can stich a story around multiple systems, different technology and tiers etc.
For example, SAP apps, Java stack/portal apps, Database checks
With customization, you can monitor some of the other apps like Web Dispatcher, PO, GRC, Ariba apps as well.
Refer to the following link: Eagle | AI.ERPOps 5.0 | Sapphire Good Clicks
Yes, refer to the following link: Eagle | AI.ERPOps 5.0 | Sapphire Good Clicks
Yes, You can find them hosted on Digitate website and on AI.ERPOps product marketing channel. https://digitate.com/case-studies/
Please refer confluence link for details. : Eagle | AI.ERPOps 5.0
For marketing documents: Eagle | AI.ERPOps 5.0 | Marketing and visit product marketing Teams channel for all marketing collateral
Refer to the website: https://digitate.com/ignio-ai-erpops/
Technically WLM is a part of platform. Regarding additional pricing information, coordinate with the sales team.
Yes, that is possible but may depend on the terms of the contract. Additional charges may be required for the shift depending on the effort.
Currently, there are two channels for our customers to subscribe:
The pricing model is based on:
However, it may depend on other factors such as different SAP products involved, etc. and decided on a case-to-case basis.
The various components upon which pricing is dependent are:
The above information is subject to change, and it depends upon the contract signed. It may vary from case to case.
ignio can integrate out-of-the-box with S4/HANA and ECC only. However, for one pharma customer using AI.ERPOps extension, the customer services team integrated Success Factor (SaaS product) successfully.
Installing Add-on is one of the prerequisites to run the OOB use cases.
You need both WLM and AI.ERPOps for this integrated use case to work. There is a separate SAP job management capability in the standalone AI.ERPOps product as well with different features. Refer to https://digitate.atlassian.net/wiki/spaces/ID/pages/3776928962 for using Job Management feature.
Yes, but not in near future.
ignio AI.ERPOps supports Transport Impact Analysis use case.
This is not available out of box but can be achieved through customization.
Alerts from ServiceNow are not integrated with AI.ERPOps yet.
No, ignio™ cannot integrate with Solution Manager Service Desk.
Yes, it is possible to integrate with various ignio™ products and that is part of the long-term roadmap.
Currently, ignio™ AI.ERPOps is integrated with WLM
Yes. ignio™ can certainly append updates to Remedy incident in the work log field.
For any ITSM tool integration feasibility need to be checked based on type of interface APIs provided by ITSM.
ignio™ integrates with ServiceNow, Remedy, and Cherwell.
Yes, the audit information is stored in ignio. It can be accessed via APIs exposed by ignio.
ignio does not send email “as” customer account email. It can send email as email@example.com. But an email box can be created in a customer’s email server by the customer’s admin, and the same can be used by ignio proxy to send/receive emails. For example, firstname.lastname@example.org can be used by ignio proxy, where ignio will store the email and password to authenticate with Cargotec’s email server.
There are the following types of users:
AI.ERPOps takes care of such keywords by performing rigorous checks such as ATC.
Yes. It is enabled.
ignio™ product support for bug fixing or configuration issues is provided as per the contract.
Yes, all the custom SAP add-ons for ignio™ AI.ERPOps can be uninstalled. Refer to Eagle | AI.ERPOps 5.0 | Add-On Installations and Upgrades
No, since its TCS internal, ignio™ AI.ERPOps cannot provide the namespace repair key.
Please check digitate store for above deliverables.
No special access is needed other than what is asked as pre-requisite. SSH is used to have security connection between proxy and ignio.
Typical time to deploy ignio AI.ERPOps (non-HA mode) for the following activities is 1 to 2 days for SaaS, provided all pre-requisites and access requests are fulfilled.
Use case configuration and e-Bonding configuration for use cases is a separate activity based on the solution designed for each use case.
There is a specific set of authorization objects (role) based on the capability. Refer to Eagle | AI.ERPOps 5.0 | List of SAP Authorizations Objects
Yes, like any other SAP ABAP stack systems, Solution Manager also supports secure integration along with all the compatible aspects such as SNC, JCO, ignio™ AI.ERPOps proxy security, and encryption.
Please refer to this link:
ignio AI.ERPOps is GDPR compliant. As part of IPSafe certification, Data Privacy assessment is conducted and approved for every release.
PII data fields such as first name, last name, address, fax are identified. The following measures have been taken to ensure GDPR compliance:
This is by design of proxy, which uses these ports to communicate with ignio and do data transfer of various kinds of data like raw data and commands to/from ignio to connect to ITSM and targets within customer DC.
Yes, ignio is deployed on Digitate’s azure cloud, and its publicly available so that proxy can reach ignio.
Yes, multiple SAP users can be used for individual ERPOps capability. Each of these capabilities can have restricted domain specific access.
No. Once its stored in ignio’s DB, then only it can be pushed to Shukra. But this development should be done by CS/PS/Customer, not by ERPOps product team.
All AI.ERPOps use cases work on SAP which is hosted on any public or private cloud.
Yes. All the AI.ERPOps APIs are exposed. You can see the data that AI.ERPOps stores.
ignio proxy is like a mid server that sits in a datacenter, pulls work from central ignio™, connects to various target systems, and performs actions.
Yes, VM Logging must be enabled on ignio™ servers to monitor the application services.
It is the standard recommended minimum sizing for ignio™ AI.ERPOps product. It varies based on the features and workload. Sizing is scalable for increased volume.
Currently, ignio™ AI.ERPOps delivers .SAR file SAP system wise such as ECC and S/4HANA.
System user (Non-dialog user)
SAP has provided a JCO connector free of charge to customers who have an SAP license. Customers need to download and install the JCO connector inside the ignio proxy. This JCO library is used by ignio to connect to SAP systems.
No additional SAP License is required to integrate ignio with SAP except the named user (system type) license which connects to SAP systems.
The following skills are needed to write custom SAP use cases.
Here is the link of ignio AI.ERPOps customization document: Eagle | AI.ERPOps 5.0 | Customization Guides
Prerequisites expected from the customer are mentioned in the following Confluence links. https://digitate.atlassian.net/wiki/spaces/ID/pages/3776645174/Eagle+AI.ERPOps+5.0+Prerequisites
For each ticket, ignio™ logs some details in the log files. The maximum size of these files is 10MB. After the 10 MB size is reached, the log file is compressed, and a new file is created. (This is a standard product feature and is applicable for all other appliances. In case of any issues in logging, connect with the support team).
Key architecture features used for performance and scalability are:
No, ignio™ AI.ERPOps needs custom SAP add-on to be deployed in customer SAP systems.
Yes, ignio™ AI.ERPOps has an architecture documentation which can be found here: Eagle | AI.ERPOps 5.0 | Understanding Architecture
In case you do not have access to the attached link, please connect with your Digitate Alliance representative.
The SAP add-on (PAT) file contains ignio’s ABAP programs for use cases execution. They are written in its own namespace. For more details, refer https://digitate.atlassian.net/wiki/spaces/ID/pages/3776649057
The general recommendation is to always install custom ignio™ SAP add-on during off-peak hours.
The process to uninstall SAR file is like PAT file. Basically .SAR is compressed form of .PAT file only.
Refer to Eagle | AI.ERPOps 5.0 | SAP Add-on Release and Installation Process
There is no impact. Refer to Eagle | AI.ERPOps 5.0 | SAP Add-on Release and Installation Process
JCO connector is SAP AG certified. It has already passed the GxP, a regulatory security compliance for pharma customers. It is plug and play type utility present out-of-the-box.
JCO is capable of handling large number of use cases used by ignio in ERP SAP Manufacturing applications.
Error handling also becomes easier in the JCO/RFC scenario.
Also, by “wrapping” JCO/RFC/BAPI logic in MII (Mfg intelligence and Integration and Analytics) BLS (BAPIs) transactions, it creates a reusable, simplified (reduced no of inputs/outputs) services for ignio to invoke in ERP SAP application.
JCO is tightly coupled integration which probably is the best in using technical integration where ignio understands all the stable end points.
The main reason why it can’t work is because a PAT file contains more than 600 SAP programs. We have used many programs which are common between the 2 PAT versions and we do not make changes to all the programs. Therefore, we cannot use both old and new at the same time.
Also, in SAP when we upgrade the newer version it goes and overwrites the older PAT (all programs). Technically, we cannot store SAP PAT file programs in the database which have 2 “active” versions.
In order to install ignio custom add-on in the SAP system, one needs minimum authorizations. This is a standard SAP requirement and holds true not only for ignio add-on, but for any SAP patch that needs to be installed. The Basis BD team must be able to identify any suitable user with relevant authorization per their organization’s policies. There are many SAP standard links available on this ask. One that I came across is https://help.sap.com/saphelp_ssb/helpdata/en/49/3e896a28ab2222e10000000a42189d/frameset.htm
The average size is around 3 to 4 MB.
You need to provide SAP component version and SAP product version. The details are available in SAP at SYSTEM > STATUS.
It is in the product roadmap.
Yes, that’s correct. It can be used to monitor both SAP ABAP (Webdynpro) and Java web-based applications.
No, the SHC dashboard gives live monitoring and HC view of critical admin level checks on a single or multiple systems
The addition of custom transaction in SHC completely depends on individual business process requirements. It can be easily developed per the solution design and with the customer’s technical team.
Cumulatively added new self-heal in System Health Check capability such as SAP system traces, SAP Logon group configurations, SAP RFC Server group configurations checks. Currently, there are more than 28 catalog items across various capabilities. Refer to Eagle | AI.ERPOps 5.0 | Catalogs for more information.
You can add multiple email IDs but not separately for each TCode at single node.
In case of ignio, SM13 TCode signifies whether all the update process are active or not. The values mentioned are of SAP standard RC(VBRC)- return codes for SM13 updates. Refer SAP standard documentation for the same.
Govern dashboard for real-time monitoring of SAP. The system health check includes trend analysis, latest work items viewing features. The dashboard is also available for IDoc management.
Yes, ignio AI.ERPOps provides self-heal actions for System Health Check capability.
Yes, SAP system health check can be implemented for multiple systems in one go.
The KPI metrices that are configured in Solution Manager are considered for the profile vital and threshold.
Solution Manager provides graphs. However some of the functionalities such as insights, risks, predictions, integration with problem tickets are currently not available.
Solution Manager capabilities are:
Solution Manager Alert Integration -Alert aggregation, suppression to find true alerts in the alert flood
Analytics – Profiling, Correlation and Predictive data Analytics on Solution Manager KPIs
As of now it’s SM 7.2. The integration works in the same way as ERP and S/4 HANA.
ignio™ AI.ERPOps based product offerings can supplement Solution Manager functionalities to deliver customers a win-win proposition. Ignio™ AI.ERPOps possesses capabilities over and above the Solution Manager and provides you with out-of-box use cases to resolve the issues with the technical monitoring data, provides you with insightful analytics on it, and handles problems with ChaRM. ignio™ supports the latest version of SAP Solution Manager (SAP Solution Manager 7.2). Please refer the following link for the more details:-
Service based approval can be configured through SR policy. Refer for Eagle | AI.ERPOps | Service Request Configuration Manual 5.0
With ignio™ AI.ERPOps, you can not only automate onboarding but also automate all routine user/role/password management requests such as :
Create User, User Modifications/Changes, Password Reset, Lock/Unlock Users etc.
Note: It depends upon the user onboarding process for enterprise.
One user entity represents one user in SAP. It’s the design of ignio to have such entities which will allow AI/ML operations to be performed for user management use case.
EWA is very static in nature. It is based on cloud-SMP logic to validate SAP systems against set or pre-configured parameters. PCM on the other hand can adapt based on the SM KPI metrics that that you feed.
PCM KPIs complement Solution Manager. With PCM, you can also ingest data manually in SAP landscapes.
Refer to row no 48 of https://digitate.atlassian.net/wiki/spaces/ID/pages/3776644118
There is no limitation. There is also the chunking logic added to keep the update of records to minimum in each call to SAP.
There are internal SAP adapter programs written to update SAP master data records based on approval and necessary validations. Missing master data generally is updated by business teams based on their knowledge. For example, vendor payment terms, material or article prices are all governed by the business teams.
For self healing, ignio suggests some recommendations.
Yes, AI.ERPOps makes use of artificial intelligence which is implemented via programming for each KPI.
Master Data Sanity check capability checks inconsistency within the systems only. For example, Inconsistency of Production system
In AI.ERPOps 5.0 release, Master Data Sanity Check Self-heal feature is introduced which rectifies the
Master Data Inconsistencies as well. Refer to Eagle | AI.ERPOps 5.0 | Master Data Sanity Check (MDSC) – Check Master Data User Guide
ignio™ MDSC does inconsistency and missing master data checks post the implementation phase.
Yes. However, ABAP and Java coding is required to implement this type of customization in sanity check.
The missing delivery plant KPI is maintained in Customer Master.
Material Price – Material
Storage Location – Storage Location
Payment Term, Bank Details – Vendor
Shipping Condition, Delivering Plant – Customer
You can customize your own custom master and custom KPIs.
Yes. ignio™ can predict it. Conflict, missing transports, version mismatch of the objects is included in this check.
ignio AI.ERPOps Impact Assessment supports ABAP Transports only.
ignio stores the new data again.
ignio AI.ERPOps sends IDoc dashboard link via email. User needs to have ignio authentication to access the dashboard link.
No. ignio™ AI.ERPOps only sends the link.
It is generic for certain standard SAP message types and error codes. User can configure customer specific self heal using customization.
You need to first run the work item API to find the latest IDoc ticket and then run IDoc API by using the IDoc ticket to get the IDoc data.
Yes. The segment level report is available in AI.ERPOps 4.1 and later.
Financial impact is in critical IDocs and error code detail report.
ignio AI.ERPOps provides Failed IDoc Financial impact summary and Business process wise summary from Dragon and above.
Yes, the HANA DB use cases are available in 4.1. Please refer our version wise catalog for details at https://digitate.atlassian.net/wiki/spaces/ID/pages/3776644850 . It is supported for both SUSE and Red Hat (RHEL) Linux flavors. However, the supported version would depend on what AIOps support as OOB.
The use cases are for SAP S/4HANA database. That means, a use case works for HANA DB users. Foe example, users who connect to HANA DB for modelling usage, admin users or business/functional users who execute views based programming.
No. The product currently does not have any capability that directly helps in migration. But the existing capabilities are supported on S/4 HANA and thus can be utilized during migration as well.
Yes, HANA DB monitoring is supported in ignio™ AI.ERPOps Dragon releases and later.
Yes. It is possible to create an ITSM ticket.
Not at the moment. You can download in .csv format and can do the modification.
ignio™ is providing consolidated list of Open PO including financial impact of open PO which has impact on regular MRP run. ignio is providing open PO and self heal to close the open POs based on different selection.
Yes, based on use case feasibility, customization can be done in ignio™ AI.ERPOps.
It can be developed in Studio only.
Yes, ignio™ AI.ERPOps have compliance capability to cover SAP Basis key parameters, Operating System and Database controls.
Refer to Compliance Configuration Manual : Eagle | AI.ERPOps 5.0 | Compliance Configuration Guide
Refer to Compliance User Manual : Eagle | AI.ERPOps 5.0 | Compliance BASIS DB OS Functional User Guide
Yes. For each plant, sales organization, production organization and so on, you need to create a separate node for one time task.
You can use data sources in case of large numbers.
SAP user entity discovery is supported.
Blueprint ingestion for SAP instances can be done through file.
For more information, see Eagle | Blueprint Configuration Manual 5.0 – ignio Docs – Confluence (atlassian.net)
SAP business processes are not supported in blueprint.
ignio™ provides an intuitive dashboard that provides a detailed ABAP dump analysis with categorization and SAP best practice recommendations for exceptions and errors.
It summarizes all the work items which are being executed based on configurations, for example, every 5 minutes.
Approval is through email. ‘Approved’ or ‘Rejected’ must be written in email subject while replying.
ignio AI.ERPOps supports auto refresh in System Health Check and IDoc Management as a part of Govern dashboard.
SAP Ariba is in a roadmap.
No. ignio™ AI.ERPOps does not have any reference use cases.
It doesn’t matter as long as proxy can reach ignio and targets. Multiple proxies can be setup as well.
Yes. ignio™ AI.ERPOps is independent and it only needs the ignio™ platform and not AIOPs.
Fitment can be computed based on:
Summary is included in the email for some use cases. But to see the report, you must have access to Ignio™.
ignio has built in-house custom capabilities/knowledge using ABAP programs which is used to collect various data from SAP targets and perform various actions.
Dashboard Report URL for Sanity Health Check, IDoc, ABAP Dump Analysis and other capabilities is sent to the email ID configured in policy. Users must have authentication to access URL
SAP integration certification ensures that the ignio™ AI.ERPOps product integration with the SAP environment is safe, secure, and compliant with SAP standards and policies. This certificate confirms the technical compliance of the product with SAP certification procedures.
ignio™ AI.ERPOps neither competes with nor complements CHaRM. But, as an extension of customization, ignio™ AI.ERPOps can integrate with CHaRM.
CHaRM is being used for transport management. ignio™ AI.ERPOps can integrate CHaRM for E2E automation with customizations.
Yes, ignio™ AI.ERPOps can connect to SAP systems hosted on HEC.
Yes, ignio™ AI.ERPOps 4.1 and 5.0 is available only on SaaS.
No, ignio™ AI.ERPOps does not support SAP APO.
Yes, ignio™ AI.ERPOps automates the recurring technical and functional issues in SAP AMS area that can avoid manual errors and helps in effort reduction.
Yes, ignio™ AI.ERPOps supports SAP systems hosted on cloud per our SAP product coverage scope. Also, Ignio proxy must have direct and secure network connectivity to SAP targets.
No, it does not. However, ignio AI.ERPOps supports the extensibility feature, where the deployment teams (PS, pilot etc.) can work with respective account teams to do their own development in the customer’s landscape. In case you do not have access to the attached link, connect with your Digitate Alliance representative.
Yes, ignio™ AI.ERPOps takes up new SAP products based on the usability and adaptability in the market and after considering its stability.
Yes, ignio™ AI.ERPOps 5.0 has limited support for SAP Java stack.
Yes, ignio™ AI.ERPOps is SAP certified for both SAP ECC and S/4 HANA.
Yes, it is S/4HANA certified.
Multilingual support available in ignio platform UI Labels applies to ignio™ AI.ERPOps as well. Multilingual support in ITSM integrations is same as that supported by ignio platform. Support for multilingual for ignio™ AI.ERPOPs specific use cases, dashboards is made available for new languages as per the requests and in upcoming releases. ignio™ AI.ERPOps supports Spanish to some extent. More languages could be added as part of future releases.
ignio™ AI.ERPOps is available only on SaaS provided by Digitate.
Core modules of ECC such as FI, MM, and SD are supported. Other modules can be supported through customization.
The product supports a vast array of popularly used SAP ERP technologies. These include ECC 6.0 – EHP 5, EHP 6, EHP 7, EHP 8 ; S/4 HANA 1709, S/4 HANA 1809, S/4 HANA 1909, S/4 HANA 2020, S/4 HANA 2021 ; Solution Manager 7.2, among others.
Notifications (like e-mails) sent by ignio can be viewed on Android and iOS.
The product supports SAP ERP as of now.
ignio™ AI.ERPOps defines AI as ability of the machine to reason out a solution to the given problem in a situation and be able to resolve it autonomously.
Anomaly detection, pattern mining, trend analysis, event correlation, proactive health checks, root cause analysis , rule- based reasoning are some of the key AI practices that have been embedded in AI.ERPOps
The USP for AI.ERPOps are:
A product that caters to both technical and functional issues in SAP operations – Caters to BASIS Admin, aids in User
Management, integrates with Solution Manager, and works well within core functional modules such as FI, MM, and SD.
Business group :
Operations group :
ignio AI.ERPOps –
ignio™ AI.ERPOps – An AI based insight driven product for autonomous SAP operations , catering to SAP Technical and Functional domains. It improves business outcomes by detecting anomalies, providing analysis with recommendations, and performing actions.
You can find the ignio™ AI.ERPOps catalogue at Eagle | AI.ERPOps 5.0 | Catalogs:
Download the excel file to read in detail. In case you do not have access to the attached link, connect with your Digitate Alliance representative.
There is single connector but multiple ABAP program which can be termed as adaptor to Sap. So we need one service account and Authorization in sap.
Yes, available as part of the release. Yes, whatever shown and in catalogue are OOB
In addition to host OS HC, we have a lot of HANA DB specific checks. E.g. tenant DB health, processes, stats info etc. BTW, there are more than 75 HANA DB health checks, Compliance & Security use cases introduced in this release. Details are available in the latest catalog.
We are taking based on priority and modules configured in lab. Let’s know afew which you want and we will check the feasibility
Need to check with CS team. It is analysis based on data from SAP only. We did not get any feedback so far.
The frequency really depends on the need. Its configurable. Yes, there are focused email notifications available for job failures. We have almost doubled our usecases count as a delta as far as the catalog items are concerned. The majority being HANA DB usecases, Idoc enhancements, Job Management capability etc.
Yes, SAP HANA DB restarts including SAP app server restarts (in a logical business flow)
Solution Manager alert Mgmt can be done on any alert which SolMan fetches. Incidentally, SM can monitor both SAP and non-SAP components including Infra. The SM alerts are automatically ingested into the right BP entity (E.g. satellite systems). This includes auto identification of CI. E.g. SAP app servers in the format <Hostname_<SAP SID>_<SAP Ins No.>
Yes, the email approval contains all details so that approvals/rejections can be done. No, we do not create ITSM ticket for SHC, but create an ignio workitem id to track fault & fix progress
No WLM integration, not at the moment. However, we have a ERPOps SR to schedule a SAP job. With customization you can trigger a job after identifying its failure.
Yes, we do. E.g. the SAP instance entity depends on OS and DB entity in BP. We can have aggregation done for alerts in case there is a major failure where all VMs go down. In this case, you can just keep OS/DB VM alert alive and aggregate/close SAP ABAP instance unavailable alert.
Both BPMon and TechMon alerts can be correlated as their origin from SolMan is the same.
Its a pull mechanism using SolMan adapter that we have developed. Pre-reqs is the ABAP program that we deliver as an SAP add-on.
Yes, this is available in Alert Inbox capability which is being shown now. You could create ITSM alerts for SolMan alerts instead of self-heal.
Suppression samples for threshold can be for static and dynamic thresholds of a SolMan KPI where it can suppress static alerts