Page tree
Skip to end of metadata
Go to start of metadata

If you aren't already familiar with what a data set is, please see AAM Data Sets. If you are familiar with them, then this help document introduces the base data sets, which data sources feed them, and why each was chosen. Projector chose these data sets based on the fact that most organizations will find them useful either as is, or with some tweaks to fit their business model.

Permissions and Settings

Most AAM data sets are fed by Projector reports. These reports are on the Reports tab of Management Portal in the Public area of Projector and prepended with AAM-. When building your own data sources, it is useful to keep this naming nomenclature. If you cannot find them, make sure you have hidden reports shown.

These reports need to be manually scheduled according to our AAM Initial Configuration guide. Scheduled reports cannot be public, so the "real" reports are likely associated with the user account of your AAM administrator.

To see the data sets in AAM, visit https://aam.projectorpsa.com/bi/datamodel. Only the AAM administrator can see all data sets by default. If you cannot see the datasets, ask your administrator to make sure you have the Data Manager role and that the data sets are shared to you.

AAM-AuditTrail

Tells you about clients, projects, and users that have been added to Projector and who added them.

InfoDescription
Data set nameAAM-AuditTrail
Projector Reports
  • AAM-AuditTrailClientsCreated (audit trail)
  • AAM-AuditTrailProjectsCreated (audit trail)
  • AAM-AuditTrailUsersCreated (audit trail)
Date rangePrevious 7 days
Import ScheduleNightly
Overwrite PolicyDelete all rows in data set w/ Apply on data from this data source only
NotesWe use an import template to change the report into human readable format. For example, "Tom created a new project called P001000-001 on April 1, 2015 at 12:05:01 pm."

AAM-Expenses

Used to analyze your unreimbursed expenses, operating costs, cost revenue, etc.

InfoDescription
Data set nameAAM-Expenses
Projector Reports (type)
  • AAM-Expenses (cost card)
Date rangeCurrent quarter
Import ScheduleNightly
Overwrite PolicyDelete all rows in data set w/ Apply on data from this data source only
Notes 

AAM-GinsuByMonth

Full year revenue analysis.

InfoDescription
Data set nameAAM-GinsuByYear 
Projector Reports
  • AAM-GinsuByMonthLastYear
  • AAM-GinsuByMonthThisYear
Date rangeLast and this year
Import ScheduleMonthly
Overwrite PolicyDelete all rows in data set w/ Apply on data from this data source only
Notes 

AAM-GinsuByWeek

Staffing, capacity planning, and revenue projections. 

InfoDescription
Data set name AAM-GinsuByWeek
Projector Reports
  •  AAM-GinsuByWeek
Date rangePrevious and next 13 weeks
Import ScheduleWeekly
Overwrite PolicyDelete all rows in data set
NotesThis data set does not have any reports built directly off of it. Rather, it is combined with the AAM-ProjectList report to create JD-GinsuByWeekWithProjectDetails (see further down).

AAM-Invoices

Unpaid invoices, outstanding AR, and pending invoices

InfoDescription
Data set nameAAM-Invoices
Projector Reports
  • AAM-Invoices
Date rangeAll dates
Import ScheduleWeekly
Overwrite PolicyDelete all rows in data set
Notes 

AAM-Issues

Project workspace issues for currently open projects.

InfoDescription
Data set nameAAM-Issues
Projector Reports
  • AAM-Issues
Date rangeAll dates
Import ScheduleNightly
Overwrite PolicyDelete all rows in data set
Notes 

AAM-MissingTime

Analyze missing time on a historical basis to identify trends.

InfoDescription
Data set nameAAM-MissingTime
Projector Reports
  • AAM-MissingTime
Date rangeLast Week
Import ScheduleWeekly
Overwrite PolicyAppend rows to data set
Notes 

 

AAM-ProjectList

A core data set that includes tons of information about a project. It does not have any reports designed directly off it. Rather, it is joined with data sets like the AAM-GinsuByWeek. By joining it, we take a data-centric report like the Ginsu and expand its scope to include everything about your engagements too.

InfoDescription
Data set nameAAM-ProjectList
Projector Reports
  • AAM-ProjectList (imported twice)
Date rangeNot applicable
Import ScheduleWeekly
Overwrite PolicyDelete all rows in data set w/ Apply on data from this data source only
ReportsThis data set does not have any reports built directly off of it. Rather, it is combined with the AAM-GinsuByWeek report to create JD-GinsuByWeekWithProjectDetails (see further down).
Notes

You may notice that this data set has two data sources. And the data source for each is exactly the same. Why is it set up this way? The difference between these two data sources is the import template used. The "Project List" template includes all project level data. The "Engagement List" template only gets engagement level data. The reason for this has to do with the other data sets that tend to be joined onto AAM-ProjectList. If your Ginsu report contains revenue that exists only at the contract line item level (because there are no actual or booked hours on the project), then joining the Ginsu by project code to this report would cause that revenue to go missing. To prevent this, we instead do the join on a unique attribute called UID-PL.

  • Engagement Level Revenue: P001000|P001000-CL1|(No-Project)
  • Project Level Revenue: P001000|P001000-CL1|(P001000-001)

AAM-ProjectPortfolioPerformance

Looks at projects from beginning to end and generates performance metrics about them.

InfoDescription
Data set nameAAM-ProjectPortfolioPerformance
Projector ReportsAAM-ProjectPortfolioPerformance (project portfolio report)
Date rangeNot applicable
Import ScheduleWeekly
Overwrite PolicyDelete all rows in data set
NotesInformation on all projects that are open, or were open as of thirty days ago

BD-Targets

This is the only default data set that does not come from Projector itself. You are responsible for filling in your revenue targets (whether that be by month, week, year, etc). It is then used to see how well you perform against those targets. 

InfoDescription
Data set nameBD-Targets
Projector ReportsNot applicable. This data does not come from Projector. It comes from a data source of your own determination.
Date rangeYou enter your targets as far into the future as you wish
Import ScheduleDetermined by your organization
Overwrite PolicyYou determine what data remains in the table
Notes 

JD-GinsuByWeekWithProjectDetails

This data set is the result of joining two other data sets. It takes a data set that is somewhat specific, AAM-GinsuByWeek, and then joins it with the AAM-ProjectList data set. The result is a very wide table with lots of attributes and metrics available.

InfoDescription
Data set nameJD-GinsuByWeekWithProjectDetails
Projector ReportsNot applicable (this is a join of AAM-GinsuByWeek and AAM-ProjectList)
Date range+/- 13 weeks
Import ScheduleNot applicable
Overwrite PolicyNot applicable
Notes 

JD-ProjectPortfolioPerformanceWithProjectDetails

This data set is the result of joining two other data sets. It takes a report that contains lots of metrics about a project, AAM-ProjectPortfolioPerformance, and then joins it with the AAM-ProjectList data set. The result is a very wide table with lots of attributes and metrics available.

InfoDescription
Data set nameJD-ProjectPortfolioPerofrmanceWithProjectDetails
Projector ReportsNot applicable (this is a join of AAM-ProjectPortfolioPerformance and AAM-ProjectList)
Date rangeNot applicable
Import ScheduleNot applicable
Overwrite PolicyNot applicable
Notes 

 

JD-GinsuByMonthWithProjectDetails

This data set is the result of joining two other data sets. It takes a data set that is somewhat specific, AAM-GinsuByMonth, and then joins it with the AAM-ProjectList data set. The result is a very wide table with lots of attributes and metrics available.

InfoDescription
Data set nameJD-GinsuByMonthWithProjectDetails
Projector ReportsNot applicable (this is a join of AAM-GinsuByMonth and AAM-ProjectList)
Date RangeNot applicable
Import ScheduleNot applicable
Overwrite PolicyNot applicable
Notes 


 

Table of Contents
  • No labels