Submission Method Sample Clauses

Submission Method. The City issues and receives most solicitations electronically through the Bid Management Vendor Portal. However, in the event paper proposals are requested, such proposals must be submitted in sealed envelopes and should be properly identified with the Proposal number and the Submission Deadline. Telephone, facsimile, or late Proposals will not be accepted or considered. TAXES Successful Proposer shall pay all federal, state and taxes, levies, duties and assessments of every nature due in connection with any work under the contract and shall indemnify and hold harmless the City of Anaheim from any liability on account of any and all such taxes, levies, duties, assessments and deductions. Proposal prices shall include allowance for said taxes.

Submission Method. The Recipient shall submit Reports and/or data securely, by one of the following methods:

Submission Method. (i) The guidance as outlined in Section 4.1 (b) of this Guideline shall apply in like manner to Master Services Agreements executed after the coming into operation of the Act as they apply to Master Services Agreements still in-force immediately before the coming into operation of the Act.

Submission Method. 3.1 Client will submit support incidents to the Telesign Customer Success team via email or phone as further defined in the Support Incident Escalation to Telesign process below (Table 1). Below outlines the types of Support inquiries that may arise, and the method that the Telesign team will take in responding to these inquiries, as well as the expected timeframe (SLAs). • Severity 3 – Functional Issues & Support Inquiries o Issue Types ▪ Escalation of a single user experience. Additional investigation requested from Telesign Support. ▪ Feature requests, functional questions and general product inquiries. Customer business is not impacted. o Response Expectations – Email response/ticket updates. o Initial Response Target– 1 business day. o Subsequent Updates – As appropriate. • Severity 2 – Services Impaired o Issue Types ▪ One or more services appear to be impacted. ▪ Multiple users reporting severe slowness or degradation of service. ▪ Voice call or SMS messages being delayed to certain countries or regions at a non-standard level. ▪ Intermittent availability of Telesign API. o Response Expectations – Primary –Email response/ticket updates. Secondary -Telephone. o Initial Response Target– 120 minutes. o Subsequent Updates – Every 2 hours/As appropriate. • Severity 1 – Critical Service Issue o Issue Types ▪ Client unable to access Telesign’s API. ▪ Majority of voice calls or SMS messages not being received by end users or the majority of messages subject to non-standard delays. ▪ Client inquiry claiming any service is ‘down’. o Response Expectations – Primary –Email response/ticket updates. Secondary -Telephone. o Initial Response Target– 60 minutes. o Subsequent Updates – Every 1 hour/As appropriate. 3.2 Any reported support incident that has been deemed as having been caused by a failure outside of Telesign’s control will be returned to Client with an appropriate explanation. 3.3 For each support incident, Client is required to provide the Telesign Customer Success team with all necessary information to facilitate timely problem resolution via phone or email. If any information is incomplete, resolution to the support incident may be delayed until Client provides the necessary information to facilitate timely problem resolution. 3.4 Telesign will investigate/communicate the incident based on the Telesign Escalation process/procedures detailed in the Telesign Incident Definitions and Handling Process. For support incident escalation by Client to the Tel...

Submission Method. Customer may contact Customer Support through: (a) Customer support portal (b) ▇-▇▇▇-▇▇▇-▇▇▇▇

Submission Method. Customer can contact the NOC through: (i) Telephone direct dial-in: New York (+▇) ▇▇▇-▇▇▇-▇▇▇▇ Los Angeles: (+▇) ▇▇▇-▇▇▇-▇▇▇▇ London +▇▇ (▇) ▇▇▇-▇▇▇-▇▇▇▇ (ii) E-mail at ▇▇▇@▇▇▇▇▇▇▇▇▇.▇▇

Submission Method. Grantee shall submit all documentation or reports electronically to ▇▇▇▇▇▇▇▇▇▇▇@▇▇▇▇.▇▇▇▇▇.▇▇.▇▇, HHSC Contract Representative and the HHSC Project Manager.

Submission Method. (i) Contractors, Sub-Contractors or Licensees are required to submit all MSAs as provided for in Section 3 of this Guideline to the Local Content Secretariat. (ii) Contractors, Sub-Contractors or Licensees are required to submit a “Notice of Submission of Master Services Agreement” and an attached FORM B submitted to the Secretariat. The format of this Notice is provided in Appendix 1 of this Guideline while FORM B is provided as an attachment to this Guideline. (iii) Form B provides a summary of the Master Services Agreements being submitted to the Local Content Secretariat for review.

Submission Method. (Go to section) Instructions: This section provides a general outline of how the data submission will occur. The method may be through a digital interface or a physical transfer. Details of a digital data transfer are likely more appropriate in an ICD. If available, a relevant ICD may be referenced. The Delivery Method should include the protocol and mode (e.g., FTP PUSH, or Express Mail). In Delivery Network, identify the server or system that will host the data transfer. The Transfer Initiation is the call or method that will initiate the transfer. Security Steps may be required for restricted data transfers and/or susceptible communication channels. More submission details can be provided in Additional Information.