I'm a new "Catia Champion" but I've been using it long enough that I'm one of those guys who still calls it MagicDraw. As a Project Lead Systems Engineer at Alcon I have used the tool to help the team align on key architectural and behavioral decisions for our medical devices. As many of you know, MBSE is unique in its ability to end the discussions that seem to go on forever when other methods are used. This tool in particular with its ability to visualize the nexus of architecture and behavior during simulations has turned what used to be project-long controversies into 3-meeting-collaborations.

One of Catia's great strengths is that it is cool. It encourages engagement. But that can be one of its biggest drawbacks as well. Among the challenges we have faced is the excess of interest in the tool that has been shown by people who have neither the capability to engage in systems thinking nor any experience with systems engineering. This can be especially dangerous because, even with Catia, bad Systems Engineering can "inoculate" people against future exposures to Systems Engineering. To put it another way: People become resistant to Systems Engineering when they have been exposed to a poor effort at Systems Engineering. And yes, you can do Systems Engineering poorly with any tool, even Catia.

By all means, champion the use of Catia. But be careful with who you allow to use it. Some usages can make your job as champion (and even your job as Systems Engineer) harder, not easier.