IMS - User contributions [en]

Terminology/BYOD

2026-07-06T07:51:43Z

L4013899526:

Terminology/BYOD

2026-07-06T07:51:22Z

L4013899526:

Terminology/BYOD

2026-07-06T07:43:16Z

L4013899526:

Terminology/BYOD

2026-07-06T07:43:07Z

L4013899526:

Terminology/BYOD

2026-07-06T07:41:33Z

L4013899526: Update subject via NeoWiki UI

Schema:Term

2026-07-06T07:39:55Z

L4013899526: Update schema via NeoWiki UI

{
"propertyDefinitions": {
"Definition": {
"type": "text",
"description": "",
"required": false,
"multiple": false,
"uniqueItems": false
},
"Is abbreviation?": {
"type": "boolean",
"description": "",
"required": false
},
"Abbreviation meaning": {
"type": "text",
"description": "",
"required": false,
"multiple": false,
"uniqueItems": false
},
"Synonyms": {
"type": "text",
"description": "",
"required": false,
"multiple": false,
"uniqueItems": false
},
"Domain": {
"type": "text",
"description": "",
"required": false,
"multiple": false,
"uniqueItems": false
},
"Definition source": {
"type": "text",
"description": "",
"required": false,
"multiple": false,
"uniqueItems": false
},
"Notes": {
"type": "text",
"description": "",
"required": false
}
}
}

Terminology/BYOD

2026-07-06T07:38:40Z

L4013899526: Update subject via NeoWiki UI

Terminology/BYOD

2026-07-06T07:36:58Z

L4013899526: Update NeoWiki subject

Terminology/BYOD

2026-07-06T07:34:43Z

L4013899526: Created blank page

Schema:Term

2026-07-06T07:26:01Z

L4013899526: Update schema via NeoWiki UI

{
"propertyDefinitions": {
"Definition": {
"type": "text",
"description": "",
"required": false
},
"Is abbreviation?": {
"type": "boolean",
"description": "",
"required": false
},
"Abbreviation meaning": {
"type": "text",
"description": "",
"required": false
},
"Synonyms": {
"type": "text",
"description": "",
"required": false
},
"Domain": {
"type": "text",
"description": "",
"required": false
},
"Definition source": {
"type": "text",
"description": "",
"required": false
}
}
}

Schema:Term

2026-07-06T07:22:29Z

L4013899526: Created page with "{ "propertyDefinitions": { } }"

{
"propertyDefinitions": {}
}

Controlled Document:Process description

2026-06-23T15:05:17Z

L4013899526:

{{CreateInput|alignment=left|buttonlabel=New Process description|preload=Template:IMS PT Process description|placeholder=Enter process name|prefix=Controlled Document:Process description/}} 
<neowiki_report format="grid">{
"properties": {
"Document Control.Owner": "Owner",
"qm/state": "State",
"Document Control.Valid until": "Valid until"
},
"conditions": [
{
"property": "Document Control.Document type",
"operator": "=",
"value": "Process description"
}
],
"sort": [
{
"property": "name",
"direction": "ASC"
}
],
"hasSubjects": [
"Document Control"
],
"mainLabel": "Document name",
"pageDisplayFormat": "subpage",
"showPageLink": true
}</neowiki_report>

Controlled Document:ISO 27001/Statement of Applicability (SoA)

2026-06-23T15:04:39Z

L4013899526:

This page provides an overview of the implementation status of ISO/IEC 27001 Annex A controls within the organization. It highlights the current selection decision (included / excluded) and for included controls the implementation status.

Controls that are not listed on this page have not yet been evaluated.<neowiki_report format="grid">{
"properties": {
"ISO 27001 Control.Selection type": "Selection",
"ISO 27001 Control.Implementation status": "Status",
"ISO 27001 Control.Category": "Category"
},
"mainLabel": "Annex A Control",
"pageDisplayFormat": "subpage",
"showPageLink": true
}</neowiki_report>

Controlled Document:Team/Sales

2026-06-23T15:03:07Z

L4013899526: Update subject via NeoWiki UI

Controlled Document:Team/Marketing

2026-06-23T15:02:49Z

L4013899526: Update subject via NeoWiki UI

Controlled Document:Team/Customer Success

2026-06-23T15:02:33Z

L4013899526: Update subject via NeoWiki UI

Controlled Document:Team/Management

2026-06-23T15:01:48Z

L4013899526: Update subject via NeoWiki UI

Controlled Document:Team

2026-06-23T15:00:27Z

L4013899526:

<neowiki_report format="grid">{
"properties": {
"qm/state": "Status"
},
"conditions": [
{
"property": "namespace",
"operator": "IN",
"value": [
1540
]
}
],
"hasSubjects": [
"Team"
],
"pageDisplayFormat": "subpage",
"showPageLink": true
}</neowiki_report>

Controlled Document:Policy

2026-06-23T14:57:48Z

L4013899526:

{{CreateInput|alignment=left|buttonlabel=New policy|placeholder=Enter policy name|prefix=Controlled Document:Policy/|preload=Template:IMS PT Policy}} 
<neowiki_report format="grid">{
"properties": {
"Document Control.Owner": "Owner",
"qm/state": "State",
"Document Control.Valid until": "Valid until"
},
"conditions": [
{
"property": "Document Control.Document type",
"operator": "=",
"value": "Policy"
}
],
"sort": [
{
"property": "name",
"direction": "ASC"
}
],
"hasSubjects": [
"Document Control"
],
"mainLabel": "Document name",
"pageDisplayFormat": "subpage",
"showPageLink": true
}</neowiki_report>

Controlled Document:Role

2026-06-23T14:57:25Z

L4013899526:

{{CreateInput|alignment=left|buttonlabel=New role definition|placeholder=Enter role name|prefix=Controlled Document:Role definition/|preload=Template:IMS PT Role definition}}
 
<neowiki_report format="grid">{
"properties": {
"Document Control.Owner": "Owner",
"qm/state": "State"
},
"conditions": [
{
"property": "Document Control.Document type",
"operator": "=",
"value": "Role definition"
}
],
"sort": [
{
"property": "name",
"direction": "ASC"
}
],
"hasSubjects": [
"Document Control"
],
"mainLabel": "Document name",
"pageDisplayFormat": "subpage",
"showPageLink": true
}</neowiki_report>

Controlled Document:Team

2026-06-23T14:43:21Z

L4013899526: Created blank page

Controlled Document:Team/Product Development

2026-06-23T14:42:33Z

L4013899526:

The Product Development team is responsible for designing, developing, and bringing new products or product improvements to market.

The team collaborates across functions such as engineering, design, quality, and marketing to translate customer needs and business goals into viable, high-quality solutions. Their work includes concept creation, prototyping, testing, and validation, ensuring that products meet regulatory, technical, and customer requirements while being delivered on time and within budget. Continuous innovation and cross-functional collaboration are key to their success.

Controlled Document:Team/Product Development

2026-06-23T14:41:30Z

L4013899526: Update subject via NeoWiki UI

Controlled Document:Policy/Quality policy

2026-06-23T14:40:21Z

L4013899526: Update subject via NeoWiki UI

== Purpose ==
The purpose of this policy is to define the organization’s commitment to quality and to establish a framework for the Quality Management System (QMS).

== Scope ==
This policy applies to all employees, processes, and activities within the organization that impact product and service quality.

== Policy Statement ==
The organization is committed to delivering products and services that consistently meet customer expectations and applicable regulatory requirements.

== Commitments ==
The organization shall:

* Ensure customer satisfaction through consistent delivery of quality products and services
* Establish and review measurable quality objectives
* Maintain and continually improve the QMS
* Ensure compliance with applicable statutory and regulatory requirements
* Promote a culture of quality and continuous improvement

== Responsibilities ==

* Top Management is responsible for establishing, implementing, and maintaining this policy
* Employees are responsible for adhering to this policy in their daily activities

== Review ==
{{Excerpt/IMS Review}}

Controlled Document:Role

2026-06-22T13:07:26Z

L4013899526:

{{CreateInput|alignment=left|buttonlabel=New role definition|placeholder=Enter role name|prefix=Controlled Document:Role definition/|preload=Template:IMS PT Role definition}}
 
<neowiki_report format="grid">
{
"properties": {
"Document Control.Owner": "Owner",
"qm/state": "State"
},
"conditions": [
{
"property": "Document Control.Document type",
"operator": "=",
"value": "Role definition" }

],
"sort": [ {
"property": "name",
"direction": "ASC"
} ],
"hasSubjects": [ "Document Control" ],
"mainLabel": "Document name"
}
</neowiki_report>

Controlled Document:Role

2026-06-22T13:07:17Z

L4013899526:

{{CreateInput|alignment=left|buttonlabel=New role definition|placeholder=Enter role name|prefix=Controlled Document:Role definition/|preload=Template:IMS PT Role definition}}
 
<neowiki_report format="grid">
{
"properties": {
"Document Control.Owner": "Owner",
"qm/state": "State",
},
"conditions": [
{
"property": "Document Control.Document type",
"operator": "=",
"value": "Role definition" }

],
"sort": [ {
"property": "name",
"direction": "ASC"
} ],
"hasSubjects": [ "Document Control" ],
"mainLabel": "Document name"
}
</neowiki_report>

Controlled Document:Role/Sales Manager

2026-06-22T13:06:58Z

L4013899526: Update NeoWiki subject

== Responsibilities ==
* Lead and manage the sales team to achieve revenue targets and business growth objectives
* Develop and execute sales strategies, forecasts, and performance plans

== Authorities ==
* Set sales targets, approve discounts within policy, and allocate sales territories
* Recruit, coach, and evaluate sales team members to drive performance

== Competencies ==
* Strong leadership and team management skills in a sales environment
* Excellent negotiation, forecasting, and data-driven decision-making abilities

Controlled Document:Role/Sales Manager

2026-06-22T13:06:51Z

L4013899526: Update subject via NeoWiki UI

Controlled Document:Role/Head of IT

2026-06-22T13:06:04Z

L4013899526: Update subject via NeoWiki UI

== Responsibilities ==
* Define and execute the organization's IT strategy aligned with business objectives
* Oversee IT operations, infrastructure, and service delivery to ensure reliability and security

== Authorities ==
* Approve IT budgets, major technology investments, and vendor contracts
* Set and enforce IT policies, standards, and governance frameworks

== Competencies ==
* Strong leadership and stakeholder management skills across business and technical teams
* Deep understanding of IT architecture, cybersecurity, and enterprise systems

Controlled Document:Role/Account Manager

2026-06-22T13:05:44Z

L4013899526: Update subject via NeoWiki UI

== Responsibilities ==
* Manage and grow relationships with key customer accounts to ensure satisfaction and retention
* Act as primary point of contact, coordinating internal teams to deliver solutions and services

== Authorities ==
* Negotiate pricing, contracts, and service agreements within defined limits
* Escalate and resolve customer issues by mobilizing internal resources as needed

== Competencies ==
* Strong client communication and relationship-building skills
* Solid understanding of customer needs, business processes, and solution offerings

Template:IMS PT Role description

2026-06-22T09:56:14Z

L4013899526: Created page with "== Responsibilities == * Responsibility 1 == Authorities== * Authority 1 ==Competencies == * Competency 1"

== Responsibilities ==
* Responsibility 1

== Authorities==
* Authority 1

==Competencies ==
* Competency 1

Controlled Document:Work instruction/Making an offer

2026-06-22T09:51:13Z

L4013899526: Update subject via NeoWiki UI

== Purpose / Goals ==
An offer is made at the request of the customer. The quality and content of the offer are of great importance here. The aim of these work instructions is to create an offer that leads to a signed contract and takes into account the interests of the customer and our company.
== Assigned process ==

*[[Controlled Document:Process description/Sales process|Sales process]]

== Work instruction ==
{| class="wikitable" style="width:100%;" data-ve-attributes="{"style":"width:100%;"}"
!'''Responsible'''
!'''Step'''
!'''Procedure'''
!'''Needed tools'''
|-
|Sales agent
|Document requirements in Odoo
|FileCheck and evaluate the documented requirements in Odoo
|''systems, checklists,''
''physical tools''
|-
|
|Generate an offer
|FileComplete the template "Offer"
|Odoo
|-
|Sales manager
|Check the offer
|FileDescription of the service
FileTerms and conditions

FileOptions

FilePrices and additional costs (net and gross values)

FilePayment conditions

FileDiscounts

FileValidity period of the offer
|Odoo
|-
|Sales agent
|Send offer via email
|
|Odoo
|-
|
|Rework the offer after feedback from client
|
|Odoo, Email
|}

Controlled Document:Process description/Patent opposition

2026-06-22T09:50:26Z

L4013899526: Update subject via NeoWiki UI

== Purpose /goals ==
The goal of this process is to ensure a structured, legally compliant, and efficient process for preparing and filing patent applications.

'''Purpose:'''

* Uniform procedures for processing preliminary patent inquiries.
* Minimizing errors and risks prior to filing a patent application.
* Optimizing client consultation and documentation.
* Increasing the success rate of patent applications.

== Process steps ==
{| class="wikitable" style="width: 100%;"
!Step
!Description
|-
|'''1. Client Inquiry'''
|Initial contact by the client with an idea or invention.
|-
|'''2. Initial Consultation'''
|Examination of protectability, explanation of the patent process, clarification of expectations.
|-
|'''3. Research Phase'''
|Conducting a prior art search (patent search, literature, market analysis).
|-
|'''4. Assessment of Patentability'''
|Legal and technical assessment of the prospects of success.
|-
|'''5. Strategic Consulting'''
|Decision on patent, utility model, or other intellectual property rights.
|-
|'''6. Draft of the Patent Application'''
|Preparation of the technical description, claims, and drawings.
|-
|'''7. Coordination with Client'''
|Consultation on the final version, clarification of any outstanding issues.
|-
|'''8. Filing with the Patent Office'''
|Formal filing of the application, including a priority application if applicable.
|-
|'''9. Documentation and Archiving'''
|Storage of all relevant documents in the firm's system.
|-
|'''10. Follow-Up'''
|Monitoring of deadlines, communication with the Patent Office, preparation for examination procedures.
|}

== Performance indicators ==

* '''Turnaround time''' from initial contact to filing (in days)
* '''Number of successfully filed patent applications per quarter'''
* '''Rate of positive feedback from the patent office (e.g., without objections)'''
* '''Client satisfaction''' (e.g., via feedback forms)
* '''Error rate in formal submissions''' (e.g., returns due to formal errors)

== Risks ==

* '''Insufficient research''' → risk of rejection due to existing intellectual property rights.
* '''Lack of or unclear communication with clients''' → misunderstandings about the scope of protection.
* '''Formal errors during filing''' → delays or rejection.
* '''Failure to meet deadlines''' → loss of priority rights or protection options.
* '''Technical description inaccurate or incomplete''' → weakening of the scope of protection.
[[Category:Protection for patents]]

Controlled Document:Process description/Patent rights

2026-06-22T09:49:26Z

L4013899526: Update subject via NeoWiki UI

== Purpose / goals ==
The goal of this process is the legally sound conduct of an opposition against a granted patent or the defense of a patent against an opposition.

'''Purpose:'''

* Protecting the client's interests by challenging or defending patent rights.
* Ensuring a legally compliant and strategically well-thought-out approach before the patent office.
* Minimizing economic risks due to unjustified patents or oppositions.

== Process steps ==
{| class="wikitable"
!Step
!Description
|-
|'''1. Client Inquiry / Intention to Oppose'''
|Clarification of the facts and objective (attacker or defender).
|-
|'''2. Check of Deadlines'''
|Ensuring that the opposition is filed within the statutory deadline (usually 9 months after patent grant).
|-
|'''3. Analysis of the Facts'''
|Examination of the contested patent or the grounds for opposition (e.g., lack of novelty, lack of inventive step).
|-
|'''4. Search and Evidence Gathering'''
|Collection of relevant documents, publications, and technical information.
|-
|'''5. Preparation of the Notice of Opposition / Response'''
|Legal argumentation, presentation of evidence, formal drafting.
|-
|'''6. Filing with the Patent Office'''
|Timely and proper submission of the opposition or defense.
|-
|'''7. Communication with the Office and parties'''
|Correspondence, preparation for oral proceedings if necessary.
|-
|'''8. Participation in oral proceedings'''
|Representation of the client before the Patent Office, presentation of arguments.
|-
|'''9. Decision and Follow-up'''
|Evaluation of the decision, consultation on further steps (e.g., appeal).
|-
|'''10. Documentation and Archiving'''
|Complete filing of all procedural documents in the office system.
|}

==Performance indicators==

* '''Success rate''' for appeals (full or partial revocations)
* '''Duration of proceedings''' from appeal to decision
* '''Client satisfaction''' with the strategic advice and outcome
* '''Quality of argumentation''' (e.g., through feedback from the Office)
* '''Rate of timely and formally correct submissions'''

==Risks==

* '''Failure to meet deadlines''' → loss of the right to appeal
* '''Insufficient reasoning''' → rejection of the appeal
* '''Missing or weak evidence''' → low prospects of success
* '''Formal errors in the submission''' → inadmissibility of the appeal
* '''Misjudgment of the chances of success''' → unnecessary costs and resource commitment
* '''Reputational risks''' with an aggressive appeal strategy

 
[[Category:Protection for patents]]

Controlled Document:Process description/Procurement of materials

2026-06-22T09:48:36Z

L4013899526: Update subject via NeoWiki UI

==Purpose / goals==
Material procurement largely includes purchasing tasks. This includes determining the order quantity, obtaining and comparing offers, placing orders, checking incoming goods and storing the goods.

The purpose of the Procurement process is to structure the purchasing processes and sourcing strategies to ensure that the services and goods we acquire are the result of objective as well as time- and cost-effective decision making.
==Predecessor==
Manage inventory
==Recipient==
Accounting
==Process steps==
{| class="wikitable" style="width:100%;"
|+R=Responsible party; P= Participants in the process
!Input (resources)!! style="width:55%;" |Steps (link to work instruction if exists)!!Output (deliverables)!!R!!P
|-
|Request form ||submit purchase request|| ||employee||
|-
|
|assess vendors
|
|purchasingemployee
|
|-
|
|negotiate terms
|
|purchasingemployee
|
|-
|
|create purchase order
|
|purchasingemployee
|
|-
|Purchase order
|receive and inspect the delivered goods
|
|receptionist
|warhouse worker
|-
|
|conduct three-way matching
|
|
|
|-
|Invoice
|approve invoice
|
|purchasing employee
|
|-
|Approved Invoice
|arrange payment
|
|accountant
|
|-
|Purchase order, approved invoice
|close out request
|
|purchasing employee
|
|}

==Process diagram==
<div class="center"><drawio filename="Process_diagram_for_Procurement_of_materials"></div>

</drawio>

==Performance indicators==
''How are the goals measured?''
==Risks==
''What could go wrong? What are possible sources of error?''
==Resources==
''What resources are necessary to complete the process?''
===Equipment ===
''Systems, software, tools,...''
===Personnel / Qualifications===
''What roles are needed to perform this process?''
==Supporting documents==
''Which documents are related to this process (policies, guidelines, checklist templates, ...) ?''

== Records ==
''Any observations or reports that confirm the effectiveness of this process (completed checklists, meeting minutes, interviews, ...).''

Controlled Document:Process description/Sales process

2026-06-22T09:47:30Z

L4013899526: Update subject via NeoWiki UI

==Purpose / goals==
A standardized sales process allows our employees to work more efficiently and helps them to perfect their sales techniques. It must be used in parallel with the acquisition strategy. This is important for both customer satisfaction and lead conversion. In addition, the sales process allows the sales team to work more consistently as it structures their operations better. The goal of the sales process is higher completion rates, better customer loyalty and, ultimately, an increase in sales.
==Predecessor==

* Marketing process
==Recipient==

* Project management process
==Process steps==
{| class="wikitable" style="width:100%;"
|+R=Responsible party; P= Participants in the process
!Input (resources)!! style="width:55%;" |Steps
!Work instruction!!Output (deliverables)!!R!!P
|-
|Contact info ||'''Contact initiation'''
|Lead-Qualifizierung||Doku in Odoo||Sales Agent||Intersted party
|-
|Results from initial contact ||'''Lead qualification'''
|Lead-Qualifizierung||Doku in Odoo||Sales Agent||Intersted party
|-
|Results from lead qualification ||'''Needs analysis'''
|Lead-Qualifizierung||Doku in Odoo||Sales Agent||Intersted party
|-
|Results from needs analysis ||'''Produkt presentation'''
|Lead-Qualifizierung||Doku in Odoo||Sales Agent||Intersted party, HW-Support
|-
|Results from needs analysis ||'''Cost estimate'''
|Making an offer||Offer letter||Sales Agent||Intersted party
|-
|Results from needs analysis ||'''Contract negotiation'''
| || ||Sales Agent||Intersted party, Sales manager
|-
|
|
|
|
|
|
|}

==Process diagrams==
<center><bs:drawio filename="Drawio/Sales-process" /></center>
 
<big> '''Show flowchart'''</big>

<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-myDivision">
<center><bs:drawio filename="Drawio/Sales-Flowchart" /></center>
</div>

==Performance indicators==
The statistics for the following performance indicators are created in ''Odoo'' and evaluated every six months.

* Sales growth
* Sales target
* Customer acquisition costs
* Sales cycle length
* Lead conversion ratio (leads per sale)
* Number of sales opportunities (potential order value)
* Upsell and cross-sell rate

==Risks==

# Performance risk: The contractually stipulated services cannot be delivered
# Cost risk: underestimation of development costs

==Resources==

===Equipment ===

* Phone
* Email
* Odoo
* Demo system
* Eval system

===Personnel / Qualifications===

# Sales agent
# Sales manager
==Supporting documents==
''Which documents are related to this process (policies, guidelines, checklist templates, ...) ?''

== Records ==
''Any observations or reports that confirm the effectiveness of this process (completed checklists, meeting minutes, interviews, ...).''

Controlled Document:Process description/Corporate culture

2026-06-22T09:45:56Z

L4013899526: Update subject via NeoWiki UI

== Purpose / goals ==
The goal of this process is to establish, maintain, and further develop a corporate culture that is consistent with the organization's strategic goals, values, and self-image.

'''Purpose:'''

* Promote employee identification, motivation, and cohesion
* Create a positive work environment that fosters performance, trust, and innovation
* Ensure consistent behavior and decision-making in line with corporate values
* Support change processes, leadership development, and employer branding

== Process steps ==
{| class="wikitable" style="width: 100%;"
!Step
!Description
|-
|'''1. Analysis of the existing culture'''
|Collection through interviews, surveys, workshops, or cultural diagnoses.
|-
|'''2. Definition of the target culture'''
|Determination of guiding values, behavioral principles, and cultural target images.
|-
|'''3. Communication and Embedding'''
|Communication of culture through internal communications, managers, onboarding, etc.
|-
|'''4. Integration into HR processes'''
|Linking with recruiting, performance appraisals, feedback systems, and continuing education.
|-
|'''5. Leading the way through managers'''
|Managers as culture carriers – training, coaching, and role models.
|-
|'''6. Culture-promoting measures'''
|Rituals, events, storytelling, recognition systems, internal platforms.
|-
|'''7. Monitoring and feedback'''
|Regular culture measurement, e.g., via pulse surveys, culture barometers, or retrospectives.
|-
|'''8. Adaptation and further development'''
|Iterative adaptation of culture measures based on feedback and company development.
|}

==Performance indicators==

* '''Employee satisfaction''' (e.g., via eNPS or engagement scores)
* '''Turnover rate''' and reasons for resignation
* '''Culture fit for new hires'''
* '''Feedback rate''' and participation in cultural measures
* '''Perception of corporate values''' (e.g., in internal surveys)
* '''Leadership commitment''' to cultural development

==Risks==

* '''Cultural contradictions''' between communicated values and lived reality
* '''Top-down approach without participation''' → low acceptance
* '''Unclear or overly abstract values''' → lack of orientation
* '''Leaders who do not exemplify culture''' → loss of trust
* '''Lack of integration into processes''' → culture remains a "nice to have"
* '''Ignoring subcultures''' → Fragmentation and Conflict

User:L4013899526

2026-06-22T09:43:05Z

L4013899526: create user page

User blog:L4013899526

2026-06-22T09:43:05Z

L4013899526: Root blog page created