Presentation is loading. Please wait.

Presentation is loading. Please wait.

Contract management v26Q3. Training overview » Create contract in WHATS’On » Linear agreements » Contract and explicit runs » Donating and sellling runs.

Similar presentations

Presentation on theme: "Contract management v26Q3. Training overview » Create contract in WHATS’On » Linear agreements » Contract and explicit runs » Donating and sellling runs."— Presentation transcript:

1 Contract management v26Q3

2 Training overview » Create contract in WHATS’On » Linear agreements » Contract and explicit runs » Donating and sellling runs » On demand agreements » Contract and agreement prototypes » Cost descriptions » Cost models » Currency » Amortizations » Payments and invoices » Commitments » Contract statusses » Availability of contracts » Restricting access to contracts » Notebook layout configuration

3 Frame contract Contract Product in contract Agreements Linear right Linear window Subcontract Linear On-demand Streaming Additional

4 Product in contract Subcontract Contract Linear right Linear window

5 Create contract in WHATS'On

6 Fill out the mandatory fields » Enter obligatory fields in contract workspace

7 Add product(s) Or Or via Drag and drop

8 Create agreement(s)

9 Add stock shot(s) » Stock shot = piece of production material (sky line, rising sun,…) » Linked to a contract as stock shot agreement

10 Stock shot agreement

11 Linear agreement

12 Fill linear right(s) & window(s)

13 Linear rights = which run types is this product allowed to broadcast and how many » A linear agreement can contain 1 or more linear rights

14 Linear rights » Per linear right the following information is available:  Run type: Run, snap or cumulative run  Number of runs/snaps/cumulative runs  Number of snaps per run  Linear window to be announced  Allow time shift for a free broadcast within this time shift  Allow free HD run on an HD channel  Snap info

15 Linear rights » Snap info  On same channel or not  Repetition rule: do weekends count  Must end in snap period or not  Snap period in calendar or broadcast days

16 Linear windows = on which channel, day, hour range, … can this run type be broadcast » A linear right contains 1 or more linear windows

17 Linear windows » Per linear window following information is available:  On which channel(s)  On what date range(s)  After what start time and before which end time  Are there blackout dates  For which platforms, definition, regions, product versions  On which weekdays  Maximum number of runs for this window  Exclusive or not

18 Entering dates » When start and end date are fixed: » When start and end date are relative:

19 Global date » Can be used to calculate relative dates

20 Restrictions per run number » F.e. The 1st run can only be broadcast between 18:00-21:00 on channel

21 Episodes tab page » Not all episodes part of the same contract?  uncheck the ones you don’t want in the ‘Episode selection list’

22 Contract runs » Details per contract run » For series, each episode has the defined number of contract runs » If needed, runs can be taken out of storage (manually in the right click menu, or automatically by setting in the site preferences – contracts tab)

23 Explicit runs » Run info per episode

24 Explicit runs for single program » Overview of explicit run information

25 General tab page of explicit runs » Per linear agreement, it is possible to predict  which run will be planned  in what period  on which channel  expected ratings

26 Planning tab page of explicit runs Compare ratings information Actual Planning

27 Donating/selling runs » On linear / Explicit runs tab » Linear / Explicit runs menu  Donate or sell linear explicit runs

28 Donating/selling runs – Resale tab

29 On demand agreement

30 On demand agreement tab page

31 On demand rights Enter rights per channel group/ region/ platform /…

32 On demand rigths » Maximum no. of overlapping episodes  For series: number of episodes that can be available on the same calendar day » Earliest allowed start and end date  Used when on demand rights are linked to the linear rights (e.g. 0 to 30 days after each transmission) -> prevents scheduling past actual end date. » To be announced  Considered as a partly valid contract

33 Contract and agreement prototypes

34 Contract and agreement prototype navigator

35 » Contract prototypes » Linear agreement prototype » On demande agreement prototypes » Streaming agreement prototypes » Additional agreement prototypes

36 Contract and agreement prototype navigator » Prototype groups  Agreement prototype groups  Contract and agreement prototype groups

37 Costs

38 Costs tab » Enter a new cost description

39 Costs tab » Enter a new cost description » Choose:  Owner = agreement or the contract  Cost model (in the cost model configuration window an administrator can limit the available cost models per cost owner)

40 Cost description – cost models » Flat fee cost  Intended for programs or for a series in total regardless of the number of episodes

41 Cost description – cost models » Cost per unit  Intended for series  Cost of each episode of that series  Total cost = Amount multiplied with expected number of episodes

42 Cost description – cost models » Barter cost  Program will be paid by means of commercial time  Manual or calculated cost  For calculation Distributor commercial time Total commercial time Commercial time cost per minute

43 Cost description – cost models » Cost per minute  Intended for stock shots  Price defined per minute Enter number of on screen seconds & minimum number of seconds. Enter cost per second or per minute Seconds multiplied by cost per second

44 Cost description – cost models » On demand revenue share  For on demand agreements  Percentage carried by TV station  Information only – no calculation

45 Cost description – cost models » Subscription cost  Based on subscriber volumes Number of subscribers entered in the subscriber volume navigator (contract administration)  Per subscription service (indicate on service for which agreements it counts)

46 Cost description – cost models » Subscription cost setting  Subscriber volume calculation type Measured subscribers Equivalent subscribers Greater of  Point of measurement: how calculation need to be done

47 Cost description – cost models » Subscription cost setting  Guaranteed minimum number of subscribers  Guaranteed minimum fee

48 Cost description – cost models » Subscription cost settings  Can also be created on contract and sub contract level, and copied from there on the cost description

49 Cost description – cost models » Subscription costs  Cost is calculated (subscriber volume * cost per subscriber)  Cost channel  Estimated cost: only when ‘estimated’ subscriber volumes are available

50 Cost description – cost models » Subscription cost – settlements  Calculation of the subscription cost  Usually at the start of the month  Results in a settlement record = saved calculation with status calculated  As long as status stays that way -> overwritten when new calculation is done.  Change status to ‘Cancelled’ or ‘Paid’ -> will never be overwritten.

51 Currency

52 » One local currency, others are foreign currencies » Exchange rate measured against local currency » Currencies are determined by administrator in ‘Currency editor’

53 Currency editor » Contract administration – currency configuration

54 Currency editor » Right click on value and choose “Modify exchange rate” » Right click and “Propagate to cost descriptions”  Based on what is set on site prefs – contract tab Always (never used) As long as agreement is not signed As long as linear window has not started

55 Currency – exchange rate on cost description » Unless it’s the default currency, you can adapt the exchange rate manually  An icon will indicate that this has been done

56 Cost description - Amortizations -

57 Define amortizations » Amortization = the deduction of capital expenses over a specific period of time. » Date-based amortizations:  independent from the planning  spread over a certain period » Run-based amortizations  A run is broadcast → A value is depreciated » Record of type “Remaining amortization value” keeps status “predicted” until user decides otherwise

58 Amortization types

59 Amortizations: Run based value » Run based » Decide amount of runs to be amortized » Give value per run

60 Amortizations: Run based percentage » Run based » Choose amortization rule (list to choose from is defined by administrator)

61 Amortizations: Straight line » Date based » Decide period » Weekly, monthly or quaterly amortizations

62 Amortizations: Declining balance » Date based » Decide period and declination percentage » Weekly, monthly or quaterly amortizations

63 Amortizations: Greater of » Mix of date and run based » Greater of both values is used

64 Amortizations: First run of first episode » Full cost amortized when first episode is planned for it’s first run

65 Amortizations tab page

66 Amortization lookup tables » To automatically enter amortization rules when entering amortization » Attributes:  Product contract category (entered on product – contract tab)  Number of runs » Result:  Amortization rule

67 Amortization lookup tables » Order of the rules is important!

68 Amortization lookup rules » In the site preferences it is indicated which lookup table needs to be used

69 Amortization lookup table » When you define a new amortization and you choose the amortization type “Run based percentage” + the rules apply  Amortization rule is automatically filled in

70 Change costs and redistribute over amortizations » Possibility to change the cost of a contract » Adapt value of amortization records by redistributing  Over predicted amortizations  Over all amortizations

71 Change costs and redistribute over amortizations

72 Generate waste » You are not going to broadcast a certain right » A certain right is not worth as much anymore » …  You can generate waste for this = decrease of value / accelerated amortization » Select cost description – right click – Generate waste

73 Generate waste

74 Payments and invoices

75 Payments » Payments can be added on  Product in contract level  On general contract level (mostly used)  From scratch via the Payment browser » Name of payment  Creditor, date of payment, amount and status

76 Payments – Product in contract level » Create a new payment from scratch OR » Create a payment based on a payment prototype

77 Payment prototypes

78 Payments – contract level » All costs in the contract are added up per creditor » Payments are for the whole contract

79 Payments – payment navigator » Open the payment navigator from payments in a contract » Launcher – Contracts – Payment browser

80 Payments – Payment navigator » Payment browser  Search for existing payments  Create new payment

81 Payments – Payment navigator » Create new payment  Search for a cost description to which you wish to link your payment (This is the same as linking payments on product in contract level)

82 Payments – Payment navigator

83 Payments – split payment » One payment split in two » General info is duplicated

84 Invoices » New invoices can be created » and payments can be added to invoices  In the contract, on contract level  In the invoice navigator

85 Invoices » Contract  Link existing invoice to the contract  Or create a new invoice

86 Invoices » Invoice navigator  Invoice can contain payments from more than one contract  Add payments

87 Invoices » Invoice navigator  Status can be set to “paid”  All payments will also be set to “paid”  New payments can no longer be linked to the invoice

88 Payment statistics » Based on payment statistics prototype (contract administration)

89 Payment statistics » Calculation from payment navigator for selection

90 Payment statistics » Search for calculated statistics

91 Commitments

92 = commitments are made before a contract is signed. This is an estimation of the final contract.

93 Contract statusses

94 Contract status All agreements receive the status of their contract, but this can be changed To change the status:

95 Contract status - configuration » Contract type configuration (under contract administration)  Contract phase limits statuses and actions that are available to the user  One status per phase can be set as default

96 Contract status - configuration » “Is in stock”: contract is taken into account when calculating stock » “Contract requires amendment”: when this is set to yes, the contract receiving this status will become read only  Only users with correct permissions (Contract Amendment Management – Editor) will still be able to amend the contract

97 Availability of contracts

98 » When a contract is still in negotiation, it may not be desirable that all users can already consult the contract. Therefore, contracts and their agreements can be made unavailable » Newly created contract is always “available” » Can be changed  Using toggle  Using contract phase with status unavailable Availablity

99 Availability » Icon for unavailable contract: » To have acces  “access to unavailable contracts” – “browser” access rigths  If user does not have this permission he will never find the contract. » Product can be made unavailable as well (WHATS’On asks when making contract unavailable)

100 Restricting access to contracts

101 » Next to having available or unavailable contracts, you might not want users responsible for certain channels to have access to contracts for other channels. » Permission navigator – user account – contract channels tab page

102 Restricting access to contracts - Linear agreements -

103 Restricting access to contracts - On demand agreements » Same configuration for on demand agreements

104 Notebook layout configuration

105 » Administrator can  limit the amount of tab pages on the contract navigator  Configure how the navigator tree and the editor is displayed

106 Thank you!

Download ppt "Contract management v26Q3. Training overview » Create contract in WHATS’On » Linear agreements » Contract and explicit runs » Donating and sellling runs."

Similar presentations

Ads by Google