This European Standard specifies safety requirements and their verification for the design and construction of pedestrian controlled integrally powered lawn aerators and scarifiers which are designed for re-generating lawns by, for instance, combing out grass, thatch and moss or cutting vertically into the lawn face using tines which rotate about a horizontal axis. It describes methods of elimination or reduction of hazards arising from their use. In addition, it specifies the type of information to be provided by the manufacturer on safe working practices.
Throughout this document, the term “machine” applies to those machines known as aerators, scarifiers, corers, lawn rakes or grass rakes.
It does not apply to:
—   aerators/scarifiers made from a machine falling within the scope of EN 709:1997+A4:2009 when fitted with an aerating/scarifying implement;
—   non-powered aerators;
—   vertical axis aerators; or
—   those aerators which cut into the soil by means of a reciprocating motion or by water pressure.
The electrical aspects of mains operated machines are covered by EN 60335-1. The safety aspects of batteries other than batteries for starting the engine and the electrical safety aspects of battery powered lawn aerators and scarifiers are not covered by this document.
It deals with all significant hazards, hazardous situations and events relevant to scarifiers and aerators, when they are used as intended and under the conditions foreseen by the manufacturer (see Clause 4). Environmental hazards and EMC have not been considered in this document.
This document is not applicable to aerators/scarifiers which are manufactured before the date of its publication.

  • Standard
    61 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This European Standard specifies safety requirements and their verification for the design and construction of pedestrian controlled internal combustion engine powered lawn aerators and scarifiers which are designed for re-generating lawns by, for instance, combing out grass, thatch and moss or cutting vertically into the lawn face using tines which rotate about a horizontal axis. It describes methods of elimination or reduction of hazards arising from their use. In addition, it specifies the type of information to be provided by the manufacturer on safe working practices.
Throughout this document, the term "machine" applies to those machines known as aerators, scarifiers, corers, lawn rakes or grass rakes.
It does not apply to:
-   aerators/scarifiers made from a machine falling within the scope of EN 709:1997+A4:2009 when fitted with an aerating/scarifying implement;
-   non-powered aerators;
-   vertical axis aerators; or
-   those aerators which cut into the soil by means of a reciprocating motion or by water pressure.
It deals with all significant hazards, hazardous situations and events relevant to scarifiers and aerators, when they are used as intended and under the conditions foreseeable by the manufacturer (see Clause 4). Environmental hazards have not been considered in this document.
This document is not applicable to aerators/scarifiers which are manufactured before the date of its publication.

  • Standard
    61 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This Technical Specification (TS) defines the Technical, Operational and Maintenance requirements for Flight Data Processing (ATC-ATC) system interoperability.
Flight Data Processing (FDP) interoperability between ATC units is a key element to facilitate and harmonise Flight Data systems data exchanges and critical to the functioning of a harmonised European Air Traffic Management system. Interoperability specification for FDP (ATC-ATC) includes coordination and transfer; correlation and surveillance, facilitation of optimum routes; MTCD and resolutions; recovery support; ground-ground situation awareness and traffic management.

  • Technical specification
    13 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This Technical Specification is for the production of conformity evidence for FDP-FDP ground-based system interoperability which has to be declared by the Air Navigation Service Provider (ANSP) before putting FDP-systems into service.
This Technical Specification defines the Technical, Operational and Maintenance requirements for Flight Data Processing (ATC-ATC) system interoperability.
Flight Data Processing (FDP) interoperability between ATC units is a key element to facilitate and harmonise Flight Data systems data exchanges and critical to the functioning of a harmonised European Air Traffic Management system.
FDP Interoperability can be achieved by the use of different techniques appropriate to the operational need, e.g. message exchange, replication mechanisms and data sharing.
The architectural framework in which the different actors have to inter-operate is of major importance to define the context in which the European Standards have to be developed.
For a systematic solution to certain flight data inconsistency problems currently existing in Europe, the definition of a Flight Object (FO) is required to become a conceptual single point of reference for flight data to be used by stakeholder systems.
Interoperability of FDP (ATC-ATC) includes coordination and transfer; correlation and surveillance, facilitation of optimum routes; MTCD and resolutions; recovery support; ground-ground situation awareness and traffic management.
Any software elements related to the software assurance level of a FDP System are outside of the scope of the present document.
Although a consensus can be reached on the present state of the art in FDP interoperability, this state of the art is not mature enough to be put into a European Standard (EN). The European Committee for Standardisation thus resolved to record the obtained technical consensus as the present Technical Specification, with informative status.
(...)

  • Technical specification
    13 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document is for the production of assurance evidence for software used in ground-based systems and their constituents.
This Community Specification on Software Assurance Levels (SWAL) is intended to apply to software that is part of the EATMN, focusing only on it’s “ground” segment and providing a reference against which stakeholders can assess their own practices for software specification, design, development, operation, maintenance, evolution and decommissioning.
This Community Specification defines the Technical, Operational and Maintenance requirements for Software Assurance Levels to demonstrate compliance with the applicable (see Annex A) Essential Requirements of the Regulation (EC) N° 552/2004 of the European Parliament and of the Council on the interoperability of the European Air Traffic network (“the Interoperability regulation”).
Requirements in the present document which refer to “should” statements or recommendations in the normatively referenced material (2.1) are to be interpreted as fully normative (“shall”) for the purpose of compliance with the present document.

  • Draft
    35 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document is for the production of assurance evidence for software used in ground-based systems and their constituents.
This Community Specification on Software Assurance Levels (SWAL) is intended to apply to software that is part of the EATMN, focusing only on it’s “ground” segment and providing a reference against which stakeholders can assess their own practices for software specification, design, development, operation, maintenance, evolution and decommissioning.
This Community Specification defines the Technical, Operational and Maintenance requirements for Software Assurance Levels to demonstrate compliance with the applicable (see Annex A) Essential Requirements of the Regulation (EC) N° 552/2004 of the European Parliament and of the Council on the interoperability of the European Air Traffic network (“the Interoperability regulation”).
Requirements in the present document which refer to “should” statements or recommendations in the normatively referenced material (2.1) are to be interpreted as fully normative (“shall”) for the purpose of compliance with the present document.

  • Draft
    35 pages
    English language
    sale 10% off
    e-Library read for
    1 day