1. A method of implementing a dynamic service-event management system, comprising the steps of describing assigned service by describing the position of an event source within bearers of the service as a two-dimensional route description, wherein a route constitutes the first dimension and an element within the route constitutes the second dimension, or as a three-dimensional route description, wherein a route constitutes the first dimension, an element within the route constitutes the second dimension and the bearer of the element within the route constitutes the third dimension; projecting of one or more events affecting status and/or quality of a service onto said service in two steps by using a common-format event type, in the first step, converting an event ( 11 , 21 , 24 ) originating from an external source in a network parser module ( 1 , 2 ) to a common-format event including an identifier of the source of the incoming event ( 11 , 21 , 24 ) as an event source identifier, a status generated by the incoming event information as a status, an operational status generated by an incoming event information expressed in percentage, an identifier of the incoming event source as a failure cause expressed in common-format, in the second step, by processing the resulting common-format event ( 12 , 22 ) in a service parser module ( 3 ), where the common-format event comprising the event source identifier, the status carried by the event, the number defining the operational status expressed in percentage, the failure causes expressed in common-format; obtaining assigned service and the position of the event source within the bearers of the service from the event source identifier with the aid of the two-dimensional or three-dimensional route description between bearers of the service; projecting the information carried by the common-format event ( 12 , 22 ) onto said service by determining a number of operational routes based on the received common-format event ( 12 , 22 ) and stored status of the bearers of the service, then based on the above; deciding the status of service is operational if there is an operational route, else deciding the status of service is faulty; determining the operational status of the service expressed as a numerical ratio of operational routes and faulty routes in percentage; determining that the failure cause of the service are the failure causes of faulty routes; storing the common-format event ( 12 , 22 ) comprising actual status of bearer in a memorabilia.