I don't if this will help much, but this is a "cut and paste" from a document out of a Project Office called the Project Manager's Information Guide:
1 OBJECTIVES
2 DEPARTMENT OVERVIEW
2.1 Overview of ADPM (Application Development Project Methodology)
2.2 IS Organization
3 PROJECT MANAGER TOOLS OVERVIEW
3.1 Software & Websites
3.2 Web Report Capabilities
3.3 Business Engine and Resource Server
3.4 Scheduling a Conference Room
4 PROJECT START UP
4.1 Project Manager Meet
4.2 PM Mentor
4.3 Project Start Up Checklist
4.4 Filing WBS Exceptions
4.5 Completing a Project Review
5 PROJECT STATUS REPORTING
5.1 Updating the Project Budget Spreadsheet
5.2 Monthly Status Report
I helped run (the manager was always out of town, so I guess I really ran it!) an IT project management office for a large bank, and the work involved a lot of project tracking and coordination work, especially when projects from different business divisions had conflicting schedules or interwoven dependencies. There was also a lot of vendor management and coordiantion. Part of my job and the other analysts in the group was to translate the business requirements into technical requirements for the vendors, push the vendors for a responseand a quote, negotiate the requirements and get a sign-off for the expenditures, then track the vendor (and the internal development teams) on their status.
I would be happy to send more info in an email if you like. mitzipearce@hotmail.com