Version: 10.2.1c and 10.2.1c SP3 |
Responder Overview > TroubleMaker Overview > Create Historical Database |
TroubleMaker requires a database from which it submits customer calls to Responder. Use the sample database called TroubleMakerData.mdb, which is installed with TroubleMaker in Program Files\Miner and Miner\Responder\TroubleMaker\.
TroubleMakerData.mdb contains all of the fields required by TroubleMaker to execute scenarios. This database contains the tables listed on this page. These tables along with their fields are described below.
You can also create new databases directly from the Generate TM Data From Archive tab. |
TmCalls Table
All of the following fields must exist in the TmCalls table. Scenario, CallID, LastName, FirstName, Account, Telephone, and TroubleAtAccount must contain values. If a record contains a No value in the TroubleAtAccount field, it will be submitted to Responder, but no incident will be created for it. The SetTroubleAtAccount query in TroubleMaker Scenario.mdb provides an easy method for assigning Yes to the TroubleAtAccount field for all records.
Field
Description
Scenario
Records may be separated into different scenarios using different scenario numbers. This field is a primary key and a foreign key to the TmScenario table.
CallId
A unique number within the scenario that identifies the call. It also determines the order in which the calls are submitted. This field is a primary key.
RegionCode
Indicates the region in which the incident resides.
CriticalCode
A numeric value that corresponds to the critical status of the incident. 0=not critical; 1=critical
CauseCode
A numeric value that corresponds to the cause of the incident.
TroubleCode
A numeric value that corresponds to the trouble type for the incident.
DeviceFcid
Feature class ID for the incident device.
DeviceOid
Object ID for the incident device.
Account
The customer's account number. If this field is blank, TroubleMaker will use the FirstName, LastName, and Telephone fields to query Responder to locate the account number.
LastName
Customer's last name.
FirstName
Customer's first name.
Telephone
Customer's telephone number.
TroubleAtAccount
Indicates whether the trouble reported occurs at the customer's location. Yes/No
CallBackRequested
Indicates whether the customer wants a return call. Yes/No
CallbackPowerNotRestored
Yes/No value indicating whether callback customer indicates that the power has been restored.
Remarks
Any remarks associated with the incident.
Hazard1Type
Type of a hazard associated with the incident
Hazard1OnSite
Yes/No value indicating whether a public safety official has arrived on the hazard site.
Hazard2Type
Type of a second hazard associated with the incident
Hazard2OnSite
Yes/No value indicating whether a public safety official has arrived on the hazard site.
CallTaker
The name of the customer service representative who fielded the customer call.
TimeReceived
The time the call was originally received.
SubmitOrder
A numeric value indicating the random order in which to submit calls.
TmScenarios
All of the following fields must exist in the TmScenarios table.
Field
Description
Scenario
A unique number identifying the scenario. This field is a primary key.
Name
A description for the scenario.
Device Facility ID
The Facility ID of the outage device.
Device Type
The Type of the outage device.
DeviceFcid
Feature class ID for the incident device.
DeviceOid
Object ID for the incident device.
Customers Affected
The number of customers affected by the outage.
NumberCalls
The number of customers that called in the scenario.
NumberHazards
The number of hazards in the scenario.
Comments
Comments about the outage.