Sie sind auf Seite 1von 14

Materials System Specification

Materials System Specification

23-SAMSS-060

7 April 2012

Manufacturing Operation Management Integration Middleware

Document Responsibility: Process Control Standards Committee

Saudi Aramco DeskTop Standards

Table of Contents

Scope

  • 1 .............................................................

2

  • 2 Conflicts and Deviations

................................

2

References

  • 3 .....................................................

2

Definitions

  • 4 ......................................................

3

General

  • 5 ..........................................................

6

Functionality

  • 6 ...................................................

7

  • 7 Management/Administration

........................

10

  • 8 Reliability and Performance

.........................

11

  • 9 Indexing and Searching

...............................

12

Security

  • 10 ........................................................

12

  • 11 Inspection and Testing

.................................

12

Documentation

  • 12 .............................................

13

Previous Issue: 24 October 2009

Next Planned Update: 7 April 2017

Primary contact: Buhulaiga, Eyad Adam on 966-3-880-1658

Copyright©Saudi Aramco 2012. All rights reserved.

Page 1 of 14

Document Responsibility: Process Control Standards Committee

Issue Date:

7 April 2012

23-SAMSS-060

Next Planned Update: 7 April 2017

Manufacturing Operation Management Integration Middleware

  • 1 Scope

    • 1.1 This specification along with the requirements specified in ANSI/ISA 95 defines the minimum mandatory functional integration, architecture and testing requirements for the Manufacturing Operation Management Integration Middleware (MOM-IMMOM-IM).

    • 1.2 This specification applies to MOM-IM including the associated software and hardware components required to integrate MOM applications.

    • 1.3 Additional requirements might be included in Company's FSD, in which case both this document and the FSD requirements shall be met.

  • 2 Conflicts and Deviations

    • 2.1 Any conflicts between this specification and other applicable Saudi Aramco Materials Systems Specifications (SAMSSs), engineering standards (SAESs), standard drawings (SASDs), or industry standards, codes, and forms shall be resolved in writing by the Company or Buyer Representative through the Manager, Process & Controls Systems Department (Dhahran, Saudi Aramco).

    • 2.2 Direct all requests to deviate from this specification in writing to the Company or Buyer Representative, who shall follow internal Company Engineering Procedure SAEP-302 and forward such requests to the Manager, Process & Control Systems Department (Dhahran Saudi Aramco).

  • 3 References Software supplied to this specification shall comply with the latest edition of these referenced specifications.

    • 3.1 Saudi Aramco Documents Saudi Aramco Engineering Procedure

  • Instructions for Obtaining a Waiver of a Mandatory Saudi Aramco Engineering Requirement

    • 3.2 Industry Codes and Standards International Society for Measurement and Control

    ISA 95

    Enterprise-Control System Integration Standard for the Interfaces between an Enterprise's Business Systems and its Manufacturing Control Systems

    Document Responsibility: Process Control Standards Committee

    Issue Date:

    7 April 2012

    23-SAMSS-060

    Next Planned Update: 7 April 2017

    Manufacturing Operation Management Integration Middleware

    4

    Definitions

    This section contains definitions for acronyms, abbreviations, words, and terms as they are used in this document. For definitions not listed, the latest issue of the ISA 95,” International Society for Measurement and Control, shall apply.

    • 4.1 Acronyms and Abbreviations

    MOM-IM

    Manufacturing Operation Management Integration

    API

    Middleware Application Program Interface

    CoTS

    Commercial Off-the-Shelf

    DA

    Direct Access

    DBMS

    Database Management System

    DD

    Detail Design

    EDI

    Electronic Data Interchange

    ESB

    Enterprise Service Bus

    ESRI

    Environmental Systems Research Institute

    FSD

    Functional Specification Document

    FTP

    File Transfer Protocol

    GIS

    Geographic Information Systems

    HDA

    Historical Data Access

    HTTP

    Hyper Text Transfer Protocol

    IMAP

    Internet Message Access Protocol

    J2EE

    Java 2 Platform, Enterprise Edition

    JDBC

    Java Database Connectivity

    JMS

    Java Messaging Service

    JMX

    Java Management Extensions

    JSR168

    Java Specification Request for how portlets are created

    LDAP

    Lightweight Directory Access Protocol

    MOM

    Manufacturing Operation Management

    MQ

    Message Queue

    OLE

    Object Linking and Embedding

    OLEDB

    Object Linking and Embedding Database

    Document Responsibility: Process Control Standards Committee

    Issue Date:

    7 April 2012

    23-SAMSS-060

    Next Planned Update: 7 April 2017

    Manufacturing Operation Management Integration Middleware

    OPC

    OLE for Process Control

    RtPM

    Real-Time Performance Management

    SAML

    Security Assertion Markup Language

    SAT

    Site Acceptance Test

    SDK

    Software Development Kit

    SMS

    Short Message Service

    SMTP

    Simple Mail Transfer Protocol

    SNMP

    Simple Network Management Protocol

    SOA

    Service Oriented Architecture

    SOAP

    Simple Object Access Protocol

    SSL

    Secure Socket Layer

    VS.NET

    Visual Studio .NET

    WSRP

    Web Services for Remote Portlets

    WS-S

    Web Services Security

    XML

    Extensible Markup Language

    • 4.2 Words and Terms This section contains definitions for acronyms, abbreviations, words, and terms as they are used in this document. For definitions not listed, the latest issue of the ISA 95,” International Society of Automation, shall apply. Configurable: The capability to select and connect standard open application to the system; or the capability to change functionality or sizing of software functions by changing parameters without having to modify or regenerate software. Configuration: The physical installation or the selection of software options to satisfy system requirements. Dead Band: The range through which an input signal may be varied without initiating an action or observable change in output signal. Enterprise Service Bus: is a middleware subsystem that facilitates and manages communication, routing, web services support, payload metadata and mediation between business entities to allow components to be added, moved, swapped or deleted with minimal disruption to other components for easier and less-costly integration.

    Document Responsibility: Process Control Standards Committee

    Issue Date:

    7 April 2012

    23-SAMSS-060

    Next Planned Update: 7 April 2017

    Manufacturing Operation Management Integration Middleware

    Field Proven: A system shall be considered to be field proven when it has been installed, commissioned, and operational in a customer facility for a period of six months or longer (excluding beta test periods). It shall be possible for Saudi Aramco to verify the field proven status of any equipment.

    Heterogeneous Technology Environment: Using applications and system software from different vendors. The solution should support but not limited to (MS.Net, J2EE, File (text, binary), FTP, HTTP, JMS, email (POP/SMTP/IMAP).

    ISA 95: This standard defines activity models of Manufacturing Operations Management (MOM) that enable an enterprise system to control system integration. The activities defined in this standard are consistent with the ANSI/ISA 95.00.01-2000 Part 1 object models definitions. The modeled activities operate between business planning and logistics functions, defined as the Part 1 Level 4 functions, and the process control functions, defined as the Part 1 Level 2 functions. The scope of Part 3 encompasses: a model of the activities associated with manufacturing operations management; Level 3 functions; and an identification of some of the data exchanged between Level 3 activities.

    Message Transformation: messages en-route to match the requirements of the sender or of the recipient. In conjunction with the routing and broadcast/multicast facilities, one application can send a message in its own native format, and two or more other applications may each receive a copy of the message in their own native format.

    Manufacturing Operation Management (MOM): is a methodology for viewing an end-to-end manufacturing process with a view to optimize efficiency.

    Manufacturing Operation Management Integration Middleware (MOM- IM): a set of components, adaptors/interfaces and communication protocols that provide integrated services with one framework.

    Operational Data: The statistical data such as alarm limits, tuning parameters, and clamping values, as opposed to process data such as input values, output values, and set-points.

    Point: A process variable derived from an input or calculated in a process calculation.

    Reliability: The capability of a system or component to perform its intended function for a specified period of time.

    Service Oriented Architecture: a perspective of software architecture that defines the use of loosely coupled software services to support the requirements of the business processes and software users. In an SOA environment, resources

    Document Responsibility: Process Control Standards Committee

    Issue Date:

    7 April 2012

    23-SAMSS-060

    Next Planned Update: 7 April 2017

    Manufacturing Operation Management Integration Middleware

    on a network are made available as independent services that can be accessed without knowledge of their underlying platform implementation.

    Standard: the word standard is used to define Commercial Off-the-Shelf (CoTS) hardware or software without the need of special configuration or customization.

    Tag: A collection of attributes that specify either a control loop or a process variable, or a measured input, or a calculated value, or some combination of these, and all associated control and output algorithms. Each tag is unique.

    Tag ID: The unique alphanumeric code assigned to inputs, outputs, equipment items, and control blocks. The tag ID might include the plant area identifier.

    Workstation: A set of electronic equipment including a minimum of one monitor, keyboard(s) and associated pointing device(s).

    5

    General

    • 5.1 Use of Standard Products

      • 5.1.1 MOM-IM shall be installed on standard vendor hardware using standard vendor software and be configured to meet the stated requirements.

      • 5.1.2 A vendor's standard software shall not be customized to meet any of Saudi Aramco's requirements.

      • 5.1.3 MOM-IM software shall be designed in a manner that requires no modification to the operating system software.

      • 5.1.4 MOM-IM software shall be designed in accordance with ESB and SOA integration standards.

      • 5.1.5 MOM-IM functional integration architecture shall be designed in accordance with ISA 95 standards.

      • 5.1.6 MOM-IM must be able to support XML data types based on ISA 95 and transform to and from ISA 95 XML messages. It should also support EDI (Electronic Data Interchange), B2MML (XML implementation of the ISA 95 standard) and BatchML (XML implementation of the ISA 88 standard).

      • 5.1.7 MOM-IM shall use standard open interfaces/adaptors in order to integrate applications.

    Document Responsibility: Process Control Standards Committee

    Issue Date:

    7 April 2012

    23-SAMSS-060

    Next Planned Update: 7 April 2017

    Manufacturing Operation Management Integration Middleware

    • 5.2 Revision Level

      • 5.2.1 All vendor proprietary software, inclusive of application software, shall be the most recent, commercially released, software revision level that is applicable to MOM-IM requirements level at the completion of the purchase order as defined in the contract or purchase order.

      • 5.2.2 All commercial off-the-shelf (CoTS) Software components provided by the vendor as part of MOM-IM shall be the latest field proven models commercially available which have been tested and approved for compatibility by the vendor at the completion of the Purchase Order as defined in the contract or purchase order.

  • 5.3 Software Revision

    • 5.3.1 MOM-IM shall allow for online upgrading of integrated application software on all redundant modules without requiring a shutdown of any connected applications and without the loss of access to any function.

    • 5.3.2 MOM-IM shall not require modifications in order to be able to run under new releases of any MOM-IM component.

  • 5.4 System Support

    • 5.4.1 Vendor shall guarantee support of all customized/commercial off-the- shelf (COTS) software components and any proprietary adaptor/interface for a period of 5 years from the date of the Purchase Order. Support shall include software upgrades and technical support.

    • 5.4.2 Withdrawal of product support for Vendor products shall be notified in writing twelve months in advance to the Manager, Process & Control Systems Department (Dhahran, Saudi Aramco).

  • 6

    Functionality

    • 6.1 Functional and Data Integration

      • 6.1.1 Saudi Aramco will provide the vendor with FSD that details the high level integration architecture diagram and illustrates the data flow between the applications.

      • 6.1.2 The vendor shall provide integration architecture that matches the functional integration diagrams provided in the FSD that illustrates the integration of the applications in terms of strategy, integration platform, throughput, speed, adapters, flows, messages, transformations, transactions and protocols.

    Document Responsibility: Process Control Standards Committee

    Issue Date:

    7 April 2012

    23-SAMSS-060

    Next Planned Update: 7 April 2017

    Manufacturing Operation Management Integration Middleware

    • 6.1.3 MOM-IM shall support different time stamped data types that include but not limited to (Real, Text, Tag, Tag IDs, Tag attributes, integer, float, double, strings, long, picture, byte, Boolean).

    • 6.1.4 MOM-IM shall be able to retrieve datasets & operational data that are based on date and time.

    • 6.1.5 MOM-IM shall be able to retrieve multiple variables that require data from more than one data source through multiple request and single request.

    • 6.1.6 MOM-IM shall have its own API/SDK/Web-Services to develop additional functionalities/interfaces.

    • 6.2 System and Platform

      • 6.2.1 MOM-IM shall allow Client to run on both Windows and Linux based workstations). Commentary Note:

    The requirements of Linux above do not apply to the downstream applications. It is applicable only for Exploration applications where it might be run from a Linux client.

    • 6.2.2 MOM-IM shall support heterogeneous technology environment that includes but not limited to (MS.NET(Windows Communication Foundation (WCF), Windows Workflow Foundation(WWF) & Windows Presentation Foundation (WPF)), J2EE, File (text, binary), FTP, HTTP, HTTPS, JMS, email (POP/SMTP/IMAP).

    • 6.2.3 MOM-IM shall support distributed architecture (all MOM-IM components can be installed on different machines or all components on one machine).

    • 6.2.4 MOM-IM shall be able to connect any number of applications across domains securely.

    • 6.3 Messaging

      • 6.3.1 MOM-IM shall support message brokering that includes:

        • a) Support for multiple messaging models including synchronous, asynchronous.

        • b) Publish and subscribe.

        • c) Support for multiple message formats including SOAP, XML, structured non-XML data, raw data, text, and email with

    Document Responsibility: Process Control Standards Committee

    Issue Date:

    7 April 2012

    23-SAMSS-060

    Next Planned Update: 7 April 2017

    Manufacturing Operation Management Integration Middleware

    attachments.

    • d) Support multiple messaging protocols that include but not limited to (JMS, MQ).

    • 6.3.2 MOM-IM shall support message transformation, event handling and use message delivery assurance and Quality of Service techniques.

    • 6.3.3 MOM-IM shall be able to provide disaster recovery and recovery of messages in the event of loss or failure of servers and loss of messages.

    • 6.3.4 MOM-IM shall be able to prioritize the message(s) based on their criticality/configurable criteria.

    • 6.3.5 MOM-IM shall be able to support both stateless and statefull transaction messages.

    • 6.3.6 MOM-IM shall have messages caching capabilities.

    • 6.3.7 MOM-IM shall have its own Graphical Configuration Environment.

    • 6.3.8 MOM-IM shall be able to transform to and from XML standard formats.

    • 6.4 Applications Interfaces MOM-IM shall provide bi-directional interfaces and support the following:

      • 6.4.1 Adapters that are not limited to the following applications (OSIsoft RtPM (PI), ODBC, SAP, Documentum).

      • 6.4.2 Interface seamlessly to Web Dashboard/Portals, that include but not limited to, (Indx XHQ, Microsoft SharePoint, SAP Enterprise Portal, OSI RtWebParts).

      • 6.4.3 Collect Messages, information and Portlets from external Web Portals using standard protocols that include, but not limited to, WSRP & JSR168.

      • 6.4.4 Integrate GIS applications such as ESRI GIS to MOM-IM.

      • 6.4.5 Integrate third party relational database management systems to MOM- IM.

  • 6.5 Standard Interfaces MOM-IM shall provide bi-directional interfaces that can support the functionalities in the following:

  • Document Responsibility: Process Control Standards Committee

    Issue Date:

    7 April 2012

    23-SAMSS-060

    Next Planned Update: 7 April 2017

    Manufacturing Operation Management Integration Middleware

    • 6.5.1 Integrate OPC compliant applications using various OPC specifications and standards that include but not limited to, OPC UA, OPC DA, and HDA client/server.

    • 6.5.2 Integrate seamlessly OLEDB/JDBC applications to MOM-IM.

    • 6.5.3 Integrate seamlessly Web Services to MOM-IM.

    • 6.5.4 Integrate seamlessly HTTP, J2EE or EDI applications to MOM-IM.

    • 6.6 Reporting

      • 6.6.1 MOM-IM shall support standard report builders that includes but not limited to Crystal Reports and SQL Server Reporting Services (SSRS). The MOM-IM shall provide wizards that will help in building SQL Marts, SQL Set and SQL Cubes using the integrated data sources.

      • 6.6.2 The Report Builder shall enable the users to print the reports and export them to spreadsheet, word processor, PDF in both Native and Raw Data Format.

      • 6.6.3 MOM-IM shall have API and SDK to allow the users to create their own report using standard tools that includes but not limited to (VS.NET, JAVA, etc.).

      • 6.6.4 The vendor shall provide operation instructions and operating log.

      • 6.6.5 MOM-IM shall support the mapping functionalities that support the displaying of GIS Web Services & Maps. These functionalities shall include, but not limited to, displaying of data, graphic, Report, and zooming.

    7

    Management/Administration

    • 7.1 MOM-IM shall be able to handle/synchronize naming conventions and OSI/RtPM modular Database structure when exchanging messages among other integrated applications.

    • 7.2 MOM-IM shall have mechanism for reusing both aggregate steps, electronic documents and encapsulating changes in platform, processes and growth.

    • 7.3 MOM-IM shall have alarming/alert features which include, but not limited to, e-mails and SMS through standard interfaces that include, but not limited to, SNMP and JMX.

    Document Responsibility: Process Control Standards Committee

    Issue Date:

    7 April 2012

    23-SAMSS-060

    Next Planned Update: 7 April 2017

    Manufacturing Operation Management Integration Middleware

    • 7.4 MOM-IM shall be able to perform data filtering to pre-process the raw measurements and operational data that include, but not limited to, Out of Range, meaningless data or Dead bands.

    • 7.5 MOM-IM shall use business rules for validating incoming or outgoing messages/data, particularly for co-occurrence constraints.

    • 7.6 MOM-IM shall be able to handle centralized administration and security framework to manage processes, adapters, machines and other MOM-IM components.

    • 7.7 MOM-IM shall require users to own basic computer knowledge (i.e., Browsing the internet and working with Office applications) and not advanced technical skills.

    • 7.8 The Administration shall be able to clone MOM-IM or part of it for reusability purposes.

    • 7.9 MOM-IM shall not require the replication of data.

      • 7.10 MOM-IM shall not store data independently from their native data sources.

      • 7.11 MOM-IM shall have the capability to do advance calculation using internal tools at the integration layer and/or external programming tools.

      • 7.12 MOM-IM shall support point-to-point, one-to-many and many-to-many routing scenarios, enabling both request-response and publish-subscribe models.

      • 7.13 MOM-IM shall support/enable event-driven real-time flow of data among the distributed integrated applications.

      • 7.14 MOM-IM shall have backup and recovery features.

    • 8 Reliability and Performance

      • 8.1 MOM-IM shall be scaleable, provide load balancing and fault tolerance.

      • 8.2 MOM-IM shall support capabilities for multi-threading of the operating system and multiple CPU environments.

      • 8.3 MOM-IM shall provide load balancing and fault tolerance in the adapters' level if required by the project or stated in the FSD.

      • 8.4 MOM-IM shall be able to handle as a minimum 500,000 messages/second.

    Document Responsibility: Process Control Standards Committee

    Issue Date:

    7 April 2012

    23-SAMSS-060

    Next Planned Update: 7 April 2017

    Manufacturing Operation Management Integration Middleware

    • 9 Indexing and Searching

      • 9.1 MOM-IM shall support taxonomy to allow Indexing.

      • 9.2 MOM-IM shall support the capability to search other search engines (i.e., Autonomy).

      • 9.3 MOM-IM shall support the capability to pass searching parameters to other search engines.

      • 9.4 MOM-IM shall support the capability to allow other search engines to search data within their application.

    • 10 Security

      • 10.1 MOM-IM shall have capability to integrate with Windows Active Directory.

      • 10.2 MOM-IM shall have capability to be integrated with other security rules of other products such as Oracle DBMS.

      • 10.3 MOM-IM shall be compatible with anti-virus software.

      • 10.4 MOM-IM shall have it own Security rules, Security administration/management, central management of site's contents and Web contents management.

      • 10.5 MOM-IM shall use standard encryption methods.

      • 10.6 MOM-IM shall be able to track users through the ability to turn on audit trail without affecting the web services contract and the ability to build into the contract and schema for logging and tracing.

      • 10.7 MOM-IM shall use fixed assignable and standard TCP ports. The product shall allow the TCP ports to be configured/changed based on Saudi Aramco Security Specifications which is going to be provided to the vendor during the purchase requisition of the project.

      • 10.8 MOM-IM shall support security standards that include but are not limited to (WS-S, SSL, SAML 1.0+ and Identity Propagation).

  • 11 Inspection and Testing

    • 11.1 Standard Software Standard software shall be tested. Testing shall be in accordance with the standard test procedures for software diagnostics.

  • Document Responsibility: Process Control Standards Committee

    Issue Date:

    7 April 2012

    23-SAMSS-060

    Next Planned Update: 7 April 2017

    Manufacturing Operation Management Integration Middleware

    • 11.2 Integrated Systems

      • 11.2.1 MOM-IM that are staged at a vendor's facilities and/or Saudi Aramco site shall be tested according to Site Acceptance Test (Pre-SAT) procedures prior to the SAT. Vendor should send the (Pre-SAT) test report to Saudi Aramco before starting the SAT at Saudi Aramco Site.

      • 11.2.2 MOM-IM servers that are staged Saudi Aramco site shall be tested according to Site Acceptance Test (SAT) procedures.

      • 11.2.3 SAT criteria shall be developed by the vendor and approved by Saudi Aramco.

    12

    Documentation

    • 12.1 The following documentation shall be supplied by the vendor as part of the project deliverables:

      • 12.1.1 601 NMRS

        • 601.1 System Scope, Development & Execution Plan

        • 601.2 System Design Proposal & Integration Specifications Document

        • 601.3 Integration Test Plan

        • 601.4 Site Acceptance Test Plan

        • 601.5 Bill of Materials

        • 601.6 Integration platform report based on the criteria of integration content (throughput, speed, messaging functionality, and transactions, etc.)

  • 12.1.2 602 NMRS

    • 602.1 System Detailed Design & Integration Specifications Document as applicable to the system that includes but not limited to:

      • 602.1.1 Message queuing functions

      • 602.1.2 One-to-one, one-to-many or many-to-many integration

      • 602.1.3 Data integration, application integration, etc.

  • Document Responsibility: Process Control Standards Committee

    Issue Date:

    7 April 2012

    23-SAMSS-060

    Next Planned Update: 7 April 2017

    Manufacturing Operation Management Integration Middleware

    • 602.2 System Performance Specifications that includes but not limited to:

      • 602.2.1 Capabilities to support multiple multi-threading

      • 602.2.2 Performance management typical cases

      • 602.2.3 Maximum number of transactions to be transmitted

      • 602.2.4 Performance figures of throughput

    • 12.1.3 603 NMRS

      • 603.1 Installation Instructions

      • 603.2 Operating Instructions (User, Advanced user & Administrator)

      • 603.3 Maintenance Manuals

      • 603.4 Certified Test Reports, and Certificates

    • 12.2 All documentation shall be in English using the US dictionary.

    • 12.3 Word processor or text files of all application software documentation shall be provided on removable electronic media.

    • 12.4 Three (3) backup copies on electronic media shall be provided of all system software, application software, and system configuration. The format and media of these copies shall be such that they can be loaded directly into the system without additional translation or data manipulation.

    7 April 2012

    Revision Summary

    Major revision.