CMII-Compliant Tools

About Our Software Tool Assessment and Certification Program

Our software assessment and certification program serves two purposes. One is to show developers of software tools how to improve their functionality. The other is to provide CMII grads with a list of tools that can support their CMII implementation.

Most of the best known software tools have been assessed relative to their ability to support the CMII methodology. Of those assessed, less than half were able to meet the minimum requirements. The tools most capable of supporting CMII are listed below.


Tool Type System Name Release/ Version Providers Name and Website Date Certified *Tool Ratings
Tools Certified or In the Process of Certification
PLM KONFIG CM® 7.0.2 Auto-trol Technology

www.auto-trol.com

Sept. 2001
PLM PLM 3.1 Usb

www.usb-muc.com

Dec. 2000 XX
PLM Teamcenter Enterprise 5.0 Siemens-UGS PLM Solutions

www.siemens.com/ugs

Feb. 2005
PLM eB CM 14.2 Enterprise Informatics

www.enterpriseinformatics.com

July 2005
PLM Agile Product Collaboration 9.0 Agile Software

www.agile.com

Sept. 2005
PLM ARAS PLM V9 ARAS Corporation

www.aras.com

Oct. 2005
PLM CMIS 9.0 NAVAIR

www.cmisweb.net

Dec. 2005
PLM PLM -- Oracle

www.oracle.com

2007 Aquired Agile 2007
PLM CMstat -- TPT Technology

(dba CMstat) www.cmstat.com

June 2007
BPM Process Vista 2.0 Inner IQ

www.inneriq.net

Sept. 2005
PLM = Product Lifecycle Management

BPM = Business Process Management

*Tool Ratings are described below



Rating Scale for CMII-Compliant Tools
COLUMN
1
2
3
4
5
The tool as assessed and certified meets the minimum requirements as defined below.
The developer continues to report improvements in overall CMII functionality since certification.
Feedback from CMII grads using and/or evaluating the tool is highly positive.
The tool is being used internally by its developer to manage development and/or other activities.
Tool is robust across the full spectrum of CMII process requirements, including automatic updates of CMII baselines from detailed ECN implementation plans.


Minimum requirements for certifying that a tool is CMII-compliant


• Baseline format, fields and functionality per the CMII model
• Able to identify baselines by model or an equivalent ID number
• Provides work flows that emulate the closed-loop change process
• Includes forms and decision points per the CMII model
• Uses field names and terminologies per the CMII model
• Uses items, documents, forms and records as key information handles
• Enables co-ownership of each document per the CMII model

 






 
image
image
image