Export (0) Print
Expand All

A feature/function comparison of Project Online and Project Server 2013

Project Server 2013
 

Applies to: Project Server 2013

Topic Last Modified: 2014-10-24

Summary:Compare the differences between Project Online and Project Server 2013 installed in an on-premises environment.

Project Online and Project Server 2013 on-premises are based on the same set of features and functionality, but there are differences between the two. The following table provides an overview of the differences between Project Online and a Project Server 2013 on-premises environment.

For more information about Project Online, see the following white paper: A Comprehensive Guide to Project Online (white paper) (by Emmanuel Fadullon, Principal Architect, Microsoft Consulting Services)

 

Feature/Function Area Feature/Function Details Project Online Project Server 2013 On-Premises Notes

Ease of Setup

Get started in minutes. Setup new users in seconds.

No training needed. Use Office tools your team knows.

99.9% Guaranteed Uptime

7x24, 365 days/year

43 minutes/month, 8 hours 46 minutes downtime per year.

Zero server footprint

No internal IT involved in backup/recovery, maintenance, updates, disaster recovery.

Evergreen service

Latest, most stable Service Packs and Cumulative Updates.

Multi-national

88 countries and regions, 32 languages.

For a list of countries and languages, see the FAQ at http://www.microsoft.com/en-us/office365/faqs.aspx#International_Availability

Work anywhere on any device

Get virtually anywhere-access on nearly any device (Access from mobile devices requires Wi-Fi capability or depends on carrier network availability).

Work on your Office files online or offline.

SharePoint Task Lists Sync

Notifications and Reminders

Administrative Backup & Restore

Project Professional for Office 365

Project Professional Characteristics:

Project Pro 2013 Access to Project Server 2013

Project Pro 2010 Access to Project Server 2013

Project Pro 2007 SP2 Access to Project Server 2013

Save as Project Pro 2010

Save as Project Pro 2007

Save as Project Pro 2000-2003

Save as Excel 2010

Save as Excel 2007

Save as Excel 97-2003

Save as PDF

Save as XPS

Save as Text

Save as CSV

Save as XML

Project Web App

Project Sites

Migration:

Manually Save 2003 .mpp from Project Pro 2013

Manually Save 2007 .mpp from Project Pro 2013

Manually Save 2010 .mpp from Project Pro 2013

Partial Automation through VBA custom dev

3rd Party:

  • FluentPro

Project Server Configuration Migration

  • Metalogix Content Matrix

Project Site Migration

  • MetaVis Migrator Online / Office 365 Suite

Project Site Migration

Project Server 2003

Step 1: Project Server 2003 to 2007 using VME (i.e. PS2007 SP2 w/ Oct 2009 CU)

Step 2a: Project Server 2007 to 2010 Database-attach Upgrade or Step 2b: Project Server 2007 to 2010 In-place Upgrade

Step 3: Project Server 2010 to 2013 Database-attach Upgrade

For more information about step 1, see Migrate your Project Server 2003 data by using the VME.

For more information about step 2a, see Project Server VME: Plan to upgrade data to Project Server 2010.

For more information about step 2b, see In-place upgrade to Project Server 2010.

For more information about step 3, see Upgrade to Project Server 2013.

Project Server 2007

Step 1a: Project Server 2007 to 2010 Database-attach Upgrade or Step 1b: Project Server 2007 to 2010 In-place Upgrade

Step 2: Project Server 2010 to 2013 Database-attach Upgrade

For more information about step 1a, see Database-attach full upgrade to Project Server 2010.

For more information about step 1b, see In-place upgrade to Project Server 2010.

For more information about step 2, see Upgrade to Project Server 2013.

Project Server 2010

Step 1: Project Server 2010 to 2013 Database-attach Upgrade

For more information, see Upgrade to Project Server 2013.

Resource Definition/Synchronization

Bulk upload via CVS

http://onlinehelp.microsoft.com/en-us/office365-enterprises/ff637601.aspx

Microsoft Online Services Directory Synchronization (with ADFS)

By using the Microsoft Online Services Directory Synchronization tool, your organization’s administrators can keep your local Active Directory continuously synchronized with Office 365. This allows you to not only create synchronized versions of each user.

For more details, see the Directory Synchronization Roadmap.

Manual resource definition

Tenant administration

Automation via VBA

3rd Party: FluentPro

Resource Migration

Business Intelligence

SSRS Integration

ODATA Access to RDB

For Project Online, note that there are limits to how many single-value custom fields, of each type, that get stored in the reporting schema. See Project Online: software boundaries and limits for more information on this and other limits that can affect performance.

NoteNote:
Refreshing OData reports through Excel Online is not available in Project Online for Government Cloud Community customers. To refresh reports so that they are viewable in Excel Online (browser-based), reports will have to be opened, refreshed and saved in the Microsoft Excel desktop client.

Direct Access to RDB

OLAP Cubes

ODATA Access to OLAP

T-SQL Access to OLAP

Excel 2007 Access to OLAP

Excel 2010 Access to OLAP

PowerPivot Add-in

Excel 2013 Services Access to OLAP

3rd Party: FluentPro

FluentPro Project Dashboard 2013

Demand Management/Workflow

Declarative – SharePoint Designer 2013

Currently workflows are not available in Project Online for Government Cloud Community customers.

Visual Studio WCF

Currently workflows are not available in Project Online for Government Cloud Community customers.

Line of Business Integration

Custom Dev with SharePoint BCS

Team Foundation Server Integration

Team Foundation Server 2012 integration with On-premise only

Dynamics Integration

Not yet available

SharePoint Online (Dedicated) integration

Project Server 2013 must be in the same farm as SharePoint 2013

On Premises SharePoint integration

Project Server 2013 must be in the same farm as SharePoint 2013

Outlook/Exchange Integration

Calendar: Out-of-office integration

Extensibility

ODATA

CSOM

Timesheet and Task Status

Simplified Single Entry Mode (SEM)

End-User Improvements

PM/Administrator Improvements

Developer/Backend Improvements

Status Reports

Data Privacy

http://trustoffice365.com/

No advertising

Office 365 does not build advertising products out of customer data. We do not scan your email or documents for building analytics, data mining, advertising, or improving the service.

No mingling

Office 365 always allows you to keep your customer data separate from consumer services.

Data portability

Office 365 customer data belongs to the customer. Customers can remove their data whenever they choose.

Transparency

Know where the major data centers are located, and how data storage location is determined. Detailed information on who can access your Office 365 customer data. Choose to receive updates regarding data center location changes, as well as security, privacy and audit information.

Industry Standards Verification

Certified for ISO 27001

Office 365 is the first major business productivity public cloud service to have implemented the rigorous set of physical, logical, process and management controls defined by ISO 27001.

EU Model Clauses

In addition to EU Safe Harbor, Office 365 is the first major business productivity public cloud service provider to sign the standard contractual clauses created by the European Union (“EU Model Clauses”) with all customers. EU Model Clauses address international transfer of data.

HIPAA-Business Associate Agreement (HIPAA-BAA)

Office 365 is the first major business productivity public cloud service provider to sign requirements for the HIPAA-BAA with all customers. HIPAA is a U.S. law that applies to healthcare entities that governs the use, disclosure and safeguarding of protected health information (PHI), and imposes requirements on covered entities to sign business associate agreements with their vendors that use and disclose PHI.

Federal Information Security Management Act (FISMA)

Office 365 for Enterprise was granted the Authority to Operate (ATO) under the Federal Information Security Management Act (FISMA) by the Broadcasting Board of Governors. Office 365-ITAR was granted ATO by the United States Department of Agriculture. Both Office 365 for Enterprise and O365-ITAR received FISMA-Moderate level ATO.

Data Processing Agreement

Microsoft offers a comprehensive standard Data Processing Agreement (DPA) to all customers. DPA addresses privacy, security and handling of customer data. Our standard Data Processing Agreement enables customers to comply with their local regulations.

Work Management Service

Performance Improvements

Browser:

http://technet.microsoft.com/en-us/library/ee683978

Internet Explorer 8

Internet Explorer 9

Internet Explorer 10

FireFox

Latest released version

Mac Safari

Latest released version

Google Chrome

Latest released version

Server-side scheduling engine

Microsoft Project Server Calculation Service 2013

SharePoint and Project App model

New Enterprise Project Types:

SharePoint Tasks List

Enterprise Project

Authentication and Authorization:

Claims Authentication

Classic Authentication

Office 365 Security:

http://www.microsoft.com/en-us/download/details.aspx?id=26647

Greater than 15 years of experience in providing security for online data

Secure Development Lifecycle

The Security Development Lifecycle (SDL) is a software development security assurance process consisting of security practices grouped by seven phases: training, requirements, design, implementation, verification, release, and response.

For more information, see Microsoft Security Development Lifecycle site.

5 Layers of Security

Moving productivity services to the cloud requires a serious consideration of security and privacy issues and technologies. Office 365 is designed to deliver the enterprise-grade security you require to move to the cloud with confidence. Our data centers are designed, built, and managed using a defense-in-depth strategy at both the physical and logical layers, and our services are engineered to be secure using the Security Development Lifecycle.

For more information, see the Security in Office 365 white paper.

Proactive Monitoring

Operations Access Restriction

Application Security:

http://technet.microsoft.com/en-us/library/fp161361.aspx

SharePoint Permissions Mode:

SharePoint Permission Mode creates SharePoint groups that directly correspond to the default security groups found in Project Permission Mode. In SharePoint Permission Mode, you cannot edit the default permissions assigned to any of these SharePoint groups. Also, you cannot create additional custom groups, categories, Resource Breakdown Structure (RBS) nodes, or edit the default permissions assigned to any of these objects. If you need more management of your user permissions in Project Server 2013, you can change to Project Permission Mode.

For more information, see Plan user access in Project Server 2013.

Unified security management through SharePoint Server

Permissions inheritance for PWA and Workspaces

Direct authorization against Active Directory security groups

Claims-based authorization

Manage authorization by role-based groups

Extensible and customizable

Project Server Permissions Mode:

http://technet.microsoft.com/en-us/library/cc197354.aspx

Claims-based authorization

Manage authorization by role-based groups

Extensible and customizable

User delegation

Ability to secure work resources

Impersonation

Security filtering using the Resource Breakdown Structure

Custom Security Categories

Microsoft Excel:

PWA Import to Excel 2013

PWA Import to Excel 2010

PWA Import to Excel 2007

Microsoft Word:

PWA Import to Word 2013

PWA Import to Word 2010

PWA Import to Word 2007

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft