Summary of Significant Accounting Policies (Policies)	3 Months Ended
Mar. 31, 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 and as stand-alone software applications. 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 and 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 customers typically send the Company a purchase order when they have an end user identified. Distributor customers typically send the Company a purchase order when they have a reseller and 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. 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 three months ended March 31, 2015, the Company recorded total product revenue of approximately $11.3 million related to this agreement. As of March 31, 2015, there is no deferred revenue 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 and as stand-alone software applications. 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 and 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 customers typically send the Company a purchase order when they have an end user identified. Distributor customers typically send the Company a purchase order when they have a reseller and 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.

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 three months ended March 31, 2015, the Company recorded total product revenue of approximately $11.3 million related to this agreement. As of March 31, 2015, there is no deferred revenue related to this agreement.