Common use of Once the Performer accomplishes Clause in Contracts

Once the Performer accomplishes. a Payable Milestone, the Performer may seek payment from the Government of the corresponding payment amount in the Payable Milestones and Corresponding Payment Schedule in Attachment 3. The Performer shall document the accomplishment of such Payable Milestone by submitting or otherwise providing the Payable Milestones Report required by Attachment 2, Part F. After written verification of the accomplishment of such Payable Milestone by the DARPA Agreements Officer’s Representative and approval by the DARPA Agreements Officer, the associated invoice will be submitted to the payment office via Wide Area Workflow (“WAWF”), as detailed in subparagraph B.6 of this Article. If a Payable Milestone is composed of more than one task (e.g., Payable Milestones 2, 6, 7, etc.), all such tasks in such Payable Milestone must be fully accomplished before the Performer may seek payment for such Payable Milestone. However, if a task in a single task Payable Milestone (or all of the tasks in a multi-task Payable Milestone) cannot be completed by the applicable Milestone (MS) Month set forth in Attachment 3, the Performer will document such event in its Monthly Technical Status Report, and the Parties will execute a contract modification to incorporate required changes in Attachment 3, and in Attachments 1 and 4, as applicable. For clarity, the “MS Mxxxx” column set forth in Attachment 3 sets forth the Parties’ good faith estimate of the date by which a Payable Milestone will be accomplished, but it is not a deadline for accomplishing the applicable Payable Milestone. In addition, missing the MS Month does not prevent the Performer from subsequently accomplishing the applicable Payable Milestone and has no effect on the corresponding payment amount in Attachment 3 once accomplished. If deemed necessary by the DARPA Agreements Officer, payment approval for the final Payable Milestone will be made after reconciliation of actual Government funding for the Program with the actual Performer Contribution amount. While there will be this final Government reconciliation and accounting of the Performer Contribution amount, the Parties agree that the quarterly accounting of the Performer Contribution, as reported in the quarterly Business Status Report submitted in accordance with Attachment 2, will not, nor is it necessarily intended or required to, uniformly or proportionally track or match the estimated schedule of the Performer Contribution set forth in either Attachments 3 or 4.

Once the Performer accomplishes. a Payable Milestone, the Performer may seek payment from the Government of the corresponding payment amount in the Payable Milestones and Corresponding Payment Schedule in Attachment 3. The Performer shall document the accomplishment of such Payable Milestone by submitting or otherwise providing the Payable Milestones Report required by Attachment 2, Part F. After written verification of the accomplishment of such Payable Milestone by the DARPA Agreements Officer’s Representative and approval by the DARPA Agreements Officer, the associated invoice will be submitted to the payment office via Wide Area Workflow (“WAWF”), as detailed in subparagraph B.6 of this Article. If a Payable Milestone is composed of more than one task (e.g., Payable Milestones 2, 6, 7, etc.), all such tasks in such Payable Milestone must be fully accomplished before the Performer may seek payment for such Payable Milestone. However, if a task in a single task Payable Milestone (or all of the tasks in a multi-task Payable Milestone) cannot be completed by the applicable Milestone (MS) Month set forth in Attachment 3, the Performer will document such event in its Monthly Technical Status Report, and the Parties will execute a contract modification to incorporate required changes in Attachment 3, and in Attachments 1 and 4, as applicable. For clarity, the “MS MxxxxXxxxx” column set forth in Attachment 3 sets forth the Parties’ good faith estimate of the date by which a Payable Milestone will be accomplished, but it is not a deadline for accomplishing the applicable Payable Milestone. In addition, missing the MS Month does not prevent the Performer from subsequently accomplishing the applicable Payable Milestone and has no effect on the corresponding payment amount in Attachment 3 once accomplished. If deemed necessary by the DARPA Agreements Officer, payment approval for the final Payable Milestone will be made after reconciliation of actual Government funding for the Program with the actual Performer Contribution amount. While there will be this final Government reconciliation and accounting of the Performer Contribution amount, the Parties agree that the quarterly accounting of the Performer Contribution, as reported in the quarterly Business Status Report submitted in accordance with Attachment 2, will not, nor is it necessarily intended or required to, uniformly or proportionally track or match the estimated schedule of the Performer Contribution set forth in either Attachments 3 or 4.

Once the Performer accomplishes. a Payable Milestone, the Performer may seek payment from the Government of the corresponding payment amount in the Payable Milestones and Corresponding Payment Schedule in Attachment 3. The Performer shall document the accomplishment of such Payable Milestone by submitting or otherwise providing the Payable Milestones Report required by Attachment 2, Part F. After written verification of the accomplishment of such Payable Milestone by the DARPA [*] Certain portions denoted with an asterisk have been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. Agreements Officer’s Representative and approval by the DARPA Agreements Officer, the associated invoice will be submitted to the payment office via Wide Area Workflow (“WAWF”), as detailed in subparagraph B.6 of this Article. If a Payable Milestone is composed of more than one task (e.g., Payable Milestones 2, 6, 7, etc.), all such tasks in such Payable Milestone must be fully accomplished before the Performer may seek payment for such Payable Milestone. However, if a task in a single task Payable Milestone (or all of the tasks in a multi-task Payable Milestone) cannot be completed by the applicable Milestone (MS) Month set forth in Attachment 3, the Performer will document such event in its Monthly Technical Status Report, and the Parties will execute a contract modification to incorporate required changes in Attachment 3, and in Attachments 1 and 4, as applicable. For clarity, the “MS MxxxxXxxxx” column set forth in Attachment 3 sets forth the Parties’ good faith estimate of the date by which a Payable Milestone will be accomplished, but it is not a deadline for accomplishing the applicable Payable Milestone. In addition, missing the MS Month does not prevent the Performer from subsequently accomplishing the applicable Payable Milestone and has no effect on the corresponding payment amount in Attachment 3 once accomplished. If deemed necessary by the DARPA Agreements Officer, payment approval for the final Payable Milestone will be made after reconciliation of actual Government funding for the Program with the actual Performer Contribution amount. While there will be this final Government reconciliation and accounting of the Performer Contribution amount, the Parties agree that the quarterly accounting of the Performer Contribution, as reported in the quarterly Business Status Report submitted in accordance with Attachment 2, will not, nor is it necessarily intended or required to, uniformly or proportionally track or match the estimated schedule of the Performer Contribution set forth in either Attachments 3 or 4.