Motorola 2011 Annual Report Download - page 55

Download and view the complete annual report

Please find page 55 of the 2011 Motorola annual report below. You can navigate through the pages in the report by either clicking on the pages listed below, or by using the keyword search tool below to find specific information within the annual report.

Page out of 131

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131

49
or term licenses is recognized ratably over the period that the licensee uses the license. Revenue from software
maintenance, technical support and unspecified upgrades is recognized over the period that these services are
delivered.
Multiple-Element Arrangements—Arrangements with customers may include multiple deliverables, including
any combination of product, services and software. These multiple element arrangements could also include an
element accounted for as a long-term contract coupled with other product, services and software. For multiple-
element arrangements that include product containing software essential to the equipment’s functionality,
undelivered software elements that relate to the product’s essential software, and undelivered non-software services,
deliverables are separated into more than one unit of accounting when (i) the delivered element(s) have value to the
customer on a stand-alone basis, and (ii) delivery of the undelivered element(s) is probable and substantially in the
control of the Company. In these arrangements, we allocate revenue to all deliverables based on their relative selling
prices. We use a hierarchy to determine the selling price to be used for allocating revenue to deliverables: (i) vendor-
specific objective evidence of fair value (“VSOE”), (ii) third-party evidence of selling price (“TPE”), and (iii) best
estimate of selling price (“ESP”).
VSOE—In many instances, products are sold separately in stand-alone arrangements as customers may
support the products themselves or purchase support on a time and materials basis. Additionally, advanced
services such as general consulting, network management or advisory projects are often sold in stand-alone
engagements. Technical support services are also often sold separately through renewals of annual contracts.
We determine VSOE based on our normal pricing and discounting practices for the specific product or
service when sold separately. In determining VSOE, we require that a substantial majority of the selling
prices for a product or service fall within a reasonably narrow pricing range, generally evidenced by the
pricing rates of approximately 80% of such historical stand-alone transactions falling within plus or minus
15% of the median rate. In addition, we consider the geographies in which the products or services are sold,
major product and service groups, customer classification, and other environmental or marketing variables in
determining VSOE.
TPE—VSOE exists only when we sell the deliverable separately. When VSOE does not exist, we attempt to
determine TPE based on competitor prices for similar deliverables when sold separately. Generally, our
go-to-market strategy for many of our products differs from that of our peers and our offerings contain a
significant level of customization and differentiation such that the comparable pricing of products with
similar functionality sold by other companies cannot be obtained. Furthermore, we are unable to reliably
determine what similar competitor products’ selling prices are on a stand-alone basis. Therefore, we are
typically not able to determine TPE.
ESP—The objective of ESP is to determine the price at which we would transact a sale if the product or
service were sold on a stand-alone basis. When both VSOE and TPE do not exist, we determine ESP by first
collecting all reasonably available data points including sales, cost and margin analysis of the product, and
other inputs based on our normal pricing practices. Second, we make any reasonably required adjustments to
the data based on market and Company-specific factors. Third, we stratify the data points, when
appropriate, based on customer, magnitude of the transaction and sales volume.
Once elements of an arrangement are separated into more than one unit of accounting, revenue is recognized
for each separate unit of accounting based on the nature of the revenue as described above.
Our arrangements with multiple deliverables may also contain a stand-alone software deliverable that is subject
to the existing software revenue recognition guidance. The revenue for these multiple-element arrangements is
allocated to the software deliverable and the non-software deliverable(s) based on the relative selling prices of all of
the deliverables in the arrangement using the hierarchy in the revenue accounting guidance. In circumstances where
we cannot determine VSOE or TPE of the selling price for all of the deliverables in the arrangement, including the
software deliverable, ESP is used for the purpose of allocating the arrangement consideration.
We account for multiple element arrangements that consist entirely of software or software-related products,
including the sale of software upgrades or software support agreements to previously sold software, in accordance
with software accounting guidance. For such arrangements, revenue is allocated to the deliverables based on the
relative fair value of each element, and fair value is determined by VSOE. Where VSOE does not exist for the
undelivered software element, revenue is deferred until either the undelivered element is delivered or VSOE is
established, whichever occurs first. When VSOE of a delivered element has not been established, but VSOE exists