ISA 50.02-5 : 1998

Introduction
1 Scope
2 Normative References
3 Definitions
   3.1 ISO/IEC 7498 terms
   3.2 ISO/IEC 8822 terms
   3.3 ISO/IEC 9545 terms
   3.4 ISO/IEC 8824 terms
   3.5 Fieldbus Data Link Layer terms
   3.6 FAL Specific Definitions
   3.7 Abbreviations and Symbols
   3.8 Conventions
4 Concepts
   4.1 Architectural Relationship
   4.2 Fieldbus Application Layer Structure
   4.3 Fieldbus Application Layer Naming and Addressing
   4.4 Architecture Summary
   4.5 FAL Service Procedures and Time Sequence Diagrams
   4.6 Common FAL Attributes
   4.7 Common FAL Service Parameters
   4.8 APDU Size
5 Object Management ASE
   5.1 Overview
   5.2 FAL Management Model Specification
   5.3 FAL Management Model Services
6 Application Process ASE
   6.1 Overview
   6.2 AP Class Specification
   6.3 Application Process ASE Service Specification
7 Application Relationship ASE
   7.1 Overview
   7.2 Application Relationship Endpoint Class
        Specifications
   7.3 Application Relationship ASE Service Specifications
8 Data Type ASE
   8.1 Overview
   8.2 Formal Definition of Data Type Objects
   8.3 FAL Defined Data Types
   8.4 Data Type ASE Service Specification
9 Variable ASE
   9.1 Overview
   9.2 Variable Model Class Specification
   9.3 Variable ASE Service Specification
10 Event ASE
   10.1 Overview
   10.2 Event Model Class Specification
   10.3 Event ASE Service Specification
11 Load Region ASE
   11.1 Overview
   11.2 Load Region Model Specification
   11.3 Load Region Service Specification
   11.4 Load Region State Machines
12 Function Invocation ASE
   12.1 Overview
   12.2 Function Invocation Model Class Specifications
   12.3 Function Invocation Model Service Specifications
   12.4 Function Invocation State Machine
Annex A - Model for Service Error Reporting
Annex B - Summary of FAL Classes
Annex C - Permitted FAL Services by AREP Role
Annex D - Queued User-triggered Uni-directional (QUU) AR
          Endpoint Formal Model
Annex E - Queued User-triggered Bi-directional Connection-Oriented
          (QUB-Co) AR Endpoint Formal Model
Annex F - Queued User-triggered Bi-directional
          Connectionless (QUB-CL) AR Endpoint Formal Model
Annex G - Queued User-triggered Bi-directional with Flow
          Control (QUB-FC) AR Endpoint Formal Model
Annex H - Queued User-triggered Bi-directional with
          Segmentation (QUB-Seg) AR Endpoint Formal Model
Annex I - Buffered User-triggered Bi-directional (BUB) AR
          Endpoint Formal Model
Annex J - Buffered Network-Scheduled Uni-directional (BNU)
          AR Endpoint Formal Model
Annex K - Buffered Network-Scheduled Bi-directional (BNB)
          AR Endpoint Formal Model
Annex L - Buffered Network-Scheduled and unscheduled Uni-directional
          (BNU-Mp) AR Endpoint Formal Model

Supplies user programs with a way to access the Fieldbus communication environment. This means the FAL can be viewed as a "window between corresponding application programs". This part defines the structure and services of the FAL - Fieldbus Application Layer. It is defined in conformance with OSI Basic Reference Model (ISO 7498) and the OSI Application Layer Structure (ISO 9545). Also defines interactions between remote applications in terms of an abstract model for defining application resources capable of being manipulated by users via FAL Services; The primitives associated with each FAL Service; The parameters associated with each primitive; and the interrelationship between and the valid sequences of the primitives for each service.