IT in general

The Quotation process is used by a customer to obtain an offer from a potential supplier for the delivery of products or services. During the Quotation process either party may reject the conditions proposed. The Quotation is then not accepted and neither party has residual obligations. For reasons of compatibility with existing practices the Customer may in his rejection include suggestions on conditions that would be acceptable for him. Again, the use of this feature is not preferred.

This document describes the extent and limits of the business process within the information chain.
The class diagram of export certification has been developed to specify the cross border exchange of information to enable business information entities to be re-used. It includes business information entities specifically required by government regulators to describe products being traded and aid the transfer of information from an export certificate system to an import clearance system. Document : BRS – E-cert Page : 5 of 29 This document describes the electronic exchange of export certificate data between government regulators to facilitate cross border entry of agricultural products.

This section describes the extent and limits of the business processes within the supply chain being described in this document. Each industry may specify, based on the BRS of the cross industry catalogue processes, its industry specific use of the catalogue message and the business processes. It also allows for industry specific functionality on details to describe a specific product. Name/Value pairs in the catalogue documents allows the Catalogue Provider to add attributes to further specify their products in the existing structure. If further elaboration is needed an industryspecific ontology can be made. Industry specific ontology is outside the scope of this BRS

Specification that describes the business process and requirements for the invoicing process. The invoicing process is used to exchange the invoice between the supplier and the for the supply of goods or services ordered, delivered, received, consumed, etc. This document describes the variants of invoicing in use in trade and industry. It considers the legal statements and, to a certain extent, the corrections of a previously sent invoice, by using credit notes or debit notes.

ISO/IEC TR 30148:2019 describes
– the structure of wireless gas meter networks, and
– the application protocol of wireless gas meter networks.

The definition of a CMDB in the context of this specification is based on the definition described in the IT Infrastructure Library (ITIL): a database that tracks and records configuration items associated with the IT infrastructure and the relationships between them. Strictly speaking, the ITIL CMDB contains a record of the expected configuration of the IT environment, as authorized and controlled through the change management and configuration management processes. The federated CMDB in this specification extends this base definition to federate any management information that complies with the specification’s patterns, schema, and interfaces, such as the discovered actual state in addition to the expected state. Typically, an administrator selects the data to be included in a CMDB by configuring the tool that implements the CMDB.

This document provides a standardized IoT Reference Architecture using a common vocabulary, reusable designs and industry best practices. It uses a top down approach, beginning with collecting the most important characteristics of IoT, abstracting those into a generic IoT Conceptual Model, deriving a high level system based reference with subsequent dissection of that model into the four architecture views (functional view, system view, networking view and usage view) from different perspectives.

AFI WG is the leading Standardization Group on Autonomic Management & Control (AMC) of Networks and Services, including Autonomic Networking, Cognitive Networking and Self-Management. Its mandate is to carry out the various Tasks and Activities described below:

• Develop use cases and requirements for automated & autonomic (self-) management of networks and services;
• Develop test frameworks and test specifications for autonomic network architectures (Self-Adaptive Networks);
• Draft test specifications for Scenarios, Use Cases and Requirements for automated & autonomic (self-) management of networks and services;
• Drive a 5G PoC Program/Project on GANA Autonomics in 5G Network Slices Creation, Autonomic & Cognitive Management & E2E Orchestration; with Closed-Loop (Autonomic) Service Assurance of IoT 5G Slices;

Maintenance and evolution of existing ETSI standards on network and service management, including NGN management (ETSI 188 series: https://www.etsi.org/deliver/etsi_ts/188000_188099/ ); and Maintenance of existing ETSI Standards linked to AFI activities: 

• ETSI TS 103 194 on Scenarios, Use Cases and Requirements for Autonomic/Self-Managing Future Internet;
• ETSI TS 103 195-1,
• ETSI TS 103 195-2,
• ETSI TS 103 195-3

GANA Model and its instantiations onto various types of network architectures and their associated management and control architectures:

• ETSI TR 103 473 on GANA autonomics in BBF Architectures;
• ETSI TR 103 404 on GANA autonomics in 3GPP Backhaul & Core Network Architectures;
• ETSI TR 103 495 on GANA autonomics in Wireless Ad-hoc/Mesh Network Architectures;

ETSI White Paper no. 16: The Generic Autonomic Networking Architecture Reference Model for Autonomic Networking, Cognitive Networking and Self-Management of Networks and Services: http://www.etsi.org/images/files/ETSIWhitePapers/etsi_wp16_gana_Ed1_20161011.pdf