SEMI E39 (OSS) Overview

Introduction

The main purpose of SEMI E39 OSS is to provide a common set of object service specifications that help define and manage objects and their properties. Through standardized terminology and services, OSS enables different systems to read, set object properties, and request object contents in a consistent way. These services can be used independently or embedded in other standards.

Types of Services

SEMI E39 defines two main types of services:

  1. Notification: Notification-type messages are initiated by the service provider and do not expect a response from the consumer or subscriber. Usually used to push status updates or event notifications to subscribers.
  2. Request: A request message is initiated by a service consumer or subscriber to request data or perform a specific action. Each request message requires a specific response message, and the content of the response depends on the type of request.

Common object-oriented terms

  • Object Type: An object type is a formal classification of an object, usually represented as a text string. Standardized object types are retained by individual standards, ensuring consistency.
  • Object Identifier (ObjID): Each object instance has one or more properties that collectively uniquely identify the object. ObjID is the basic property of all public objects and is used to uniquely identify the object.
  • Object Handle: An object handle is a numeric property assigned by the application that created the object and used to identify the object.
  • Object specifiers (ObjSpec): In the request, ObjSpec is used to specify the proxy for the object creation service; in the response, it represents the object specifier for the new instance. If the object does not exist or is not in the domain of the receiving entity, the argument in the request can be an empty string.
  • Top Object: The top object is the supertype of all public objects and defines the basic properties and operations of all public objects. Each public object must respond to an ‘ObjType’ and a text string, and support operations to get and set properties.

Common Object Service

SEMI E39 defines a series of commonly used object services. Here are some of the key services:

  1. GetAttr service (SECS-II message: S14F1/F2): Used to read the attribute values of an object.
  2. SetAttr service (SECS-II message: S14F3/F4): Used to set the attribute values of an object.
  3. GetType service (SECS-II message: S14F5/F6): Used to get the type of an object.
  4. GetAttrName service (SECS-II message: S14F7/F8): Used to get the name of an object attribute.
  5. Create service (SECS-II message: S14F9/F10): A service consumer can request the service provider to create a new object and assign values to its properties. If you try to set a property that is not allowed, the request may be rejected.
  6. Delete service (SECS-II message: S14F11/F12): A service consumer can request the deletion of an object.
  7. Attach service (SECS-II message: S14F13/F14): A service consumer may request an object to be attached to itself.
  8. Detach service (SECS-II message: S14F15/F16): The manager of the attached object can request to detach the object.
  9. Reattach service (SECS-II message: S14F13/F14): An object can request to be reattached to another supervisor object.
  10. ObjectAction Service (SECS-II message: S14F19/F20): A service consumer can request a specific object to perform a specific action.
  11. Object Completion Notification (SECS-II message: S14F21/F22): This notification is sent by the service provider to the requester when a previously requested operation is completed.
  12. GetServiceNames service (SECS-II message: S14F25/F26): A service consumer can request a list of services it supports from the object owner.
  13. GetServiceParameters service (SECS-II message: S14F27/F28): A service consumer can request a list of parameters of its supported services from the object owner.

Summary

The SEMI E39 Object Service standard provides software technicians in the semiconductor industry with a powerful set of tools for managing and manipulating objects and their properties. Through standardized terminology and services, OSS not only improves system interoperability, but also reduces redundancy, enabling developers to build and maintain complex semiconductor manufacturing systems more efficiently.

To learn more about SEMI E39 solutions, please contact support@kxware.com.

For SEMI standards document, please visit the SEMI site: https://www.semi.org/en/products-services/download-standards.