| 1. Human Resource: | | 1. Human Resource Management (HRM) is about (1) People, (2) Companies and (3) Projects (contracts). | | 2. Every contact and Person is represented by a collection of information. | | 3. Every Company as customer or supplier is represented by a collection of information. | | 4. Every potential and actual project becomes a collection of information. The primary index to information is the project - most information is for a named project, but some information is for a company or person. | | 5. People do business with People - People represent their Company - People do business as a Project. | | 6. Project is a contract by a client Company who pays a supplier Company. | | 7. Project Managment is Contract Management in compliance with ISO 9001 Quality Management Standard (and PRINCE2). | | 8. Financial Accounts: | | (1). Every Person has their own private (expense) financial accounts. | | (2). Every Company has its own financial accounts. | | (3). Every Project has its own shared (client-supplier) financial accounts. | | 9. Rights: | | (1). Every Person has the right to manage their own Personal HR information. | | (2). A "supervisor" or "manager" Person may be granted the right to process their Project HR information. | | (3). A "manager" Person may be granted the right to manage their own Company HR information. | | 10. Every Person, Company and Project has its own unique information regarding: | | (1). Diary of Tasks. | | (2). HR information about People, Companies and Projects. | | (3). Assets including equipment, accounts and intellectual property (documents). |
| 2. Glossary: | | 1. "Human Resource" is information about a customers and suppliers, as companies and people doing business with projects or contacts. | | 2. "COMPANY": means CRM and CRM means company as customer, client and supplier. | | 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 shall be encrypted. | | 4. "PROJECT" is a potential or actual contract undertaken over one or many days involving one or many people. | | 5. "SITE": is a project, company or person as a collection of information. | | 6. Every site is a HR object as Person, Company or Project. | | 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. | | 8. "SUPPLY CHAIN" is where a large project is divided into many contracts where each contract has its own Client and Supplier; and where a Supplier of one contract may be the Client of another contract. Each contract is a project as far as the client-supplier relationship is concerned. |
| 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. | | Why: | | (1). Productive people use advanced digital tools with very high levels of automation. | | (2). Efficient companies employ productive people with advanced tools. | | (3). Stop employing people on minimum rates with minimum motivation and minimum productivity. Start employing very productive people who are highly motivated with good rates and advanced tools. Every three productive people are paid the same as five people on minimum rate - they do more and do it faster. Improve the tools and three productive people can be paid the same as six or eight people on minimum rate. | | (4). People are 99% of a company, everything else is . |
| 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 a contract represented by a wide range of optional information that may include: | | (1). Project: or site or contract as name and identifier . | | (2). Supplier: (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). Human Resource: as people involved. | | (7). Assets: as equipment and documents (emails). |
| 7. Site Information: | | (1) Person | | (1.1) Authentication | | (1.2) Payroll | | (1.3) Skill | | (1.4) Leave | | (1.5) Document (email) | | (1.6) Task (time sheet + HAV) | | (2) Company | | (2.1) Owner | | (2.2) Client | | (2.3) Supplier | | (3) Project (contract) | | (3.1) Address | | (3.2) Bank (credit check | | (3.3) Task (hole) |
| 8. Quality Management (QMS) | | 1. Every project, no matter how big or how small, is operated in full compliance with ISO 9001 Quality Mnagement Standard. | | 2. Quality Management can be identified by: | | (1) Plan what to do with a project RAMS with method statement. | | (2) Do what is planned with Daily Activity Briefings as a mini or partial RAMS. | | (3) Check (study and analyse) the plan and the actual results to identify issues that could be done better. | | (4) Act with the benefit of hindsight to refine the project RAMS so the next project RAMS is more complete and correct. | | 3. A benefit of quality management is continual improvements to project RAMS so the next project RAMS is more accurate that previous RAMS. In this context, the project RAMS is the project quotation and project contract, including cost estimates for hired assets, manpower and supplies. The project financial accounts will identfy variances between what was planned and actual costs. | | 4. Quality Management is used to measure: | | (1) Manpower cost, time and quality, including incidential expenses. | | (2) Assets as hired equipment cost, time and quality. | | (3) Supplies as procurred goods cost, time and quality. | | 5. The construction business has a mission to build people who build tools that build buildings - QMS is part of building people with the right tools to do the job in an ever improving way. KAZEN means iteration with ever increasing levels of knowledge based on actual experience to exceed all other methods of working. | | 6. It is suggested that in the long-term, a large number of tiny improvements will always outperform massive innovation - never innovate, just continually improve. |
| 9, Privacy Policy: | | PSEUDONYMISE Policy means the names of people, projects and companies are never stored in a record. All names must be defined to the application and selected from a list so only a token is stored as data in a task. All names are encrypted and replicated in a way that they can be represented by an abstract token. | | 1. B28 Every task is by date (22) and by site (03). | | 2. B25 Personal task is also be key (13). | | 3. B28 Excavation cost calculation shown as message (64) with amount (25). | | 4. B25 Time sheet hours and cost calculation shown as message (64) with amount (25). |
| x, Architecture: | | 1. All three HR objects must have a unique primary key because all three have their own site, diary, HR and asset information. | | 2. B22 means the HR object that contains information about People, Companies and Projects as three different types of record. | | 3. When a new person, company or project is added, a new unique primary key is created that acts to partition associated diary, HR and asset data using site c03. Every HR record has one and only one site key in c03 - that used by the author at the time the HR record was created. | | 4. B22 may be said to be multi-tenancy, where one tenant with a unique site c03 is not granted access to data with any other site c03 value. | | How to add new HR data: | | (1). People are paid by a Company, so the Company must be added before that Company is selected and People added as dependent on that Company. | | (2). Project is paid by a Company, so the Company must be added before that Company is selected and Project added as dependent on that Company. | | (3). A Project will pay a Company (contrator) so the Company must be added before that Company can be selected as being paid by the Project. | | (4). Every Company has their own unique HR data including their own set of Companies - select the owning company site before adding a dependent company. |
| Document Control. | | 1. Document Title: Human Resource. | | 2. Description: Human Resource. | | 3. Keywords: Human Resource. | | 4. Privacy: Shared with approved people for the benefit of humanity. | | 5. Edition: 1.1. | | 6. Issued: 2 Jan 2018. |
|
|