Revenue Recognition Effective January 1, 2017, the Company adopted Accounting Standards Codification (ASC), Topic 606, Revenue from Contracts with Customers (Topic 606). This standard applies to all contracts with customers, except for contracts that are within the scope of other standards, such as collaboration arrangements and leases. Prior to the three months ended June 30, 2018, when the Company recorded its initial revenue under Topic 606, the Company did not have any revenue-generating arrangements and therefore there was no transition impact from the adoption of Topic 606. Under Topic 606, an entity recognizes revenue when its customer obtains control of promised goods or services, in an amount that reflects the consideration that the entity expects to receive in exchange for those goods or services. To determine revenue recognition for arrangements that an entity determines are within the scope of Topic 606, the entity performs the following five steps: (i) identify the contract with a customer; (ii) identify the performance obligations in the contract; (iii) determine the transaction price, including variable consideration, if any; (iv) allocate the transaction price to the performance obligations in the contract; and (v) recognize revenue when (or as) the entity satisfies a performance obligation. The Company only applies the five-step model to contracts when it is probable that the Company will collect the consideration to which it is entitled in exchange for the goods or services it transfers to a customer. Once a contract is determined to be within the scope of Topic 606, the Company assesses the goods or services promised within each contract and determines those that are performance obligations. Arrangements that include rights to additional goods or services that are exercisable at a customers discretion are generally considered options. The Company assesses if these options provide a material right to the customer and if so, they are considered performance obligations. The exercise of a material right may be accounted for as a contract modification or as a continuation of the contract for accounting purposes. The Company assesses whether each promised good or service is distinct for the purpose of identifying the performance obligations in the contract. This assessment involves subjective determinations and requires management to make judgments about the individual promised goods or services and whether such are separable from the other aspects of the contractual relationship. Promised goods and services are considered distinct provided that: (i) the customer can benefit from the good or service either on its own or together with other resources that are readily available to the customer (that is, the good or service is capable of being distinct) and (ii) the entitys promise to transfer the good or service to the customer is separately identifiable from other promises in the contract (that is, the promise to transfer the good or service is distinct within the context of the contract). In assessing whether a promised good or service is distinct in the evaluation of a collaboration arrangement subject to Topic 606, the Company considers factors such as the research, manufacturing and commercialization capabilities of the collaboration partner and the availability of the associated expertise in the general marketplace. The Company also considers the intended benefit of the contract in assessing whether a promised good or service is separately identifiable from other promises in the contract. If a promised good or service is not distinct, the Company is required to combine that good or service with other promised goods or services until it identifies a bundle of goods or services that is distinct. The transaction price is then determined and allocated to the identified performance obligations in proportion to their standalone selling prices (SSP) on a relative SSP basis. SSP is determined at contract inception and is not updated to reflect changes between contract inception and when the performance obligations are satisfied. Determining the SSP for performance obligations requires significant judgment. In developing the SSP for a performance obligation, the Company considers applicable market conditions and relevant entity-specific factors, including factors that were contemplated in negotiating the agreement with the customer and estimated costs. In certain circumstances, the Company may apply the residual method to determine the SSP of a good or service if the standalone selling price is considered highly variable or uncertain. The Company validates the SSP for performance obligations by evaluating whether changes in the key assumptions used to determine the SSP will have a significant effect on the allocation of arrangement consideration between multiple performance obligations. If the consideration promised in a contract includes a variable amount, the Company estimates the amount of consideration to which it will be entitled in exchange for transferring the promised goods or services to a customer. The Company determines the amount of variable consideration by using the expected value method or the most likely amount method. The Company includes the unconstrained amount of estimated variable consideration in the transaction price. The amount included in the transaction price is constrained to the amount for which it is probable that a significant reversal of cumulative revenue recognized will not occur. At the end of each subsequent reporting period, the Company re-evaluates the estimated variable consideration included in the transaction price and any related constraint, and if necessary, adjusts its estimate of the overall transaction price. Any such adjustments are recorded on a cumulative catch-up basis in the period of adjustment. If an arrangement includes development and regulatory milestone payments, the Company evaluates whether the milestones are considered probable of being reached and estimates the amount to be included in the transaction price using the most likely amount method. If it is probable that a significant revenue reversal would not occur, the associated milestone value is included in the transaction price. Milestone payments that are not within the Companys control or the licensees control, such as regulatory approvals, are generally not considered probable of being achieved until those approvals are received. In determining the transaction price, the Company adjusts consideration for the effects of the time value of money if the timing of payments provides the Company with a significant benefit of financing. The Company does not assess whether a contract has a significant financing component if the expectation at contract inception is such that the period between payment by the licensees and the transfer of the promised goods or services to the licensees will be one year or less. The Company assessed its revenue-generating arrangement in order to determine whether a significant financing component exists and concluded that a significant financing component does not exist in the arrangement. For arrangements with licenses of intellectual property that include sales-based royalties, including milestone payments based on the level of sales, and the license is deemed to be the predominant item to which the royalties relate, the Company recognizes royalty revenue and sales-based milestones at the later of (i) when the related sales occur, or (ii) when the performance obligation to which the royalty has been allocated has been satisfied. The Company then recognizes as revenue the amount of the transaction price that is allocated to the respective performance obligation when (or as) each performance obligation is satisfied at a point in time or over time, and if over time this is based on the use of an output or input method.