|
| No owner wants to be told that their unique business opportunity already has a proven CRM solution so this fact is a trade secret. |
| Each unique business is just a different set of terminology imposed on our CRM framework. |
| "u" in the number system will be "3" to "8" for different user roles. |
| 1. Customer, Client, Delegate, Student, Business Associate, Supplier, Member, Vendor, Consignee, Company. |
| .1.1 Company may be a partner in a supply or value chain. |
| .1.2 Location, branch, site, office, department, area, place as optional address where business is conducted for the company. |
| .1.3 Person is optional in each location: business is done by people. |
| 2. Asset, Service, Product, Course, Vacation, Consignment, Scheme, Shipment as the objective of the business with prices, rates and fees. |
| .2.1 Feature of asset may include optional equipment, parts, services, packing, delivery, tax for a date range. |
| 3. Order, Booking, Contract, Reservation, Policy, Quotation, Invoice, Cover. |
| ..3.a Quotation is an initial state of the order. |
| ..3.b Invoice is an intermediate state of the order. |
| ..3.c Paid is a later state of the order. |
| .3.1 Detail of order may match each asset feature as order line items. |
| .3.2. Payment, Finance, Account, Money is the point of doing business. |
| 4. Request, Claim, Concern, Complaint, Customer Service Issue (for one order). |
| .4.1 Third Party, Plaintiff, Claimant, Complainant with their own lawyer, insurer, authority. |
| .4.2 Solution as optional plan of action for each party with possible compensation. |
| A business solution may involve more than one CRM structure. For example a sales order service will exist below the "Customer" structure and a purchase order service will exist below the "Supplier" structure. A "booking" is an order to bring together a customer with a supplier asset. |
| Every record has any number of associated notes or tasks. |
| Popup pages search begining for each record, and switch to the popup pages when drilling down the hiearchy: |
| u10x Customer. |
| u11x Customer Task. |
| u12x Location. |
| u13x Location Task. |
| u14x Person. |
| u15x Person Task. |
| u16x Asset. |
| u17x Asset Task. |
| u18x Feature. |
| u19x Feature Task. |
| u20x Order. |
| u21x Order Task. |
| u22x Detail. |
| u23x Detail Task. |
| u24x Payment. |
| u25x Payment Task. |
| u26x Claim (M). |
| u27x Claim Task. |
| u28x Claimant (T). |
| u29x Claimant Task. |
| Each record is independent so add and clone functions are not supported. |
| uxx1 xxxxx Popup (guide). |
| uxx2 xxxxx Search. |
| uxx3 xxxxx List. |
| uxx6 xxxxx Change. |
| uxx7 xxxxx Sheet. |
| uxx8 xxxxx History (layout). |
| Customer company, location and person may be logical records in the same customer table. All other records tend to have their ownn unique table. All task notes tend to share the same physical table as logical records. |
| Popup pages navigating down the hierarchy: |
| u30x Customer. |
| u31x Customer Task. |
| u32x Location. |
| u33x Location Task. |
| u34x Person. |
| u35x Person Task. |
| u36x Asset. |
| u37x Asset Task. |
| u38x Feature. |
| u39x Feature Task. |
| u40x Order. |
| u41x Order Task. |
| u42x Detail. |
| u43x Detail Task. |
| u44x Payment. |
| u45x Payment Task. |
| u46x Claim. |
| u47x Claim Task. |
| u48x Claimant. |
| u49x Claimant Task. |
| Hierarchical drill down of records with add and clone popup pages. |
| uxx3 xxxxx List. |
| uxx4 xxxxx Add. |
| uxx5 xxxxx Clone. |
| uxx6 xxxxx Change. |
| Scheme is an insurer (supplier) product (asset feature) with rates. Rates for a supplier asset will change and are (only) valid for a date range. |
| Tax is a government (supplier) product (asset feature) with rates. Rates for a tax will change and are valid for a date range. |
| Long page navigating down the hierarchy: |
| u50x Customer. |
| u51x Customer Task. |
| u52x Location. |
| u53x Location Task. |
| u54x Person. |
| u55x Person Task. |
| u56x Asset. |
| u57x Asset Task. |
| u58x Feature. |
| u59x Feature Task. |
| u60x Order. |
| u61x Order Task. |
| u62x Detail. |
| u63x Detail Task. |
| u64x Payment. |
| u65x Payment Task. |
| u66x Claim. |
| u67x Claim Task. |
| u68x Claimant. |
| u69x Claimant Task. |
| Hierarchical drill down of records with add and clone parts. |
| uxx3 xxxxx List. |
| uxx4 xxxxx Add. |
| uxx5 xxxxx Clone. |
uxx6 xxxxx Change.| 4.5.10 Motor Data Structure | | A simplified data model is employed with actual and future potential records. | | Every motor logical racord and physical table has a "M" prefix. |
| Key Assignment | | c01 is primary key. | | c02 is ACTive or INActive or DEFault. | | c03 is site code such as TRM for training motor. Every WLR record c03='ALL'. | | c04 is customer (MCU) as motor driver or policy holder. | | c05 is extra motor driver (MDR). | | c06 is zero and reserved for 3rd level customer contact names. | | c07 is zero and reserved for scheme identifier when multiple schemes are in use. | | c08 is asset as vehicle (MVE). | | c09 is policy (MPO). | | c10 is finance (MFI) and claim (MMC). | | c11 is claimant (MTC). | | c12 is note (M*N) as workflow. | | c13 is zero and reserved for note topic chain. |
| Key codes | | c01 means the primary key is replicated in this field as a unique identifier in the whole system. | | cnn where nn is 04 to 13 means the current key value is replicated in this field as part of a hierarchy. |
| Key Performance Indicators | | MCU-COUNT count customer MCU records. | | MDR-COUNT count driver MDR records in mcu1. | | MAS-COUNT count vehicle MAS records. | | MPO-COUNT count policy MPO records. | | MFI-COUNT count finance MFI records. | | MMC-COUNT count claim MMC records. | | MTC-COUNT count claimant MTC records. | | MCN-COUNT count customer notes MCN records in mwf1. | | MDN-COUNT count driver notes MDN records in mwf1. | | MVN-COUNT count vehicle notes MVN records in mwf1. | | MPN-COUNT count policy notes MPN records in mwf1. | | MFN-COUNT count finance notes MFN records in mwf1. | | MMN-COUNT count claim notes MMN records in mwf1. | | MTN-COUNT count claimant notes MTN records in mwf1. | | MPO-SUM sum value of policy MPO records. | | MFI-SUM sum value of finance MFI records. |
| WLR Data Structure for Motor App | | Code | Table | Purpose | 04 | 05 | 06 | 07 | 08 | 09 | 10 | 11 | 12 | | MSC | msc1 | scheme (S) | c01 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | MCU | mcu1 | customer (C) | c01 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | MCN | mwf1 | customer note | c04 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | c01 | | MDR | mcu1 | driver (D) | c04 | c01 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | MDN | mwf1 | driver note | c04 | c05 | 0 | 0 | 0 | 0 | 0 | 0 | c01 | | MAS | mas1 | asset (A) | c04 | 0 | 0 | 0 | c01 | 0 | 0 | 0 | 0 | | MAN | mwf1 | asset note | c04 | 0 | 0 | 0 | c08 | 0 | 0 | 0 | c01 | | MPO | mpo1 | policy order (P) | c04 | 0 | 0 | 0 | c08 | c01 | 0 | 0 | 0 | | MPN | mwf1 | policy note | c04 | 0 | 0 | 0 | c08 | c09 | 0 | 0 | c01 | | MFI | mfi1 | finance (F) | c04 | 0 | 0 | 0 | c08 | c09 | c01 | 0 | 0 | | MFN | mwf1 | finance note | c04 | 0 | 0 | 0 | c08 | c09 | c10 | 0 | c01 | | MMC | mmc1 | claim (M) | c04 | 0 | 0 | 0 | c08 | c09 | c01 | 0 | 0 | | MNN | mwf1 | claim note | c04 | 0 | 0 | 0 | c08 | c09 | c10 | 0 | c01 | | MTC | mtc1 | claimant (T) | c04 | 0 | 0 | 0 | c08 | c09 | c10 | c01 | 0 | | MTN | mwf1 | claimant note | c04 | 0 | 0 | 0 | c08 | c09 | c10 | 0 | c01 | | MTA | mtc1 | claimant authority | c04 | 0 | 0 | 0 | c08 | c09 | c10 | 0 | c01 | | MTS | mtc1 | claimant insurer | c04 | 0 | 0 | 0 | c08 | c09 | c10 | 0 | c01 | | MTW | mtc1 | claimant lawyer | c04 | 0 | 0 | 0 | c08 | c09 | c10 | 0 | c01 |
| Reserved for Motor App | | Code | Table | Purpose | 04 | 05 | 06 | 07 | 08 | 09 | 10 | 11 | 12 | | MUC | mcu1 | contact (U) | c04 | c05 | c01 | 0 | 0 | 0 | 0 | 0 | 0 | | MEQ | meq1 | equipment (E) | c04 | 0 | 0 | 0 | c08 | c01 | 0 | 0 | 0 | | MBA | mba1 | Broker Agr (B) | c04 | 0 | 0 | 0 | c08 | c09 | c01 | 0 | 0 |
|