Continuous Improvement Process (CIP)

by
Odoo

50.06

v 16.0 Third Party 2
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Employees (hr)
Lines of code 493
Technical Name cip
LicenseOPL-1
Websitehttps://www.oybi.com
Versions 14.0 15.0 16.0
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Employees (hr)
Lines of code 493
Technical Name cip
LicenseOPL-1
Websitehttps://www.oybi.com
Versions 14.0 15.0 16.0

Continuous Improvement Module

Continuous Improvement Module



Finally, an easy to access and manage "suggestion box" that empowers every employee to actively engage in the success of the company. Success-driven companies are always looking for ways to increase efficiency, increase revenue, and lower expenses. The best source of those ideas can come from the people who live them every day. Simply put, the best ideas can come from your front-line employees. The Continuous Improvement Module gives every employee a voice and empowers them to not only share ideas but also drive success. This module goes even further by allowing them to track their idea and see the results and/or feedback from their suggestion. This expanded transparency is effective in showing appreciation for the ideas provided. The most powerful asset any company has is an active and engaged group of employees. This module by OYBI unlocks the full power of your employees and empowers them to work at making the company better, making their positions more effective and less stressful. No other tool can better engage your employees and actively involve them in making your business better. This module gives you the flexibility to create your own process flow, allowing you to configure your Sources, Stages, Tags, Types, etc. You can see this in a graph or report. Below you will find some workflow examples and screenshots of the module in action.



A Cost-Effective Tool to Drive Success.

CIP Process Flow

Ideas

The Ideas form is the heart of the application and is where your users will submit their ideas for consideration.

  • Responsible Manager: This is the manager responsible for the oversight of this CIP idea.
  • Assigned To: This is where the user can assign themselves to the idea, or a new assignee can be given at a later point in the process. The application will always track who the creator was, separate from the assigned user.
  • Related Partners: This field supports the linking of one or more Partners (customers, vendors, employees) that have some sort of relativity to the idea. An example would be if the idea is for a new product that the employee believes could be sold to one or more of our customers. You could use the Related Partners field to define which customers the employee believes would purchase the product/service.
  • Tag: Use this to identify the record with Tags. These Tags can be color-coded as well. See "Tags" below.
  • Narrative Description: This field is where the employee can enter the description of the idea.
  • Type: This field can be used to identify the "Type" of CIP idea. This list is modifiable via Configuration/Types. See "Types" below.
  • Source: This field can be used to identify where the idea came from. This list is modifiable via Configuration/Sources. See "Sources" below.
  • Created By: This is the original creator of the idea. This is different from the "Assigned To" value because an idea may change assignment during the progression of the work flow, but we want to always track the submitting user.
  • Status Note: This field can be used to further define the status of the idea, outside the stage it is in. For instance, the stage may be "in process" but the status notes may say "estimated to be completed by 12/31/22"
  • Stage: The stages are used to track where the idea is in the flow, configurable in Configuration/Stages. In this application, Stages have several special functions. Please see "Stages" below for more information.
  • Chatter: This application supports full chatter functionality; including followers, messages, and notes. Most changes to the idea are also logged in the chatter for traceability

Native Support for Form, List and Kanban views

Sources

Sources are a piece of metadata that will allow you to track the ideas by originating sources. This list can be configured to best fit your business needs. An example list of sources would be "Employee", "Supplier", "Customer", or "Other".

Native Support for Form, List and Kanban views

Stages

Much more than just a status!

Stages are typically used to track the status of a record, through a predefined workflow. The CIP module is no exception. However, we have pre=built in some great add-on functionality to support automation of the workflow.

  • Folded by Default: Setting this checkbox will automatically fold the stage on the Ideas Kanban view, which groups by stage.
  • Default: Setting this checkbox will use this stage as the default when creating a new Idea.
  • Admin Only: In the CIP Module there are two security groups, CIP Users and CIP Admins. If this checkbox is checked, only users in the CIP Admin group will be allowed to move an Idea into this stage.
  • Manager Email Template: This feature allows you to configure email templates that are sent upon moving an idea into this stage. An example manager email template would be when moving an idea to the "Submitted" stage and email the assigned manager to let them know that there is a new idea submitted for their approval.
  • Employee Email Template: This feature works the same as the Manager Email Template - but allows for a secondary email template to be sent to the assignee, or creator. An example would be an email on the "Approved" stage to let the employee know that their idea was approved.

Native Support for Form, List and Kanban views

Tags

Tags are used as another piece of meta data that can be used for sorting, reporting, and quick visualization on the Idea. The Idea Tags support color coding as well.

Native Support for Form, List and Kanban views

Types

Types are the last form of meta data which can be used to track a list of Idea Types like Product, Process, Resources, Hardware and Software.

Native Support for Form, List and Kanban views

About the Author

Own Your BI, LLC (OYBI) is a certified Odoo Partner located in Ludington, Michigan (USA). We are a team of application consultants, developers, and integrators with decades of experience in the Manufacturing and Retail industries. Feel free to reach out to our team for any implementation, customization, or consulting needs.

Email Us

Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.