1 Scope

This document provides a comprehensive overview of the Application and Use Cases defined in the OPC UA Companion Specification Mining. As explained in OPC 40560, this document contains definitions and descriptions of the Application and Use Cases defined by the Specialist Working Groups for machines and systems participating in discontinuous unloading process as part of the load-and-haul cycle.

2 Normative references

The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments and errata) applies.

OPC 10000-1, OPC Unified Architecture - Part 1: Overview and Concepts

OPC 10000-1

OPC 40560, OPC Unified Architecture for Mining - General

http://opcfoundation.org/UA/Mining/General/

3 Terms, definitions and conventions

3.1 Overview

It is assumed that basic concepts and motivations of OPC UA information modelling from OPC 10000-1 are understood in this document. This document will describe the abstract Application Case Dozing and its constituent Use Cases. These have been developed by a Specialist Working Group and serve as a base for the OPC UA information models of machines and systems taking part in dozing operations typically conducted in surface mining operations to clear a certain area from cluttered rock or soil.

Note that OPC UA terms and terms defined in this specification are italicized in the specification.

3.2 Abbreviated Terms

3.3 Conventions used in this document

For a definition and example of the terms of ‘Application Case’ and ‘Use Case’, please refer to OPC 40560.

4 Application and Use Cases of OPC 40569-4: Dozing

4.1 Application Case Dozing

The Application Case Dozing is composed of all defined and modelled Use Cases for a surface mining dozing operation. Specifically, this refers to rock clearing operations. The detailed descriptions and diagrams for the UCs belonging to this AC can be found in Chapter 4.2. Table 1 contains information regarding the chapter number of each Use Case within the AC Dozing and the involved equipment. The rows contain the different equipment types used within the Use Cases, which are displayed in the columns.

4.2 Use Cases for the AC Dozing

The Dozing AC consists of two interacting participants - a dozer and any other machine. Goal of this AC is to have the dozer machine clear a certain area. Typically, a surface mining load-and-haul operation causes the loading area to be cluttered with rock fallen from either the truck bed or from an excavator’s shovel. Any type of machine can then detect this and request the dozer to start clearing the area. To support autonomous, decentralized dozing operations, the following Use Cases describe the required machine communication between two a dozer and any other machine for requesting the dozer’s clearing operation and passing safely through an area that it currently being cleared by the dozer as depicted in Figure 1.

4.2.1 Use Case Request Dozing

Any machine can request a dozer machine to perform a dozing job in a specific area. The mobile machine capable of doing dozing jobs, provides a SetWorkJob-Method. When calling this method, the other vehicle needs to pass three arguments: The first argument is a list of cartesian coordinates defining a 3D Polygon as a working area. The second argument is list of cartesian coordinates defining a 3D Polygon as a dump area. The dump area can be null, if the dozer is free to decide where to dump the soil and rock. The third argument is a number defining the job type, the dozing machine should perform. These include, amongst others,

Clean-Up operations

Ripping operations

Topsoil-Removal operations

Blast-Clean-Up operations etc.

A graphical representation of the UC is depicted in Figure 2.

4.2.2 Use Case Dozing

Given that a dozer machine is performing dozing operations in a specific area, the dozer occupies a certain working area, which is not safe to pass for other machines. This area is defined as an ExclusionZone. Other machines can read the ExclusionZone of the dozing machine. If the other machine wants to enter the ExclusionZone, the other machine can interrupt the dozer in its current operation.

Stopping the dozer from performing its current operation is made possible by being able to call the RequestStopOperation-Method or the ClearWay-Method provided by the dozer. The RequestStopOperation-Method stops the dozing machine’s operation and indicates that the dozer should not move at all. When calling the ClearWay-Method, the other machine needs to pass a list of CartesianCoordinates, defining a 2D Polygon, as an input argument for the method. The dozing machine then moves out of this area.

The other machine can subscribe the ExclusionZone of the dozer to receive notifications about updates to the dozer’s ExclusionZone. As soon as the dozer has stopped (if the RequestStopOperation-Method was called) or moved out of the area (if the ClearWay-Method was called), the ExclusionZone of the dozer changes, since the area is safe to pass now. The other machine can now pass safely. After leaving the former ExclusionZone, the other machine can call the method ResumeOperation. Then, the dozer continues its previous operation and changes the ExclusionZone to what it was before.

A sequence diagram of this UC interaction is shown in Figure 3.

4.2.3 Use Case ParameterSubscription

The ParameterSubscription UC allows any mobile machine to request meta-information, such as AssetId or DeviceClass of another mobile machine. As mobile mining machines, such as a hydraulic excavator, dozer or a dump truck, typically roam around freely, it becomes necessary, in the context of an autonomous, decentralized operation, for machines to inform each other about their current location and device type. Using the variables described in this UC, this information can be requested or subscribed. A sequence diagram of this UC is depicted in Figure 4.

___________

Agreement of Use

COPYRIGHT RESTRICTIONS

This document is provided "as is" by the OPC Foundation and VDMA.

Right of use for this specification is restricted to this specification and does not grant rights of use for referred documents.

Right of use for this specification will be granted without cost.

This document may be distributed through computer systems, printed or copied as long as the content remains unchanged and the document is not modified.

OPC Foundation and VDMA do not guarantee usability for any purpose and shall not be made liable for any case using the content of this document.

The user of the document agrees to indemnify OPC Foundation and VDMA and their officers, directors and agents harmless from all demands, claims, actions, losses, damages (including damages from personal injuries), costs and expenses (including attorneys' fees) which are in any way related to activities associated with its use of content from this specification.

The document shall not be used in conjunction with company advertising, shall not be sold or licensed to any party.

The intellectual property and copyright is solely owned by the OPC Foundation and VDMA.

PATENTS

The attention of adopters is directed to the possibility that compliance with or adoption of OPC or VDMA specifications may require use of an invention covered by patent rights. OPC Foundation or VDMA shall not be responsible for identifying patents for which a license may be required by any OPC or VDMA specification, or for conducting legal inquiries into the legal validity or scope of those patents that are brought to its attention. OPC or VDMA specifications are prospective and advisory only. Prospective users are responsible for protecting themselves against liability for infringement of patents.

WARRANTY AND LIABILITY DISCLAIMERS

WHILE THIS PUBLICATION IS BELIEVED TO BE ACCURATE, IT IS PROVIDED "AS IS" AND MAY CONTAIN ERRORS OR MISPRINTS. THE OPC FOUDATION NOR VDMA MAKES NO WARRANTY OF ANY KIND, EXPRESSED OR IMPLIED, WITH REGARD TO THIS PUBLICATION, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF TITLE OR OWNERSHIP, IMPLIED WARRANTY OF MERCHANTABILITY OR WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE OR USE. IN NO EVENT SHALL THE OPC FOUNDATION NOR VDMA BE LIABLE FOR ERRORS CONTAINED HEREIN OR FOR DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, RELIANCE OR COVER DAMAGES, INCLUDING LOSS OF PROFITS, REVENUE, DATA OR USE, INCURRED BY ANY USER OR ANY THIRD PARTY IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The entire risk as to the quality and performance of software developed using this specification is borne by you.

RESTRICTED RIGHTS LEGEND

This Specification is provided with Restricted Rights. Use, duplication or disclosure by the U.S. government is subject to restrictions as set forth in (a) this Agreement pursuant to DFARs 227.7202-3(a); (b) subparagraph (c)(1)(i) of the Rights in Technical Data and Computer Software clause at DFARs 252.227-7013; or (c) the Commercial Computer Software Restricted Rights clause at FAR 52.227-19 subdivision (c)(1) and (2), as applicable. Contractor / manufacturer are the OPC Foundation, 16101 N. 82nd Street, Suite 3B, Scottsdale, AZ, 85260-1830

COMPLIANCE

The combination of VDMA and OPC Foundation shall at all times be the sole entities that may authorize developers, suppliers and sellers of hardware and software to use certification marks, trademarks or other special designations to indicate compliance with these materials as specified within this document. Products developed using this specification may claim compliance or conformance with this specification if and only if the software satisfactorily meets the certification requirements set by VDMA or the OPC Foundation. Products that do not meet these requirements may claim only that the product was based on this specification and must not claim compliance or conformance with this specification.

TRADEMARKS

Most computer and software brand names have trademarks or registered trademarks. The individual trademarks have not been listed here.

GENERAL PROVISIONS

Should any provision of this Agreement be held to be void, invalid, unenforceable or illegal by a court, the validity and enforceability of the other provisions shall not be affected thereby.

This Agreement shall be governed by and construed under the laws of Germany.

This Agreement embodies the entire understanding between the parties with respect to, and supersedes any prior understanding or agreement (oral or written) relating to, this specification.