SIST-TP CLC/R217-015:2004
(Main)Pinnacles Component Information Standard 1.2 - PCIS Tutorial
Pinnacles Component Information Standard 1.2 - PCIS Tutorial
D116/196: TC 217 disbanded * D122/065: Withdrawn
Informacijski standard o komponentah Pinnacles 1.2 – PCIS predavanje
General Information
Standards Content (Sample)
SLOVENSKI SIST-TP CLC/R217-015:2004
STANDARD
september 2004
Informacijski standard o komponentah Pinnacles 1.2 – PCIS predavanje
Pinnacles Component Information Standard 1.2 - PCIS Tutorial
ICS 35.240.50 Referenčna številka
SIS
...
This May Also Interest You
This technical report presents an overview and guidance for IEC 61158, IEC 61784-1, IEC 61784-2 and IEC 61800-7 with respect to a real-time serial interface between the control unit and its associated devices, which is utilized to transmit periodic and non periodic data. This interface is intended to apply to industrial machines, such as machine tools, with multiple devices connected via this interface. This interface supports different operation modes.
- Technical report13 pagesEnglish languagesale 10% offe-Library read for×1 day
IEC 62351-3:2023 specifies how to provide confidentiality, integrity protection, and message level authentication for protocols that make use of TCP/IP as a message transport layer and utilize Transport Layer Security when cyber-security is required. This may relate to SCADA and telecontrol protocols, but also to additional protocols if they meet the requirements in this document.
IEC 62351-3 specifies how to secure TCP/IP-based protocols through constraints on the specification of the messages, procedures, and algorithms of Transport Layer Security (TLS) (TLSv1.2 defined in RFC 5246, TLSv1.3 defined in RFC 8446). In the specific clauses, there will be subclauses to note the differences and commonalities in the application depending on the target TLS version. The use and specification of intervening external security devices (e.g., "bump-in-the-wire") are considered out-of-scope.
In contrast to previous editions of this document, this edition is self-contained in terms of completely defining a profile of TLS. Hence, it can be applied directly, without the need to specify further TLS parameters, except the port number, over which the communication will be performed. Therefore, this part can be directly utilized from a referencing standard and can be combined with further security measures on other layers. Providing the profiling of TLS without the need for further specifying TLS parameters allows declaring conformity to the described functionality without the need to involve further IEC 62351 documents.
This document is intended to be referenced as a normative part of other IEC standards that have the need for providing security for their TCP/IP-based protocol exchanges under similar boundary conditions. However, it is up to the individual protocol security initiatives to decide if this document is to be referenced.
The document also defines security events for specific conditions, which support error handling, security audit trails, intrusion detection, and conformance testing. Any action of an organization in response to events to an error condition described in this document are beyond the scope of this document and are expected to be defined by the organization’s security policy.
This document reflects the security requirements of the IEC power systems management protocols. Should other standards bring forward new requirements, this document may need to be revised.
This second edition cancels and replaces the first edition published in 2014, Amendment 1:2018 and Amendment 2:2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) Inclusion of the TLSv1.2 related parameter required in IEC 62351-3 Ed.1.2 to be specified by the referencing standard. This comprises the following parameter:
• Mandatory TLSv1.2 cipher suites to be supported.
• Specification of session resumption parameters.
• Specification of session renegotiation parameters.
• Revocation handling using CRL and OCSP.
• Handling of security events.
b) Inclusion of a TLSv1.3 profile to be applicable for the power system domain in a similar way as for TLSv1.2 session.
- Standard52 pagesEnglish languagesale 10% offe-Library read for×1 day
This part of IEC 61987 provides
• a characterization for the integration of infrastructure devices in the Common Data
Dictionary (CDD);
• generic structures in conformance with IEC 61987-10 for Operating Lists of Properties
(OLOPs) and Device Lists of Properties (DLOPs) of infrastructure devices.
The generic structures for the OLOP and DLOP contain the most important blocks for
infrastructure devices. Blocks pertaining to a specific equipment type will be described in the
corresponding part of the IEC 61987 series. Similarly, equipment properties are not part of this
part of IEC 61987. For instance, the OLOP and DLOP for I/O-modules are to be found in
IEC 61987-32.
- Standard27 pagesEnglish languagesale 10% offe-Library read for×1 day
- Draft24 pagesEnglish languagesale 10% offe-Library read for×1 day
This document specifies basic requirements for the installation of media for communication networks within and between the automation islands, of industrial sites. This standard covers balanced and optical fibre cabling. It also covers the cabling infrastructure for wireless media, but not the wireless media itself. Additional media are covered in the IEC 61784-5 series.
This document is a companion standard to the communication networks of the industrial automation islands and especially to the communication networks specified in the IEC 61158 series and the IEC 61784 series.
In addition, this document covers the connection between the generic telecommunications cabling specified in ISO/IEC 11801-3 and the specific communication cabling of an automation island, where an automation outlet (AO) replaces the telecommunication outlet (TO) of ISO/IEC 11801-3.
NOTE If the interface used at the AO does not conform to that specified for the TO of ISO/IEC 11801-3, the cabling no longer conforms to ISO/IEC 11801-3 although certain features, including performance, of generic cabling may be retained.
This document provides guidelines that cope with the critical aspects of the industrial automation area (safety, security and environmental aspects such as mechanical, liquid, particulate, climatic, chemicals and electromagnetic interference).
This document does not recognise implementations of power distribution with or through Ethernet balanced cabling systems that are not specified in IEEE 802.3af and in IEEE 802.3at.
This document deals with the roles of planner, installer, verifier, and acceptance test personnel, administration and maintenance personnel and specifies the relevant responsibilities and/or gives guidance.
- Amendment4 pagesEnglish languagesale 10% offe-Library read for×1 day
- Draft3 pagesEnglish languagesale 10% offe-Library read for×1 day
This part of IEC 62351 defines the application authentication mechanism (A-profile) specifying messages, procedures and algorithms for securing the operation of all protocols based on or derived from IEC 60870-5: Telecontrol Equipment and Systems - Transmission Protocols.
This Standard applies to at least those protocols listed in Table 1.
[Table 1]
The initial audience for this International Standard is intended to be the members of the working groups developing the protocols listed in Table 1.
For the measures described in this standard to take effect, they must be accepted and referenced by the specifications for the protocols themselves. This document is written to enable that process. The working groups in charge of take this standard to the specific protocols listed in Table 1 may choose not to do so.
The subsequent audience for this specification is intended to be the developers of products that implement these protocols.
Portions of this standard may also be of use to managers and executives in order to understand the purpose and requirements of the work.
This document is organized working from the general to the specific, as follows:
- Clauses 2 through 4 provide background terms, definitions, and references.
- Clause 5 describes the problems this specification is intended to address.
- Clause 6 describes the mechanism generically without reference to a specific protocol.
- Clauses 7 and 8 describe the mechanism more precisely and are the primary normative part of this specification.
- Clause 9 define the interoperability requirements for this authentication mechanism.
- Clause 10 describes the requirements for other standards referencing this specification
Unless specifically labelled as informative or optional, all clauses of this specification are normative.
- Standard126 pagesEnglish languagesale 10% offe-Library read for×1 day
The IEC 62714 series specifies an engineering data exchange format for use in industrial automation systems.
This part of IEC 62714 specifies normative as well as informative AML libraries for the modelling of engineering information for the exchange between engineering tools in the plant automation area by means of AML. Moreover, it presents additional user defined libraries as an example. Its provisions apply to the export/import applications of related tools.
This part of IEC 62714 specifies AML role class libraries and AML attribute type libraries. Role classes provide semantics to AML objects, attribute types provide semantics to AML attributes. The association of role classes to AML objects or attribute types to AML attributes represent the possibility to add (also external) semantic to it. By associating a role class to an AML object or an attribute type to an AML attribute,it gets a semantic.This part of IEC 62714 does not define details of the data exchange procedure or implementation requirements for the import/export tools.
- Standard61 pagesEnglish languagesale 10% offe-Library read for×1 day
- Draft60 pagesEnglish languagesale 10% offe-Library read for×1 day
Communication Profile Family 9 (commonly known as HART®1) defines communication profiles based on IEC 61158-5-20 and IEC 61158-6-20. The basic profile CP 9/1 is defined in IEC 61784-1.
This part of IEC 62453 provides information for integrating the HART® technology into the FDT standard (IEC 62453-2).
This part of the IEC 62453 specifies communication and other services.
This standard neither contains the FDT specification nor modifies it.
- Standard51 pagesEnglish languagesale 10% offe-Library read for×1 day
- Draft49 pagesEnglish languagesale 10% offe-Library read for×1 day
This part of IEC 62453 explains the common principles of the field device tool concept. These
principles can be used in various industrial applications such as engineering systems,
configuration programs and monitoring and diagnostic applications.
This document specifies the general objects, general object behavior and general object
interactions that provide the base of FDT.
- Standard168 pagesEnglish languagesale 10% offe-Library read for×1 day
This part of IEC 61131 specifies a single-drop digital communication interface technology for small sensors and actuators SDCI (commonly known as IO-LinkTM2), which extends the traditional digital input and digital output interfaces as defined in IEC 61131-2 towards a point-to-point communication link. This technology enables the transfer of parameters to Devices and the delivery of diagnostic information from the Devices to the automation system.
This technology is mainly intended for use with simple sensors and actuators in factory automation, which include small and cost-effective microcontrollers.
This part specifies the SDCI communication services and protocol (physical layer, data link layer and application layer in accordance with the ISO/OSI reference model) for both SDCI Masters and Devices.
This part also includes EMC test requirements.
This part does not cover communication interfaces or systems incorporating multiple point or multiple drop linkages, or integration of SDCI into higher level systems such as fieldbuses.
- Standard333 pagesEnglish languagesale 10% offe-Library read for×1 day
- Draft298 pagesEnglish languagesale 10% offe-Library read for×1 day
Engineering processes of technical systems and their embedded automation systems have to be executed with increasing efficiency and quality. Especially since the project duration tends to increase as the complexity of the engineered system increases. To solve this problem, the engineering process is more often being executed by exploiting software based engineering tools exchanging engineering information and artefacts along the engineering process related tool chain.
Communication systems establish an important part of modern technical systems and, especially, of automation systems embedded within them. Following the increasing decentralisation of automation systems and the application of fieldbus and Ethernet technology connecting automation devices and further interacting entities have to fulfil special requirements on communication quality, safety and security. Thus, within the engineering process of modern technical systems, engineering information and artefacts relating to communication systems also have to be exchanged along the engineering process tool chain.
In each phase of the engineering process of technical systems, communication system related information can be created which can be consumed in later engineering phases. A typical application case is the creation of configuration information for communication components of automation devices including communication addresses and communication package structuring within controller programming devices during the control programming phase and its use in a device configuration tool. Another typical application case is the transmission of communication device configurations to virtual commissioning tools, to documentation tools, or to diagnosis tools.
At present, the consistent and lossless transfer of communication system engineering information along the complete engineering chain of technical systems is unsolved. While user organisations and companies have provided data exchange formats for parts of the relevant information like FDCML, EDDL, and GSD the above named application cases cannot be covered by a data exchange format. Notably the networking related information describing communication relations and their properties and qualities cannot be modelled by a data exchange format.
- Standard58 pagesEnglish languagesale 10% offe-Library read for×1 day
- Draft52 pagesEnglish languagesale 10% offe-Library read for×1 day
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.