Developing and introducing a project model in a tech company

I have just started a project which goal is to develop and introduce a common project model in a medium sized technology company. We have just started to review some of the established models/frameworks, in order to decide whether to use any of them as a basis for our own projectmodel. So far we have looked at the following frameworks:

• PROPS
• PRINCE II
• PMI / PMBok
• Difi's project guide (Norwegian)
• A couple of models from other companies
  

We have not concluded yet, but the feeling so far is that all frameworks mentioned above are too complex to introduce in our organisation. However, parts of the frameworks are obviously sensible to include in the model we are building.

The project charter defines six areas that the project framework has to cover:

• Project phases
• Decision points
• Project templates
• Project roles
• Project terminology
• Routine descriptions

In addition I would like to cover the human perspective, as well as the link between business strategies and initiation of projects.

An important premise is that the new framework can (and will) be used for all kinds of projects in our organisation - which includes development-, organisational-, procurementprojects and so on.

My project group is eager to start defining phases and decision points with templates and descriptions, but I am not sure how to proceed with this matter.

Does anyone have any experience with developing and/or introducing a brand new project model? Do you think we sould use one exsiting framework as a base, or should we pick the best elements from different models and create our own model? The last option is ofcourse to start developing our own model from scratch, but that would probably be the same as reinventing the wheel?

Any help is greatly appreciated.

/BjørnK