forked from Controls/gitea-pages
added Controls Internal structure
This commit is contained in:
@@ -0,0 +1,4 @@
|
||||
# Homeoffice Procedures
|
||||
|
||||
Here you can find procedural and technical information how homeoffice works in the Controls Section.
|
||||
These procedures are specific and might not be the same in other sections or departments in PSI.
|
||||
@@ -0,0 +1,4 @@
|
||||
# Infrastructure
|
||||
|
||||
Information about the Controls Infrastructure and setups. If you want to understand the architecture please go to
|
||||
Knowledge Center -> Explanation.
|
||||
@@ -0,0 +1,4 @@
|
||||
# Names and Places
|
||||
|
||||
To ensure that we can help each other and easily deputize for each other, there are certain rules of how to name stuff
|
||||
and where to put it. These rules should be followed. Exeptions should be documented clearly.
|
||||
@@ -0,0 +1,30 @@
|
||||
# Onboarding
|
||||
|
||||
This page contains a list of preparations and activities for new Control Section members. It could be used as a checklist.
|
||||
|
||||
## Concept
|
||||
|
||||
This process assumes that there is a **mentor** ("Goetti") assigned to the newcomer, that serves as the first point of questions and during an initial period
|
||||
makes sure the new section member has someone to ask, bring them with to lunch once in a while and for a coffee as needed.
|
||||
|
||||
The **timeline** for this is over the first couple of months, possibly up to 6 months, in order not to overwhelm the person with information and allow them to
|
||||
also settle in with their work. Technical information makes more sense to get earlier on, while organizational experience makes more sense once the
|
||||
person is more used to the environment.
|
||||
|
||||
## Preparations
|
||||
|
||||
Done or checked by the line manager of the newcomer.
|
||||
|
||||
## Access Permissions
|
||||
|
||||
Not all of the permissions are always done automatically.
|
||||
|
||||
## Visits and Meetings
|
||||
|
||||
The purpose of this part is networking and getting a view of the span of stakeholders we have, regardless of if they are directly relevant to
|
||||
the person's work. It goes towards understanding what the whole section does, and that we have a wide span of needs that we address.
|
||||
|
||||
## Services and Concepts
|
||||
|
||||
Things to show, bookmark, and learn.
|
||||
|
||||
@@ -0,0 +1,4 @@
|
||||
# Pikett Procedures
|
||||
|
||||
The pages in this section are about general procedures and how to get paid for Pikett. If you are on Pikett and search for
|
||||
help about a problem, look in the Knowledge Center -> Troubleshooting.
|
||||
@@ -0,0 +1,3 @@
|
||||
# Workflows and Procedures
|
||||
|
||||
Here you should find links to templates and explanations how procedures and workflows in the Controls section should work.
|
||||
@@ -1,9 +1,8 @@
|
||||
# Basic Help
|
||||
# Controls Internal
|
||||
|
||||
This documentation pages contain relevant information for Control Section members.
|
||||
|
||||
Picture Test:
|
||||
|
||||

|
||||
|
||||
This is a collection of basic help topics.
|
||||
|
||||
- [How to submit Tickets or Feature requests](Tickets.md)
|
||||
- [Collection of useful Links](UsefulLinks.md)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user