mirror of
https://github.com/Karaka-Management/Organization-Guide.git
synced 2026-01-10 20:48:39 +00:00
remove whitespace
This commit is contained in:
parent
fd535a1b27
commit
b17bd20351
6
.github/issue_template.md
vendored
6
.github/issue_template.md
vendored
|
|
@ -1,15 +1,9 @@
|
|||
### Expected behavior
|
||||
|
||||
|
||||
|
||||
### Actual behavior
|
||||
|
||||
|
||||
|
||||
### Steps to reproduce the behavior
|
||||
|
||||
|
||||
|
||||
### Importance
|
||||
|
||||
- [ ] Application breaking
|
||||
|
|
|
|||
|
|
@ -25,7 +25,4 @@
|
|||
* Forms
|
||||
* Forms to be used for certain organization activities
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -14,4 +14,3 @@ THE SOFTWARE.
|
|||
|
||||
BY CONTRIBUTING YOU AUTOMATICALLY ACCEPT THE INDIVIDUAL CONTRIBUTOR LICENSE
|
||||
AGREEMENT 1.0 ("CLA") INCLUDED IN THIS REPOSITORY.
|
||||
|
||||
|
|
|
|||
|
|
@ -47,4 +47,3 @@ Unless required by applicable law or agreed to in writing, Licensor provides the
|
|||
7. Limitation of Liability
|
||||
|
||||
In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
|
||||
|
||||
|
|
|
|||
|
|
@ -39,7 +39,6 @@ In particular, personal data is used as follows:
|
|||
* If you make use of the possibility to send inquiries to us by means of our contact form, we will ask You for your name and e-mail address. Furthermore, you can enter Your individual message to Us in the message field.
|
||||
* Some SERVICES allow You to provide optional personal data such as Your name, address etc. If You choose to provide these information they will be stored by Us for the sole purpose of using them in Our SERVICES and internal statistics.
|
||||
|
||||
|
||||
## Cookies
|
||||
|
||||
Cookies are unique identifies that we transfer to Your DEVICE to enable Our systems to recognize Your device and to provide some of our SERVICES and WEBSITE functionality.
|
||||
|
|
|
|||
|
|
@ -34,6 +34,4 @@ When value-in-use calculations are undertaken, management has to estimate the ex
|
|||
|
||||
Work in progress is measured at the production costs considering a loss-free valuation. The production costs include the minimum components as prescribed under section 255 (2) HGB and mainly relate to personnel expenses and expenses for external services.
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
|
|
|||
|
|
@ -2,6 +2,4 @@
|
|||
|
||||
Cash and cash equivalents in the statement of financial position comprise cash at banks, cash on hand and short-term deposits with an original maturity of three months or less.
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
|
|
|||
|
|
@ -3,6 +3,4 @@
|
|||
Generally, assets and liabilities in a foreign currency are translated with the mid spot exchange rate at the balance sheet date. For items with a remaining life of more than one year, the realization principle
|
||||
according to section 252 (1) No. 4 sentence 2 HGB and the historical cost principle according to section 253 (1) sentence 1 HGB have been applied. In the profit and loss account, information regarding the foreign currency effects is presented separately in the other operating income and the other operating expenses. This contains realized and unrealized effects.
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
|
|
|||
|
|
@ -14,7 +14,4 @@ The account system follows SKR 03 (Standardkontenrahmen).
|
|||
|
||||
New real accounts, cost centers and cost objects can only be created by the head of finance, head of controlling or head of accounting. Additionally, automated workflows may also generate real accounts, cost centers and cost objects. Examples for such automated workflows can be updates to the account system, creation of new departments etc.
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -4,6 +4,4 @@
|
|||
|
||||
Trade payables are obligations to pay for goods or services that have been acquired in the ordinary course of business from suppliers. Trade payables are classified as current liabilities if payment is due within one year or less (or in the normal operating cycle of the business if longer). If not, they are presented as non-current liabilities. Trade payables are recognized initially at fair value and subsequently measured at amortized cost using the effective interest method.
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
|
@ -8,6 +8,4 @@ Receivables and other assets are stated at their nominal value. All items subjec
|
|||
|
||||
Other long-term receivables are generally recognized at nominal value. Impairments are recorded, if write-downs are required. A reversal of impairment losses is recognized when there is an indication that the reasons for write-downs recognized in previous years are no longer present.
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
|
|
|||
|
|
@ -58,8 +58,4 @@ $$
|
|||
ROA = \frac{Net Income}{Total Assets}
|
||||
$$
|
||||
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -16,7 +16,4 @@ Revenues, expenses and assets are recognized net of the amount of sales tax, exc
|
|||
* in the case of receivables and payables that are stated with the amount of sales tax included The net amount of sales tax recoverable from, or payable to, the taxation authority is included as part of
|
||||
receivables or payables in the statement of financial position.
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -42,6 +42,4 @@ All drivers are responsible for their traffic violations. This includes also bei
|
|||
|
||||
The car must be returned in good condition by the end of the lease term or if the employment at the organization ends. Gross negligence including repairs for unreported damages must be paid by the employee.
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
|
|
|||
|
|
@ -44,4 +44,3 @@ This Code of Conduct is adapted from the [Contributor Covenant][homepage], versi
|
|||
|
||||
[homepage]: http://contributor-covenant.org
|
||||
[version]: http://contributor-covenant.org/version/1/4/
|
||||
|
||||
|
|
|
|||
|
|
@ -48,6 +48,4 @@ Disrespecting this policy possibly leads to a warning and potentially excluding
|
|||
|
||||
This policy is binding even after separation.
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
|
|
|||
|
|
@ -32,6 +32,4 @@ All conflicts of interest will be resolved as fairly as possible. Senior organiz
|
|||
|
||||
Disrespecting this policy possibly leads to a warning and potentially excluding the involved person from any further activities of the organization. Depending on the severeness legal actions may follow.
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
|
|
|||
|
|
@ -2,6 +2,4 @@
|
|||
|
||||
The developer and development guidelines are published in a separate documentation called the [Developer-Guide](https://github.com/Karaka-Management/Developer-Guide). The reason for this is that also clients and third parties can modify the source code or create extensions. This documentation contains a vast amount of information which helps to understand the code structure, code standards etc.
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
|
|
|||
|
|
@ -105,6 +105,4 @@ This document and the information contained herein is provided on an “AS IS”
|
|||
|
||||
The date time format in all documents must follow the [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) standardization: `YYYY-MM-DD` or `YYYY-MM-DD HH:MM:SS` (sometimes written as `YYYY-MM-DD h:i:s`).
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
|
|
|||
|
|
@ -52,6 +52,4 @@ The data reconstruction is documented in a reconstruction tutorial in the IT pro
|
|||
|
||||
The responsibility for the data backup lies with the head of IT. Other IT employees may only take over these tasks if the head of IT considers these employees sufficiently trained in this area. The responsible employees must control the data integrity of the backups once a quarter.
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
|
|
|||
|
|
@ -43,4 +43,3 @@ Potential documents to be changed are:
|
|||
The responsibility for the data backup lies with the head of IT. Other IT employees may only take over these tasks if the head of IT considers these employees sufficiently trained in this area. The responsible employees must ensure the appropriatness of the changes and authorization.
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -34,4 +34,3 @@ Logging must be always enabled for errors and warnings. Additional logging can b
|
|||
The responsibility for the database lies with the head of IT. No other employee may directly interact witht the database except for backups and restarting the database in case of failures.
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -62,4 +62,3 @@ IT support can be requested through the support portal (e..g faulty hardware) an
|
|||
Every employee is responsible for following this guideline.
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -71,4 +71,3 @@ Security software which must be used on the main server are:
|
|||
The responsibility for the IT security lies with the head of IT. Other IT employees may only take over these tasks if the head of IT considers these employees sufficiently trained in this area.
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -31,7 +31,4 @@ graph TD;
|
|||
SWITCH_PRIVATE---LOCAL_BACKUP_SERVER[Local backup server];
|
||||
```
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -51,4 +51,3 @@ All jobs must be logged and monitored to ensure their correct operations. In cas
|
|||
The overall responsibility for the IT operations lies with the head of IT. However, every IT employee is responsible within their area of work for upholding the IT guidelines and policies as well as a smooth operation of the IT.
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -10,6 +10,4 @@ Members should not spend more than 40 hours per week on the organization as we b
|
|||
|
||||
Extremely few or insignificant contributions may lead to the exclusion from the organization based on judgmental basis by a senior member. A member can expect to receive a warning in advance in order to provide the chance to increase the activity or provide reasons for the past activities.
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
|
@ -20,6 +20,4 @@ Our goal is to provide products and services at the highest quality to make our
|
|||
|
||||
Disrespecting this policy possibly leads to a warning and potentially excluding the involved person from any further activities of the organization. Depending on the severeness legal actions may follow.
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
|
|
|||
|
|
@ -106,7 +106,6 @@ Possible resources for checking tariff numbers are "Warenverzeichnis für die Au
|
|||
|
||||
## Sanction checks
|
||||
|
||||
|
||||
## Annex
|
||||
|
||||
"Export" means any cross-border transfer from Germany to other countries - also to other EC Member States - including non-tangible transfer by means of electronic media (cf. Art.2 No.2 iii Dual-Use Regulation) as well as including short-term exports (e.g. for trade fairs). Exports in the sense of these organizational instructions are also deemed to be exports if SDG does not act on its own behalf but, for example, on behalf of another domestic or foreign company in the SDG group. The inspection and action obligations set out in these organizational instructions also apply to such exports.
|
||||
|
|
|
|||
|
|
@ -61,6 +61,4 @@ Entertainment expenses are calculated per day and are only paid if they are real
|
|||
| ---------------------------- | ----------- | -------------------- | ----------- |
|
||||
| per business partner per day | 50.00 EUR | 120.00 EUR | 200.00 EUR |
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
|
|
|||
|
|
@ -62,8 +62,4 @@ graph TD;
|
|||
REPORT-->TAKE_MEASURES([EC: Take measures]);
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
|
|
|||
|
|
@ -127,8 +127,6 @@ The name of the branch can be chosen freely however it is recommended to follow
|
|||
merge develop
|
||||
```
|
||||
|
||||
|
||||
|
||||
The senior developer who performs the code review merges the change request into the `develop` branch after their successful code review. Unsuccessful reviews lead to change requests by the original developer, other developers who can make the requested changes, changes by the senior developer who performed the review, or dismissal of the changed code. (**R10**)
|
||||
|
||||
## Approved dependencies
|
||||
|
|
@ -148,4 +146,3 @@ Developers may only rely on the dependencies defined in [IT Equipment & Software
|
|||
* [Tutorials](./Development/Tutorials)
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -29,6 +29,4 @@
|
|||
|
||||
* EY: Efficient
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
|
|
|||
|
|
@ -85,6 +85,4 @@ The IT system is performing a credit score check, a sanction check and a VAT ID
|
|||
|
||||
Once a day every supplier is automatically checked against sanction lists. (**R17**)
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
|
|
|||
|
|
@ -36,6 +36,4 @@
|
|||
|
||||
* EY: Efficient
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
|
|
|||
|
|
@ -165,6 +165,4 @@ The organization occasionally purchases contact addresses (email & mail addresse
|
|||
|
||||
The organization occasionally visits events where it holds presentations with various topics. Additionally, the organization sometimes has a booth at trade fairs, seminars etc. where it presents their products.
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
|
|
|||
|
|
@ -43,6 +43,4 @@
|
|||
|
||||
* EY: Efficient
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
|
|
|||
|
|
@ -88,7 +88,4 @@ All customer support requests must be documented as customer tickets in the IT s
|
|||
|
||||
Every closed support ticked gets followed up with a automatic email which asks the customer to rate his satisfaction with the support. (**R16**)
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -36,7 +36,4 @@
|
|||
|
||||
* EY: Efficient
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -174,7 +174,4 @@ Every employee is checked automatically every night against sanctions lists in t
|
|||
|
||||
* [Onboarding Does and Donts](./HR/Hiring/Onboarding/Onboarding%20Does%20and%20Donts.md)
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -28,7 +28,4 @@ graph TD;
|
|||
SIGN_CONTRACT-->TRAIN([Department: Train employee])
|
||||
```
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -52,6 +52,4 @@
|
|||
|
||||
* EY: Efficient
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
|
|
|||
|
|
@ -140,7 +140,4 @@ The deadline is the 5th work day of the following month.
|
|||
|
||||
The tasks and responsibilities can be found in the [Monthly Reporting Checklist](./Finance/Reporting/Monthly%20Reporting%20Checklist.md). The checklist must be signed by every responsible person after completing the defined task. (**R10**)
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -119,6 +119,4 @@ gantt
|
|||
Submit KPI to HOD : des17, 2022-08-05, 1h
|
||||
```
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0firefod
|
||||
|
|
|
|||
|
|
@ -13,7 +13,6 @@
|
|||
| 9 | CFO | Operational Risk (Finance) | The annual financial audit tasks are not well defined. | 1 | 1 | | | | An audit checklist exists defining the responsibilities. | 1 | 1 | | | yes | yes | |
|
||||
| 10 | CFO | Operational Risk (Finance) | The reporting tasks are not well defined. | 1 | 1 | | | | A reporting checklist exists defining the responsibilities. | 1 | 1 | | | yes | yes | |
|
||||
|
||||
|
||||
## Abbreviations
|
||||
|
||||
* R: Responsible
|
||||
|
|
@ -30,6 +29,4 @@
|
|||
|
||||
* EY: Efficient
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0firefod
|
||||
|
|
|
|||
|
|
@ -51,7 +51,4 @@ The following controlling instruments are implemented (**R6**).
|
|||
|
||||
From the controlling activities optimizations arise which can be brought forward by anyone in [meetings](./Management/Information%20Flow.md) and changes can be made to the processes by the responsible persons defined in the [Document Owners](./Document%20Owners.md).
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,4 @@ graph TD;
|
|||
OPTIMIZE-->PLAN
|
||||
```
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -25,7 +25,4 @@
|
|||
|
||||
* EY: Efficient
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -38,7 +38,4 @@ The quality management department can improve some of the *deficiencies* by them
|
|||
|
||||
The quality management department is responsible for ensuring the correctness, completeness and overall quality of the process documentation as well as the related documents. For this reason the quality management department has to check these documents once a year and ensure that all documents have the necessary approvals, are still up-to-date, correct and complete. The basis for this check is the [Document Owners](./Document%20Owners.md) list. (**R3**)
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -17,4 +17,3 @@ graph TD;
|
|||
DOCUMENT_OWNER_CHANGES([Owner: Draft document change])-->APPROVAL[Owner: Approval acc. to Document Owners list];
|
||||
APPROVAL-->UPDATE([DQM: Replace old document with new version]);
|
||||
```
|
||||
|
||||
|
|
|
|||
|
|
@ -22,7 +22,4 @@
|
|||
|
||||
* EY: Efficient
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -35,7 +35,4 @@ New software or software updates must be tested by the IT team in a sandbox envi
|
|||
|
||||
The IT Security policy defines additional best practices and guidelines how to handle IT security.
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -49,7 +49,4 @@ graph TD;
|
|||
VALIDATE_TEST--Yes-->MIGRATE[IT: Migrate change to live];
|
||||
```
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -26,6 +26,4 @@
|
|||
|
||||
* EY: Efficient
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
|
@ -64,6 +64,4 @@ This creates a pull request which is a request to put your code changes into the
|
|||
|
||||
Please note that your code changes may not get accepted if they don't uphold the coding standards mentioned in the developer guide or if the code changes don't fit the goal of the code base.
|
||||
|
||||
|
||||
|
||||
2021-01-01 - Version 1.0
|
||||
|
|
@ -12,7 +12,4 @@
|
|||
| Full income statement | CFO + CEO | CEO + executive staff members | | |
|
||||
| Overall responsibility | CEO + CFO | | | |
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -32,6 +32,4 @@ Name:
|
|||
|
||||
Signature:
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
|
@ -45,7 +45,4 @@
|
|||
| Audit report e.g. taxes (if available) | | | |
|
||||
| Overall responsibility | Head of Finance + CFO | | |
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -5,7 +5,4 @@
|
|||
| Define audit schedule with auditors | Head of Finance | | |
|
||||
| | | | |
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -19,4 +19,3 @@
|
|||
| Submit reporting | | | |
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -21,7 +21,4 @@
|
|||
| Status update on key projects and tasks | CTO + CFO | | | |
|
||||
| Explanation for sales and costs (provided by head of departments) | CFO | | | |
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,4 @@
|
|||
| 3 | The company appreciates my work. | | | | | |
|
||||
| 4 | The company is sucessfull. | | | | | |
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -25,7 +25,4 @@ Name:
|
|||
|
||||
....
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -28,7 +28,4 @@ Name:
|
|||
|
||||
....
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -1,16 +1,11 @@
|
|||
# Default Rejection
|
||||
|
||||
|
||||
|
||||
Dear {NAME}
|
||||
|
||||
We appreciate your interest in our organization and the position of {POSITION} for which you applied. After reviewing the application, yours was not selected for further consideration.
|
||||
|
||||
The selection committee appreciates the time you invested in your application and we wish you best of lock for your future endeavors.
|
||||
|
||||
|
||||
|
||||
Best regards,
|
||||
|
||||
{HR_EMPLOYEE_NAME}
|
||||
|
||||
|
|
|
|||
|
|
@ -13,7 +13,4 @@
|
|||
|
||||
> Positions can be empty (except the search approval) and to be defined (TBD) by HR.
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,4 @@
|
|||
| Car is taken care of | | Fleet manager | |
|
||||
| Training plan is taken care of | | Head of HR | |
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -48,6 +48,4 @@ This Agreement shall be governed exclusively by German law. The courts of Hessen
|
|||
|
||||
This agreement constitutes the entire agreement and supersedes all prior or contemporaneous oral or written agreements concerning such Contribution. This agreement may only be changed by mutual agreement of authorized representatives of the parties in writing. You agree to notify the Company of any facts or circumstances of which you become aware that would make these representations inaccurate in any respect.
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
|
|
|||
|
|
@ -1,2 +1 @@
|
|||
# Employment Contract
|
||||
|
||||
|
|
|
|||
|
|
@ -32,7 +32,4 @@ js: Jasmine
|
|||
* run phpcs: `php vendor/bin/phpcs ./ --standard="Build/Config/phpcs.xml" -s --report-junit=Build/test/junit_phpcs.xml`
|
||||
* run eslint: `npx eslint jsOMS/ -c Build/Config/.eslintrc.json`
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -61,7 +61,4 @@ Yes, although only very few libraries. They can be found in Resources/ and Libra
|
|||
* eslint: Build repository
|
||||
* PHPUnit: respective repository
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -35,6 +35,4 @@
|
|||
* Jug
|
||||
* Glass
|
||||
|
||||
|
||||
|
||||
*\*All prices in net*
|
||||
|
|
@ -8,7 +8,6 @@
|
|||
| Explain DO'S and DON'TS | HR | | |
|
||||
| Introduction to team | Head of department | | |
|
||||
|
||||
|
||||
## Development sepecifc
|
||||
|
||||
| Topic | Date | By | Done |
|
||||
|
|
@ -22,7 +21,4 @@
|
|||
| Q&A about the code base, application design, etc. | Department | | |
|
||||
| Handover of some basic issues/tasks/todos | Department | | |
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -15,7 +15,4 @@
|
|||
1. Don't be late to appointments. It can happen but it shouldn't be a normal occurrence
|
||||
2. Don't represent the project and organization in a bad light
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -14,6 +14,4 @@
|
|||
| Company presentation | | HR |
|
||||
| Training of company processes, guidelines and quality management aspects | | HR & QM |
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,5 @@
|
|||
# Automated Jobs
|
||||
|
||||
|
||||
|
||||
| Type / Description | Interval | Start | Comment |
|
||||
| ----------------------------------- | -------- | ----- | ------------------------------ |
|
||||
| Backup to NAS | Daily | 02:00 | |
|
||||
|
|
@ -11,7 +9,4 @@
|
|||
| Push master branch to remote server | Daily | 03:00 | |
|
||||
| Demo application setup | Daily | 03:00 | |
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -61,7 +61,4 @@
|
|||
| Intrusion prevention system | fail2ban |
|
||||
| Intrusion detection/prevention system | snort |
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -33,7 +33,4 @@ The following list only contains user permissions of A, OS, DB, N, O which are r
|
|||
* DB: DBMS
|
||||
* N: Network
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,4 @@ Before buying/implementing a new software the following aspects must be checked:
|
|||
| Estimated ROI in years | | Investment Form | ||
|
||||
| Opinion project manager | | See above | ||
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,3 @@
|
|||
# Third Party Software Validation - Update
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,5 @@
|
|||
# Interdependency
|
||||
|
||||
|
||||
| | Development | Purchase | Sales | Management | Support & Service | Quality Management | IT | Finance | HR | Marketing |
|
||||
| - | - | - | - | - | - | - | - | - | - | - |
|
||||
| Development | | | | | | |x||||
|
||||
|
|
|
|||
|
|
@ -60,4 +60,3 @@
|
|||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -85,7 +85,4 @@ The decision why Karaka decided to use PHP came down to the following points:
|
|||
7. Further implement basic modules (news, profile, wiki, kanban, Q&A, calendar, messaging)
|
||||
8. Create new design
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -60,7 +60,4 @@ None
|
|||
|
||||
None
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -101,7 +101,4 @@ None
|
|||
|
||||
None
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,4 @@ flowchart TD;
|
|||
|
||||
```
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -60,7 +60,4 @@
|
|||
|
||||
* Own organization size/workload. A large amount of modules and tools are required to reach the critical size to make a product which is beneficial for a large amount of organizations and businesses
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -33,4 +33,3 @@ Posting interval: > 1 a month
|
|||
## Google
|
||||
|
||||
Link:
|
||||
|
||||
|
|
|
|||
|
|
@ -76,7 +76,4 @@ flowchart TD;
|
|||
|
||||
Additional responsibilities are defined in the respective process documentation, [Document Owners](./Document%20Owner.md) and individual employee contracts.
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -23,4 +23,3 @@ flowchart TD;
|
|||
```
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -28,7 +28,4 @@ Employee: YOUR_NAME
|
|||
|
||||
Signature:
|
||||
|
||||
|
||||
|
||||
2021-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -30,7 +30,4 @@
|
|||
|
||||
Consider to update the [Approved Customer Software](../Support/Approved%20Customer%20Software.md) when changing this table.
|
||||
|
||||
|
||||
|
||||
2021-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -68,10 +68,6 @@ The risk management is implemented with reasonable amounts of human resources, l
|
|||
|
||||
## Summary
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
NAME, LAST NAME
|
||||
|
||||
2022-12-31
|
||||
|
|
|
|||
|
|
@ -45,7 +45,6 @@ The following four-steps represent the management process
|
|||
|
||||
The intent of risk identification is to answer the question “What can go wrong?” by:
|
||||
|
||||
|
||||
* Looking at current and proposed staffing, processes, suppliers, products, resources, dependencies, etc.
|
||||
* Reviewing potential shortfalls against expectations
|
||||
* Analyzing negative trends
|
||||
|
|
@ -66,7 +65,6 @@ Risk identification is the activity that examines each element of the company to
|
|||
|
||||
Risk analysis answers the question “What are the likelihood and consequence of the risk?” and “How high is the risk?”. The following tasks are part of the risk analysis:
|
||||
|
||||
|
||||
* Estimate the likelihood the risk event will occur
|
||||
* Estimate the possible consequence in terms of cost, schedule and performance
|
||||
* Determine the resulting risk level and prioritize for mitigation
|
||||
|
|
@ -85,7 +83,6 @@ Risk likelihood is the evaluated probability an event will occur given existing
|
|||
| 2 | Low Likelihood | \> 20% ≤ 40% |
|
||||
| 1 | Not Likely | \> 0% ≤ 20% |
|
||||
|
||||
|
||||
The initial assessment of probability of occurrence needs to be considered in combination with consequences, should the event be realized, and also the effectiveness of mitigation actions when making decisions on whether a given probability level is too high and would preclude proceeding on a planned course of action. Depending on the circumstances, there may be cases in which a risk (probability and consequence) is high enough to change course, in the absence of assured mitigation.
|
||||
|
||||
While dealing with individual risks, decision makers should understand the overall risk exposure of the company and the threat that cumulative or compounding effects of multiple risks pose to successfully satisfying business objectives. Multiple risks may expose the company to a greater risk than any individual risk due to complexity, stretched resources, risk interactions, or the aggregate likelihood of the risk realization.
|
||||
|
|
@ -153,7 +150,4 @@ The Risk Management System needs to be reviewed on a regular basis in terms of e
|
|||
|
||||
**Company:** The review is performed annually.
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,4 @@
|
|||
| Documents audited | |
|
||||
| Remarks | |
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,4 @@
|
|||
| Is the Whistleblower System working according to design? | | |
|
||||
| Check if the annual internal quality management audit was performed | | |
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,5 @@
|
|||
|
||||
|
||||
|
||||
|
||||
## Authorization Table
|
||||
|
||||
| Name / Category | Authorization | Customization | Software & Data | Support |
|
||||
|
|
@ -9,4 +7,3 @@
|
|||
| Name1 Name2 (CEO) | x | x | x | x |
|
||||
| Name1 Name2 (Head of IT) | x | x | x | x |
|
||||
| Name1 Name2 (Key User) | | | | x |
|
||||
|
||||
|
|
|
|||
|
|
@ -15,7 +15,4 @@
|
|||
- [x] Hide unused modules (e.g. calendar module in navigation)
|
||||
- [x] Test basic functionality
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -33,7 +33,4 @@
|
|||
|
||||
Consider to update the [Key Supplier Evaluation](../Purchase/Key%20Supplier%20Evaluation.md) when changing this table.
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
|
||||
|
|
|
|||
|
|
@ -22,8 +22,6 @@
|
|||
|
||||
* PHP:
|
||||
|
||||
|
||||
|
||||
- [ ] The server hardware, software and assigned resources fulfill the recommendations
|
||||
|
||||
**Comment:**
|
||||
|
|
@ -147,6 +145,4 @@ Customer:
|
|||
|
||||
Supervised by (customer):
|
||||
|
||||
|
||||
|
||||
2022-01-01 - Version 1.0
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue
Block a user