projectified

T-SQL for Returning Tasks Scheduled to Start within 7 Days

This is just a snippet of T-SQL to return the Project Name, Task Name, Task Start, and Task Finish dates for all tasks in the Project Server Reporting Database that are scheduled to start between the current SQL Server system time and the current system time plus 7 days.

The core of this is really just the use of SysDateTime and the DateAdd functions. Other than that it is a very basic query.

This gets asked for every once in a while so I will put it out here for those searching.

 

   1: SELECT     MSP_EpmProject_UserView.ProjectName, MSP_EpmTask_UserView.TaskName, 

   2:            MSP_EpmTask_UserView.TaskStartDate,MSP_EpmTask_UserView.TaskFinishDate

   3: FROM         MSP_EpmProject_UserView INNER JOIN

   4:                       MSP_EpmTask_UserView ON MSP_EpmProject_UserView.ProjectUID = 

   5:                       MSP_EpmTask_UserView.ProjectUID

   6: WHERE     (MSP_EpmTask_UserView.TaskStartDate > sysdatetime()) AND 

   7:           (MSP_EpmTask_UserView.TaskStartDate < DATEADD(dd, 7, sysdatetime()))

Groups and Categories

This is something I posted over on my Microsoft blog a while back but it comes up so often that I wanted to repost it over here.

Project Server security is something that is very flexible once you get used to how it works but it can be a bit confusing when you first look at it.

Here are the basics as I explain them to my customers:

The Group

Groups contain sets of users and they define the system level permissions that those users have the rights to perform. These include: Logging in, performing certain admin functions, create a new project, create a new resource, etc..

The Category

Categories provide access to projects, resources and views. The projects and resources that the category provides access to can be specifically called out by name or they can by dynamically included based on a set of rules within the category itself. For example a category can provide access to all projects where the user is the project owner or a status manager on a task, or all the projects where the Project Owner is ‘below’ the user in the RBS structure. I refer to this set of projects and resources as the “Scope” of the category.

Categories can be shared by many groups because of the dynamic way the scopes can be defined. The dynamic options for project and resource scope are dependent on the user and their relationship (via the RBS structure) to either the owner or team members on a project or to the resources themselves. I often, for simplicity, create a role based group and then a corresponding category. It sometimes means that there are technically more categories than is absolutely required but it does make the whole security model a bit easier to follow.

 

The Group\Category Permissions

This is the part that people often overlook.

A group and a category can be ‘linked’ or joined. When this happens there is a set of permissions that sit at that joint. This set of permissions defines what the members of that group can DO with the projects and resources within the “Scope” of the category.

If you open a Group and you see the list of Categories that are associated to group there is one of these grids for each category. If you select one of the Categories associated with the group the grid pertains to THAT pairing of group and category. If you select a different category the grid changes and is now pertaining only to THAT pairing. The same is true if you open a category and select the Groups that are associated with it. The grid pertains to the pairing. It can be edited in both places but it remains the same.

Deployment Practices: Required Fields

Few things are more frustrating then using a system and being presented with a field you MUST fill in to continue at a time when you don’t know which value is appropriate for that field. Project Server is no exception.

You can make any enterprise custom field in Project Server a required field. At the project level this means that a project cannot be saved until each of these fields contains a value. This is great if you know for sure that the project manager will always know which value to pick from the list at the time they first save their project. But if they don’t you have a couple of things that are going to happen and you need to be prepared for them and decide if they are your intended consequences.

1. The project manager will NOT save their project until they find the answer (remember that the answer COULD be several days away.) Do you really want the PM to NOT save the project because they don’t have the answer to this one field? Where will they start their planning in the mean time? Where will their data go?
2. The project manager will pick one of the values from the list just so they can save the project even if that value is not right. Remember that they may not remember to come back and fix it when they have the right information!
3. The project manager will curse you (the administrator) and pray to their God that you be injured in some way very soon.

Number 3 is going to happen for sure, count on it. What you have to decide is if you want number 1 or number 2 to be happening while your curse\injury takes place. The easy way to avoid all three is to either NOT make fields required unless you 100% sure that the project manager will know which value pertains to their project OR provide them a “Not Yet Known” value in the lookup table.

I tend to prefer the “NOT YET KNOWN” option. It allows your views and reports to show which projects have complete field profiles and which projects are in need of more complete data. Just make sure that the people you have creating reports and views know to allow for this value in their filters. This means that if you want to show all projects where a field equals “X”  or “Y” that it should also contain projects where it equals “Not Yet Known” because those projects MIGHT be "X” or “Y”, we just don’t know yet. :-)

 

Technorati Tags: Project Server,EPM

Deployment Practices: Why Resource Max Units Should Never Be 100%

Reason number one is that in all but the most extraordinary situations it is modeling a situation that is just not possible.

But first some background on what Max Units really is. Max Units defines the percentage of a resource’s full calendar working “period” that they can be assigned to work on tasks before Project sees them as being over-allocated.

Example:
A resource’s calendar says they come in at 8am and work until 5pm and take a 1 hour lunch. They do this Monday – Friday. That is an 8 hour work day\40 hour work week. So if the Max Units is 100% then if the resource is assigned to work 9 hours in one day they will be seen as over-allocated. Same for if they are assigned to work on 2, 1 hour tasks during the same hour. This goes down to the minute level too so if two 1 hour tasks overlap by 1 minute then for that 1 minute they are over-allocated.

This helps the PM create models of assignments and get an idea of how many hours each team member is being assigned to tasks and how that falls across time, other assignments, etc.

So now you might be seeing what is wrong with 100% Max Units. It says that if I work an 8 hour day, I am available to work 8 hours on tasks. On it’s face this sounds logical but dive a little deeper and it becomes obvious that this is just not possible. Nobody ever arrived at work at 8am, took a 1 hour lunch, and then left promptly at 5pm AND got 8 hours of work done on tasks. EVER.

OK wait, I take it back. It is possible that someone did this on your project:  IF your project schedule has tasks for things like: going to the bathroom, answering non-project related emails, going to a company meeting, being tapped on the shoulder by your cube-neighbor and being asked for “just a quick 5 mins. of help” (that turned into 30 mins), the list goes on and on. So if your project contains a task for every possible distraction from YOUR project and you expect your resources to track all of that then never mind. You can set your Max Units to 100%. (just count on a lot of churn on your team.)

But for most of us it is not possible to work 8 full hours on PROJECT WORK in an 8 hour day. Doing so means that you were present for more than 8 hours so that all the other things had time in your day along side your real work. The best way to help our models (because that what project schedules really are: models of what we want our project work to look like) be more accurate is to lower Max Units to something more like 85%. That would be the highest I would ever go on any project I was managing. I have seen it set as low as 75% at some sites but generally I see 80-85%.

What this means is that if you have a 1 day duration task and you assign a resource that has an 85% Max Units value, Project will calculate the Work for that task to be 6.8 hours. This means that you are modeling that on average this resource spends 1.2 hours of their 8  hour day doing something OTHER THAN working on your project. A Max Units value of 75% means that 2 hours is spent doing other things. Of course some will get more than 6.8 done in a day and some will get less done. It depends on the nature of their job, their relationship with other projects, other teams, etc. So the value you set will never be perfectly accurate but it WILL certainly be MORE accurate than 100% which is nearly always wrong. The point here is to make your model as accurate as you can.

 

____________________________________________________________

I’m hoping to start a small series of Deployment Practices posts here covering things I have found to be useful ideas, practices or methods for deploying Project Server. Please email me if you have suggestions or questions.

Technorati Tags: Project Server,Resource Management,EPM

Cool Sample PSI Apps and OLAP Info

Chris Boyd and Brian Smith do it again.

Check here for two cool sample applications, one for showing how to create, read and update custom fields via the PSI and another used for reading custom field data and then publishing projects, again via the PSI.

Check here for good info about OLAP cubes, Data Analysis (timeouts, plan guides and the tempdb)

Project and Project Server SP1 Are Here!

The haters should note the date please. :-)

This TechNet article covers the how to (Read it before you update):

http://technet2.microsoft.com/Office/en-us/library/c3b86049-7cba-4b9c-8335-e37fb6e7518a1033.mspx?mfr=true

Here is WSS SP1:
http://www.microsoft.com/downloads/details.aspx?FamilyId=4191A531-A2E9-45E4-B71E-5B0B17108BD2&displaylang=en

Here is Office Servers SP1 (which includes Project Server and Office SharePoint Server):
http://www.microsoft.com/downloads/details.aspx?FamilyID=ad59175c-ad6a-4027-8c2f-db25322f791b&DisplayLang=en

Here is Project 2007 SP1:
http://www.microsoft.com/downloads/details.aspx?FamilyID=CEC3E1E2-D802-4A03-BC78-05C48472559B&displayLang=en

Here is the Project Server MUI SP1:
http://www.microsoft.com/downloads/details.aspx?FamilyId=D322BA67-B199-4503-8AFF-6813B320D708&displaylang=en

Here is the Office Server MUI SP1:
http://www.microsoft.com/downloads/details.aspx?FamilyId=3A6C26FD-0BEB-40D5-8CBA-15164FAAB150&displaylang=en

And for Good Measure here is the Office 2007 SP1 download:
http://www.microsoft.com/downloads/details.aspx?FamilyId=9EC51594-992C-4165-A997-25DA01F388F5&displaylang=en

Programmatic Access to Enterprise Custom Fields in Project Server 2007

If you have poked around VBA in Project Professional 2007 you may have noticed that there is not what I would call "direct" object model access to the enterprise custom fields you create in Project Server 2007. For one thing these fields are not like they were in Project Server 2003. In 2003 you got 30 Outline Code fields and you renamed them but via VBA you still accessed the field as OutlineCodeXX. In 2007 you create enterprise fields 'from scratch.' They are not just renamed fields. They are new fields. The object model is not dynamic in a way that allows it to add new members as they are created. This means that you cant just get to a field by the old method: Activeproject.Tasks(1).OutlineCode1.

To access an Enterprise Task field called "Task Alignment" you would use the following code:

Activeproject.Tasks(1).GetField(FieldID:=Application.FieldNameToFieldConstant(FieldName:="INSERT FIELD NAME),FieldType:=pjTask)

You use the GetField method. This method requires the FieldID. To get the FieldID (since it is unlikely you know it) you use the FieldNametoFieldConstant method.

Default Assignment Owner

There are situations where the team members that are doing the actual work on tasks do not have ready access to a computer. This makes their use of Project Server Web Access to report status on their task assignments impossible or at least highly unlikely. In the past situations like this would require assigning the tasks to a supervisor and then having the supervisor submit status for the resources. But this was not a great solution as it obscured the usage levels of the actual resources and was confusing for the supervisor to keep track of who was assigned to any given task. Project Server 2007 adds a feature that makes this kind of situation much easier to handle.

Every Assignment on a project in Project Server has a property called "Assignment Owner" that contains the name of the Project Server user that will be entering status updates for that assignment. If the Assignment Owner for an assignment is "Brian Kennemer" then it will show up on my "My Tasks" page in PWA. Every resource in Project Server has a property called "Default Assignment Owner." This property defines the default name that is put into the Assignment Owner field when that resource is assigned to a task. By default it is the name of the resource but you can put any active user into the field for a resource. So in our situation above the solution would be to put the name of the supervisor into the Default Assignment Owner field for each of their team members. Then whenever a task is assigned to one of the team members that assignment will show up on the My Tasks page of the supervisor.

With this solution the tasks are assigned to actual team members so their usage and availability can be accurately tracked and the assignments show up on the supervisors My Tasks page for easy status updates (the name of the assigned resource shows up in the view to help the supervisor keep track.)

If you have this situation in your deployment look into this feature. If you need a hand drop me an email.

And Circle Gets the Square!

Wow it has been a long time since I have posted. I would love to say that I have not had a free minute as an excuse but sadly I have had free minutes, not many but I have and I used them on my family instead of writing blog entries. Sue me. :-)

Some highlights since I last posted:

• Microsoft Office Project 2007 and Microsoft Office Project Server 2007 have shipped (along with the slightly less important to me personally: Office 2007 and a little product called Vista)
• I have been doing the technical editing\reviewing for several of the new books that will be coming out about Project 2007 and they are looking good. I’m doing one on SharePoint now and will have at least one more about Project and then one about Project Server that I will be working on later. I will let you know when they ship
• I have been working on some cool projects internal to Microsoft in the RPM space and on deploying Project Server to a few internal groups. Very fun stuff.

The biggest deal for me is that I submitted a paper to the Bill Gates ThinkWeek process and it was not only accepted but also read and commented on by Bill himself! There are over a 1000 submitted and only a handful are selected to be read by the broader ThinkWeek working group and an even smaller number are read by Bill and an even smaller number actually get feedback from Bill. So needless to say I was pretty excited. While I cannot comment publically about the exact subject of the  paper suffice to say that it is about Project Server and it was well received. :-) It got the right group of people talking about the right subjects and it increased visibility of the product and it’s role. Exactly what I hoped it would do!

For those that do not know what ThinkWeek is:

What is "think week"? It is a week that BillG sets aside roughly every six months to think deeply about a range of topics impacting our company and the industry. Microsoft full time employees are encouraged to submit papers for think week - topics for the papers are broad ranging: new product ideas, promising research, trends that will affect Microsoft or the software industry, explanations of new technologies, suggestions for improving product development, etc.

It has been a very productive couple of months, just not in terms of the “blog posts per week” metric I used to use! :-)

Did I hear you ask for more custom fields?

Project Server 2007 makes a major change to the way that enterprise custom fields are handled. Instead of being tied to a limited set of fields (Enterprise Text1, Enterprise Text2, etc.) the new system starts with basically no custom fields and you get to add as may as you want.

The interface allows you to add a new field and that new field has several attributes that include:

• Entity (Project, Task or Resource)
• Type (Cost, Date, Flag, Duration, Number and Text)
• Summary rollup
• Whether the field will use a Lookup Table or a formula or be 'hand entered'
• Assignment 'Roll down'
• If the field will display it's value or Graphical Indicators
• If the field will be required to contain a value

Notice that Type does not include "Outline Code". There will no longer be an field type called outline code. Since any field can have a hierarchical lookup table like Project Server 2003 outline codes essentially in 2007 any enterprise custom field can be an 'outline code'.

Lookup Tables are created independently of the fields themselves which makes sharing them between fields much easier.

This brings us to the question you are likely asking yourself now: if there are no enterprise outline codes then how does the OLAP cube get user defined dimensions? Well I'm glad you asked me that...

Any Project, Resource or Task enterprise custom field can be a dimension! (Yes ANY!) There is a Cube Configuration page that allows you to pick from your defined custom fields and decide which ones should be OLAP Cube dimensions. Ready for part two of that? Any Project, Resource or Task enterprise Cost, Number or Duration field can be a measure in the cube as well. These get defined in a central page and then show up as available for any Data Analysis view (Data Analysis is what Portfolio Analyzer views are called in Project Server 2007).

Oh and all the custom field customizations happen directly in Project Web Access.

Very cool stuff coming.

Tags: project 2007, project server 2007