Larry,
I could give you a laundry list of stuff like Business Value, Business
Sponsor Org and such. The problem I've run into with defining enterprise
fields centers around who owns the value for a given field. If the answer is
not the project manager, then you are going to have to involve more people in
the project setup process.
I would advise starting small and letting it grow. We did the opposite and
wound up frustrating the PMs when they didn't know what value was supposed to
go in a given field.
Fields that have worked well have three characteristics. First, the PM
understands the purpose of the information. Second, it is to be used to
group projects, resources and tasks in some way familiar to the organization.
Third, it can also be used to filter the information to create a specific
view of the portfolio.
So, in the end, I think we had about 10 really useful fields. Indicators
for budget, schedule, project risk and overall Project status. Business
Sponsor, Business Value, Project Size (we have internal processes based on
sizing), Project Status(Pipeline, Planning, Active, Completed, Canceled) and
two others that escape me.
I hope this helps.
TGG