2.2.0.25falsefalse0201 - Disclosure - The Company and its Significant Accounting Policiestruefalsefalse1falsefalseUSDfalsefalse8/1/2010 - 1/31/2011 USD ($) USD ($) / shares $Aug-01-2010_Jan-31-2011http://www.sec.gov/CIK0001173752duration2010-08-01T00:00:002011-01-31T00:00:00USDStandardhttp://www.xbrl.org/2003/iso4217USDiso42170SharesStandardhttp://www.xbrl.org/2003/instancesharesxbrli0USDEPSDividehttp://www.xbrl.org/2003/iso4217USDiso4217http://www.xbrl.org/2003/instancesharesxbrli0USDUSD$2true0us-gaap_GeneralPoliciesAbstractus-gaaptruenadurationNo definition available.falsefalsefalsefalsefalsefalsefalsefalsefalsefalse1falsefalsefalse00falsefalsefalsefalsefalseOtherxbrli:stringItemTypestringNo definition available.falsefalseThe Company and its Significant Accounting Policies [Abstract]3false0us-gaap_OrganizationConsolidationAndPresentationOfFinancialStatementsDisclosureTextBlockus-gaaptruenadurationNo definition available.falsefalsefalsefalsefalsefalsefalsefalsefalsefalseverboselabel1falsefalsefalse00    <div style="font-family: 'Times New Roman',Times,serif; margin-left: 0in; "> <div align="center" style="font-size: 10pt; margin-top: 0pt"><b></b> </div> <div align="left"> </div> <div align="center" style="font-size: 10pt; margin-top: 0pt"><b></b> </div> <div align="center" style="font-size: 10pt"><b></b></div> <div align="left" style="font-size: 10pt; margin-top: 10pt"><b>1. The Company and its Significant Accounting Policies</b> </div> <div align="left" style="font-size: 10pt; margin-top: 10pt"><b>The Company</b> </div> <div align="left" style="font-size: 10pt; margin-top: 10pt; text-indent: 8%">Aruba Networks, Inc. (the “Company”) was incorporated in the state of Delaware on February 11, 2002. The Company securely connects local and remote users to corporate IT resources via distributed enterprise networks. The Company’s portfolio of campus, branch office, teleworker, and mobile solutions simplifies operations and provides secure access to all corporate applications and services — regardless of a user’s device, location, or network. The products the Company licenses and sells include high-speed 802.11n wireless local area networks, Virtual Branching Networking solutions for branch offices and teleworkers, and network operations tools, including spectrum analyzers, wireless intrusion prevention systems, and the AirWave Wireless Management Suite for managing wired, wireless, and mobile device networks. The Company has offices in North America, Europe, the Middle East and the Asia Pacific region and employs staff around the world. </div> <div align="left" style="font-size: 10pt; margin-top: 10pt"><b>Basis of Presentation</b> </div> <div align="left" style="font-size: 10pt; margin-top: 10pt; text-indent: 8%">The accompanying consolidated financial statements include the accounts of the Company and its wholly-owned subsidiaries. All intercompany accounts and transactions have been eliminated. The accompanying statements are unaudited and should be read in conjunction with the audited consolidated financial statements and related notes contained in the Company’s Annual Report on Form 10-K filed on September 24, 2010. The July 31, 2010 consolidated balance sheet data were derived from audited financial statements, but do not include all disclosures required by accounting principles generally accepted in the United States (“U.S.”) of America. </div> <div align="left" style="font-size: 10pt; margin-top: 10pt; text-indent: 8%">The accompanying unaudited consolidated financial statements have been prepared in accordance with U.S. generally accepted accounting principles (“GAAP”), pursuant to the rules and regulations of the Securities and Exchange Commission (“SEC”). They do not include all of the financial information and footnotes required by GAAP for complete financial statements. The Company believes the unaudited consolidated financial statements have been prepared on the same basis as its audited financial statements as of and for the year ended July 31, 2010 and include all adjustments necessary for the fair statement of the Company’s financial position as of January 31, 2011, its results of operations for the three and six months ended January 31, 2011 and 2010, and its cash flows for the six months ended January 31, 2011 and 2010. The results for the three and six months ended January 31, 2011 are not necessarily indicative of the results to be expected for any subsequent quarter or for the fiscal year ending July 31, 2011. </div> <div align="left" style="font-size: 10pt; margin-top: 10pt; text-indent: 8%">Other than the adoption of the provisions of Financial Accounting Standards Board (“FASB”) Accounting Standards Codification (“ASC”) Accounting Standards Update (“ASU”) 2009-14, <i>Software (Topic 985): Certain Revenue Arrangements That Include Software Elements</i>, and ASU 2009-13, <i>Revenue Recognition (Topic 605): Multiple-Deliverable Revenue Arrangements</i>, there have been no significant changes in the Company’s accounting policies during the three and six months ended January 31, 2011, as compared to the significant accounting policies described in the Company’s Annual Report on Form 10-K for the year ended July 31, 2010. </div> <div align="left" style="font-size: 10pt; margin-top: 10pt"><b>Revenue Recognition</b> </div> <div align="left" style="font-size: 10pt; margin-top: 10pt; text-indent: 8%">In October 2009, the FASB amended the accounting standards for revenue recognition to remove tangible products containing software components and non-software components that function together to deliver the product’s essential functionality from the scope of industry-specific software revenue recognition guidance. In October 2009, the FASB also amended the accounting standards for multiple-element revenue arrangements to: </div> <div style="margin-top: 10pt"> <table width="100%" border="0" cellpadding="0" cellspacing="0" style="font-size: 10pt; text-align: left"> <tr valign="top" style="font-size: 10pt; color: #000000; background: transparent"> <td width="4%" style="background: transparent"> </td> <td width="3%" nowrap="nowrap" align="left">(i)</td> <td width="1%"> </td> <td>provide updated guidance on how the elements in a multiple-element arrangement should be separated, and how the consideration should be allocated;</td> </tr> <tr> <td style="font-size: 8pt"> </td> </tr> <tr valign="top" style="font-size: 10pt; color: #000000; background: transparent"> <td width="4%" style="background: transparent"> </td> <td width="3%" nowrap="nowrap" align="left">(ii)</td> <td width="1%"> </td> <td>require an entity to allocate revenue amongst the elements in an arrangement using estimated selling prices (“ESP”) if a vendor does not have vendor-specific objective evidence (“VSOE”) of the selling price or third-party evidence (“TPE”) of the selling price; and</td> </tr> <tr> <td style="font-size: 8pt"> </td> </tr> <tr valign="top" style="font-size: 10pt; color: #000000; background: transparent"> <td width="4%" style="background: transparent"> </td> <td width="3%" nowrap="nowrap" align="left">(iii)</td> <td width="1%"> </td> <td>eliminate the use of the residual method and require an entity to allocate revenue using the relative selling price method.</td> </tr> </table> </div> <div align="left" style="font-size: 10pt; margin-top: 10pt; text-indent: 8%">The Company adopted this accounting guidance at the beginning of its first quarter of fiscal 2011 on a prospective basis for applicable arrangements originating or materially modified after July 31, 2010. The impact of this adoption was not material to the Company’s financial position and results of operations in the three and six months ended January 31, 2011. </div>   </div>  <div style="font-family: 'Times New Roman',Times,serif; margin-left: 0in; "> <div align="left" style="font-size: 10pt; margin-top: 10pt; text-indent: 8%">This guidance does not generally change the units of accounting for the Company’s revenue transactions. Most non-software products and services qualify as separate units of accounting because they have value to the customer on a stand-alone basis and the Company’s revenue arrangements generally do not include a right of return relative to delivered products. </div> <div align="left" style="font-size: 10pt; margin-top: 10pt; text-indent: 8%">The majority of the Company’s products are hardware appliances containing software components that function together to provide the essential functionality of the product. Therefore, the Company’s hardware appliances are considered non-software elements and are not subject to the industry-specific software revenue recognition guidance. </div> <div align="left" style="font-size: 10pt; margin-top: 10pt; text-indent: 8%">The Company’s product revenue also includes revenue from the sale of stand-alone software products. Stand-alone software products may operate on the Company’s hardware appliance, but are not considered essential to the functionality of the hardware. Sales of stand-alone software generally include a perpetual license to the Company’s software. Sales of stand-alone software continue to be subject to the industry-specific software revenue recognition guidance. </div> <div align="left" style="font-size: 10pt; margin-top: 10pt; text-indent: 8%">For all arrangements originating or materially modified after July 31, 2010, the Company recognizes revenue in accordance with the amended accounting guidance. Certain arrangements with multiple-elements may continue to have stand-alone software elements that are subject to the existing software revenue recognition guidance along with non-software elements that are subject to the amended revenue accounting guidance. The revenue for these multiple element arrangements is allocated to the stand-alone software elements as a group and the non-software elements based on the relative selling prices of all of the elements in the arrangement using the fair value hierarchy in the amended revenue accounting guidance. </div> <div align="left" style="font-size: 10pt; margin-top: 10pt; text-indent: 8%">For sales of stand-alone software after July 31, 2010 and for all transactions entered into prior to the first quarter of 2011, the Company recognizes revenue based on software revenue recognition guidance. Under the software revenue recognition guidance, the Company uses the residual method to recognize revenue when a product agreement includes one or more elements to be delivered at a future date and VSOE of the fair value of all undelivered elements exists. In the majority of the Company’s contracts, the only element that remains undelivered at the time of delivery of the product is support services. Under the residual method, the fair value of the undelivered elements is deferred and the remaining portion of the contract fee is recognized as product revenue. If evidence of the fair value of one or more undelivered elements does not exist, all revenue is generally deferred and recognized when delivery of those elements occurs or when fair value can be established. When the undelivered element for which the Company does not have VSOE of fair value is support, revenue for the entire arrangement is bundled and recognized ratably over the support period. </div> <div align="left" style="font-size: 10pt; margin-top: 10pt; text-indent: 8%">VSOE for elements of an arrangement is based upon the normal pricing and discounting practices for those services when sold separately, and VSOE for support services is measured by the stand-alone renewal rate offered to the customer. In determining VSOE, the Company requires that a substantial majority of the selling prices for an element falls within a reasonably narrow pricing range, generally evidenced by a substantial majority of such historical stand-alone transactions falling within a reasonably narrow range of the median rates. In addition, the Company considers major service groups, geographies, customer classifications, and other variables in determining VSOE. </div> <div align="left" style="font-size: 10pt; margin-top: 10pt; text-indent: 8%">The Company is typically not able to determine TPE for the Company’s products or services. TPE is determined based on competitor prices for similar elements when sold separately. Generally, the Company’s go-to-market strategy differs from that of the Company’s peers and the Company’s offerings contain a significant level of differentiation such that the comparable pricing of products with similar functionality cannot be obtained. Furthermore, the Company is unable to reliably determine what similar competitor products’ selling prices are on a stand-alone basis. </div> <div align="left" style="font-size: 10pt; margin-top: 10pt; text-indent: 8%">When the Company is unable to establish selling price of its non-software elements using VSOE or TPE, the Company uses ESP in its allocation of arrangement consideration. The objective of ESP is to determine the price at which the Company would transact a sale if the product or service were sold on a stand-alone basis. The Company determines ESP for a product or service by considering multiple factors including, but not limited to, cost of products, gross margin objectives, pricing practices, geographies, customer classes and distribution channels. </div> <div align="left" style="font-size: 10pt; margin-top: 10pt; text-indent: 8%">The Company regularly reviews VSOE and ESP and maintains internal controls over the establishment and updates of these estimates. There was not a material impact during the second quarter or first six months of fiscal 2011, nor does the Company currently expect a material impact in the near term from changes in VSOE or ESP. </div> <div align="left" style="font-size: 10pt; margin-top: 10pt; text-indent: 8%">Product revenue consists of revenue from sales of the Company’s hardware appliances and perpetual software licenses. The Company recognizes product revenue when all of the following have occurred: (1) the Company has entered into a legally binding arrangement with a customer; (2) delivery has occurred; (3) customer payment is deemed fixed or determinable and free of contingencies and significant uncertainties; and (4) collection is reasonably assured. </div> <div align="left" style="font-size: 10pt; margin-top: 10pt; text-indent: 8%">For sales to direct end-users and channel partners, including value-added resellers, value-added distributors, and OEMs, the Company recognizes product revenue upon delivery, assuming all other revenue recognition criteria are met. For the Company’s hardware appliances, delivery occurs upon transfer of title and risk of loss, which is generally upon shipment. It is the Company’s practice to identify an end-user prior to shipment to a channel partner. For end-users and channel partners, the Company generally has no significant obligations for future performance such as rights of return or pricing credits. A portion of the Company’s sales are made through distributors under agreements allowing for stocking of the Company’s products in their inventory, pricing credits and limited rights of return for stock rotation. Product revenue on sales made through these distributors is initially deferred and revenue is recognized upon sell-through as reported by the distributors to the Company. Shipping charges billed to customers are included in product revenue and the related shipping costs are included in cost of product revenue. </div>   </div>  <div style="font-family: 'Times New Roman',Times,serif; margin-left: 0in; "> <div align="left" style="font-size: 10pt; margin-top: 10pt; text-indent: 8%">Support and services offerings consist of support agreements, professional services, and training. Support services include repair and replacement of defective hardware appliances, software updates and access to technical support personnel. Software updates provide customers with rights to unspecified software product upgrades and to maintenance releases and patches released during the term of the support period. Revenue for support services is recognized on a straight-line basis over the service contract term, which is typically one to five years. Professional services are recognized upon delivery or completion of performance. Professional service arrangements are typically short-term in nature and are largely completed within 90 days from the start of service. Training services are recognized upon delivery of the training. </div> <div align="left" style="font-size: 10pt; margin-top: 10pt; text-indent: 8%">The Company’s fees are typically considered to be fixed or determinable at the inception of an arrangement, generally based on specific products and quantities to be delivered. Substantially all of the Company’s contracts do not include rights of return or acceptance provisions. To the extent that the Company’s agreements contain such terms, the Company recognizes revenue once the customer has accepted, or once the acceptance provisions or right of return lapses. Payment terms to customers generally range from net 30 to 60 days. In the event payment terms are provided that differ from the Company’s standard business practices, the fees are deemed to not be fixed or determinable and revenue is recognized when the payments become due, provided the remaining criteria for revenue recognition have been met. </div> <div align="left" style="font-size: 10pt; margin-top: 10pt; text-indent: 8%">The Company assesses the ability to collect from its customers based on a number of factors, including credit worthiness of the customer and past transaction history of the customer. If the customer is not deemed credit worthy, the Company defers revenue from the arrangement until payment is received and all other revenue recognition criteria have been met. </div> </div>  <!-- Begin Block Tagged NotefalsefalsefalsefalsefalseOtherus-types:textBlockItemTypestringDescription containing the entire organization, consolidation and basis of presentation of financial statements disclosure. May be provided in more than one note to the financial statements, as long as users are provided with an understanding of (1) the significant judgments and assumptions made by an enterprise in determining whether it must consolidate a VIE and/or disclose information about its involvement with a VIE, (2) the nature of restrictions on a consolidated VIE's assets reported by an enterprise in its statement of financial position, including the carrying amounts of such assets, (3) the nature of, and changes in, the risks associated with an enterprise's involvement with the VIE, and (4) how an enterprise's involvement with the VIE affects the enterprise's financial position, financial performance, and cash flows. Describes procedure if disclosures are provided in more than one note to the financial statements.Reference 1: http://www.xbrl.org/2003/role/presentationRef -Publisher FASB -Name FASB Staff Position (FSP) -Number FAS140-4 and FIN46(R)-8 -Paragraph 8, C1, C7 Reference 2: http://www.xbrl.org/2003/role/presentationRef -Publisher AICPA -Name Accounting Research Bulletin (ARB) -Number 51 -Paragraph 2-6 Reference 3: http://www.xbrl.org/2003/role/presentationRef -Publisher AICPA -Name Statement of Position (SOP) -Number 94-6 -Paragraph 10 Reference 4: http://www.xbrl.org/2003/role/presentationRef -Publisher FASB -Name FASB Interpretation (FIN) -Number 46R -Paragraph 4, 14, 15 falsefalseThe Company and its Significant Accounting Policies12The Company and its Significant Accounting PoliciesUnKnownUnKnownUnKnownUnKnownfalsetrue