ISO/IEC JTC 1 SC 42 Artificial Intelligence - Working Group 4
Use Cases & Applications 08/21/2019
The quality of use case submissions will be evaluated for inclusion in the Working Group's Technical Report based on the application area, relevant AI technologies, credible reference sources (see References section), and the following characteristics:
 Data Focus & Learning: Use cases for AI system which utilizes Machine Learning, and those that use a fixed a priori knowledge base.
 Level of Autonomy: Use cases demonstrating several degrees (dependent, autonomous, human/critic in the loop, etc.) of AI system autonomy.
 Verifiability & Transparency: Use cases demonstrating several types and levels of verifiability and transparency, including approaches for explainable AI, accountability, etc.
 Impact: Use cases demonstrating the impact of AI systems to society, environment, etc.
 Architecture: Use cases demonstrating several architectural paradigms for AI systems (e.g., cloud, distributed AI, crowdsourcing, swarm intelligence, etc.)
 Functional aspects, trustworthiness, and societal concerns
 AI life cycle components include acquire/process/apply.
Automatic generation of Daily Performance Report, reduction in overall drilling time, cut down Invisible Loss Time and improve rig asset management
Short Description (up to 150 words)
It is important for a drilling contractor to have real time monitoring of rig parameters to optimize operations. The customer lacked granular insights during drilling, could not ascertain the root cause of non-productive time, and manual interpretation of signals led to missing of anomalies further degrading performance.
Cerebra product extracted and ingested different types of signals from surface and downhole sensors to perform near real-time processing. More than 170 vital signals every second from each oil rig were processed by Cerebra to provide near real time insights into drilling operations. This was achieved by handling Data Format and Data Extraction standards and Cerebra’s Visualization Studio provides the flexibility of generating customized asset utilization reports, thus helping the oilfield engineers to understand the root causes of non-productive time and better utilize the assets on field. Rig specific utilization reports, and weekly and monthly utilization reports helped to plan drilling operations improving drilling efficiency.
Mandate of the key sensors based on the type of equipment Based on the type of equipment, the makers need to have the basic set on sensors imbibed onto the system. E.g. for a pump – it is important to measure the input flow and output flow rates, vibrations, rotation speed, lube oil temperature and pressure. This will guide the equipment manufactures to provide their customers and their data products to capture the minimum required data and understand the equipment performance.
Mandate for the organizations to expose the minimum and key parameters. The equipment owners need to enable the basic set of sensors for the equipment health and performance which are required for monitoring the asset from any failures.
Standards for data formats Each organization has a different way of capturing data and storing them in different formats. Due to which the solutions are not scalable across organizations though the product behind them is same. It takes customised efforts each time.
Guidelines for deciding the sampling frequency based on the type of data We see a need to have a specific set of guidelines to capture data at a minimum required sampling frequency. For e.g. a vibration sensor should capture data at least at 1 ms.
Guidelines for feature engineering There must be guidelines as to how the features need to be engineered for AI models. Lack of this would lead to more black box models not explaining how the models behave the way they do.
Guidelines for standardization of event types and codes There are multiple events which occur for an asset or in a manufacturing plant. Guidelines would help people capture the data in a similar fashion helping the industry to benchmark against one another and at industry level we can understand, which events are the most critical.
Guidelines for standardization of fault and error codes for an equipment or process Similar to events, it is also useful to capture fault, failure and error codes in a standard way.
Process guidelines for event related data (maintenance and work orders) Guidelines would help people capture the data in a similar fashion helping the industry to benchmark against one another and at industry level we can understand, which events are the most critical.
Peer-reviewed scientific/technical publications on AI applications (e.g. ).
Patent documents describing AI solutions (e.g. , ).
Technical reports or presentations by renowned AI experts (e.g. )
High quality company whitepapers and presentations
Publicly accessible sources with sufficient detail
This list is not exhaustive. Other credible sources may be acceptable as well.
Examples of credible sources:
 B. Du Boulay. "Artificial Intelligence as an Effective Classroom Assistant". IEEE Intelligent Systems, V 31, p.76-81. 2016.
 S. Hong. "Artificial intelligence audio apparatus and operation method thereof". N US 9,948,764, Available at: https://patents.google.com/patent/US20150120618A1/en. 2018.
 M.R. Sumner, B.J. Newendorp and R.M. Orr. "Structured dictation using intelligent automated assistants". N US 9,865,280, 2018.
 J. Hendler, S. Ellis, K. McGuire, N. Negedley, A. Weinstock, M. Klawonn and D. Burns. "WATSON@RPI, Technical Project Review".
URL: https://www.slideshare.net/jahendler/watson-summer-review82013final. 2013