Revenue Management Application / Pricing

What are the technical specifications for RMA?

A. Freeman — Thu, 09 Nov 2017 00:11:01 GMT

Current Revision posted to Revenue Management Application / Pricing by A. Freeman on 11/9/2017 12:11:01 AM

The minimum requirements for RMA are the same as for T-Stats. If your current T-Stats server (and workstations using T-Stats) meet the minimum specs for T-Stats for an organization of your size, they should be adequate for RMA. RMA adds additional components to the existing T-Stats data warehouse to support the RMA. The RMA data loads as part of the nightly T-Stats load job, and thus adds some time to the duration of that run. However, that time is usually comparatively small to the overall duration of the T-Stats load, but of course varies based on the actual data and server involved.

The Software and Hardware Requirements are included in the T-Stats Installation Guide in Chapter 2.1: Software and Hardware Requirements.

RMA is currently compatible with both T-Stats v4.5 and Tessitura v12.5.1.

Revenue Management Application / Pricing

Anonymous — Mon, 09 Oct 2017 15:07:31 GMT

Current Revision posted to Revenue Management Application / Pricing by Anonymous on 10/9/2017 3:07:31 PM

I need help with the RMA!

Chris Wallingford — Fri, 04 Nov 2016 13:24:02 GMT

Current Revision posted to Revenue Management Application / Pricing by Chris Wallingford on 11/4/2016 1:24:02 PM

If you are looking for technical assistance for the Revenue Management Application, please e-mail RMA@jcainc.com for prompt and helpful support.

Help resources are also available at www.RevenueManagementApplication.com

I need help with the RMA!

Chris Wallingford — Fri, 04 Nov 2016 13:23:24 GMT

Revision 2 posted to Revenue Management Application / Pricing by Chris Wallingford on 11/4/2016 1:23:24 PM

If you are looking for technical assistance for the Revenue Management Application, please e-mail RMA@jcainc.com for prompt and helpful support.

Help resources are also available at [[www.RevenueManagementApplication.com|www.RevenueManagementApplication.com]]

I need help with the RMA!

A. Freeman — Tue, 01 Apr 2014 11:04:19 GMT

Revision 1 posted to Revenue Management Application / Pricing by A. Freeman on 4/1/2014 11:04:19 AM

If you are looking for technical assistance for the Revenue Management Application, please e-mail RMA@jcainc.com for prompt and helpful support.

How are "on sale" dates determined in the RMA?

Chris Wallingford — Wed, 03 Apr 2013 14:01:42 GMT

Revision 4 posted to Revenue Management Application / Pricing by Chris Wallingford on 4/3/2013 2:01:42 PM

Some RMA reports look at the time between when a ticket was purchased, and when tickets went on sale. For example:

* Opening and Closing Sales Curve
* Sales Curve by Weeks After On-Sale

By default, the RMA looks at your Tessitura price maps for the performance, and uses the earliest starting date it finds. The RMA is dependent upon price map start dates in general for monitoring pricing and the on sale date is no exception to that practice. If however, this landmark is not acceptable for your organization's business rules, then it is possible to customize how the RMA determines your on sale dates.

There is a moment in time when tickets go from not being on sale to being on sale. How do you control when that time is? If it's not the earliest starting price map, is it the start date on a particular price map on a particular price type, or is it the start date on a particular mode of sale, or is it the performances' "web publish dates", or something else? Whatever it is, you can use the following two step process to customize the RMA to fit your business logic.

1. Add the @load_use_local_onsale_date=1 parameter to their RMA load job
2. Edit the [TPI].[LocalLoadOnsaleDates] stored procedure (which includes sample code for the default method) to use whatever default start date you need.

Sample code using Publish Client Date:

declare @perf_onsale table (perf_no int, onsale_dt datetime)
insert into @perf_onsale
select perf_no, convert(datetime,convert(char(10),min(publish_client_start),120))
from [production tessitura server].impresario.dbo.t_perf
group by perf_no
order by perf_no

update a
set a.onsale_dt=b.onsale_dt
from TPI.PSAM_ZONEPT a
join @perf_onsale b on a.perf_no=b.perf_no
where @division_str is null or division is null or charindex(',' + convert(varchar,division) + ',',',' + @division_str + ',') > 0

What are the technical specifications for RMA?

Chris Wallingford — Tue, 12 Mar 2013 10:59:43 GMT

Revision 2 posted to Revenue Management Application / Pricing by Chris Wallingford on 3/12/2013 10:59:43 AM

The Software and Hardware Requirements are included in the T-Stats Installation Guide in Chapter 2.1: Software and Hardware Requirements.

RMA is currently compatible with both T-Stats v2 and T-Stats v3, as well as Tessitura versions 10 and 11.

How are "on sale" dates determined in the RMA?

A. Freeman — Tue, 05 Mar 2013 12:00:46 GMT

Revision 3 posted to Revenue Management Application / Pricing by A. Freeman on 3/5/2013 12:00:46 PM

Some RMA reports look at the time between when a ticket was purchased, and when tickets went on sale. For example:

Opening and Closing Sales Curve
Sales Curve by Weeks After On-Sale

Add the @load_use_local_onsale_date=1 parameter to their RMA load job
Edit the [TPI].[LocalLoadOnsaleDates] stored procedure (which includes sample code for the default method) to use whatever default start date you need.

Why doesn't RMA match my Tessitura report?

A. Freeman — Tue, 26 Feb 2013 13:01:03 GMT

Revision 7 posted to Revenue Management Application / Pricing by A. Freeman on 2/26/2013 1:01:03 PM

General Reasons

Double check your Tessitura report parameters against your RMA report filters.
Check your RMA SQL Job Load parameters for the exclusion of certain price categories.
Is the Tessitura report in question a custom report? Depending on the details of the custom code behind the report, it may be that the report is coded to filter out items which are not being filtered in RMA.
RMA deals with inventory, and thus to it, a donated (not yet resold) seat is an available seat; it is currently empty and thus for the purposes of inventory analysis is treated as available.

Troubleshooting

In the RMA, from the Price Type Reports folder, run the Average Sales by Price Type report.
- On the filters tab, add a Season filter and select only the season in question
- On the groupings tab, set the x axis level 1 grouping to Production Season
- Set the x axis level 2 grouping to Unique Performance
- Set the y axis level 1 grouping to Price Type Category
- Save and View the report
- With the report open, then from the View menu select Source Data, click the Copy to Clipboard button and paste it into Excel.
From Tessitura run the Performance Sales Summary by PT Category report for one Season – preferably a past season in which sales are not occurring so that you are not comparing a moving target.
- Set the Performance Start and End dates to include all the performances in the season
- Set Mode Summary for now
- Set Season to the Season in question
- Group By Event
- Do not set a historical date
- Set Include Resold Seats to No

From Tessitura run the Donated Seats report for the same season.
- Group by Performance

Review the amounts for each price type category in the Performance Sales Summary by PT Category report. Subtract seats that have been donated for resale. You can also use T-Stats to identify those seats that are donated for resale and organize them by price type category for a direct comparison. The variance between the Average Sales by Price Type report and the Performance Sales Summary by PT Category report should be equal to the amount of donated seats.

Why doesn't RMA match my Tessitura report?

A. Freeman — Tue, 26 Feb 2013 12:59:58 GMT

Revision 6 posted to Revenue Management Application / Pricing by A. Freeman on 2/26/2013 12:59:58 PM

General Reasons

Double check your Tessitura report parameters against your RMA report filters.
Check your RMA SQL Job Load parameters for the exclusion of certain price categories.
Is the Tessitura report in question a custom report? Depending on the details of the custom code behind the report, it may be that the report is coded to filter out items which are not being filtered in RMA.
RMA deals with inventory, and thus to it, a donated (not yet resold) seat is an available seat; it is currently empty and thus for the purposes of inventory analysis is treated as available.

Troubleshooting

In the RMA, from the Price Type Reports folder, run the Average Sales by Price Type report.
- On the filters tab, add a Season filter and select only the season in question
- On the groupings tab, set the x axis level 1 grouping to Production Season
- Set the x axis level 2 grouping to Unique Performance
- Set the y axis level 1 grouping to Price Type Category
- Save and View the report
- With the report open, then from the View menu select Source Data, click the Copy to Clipboard button and paste it into Excel.
From Tessitura run the Performance Sales Summary by PT Category report for one Season – preferably a past season in which sales are not occurring so that you are not comparing a moving target.
- Set the Performance Start and End dates to include all the performances in the season
- Set Mode Summary for now
- Set Season to the Season in question
- Group By Event
- Do not set a historical date
- Set Include Resold Seats to No

From Tessitura run the Donated Seats report for the same season.
- Group by Performance

What are the technical specifications for RMA?

A. Freeman — Thu, 20 Dec 2012 14:00:20 GMT

Revision 1 posted to Revenue Management Application / Pricing by A. Freeman on 12/20/2012 2:00:20 PM

The Software and Hardware Requirements are included in the T-Stats Installation Guide in Chapter 2.1: Software and Hardware Requirements.

RMA is currently compatible with both T-Stats v2 and T-Stats v3, as well as Tessitura versions 10 and 11.

How are "on sale" dates determined in the RMA?

A. Freeman — Fri, 07 Dec 2012 15:10:55 GMT

Revision 2 posted to Revenue Management Application / Pricing by A. Freeman on 12/7/2012 3:10:55 PM

Some RMA reports look at the time between when a ticket was purchased, and when tickets went on sale. For example:

Opening and Closing Sales Curve
Sales Curve by Weeks After On-Sale

Add the @load_starting_base_price_method=1 parameter to their RMA load job
Edit the [TPI].[LocalLoadOnsaleDates] stored procedure (which includes sample code for the default method) to use whatever default start date you need.

How are "on sale" dates determined in the RMA?

A. Freeman — Fri, 07 Dec 2012 15:02:48 GMT

Revision 1 posted to Revenue Management Application / Pricing by A. Freeman on 12/7/2012 3:02:48 PM

Some RMA reports look at the time between when a ticket was purchased, and when tickets went on sale. For example:

Opening and Closing Sales Curve
Sales Curve by Weeks After On-Sale

Add the @load_starting_base_price_method=1 parameter to their RMA load job
Edit the [TPI].[LocalLoadOnsaleDates] stored procedure (which includes sample code for the default method) to use whatever default start date you need.

Why doesn't RMA match my Tessitura report?

A. Freeman — Wed, 05 Dec 2012 20:11:19 GMT

Revision 5 posted to Revenue Management Application / Pricing by A. Freeman on 12/5/2012 8:11:19 PM

General Reasons

Double check your Tessitura report parameters against your RMA report filters.
Check your RMA SQL Job Load parameters for the exclusion of certain price categories.
Is the Tessitura report in question a custom report? Depending on the details of the custom code behind the report, it may be that the report is coded to filter out items which are not being filtered in RMA.
RMA deals with inventory, and thus to it, a donated (not yet resold) seat is an available seat; it is currently empty and thus for the purposes of inventory analysis is treated as available.

Troubleshooting

In the RMA, from the Price Type Reports folder, run the Average Sales by Price Type report.
- On the filters tab, add a Season filter and select only the season in question
- On the groupings tab, set the x axis level 1 grouping to Production Season
- Set the x axis level 2 grouping to Unique Performance
- Set the y axis level 1 grouping to Price Type Category
- Save and View the report
- With the report open, then from the View menu select Source Data, click the Copy to Clipboard button and paste it into Excel.
From Tessitura run the Performance Sales Summary by PT Category report for one Season – preferably a past season in which sales are not occurring so that you are not comparing a moving target.
- Set the Performance Start and End dates to include all the performances in the season
- Set Mode Summary for now
- Set Season to the Season in question
- Group By Event
- Do not set a historical date
- Set Include Resold Seats to No

From Tessitura run the Donated Seats report for the same season.
- Group by Performance

Why doesn't RMA match my Tessitura report?

A. Freeman — Wed, 05 Dec 2012 20:10:45 GMT

Revision 4 posted to Revenue Management Application / Pricing by A. Freeman on 12/5/2012 8:10:45 PM

General Reasons

Double check your Tessitura report parameters against your RMA report filters.
Check your RMA SQL Job Load parameters for the exclusion of certain price categories.
Is the Tessitura report in question a custom report? Depending on the details of the custom code behind the report, it may be that the report is coded to filter out items which are not being filtered in RMA.
RMA deals with inventory, and thus to it, a donated (not yet resold) seat is an available seat; it is currently empty and thus for the purposes of inventory analysis is treated as available.

Troubleshooting

In the RMA, from the Price Type Reports folder, run the Average Sales by Price Type report.
- On the filters tab, add a Season filter and select only the season in question
- On the groupings tab, set the x axis level 1 grouping to Production Season
- Set the x axis level 2 grouping to Unique Performance
- Set the y axis level 1 grouping to Price Type Category
- Save and View the report
- With the report open, then from the View menu select Source Data, click the Copy to Clipboard button and paste it into Excel.
From Tessitura run the Performance Sales Summary by PT Category report for one Season – preferably a past season in which sales are not occurring so that you are not comparing a moving target.
- Set the Performance Start and End dates to include all the performances in the season
- Set Mode Summary for now
- Set Season to the Season in question
- Group By Event
- Do not set a historical date
- Set Include Resold Seats to No
From Tessitura run the Donated Seats report for the same season.
- Group by Performance

Why doesn't RMA match my Tessitura report?

A. Freeman — Wed, 05 Dec 2012 20:08:17 GMT

Revision 3 posted to Revenue Management Application / Pricing by A. Freeman on 12/5/2012 8:08:17 PM

General Reasons

Double check your Tessitura report parameters against your RMA report filters.
Check your RMA SQL Job Load parameters for the exclusion of certain price categories.
Is the Tessitura report in question a custom report? Depending on the details of the custom code behind the report, it may be that the report is coded to filter out items which are not being filtered in RMA.
RMA deals with inventory, and thus to it, a donated (not yet resold) seat is an available seat; it is currently empty and thus for the purposes of inventory analysis is treated as available.

Troubleshooting

In the RMA, from the Price Type Reports folder, run the Average Sales by Price Type report.
- - On the filters tab, add a Season filter and select only the season in question
  - On the groupings tab, set the x axis level 1 grouping to Production Season
  - Set the x axis level 2 grouping to Unique Performance
  - Set the y axis level 1 grouping to Price Type Category
  - Save and View the report
  - With the report open, then from the View menu select Source Data, click the Copy to Clipboard button and paste it into Excel.
From Tessitura run the Performance Sales Summary by PT Category report for one Season – preferably a past season in which sales are not occurring so that you are not comparing a moving target.
- - Set the Performance Start and End dates to include all the performances in the season
  - Set Mode Summary for now
  - Set Season to the Season in question
  - Group By Event
  - Do not set a historical date
  - Set Include Resold Seats to No
From Tessitura run the Donated Seats report for the same season.
- - Group by Performance

Why doesn't RMA match my Tessitura report?

A. Freeman — Wed, 05 Dec 2012 20:07:26 GMT

Revision 2 posted to Revenue Management Application / Pricing by A. Freeman on 12/5/2012 8:07:26 PM

General Reasons

Double check your Tessitura report parameters against your RMA report filters.
Check your RMA SQL Job Load parameters for the exclusion of certain price categories.
Is the Tessitura report in question a custom report? Depending on the details of the custom code behind the report, it may be that the report is coded to filter out items which are not being filtered in RMA.
RMA deals with inventory, and thus to it, a donated (not yet resold) seat is an available seat; it is currently empty and thus for the purposes of inventory analysis is treated as available.

Troubleshooting

In the RMA, from the Price Type Reports folder, run the Average Sales by Price Type report.
- On the filters tab, add a Season filter and select only the season in question
- On the groupings tab, set the x axis level 1 grouping to Production Season
- Set the x axis level 2 grouping to Unique Performance
- Set the y axis level 1 grouping to Price Type Category
- Save and View the report
- With the report open, then from the View menu select Source Data, click the Copy to Clipboard button and paste it into Excel.
From Tessitura run the Performance Sales Summary by PT Category report for one Season – preferably a past season in which sales are not occurring so that you are not comparing a moving target.
- Set the Performance Start and End dates to include all the performances in the season
- Set Mode Summary for now
- Set Season to the Season in question
- Group By Event
- Do not set a historical date
- Set Include Resold Seats to No
From Tessitura run the Donated Seats report for the same season.
- Group by Performance

Why doesn't RMA match my Tessitura report?

A. Freeman — Wed, 05 Dec 2012 20:07:08 GMT

Revision 1 posted to Revenue Management Application / Pricing by A. Freeman on 12/5/2012 8:07:08 PM

General Reasons

Double check your Tessitura report parameters against your RMA report filters.
Check your RMA SQL Job Load parameters for the exclusion of certain price categories.
Is the Tessitura report in question a custom report? Depending on the details of the custom code behind the report, it may be that the report is coded to filter out items which are not being filtered in RMA.
RMA deals with inventory, and thus to it, a donated (not yet resold) seat is an available seat; it is currently empty and thus for the purposes of inventory analysis is treated as available.

Troubleshooting

In the RMA, from the Price Type Reports folder, run the Average Sales by Price Type report.
- On the filters tab, add a Season filter and select only the season in question
- On the groupings tab, set the x axis level 1 grouping to Production Season
- Set the x axis level 2 grouping to Unique Performance
- Set the y axis level 1 grouping to Price Type Category
- Save and View the report
- With the report open, then from the View menu select Source Data, click the Copy to Clipboard button and paste it into Excel.
From Tessitura run the Performance Sales Summary by PT Category report for one Season – preferably a past season in which sales are not occurring so that you are not comparing a moving target.
- Set the Performance Start and End dates to include all the performances in the season
- Set Mode Summary for now
- Set Season to the Season in question
- Group By Event
- Do not set a historical date
- Set Include Resold Seats to No
From Tessitura run the Donated Seats report for the same season.
- Group by Performance

How does the RMA report pricing changes on rezoned seats?

A. Freeman — Fri, 30 Nov 2012 18:36:57 GMT

Revision 4 posted to Revenue Management Application / Pricing by A. Freeman on 11/30/2012 6:36:57 PM

The seat will be reported as having the starting and current base price of the zone into which it’s been moved. If the seat is sold or reserved, the zone reflected is that of the sublineitem. If the seat is neither sold nor reserved, the zone reflected is from the zmap. There may be a temporary discrepancy if rezoning is done in Facility Manager for an entire zone map between the time the change is made and the next time the facility synchronization scripts process.

More technically:

When rezoning a single performance via Season Maintenance:
- The zone_no on tx_perf_seat is changed immediately if the seat has not been sold.
- If it is sold or reserved, zone_no doesn’t change.
- Running the facility sync doesn’t have an impact.

When rezoning an entire zone map via Facility Manager:
- The zone_no on tx_perf_seat does not change immediately.
- When you run the facility sync, the zone_no in tx_perf_seat is changed for both sold/reserved and unsold seats.
- The zone on sold/reserved sublineitems does not change.

If tracking these pricing changes is vital, consider creating enough zones that the seats won’t need to change zones in order to be assigned the appropriate price increase when the time comes. This is sometimes referred to as "micro-zoning".

How does the RMA report pricing changes on rezoned seats?

A. Freeman — Fri, 30 Nov 2012 11:48:57 GMT

Revision 3 posted to Revenue Management Application / Pricing by A. Freeman on 11/30/2012 11:48:57 AM

More technically:

When rezoning a single performance via Season Maintenance:
- The zone_no on tx_perf_seat is changed immediately if the seat has not been sold.
- If it is sold or reserved, zone_no doesn’t change.
- Running the facility sync doesn’t have an impact.

When rezoning an entire zone map via Facility Manager:
- The zone_no on tx_perf_seat does not change immediately.
- When you run the facility sync, the zone_no in tx_perf_seat is changed for both sold/reserved and unsold seats.
- The zone on sold/reserved sublineitems does not change.