CIMOS™ FMEA

Each FMEA can be stored in parallel two languages (e.g. French / English). You can then print out either French or English only as well as a combination of both languages. The catalogs for standard text modules are also multilingual.

CIMOS™ contains the new action priority evaluation scheme (AP tables), structure trees and a detailed functional analysis module. The printout in the new AIAG / VDA 2019 Red Print Ed. form format (Design, Process, MSR) is also included. The new P-diagram (parameter diagram) will also be available shortly.

Yes.

Yes, any number of user accounts with specific privileges for individual program functions can be created.

The corresponding manual chapter is available for each program function mask and each menu with a click of the mouse.

Yes, the input of FMEA and CP is guaranteed without contradictions (e.g. not "visual inspection" in FMEA and "automated sensor inspection" in CP).

Once that and beyond, it is possible to define reusable analysis modules for individual components or process steps. This yields a noticeable rationalization effect (automated adoption of changes in the "FMEA module" in variant projects). Complete structure hierarchies can also be copied as "variant trees".

The knowledge base search function uses keywords (e.g. a failure mode description) to carry out a scanning process in similar projects and, if analogies are found, generates a list of similar items for import.

Not only for the FMEA categories Design, Process and MSR, but also for e.g. individual process types or function groups, special evaluation catalogs can included. In addition, detailed AP (Action Priority) tables can be defined.

Critical characteristics (CC safety and certification) and main characteristics (CC functional) can be classified in CIMOS™ and supported by catalogs. This can be used as a selection criterion for data evaluations. The systematic allocation is based on the determination of external (divided into main, secondary and supportive) and derived internal functions in connection with the assessment of the effects (PN Significance).

The number of system levels is not limited in CIMOS™. The application also allows the modular linking of complete structure tree branches.

As part of the "cross reference list", the system delivers e.g. the information in which higher level projects a working step PFMEA or a component DFMEA is contained. FMEAs can also be filtered by e.g. process / function type in project listings.

CIMOS™ creates a consolidated, sequential printout in the format of the form type you selected (AIAG / VDA, IATF, QS 9000 etc.). For each system element passage (process step or component) there are optional informative lines for the printout, e.g. for version and modification status, as well as structure level position.

All pending action deadlines are listed in sorted form in the "time limit monitoring". Sorting according to AP (action priority) is also available. It is possible to send reminders for overdue measures. The "Deadline Early Warning System" allows automated mailing to the responsible staff member with an indication of upcoming tasks.

The expected effectiveness of a measure can be classified in CIMOS™ according to an grading system and used as an additional evaluation criterion.

Priority lists (PN and AP), pareto diagram, risk matrix, management report, time limit supervision. All evaluations can be filtered according to various criteria (function / process types, project scope, keyword ...).

CIMOS™ includes fully automatic document versioning with a release system and archiving of the version status. Differences in content between older and younger versions are highlighted in color on request. This functionality also applies to the area of the Control Plan (CP).

Yes, a corresponding add-on module is available. With this, import masks can be individually defined and saved for various Excel™ table formats.

FMEAs can be exported to HTML table format. This allows a smooth import in e.g. Excel™ or other standard applications.

Update routines are regularly provided for CIMOS™. After selecting the server directory and entering the required FMEA admin password, the upgrade is imported automatically (progress bar). Activation codes and your license information remain valid.

MBFG offers workshops on program operation for CIMOS™. For this, at max. 6 hrs. of online training will be sufficient. In addition, a 1-day methodology training course can be booked. We provide team coaching in cooperation with consulting partners.

No. You can do the simple installation yourself. Additional effort arises in the case of company-specific configurations (adjustments), and maintenance on the basis of service contracts (updates, annual billing) are optionally available. Training according to time accounting (see FAQ).

Yes, whereby individual diagram elements (e.g. for working steps) can also be linked to the associated PFMEAs.

Yes, including free adjustment of scaling, margins etc.

One or even several documents can be linked to each function / characteristic, each failure mode, effect, cause, etc. When opened, the Windows™ application assigned to the respective file type (extension) starts (also works with CAD viewers).

Is available for download. Runs indefinitely, the limits are: 

- max. 40 individual projects 

- printout limited to one page with watermark (print preview is free)

- no import / export functions

Otherwise, the trial version is identical to the full version. For the free download (Password "level1") go to "fmea.cn"

Yes. In your company own network environment as a floating server license (e.g. limited to max. three parallel users, but it does not matter from which workstations these three users take access). Windows™ Server 2019/2016/2012 and front-end Win 10/8/7 are supported. No Mac and no Unix.

As a VPN (Virtual Private Network) connection with permanent hardware BOVPN tunnel (Branch Office VPN). The Client VM (Virtual Machine) is activated for the BOVPN and the users at the remote location can access the application via RDP (Remote Desktop) via Internet and VPN router in the same way as the users at the main company location.

Numerous reasons speak against web-based models: 

a)  Need for a working stable internet connection, which is not always guaranteed

b)  Misdirected service activities due to short-term connection time outs and fluctuations in bandwidth

c)  Loss of data in the case of interruptions, then possibly complex restoration procedures

d)  Performance bottlenecks and long response times caused by slowing Internet

e)  Delegation of data backup to service providers whose reliability (cycles, etc.) cannot always be tracked

f)  Time pressure and possibly communication problems in case of necessary complete or partial restoration of data 

g)  External mirroring and replication of FMEA relevant documents with possibly sensitive company data 

h)  Possibly inconsistently configured security settings on the "remote" user systems

i)  Encryption problems (safety leaks) in data transmission (FMEA data contain sensitive information) 

j)  Sabotage and retrieval of data content also from outside the company with revealed passwords

k)  Dependency on the (mostly unknown in detail) security mechanisms of the cloud provider (hackers)

l)  Unclear structures of the SaaS provider, e.g. with regard to data outsourcing to subcontractors 

m)  FMEA access problems in the case of cloud server maintenance (time zone shift) 

n)  Difficult to calculate (often higher) application prices based on usage times etc. 

o)  Frequently surcharges for flexible customer-specific access authorization models (folders / documents)

p)  High-priced, if available at all, customizing (individual program adjustments)

q)  Need for internet access (browsers, firewalls, malware blockers) on every user workstation

r)  Inhomogeneous environments, compatibility problems with different browser applications / versions 

s)  SaaS interface compatibility problems in data exchange with third-party applications on local servers 

t)  Involvement of a third party provider for cloud services, resulting in additional financial expenses 

u)  Necessity to drawing up complex "outsourcing contracts" that have to be updated regularly (GDPR .....) 

v)  Gaps in data law if the cloud server is actually located outside of your country / continent

w)  Longer-term contract binding to service providers with corresponding payment obligations  

x)  Dependence on support services in the event of a change of provider, e.g. because of poor support 

y)  Dependency relationship, no further use of the FMEA software in the case of SaaS contract termination 

z)  Blocked access to FMEA project data in the event of bankruptcy by the third-party provider or its subcontractor 

Technologically, CIMOS™ is also portable on cloud platforms. With reference to the above However, we refrain from such fragile models, especially with regard to the outstanding protection value of FMEA data. 

Risk management is an area of application predestined for on-premises use