Home » Currently Reading:

Tracer – MS Project Server Interface

Tracer_Small_Logo

 

 

Tracer has a bi-directional interface with MS Project Server to provide maximum flexibility in planning and scheduling a project. Projects can be defined either in Tracer or MS Project Server. Once a project has been identified as one that needs to be synchronized, the two tools automatically update each other. As a result, the power of MS Project Server can be used for defining tasks and their dependencies, as well as resource leveling and scheduling. Tracer’s power is the ability to track tasks and effort at the resource level as work is being performed.

 

  • Bi-Directional interface that SYNCHRONIZES MS PROJECT DETAIL with Tracer work events
  • MS Project Task assignments automatically show up on RESOURCE DASHBOARDS
  • Tracer’s interface LEVERAGES THE FUNCTIONALITY of MS Project for resource loading and scheduling

Project plans can be created within Tracer and uploaded into MS Project Server for load leveling and scheduling or project plans can be downloaded into Tracer from MS Project Server. Project plans can be created independent of  Tracer: resource assignment, estimating, successor / predecessor relationships, l0ad leveling and scheduling. The completed project plan can be imported into Tracer and all tasks will automatically be distributed to resource dashboards. Time is tracked against tasks and when tasks are closed in Tracer MS Project Server updated with all relevant data from Tracer. In this way Tracer and MS Project are always kept in sync.

 

If tasks are added, changed, deleted or resource task relationships changes in MS Project, all changes are automatically passed along to Tracer and are reflected “Immediately”on the individual resource dashboards. All metric reporting: Estimate / Actual, Earned Value. Performance Ratios and much more are automatically produced by Tracer. All standard reports produced by MS Project Server are now accurate and up-to-date as of the last synchronization (which can be done at any time).

MSPS Interface

 

Tracer keeps the MS Project Plan and Tracer data in sync – all tasks are tracked by resources on their individual task dashboard. Each resource can see if their tasks are on-schedule or late. Late task alerts can be automatically sent to the Project Manager. Project issues can be tracked within Tracer which communicate items that are delaying work. Issues are directed through alerts to those who are responsible for insuring issues are resolved in a timely manner.

Grater visibility of individual tasks throughout the project team helps insure that late tasks cannot go un-noticed by the resource or Project Manager.

 

MSPS Interface_B

Our Sponsors

IT Support Services Comments

  • Bob Anderson: Daniel, from a certain point of view you are correct. CMMI- DEV deals primarily with software development best practices, the old CMM Level-5 dealt a great deal with defects. However, as you know the ...
  • Bob Anderson: Gunter, there are many possible SLA components and metrics that can be defined for any application software support. First I would recommend that you read this article which I had published in Compute...
  • Bob Anderson: Amiet, I would put it under the "Incident" process and track dates, number of occurrences, how much lost time, cause (who did it). You will need data for management if the practice has to stop. If you...
  • Bob Anderson: Amit, first of all why is the customer powering down the equipment? This should be brought to the attention of management and a very strong note sent to whoever is doing this.  If they are doing it on...
  • Bob Anderson: Mark, it is doubtful that you can fix the problem, it is mainly a management issue. The best you can do is to gather statistics on the backlog of enhancements, the number and severity of incidents, an...

ITIL V3 Application Support Q & A

If you have any question on the blog content or have some specific question on how ITSM & ITIL can dramatically improve performance and reduce the cost of your Application Support service "Ask Bob"
Question :
Answer :
Gunter, there are many possible SLA components and metrics that can be defined for any application software support. First I would recommend that you read this article which I had published in Computer World on "How to create Meaningful IT Support SLA's"  use this link...
Question :
Answer :
Daniel, from a certain point of view you are correct. CMMI- DEV deals primarily with software development best practices, the old CMM Level-5 dealt a great deal with defects. However, as you know the folks who developed the original CMM  were not really initially inter...
Question :
Answer :
Amiet, I would put it under the "Incident" process and track dates, number of occurrences, how much lost time, cause (who did it). You will need data for management if the practice has to stop. If you want to be "proactive" in stopping this practice" you must capture bu...
Question :
Answer :
Mark, it is doubtful that you can fix the problem, it is mainly a management issue. The best you can do is to gather statistics on the backlog of enhancements, the number and severity of incidents, and how many technical support calls from users you get and the average...
Question :
Answer :
Amit, first of all why is the customer powering down the equipment? This should be brought to the attention of management and a very strong note sent to whoever is doing this.  If they are doing it on their own without any instruction to do so and it affects other user...