Deliverable name WP no Sample Clauses

Deliverable name WP no. Lead participant D16 Project Presentation (WEB Presence) 7 AIT Estimated person-months Del. type Security Delivery (proj.-month)
Sample 1Sample 2See All (6)
AutoNDA by SimpleDocs
Deliverable name WP no. Lead bene- ficiary Estimated indicative person- months Nature9 Dissemi- nation level 10 Delivery date11 (proj. month) D1 First generation opportunistic context recognition chain 1,2,3 UP 39 R PU 12 D2 Second generation opportunistic contextrecognition chain 1,2,3 ETHZ 45 R PU 24 D3 Third generation opportunistic context recognition chain incl. opportunistic BCI 1,2,3 EPFL 47 R PU 36 D4.1 Self-description mark-up language, self- aggregation and self- composition algorithms 4 JKU 12 R PU 12 D4.2 Goal description language and coordination architecture for decentralized self- management, 4 JKU 10 R PU 24 D4.3 Validation of OPPORTUNITY Framework 4 JKU 11 R PU 36 D5.1 Stage 1 case study report and stage 2 specification 5 UP 10 R PU 12 D5.2 Stage 2 case study report and stage 3 specification 5 UP 11 R PU 24 D5.3 Stage 3 (incl. opportunistic BCI) case study report 5 UP 12 R PU 36 D6.1 Annual Report 1st Year 6 ETHZ 2 R CO 12 D6.2 Annual Report 2nd Year 6 ETHZ 2 R CO 24 7 In a project which uses ‘Classified information7’ as background or which produces this as foreground the template for the deliverables list in Annex 7 has to be used 8 Deliverable numbers in order of delivery dates: D1 – Dn 9 Please indicate the nature of the deliverable using one of the following codes: R = Report, P = Prototype, D = Demonstrator, O = Other 10 Please indicate the dissemination level using one of the following codes: PU = Public PP = Restricted to other programme participants (including the Commission Services) RE = Restricted to a group specified by the consortium (including the Commission Services) CO = Confidential, only for members of the consortium (including the Commission Services) 11 Month in which the deliverables will be available. Month 1 marking the start date of the project, and all delivery dates being relative to this start date.
Sample 1
Deliverable name WP no. Lead participant D5 The REGNET-System, Version-1 2 ZEUS Estimated person-months Del. type Security Delivery (proj.-month)
Sample 1
Deliverable name WP no. Leader beneficiary Estimated indicative person- months Nature12 Dissemi- nation level13 Delivery date14 D1.1 Periodic Report for period 1 (year 1) 1 ST 3 R PU M12 D1.2 Periodic Report for period 2 (year 2) 1 ST 3 R PU M24 D1.3 Final report 1 ST 3 R PU M36 D1.4 Interim Report for period 1 1 ST 2 R PU M6 D1.5 Interim Report for period 2 1 ST 2 R PU M18 D1.6 Interim Report for period 3 1 ST 2 R PU M30 11 Deliverable numbers in order of delivery dates: D1 – Dn 12 Please indicate the nature of the deliverable using one of the following codes: R = Report, P = Prototype, D = Demonstrator, O = Other 13 Please indicate the dissemination level using one of the following codes: PU = Public PP = Restricted to other programme participants (including the Commission Services) RE = Restricted to a group specified by the consortium (including the Commission Services) CO = Confidential, only for members of the consortium (including the Commission Services) 14 Month in which the deliverables will be available. Month 1 marking the start date of the project, and all delivery dates being relative to this start date.
Sample 1

Related to Deliverable name WP no

  • Conversion of Live Telephone Exchange Service to Analog 2W Loops The following coordination procedures shall apply to “live” cutovers of VERIZON Customers who are converting their Telephone Exchange Services to SPRINT Telephone Exchange Services provisioned over Analog 2W unbundled Local Loops (“Analog 2W Loops”) to be provided by VERIZON to SPRINT.

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • Shipping must be Freight On Board Destination to the delivery location designated on the Customer purchase order The Contractor will retain title and control of all goods until delivery is completed and the Customer has accepted the delivery. All risk of transportation and all related charges are the responsibility of the Contractor. The Customer will notify the Contractor and H-GAC promptly of any damaged goods and will assist the Contractor in arranging for inspection. The Contractor must file all claims for visible or concealed damage. Unless otherwise stated in the Agreement, deliveries must consist only of new and unused merchandise.

  • Unbundled Voice Loop – SL2 (UVL-SL2 Loops may be 2-wire or 4-wire circuits, shall have remote access test points, and will be designed with a DLR provided to NewPhone. SL2 circuits can be provisioned with loop start, ground start or reverse battery signaling. OC is provided as a standard feature on XX0 Xxxxx. The OC feature will allow NewPhone to coordinate the installation of the Loop with the disconnect of an existing customer’s service and/or number portability service. In these cases, BellSouth will perform the order conversion with standard order coordination at its discretion during normal work hours.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.

  • Purchase Order and Sales Contact Name Please identify the individual who will be responsible for receiving and processing purchase orders and sales under the TIPS Contract.

Time is Money Join Law Insider Premium to draft better contracts faster.