Summary of Significant Accounting Policies (Policies)	6 Months Ended
Jun. 30, 2015
Accounting Policies [Abstract]
Revenue Recognition	Revenue Recognition The Company derives its revenue from sales of its products, support and services. Product revenue consists of the Company’s software integrated with industry standard hardware and sold as complete turn-key integrated solutions, as stand-alone software applications or sold on a subscription or consumption basis. Depending on the nature of the arrangement revenue related to turn-key solutions and stand-alone software applications are generally recognized upon shipment and delivery of license keys. For certain arrangements revenue is recognized based on usage or ratably over the term of the arrangement. Support and services revenue consists of both maintenance revenues and professional services revenues. Revenue is recorded net of applicable sales taxes. In accordance with the authoritative guidance issued by the FASB on revenue recognition, the Company recognizes revenue when persuasive evidence of an arrangement exists, the fee is fixed or determinable, delivery has occurred, and collection of the resulting receivable is deemed probable. Products delivered to a customer on a trial basis are not recognized as revenue until the trial period has ended and acceptance has occurred by the customer. Reseller and distributor customers typically send the Company a purchase order when they have an end user identified. For bundled arrangements that include either maintenance or both maintenance and professional services, the Company uses the residual method to determine the amount of product revenue to be recognized. Under the residual method, consideration is allocated to the undelivered elements based upon vendor-specific objective evidence (“VSOE”) of the fair value of those elements, with the residual of the arrangement fee allocated to and recognized as product revenue. If VSOE does not exist for all undelivered elements of an arrangement, the Company recognizes total revenue from the arrangement ratably over the term of the maintenance agreement. The Company's long-term portion of deferred revenue consists of (i) payments received for maintenance contracts with terms in excess of one year as of the balance sheet date, and (ii) payments received for product sales bundled with multiple years of maintenance but for which VSOE did not exist for all undelivered elements of the arrangement. The Company provides an allowance for product returns as a reduction of revenue, based upon historical experience and known or expected trends. When more than one element, such as hardware, software and services are contained in a single arrangement, the Company will first allocate revenue based upon the relative selling price into two categories: (1) non-software components, such as hardware and any hardware-related items, as required system software that functions with the hardware to deliver the essential functionality of the hardware and related post-contract customer support, and software as service subscriptions and (2) software components and applications, such as post-contract customer support and other services. The Company will then allocate revenue within the non-software category to each element based upon their relative selling price using a hierarchy of VSOE, third-party evidence of selling price (“TPE”) or estimated selling prices (“ESP”), if VSOE or TPE does not exist. The Company will allocate revenue within the software category to the undelivered elements based upon their fair value using VSOE with the residual revenue allocated to the delivered elements. If the Company cannot objectively determine the VSOE of the fair value of any undelivered software element, the Company will defer revenue for all software components until all elements are delivered and services have been performed, until fair value can objectively be determined for any remaining undelivered elements, or until software maintenance is the only undelivered element which the Company has VSOE for, in which case revenue is recognized over the maintenance term for all software elements. Revenues associated with maintenance services are deferred and recognized as revenue ratably over the term of the contract. Revenues associated with software implementation and software engineering services are recognized when the services are performed. Costs of providing these services are included in cost of support and services. The Company has entered into various distribution, licensing and joint promotion agreements with OEMs, whereby the Company has provided to the OEM a non-exclusive software license to install the Company’s software on certain hardware or to resell the Company’s software in exchange for payments based on the products distributed by these OEMs. Such payments from the OEM or distributor are recognized as revenue in the period reported by the OEM. From time to time the Company will enter into funded software development arrangements. Under such arrangements, revenue recognition will not commence until final delivery and/or acceptance of the product. For arrangements where the Company has VSOE for the undelivered elements, the Company will follow the residual method and recognize product revenue upon final delivery and/or acceptance of the product. For arrangements where the Company does not have VSOE for the undelivered elements, the Company will recognize the entire arrangement fee ratably commencing at the time of final delivery and/or acceptance through the end of the service period in the arrangement. Certain arrangements, for which VSOE of fair value for the undelivered maintenance elements cannot be established, are accounted for as a single unit of account. The revenue recognized from single units of accounting are typically allocated and classified on the consolidated statements of operations as product revenue and support and services revenue. Since VSOE cannot be established, VSOE of similar maintenance offerings provides the basis for the support and services revenue classification, and the remaining residual consideration provides the basis for the product revenue classification. In 2013, the Company entered into a joint development agreement whereby final acceptance of the software delivered under the joint development agreement occurred on November 16, 2014. During 2014, the Company began to recognize the total committed fee as revenue ratably over a twenty-five and a half month period which began on November 16, 2014 which included a contractual twenty-four month maintenance period. During the first quarter of 2015, the customer elected to terminate their maintenance agreement and as such all unrecognized deferred revenue was accelerated and recognized as product revenue during the quarter. During the six months ended June 30, 2015, the Company recorded total product revenue of approximately $11.3 million related to this agreement. There was no product revenue recorded during the three months ended June 30, 2015 related to this agreement. As of June 30, 2015, there is no deferred revenue or undelivered services remaining related to this agreement.

Revenue Recognition

The Company derives its revenue from sales of its products, support and services. Product revenue consists of the Company’s software integrated with industry standard hardware and sold as complete turn-key integrated solutions, as stand-alone software applications or sold on a subscription or consumption basis. Depending on the nature of the arrangement revenue related to turn-key solutions and stand-alone software applications are generally recognized upon shipment and delivery of license keys. For certain arrangements revenue is recognized based on usage or ratably over the term of the arrangement. Support and services revenue consists of both maintenance revenues and professional services revenues. Revenue is recorded net of applicable sales taxes.

In accordance with the authoritative guidance issued by the FASB on revenue recognition, the Company recognizes revenue when persuasive evidence of an arrangement exists, the fee is fixed or determinable, delivery has occurred, and collection of the resulting receivable is deemed probable. Products delivered to a customer on a trial basis are not recognized as revenue until the trial period has ended and acceptance has occurred by the customer. Reseller and distributor customers typically send the Company a purchase order when they have an end user identified. For bundled arrangements that include either maintenance or both maintenance and professional services, the Company uses the residual method to determine the amount of product revenue to be recognized. Under the residual method, consideration is allocated to the undelivered elements based upon vendor-specific objective evidence (“VSOE”) of the fair value of those elements, with the residual of the arrangement fee allocated to and recognized as product revenue. If VSOE does not exist for all undelivered elements of an arrangement, the Company recognizes total revenue from the arrangement ratably over the term of the maintenance agreement. The Company's long-term portion of deferred revenue consists of (i) payments received for maintenance contracts with terms in excess of one year as of the balance sheet date, and (ii) payments received for product sales bundled with multiple years of maintenance but for which VSOE did not exist for all undelivered elements of the arrangement. The Company provides an allowance for product returns as a reduction of revenue, based upon historical experience and known or expected trends.

When more than one element, such as hardware, software and services are contained in a single arrangement, the Company will first allocate revenue based upon the relative selling price into two categories: (1) non-software components, such as hardware and any hardware-related items, as required system software that functions with the hardware to deliver the essential functionality of the hardware and related post-contract customer support, and software as service subscriptions and (2) software components and applications, such as post-contract customer support and other services. The Company will then allocate revenue within the non-software category to each element based upon their relative selling price using a hierarchy of VSOE, third-party evidence of selling price (“TPE”) or estimated selling prices (“ESP”), if VSOE or TPE does not exist. The Company will allocate revenue within the software category to the undelivered elements based upon their fair value using VSOE with the residual revenue allocated to the delivered elements. If the Company cannot objectively determine the VSOE of the fair value of any undelivered software element, the Company will defer revenue for all software components until all elements are delivered and services have been performed, until fair value can objectively be determined for any remaining undelivered elements, or until software maintenance is the only undelivered element which the Company has VSOE for, in which case revenue is recognized over the maintenance term for all software elements.

Revenues associated with maintenance services are deferred and recognized as revenue ratably over the term of the contract. Revenues associated with software implementation and software engineering services are recognized when the services are performed. Costs of providing these services are included in cost of support and services.

The Company has entered into various distribution, licensing and joint promotion agreements with OEMs, whereby the Company has provided to the OEM a non-exclusive software license to install the Company’s software on certain hardware or to resell the Company’s software in exchange for payments based on the products distributed by these OEMs. Such payments from the OEM or distributor are recognized as revenue in the period reported by the OEM.

From time to time the Company will enter into funded software development arrangements. Under such arrangements, revenue recognition will not commence until final delivery and/or acceptance of the product. For arrangements where the Company has VSOE for the undelivered elements, the Company will follow the residual method and recognize product revenue upon final delivery and/or acceptance of the product. For arrangements where the Company does not have VSOE for the undelivered elements, the Company will recognize the entire arrangement fee ratably commencing at the time of final delivery and/or acceptance through the end of the service period in the arrangement. Certain arrangements, for which VSOE of fair value for the undelivered maintenance elements cannot be established, are accounted for as a single unit of account. The revenue recognized from single units of accounting are typically allocated and classified on the consolidated statements of operations as product revenue and support and services revenue. Since VSOE cannot be established, VSOE of similar maintenance offerings provides the basis for the support and services revenue classification, and the remaining residual consideration provides the basis for the product revenue classification. In 2013, the Company entered into a joint development agreement whereby final acceptance of the software delivered under the joint development agreement occurred on November 16, 2014. During 2014, the Company began to recognize the total committed fee as revenue ratably over a twenty-five and a half month period which began on November 16, 2014 which included a contractual twenty-four month maintenance period. During the first quarter of 2015, the customer elected to terminate their maintenance agreement and as such all unrecognized deferred revenue was accelerated and recognized as product revenue during the quarter. During the six months ended June 30, 2015, the Company recorded total product revenue of approximately $11.3 million related to this agreement. There was no product revenue recorded during the three months ended June 30, 2015 related to this agreement. As of June 30, 2015, there is no deferred revenue or undelivered services remaining related to this agreement.