Submission Methods Sample Clauses

Submission Methods. SECURE G2G Portal User Interface (UI) – government agencies who will be scanning paper or uploading image files directly into the SECURE G2G Portal must use a token for authentication. Government agencies will receive recording confirmation via the UI. The UI allows user to upload a pre-scanned 300 DPI TIFF Group IV image or use a browser scanner ▇▇▇▇▇ plugin. SECURE G2G Portal Web API (API) – government agencies that directly connect to the API must adhere to the XSD standard. The XML files that are uploaded must include Base64 encoded 300 DPI TIFF Group IV image files. This process does not require a user to be involved in the transfer; it is an automatic process that will be programmed by the submitter in conjunction with the County. Agencies will receive recorded information via XML return package.
View SourceView Similar (2)
Submission Methods. SECURE G2G Portal User Interface (UI) – State Government Agencies who will be scanning paper or uploading image files directly into the SECURE G2G Portal must use a token for authentication. State Government Agencies will receive recording confirmation via the UI. The UI allows user to upload a pre-scanned 300 DPI TIFF Group IV image or use a browser scanner ▇▇▇▇▇ plugin. SECURE G2G Portal Web API (API) – State Government Agencies that directly connect to the API must adhere to the XSD standard. The XML files that are uploaded must include Base64 encoded 300 DPI TIFF Group IV image files. This process does not require a user to be involved in the transfer; it is an automatic process that will be programmed by the submitter in conjunction with the County. State Government Agencies will receive recorded information via XML return batch. SECURE G2G Portal File Transfer Site (File Transfer Site) – State Government Agencies that use the File Transfer Site will use secure file transfer protocols (FTPS or SFTP) to upload XML files. The SECURE G2G Portal will process the XML files uploaded by State Government Agencies and submit the XML files to the SECURE Web API on behalf of the State Government Agencies. The XML files shall remain encrypted in transit until they reach the designated Participating County. XML files containing recording confirmations will be placed on the File Transfer Site within one Participating County business day, not including Participating County’s holidays, for State Government Agencies to retrieve. The design of the single standard XML file format for use with the File Transfer Site will include all elements required by any County for recording documents. State Government Agency will use a standard naming convention to identify the Partner or Owner Participating County with which the file is to be recorded. State Government Agency will confirm that the name of the response file reflects the same county that was identified in the submission file.
View SourceView Similar (2)
Submission Methods. You must submit your application through ▇▇▇▇▇▇.▇▇▇ unless we give you an exemption for a paper submission. See get registered. For instructions on how to submit in ▇▇▇▇▇▇.▇▇▇, see Quick Start Guide for Applicants. Make sure that your application passes the ▇▇▇▇▇▇.▇▇▇ validation checks or we may not get it. Do not encrypt, zip, or password protect any files. See Contacts and Support if you need help. This NOFO is not subject to Executive Order 12372, Intergovernmental Review of Federal Programs. No action is needed other than checking “No” on the SF-424 box 19c.
View Source
Submission Methods. SECURE ERDS User Interface (UI)– users who will be scanning paper or uploading image files directly into SECURE ERDS will receive recording confirmation via the SECURE ERDS UI. SECURE ERDS UI allows user to upload a pre-scanned 300 DPI TIFF Group IV image or use a browser scanner ▇▇▇▇▇ plugin. SECURE ERDS Web API – users that directly connect to the SECURE ERDS Web API must adhere to the XSD standard. The SECURE ERDS XML files that are uploaded must include Base64 encoded 300 DPI TIFF Group IV image files. This process does not require a user to be involved in the transfer; it is an automatic process that will be programmed by the submitter in conjunction with the County. Users will receive recorded information via XML return package. HTTPS is required for the submission of instruments. The required security framework is provided for in the SECURE ERDS software. The ERDS software shall use a minimum of 128 bit file and image encryption. Industry standard Secure Sockets Layer (SSL) and user login with password that is encrypted shall be employed. User passwords are controlled by the user and at a minimum changed at 90 day intervals to reduce security exposure. a) Endpoint Security (Authentication Token) - one token will be required for each user that will be utilizing SECURE ERDS. For use of the token to submit documents for ERDS recording electronically, please refer to the SECURE ERDS User Manual.
View Source
Submission Methods. Two submission functions are provided as part of the Pipeline Service. One submit function, batch_submit, is provided for submission of workflows which are not interactively monitored. While int_submit is provided for interactively monitored workflows, such as those created from an authoring environment e.g. the LONI Pipeline. Both functions take a sessionID, which maps a particular user to the submitted workflow and a workflow specification is provided as a SOAP attachment.
View Source

Related to Submission Methods

  • Construction Methods 3.1 The Contractor shall provide all tools, equipment, materials, labor and work for the excavation and removal of the unsuitable subgrade soils and their subsequent replacement with the specified backfill soils as directed by the Owner’s representative. All work under this item shall be performed in a safe and workmanlike manner. 3.2 All work shall be performed in accordance with DelDOT Standard Specifications Section 821. 3.3 Following the removal of existing pavements, the Owner’s representative will review the exposed subgrade and provide recommendations for the undercutting of unsuitable subgrade materials as required. The depth and extent of undercut excavation, if required, will be determined by the Owner’s representative at the time of excavation. 3.4 All excavated materials shall become the property of the Contractor and be removed from the site at the completion of the project at no additional expense to the Owner. 3.5 Undercut excavations should be backfilled with graded aggregate. Backfill shall be placed in loose lifts not exceeding 8 inches thick. Each lift should be compacted with at least 3 passes of a minimum 5-ton, walk-behind or self-propelled vibratory roller when the size of the area permits, or with a vibrating plate mechanical compactor for smaller areas. Lift thickness shall be reduced to 6 inch loose lift when using a vibratory plate compactor. 3.6 The Contractor shall take precautions as necessary to minimize the potential for disturbance or softening of the pavement subgrade materials from inclement weather or construction traffic. As a minimum, this shall include the placement of backfill on the same day as the excavation. Any soft areas which develop shall be undercut and replaced with graded aggregate at no additional cost to the Owner. 3.7 Where undercutting is performed, the geotextile fabric shall be installed. The fabric should be pulled tight and lapped a minimum of 12 inches.

  • Alternative Resolution Methods Any time during the grievance process, by mutual consent, the parties may use alternative methods to resolve the dispute. If the parties agree to use alternative methods, the time frames in this Article are suspended. If the selected alternative method does not result in a resolution, the Union may return to the grievance process and the time frames resume. Any expenses and fees of alternative methods will be shared equally by the parties.

  • BID SUBMISSION All Bids are to be packaged, sealed and submitted to the location stated in the Bid Specifications. Bidders are solely responsible for timely delivery of their Bids to the location set forth in the Bid Specifications prior to the stated Bid opening date/time. A Bid return envelope, if provided with the Bid Specifications, should be used with the Bid sealed inside. If the Bid response does not fit into the envelope, the Bid envelope should be attached to the outside of the sealed box or package with the Bid inside. If using a commercial delivery company that requires use of their shipping package or envelope, Bidder’s sealed Bid, labeled as detailed below, should be placed within the shipper’s sealed envelope to ensure that the Bid is not prematurely opened. All Bids must have a label on the outside of the package or shipping container outlining the following information: “BID ENCLOSED (bold print, all capitals) • Group Number • IFB or RFP Number • Bid Submission date and time” In the event that a Bidder fails to provide such information on the return Bid envelope or shipping material, the receiving entity reserves the right to open the shipping package or envelope to determine the proper Bid number or Product group, and the date and time of Bid opening. Bidder shall have no claim against the receiving entity arising from such opening and such opening shall not affect the validity of the Bid or the procurement. Notwithstanding the receiving agency’s right to open a Bid to ascertain the foregoing information, Bidder assumes all risk of late delivery associated with the Bid not being identified, packaged or labeled in accordance with the foregoing requirements. All Bids must be signed by a person authorized to commit the Bidder to the terms of the Bid Documents and the content of the Bid (offer).

  • Claims Submission We will submit your claims and assist you in any way we reasonably can to help get your claims paid. Your insurance company may need you to supply certain information directly. It is your responsibility to comply with their request. Please be aware that the balance of your claim is your responsibility whether or not your insurance company pays your claim. Your insurance benefit is a contract between you and your insurance company; we are not party to that contract.

  • NOTIFICATIONS AND SUBMISSION OF REPORTS Unless otherwise stated in writing after the Effective Date, all notifications and reports required under this IA shall be submitted to the following entities: Administrative and Civil Remedies Branch Office of Counsel to the Inspector General Office of Inspector General U.S. Department of Health and Human Services ▇▇▇▇▇ Building, Room 5527 ▇▇▇ ▇▇▇▇▇▇▇▇▇▇▇▇ ▇▇▇▇▇▇, ▇▇ ▇▇▇▇▇▇▇▇▇▇, ▇▇ ▇▇▇▇▇ Telephone: (▇▇▇) ▇▇▇-▇▇▇▇ Facsimile: (▇▇▇) ▇▇▇-▇▇▇▇ LFAC: ▇▇▇▇▇▇▇ ▇. ▇▇▇▇▇, DPM ▇▇▇▇ ▇▇▇▇▇▇▇▇▇▇▇ ▇▇. ▇-▇▇▇ ▇▇▇▇▇▇▇▇▇, ▇▇ ▇▇▇▇▇ Telephone: (▇▇▇) ▇▇▇-▇▇▇▇ Email: ▇▇.▇▇▇▇▇@▇▇▇▇▇.▇▇▇ Unless otherwise specified, all notifications and reports required by this IA may be made by electronic mail, overnight mail, hand delivery, or other means, provided that there is proof that such notification was received. Upon request by OIG, LFAC may be required to provide OIG with an additional copy of each notification or report required by this IA in OIG’s requested format (electronic or paper).