COMPLIANCE INFO 2005 - 2009 - Laserfiche WebLink

Home Browse Search

FUELQ--y Five Greenway Plaza,Suite 1300 Houston,Texas 77046 Supply Chain Management phone 713 222 5793 fax 713 222 5701 & Tax Automation Solutions www.FuelQuest.com 26 January 2009 Dear 7 Eleven Compliance Group, On January 20'h, 2009, Our AMS team received notification that your group was served a Notice of Violation by the State of California for site 19976 in Manteca California. According to the inspector, a reason for this notice was based on no record of work orders for certain alarms in January 2008. Your group has requested we investigate the alarms the inspector questioned on the violation and report back explanations indicating why the alarms were not dispatched. Following is detailed information regarding the alarms questioned in the violation and what the FuelQuest Alarm Management Services (AMS) team did to resolve: January 4, 2008 at 2:13AM PST, site reports to FuelQuest Fuel and High Liquid Alarms for Sensors 1-6. At 2:34AM PST, our AMS team starts their triage of these alarms. This involves manually connecting to the ATG using Telnet to validate the alarm using the Veeder Root commands 110100, S0300 and then 110100 again. 110100 is a System Status command and shows any current active alarms. S0300 is known as an Alarm Reset command and when the Veeder Root unit receives this command it verifies if the alarm condition is still active, meaning the condition that caused the alarm is still present. Based on these commands, the Veeder Root displayed "ALL FUNCTIONS NORMAL" once the final System Status command was sent. The AMS team then documented in our FMS system the telnet session in the Notes field within the FMS application, placed RR (Remote Resolve) in our Reference ID field, and closed the alarm with no further action required per the established protocol. January 6, 2008 at 3:50AM PST, site reports to FuelQuest High Liquid Alarms for Sensors 1 & 3. At 4:08AM PST, our AMS team manually connected to the ATG using Telnet to validate the alarm using the Veeder Root commands 110100, S0300 and then 110100 again. Based on these commands, the Veeder Root displayed "ALL FUNCTIONS NORMAL" once the final System Status command was sent. The AMS team documented the telnet session in the Notes field within our FMS system, placed RR (Remote Resolve) in our Reference ID field, and closed the alarm with no further action required per the established protocol. At the time these alarms were triggered, our agreed to protocol stated that all P1 alarms were to be responded to within 1 hour of receiving the alarm. If the alarm condition was still present, then a ticket would need to be created in Clarify and the ticket number recorded in our system. It is our observation that the AMS team performed their role and function by handling these alarms within the guidelines of the established protocol at that time. Accompanying this letter is an Alarm History report from our FMS system showing the alarms and the corresponding notes that the AMS team documented. Per our Agreement, this document and accompanying report fulfills your request of investigation and explanation of how these alarms were handled. Yours S[�cerely� FUelQ s Inc.