Our very own Grant Larsen and Dr. Gili Mendel joined forces to deliver a great webcast on Nov 16th, called “Asset Management powered by Jazz”

The topic is oriented around collaborative lifecycle management (CLM) processes and how to use RAM to effectively share or reference CLM assets throughout the organization. Dr. Gili does a free-wheeling demo, so check it out!

Advertisements

A new youTube video highlights how RAM and other Rational software is helping General Motors create smarter products like the Chevrolet Volt. RAM is highlighted at the 2:55 mark in the video.

Rational Asset Manager V7.5 released today on jazz.net. This release includes some cool innovations in usability, new and improved integrations, and more flexible licensing and deployment options.

Check out the new and noteworthy; it includes videos on many of the new features.

I hope you enjoy the five-part video series, illustrating the value of RAM for practitioners during key points in the software development lifecycle.

On behalf of the entire product team, I’d like to thank thank our large community of users and design partners for their feedback and involvement, helping this to be the most powerful and usable release to date.

Governing, and Tracking the development of Services end to end is not a simple task.

In this movie, Dr. Gili Mendel extends the ALE series (by Derek Baron) and provides a technical perspective on the development of service specification and implementation.

I’d like to share some exciting news. Last Friday we delivered our third and final milestone release for the next version of Rational Asset Manager. It features innovations in usability, new and improved integrations, and more flexible licensing and deployment options.

Checkout the What’s New page on Jazz.net to learn more about the milestone release:

We thank our large community of users and design partners for their feedback!

Recently, I’ve received a number of questions about how to enforce Asset Categorization. For example, you may want to require the following categorization before the asset can be approved:

NOTE: If the images appear fuzzy, just click on them to get a clearer view.

The first place you might look is the Asset Type Constraints :

And since there is no section on categorization constraints, there appears to be no control.

You may have noticed the tab supporting automatic categorization, which is a cool topic I will cover another time.

However, back to the point of this post. RAM provides lifecycle policies to help enforce rules for categorization. These are managed as part of the Lifecycle configuration:

There are two related to Categorization:

These can be set to run at specific states and at certain times, such as when the asset enters a state. Yet while policies might prevent you from changing the state of an asset, they do not prevent you from submitting a new asset to the repository.

The first one can add/remove categories explicitly:

The second can help enforce the rule that a category is selected:

So now, when an asset is created, it can be enforced that categorization must be applied before it can transition to the next state:

1. Someone submits an Asset (the policy doesn’t stop this)

2. When they try to move the state, the policy fails:

You can View results to see why the policy failed:

Lifecycle policies can be very powerful, and with a little creativity you can automate many of your business rules.

In this third installment you’ll learn a little about the Impact Analysis available in ALE, enjoy!