Naming Conventions Clause Samples

Naming Conventions. The North American Leadership Group (NA-LG), in conjunction with the Legal Project Team, is charged with developing the standard naming convention for future drafts produced by the A4L Community. It is expected that major agreed upon revisions (i.e. numerous new or modified clauses, exhibits or additional guidance) will utilize major release version numbers v1.0, v2.0, v3.0, etc. This will be driven when significant changes are made to the draft. Should any Community Members find non-substantive issues in the current version of the NDPA (e.g. typos, minor word agreement, small Exhibit modifications, etc.), they should inform the Legal Project Team, Vendor Project Team or SDPC Alliance Leadership Project Team at the earliest convenience. Minor agreed-upon revisions of the current version (e.g. typos, minor word agreement, small Exhibit modifications, etc.) will utilize the minor revision edits of v1.1, v1.2, v2.1, v2.2, etc.

Naming Conventions. To manage the created number of documents, common rules for file names need to be followed. File names need to comply with the following rule which is also described in D9.1 Project handbook: • EMPOWER_Index_DocName_Date_Version_Partner.ext with the following meanings: • Index Number of WP or deliverable e.g. WP1 or D1.4 • DocName Short name suitable for content identification e.g. KickOff • Date Date of document creation e.g. 2023-05-22 • Version Version number e.g. V1.1 • Partner Acronym of document responsible partner e.g. AIT • ext File extension e.g. pptx

Naming Conventions. No change.

Naming Conventions. After Closing Buyer will honor all donor agreements for the naming of buildings, facilities or programs at the Hospitals.

Naming Conventions. A. Landlord and Tenant hereby acknowledge and agree that prior to the 1A Effective Date, Landlord has caused (i) Suite 1.14A in the Building to be renumbered to Suite 418A, (ii) Suite 1.5 in the Building to be renumbered to Suite 405, (iii) Suite 1.5.1 in the Building to be renumbered to Suite 407, and (iv) Suite 1.5.2 to be renumbered to Suite 409. B. Accordingly, effective as of, and from and after, the 1A Effective Date, (i) all references in the Lease to “Suite 1.14A” are hereby deemed to be references to “Suite 418A”, (ii) all references in the Lease to “Suite 1.5” are hereby deemed to be references to “Suite 405”, (iii) all references in the Lease to “Suite 1.5.1” are hereby deemed to be references to “Suite 407”, and (iv) all references in the Lease to “Suite 1.5.2” are hereby deemed to be references to “Suite 409”. Suite 418A, as it exists on the 1A Effective Date, is also referred to in this Amendment as “Original Suite 418A”.

Naming Conventions. The Grantee will use the naming conventions as shown in the chart below when establishing agency programs in FACSPro. Use the Agency Program Name column for identifying the naming convention for program names and the System Program column for selecting the appropriate system program. The Grantee System Administrator can add text to the agency program name after the required label. • Agency Program Name and System Program: • Locate the PROGRAM in the first column of the chart • Enter the corresponding AGENCY PROGRAM NAME • Make sure the corresponding SYSTEM PROGRAM is selected during setup Examples: Program: CSBG Agency Name: BCAEO-CSBG-(Agency to determine) System Program: CSBG Agency Program Naming Chart PROGRAM AGENCY PROGRAM NAME * SYSTEM PROGRAM CSBG BCAEO‐CSBG‐(Agency to Determine) CSBG CSBGD BCAEO‐CSBG DISCRETIONARY Discretionary Funds Program CSBGM BCAEO‐CSBG MIGRANT SERVICES Migrant Services CSBGT BCAEO‐CSBG VITA TAX SERVICES VITA‐Tax Preparation Program CSBGT BCAEO‐CSBG NON VITA TAX SERVICES Tax Preparation Program‐NON VITA LCA BCAEO‐LCA Emergency Services‐FUEL‐LCA MEAP LCA BCAEO-MEAP-LCA Emergency Services-MEAP-Deliverable Fuel DOE/LIHEAP BCAEO-Weatherization Weatherization Grantees will use the chart shown below to standardize the grant entry for the funding type, funding source and the grant/contract number. Funding Source Naming Chart AGENCY PROGRAM NAME FUNDING TYPE FUNDING SOURCE CONTRACT NUMBER BCAEO‐CSBG‐(Agency to Determine) Federal Michigan Dept. of Human Services Contract # from SOE. Examples: BCAEO CSBG Federal Michigan Dept. of Human Services CSBGXX‐12345‐1 BCAEO‐CSBG DISCRETIONARY Federal Michigan Dept. of Human Services CSBGDXX‐12345 BCAEO‐CSBG MIGRANT SERVICES Federal Michigan Dept. of Human Services CSBGDXX‐12345 BCAEO‐CSBG VITA TAX SERVICES Federal Michigan Dept. of Human Services CSBGDXX‐12345 BCAEO‐CSBG NON VITA TAX SERVICES Federal Michigan Dept. of Human Services CSBGDXX‐12345 BCAEO‐LCA Federal Michigan Dept. of Human Services LCAXX‐12345 BCAEO MEAP LCA Federal Michigan Dept of Human Services LCAXX‐12345 Funding Source Setup (Weatherization Programs only) Weatherization Agency Programs (DOE, DOE-S, MPSC, LIHEAP, Gas Utility, and Electric Utility) are entered by the system administrator during funding setup. The weatherization funding source option in FACSPro allows the system administrator to setup multiple funding sources. Steps to setup the Weatherization Funding (Enter each funding source using the steps below): • Enter in...

Naming Conventions. 8.3.1. Model file nomenclature Here are examples of descriptions by Discipline, their letter being in parentheses. To standardize the way files are named, here are the nomenclature rules. Building Number_Discipline_Subdiscipline_Building_RevitVersion.rvt Note: Each section must be separated by an underscore. 194_M_PL_PAC_R20.rvt 1st section – Building Number 2nd section – Discipline 1 letter (see tables below). 3rd section – Sub-discipline 2-3 letters (only if necessary; see tables below). 4th section – Indicates the building acronym – to be determined at beginning of project. 5th section – Indicates the version of Revit. STRUCTURE (S) Structure STR Envelope ENV Furniture (if required) FUR Site SITE LIGHTING LG General (Legend, Details, Diagrams) GM Ventilation and regulation VR Ventilation VE Regulation RE Plumbing PL Fire Protection FP Heating and Cooling HC 8.3.2. Nomenclature of worksets Worksets should be named in a consistent and logical manner to provide adequate control over the efficiency of the model, allowing for members of design teams to collaborate with clear intent. Workset complexity will be subject to project type and will be at the direction of the Prime Consultant in coordination with disciplines. The principles set out below can be amended in agreement with all parties. The use of levels or zones may not be necessary based on the size of the project and will be agreed upon by all parties at the outset of the project.

Naming Conventions. [SOWG-231] The Contractor shall use filenames for all documentation deliverables in compliance with the following filename convention [NU|NR]_[Contract number]_[Name of document]_[v0.x|v1.0].[filename extension] and the fields used in the filename convention shall be used as follows:

Naming Conventions. For the purposes of this Clause 26 (Confidentiality), whichever of the Owner, Operator or the Lessee that is disclosing Confidential Information shall be referred to as the "Disclosing Party" and whichever of the Owner, Operator or the Lessee that is receiving Confidential Information shall be referred to as the "Receiving Party".