35.240.69 – IT applications in postal services – PDF Standards Store

DIN CEN/TS 15873:2009 Edition

Tue, 05 Nov 2024 15:20:58 +0000

This document defines a file format for the generation of postal address directories. It is designed to hold all information necessary to support address reading software including data required for forwarding applications. In typical postal automation systems these fileswill be processed by directory generation software which creates application specific loadable data. This data – usually referred to as operational directory – is heavily compressed and contains access tables tailored for the specific reading software. Not in the scope of this document are topics external to file like compression, checksums, the interface for transmission to the supplier, modification permissions, error handling on inconsistent data and undo in updates.

DIN CEN/TS 15448, DIN SPEC 16583:2015 Edition

Tue, 05 Nov 2024 15:20:50 +0000

Postal services - Open standard Interface between image controller and enrichment devices (OCRs, video coding systems, voting systems)

Published By	Publication Date	Number of Pages
DIN	2015-03	249

DIN CEN/TS 14014, DIN SPEC 16584:2015 Edition

Tue, 05 Nov 2024 15:20:44 +0000

The purpose of this Technical Specification is to define the syntax rules for a datastream for the submission of printing data to a Hybrid Mail operator or betweenHybrid Mail operators. The Technical Specification defines a XML Schema Definition(XSD) describing the data stream. The description is based upon the XML(eXtended Mark-up Language) definition of rules and semantics for defining anXSD. The purpose of this is to offer a generalised syntax description that canprovide seamless integration with a number of existing applications generating datathat is liable to be forwarded to or from a Hybrid Mail operator. The use of an XSDwill ensure that the documents confirm to the standard defined and that the outputhas the correct syntax. Software manufacturers can use an XSD to programapplications that will produce "correct" outputs. This Technical Specification definesthe syntax for creating a data stream that will eventually be converted into adeliverable. The overall object (a batch) can be divided into one or more objects thatagain can be divided into objects. The hierarchy includes bundles that contains acommon part and letters. Each object has a number of characteristics attached to it.This diagram shows the structure of a HML (Hybrid Mail Language) document: eachletter is self-contained (contains all the necessary information to be delivered on acertain destination).

AS ISO/IEC 38505.1:2018

Tue, 05 Nov 2024 13:17:59 +0000

Information technology - Governance of IT - Governance of data - Application of AS ISO/IEC 38500 to the governance of data

Published By	Publication Date	Number of Pages
AS	2018-05-03	31

AS ISO/IEC 27004:2018

Tue, 05 Nov 2024 13:17:51 +0000

Adopts ISO/IEC 27004:2016 to provide guidelines intended to assist organizations in evaluating
the information security performance and the effectiveness of an information security
management system in order to fulfil the requirements of ISO/IEC 27001:2013, 9.1.

Scope

This document provides guidelines intended to assist organizations in evaluating the information security performance and the effectiveness of an information security management system in order to fulfil the requirements of ISO/IEC 27001:2013, 9.1. It establishes:
a) the monitoring and measurement of information security performance;
b) the monitoring and measurement of the effectiveness of an information security management system (ISMS) including its processes and controls;
c) the analysis and evaluation of the results of monitoring and measurement.
This document is applicable to all types and sizes of organizations.

UNE-CEN/TS 17457:2020:2021 Edition

Tue, 05 Nov 2024 08:19:13 +0000

Postal services - Digital, optional online connected, opening and closing systems for parcel receptacles for home use with free access for the delivery and collection operators and consumers

Published By	Publication Date	Number of Pages
AENOR	2021-04-01	24

BSI PD CEN/TS 17073:2020

Sun, 20 Oct 2024 01:15:58 +0000

This document will specify the interface between the e-merchant (any commercial customer sending parcels) and the first logistic operator, including both public and private carriers. For the application of this document, a cross border parcel is a parcel crossing a border into and within Europe.

The interface is composed of two items:

the physical label attached on the parcel: contents, sizes, minimum requirements to guarantee the quality and efficiency of the logistic process (sorting, delivery).
the electronic exchanges between the sender and the logistic operator with the description of the data to be provided, the format of the exchanges.

While designated operators of UPU have drawn up business requirements using proprietary standards and related data components, online merchants have developed open, not-for-profit standards for final delivery which are integrated into their existing supply chain management environment.

NOTE 1

The data element enables the growth of integrated, data-driven systems which support highly efficient and customer-driven cross-border ecommerce. This reflects the current trend to B-to-B-to-C delivery solutions in the European and international cross border e-commerce markets. Delivery from original source to final consumer can be split over more than one service provider.

NOTE 2

C-to-B-to-B-to-C solutions will be an extension, in particular when returns are specified. The “first C” would indicate that consumers wishing to return items, or induct items themselves, will be able to print labels following the fundamentals specified in this standard.

E-merchants exchange data with logistic operators (i.e. the postal operators, but not limited to those designated to fulfil the rights and obligations of UPU member countries) to help, simplify and enable the consequential logistic and transactional tasks. The establishment of common definitions and electronic formats safeguards the reliability and decreases the overall costs by avoiding software development costs, multiple printing equipment, over-labelling during the process, and the manual sorting.

PDF Catalog

PDF Pages	PDF Title
2	undefined
7	1 Scope 2 Normative references
8	3 Terms and definitions 4 The physical parcel label 4.1 Contents in the label
10	4.2 Label dimensions 4.3 General display rules 4.3.1 Label text font
11	4.3.2 Colours 4.3.3 Label zones
12	4.3.4 Zone contents
13	4.4 Header zone 4.4.1 General 4.4.2 Header dimensions – zone A
14	4.5 Sender zone 4.5.1 General 4.5.2 Sender zone dimensions – zone B 4.5.3 FROM indicator
15	4.5.4 Address of sender – zone B0 and B1 4.5.5 Sender telephone number – zone B2 4.5.6 Customer account number and / or sender Email – zone B3
16	4.5.7 Requirements for rendering of addresses on item labels 4.6 Addressee zone 4.6.1 General 4.6.2 Addressee zone dimensions – zone C
17	4.6.3 TO indicator 4.6.4 Name and address of addressee – zones C0 and C1 4.6.5 Telephone number – zone C2
18	4.6.6 Email address – zone C3 4.6.7 Requirements for rendering addresses on item label 4.7 Instruction zone 4.7.1 General
19	4.7.2 Instruction zone dimensions 4.7.3 Symbol dimensions 4.7.4 Standard symbols 4.8 Item-identifier zone – Zone E 4.8.1 General
20	4.8.2 Dimensions of item-identifier zone – Zone E 4.8.3 Barcode printing quality 4.8.4 Unique item identifier – Zone E1
21	4.8.5 Additional barcode – Zone E2 4.8.6 Barcode zone example
23	4.9 Label examples
26	4.10 Address printed quality 4.11 Icons 4.12 Label materials
27	Annex A (informative)Electronic exchange connected to the parcel and the label
28	Annex B (informative)Description of the data to be transmitted to the logistic operator (case with S10 identifier)
30	Annex C (informative)Instruction symbols
32	Annex D (informative)Guideline for the Utilization of GS1 Standards in the CEP industry
35	Annex E (informative)IFTMIN – The necessary specification

BSI PD CEN/TS 17073:2020

Sun, 20 Oct 2024 01:14:55 +0000

The interface is composed of two items:

the physical label attached on the parcel: contents, sizes, minimum requirements to guarantee the quality and efficiency of the logistic process (sorting, delivery).
the electronic exchanges between the sender and the logistic operator with the description of the data to be provided, the format of the exchanges.

NOTE 1

NOTE 2

PDF Catalog

PDF Pages	PDF Title
2	undefined
7	1 Scope 2 Normative references
8	3 Terms and definitions 4 The physical parcel label 4.1 Contents in the label
10	4.2 Label dimensions 4.3 General display rules 4.3.1 Label text font 4.3.2 Colours
11	4.3.3 Label zones
12	4.3.4 Zone contents 4.4 Header zone 4.4.1 General 4.4.2 Header dimensions – zone A
13	4.5 Sender zone 4.5.1 General 4.5.2 Sender zone dimensions – zone B 4.5.3 FROM indicator
14	4.5.4 Address of sender – zone B0 and B1 4.5.5 Sender telephone number – zone B2 4.5.6 Customer account number and / or sender Email – zone B3
15	4.5.7 Requirements for rendering of addresses on item labels 4.6 Addressee zone 4.6.1 General 4.6.2 Addressee zone dimensions – zone C 4.6.3 TO indicator
16	4.6.4 Name and address of addressee – zones C0 and C1 4.6.5 Telephone number – zone C2 4.6.6 Email address – zone C3
17	4.6.7 Requirements for rendering addresses on item label 4.7 Instruction zone 4.7.1 General 4.7.2 Instruction zone dimensions 4.7.3 Symbol dimensions
18	4.7.4 Standard symbols 4.8 Item-identifier zone – Zone E 4.8.1 General 4.8.2 Dimensions of item-identifier zone – Zone E 4.8.3 Barcode printing quality 4.8.4 Unique item identifier – Zone E1
19	4.8.5 Additional barcode – Zone E2
20	4.8.6 Barcode zone example
21	4.9 Label examples
24	4.10 Address printed quality 4.11 Icons 4.12 Label materials
25	Annex A (informative)Electronic exchange connected to the parcel and the label
26	Annex B (informative)Description of the data to be transmitted to the logistic operator (case with S10 identifier)
28	Annex C (informative)Instruction symbols
30	Annex D (informative)Guideline for the Utilization of GS1 Standards in the CEP industry
33	Annex E (informative)IFTMIN – The necessary specification

BSI PD CEN/TS 16919:2016

Sun, 20 Oct 2024 01:12:52 +0000

An IDT-PAE interface enables interoperability among several systems and processes by providing specifications to the following requirements:

Data Collection and Transfer: Specification of data transported from the devices to higher level systems. There may be more than one permissible protocol referring to different OSI layers. The standard will define where the communication requires polling and where asynchronous messages are used. The basis is messages triggered by events.
Data Storage and Format: Specification how data is formatted and structured. This concerns the choice between XML, CSV, EDI, JSON and other formats including possible binary representations.
Data Model: Specification of the semantics (meanings) behind the data. This is the most important part and the one of the most important objectives for the specification. This means that conceptual data model and its mapping to the Data Format will be developed. Major focus on specifications level of detail will be placed in order to provide a document that will provide detailed specification information without being too general or too specific.

BSI PD CEN/TS 16326:2013

Sun, 20 Oct 2024 01:10:56 +0000

This Technical Specification constitutes the functional specification of a secure electronic postal service, referred to as the postal registered electronic mail or PReM service. PReM provides a trusted and certified electronic mail exchange between mailer, postal operators and addressee/mailee. In addition, evidence of corresponding events and operations within the scope of PReM will be generated and archived for future attestation. The PReM service is defined by reference to the concepts, schemas and operations defined in CEN/TS 15121-1:2011. It utilises six SePS operational verbs (CheckIntegrity, LogEvent, Postmark, RetrieveResults, Sign and Verify) and the five additional server-side operational verbs (SendMessagetoDestination, Subscribe Notification, UnscbscribeNotification, RejectMessage and ReceiveNotification) to fulfil the operational requirements of a PReM System. Return of Investment (ROI), market potential, revenues model, business plan and pricing policy are outside the scope of this functional specification. Postal operators are advised to make the necessary marketing study and research prior to considering leasing, procuring or developing such a PReM system in accordance with this functional specification.