<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="https://www.designingbuildings.co.uk/skins/common/feed.css?301"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://www.designingbuildings.co.uk/w/index.php?feed=atom&amp;target=Hamish_Minaei&amp;title=Special%3AContributions%2FHamish_Minaei</id>
		<title>Designing Buildings - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://www.designingbuildings.co.uk/w/index.php?feed=atom&amp;target=Hamish_Minaei&amp;title=Special%3AContributions%2FHamish_Minaei"/>
		<link rel="alternate" type="text/html" href="https://www.designingbuildings.co.uk/wiki/Special:Contributions/Hamish_Minaei"/>
		<updated>2026-11-19T13:40:03Z</updated>
		<subtitle>From Designing Buildings</subtitle>
		<generator>MediaWiki 1.17.4</generator>

	<entry>
		<id>https://www.designingbuildings.co.uk/wiki/File_naming_conventions</id>
		<title>File naming conventions</title>
		<link rel="alternate" type="text/html" href="https://www.designingbuildings.co.uk/wiki/File_naming_conventions"/>
				<updated>2026-11-19T09:10:18Z</updated>
		
		<summary type="html">&lt;p&gt;Hamish Minaei: Created page with &amp;quot;== Introduction ==  A file naming convention is an agreed set of rules for naming project files, such as drawings, models, specifications and reports. A consistent convention mak...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
A file naming convention is an agreed set of rules for naming project files, such as drawings, models, specifications and reports. A consistent convention makes files easier to find, sort and identify, and reduces the risk of the wrong version being used or issued.&lt;br /&gt;
&lt;br /&gt;
== Common problems ==&lt;br /&gt;
&lt;br /&gt;
Where no convention is agreed, file names often record status informally, for example Plan_v2_FINAL_revised.dwg. This leads to:&lt;br /&gt;
&lt;br /&gt;
* uncertainty about which file is current&lt;br /&gt;
* duplicated and superseded copies circulating by email&lt;br /&gt;
* files that cannot be sorted or searched reliably&lt;br /&gt;
* information about status and revision being lost when a file is renamed&lt;br /&gt;
&lt;br /&gt;
== Structured naming ==&lt;br /&gt;
&lt;br /&gt;
In the UK, the National Annex to BS EN ISO 19650-2 sets out a structured naming convention made up of fields separated by hyphens. The fields identify the project, the originator, the volume or system, the level or location, the type of information, the role and a number. Status and revision are recorded as metadata against the file, rather than in the file name itself.&lt;br /&gt;
&lt;br /&gt;
Keeping status and revision out of the file name means the name stays the same throughout the life of a document, while its status (for example, shared for coordination or published for construction) and its revision change.&lt;br /&gt;
&lt;br /&gt;
== Good practice ==&lt;br /&gt;
&lt;br /&gt;
* Agree the convention at the start of a project and record it in the project information standard.&lt;br /&gt;
* Use fixed-length codes so that files sort correctly.&lt;br /&gt;
* Avoid words such as FINAL, LATEST or NEW in file names.&lt;br /&gt;
* Record changes in a revision history or version control system, with a short description of each change.&lt;br /&gt;
* Use a common data environment so that only one current version of each file is shared.&lt;br /&gt;
&lt;br /&gt;
== Related articles on Designing Buildings ==&lt;br /&gt;
&lt;br /&gt;
* [[BS_EN_ISO_19650|BS EN ISO 19650]]&lt;br /&gt;
* [[Common_data_environment_CDE|Common data environment CDE]]&lt;br /&gt;
* [[Drawing_register|Drawing register]]&lt;br /&gt;
* [[Version_control|Version control]]&lt;br /&gt;
&lt;br /&gt;
--[[User:Hamish Minaei|Hamish Minaei]] 09:10, 19 Nov 2026 (BST)&lt;br /&gt;
&lt;br /&gt;
[[Category:Standards_/_measurements]] [[Category:Design]] [[Category:BIM]]&lt;/div&gt;</summary>
		<author><name>Hamish Minaei</name></author>	</entry>

	<entry>
		<id>https://www.designingbuildings.co.uk/wiki/Browser-based_CAD</id>
		<title>Browser-based CAD</title>
		<link rel="alternate" type="text/html" href="https://www.designingbuildings.co.uk/wiki/Browser-based_CAD"/>
				<updated>2026-11-19T09:09:35Z</updated>
		
		<summary type="html">&lt;p&gt;Hamish Minaei: Replaced content with &amp;quot;== Introduction ==

--Hamish Minaei 09:09, 19 Nov 2026 (BST)

Category:Design Category:BIM

&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
--[[User:Hamish Minaei|Hamish Minaei]] 09:09, 19 Nov 2026 (BST)&lt;br /&gt;
&lt;br /&gt;
[[Category:Design]] [[Category:BIM]]&lt;/div&gt;</summary>
		<author><name>Hamish Minaei</name></author>	</entry>

	<entry>
		<id>https://www.designingbuildings.co.uk/wiki/Browser-based_CAD</id>
		<title>Browser-based CAD</title>
		<link rel="alternate" type="text/html" href="https://www.designingbuildings.co.uk/wiki/Browser-based_CAD"/>
				<updated>2026-11-19T09:08:51Z</updated>
		
		<summary type="html">&lt;p&gt;Hamish Minaei: Created page with &amp;quot;== Introduction ==  Browser-based CAD is computer aided design software that runs inside a web browser rather than as an application installed on a computer. Drawings are typical...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
Browser-based CAD is computer aided design software that runs inside a web browser rather than as an application installed on a computer. Drawings are typically stored on a server, and users open them through a web link.&lt;br /&gt;
&lt;br /&gt;
== Background ==&lt;br /&gt;
&lt;br /&gt;
CAD software has traditionally been installed locally and licensed per computer or per user, with drawings stored as files on local drives or network servers. Improvements in browser graphics have made it practical to run 2D drafting, and increasingly 3D modelling, inside a browser.&lt;br /&gt;
&lt;br /&gt;
== Characteristics ==&lt;br /&gt;
&lt;br /&gt;
* No installation: the software runs on any computer with a modern browser, regardless of operating system.&lt;br /&gt;
* Central storage: drawings are stored on a server, so there is a single current version rather than multiple copies.&lt;br /&gt;
* Sharing by link: drawings can be shared with view, comment or edit permissions.&lt;br /&gt;
* Version history: because changes are saved centrally, many tools record a full history of edits.&lt;br /&gt;
* Real-time collaboration: several users can work on the same drawing at once.&lt;br /&gt;
&lt;br /&gt;
== Limitations ==&lt;br /&gt;
&lt;br /&gt;
* Reliance on an internet connection, although some tools support offline working.&lt;br /&gt;
* Performance limits on very large drawings.&lt;br /&gt;
* Variable fidelity when importing and exporting DWG and DXF files.&lt;br /&gt;
* Fewer specialist commands and add-ons than mature desktop software.&lt;br /&gt;
* Data is held by a third party, which raises questions about hosting location, security, backup and export if a subscription ends.&lt;br /&gt;
&lt;br /&gt;
== Evaluating browser-based CAD ==&lt;br /&gt;
&lt;br /&gt;
Before adopting a browser-based tool for project work, practices commonly test it on a live project: importing existing drawings, carrying out typical drafting tasks, sharing with a client or contractor who has no CAD software, recording a revision, and exporting and plotting to scale. Licence terms should be checked, as some free tiers do not permit commercial use.&lt;br /&gt;
&lt;br /&gt;
== Related articles on Designing Buildings ==&lt;br /&gt;
&lt;br /&gt;
* [[Computer_aided_design_CAD|Computer aided design CAD]]&lt;br /&gt;
* [[Cloud_computing|Cloud computing]]&lt;br /&gt;
* [[Common_data_environment_CDE|Common data environment CDE]]&lt;br /&gt;
* [[Version_control|Version control]]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;signature&amp;amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Design]] [[Category:BIM]]&lt;/div&gt;</summary>
		<author><name>Hamish Minaei</name></author>	</entry>

	<entry>
		<id>https://www.designingbuildings.co.uk/wiki/Version_control</id>
		<title>Version control</title>
		<link rel="alternate" type="text/html" href="https://www.designingbuildings.co.uk/wiki/Version_control"/>
				<updated>2026-11-19T09:07:59Z</updated>
		
		<summary type="html">&lt;p&gt;Hamish Minaei: Created page with &amp;quot;== Introduction ==  Version control is the practice of recording changes to a document, drawing or model over time, so that any earlier state can be identified, compared and rest...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
Version control is the practice of recording changes to a document, drawing or model over time, so that any earlier state can be identified, compared and restored. In software development it has been standard practice for decades. In construction and engineering design it applies to drawings, models, specifications and schedules, where several people may edit the same information over the life of a project.&lt;br /&gt;
&lt;br /&gt;
== Why version control matters for drawings ==&lt;br /&gt;
&lt;br /&gt;
Without a formal system, versions are often tracked through file names, such as SitePlan_v3_FINAL.dwg. This approach has several weaknesses:&lt;br /&gt;
&lt;br /&gt;
* It is not clear which file is current.&lt;br /&gt;
* Two people can edit separate copies and overwrite each other's work.&lt;br /&gt;
* The reason for a change is not recorded.&lt;br /&gt;
* Superseded copies can be issued by mistake.&lt;br /&gt;
&lt;br /&gt;
A version control system replaces file-name tracking with a single record for each drawing and a history of changes, each with an author, a date and a short description.&lt;br /&gt;
&lt;br /&gt;
== Key concepts ==&lt;br /&gt;
&lt;br /&gt;
* History: an ordered record of every saved change. Any earlier state can be viewed or restored.&lt;br /&gt;
* Change description: a short note explaining what was changed and why, for example &amp;amp;quot;Stair core moved 600 mm north following structural comments&amp;amp;quot;.&lt;br /&gt;
* Comparison: a view showing the differences between two versions. For drawings this is usually visual, with added and removed geometry shown in different colours.&lt;br /&gt;
* Branching: creating a separate line of work from a known version, for example to develop a design option, without changing the main drawing.&lt;br /&gt;
* Merging: bringing the changes from a branch back into the main drawing once an option is approved.&lt;br /&gt;
* Conflict: a situation where two branches change the same element in different ways, requiring a person to decide which change to keep.&lt;br /&gt;
&lt;br /&gt;
== Version control and information management ==&lt;br /&gt;
&lt;br /&gt;
Version control works alongside formal information management processes. Under BS EN ISO 19650, information containers in a common data environment carry status and revision codes, and only approved information is shared or published. Version control tools record the detailed history behind each revision.&lt;br /&gt;
&lt;br /&gt;
Branching is common in software and is beginning to appear in CAD tools. A study of 719 posts on online CAD forums found that designers wanted to use branching to explore design alternatives, although tool support was still limited (Cheng et al., 2023).&lt;br /&gt;
&lt;br /&gt;
== Related articles on Designing Buildings ==&lt;br /&gt;
&lt;br /&gt;
* [[Common_data_environment_CDE|Common data environment CDE]]&lt;br /&gt;
* [[Computer_aided_design_CAD|Computer aided design CAD]]&lt;br /&gt;
* [[Design_review|Design review]]&lt;br /&gt;
* [[File_naming_conventions|File naming conventions]]&lt;br /&gt;
* [[Browser-based_CAD|Browser-based CAD]]&lt;br /&gt;
&lt;br /&gt;
== External references ==&lt;br /&gt;
&lt;br /&gt;
* [https://arxiv.org/pdf/2307.02583.pdf Cheng, K., Cuvin, P., Olechowski, A. and Zhou, S. (2023). User Perspectives on Branching in Computer-Aided Design.]&lt;br /&gt;
&lt;br /&gt;
--[[User:Hamish Minaei|Hamish Minaei]] 09:07, 19 Nov 2026 (BST)&lt;br /&gt;
&lt;br /&gt;
[[Category:Design]] [[Category:BIM]]&lt;/div&gt;</summary>
		<author><name>Hamish Minaei</name></author>	</entry>

	</feed>