This week’s tip addresses how we deal with complex technology such as medical devices, smartphones, or any large scale system. In many cases, we need to provide our executive a well-defined cross-project report that supports their decision process. This is never something that one person should take action on. Instead, such projects are best approached in a collaborative manner. One of the greatest capabilities ORCANOS has pioneered and brought to the market was the ability to give users a way to simulate the architecture of the product and break it into deliverable components; almost like we do when we build the BOM for our manufacturing process. Using the Solution project work item provides the option to gather under one roof, all the subcomponents needed to manage projects. This type of view in ORCANOS gives you endless ways to review each subcomponent, including all projects details.
The example below illustrates my point:
Let’s assume we have 3 different products that are being represented on ORCANOS, using three different ORCANOS Solutions:
- Product 1 is being represented by Solution 1, and comprises the following sub-components underneath, which are being represented by ORCNAOS Projects:
- Subcomponent 1 is Software Project: Software 1
- Subcomponent 2 is a Hardware project: Hardware 1
- Subcomponent 3 is a Mechanical project: Mechanical 1
- Product 2 is being represented by Solution 2, and includes the following sub-components underneath, which are being represented by ORCANOS Projects:
- Subcomponent 1 is Software Project: Software 2
- Subcomponent 2 is a Hardware project: Hardware 2
- Subcomponent 3 is a Mechanical project: Mechanical 2
- Product 3 is being represented by Solution 3, and entails the following sub components underneath, which are being represented by ORCANOS Projects:
- Subcomponent 1 is Software Project: Software 3
- Subcomponent 2 is a Hardware project: Hardware 3
- Subcomponent 3 is a Mechanical project : Mechanical 3
Now, let’s assume we would like to have a lateral view, Cross discipline: In This case, we will establish a new QPack Solution called ‘Reports’ , and relate all projects to this Solution. The Reports Solution structure will be as follows:
- Software 1 (Project)
- Software 2 (Project)
- Software 3 (Project)
- Hardware 1 (Project)
- Hardware 2 (Project)
- Hardware 3 (Project)
- Mechanical 1 (Project)
- Mechanical 2 (Project)
- Mechanical 3 (Project)
This kind of aggregative tree structure, will enable retrieving cross products data, using the ORCANOS Views (Filter) capabilities.
How To Create Cross Project View?
As mentioned above, the solution lies in establishing one ORCANOS Solution, which holds all relevant ORCANOS projects underneath it. From QPack Admin interface you can create a solution such as Portfolio View, which will include as many other project components as required.
- Establish a new ORCANOS Solution called ‘Reports’ (How To: http://www.orcanos.com/help/Knowledgebase/creating-a-new-project/)
- Relate all projects to this solution (How To: http://www.orcanos.com/help/Knowledgebase/addremove-projects-from-solution/)
- Build yourself cross project filters and dashboards.
Notice that this technique is effective only when all project data are being managed on a Project level, and not on a Solutions level !!!
QMS Solution: This solution includes all the Quality Management System components are useful when required by the Quality Manager to perform tasks. In such cases you may find for example the following projects
- Document Management System
- Service Center (Complaint Management)
- Risk Management (RMF File)
- QMS E-Forms (CAPA, ECO, Training, MRB etc.)
- Risk Mitigation Related Projects (Software, Hardware, Mechanical)
Having all the above projects under one solution gives the QA/RA personnel a means of controlling quality events, and performing all quality control activities as required such as; traceability and action items.