Paul Davis
 Intranet --> Personal Work Spaces --> Paul Davis --> About Me  
   

Paul Davis


Paul Davis is the IT director for the Cornell College of Engineering and heads up the Engineering College's Office of Information Technology. Until accepting this position in October of 2007, he was a senior programmer analyst in the dean's office. He and his staff are currently responsible for:

 

Paul also has an interest in IT project management, IT project and service governance, and administrative systems architecture, particularly middleware infrastructure.

 

Paul received his M.A. in Sociology and a B.A. in Organizational Studies from UC Davis. He has worked at The Minnesota Educational Computing Corporation (MECC), NeXT, UC Davis, and Cornell. Prior to becomming a programmer, he was a carpenter and cabinet maker outside New York City and in Ithaca NY.

 

Contact Information for Paul Davis.

 


Here are a few things Paul has written, developed, or presented:

 

IT Project and Service Governance

  • 3/28/07 - Response to Audit Query about our Systems Development Life Cycle Management. Geofrey Yearwood asked the ITMC members address questions as a part of their audit of CIT's IS Department about our documented software lifecycle management methodologies. In particular, he is interested in learning about how we gather feature requests and get sign off from our user stakeholders.
  • 1/25/05 - Evaluation of IT services and governance models for College Intranet - We're building out an intranet and we want to leverage whatever IT services we can. I itemize 9 IT services we will want to use and their status on campus. this document is intended to start discussions, not to be a definitive evaluation. [governance]
  • 1/14/05 - Presentation to the CommonSpot CMS SIG kick off meeting - I presented the history of the Web Content Management System evaluation and purchase at the kick off meeting for the CommonSpot SIG. [governance]
  • 1/9/05 - Ideas for IT Project governance - This was an early effort to think about IT project governance. It was a stream of consciousness effort I did early one morning and it looks at governance from the end users up so some of the committee names are a bit strange. e.g.: SIG board instead of advisory committee. I've cleaned these ideas up in the email above about the evaluation of IT services for the college intranet. [governance]
  • 1/7/04 - Migrating Locally built Administrative Systems to Larger Audiences - CIT requested input on why units were building their own systems to meet similar business needs. This was my response. In it I describe three different efforts to migrate local systems to a broader audience and the lessons learned for each effort. I also talk about why distributed units are likely to develop systems that meet their needs better than any central unit. Therefore they need to be involved in project development and governance. [governance]

 

Project Management

  • 1/30/05 - Project management tools - A number of people have asked me about the tools I use to organize my project documents so I decided to finally write it down. Here is the result. [Project Management]
  • 1/5/04 - Taking photos of Whiteboards after meetings - I wrote this in response to an evaluation of dedicated whiteboard recording tools. I carry a small camera with me everywhere to take pictures of whiteboards before they get erased. You'll see whiteboard photos posted all over our intranet. [Project Management]

 

Administrative Systems Architecture

  • 7/7/2005 - Draft specification for a group management tool - The Identity Management group is working on developing some Authorization management tools for campus. One aspect of these tools is being able to assign people to groups for authorization assignment. This is particularly important to me because I'm building an intranet web site for Engineering that will make heavy use of a group memberships to deliver appropriate content to web visitors.

    In this effort, I developed a specification for a system I could build relatively easily in FileMaker to use to spur discussion of features we need.

  • 5/17/2005 - College Intranet specification - We developed an RFP for our college Intranet web site project. The intro to that specification has links to all the relevent documents except a taxonomy driven navigation system we have decided to use instead of the flatter meta data driven navigation described in the RFP.
  • 5/12/2005 - My opinion of what an enterprise portal should do - My boss asked me about the relationship of our internet and our campus enterprise portal. This is my notes to her. I make the argument that portals should aggregate the front ends for an enterprise's computer systems & web sites. Because each portlet cannot contain enough of the computer systems interface, you still need the full web based interface as well. The admin system's portlet simply provides a very personalized and timely view of the most useful entry points for the systems a web visitor is likely to need.
  • 4/6/2005 - Guidelines for migrating files to FileMaker 7 - Many people on campus are migrating old databases to FileMaker 7 from earlier versions. This isn't a trivial process. In this response to the FileMaker List, I describe some huiristics for the process and particularly for deciding when it's worth hiring someone to help.
  • 4/2003 - Presentation about integrating Brio and Cold Fusion - We were working on developing an HR DataMart and delivering it with our campus' Brio infrastructure. In this process I identified problems with our current Brio infrastructure and how to address them. I also talk about the importance of using an application framework with Cold Fusion. [Architecture]
  • 8/25/04 - Requirements to integrate FileMaker 7 with Cornell's LDAP - Prior to going to the 2004 Devcon, I wanted to understand what it would take to integrate FileMaker with CU's Kerberos and Authorization Directory. This is the document that resulted.
  • 9/21/01 - College data delivery infrastructure - After I was hired (2/0/01), I wanted to develop a standard data delivery infrastructure for the college. I set some criteria, developed an example application and walk through, and delivered a presentation to relevant people from the college and campus. About 50 people attended. This infrastructure was based on FileMaker so I had the head of their Systems Engineering operation present about making FileMaker IT friendly. [Architecture]

 

Reporting and Data Analysis

  • 11/04 - Reporting Fractional Appointments - As more faculty are appointed accross department boundaries and we have to report on faculty in different ways, how we report their effort has become a bit of an issue. This was my position on the issue. As I post this (1/06) it is not entirely settled yet.

Some of the Projects Undertaken

  • 12/06 - Hired a programmer.

    Here is the relevent information about the Programmer Analyst III position. This position will report to Paul Davis.

  • 1/11/05 - Brio training and training site - After our team evaluated all the financial systems available on campus, we realized that our financial staff were under-utilizing Brio. I developed and delivered this training targeted at the needs of our financial staff.
  • 10/2003-3/04 - RFP and Vendor evaluation for public web site renewal - We decided we needed a new public web site. I was heavily involved in the RFP development and proposal evaluation.
  • 7/2003 - Dean's office Intranet - Starting in February of 2003 I lead a team to evaluate technologies and develop a plan for an intranet for the deans office. We selected Macro Media Contribute as the web CMS tool. The Intranet is located at intranet.engr.cornell.edu. We're currently in the process of building a college wide Intranet.
  • ~3/03 - Budget Web Site - To streamline the process of having the managers submit their budgets to the college we created a site for one stop shopping regarding budget matters. This site has information on "what you should be doing now", detailed instructions, and all the tools and resources they might need including links to relevant Brio reports, CPBS, etc.
  • ~3/03 - Budget Exceptions report - This custom Brio report allows department managers to review their work force planning data. The data submission tools the University provides do not offer much error checking so I developed this report to provide feedback on inconsistent data entry.
  • ~11/01 - Research Expenditure submission - We use Brio to gather research expenditure data, then departments correct the data in Excel and submit it to me where I use FileMaker to report on the data. This process has been improved each year.
  • ~11/02 - Course Data submission tool - We gather course, instructor and contact hour information in this FileMaker tool for reporting purposes. This tool has been improved each year.
  • ~4/01 - Salary Improvement Program tool - This tool was developed in FileMaker to gather information about people's raises. It's been updated each year.

Note: Older dates are very approximate. Items marked with a Kerberos key () are access restricted, either to Cornell employees or to a more restricted group.

 


Here is my resume

 

 
 
Maintained by Paul Davis   |   Last updated 2008-02-05
Cornell University Cornell University Cornell University College of Engineering