Integrating Project Server & SharePoint 2010Deployment Approaches, Integration Options & making the most of the SharePoint Enterprise FeaturesGiles HamsonSenior SharePoint / Project Server ArchitectCorporate Project Solutions
Session Objectives After attending this session you will understand the different
approaches to implementing SharePoint and Project Server together and the key benefits to each method.
In addition you will also takeaway: Understanding how SharePoint and Project Server work together Using the enterprise features of SharePoint to leverage Project
Server data How SharePoint and Project Server techniques differ and can cause
issues with implementation
Presenter Giles Hamson – Senior SharePoint / Project Server Architect
Implementing SharePoint solutions since 2004
Integrating Project Server with SharePoint since 2008 Social & Community
ghamson.wordpress.com
@ghamson
Agenda Brief history of Microsoft Project / Project Server Deployment approaches Integration and consistency Breaking the rules Questions
Windows ServerWindows
MS-DOS
1991 – Project for Windows1992 – Project 3.01993 – Project 4.01995 – Project 4.1a1998 – Project 98 (9.0)2000 – Project 2000 (10.0)2002 – Project 2002 (11.0)2003 – Project 2003 (12.0)2007 – Project 2007 (13.0)2010 – Project 2010 (14.0)
1984 – Project 1.01985 – Project 2.01986 – Project 3.01986 – Project 4.0
Mac1991 – Project1993 – Project 4.0
A Brief History
2000 – Project Central2002 – Project Server 2002 (STS 1.0)2003 – Project Server 2003 (WSS 2.0)2007 – Project Server 2007 (WSS 3.0)2010 – Project Server 2010 (SPS 2010)
Are SharePoint Server 2010 and Project Server 2010 integrated?
Deployment Approaches
1. Out of the box Project Web App Standard Project Web App (PWA)
Project Sites in the PWA Site Collection Risk, Issue, Deliverable lists Project Documents library
Pros Cons Project Team Sites created on
plan publish Integration with Project
Professional client
List data BI is limited to cube data
Risk / Issue roll ups including custom fields not easy without customisation
Changes made to future project site templates not added retrospectively
Site Content Types can be used but w/o SharePoint Designer Workflows
1. Out of the box
2. Separate site collection Standard Project Web App (PWA)
Project Sites under a separate Site Collection No coding required to user new site collection
Pros Cons Project Team Sites created on
plan publish Standard master page can be
changed to allow for custom design
Roll ups via Content Query Web Part
Site Content Types can be used with SharePoint Designer Workflows
Integration features break if custom content types used in standard PS2010 lists
Changes made to future project site templates are not added retrospectively
2. Separate site collection
3. Centralized lists Centralized soft data libraries and filtered dashboards for
“Project Sites” Using the enterprise features to connect to Project Server via the BDC and
ensure the plan GUID and associated metadata is tagged against all items All list items tagged with:
Project Programme Division
Standard Project Web App (PWA) Project Sites disabled
More development required Flexible approach but requires PM maturity
Ideal if requirements cannot be defined up front
Pros Cons Cross project, Programme &
Division based reporting becomes easier using standard features: List Views Filters Chart Web Part etc…
Changes made to lists and dashboard pages are across all projects / programmes new and old.
Integration features break because standard content types cannot be used* For customers mature in PM
practices where standard project sites are limiting.
Requires customisation to provide consistent look and feel
Standard SharePoint functionality problematic alerts, personal views, project /
programme based permissions.
3. Centralized lists
1. Out of the box 3. Centralized lists EPM and SharePoint
capability is new to the business
You can transition to separate site collections once maturity has been gained
Requirements for EPM are high level but project management maturity is high
Dashboards need to be created dynamically and used across all projects
2. Separate site collection
Requirements for EPM include workflow around soft data to support the business
Custom look and feel required for corporate style guidelines
Deployment approachesAll approaches are valid but which should be chosen?
Integration and consistency
Integration Project Server Interface (PSI)
Project Resource Timesheet+ others
Project Server Event Handlers (run on save and publish events) http://www.nintex.com/en-US/Products/Pages/NintexWorkflowForProjectServer2010.aspx
Project Server Workflows (Nintex & UMT offer WYSIWYG options) http://www.umt.com/products.aspx
Examples…
Caution Not all functions in Project
Server and Project Professional are available In particular baselines
Integration Examples Resource pool synchronization
ERP(Dynamics /
SAP)
CPS Resource Sync
(Scheduled)
Resource PSI(Project Server
Interface)Project Server
Integration Examples Timesheet population (contracted hours)
Resource PSIContracted Hours
JavaScript interacting with JSGrid Control& Status Bar
Integration Examples Timesheet population (contracted hours)
Consistent look & feel 1. Out of the box
The Master Page cannot be edited (not supported by Microsoft) SharePoint Designer 2010 will not connect to Project Web App
2. Separate site collection Site collection master page editable in project sites Project site owners can change the theme of project sites
3. Centralized lists Site collection master page editable in project sites Look and feel controlled by Administrator / Developer
So what can we do?
FeatureAdd jQuery / CSS
to AdditionalPageHea
d placeholder
Business intelligence Project Server has been built with BI in mind
Reporting Database Data from plans and standard project sites are available on the
publish of plans Almost real-time reporting of Plan, Resource and Timesheet data
Chart Web Part, Reporting Services, Excel Services, PowerPivot, Visio Services and list views can all be used to surface the data
Business intelligence
Reporting with Project Server 2010 Whitepaper: http://go.microsoft.com/fwlink/p/?LinkId=215299
Business intelligence
Reporting with Project Server 2010 Whitepaper: http://go.microsoft.com/fwlink/p/?LinkId=215299
Business intelligence Analysis Service Cube
Built to a schedule (Typically daily over night) Provides time phased reporting without any customisation Perfect for PerformancePoint (now included as standard as part of
SharePoint Server 2010 Enterprise), Chart Web Part and Analysis Services Filters
Business intelligence
Reporting with Project Server 2010 Whitepaper: http://go.microsoft.com/fwlink/p/?LinkId=215299
Performance I/O on the WFE server is a lot more intense than SharePoint
Memory usage due to PSI calls, Project & Timesheet queues All on top of SharePoint standard functionality
Disk I/O on SQL Server due to Save, Publish, Reporting Database BI Imagine hundreds of Project Managers hitting publish at once For each plan 3 databases are being saved to. Tens of thousands of rows
Performance If this sounds like an unlikely scenario…
Imagine timesheets linked to plans (Single Entry Mode). Timesheets entered and approved on a weekly basis. Plans should be up to date for Team Members to assign actuals
against planned work.
050
100150200250300350400450500
31-Ja
n-12
1-Fe
b-12
2-Fe
b-12
3-Fe
b-12
4-Fe
b-12
5-Fe
b-12
6-Fe
b-12
7-Fe
b-12
8-Fe
b-12
9-Fe
b-12
10-F
eb-1
2
11-F
eb-1
2
12-F
eb-1
2
13-F
eb-1
2
14-F
eb-1
2
15-F
eb-1
2
16-F
eb-1
2
17-F
eb-1
2
18-F
eb-1
2
19-F
eb-1
2
20-F
eb-1
2
21-F
eb-1
2
22-F
eb-1
2
23-F
eb-1
2
24-F
eb-1
2
25-F
eb-1
2
26-F
eb-1
2
27-F
eb-1
2
28-F
eb-1
2
29-F
eb-1
2
Number of Unique Visitors
Number of Unique Visitors
Performance To combat this:
Physical hardware or dedicated virtual hosts are recommended Virtualisation should not have stepped performance based on
demand. Ensure network performance between WFE and DB is fast Ensure I/O performance on SAN’s are optimum Ensure RAM and Processor is suitable for the task Follow Microsoft Best Practice on Project Server capacity planning:
http://technet.microsoft.com/en-us/library/ff686784.aspx
Breaking the rules
Breaking the rules Resource Pool
Users are not part of the User Profile service or even Active Directory
Display name must be unique and is used through out Project Server
Active Directory users are linked to a user resource An AD username can only be linked to a single resource NB: The AD username must exist to validate after June 2010 Cumulative
Update
Forms Based Authentication can be used but is known to have issues with certain web parts and is not recommended within PWA
Breaking the rules Permission Model
Completely separate to the SharePoint permission model
Special Project Server SharePoint groups are synchronised within the Project Site on every plan publish
If a user is on the project team (Build Team within the client), they are automatically assigned Team Member rights to the project site Team Member is typically a Contribute user within the Project Site
The owner of the plan is considered the Project Manager Project Managers have Owner access to the Project Site
Synchronisation process deletes and recreates rather than handling delta’s
Breaking the rules Browser Compatibility (Project Web App)
Officially IE7, IE8 only support at RTM SP1 introduced:
IE9 support Standard SharePoint browser support (Firefox 3.6+, Safari 4.0+, Chrome) for
team member functionality (My Reminders, My Risks & Issues, Task Updates & Timesheet Entry)
NB: This includes exporting out the web parts and placing them into a standard SharePoint site collection
http://technet.microsoft.com/en-us/library/ff631137.aspx
Project Web App cannot be customised using SharePoint Designer Changing the Master Page (although possible) is not supported in
Project ServerFeature
Add jQuery / CSS to AdditionalPageHead placeholder
Breaking the rules Plan integration with Team Sites
Feature stapled upon project site creation Feature creates:
Risk, Issue and Deliverable list My Risks and Issues & My Reminders web part dependant on list content
type, list name and column names NB: If names are changed within the list, functionality breaks
Project Documents library Applies event handlers code to lists update the Draft database with deliverable
details
Project Web App quick launch Managed by custom Project Server admin interface with changes
applied by a timer job upon save.
Conclusions
Takeaways Deployment approach 3 in
practice 8 Billion reasons why ARM chose
Project Server 2010 (Twitter: #PC301)
Each approach is valid but maturity assessments are required before implementation Project Management & Technology
Reporting is the key to a successful implementation with user adoption
Further Reading Project Server Capacity Planning:
http://technet.microsoft.com/en-us/library/ff686784.aspx
Plan Browser Compatibility: http://technet.microsoft.com/en-us
/library/ff631137.aspx
Reporting with Project Server 2010:
http://go.microsoft.com/fwlink/p/?LinkId=215299
www.msprojectconference.com
Your feedback is very important to us! You can fill out session evaluations by logging into MyPC on your laptop or mobile device
evaluation prizes daily
Should you win an evaluation prize, you may claim it at the Registration Desk on Level 3
MYPCfill out evaluations & win prizes!
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted
to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
PC324
Recommended
