XML 45 R17.htm IDEA: XBRL DOCUMENT v2.4.0.6
12. DARPA CONTRACT AND RELATED REVENUE RECOGNITION
6 Months Ended
Sep. 30, 2012
Darpa Contract And Related Revenue Recognition  
DARPA CONTRACT AND RELATED REVENUE RECOGNITION

With respect to revenue recognition, we entered into a government contract with DARPA and have recognized revenue during the fiscal year ended March 31, 2012 of $1,358,189 under such contract. We adopted the Milestone method of revenue recognition for the DARPA contract under ASC 605-28 “Revenue Recognition – Milestone Method” and we believe we meet the requirements under ASC 605-28 for reporting contract revenue under the Milestone Method for the fiscal year ended March 31, 2012.

 

In order to account for this contract, the Company identifies the deliverables included within the contract and evaluates which deliverables represent separate units of accounting based on if certain criteria are met, including whether the delivered element has standalone value to the collaborator. The consideration received is allocated among the separate units of accounting, and the applicable revenue recognition criteria are applied to each of the separate units.

 

A milestone is an event having all of the following characteristics:

 

(1) There is substantive uncertainty at the date the arrangement is entered into that the event will be achieved. A vendor’s assessment that it expects to achieve a milestone does not necessarily mean that there is not substantive uncertainty associated with achieving the milestone.

 

(2) The event can only be achieved based in whole or in part on either: (a) the vendor’s performance; or (b) a specific outcome resulting from the vendor’s performance.

 

(3) If achieved, the event would result in additional payments being due to the vendor.

 

A milestone does not include events for which the occurrence is either: (a) contingent solely upon the passage of time; or (b) the result of a counterparty’s performance.

 

The policy for recognizing deliverable consideration contingent upon achievement of a milestone must be applied consistently to similar deliverables.

 

The assessment of whether a milestone is substantive is performed at the inception of the arrangement. The consideration earned from the achievement of a milestone must meet all of the following for the milestone to be considered substantive:

 

(1) The consideration is commensurate with either: (a) the vendor’s performance to achieve the milestone; or (b) the enhancement of the value of the delivered item or items as a result of a specific outcome resulting from the vendor’s performance to achieve the milestone;

 

(2) The consideration relates solely to past performance; and

 

(3) The consideration is reasonable relative to all of the deliverables and payment terms (including other potential milestone consideration) within the arrangement.

 

A milestone is not considered substantive if any portion of the associated milestone consideration relates to the remaining deliverables in the unit of accounting (i.e., it does not relate solely to past performance). To recognize the milestone consideration in its entirety as revenue in the period in which the milestone is achieved, the milestone must be substantive in its entirety. Milestone consideration cannot be bifurcated into substantive and nonsubstantive components. In addition, if a portion of the consideration earned from achieving a milestone may be refunded or adjusted based on future performance, the related milestone is not considered substantive.