Buenas,
Volvemos a la carga con los “white papers”; y seguimos con Project Online 
. Esta vez es Emmanuel Fadullon, un Principal Consultant, el autor de esta guía, la cual puede descargarse del siguiente enlace:
A Comprehensive Guide to Project Online
La introducción es bastante explícita, y pensamos no está de más hacer una breve traducción, para que quien no pudiera estar familiarizado con algunos conceptos, empiece a tener las cosas más claras a este respecto:
Office 365 es una plataforma de servicios en la nube con “Software as a Service (SaaS)” que ofrece acceso desde cualquier lugar a aplicaciones de office, como el correo, calendario, video conferencias en alta definición, redes sociales empresariales, documentación actualizada, etc desde ordenadores, tabletas y/o teléfonos inteligentes. Project Online es el servicio en Office 365 del componente de de la Administración de la Cartera de Proyectos.
Con estos dos criterios claros: Office 365 y Project Online, ya estamos en condiciones de tener una idea más clara acerca del mundo “online” de Project. Las ventajas del mundo “online” sobre el “on-premise” (el que estamos acostumbrados de versiones anteriores, e incluso la última está disponible en este modelo) son las siguientes:
- Comienzo de uso rápido y sencillo
- 99.9% de disponibilidad
- Seguridad
- Ahorro en infraestructuras
- Actualización automática del sistema
En la siguiente tabla se ofrece una comparativa de las mejoras y novedades:
|
Feature/Function
|
New
|
Improved
|
Notes
|
|
User Interface
|
|
l
|
Simplified: reduced ribbon, add-line improvements
|
|
User Interaction
|
|
l
|
Carry-forward admin lines, grouping and sorting
|
|
Non-project time tracking
|
|
l
|
|
|
Filter categories by department
|
|
l
|
|
|
Control view defaults
|
|
l
|
Grouping and sorting, Always show admin categories
|
|
Timesheet managers list
|
|
l
|
Non-fixed approval routing
|
|
Close tasks for update
|
|
l
|
|
|
Log level manager
|
|
l
|
|
|
Eventing model
|
|
l
|
Feedback (OnUpdating, OnSubmitting)
Adjustment (OnReviewing, OnSubmitting)
|
|
Performance
|
|
l
|
|
|
Data Retention
|
|
l
|
|
|
Timesheet jobs out of queue
|
|
l
|
|
|
Work Management Service
|
l
|
|
Aggregate tasks centrally: view work and to-dos, newsfeed tasks caching
OOB task aggregation with SharePoint, Exchange and Project Server
No config options in Central Admin
Provider model implementation dependent to enable future integration of additional systems
|
|
Web Tier
|
|
l
|
Reduced Page load time
WAN optimizations
Direct Business Objects database queries for non-queue jobs
|
|
Application Tier
|
|
l
|
Queue service optimization
Reduced DB requests
AD Synchronization Improvements
|
|
Database Tier
|
|
l
|
Optimized security validation
Data transfer improvements (i.e. using Table Value Parameters)
SQL best practices (i.e. daily maintenance jobs)
|
|
Homepage
|
|
l
|
72% improvement of page load times
|
|
Project Schedule
|
|
l
|
90% improvement of page load times
|
|
Resource Center
|
|
l
|
71% improvement of page load times
|
|
Timesheet
|
|
l
|
50% improvement of page load times
|
|
Multi-browser support
|
l
|
|
Full PWA support for:
Internet Explorer 10, 9, 8
FireFox 10
Safari 5
Google Chrome 17
|
|
Server-side scheduling engine
|
l
|
|
Implemented as a Windows service - Microsoft Project Server Calculation Server 2013
On par with Project 2013 client scheduling engine
|
|
SharePoint and Project app model
|
l
|
|
An app is typically a self-contained, interactive program that performs a small number of related tasks
SharePoint applications no longer live in SharePoint. Within apps, SharePoint 2013 decouples server-side code from the server, enabling you to run server-side code from outside SharePoint, in the cloud
Custom code executes in the client, cloud or on-premises
Apps are granted permissions to SharePoint via OAuth
Apps communicate with SharePoint via REST / CSOM
Acquire apps via centralized Marketplace
Apps are for End Users
Cloud & Web-Oriented
|
|
SharePoint Tasks List Project
|
l
|
|
Team site is in control, tasks are managed in SharePoint
Enterprise Project Type
This is when Project Server has full control of the Projects and Tasks
|
|
New “grow-up” mode
|
l
|
|
|
|
Activate/Deactivate PPM Features
|
l
|
|
|
|
Connected SharePoint Site
|
l
|
|
|
|
Authentication and Authorization
|
l
|
|
Default is Claims authentication
Claims authentication cookie (“FedAuth” cookie) is tracked at the Distributed Cache Service level
Classic authentication enabled via Windows PowerShell (not through UI)
No need to re-authenticate at each WFE like in SharePoint 2010
|
|
SharePoint Permission Mode
|
l
|
|
SharePoint Permissions Mode:
Permissions managed in SharePoint
Resources managed in Project Server
Project Server Permissions Mode:
Permissions and Resources managed in Project Server
Default for upgraded sites
|
La comparativa entre Project Online y “On-premises” es muy larga para copiarla aquí, pero os recomendamos le echéis un vistazo, porque os va a aclarar las posibles dudas que pudierais tener al respecto. El documento está lleno de referencias a artículos e información disponible, toda ella muy relevante y actualizada.
No hemos podido resistir la tentación de incluir los siguientes diagramas de flujo:
Lo mismo para esta tabla, relativa a escenarios de migración:
|
Scenario
|
Project Server 2007
|
Project Server 2010
|
Project Online
|
|
On-premises Project Server 2013
|
N/A
|
N/A
|
Migrate
|
|
Existing hosted 2010 customers
|
N/A
|
Migrate
|
Migrate
|
|
Existing 2007 customers
|
N/A
|
Upgrade
|
Migrate
|
|
Existing 2003 customers
|
Upgrade
|
Upgrade
|
Migrate
|
|
Project Desktop only customers
|
N/A
|
N/A
|
N/A
|
|
New customers
|
N/A
|
N/A
|
Subscribe
|
|
Existing 2010 customers
|
N/A
|
N/A
|
Migrate
|
Esperamos os resulte de interés, y resuelva las posibles dudas que os pudieran quedar con este tema.
Un saludo
Jorge Puig
