Exchange Formats Sample Clauses

Exchange Formats. The “BIM Strategy Framework” recommends that in the Rail Baltica Global Project the information exchange and capture is done using as far as possible “Open” (non-proprietary) file formats leaving the supply chain to develop and create information for exchange using tools that fit in with their own skills and expertise. This requires suppliers of information to convert their deliveries into a format approved by RB Rail and acceptable to the project CDE also that they share that information in the CDE with other suppliers where permissions are granted. The “Detailed BIM Strategy” should take the recommended format principles outlined in the “BIM Strategy Framework” and develop them into detailed exchange formats. Taking into account the findings in the Requirements Analysis stage and the tenderers own experience in Rail Project information delivery. The “Detailed BIM Strategy” should consider whether and how native model files are captured and archived.
Sample 1
AutoNDA by SimpleDocs

Related to Exchange Formats

  • File Format Standard Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format is as follows:

  • Change Order Formats Formats for Lump Sum Change Orders and for Change Orders based upon either a force account or upon unit pricing with an indeterminate number of units are in Section 7, Forms.

  • Codebook Format The codebook describes an ASCII data set (although the data are also being provided in a SAS transport file). The following codebook items are provided for each variable: Identifier Description Name Variable name (maximum of 8 characters) Description Variable descriptor (maximum 40 characters) Format Number of bytes Type Type of data: numeric (indicated by NUM) or character (indicated by XXXX) Start Beginning column position of variable in record End Ending column position of variable in record

  • Transfer Format Transfers may include, but are not limited to, conversion of all Data into or from an industry standard format or providing application programmable interface. ENCRYPTION Data must be encrypted at all times unless specifically outlined otherwise in the Authorized User Agreement. At a minimum, encryption must be carried out at the most current NYS Encryption Standard (NYS-S14-007), (or successor policy with key access restricted to the Authorized User only, unless with the express written permission of the Authorized User. All Data in transit must be handled in accordance with ITS Policy NYS-S14-007 (or successor) or the National Institute of Standards and Technology (NIST) Federal Institute Processing Standard (FIPS)-140-2 or Transport Layer Security (TLS) 1, or TLS2 (or successor). The Authorized User Agreement shall specify the respective responsibilities of the Authorized User and the Contractor for the encryption of Data.

  • Traditional IRA-to-Xxxx XXX Conversions If you convert to a Xxxx XXX, the amount of the conversion from your Traditional IRA to your Xxxx XXX will be treated as a distribution for income tax purposes, and is includible in your gross income (except for any nondeductible contributions). Although the conversion amount generally is included in income, the 10 percent early distribution penalty tax will not apply to conversions from a Traditional IRA to a Xxxx XXX, regardless of whether you qualify for any exceptions to the 10 percent penalty tax. If you are required to take a required minimum distribution for the year, you must remove your required minimum distribution before converting your Traditional IRA.

  • Formats Formats for records must be satisfactory to FTA and include, but are not limited to, electronic records, including any emails related to the Award, records on paper, and records created in other formats.

  • Distribution Upgrades The Connecting Transmission Owner shall design, procure, construct, install, and own the Distribution Upgrades described in Attachment 6 of this Agreement. If the Connecting Transmission Owner and the Interconnection Customer agree, the Interconnection Customer may construct Distribution Upgrades. The actual cost of the Distribution Upgrades, including overheads, shall be directly assigned to the Interconnection Customer. The Interconnection Customer shall be responsible for its share of all reasonable expenses, including overheads, associated with owning, operating, maintaining, repairing, and replacing the Distribution Upgrades, as set forth in Attachment 6 to this Agreement.

  • Alternate Work Schedules Workweeks and work shifts of different numbers of hours may be established for overtime-eligible employees by the Employer in order to meet business and customer service needs, as long as the alternate work schedules meet federal and state law. When there is a holiday, employees may be required to switch from their alternate work schedules to regular work schedules.

  • Network Upgrades and Distribution Upgrades The Participating TO shall design, procure, construct, install, and own the Network Upgrades and Distribution Upgrades described in Appendix A. The Interconnection Customer shall be responsible for all costs related to Distribution Upgrades. Unless the Participating TO elects to fund the capital for the Distribution Upgrades and Network Upgrades, they shall be solely funded by the Interconnection Customer.

  • Accounting Format Applications for Payment shall be broken down by CSI Category and, in certain situations, by CSI Description and capital asset category, as set forth in the form for Application for Payment. The purpose is to provide appropriate backup documents for the Contractor’s Final Certification of Costs in conformance with GASB 34 accounting standards. See Section 7 – Forms, “Application for Payment” and Final Certification of Costs.

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