Difference between revisions of "Problem reporting"
m (Protected "Problem reporting" ([edit=sysop] (indefinite) [move=sysop] (indefinite))) |
|
(No difference)
|
Revision as of 10:44, 7 March 2013
According to the Central Reporting Office (CRO) terms of reference one of the key tasks of the CRO is to manage problem reporting, investigation and resolution when local resolution is impossible. It is anticipated that there will be two levels of problem reporting and investigation; a local level managed by a particular stakeholder (e.g. ANSP, ACSP, airline, avionics supplier etc.) and a central level managed by the CRO. Whether any particular stakeholder decides to offer a local problem reporting and investigation service is a matter for them to decide and if they do decide to offer such as service, how that service operates is also a matter for them to decide. However in order to maintain an overview of the status of the entire system the CRO would like to be informed about all problems found and their resolutions, even if those problems have been reported and resolved at the local level. Hence the CRO offers a Problem Reporting tool that allows:
- Problems that are reported and resolved locally to be recorded centrally with the CRO.
- Problems that are reported locally but which cannot be resolved locally to be passed on to the CRO for resolution. This may be for any reason, for example because the problem involves the interaction of several parts of the overall system.
Access to the problem reporting tool is restricted to registered users, but a description of important problems and their resolutions is maintained on this wiki for general information.
What sort of problems should be reported?
The CRO problem reporting procedure is intended to be used to record any kind of problem experienced in the implementation and usage of the data link services in Europe. For example it should be used to report problems relating to:
- The operational use of datalink services (DLIC, ACM, ACL and AMC)
- The use of ATN
- The accomodation of FANS 1/A aircraft
- The use of VDL Mode 2
- Any of the documentation associated with the implementation of the DLS IR (e.g. the implementing rule itself, the SPR, guidance documents etc.)
- Any specific piece of technical equipment.
The procedure should not be used to ask for clarification of any documentation, there is a separate forum for this purpose. Nor should the system be used for problems in local documentation, this is expected to be handled locally.
How to report a problem
A separate online tool is provided to manage problem reporting and a guide for how to use the CRO Problem Reporting tool is provided on this wiki.