I fall into the group of people that don't care about numbering things. This is an age-old "version numbering" problem for software. With the Enterprise 2.0 debate, IMO, we don't even have to number anything--we can just provide a collection of products and services that solve customer's immediate and near-future problems, and will be flexible enough to grow with them and have enough longevity to last through the typical 3 year technology lifecycle. So in other words, a SOLUTION. It doesn't have to have a number, necessarily, it could have a year or it could have nothing. If you have to number it, call it "MyEnterpriseSolution 2011." MyEnterpriseSolution 2011 will be different for every company because every company is in a different business, a different point in their social and customer relationship lifecycle, etc. MyEnterpriseSolution 2011 will be different from MyEnterpriseSolution 2012 because there will be something new to think about at the end of 2011. So MyEnterpriseSolution 2011 will hopefully get your company to 2014 because you were able to live with MES2011 because it had flexible workflows, business rules, and a good API's to band-aid you through. Every year companies could roll out their collection of services and products that they feel are the most flexible, scalable, and have the longest longevity to meet Enterprise Requirements.You also just discovered why companies never involve me in naming products or numbering them.
