XML 47 R16.htm IDEA: XBRL DOCUMENT v2.4.0.8
Basis of Reporting (Policies)
3 Months Ended
Mar. 29, 2014
Accounting Policies [Abstract]  
Revenue Recognition, Policy [Policy Text Block]
Revenue Recognition - The Company recognizes revenue from time and materials consulting contracts in the period in which its services are performed. In addition to time and materials contracts, the Company also has fixed fee contracts. The Company recognizes revenues on milestone or deliverables-based fixed fee contracts and time and materials contracts not to exceed contract price using the percentage of completion-like method described by Financial Accounting Standards Board ("FASB") Accounting Standards Codification ("ASC") 605-35,"Revenue Recognition - Construction-Type and Production-Type Contracts." For fixed fee contracts where services are not based on providing deliverables or achieving milestones, the Company recognizes revenue on a straight-line basis over the period during which such services are expected to be performed. In connection with some fixed fee contracts, the Company may receive payments from customers that exceed revenues up to that point in time. The Company records the excess of receipts from customers over recognized revenue as deferred revenue. Deferred revenue is classified as a current liability to the extent it is expected to be earned within twelve months from the date of the balance sheet.
 
The FASB ASC 605-35 percentage-of-completion-like methodology involves recognizing revenue using the percentage of services completed, on a current cumulative cost to total cost basis, using a reasonably consistent profit margin over the period. Due to the longer term nature of these projects, developing the estimates of costs often requires significant judgment. Factors that must be considered in estimating the progress of work completed and ultimate cost of the projects include, but are not limited to, the availability of labor and labor productivity, the nature and complexity of the work to be performed, and the impact of delayed performance. If changes occur in delivery, productivity or other factors used in developing the estimates of costs or revenues, the Company revises its cost and revenue estimates, which may result in increases or decreases in revenues and costs, and such revisions are reflected in income in the period in which the facts that give rise to that revision become known.
 
The Company develops, installs and supports customer software in addition to the provision of traditional consulting services. The Company recognizes revenue in connection with its software sales agreements under ASC 985-605, utilizing the percentage of completion-like method described in ASC 605- 35. These agreements include software right-to-use licenses ("RTU's") and related customization and implementation services. Due to the long-term nature of the software implementation and the extensive software customization based on normal customer specific requirements, both the RTU’s and implementation services are treated as a single element for revenue recognition purposes.
 
In addition to the professional services related to the customization and implementation of its software, the Company may also provide post-contract support ("PCS") services, including technical support and maintenance services as well as other professional services not essential to the functionality of the software. For those contracts that include PCS service arrangements which are not essential to the functionality of the software solution, the Company separates the FASB ASC 605-35 software services and PCS services utilizing the multiple-element arrangement model prescribed by FASB ASC 605-25, "Revenue Recognition - Multiple-Element Arrangements". FASB ASC 605-25 addresses the accounting treatment for an arrangement to provide the delivery or performance of multiple products and/or services where the delivery of a product or system or performance of services may occur at different points in time or over different periods of time. The Company utilizes FASB ASC 605-25 to separate the PCS service elements and allocate total contract consideration to the contract elements based on the relative fair value of those elements utilizing PCS renewal terms as evidence of fair value. Revenues from PCS services are recognized ratably on a straight-line basis over the term of the support and maintenance agreement.
Fair Value Measurement, Policy [Policy Text Block]
Fair Value Measurement - The Company utilizes the methods of fair value measurement as described in FASB ASC 820, “Fair Value Measurements” to value its financial assets and liabilities, including the financial instruments issued in the transaction described in Note 2, Strategic Alliance and Investment by Elutions, Inc. As defined in FASB ASC 820, fair value is based on the price that would be received to sell an asset or paid to transfer a liability in an orderly transaction between market participants at the measurement date. In order to increase consistency and comparability in fair value measurements, FASB ASC 820 establishes a fair value hierarchy that prioritizes observable and unobservable inputs used to measure fair value into three broad levels, which are described below:
 
Level 1: Quoted prices (unadjusted) in active markets that are accessible at the measurement date for assets or liabilities. The fair value hierarchy gives the highest priority to Level 1 inputs.
 
Level 2: Observable prices that are based on inputs not quoted on active markets, but corroborated by market data.
 
Level 3: Unobservable inputs are used when little or no market data is available. The fair value hierarchy gives the lowest priority to Level 3 inputs.
 
In determining fair value, the Company utilizes valuation techniques that maximize the use of observable inputs and minimize the use of unobservable inputs to the extent possible as well as considers counterparty credit risk in its assessment of fair value.
Managed Services Implementation Revenues and Costs [Policy Text Block]
Managed Services Implementation Revenues and Costs - Managed service arrangements provide for the delivery of a software or technology based solution to clients over a period of time without the transfer of a license or a software sale to the customer. For long-term managed service agreements, implementation efforts are often necessary to develop the software utilized to deliver the managed service. Costs of such implementation efforts may include internal and external costs for coding or customizing systems and costs for conversion of client data. The Company may invoice its clients for implementation fees at the go-live date of the underlying software. Lump sum implementation fees received from clients are initially deferred and recognized on a pro-rata basis as services are provided. Specific, incremental and direct costs of implementation incurred prior to the services going live are deferred pursuant to FASB ASC 605-35-25 and amortized over the period that the related ongoing services revenue is recognized to the extent that the Company believes the recoverability of the costs from the contract is probable. If a client terminates a managed services arrangement prior to the end of the contract, a loss on the contract may be recorded, if applicable, and any remaining deferred implementation revenues and costs would then be recognized into earnings generally over the remaining service period through the termination date. During the thirteen weeks ended March 29, 2014, implementation costs of $150,000 related to managed services contracts were deferred. No implementation costs related to managed services contracts were deferred during the thirteen weeks ended March 30, 2013.
Research, Development, and Computer Software, Policy [Policy Text Block]
Research and Development and Software Development Costs - During the thirteen weeks ended March 29, 2014 and March 30, 2013, software development costs of $204,000 and $195,000, respectively, were expensed as incurred. No software development costs were capitalized during the thirteen weeks ended March 29, 2014 and March 30, 2013.
Foreign Currency Transactions and Translations Policy [Policy Text Block]
Foreign Currency Transactions and Translation - Cartesian Limited and the international operations of Cambridge Strategic Management Group, Inc. conduct business primarily denominated in their respective local currency, which is their functional currency. Assets and liabilities have been translated to U.S. dollars at the period-end exchange rates. Revenues and expenses have been translated at exchange rates which approximate the average of the rates prevailing during each period. Translation adjustments are reported as a separate component of other comprehensive income (loss) in the Condensed Consolidated Statements of Operations and Comprehensive Loss. Accumulated other comprehensive loss resulting from foreign currency translation adjustments totaled $3.7 million and $3.8 million as of March 29, 2014 and December 28, 2013, respectively, and is included in Total Stockholders’ Equity in the Condensed Consolidated Balance Sheets. Assets and liabilities denominated in other than the functional currency of a subsidiary are re-measured at rates of exchange on the balance sheet date. Resulting gains and losses on foreign currency transactions are included in the Company’s results of operations. Realized and unrealized exchange gains and losses included in the results of operations were not significant during the thirteen weeks ended March 29, 2014 and March 30, 2013
Earnings Per Share, Policy [Policy Text Block]
Net Loss Per Share - The Company has not included the effect of stock options and non-vested shares in the calculation of diluted loss per share for the thirteen weeks ended March 29, 2014 and March 30, 2013 as the Company reported a net loss for these periods and the effect would have been anti-dilutive.
New Accounting Pronouncements, Policy [Policy Text Block]
Recent Accounting Pronouncements - In July 2013, the FASB issued Accounting Standards Update No. 2013-11, Presentation of an Unrecognized Tax Benefit When a Net Operating Loss Carryforward, a Similar Tax Loss, or a Tax Credit Carryforward Exists (“FASB ASU 2013-11”). The update requires that an unrecognized tax benefit, or a portion of an unrecognized tax benefit, be presented in the financial statements as a reduction to a deferred tax asset for a net operating loss carryforward, a similar tax loss, or a tax credit carryforward, except as follows. To the extent a net operating loss carryforward, a similar tax loss, or a tax credit carryforward is not available at the reporting date under the tax law of the applicable jurisdiction to settle any additional income taxes that would result from the disallowance of a tax position or the tax law of the applicable jurisdiction does not require the entity to use, and the entity does not intend to use, the deferred tax asset for such purpose, the unrecognized tax benefit should be presented in the financial statements as a liability and should not be combined with deferred tax assets. The provisions of FASB ASU 2013-11 are effective for annual and interim periods beginning after December 15, 2013. The adoption of the provisions of FASB ASU 2013-11 did not materially impact the Company's condensed consolidated financial statements.