Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. late July 00: Make a copy of the TI Service Pricing FY01 sheet (call it TI Service Pricing FY02).  FY01 prices are now set in stone (in the former); the latter is a working document for revising and adding FY02 prices. Link the new copy to the TI Service Catalog and Billing Coordination meeting calendar event.

  2. late July 00: Create a Jira Epic "Service Pricing FY02" with high-level Description phases:

    • [] plan new fees or service offerings that will require changing F&F (July-November 00)

    • [] tweak/update pricing models as desired (July-November 00)

      • November: dump OIT salary data from Cognos, fully load it with OPE/S&S, store in OIT Service Pricing > OIT Salary Dumps

        • Cognos > Run Employee and Index Information by Organization Code - H0004 with org code 610000, export as Excel, import into Google Sheets

    • [] finalize pricing model & check for increases that will impact F&F (November 00)

    • [] assemble and submit all changes to F&F (November 00)

      • [] develop detailed budget submissions for new/increased F&F fees (December 00)

    • [] make any final pricing refinements/adjustments later pricing changes that don’t require F&F changes (January-April 01)

    • [] trigger audit/reviews of special customer billing/pricing that wouldn’t be updated in any other way (February-March 01)

      • Review/update Vanport Building Technology SLA pricing for FY02

      • Review/update Housing buildings/rooms/rates (HCOM charges) Review/update and UPL rooms/rates (UPL* charges on AUX390)

    • [] announce new pricing as necessary (May 01)

    • [] activate new FY02 pricing (early July 01)

  3. As you work on specific services, create Child issues of this Epic and corresponding sub-items in the Description checklist.

  4. Fines & Fees for FY02 become active in July 01 and need to be submitted ~January 01, so get started early: price revisions or price development for new service offerings that are part of Fines & Fees should be in progress by September and complete by November.

  5. November 00: Finalize any new prices that would require Fines & Fees changes (at least "not to exceed" ceilings) with service offering managers, the TI service catalog and billing coordination committee, and finally the OIT Fiscal Officer in Fines & Fees review meetings.

  6. December 00: Develop detailed fee calculation budget for each new fee or increase, using the Fines & Fees committee’s current template, to prepare for their submission by OIT Fiscal Officer in January 01.

  7. January-April 01: Finalize all new prices, and review/update special customer billed units/rates.

  8. May 01: Announce new prices to appropriate populations, as necessary.

  9. early July 01: Activate new prices

    1. Update service catalog customer views (main & technical), TC price list, and consolidated rate sheet.

    2. Apply to PCR-360: create new Services and Charges as necessary, amend Charges as necessary

...