Toimialayhteisöt

 

ISO 9626:2016 applies to rigid stainless steel needle tubing suitable for use in the manufacture of hypodermic needles and other medical devices primarily for human use. It provides requirements and test methods for the tubes manufactured for needles as component used in medical devices. Additional performance testing on the tube aspect may be required when the component is incorporated in the ready-to-use device. It specifies the dimensions and mechanical properties of steel tubing of designated metric sizes 3,4 mm (10 Gauge) to 0,18 mm (34 Gauge). It does not apply to flexible stainless steel tubing because the mechanical properties differ from those specified for rigid tubing in ISO 9626:2016. However, manufacturers and purchasers of flexible tubing are encouraged to adopt the dimensional specifications given in ISO 9626:2016.

 

ISO 7864:2016 specifies requirements for sterile hypodermic needles for single use of designated metric sizes 0,18 mm to 1,2 mm. It does not apply to those devices that are covered by their own standard such as dental needles and pen needles.

 

 

This document specifies the requirements for marking of industrial metallic valves. It defines the method of applying the markings, on the body, on a flange, on an identification plate or any other location. When specified as a normative reference in a valve product or performance standard, this document is considered in conjunction with the specified requirements of that valve product or performance standard. The marking requirements for plastic valves are not within the scope of this document.

 

This document applies to the following types of cranes: 1. mobile cranes, with the following characteristics: - self-powered crane mounted on a chassis, equipped with a boom, which may be fitted on a mast (tower), and capable of travelling laden or unladen, without the need for fixed runways and which relies on gravity for stability, the chassis of the crane not having any capability to carry goods other than crane parts or equipment whilst travelling on public roads; - mobile cranes can operate on tyres or crawlers. In fixed positions, they can be supported by outriggers or other accessories increasing their stability; - the superstructure of mobile cranes can be of the type of full circle slewing, limited slewing or non-slewing. It is normally equipped with one or more hoists and/or hydraulic cylinders for lifting and lowering the boom and the load; - mobile cranes can be equipped either with telescopic booms, with articulated booms, with lattice booms - or a combination of these - of such a design that they can readily be lowered; - loads can be handled by hook block assemblies or other load-lifting attachments for special services. 2. mobile harbour cranes, with the following characteristics: - mobile crane without on-road approval; - the main purpose of the mobile harbour crane is cargo-, bulk-handling with a moderate to very heavy number of load cycles in accordance with ISO 4301-2:2020 or heavy lift operation. 3. off-road mobile cranes - mobile crane which travels on site. EXAMPLES Rough terrain crane, crawler crane. 4. on-road mobile cranes - mobile crane which has the necessary equipment to travel on public roads and on the job site. EXAMPLES All terrain crane, truck crane. NOTE 1 The term "boom" used in this standard is referred to as "jib" in the Outdoor Noise Directive see Bibliography [1]. NOTE 2 Examples for typical mobile cranes are shown in Annex A. This document is applicable to the design, installation of safety devices, information for use, maintenance and testing of mobile cranes. This document is applicable for mobile cranes mounted on other types of carriers (e.g. railcars, skidding systems, portals on rails, rubber tyred portals), but does not cover the additional hazards related to the mounting of mobile cranes on these types of carriers. Types of mobile crane types and their major components are given in Clauses A.1, A.2, B.1 and B.2. This document, unless explicitly referred, is not applicable to: 5. loader cranes (see EN 12999); 6. off-shore cranes (see EN 13852-1); 7. floating cranes (see EN 13852-2); 8. slewing jib cranes (see EN 14985); 9. variable reach trucks (see the EN 1459 series of standards); 10. to cranes, installed on an agricultural tractor, intended to tow a trailer which has capability to carry goods; 11. mobile self-erecting tower cranes (see EN 14439); 12. earth-moving machinery (see the EN 474 series of standards); 13. drilling and foundation equipment (see the EN 16228 series of standards). This document does not cover hazards related to: - the lifting of persons. NOTE 3 The use of mobile cranes for the lifting of persons is subject to specific national regulations. - the working in the vicinity of live overhead powerlines, see also ICSA N007 Guidance - Safe Crane Operation in the Vicinity of Power Lines. International Crane Stakeholder Assembly (see Bibliography [19]). - the combination of a mobile crane with other machinery. - the use of the mobile crane in potentially explosive atmosphere. - duty cycle operation such as grab, magnet, piling or similar operation, is outside the scope of this document. The hazards covered by this document are identified by Annex C. This document is not applicable to mobile cranes which are manufactured before the date of publication of this document by CEN.

 

This document provides specifications for the production of unreinforced, reinforced and prestressed precast concrete products protected from adverse weather conditions during production, and made of compact light-, normal- and heavyweight concrete according to EN 206 with no appreciable amount of entrapped air other than entrained air. Concrete containing fibres for other than mechanical properties (steel, polymer or other fibres) is also covered. This document also covers clay, EPS, and lightweight formwork blocks for beam-and-blocks floor systems. It does not cover precast reinforced components of lightweight aggregate concrete with open structure nor glassfibre reinforced concrete. It can also be used to specify products for which there is no standard.

 

ISO 21010:2017 specifies gas/material compatibility requirements (such as chemical resistance) for cryogenic vessels, but it does not cover mechanical properties (e.g. for low-temperature applications). ISO 21010:2017 provides general guidance for compatibility with gases and detailed compatibility requirements for oxygen and oxygen-enriched atmospheres. This document also defines the testing methods for establishing oxygen compatibility of materials (metallic and non-metallic) to be used for cryogenic vessels and associated equipment. ISO 21010:2017 focuses on materials that are normally with or could be in contact with cryogenic fluids.

 

ISO 21029-1:2018 specifies requirements for the design, fabrication, type test and initial inspection and test of transportable vacuum-insulated cryogenic pressure vessels of not more than 1 000 l volume. This document applies to transportable vacuum-insulated cryogenic vessels for fluids as specified in 3.1 and Table 1 and does not apply to such vessels designed for toxic fluids. NOTE 1 This document does not cover specific requirements for refillable liquid hydrogen and LNG tanks that are primarily dedicated as fuel tanks in vehicles. For fuel tanks used in land and marine vehicles, see ISO 13985. NOTE 2 Specific requirements for open top dewards are not covered by this document.

 

This document gives guidance on the sample preparation of milk and milk products for physical and chemical analysis, including analysis by applying instrumental methods. This document describes the (sub)sampling, and sample preparation steps carried out after sampling according to ISO 707 | IDF 50 (1) and prior to method-specific sample preparations, e.g. as with analytical methods listed in References (2) to (21). NOTE Analysis on volatile substances, minor components or allergens can require additional precautionary measures in sample preparation in order to avoid loss of or contamination with one or more target analytes.

 

This document specifies requirements for high chromium white cast iron grit, as supplied for blast-cleaning processes. It specifies ranges of particle sizes, together with corresponding grade designations. Values are specified for hardness, density, defect/structural requirements, metallographic structure and chemical composition. The requirements specified in this document apply to abrasives supplied in the new condition only. They do not apply to abrasives either during or after use. High chromium white cast iron grits are used in both static and site blasting equipment. They are most often selected where there is a possibility for the recovery and re-use of the abrasive. NOTE 1 Although this document has been developed for preparation of steelwork, these materials are predominantly used for non-ferrous substrates. The properties specified will generally be appropriate for use when preparing other material surfaces, or components, using blast-cleaning techniques, and can be used for applications where no subsequent coating is applied. NOTE 2 Whenever dissimilar metals are used together, galvanic corrosion can occur.

 

1.1 General Scope of the Standard The main objective of the present standard is to present the Reference Data Model for Public Transport, based on: - the Reference Data Model, EN12896, known as Transmodel V5.1, - CEN EN 28701, known as IFOPT, incorporating the requirements of - EN 15531-1 to -3 and TS 15531-4 and -5: Service interface for real-time information relating to public transport operations (SIRI), - TS 16614-1 and 2: Network and Timetable Exchange (NeTEx), in particular, the specific needs for long distance train operation. A particular attention is drawn to the data model structure and methodology: - the data model is described in a modular form in order to facilitate the understanding and the use of the model, - the data model is entirely described in UML. In particular, a Reference Data Model kernel is described, referring to the data domain: - Network Description: routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places. This part corresponds to the Transmodel V5.1 Network Description extended by the IFOPT relevant parts. Furthermore, the following functional domains are considered: - Timing Information and Vehicle Scheduling (runtimes, vehicle journeys, day type-related vehicle schedules) - Passenger Information (planned and real-time) - Fare Management (fare structure, sales, validation, control) - Operations Monitoring and Control: operating day-related data, vehicle follow-up , control actions - Management Information and Statistics (including data dedicated to service performance indicators). - Driver Management: - Driver Scheduling (day-type related driver schedules), - Rostering (ordering of driver duties into sequences according to some chosen methods), - Driving Personnel Disposition (assignment of logical drivers to physical drivers and recording of driver performance). The data modules dedicated to cover most functions of the above domains will be specified. Several concepts are shared by the different functional domains. This data domain is called “Common Concepts”. 1.2 Functional Domain Description The different functional domains taken into account in the present standard and of which the data have been represented as the reference data model are described in “Public Transport Reference Data Model - Part 1: Common Concepts”. They are: - Public Transport Network and Stop Description - Timing Information and Vehicle scheduling - Passenger information - Fare Management - Operations monitoring and control - Management information - Personnel Management: Driver Scheduling, Rostering, Personnel Disposition. The aspects of multi-modal operation and multiple operators’ environment are also taken into account. 1.3 Particular Scope of this Document The present European Standard entitled “Reference Data Model for Public Transport – Part 3: Timing Information and Vehicle Scheduling”. incorporates - Journey and Journey Times Model: describes the time-related information at the level of vehicle journeys, i.e. planned timing for the vehicles at day-type level. - Dated Journey Model: describes the link of the timing information for a single operating day and the day type related timing, - Passing Times Model: describes all the different types of passing times for the day type related information, - Vehicle Service Model: describes the information related the work of vehicles as planned for days types. It constitutes the main part of the Vehicle Scheduling Data Domain. - Vehicle Journey Assignment Model: describes operational assignments (advertised vehicle labels, stopping positions) related to particular vehicle journeys. This document itself is composed of the following parts: - Main document (normative) representing the data model, (...)

 

1.1 General Scope of the Standard The main objective of the present standard is to present the Reference Data Model for Public Transport, based on: - the Reference Data Model, EN 12896, known as Transmodel V5.1; - EN 28701:2012, Intelligent transport systems - Public transport - Identification of Fixed Objects in Public Transport (IFOPT), although note that this particular standard has been withdrawn as it is now included within Parts 1 and 2 of this standard (EN 12896-1:2016 and EN 12896-2:2016) following their successful publication. incorporating the requirements of: - EN 15531-1 to -3 and CEN/TS 15531-4 and -5: Public transport - Service interface for real-time information relating to public transport operations (SIRI); - CEN/TS 16614-1 and -2: Public transport - Network and Timetable Exchange (NeTEx), in particular the specific needs for long distance train operation. Particular attention is drawn to the data model structure and methodology: - the data model is described in a modular form in order to facilitate the understanding and the use of the model; - the data model is entirely described in UML. The following functional domains are considered: - Network Description: routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places; - Timing Information and Vehicle Scheduling (runtimes, vehicle journeys, day type-related vehicle schedules); - Passenger Information (planned and real-time); - Fare Management (fare structure, sales, validation, control); - Operations Monitoring and Control: operating day-related data, vehicle follow-up, control actions; - Driver Management: - Driver Scheduling (day-type related driver schedules), - Rostering (ordering of driver duties into sequences according to some chosen methods), - Driving Personnel Disposition (assignment of logical drivers to physical drivers and recording of driver performance); - Management Information and Statistics (including data dedicated to service performance indicators). The data modules dedicated to cover most functions of the above domains will be specified. Several concepts are shared by the different functional domains. This data domain is called "Common Concepts". 1.2 Functional Domain Description The different functional domains (enumerated above) taken into account in the present standard, and of which the data have been represented as the reference model, are described in EN 12896-1:2016, Public transport - Reference data model - Part 1: Common concepts. 1.3 Particular Scope of this Document The present document entitled Public transport - Reference data model - Part 5: Fare Management addresses Fare Information for Public Transport and incorporates the following data packages: - Fare Structure; - Access Right Assignment; - Fare Pricing; - Sales Description; - Sales Transaction; - Fare Roles; - Validation and Control; - Explicit Frames for Fares. This document itself is composed of the following parts: - Main document (normative) representing the data model for the concepts shared by the different fare domains covered by Transmodel, - Annex A (normative), containing the data dictionary, i.e. the list of all the concepts and attribute tables present in the main document together with the definitions, - Annex B (normative), providing a complement to the "Common Concepts" domain, particularly useful for parts 4 to 8 of the Public Transport Reference Data Model, Annex C (informative), indicating the data model evolutions from previous versions of Transmodel (EN 12896:2006).

 

This document incorporates the following main data packages: - Dated Production Components; - Call; - Dated Call; - Production Plan; - Detecting & Monitoring; - Situation; - Messaging; - Control Action; - Operational Event & Incident; - Facility Monitoring & Availability; - Occupancy. It is composed of the following parts: - main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative); - Annex A containing the data dictionary and attribute tables, i.e. the list of all the concepts presented in the main document together with their definitions (normative); - Annex B presenting the model evolution (informative); - Annex C detailing the mapping to DATEX-II and SIRI (informative). - Annex D, providing details of the significant technical changes between this document and EN 12896 4:2019 (informative).

 

1.1 General scope of the Standard The main objective of this European Standard is to present the Public Transport Reference Data Model based on: - the Public Transport Reference Data Model published 2006 as EN12896 and known as Transmodel V5.1, - the model for the Identification of Fixed Objects for Public transport, published 2009 as EN 28701and known as IFOPT, incorporating the requirements of - EN15531-1 to 3 and TS15531-4 and 5: Service interface for real-time information relating to public transport operations (SIRI), - TS16614-1 and 2: Network and Timetable Exchange (NeTEx), in particular the specific needs for long distance train operation. Particular attention is drawn to the data model structure and methodology: - the data model is described in a modular form in order to facilitate understanding and use of the model, - the data model is entirely described in UML. In particular, a Reference Data Model kernel is described, referring to the data domain: - Network Description: routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places. This part corresponds to the network description as in Transmodel V5.1 extended by the relevant parts of IFOPT. Furthermore, the following functional domains are considered: - Timing Information and Vehicle Scheduling (runtimes, vehicle journeys, day type-related vehicle schedules) - Passenger Information (planned and real-time) - Operations Monitoring and Control: operating day-related data, vehicle follow-up , control actions - Fare Management (fare structure and access rights definition, sales, validation, control) - Management Information and Statistics (including data dedicated to service performance indicators). - Driver Management: - Driver Scheduling (day-type related driver schedules), - Rostering (ordering of driver duties into sequences according to some chosen methods), - Driving Personnel Disposition (assignment of logical drivers to physical drivers and recording of driver performance). The data modules dedicated to cover most functions of the above domains will be specified. Several concepts are shared by the different functional domains. This data domain is called “Common Concepts”. 1.2 Functional domain description 1.2.1 Public transport network and stop description The reference data model includes entity definitions for different types of points and links as the building elements of the topological network. Stop points, timing points and route points, for instance, reflect the different roles one point may have in the network definition: whether it is used for the definition of (topological or geographical) routes, as a point served by vehicles when operating on a line, or as a location against which timing information like departure, passing, or wait times are stored in order to construct the timetables. The line network is the fundamental infrastructure for the service offer, to be provided in the form of vehicle journeys which passengers may use for their trips. The main entities describing the line network in the reference data model are the line, the route and the journey pattern, which refer to the concepts of an identified service offer to the public, the possible variants of itineraries vehicles would follow when serving the line, and the (possibly different) successions of stop points served by the vehicles when operating on the route. The functional views of the network are described as layers. A projection is a mechanism enabling the description of the correspondence between the different layers. This mapping between the layers is particularly useful when spatial data from different environments (sources, functional domains) have to be combined. An example of such a situation is the mapping of the public transport network on the road network. (...)

 

This document incorporates the following main data packages: - Network Description; - Fixed Object; - Tactical Planning Components; - Explicit Frame. It is composed of the following parts: - main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative); - Annex A containing the data dictionary and attribute tables, i.e. the list of all the concepts presented in the main document together with their definitions (normative); - Annex B presenting the model evolution (informative). - Annex C, providing details of the significant technical changes between this document and EN 12896-2:2016 (informative).

 

This document specifies requirements and test methods for pipes and fittings which are part of piping systems for the renovation of underground non-pressure drainage and sewerage networks. It is applicable to pipes, fittings and assemblies, made from thermoplastic composite materials, as manufactured and as installed. It is not applicable to the existing pipeline. It is applicable to technique families for renovation: — lining with spirally-wound (SWO) pipes; — lining with a rigidly anchored plastic inner layer (RAPL). and intended to be used at an operating temperature of 20 °C as the reference temperature. In the case of lining with SWO pipes, where the pipes, are formed on site, to a fixed or variable diameter, by spirally winding and jointing a pre-manufactured profiled plastics strip, this document applies to, strips made of unplasticized poly(vinyl chloride) (PVC U), or of polyethylene (PE), with or without steel stiffening elements, and installed with or without integral locking mechanism. In the case of lining with RAPL, where a single rigid annulus of structural cementitious grout is formed behind a plastics inner layer serving as permanent formwork anchored to the grout. This document applies to integrally joined profiled plastics strips of PVC-U or PE or studded sheets of PE, and grout systems with or without steel reinforcement. It does not apply to the structural design of the lining system. NOTE Systems with multiple annuli are available, but these are controlled by patent rights and not covered by this document.

 

This document specifies requirements and test methods for pipes and fittings which are part of piping systems for the rehabilitation, by means of renovation and trenchless replacement, of underground non-pressure drains and sewers networks. It is applicable to pipes, fittings and assemblies, made from thermoplastic composite materials, as manufactured and as installed. It is not applicable to the existing pipeline. It is applicable to the following technique families for renovation: and intended to be used at a service temperature not exceeding 45 °C according to material as follows: in both cases with re-rating factors on mechanical characteristics for service temperatures in excess of 35 °C determined by dedicated type testing. In the case of lining with SWO pipes, where the pipes, are formed on site, to a fixed or variable diameter, by spirally winding and jointing a pre-manufactured profiled plastics strip, this document applies to, strips made of unplasticized poly(vinyl chloride) (PVC U), or of polyethylene (PE), with or without steel stiffening elements, and installed with or without integral locking mechanism. In the case of lining with RAPL, where a single rigid annulus of structural cementitious grout is formed behind a plastics inner layer serving as permanent formwork anchored to the grout. This document applies to integrally joined profiled plastics strips of PVC-U or PE or studded sheets of PE, and grout systems with or without steel reinforcement. It does not apply to the structural design of the lining system.

 

The document incorporates the following main data packages: - Trip Description; - Passenger Information Queries. It is composed of the following parts: - main document representing the data model for the concepts shared by the different fare domains covered by Transmodel (normative); - Annex A, containing the data dictionary and attribute tables, i.e. the list of all the concepts presented in the main document together with the definitions (normative); - Annex B presenting the model evolution (informative). - Annex C, providing details of the significant technical changes between this document and EN 12896 6:2019 (informative).

 

1.1 General Scope of the Standard The main objective of the present standard is to present the Reference Data Model for Public Transport, based on: - the Reference Data Model, EN 12896, known as Transmodel V5.1; - EN 28701:2012, Intelligent transport systems - Public transport - Identification of Fixed Objects in Public Transport (IFOPT), although note that this particular standard has been withdrawn as it is now included within Parts 1 and 2 of this European Standard (EN 12896-1:2016 and EN 12896-2:2016) following their successful publication; incorporating the requirements of: - EN 15531-1 to -3 and CEN/TS 15531-4 and -5: Public transport - Service interface for real-time information relating to public transport operations (SIRI); - CEN/TS 16614-1 and -2: Public transport - Network and Timetable Exchange (NeTEx), in particular the specific needs for long distance train operation. Particular attention is drawn to the data model structure and methodology: - the data model is described in a modular form in order to facilitate the understanding and the use of the model; - the data model is entirely described in UML. The following functional domains are considered: - Network Description: routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places; - Timing Information and Vehicle Scheduling (runtimes, vehicle journeys, day type-related vehicle schedules); - Passenger Information (planned and real-time); - Fare Management (fare structure, sales, validation, control); - Operations Monitoring and Control: operating day-related data, vehicle follow-up, control actions; - Driver Management: - Driver Scheduling (day-type related driver schedules), - Rostering (ordering of driver duties into sequences according to some chosen methods), - Driving Personnel Disposition (assignment of logical drivers to physical drivers and recording of driver performance); - Management Information and Statistics (including data dedicated to service performance indicators). The data modules dedicated to cover most functions of the above domains will be specified. Several concepts are shared by the different functional domains. This data domain is called "Common Concepts". 1.2 Functional Domain Description The different functional domains (enumerated above) taken into account in the present document, and of which the data have been represented as the reference model, are described in EN 12896-1, Public transport - Reference data model - Part 1: Common concepts. 1.3 Particular Scope of this Document The present document entitled Public transport - Reference data model - Part 7: Driver management incorporates the following data packages: - Driver Scheduling; Rostering; - Personnel Disposition; - Driver Control Actions. This document itself is composed of the following parts: - Main document (normative) presenting the data model for the concepts shared by the different domains covered by Transmodel, - Annex A (normative), containing the data dictionary, i.e. the list of all the concepts and attribute tables present in the main document together with the definitions, - Annex B (normative), providing a complement to EN 12896-1:2016, particularly useful for Parts 4 to 8 of the Public Transport Reference Data Model; and - Annex C (informative), indicating the data model evolutions.

 

This document describes a highly specific method for the enumeration of Escherichia coli (E. coli) in water. The method is based on membrane filtration followed by culture at 44 °C on chromogenic agar medium containing an ingredient for the detection of the enzyme ß-glucuronidase, and calculation of the number of target organisms in the sample[5,6,13]. Because of the high specificity of the method, this document is suitable for waters with high levels of background bacteria, such as surface waters including bathing water and wastewater provided that they contain little particulate or colloidal matter relative to the E. coli concentration. The method can be used for fresh water and, with an adaptation, for marine water. E. coli strains which do not grow at 44 °C and those that are ß-glucuronidase negative, such as E. coli O157, will not be detected as E. coli by this method. This method is not applicable to the enumeration and detection of coliform bacteria other than E. coli.