Details of complaint: on 2/8/2018 customer reported several telemetry transmitters were experience communication loss.Customer was advised to reboot the org and check the network switch.Customer was to call back to confirm resolution.Additional follow up attempts did not yield a response.Service requested: troubleshooting.Service performed: troubleshooting.Investigation result: service history for the org receiver shows one additional communication loss incident: ticket (b)(4) - reported on 1/3/2019.The communication loss incidents were resolved by rebooting the org.The root cause could not be determined.-- service history for this facility shows the following communication loss incidents: (b)(4) - reported 4/23/2019.Not related to org receivers.(b)(4) - reported on 1/3/2019.The communication loss incidents were resolved by rebooting the org.The root cause could not be determined.37321 - reported 8/19/2018.Four telemetry transmitters were showing communication loss on the cns.The root cause could not be determined due to insufficient information provided.Customer did not respond to further inquiries.36364 - reported 8/5/2018.Not related to org receivers.In the current ticket and in (b)(4), org was causing the communication.However, the root cause as to why communication loss occurred could not be determined, due to insufficient data.Since the last reported org issue on 1/3/2019, there has been no other org related issues at this facility.Additional information: b4.Date of this report f6.Date user facility/importer became aware of the event f7.Type of report f11.Date report sent to fda f13.Date report sent to manufacturer g4.Date received by manufacturer g7.Type of report h2.If follow-up, what type? additional information h6.Event problem and evaluation codes h10.Additional manufacturer narrative.
|