According to the official OpenUP website the PM for a software development project that follow the OpenUP methodology is supposed to
- Encourage stakeholder consensus on prioritizing the sequence of work
- Stimulate team collaboration on creating long term and short term plans for the project
- Focus the team on continually delivering tested software for stakeholder evaluation
- Help create an effective working environment to maximize team productivity
- Keep stakeholders and the team informed on project progress
- Provide a framework to manage project risk and continually adapt to change
Points 1, 2, 5 are common to all PM in the universe, stakeholder management, expectation management and motivation management are part of the communication ability required as part of the role. However there are some other points that make me feel not so good:
Focus the team on continually delivering tested software for stakeholder evaluation
Stakeholder evaluation expression seems to be wrong. Stakeholder could be anyone with special interest in the project but not necessarily with decision power. Therefore, stakeholder is not the target of the deliverables for testing. More than one time you will be asked for “What if…” items, “Now that we already do this why…” items that everybody hate. Deliver & Deploy should be done only to the focus group -the right persons that will manage the results in an effective manner and following the software specs, probably an offshore QA team, a client QA or internal QA.
Help create an effective working environment to maximize team productivity
The working environment could be a lot of things, but probably means all external factors related for example to company environment, place/location and contractual stuff. However as IT and software developer I recommend to improve also the software environment -i.e. improve the software tools that the team use to do their work. I will recommend free/open source software 
but obviously is not necessarily the situation for every project. Something that is common in the companies is to have tools but most of the m out of date, not legally acquired -at least in Colombia is a common practice- not working. As PM you should validate the work effort to build the software but also additional effort imposed by the use of the tools -even the time logger tool that I hope you use. If you will ask the team for additional tasks like time logging, change control documentation and other tasks related to software development and project management, be sure that they can do it fast and easy.
Provide a framework to manage project risk and continually adapt to change
A framework is a set of tools, for a person that is handling a project in progress in quite unfair to ask her/him for also the PM framework. In the most of the cases PM should ask the PM Office or the historical records of the company projects to get templates or at least examples. In the case there is no information available you will have to take a look to the templates available in the Internet – I hope I can finish my templates soon so I can post them.
OpenUP site provides a lot of useful information but please validates it before use.