Commit f5d76b28 authored by Eteri's avatar Eteri Committed by Klaus Wölfel

Few typos fixed in P-OSOE-Career.Assigment.007.en.html

parent 2edb89c0
...@@ -37,7 +37,7 @@ ...@@ -37,7 +37,7 @@
<h1>Persons in ERP5: staff, client, supplier</h1> <h1>Persons in ERP5: staff, client, supplier</h1>
<img title="Person: staff, client, supplier?" src="http://img.erp5.cn/osoe-Careers.And.Assignments.Person.Staff.Client.Supplier?format=png" alt="Person: staff, client, supplier?" type="image/png"> <img title="Person: staff, client, supplier?" src="http://img.erp5.cn/osoe-Careers.And.Assignments.Person.Staff.Client.Supplier?format=png" alt="Person: staff, client, supplier?" type="image/png">
<details open="open"> <details open="open">
<p>All people who have interaction with our company should to be entered in the ERP system based on different roles such as staff, clients, suppliers, etc. After a person has been created, he/she can be assigned with different duties, linked to different organisations, set relations to different functions. In this way, all people could be managed according to the company’s needs.</p><p>In our VIFIB case, the company VIFIB has staff (role "Internal") – engineers of software development, technicians who manage computer hardware and software, managers, accountants, administration and so on. VIFIB has clients (role "Client") who purchase hosting capacity for their own use or for retail through their own SlapOS platform, and clients who are software developers and need software certifications. VIFIB has suppliers (role "Supplier") who supply computer capacity and hosting space, and suppliers of software licenses and software integration service. VIFIB is also in relation with journalists (role 'Media'), and social insurance center (role "Administration").</p><p> <p>All people who have interaction with our company should be entered in the ERP system based on different roles such as staff, clients, suppliers, etc. After a person has been created, he/she can be assigned with different duties, linked to different organisations, set relations to different functions. In this way, all people could be managed according to the company’s needs.</p><p>In our VIFIB case, the company VIFIB has staff (role "Internal") – engineers of software development, technicians who manage computer hardware and software, managers, accountants, administration and so on. VIFIB has clients (role "Client") who purchase hosting capacity for their own use or for retail through their own SlapOS platform, and clients who are software developers and need software certifications. VIFIB has suppliers (role "Supplier") who supply computer capacity and hosting space, and suppliers of software licenses and software integration service. VIFIB is also in relation with journalists (role 'Media'), and social insurance center (role "Administration").</p><p>
In ERP5, there are two principles in identifying people. First, the role of a person should be differentiated among client, supplier, and stuff as shown in the graphics above. However, we should also be able to assign multiple roles to a person. For example, a VIFIB client who purchases large amounts of hosting capacity for retail use could also provide computer capacity to VIFIB through their SlapOS platform, thus becomes a VIFIB supplier. So this person is at the same time a client and a supplier <strong>(different roles in the same Person document)</strong> In ERP5, there are two principles in identifying people. First, the role of a person should be differentiated among client, supplier, and stuff as shown in the graphics above. However, we should also be able to assign multiple roles to a person. For example, a VIFIB client who purchases large amounts of hosting capacity for retail use could also provide computer capacity to VIFIB through their SlapOS platform, thus becomes a VIFIB supplier. So this person is at the same time a client and a supplier <strong>(different roles in the same Person document)</strong>
. Second, every person created must be unique. We should only create the same person once and be able to use it everywhere needed. If we create two Person documents for the same person (e.g.Person 1 Supplier and Person 1 Client), then the documents are redundant, and could lead to many confusions in using them. . Second, every person created must be unique. We should only create the same person once and be able to use it everywhere needed. If we create two Person documents for the same person (e.g.Person 1 Supplier and Person 1 Client), then the documents are redundant, and could lead to many confusions in using them.
</p> </p>
...@@ -52,7 +52,7 @@ ...@@ -52,7 +52,7 @@
<h1>People change organisations</h1> <h1>People change organisations</h1>
<img title="People change of organisations" alt="People change of organisations" src="http://img.erp5.cn/osoe-Careers.And.Assignments.People.Change.Of.Organisations?format=png" type="image/png"> <img title="People change of organisations" alt="People change of organisations" src="http://img.erp5.cn/osoe-Careers.And.Assignments.People.Change.Of.Organisations?format=png" type="image/png">
<details open="open"> <details open="open">
<p>In ERP5, a person can be represented by a Person document that linked to an Organisation document, but both entities are independent and have their own life cycle. A person can work for one or many organisations, or change organisations during his/her career. However, keep in mind that there is no need to create a new person, you should just update the existing one by creating a new career step.</p> <p>In ERP5, a person can be represented by a Person document and by an Organisation document he/she is linked to, but both entities are independent and have their own life cycle. A person can work for one or many organisations, or change organisations during his/her career. However, keep in mind that there is no need to create a new person, you should just update the existing one by creating a new career step.</p>
</details> </details>
</section><section class="illustration"> </section><section class="illustration">
<h1>Tracking a person's career</h1> <h1>Tracking a person's career</h1>
...@@ -64,10 +64,10 @@ ...@@ -64,10 +64,10 @@
<h1>Career workflow</h1> <h1>Career workflow</h1>
<img title="Career workflow" alt="Career workflow" src="http://img.erp5.cn/osoe-Careers.And.Assignments.Career.Workflow?format=png" type="image/png"> <img title="Career workflow" alt="Career workflow" src="http://img.erp5.cn/osoe-Careers.And.Assignments.Career.Workflow?format=png" type="image/png">
<details open="open"> <details open="open">
<p>We have a very simple work-flow for career steps. A career step can be started, cancelled, or stopped.</p> <p>We have a very simple workflow for career steps. A career step can be started, cancelled, or stopped.</p>
</details> </details>
</section><section class="illustration"> </section><section class="illustration">
<h1>Assign duties to Person</h1> <h1>Assign duties to a Person</h1>
<img title="People are assigned duties" alt="People are assigned duties" src="http://img.erp5.cn/osoe-Careers.And.Assignments.People.Are.Assigned.Duties?format=png" type="image/png"> <img title="People are assigned duties" alt="People are assigned duties" src="http://img.erp5.cn/osoe-Careers.And.Assignments.People.Are.Assigned.Duties?format=png" type="image/png">
<details open="open"> <details open="open">
<p>However, careers could only represent a person’s big career steps, but not the positions and responsibilities of the person in a given organisation. In ERP5, “assignments” are used to represent positions and duties of a person.</p><p>Assignments are completely independent from career steps. Firstly, a person could have multiple positions and a variety of duties in one career step. Secondly, the assignments could be very different from each other, and sometimes could even be far from the career step itself. For example, the financial manager of VIFIB might be assigned the duty of handling the director role for a short time when the company director is absent for business trips. Thirdly, assignments are not always related to the organisation that the person works for in a career step. For example, a software developer of VIFIB might be assigned the “project manager” position for a project from VIFIB’s client organisation for a defined period of time.</p> <p>However, careers could only represent a person’s big career steps, but not the positions and responsibilities of the person in a given organisation. In ERP5, “assignments” are used to represent positions and duties of a person.</p><p>Assignments are completely independent from career steps. Firstly, a person could have multiple positions and a variety of duties in one career step. Secondly, the assignments could be very different from each other, and sometimes could even be far from the career step itself. For example, the financial manager of VIFIB might be assigned the duty of handling the director role for a short time when the company director is absent for business trips. Thirdly, assignments are not always related to the organisation that the person works for in a career step. For example, a software developer of VIFIB might be assigned the “project manager” position for a project from VIFIB’s client organisation for a defined period of time.</p>
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment