| 1. Customer Relationship: | | 1. Customer Relationship Management (Customer Relationship) is about companies, projects and people. | | 2. Every potential and actual project becomes a collection of information. | | 3. Every contact and person is represented by a collection of information. | | 4. Every company as customer or supplier is represented by a collection of information. | | 5. The primary index to information is the project - most information is for a named project, but some information is for head office. |
| 2. Glossary: | | 1. "Customer Relationship" is information about a customers and suppliers, as companies and people. | | 2. "COMPANY": means CRM and CMR means company. | | 3. "PERSON": includes own staff, contractors, sub-contractors, client staff and everybody involved on a project. The existance and use of a persons name is subject to strict legal privacy and security controls - all names must be encrypted. | | 4. "PROJECT" is a potential or actual job of work undertaken over one or many days involving one or many people. | | 5. "SITE": is a large project where the amount of work involved can be fragmented into a number of projects. | | 6. Every site is a project but not every project is big enough to be a site. | | 7. Every site has its own unique task diary, CRM and asset register. A project may have shared task diary, shared CRM and shared asset register. |
| 3. Naming Conventions: | | 1. Every person must have a unique name and an assigned identifier. Where two people have identical names, a way must be devised to represent each person with a unique name. | | 2. A person may also have a "known as" name as a handle or nickname for ease of use. | | 3. Every company must have a unique legal name and an assigned identifier - use Companies House . | | 4. A company may also have a "trading" name or initials for ease of use. | | 5. Every project must have a unique given name and an assigned identifier. |
| 4. People: | | 1. Each person is represented by a wide range of optional information that may include: | | (1). Myself: as pseudonymised name and identifiers. | | (2). Address: as home or work. | | (3). Friends: as next of kin, spouse, children and others. | | (4). Bank: for transfer payments to the person. | | (5). Payroll: as mandated by HMRC by day, week, month, year. | | (6). Company: as employment history of projects completed. | | (7). Skill: as qualifications, courses, clearances, licenses, achievements, etc.. | | (8). Device: as computing device used. Assets such as vehicle or equipment responsibility. | | (10). Time: as daily hours worked evidence. | | (11). HAVS: as daily vibration evidence. |
| 5. Company: | | 1. Each company is represented by a wide range of optional information that may include: | | (1). Company: as legal name and identifiers. | | (2). Address: as each office or place of work or location. | | (3). Owner: as ownership history. | | (4). Bank: for transfer payments to the company. | | (5). Payroll: as mandated by HMRC by day, week, month, year. | | (6). Projects: as history of projects completed or services provided. |
| 6. Project: | | 1. Each project is represented by a wide range of optional information that may include: | | (1). Project: or site as name and identifier . | | (2). Owner: (pay to) as identifier of contractor or supplier. | | (3). Client: (paid by) as identifier of client or customer. | | (4). Address: as identifier of project site office. | | (5). Task Diary: as everything that happened or will happen. | | (6). Customer Relationship: as people involved. | | (7). Assets: as equipment and documents (emails). |
| CRM Information: | | 1. CRM as HRM information consists of a common parent with a large number of optional children. | | 2. Some children have one occurance as a form like payroll while other children have a list like leave |
| Document Control. | | 1. Document Title: Customer Relationship. | | 2. Description: Customer Relationship. | | 3. Keywords: Customer Relationship. | | 4. Privacy: Shared with approved people for the benefit of humanity. | | 5. Edition: 1.1. | | 6. Issued: 2 Jan 2018. |
|
|