Naming Conventions. Files MUST: • Be named as identified in the XML (see section 7).
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.
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 Funding Source Setup (Non-Weatherization Programs) 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 eac...
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. Example of nomenclature: 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 ARCHITECTURE (A) Envelope ENV Furniture (if required) FUR Site SITE ELECTRICAL (E) LIGHTING LG MECHANICAL (M) General (Legend, Details, Diagrams) GM Ventilation and regulation VR Ventilation VE Regulation RE Plumbing PL Fire Protection FP Heating and Cooling HC
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. The SDPC Management Board, in conjunction with the NDPA Policy, Procedure and Usage Project Team, is charged with developing the standard naming convention for future drafts produced by the SDPC 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. Xxxxx agreed upon revisions of the draft (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. This section describes the naming conventions used in this chapter. The descriptions are based on the concepts of Process, Process-step, Attribute and Dataset. For facilitating the reading and the use of this Rulebook, structured identification-numbers are used as follows: Process-steps: CT-xx-yy, where xx-yy is the unique sequence number in this Rulebook Datasets: DS-xx, where xx represents the unique sequence number in this Rulebook Attributes: AT-xx, where xx represents the unique sequence number in this Rulebook
Naming Conventions. The Company uses a number of naming conventions. D.12.1 Convention for Input and Output Documents The Company Input and Output Documents are identified in accordance with the following convention: gggg-nnnn where: gggg Represents a code representing the Ad hoc Group, Working Group, Plenary Meeting, Executive Committee or Board. nnnn The unique number of the document. The identifier for a document is used both on the document itself and in the naming of digital files of the document. The file name is typically extended by a human readable string and an extension to indicate the file type (e.g. “Plenary-0000 Document Register.xls”). The Secretariat shall maintain a document register, itself numbered Plenary-0000, on the document exchange repository (see Section D.12.5).
