Bundle of my ExcelCalcs UpLoads

{The link to download the bundle is at the bottom of the post.}

Whilst my preference is that my spreadsheets are downloaded via ExcelCalcs and that queries are placed in the ExcelCalcs forum, it is apparent that people request the spreadsheets without need to join ExcelCalcs. Most of my spreadsheets are dependent on links to other workbooks, some .xls and others .xla, in consequence the download limits on ExcelCalcs may prevent new users from obtaining a fully working set of my workbooks. None of my spreadsheets are dependent on XLC , whilst I believe it is good software, I have moved beyond the need to format my calculations in standard text book format. For my comparison of MathCAD/SMath type applications versus spreadsheets read:
Electronic Calculations (eCalc's) .
My primary concern is calculating results and making decisions, not documenting the journey taken, as a consequence I make extensive use of visual basic for applications (vba), with MS Excel primarily being used to provide: a file format, editor, and reporting capability.

The spreadsheets are primarily concerned with structural design of manufactured structural products (MSP). Such products mainly comprise of steel, cold-formed steel, and timber sheds and canopies. The spreadsheets are modifications of the production spreadsheets we have used for design for many years at MiScion Pty Ltd (also Trading as Roy Harrison and Associates).

The spreadsheets we use in-house are for more complete buildings, involving member and connection design (eg. schShedDesignerR01.xls is a cut down version). The idea of releasing the spreadsheets was to provide the building blocks for others to build custom workbooks for other more specific building forms. If people want custom workbooks or vb.net/vba applications for their structural product then I can be contacted at MiScion Pty Ltd.

Structural design of a product can be divided between the following three major activities:

1. Brief Description: Design Brief
2. Evidence-of-Suitability
3. Detail Description:Specification

Provision of Structural Calculations primarily falls into the evidence-of-suitability activity. Whilst drawing falls into both the design brief and specification activities.

Structural design can also be considered divided into the following:

1. Product Structure/Description
2. Dimension & Geometry
3. Design Actions
4. Design Action-Effects
5. System/Component Stability/Resistance
• Design/Assessment of Structural Form
• Design/Assessment of Members
• Design/Assessment of Connections
• Design/Assessment of Interface/Supports (Footings)

The spreadsheets are listed below roughly divide into the above categories. For further information links to ExcelCalcs and Blog posts are provided. At present most of the blog posts simple display the ExcelCalcs page, but in the future I will add more detail about the workbooks. Also note that the graphics on the ExcelCalcs page were put there by the site administrator not myself, and don't always reflect the nature of the spreadsheet: and editing the page is limited, therefore the blog posts here will be up dated and modified first.

(c)Copyright 2015 Steven Conrad Harrison
The Bundled Package Comprises of the following Files:
FILENAME	DESCRIPTION	Blog	ExcelCalcs
gpl.txt
readme.txt
Chart9BTC3 y04m06d14.pdf	ColdFormed Steel Sheds Australia Height Span Limits of C-Sections.	blog	ExcelCalcs
TECHNICAL LIBRARY
schTechLIB.xla	Libary of functions. schTechLIB contents	blog	ExcelCalcs
schTechLIBV2.xla	Library without DAO references
ENVIRONMENT
Beaufort.xls	Beaufort wind Scale	blog	ExcelCalcs
as4055.xls	AS4055 Simplified wind loading for products	blog	ExcelCalcs
as4055v1.xls	AS4055v2 Simplified wind loading for products	blog	ExcelCalcs
schWindAssessment_r02.xls	Wind Loading to AS1170.2	blog	ExcelCalcs
DIMENSION & GEOMETRY
drawWorkSheet2009.xls	Experiments with Parametric Sketches using XY Charts.	blog	ExcelCalcs
schAcadLTCivilScriptWriter.xls	Civil engineering Long Profiles and Sections.	blog	ExcelCalcs
schBuildingDimensions.xls	Dimension and Geometry of Gable Frame shed Frame Member Lengths and Bracing Lengths.	blog	ExcelCalcs
schDrawSection.xls	Draw Sections.	blog	ExcelCalcs
schCADDv2.xls	CADD.	blog	ExcelCalcs
drawShed.zip	CAD: Automatic generation of framing plans and elevations simple gable frame.	blog	ExcelCalcs
sample.dwg
schDrawShed.xls
vbaDXF.zip	VBA Experiments Parsing ACAD DXF files.	blog	ExcelCalcs
DXFtoolsV01.xls
vbaDXF1.xls
vbaDXF2.xls
vbaDXF3.xls
drawShedDC1.zip	CAD: Experiments with DesignCAD: Draw 3D framing of American Barn type structure.	blog	ExcelCalcs
Column1.dcd
schDrawShedDC1.xls
ExcelShapes.zip	VBA Experiments with Excel Shapes Layer: Structural Framing Plans.	blog	ExcelCalcs
struMtrl.mdb
shapesTut01B.xls
drawTut.zip	VBA Experiments with ACAD Script Automation.	blog	ExcelCalcs
drawTut01.xls
drawTut02.xls
drawTut03.xls
drawTut04.xls
drawTut05.xls
SampleSCR1.xls
UnSymmetricalGableSCR.xls
vbaDraw01punch.xls
vbaDraw02.xls
vbaDraw03.xls
vbaDraw04.xls
schHolePunching.xls	Estimating: Hole punching requirements for roll-formed sections.
PRODUCT STRUCTURE TREE
bomStructureTreeStage3.xls	exploded BOM (Bill of Materials).	blog	ExcelCalcs
schBOMStructureTreeStage1.xls	Indented Bill of Material.	blog	ExcelCalcs
explodedBOM.zip	IE/POM/CAPM Automatic Explosion of Bill of Materials.	blog	ExcelCalcs
Assemblies.xls
Materials.xls
mrpBOMv2.xls
ASSEMBLY ANALYSIS/DESIGN
schGableCanopyTimber.xls	Gable Canopy to Australian Codes.	blog	ExcelCalcs
schKleinlogel03.xls	Kleinlogel.	blog	ExcelCalcs
schShedDesignerR01.xls	Wind Loads on Gable Frame to Australian Wind Code AS1170.2.	blog	ExcelCalcs
schDesignEngineR01.zip	Application for Generation of Height Span Charts Gable Frame Sheds.	blog	ExcelCalcs
AcadScript.xls
BeamCalc.xls
Building00.xls
DBGtrace.xls
DataCosmos.xlt
DesignEngine.xls
GUI_lib.xls
Geom3D.xls
HeightSpanTableForm.xlt
Klein3.xlt
Primer.xls
RigidFrame.xls
Structure.xls
XStrings.xls
Xmaths.xls
as1170.xls
as4600.xls
struMtrl.mdb
MATERIALS
schStruMtrl.xls	Structural Materials Data Steel.	blog	ExcelCalcs
schTimberMatrl.xls	Timber Data for AS1720.	blog	ExcelCalcs
struMtrl.mdb	MS Access database of properties. origin of schStruMtrl.xls.
MEMBER DESIGN
schDsgn1720.xls	Calculator assessment of timber structures to AS1720.	blog	ExcelCalcs
schColdformedCee.xls	Example Using Circular References to Force Iteration: Calculation Effective Section Modulus for Coldformed C-Section to AS4600.	blog	ExcelCalcs
schDsgn4600.xls schDsgn4600R2013.xls	Calculator for assessment of cold-formed steel structures to AS4600. Further information on set up can be found here.	blog	ExcelCalcs
schDsgn4100.xls	Calculator for assessment of steel structures to AS4100.	blog	ExcelCalcs
CONNECTIONS DESIGN
schTechNote022pt2.xls	Tables for strength of bolted joints in thin cold-formed steel sheets to AS4600.	blog	ExcelCalcs
PRODUCTION AND OPERATION MANAGEMENT
schPlannerCalendar.xls	Planner Calendar.	blog	ExcelCalcs
schWorkStudy.xls	IE: Work study flow process chart.	blog	ExcelCalcs
GEOGRAPHICAL INFORMATION SYSTEMS
centralPlaces4.zip	Experiments with Geographical Information System (GIS) central places.	blog	ExcelCalcs
CentralPlaces4ShedSuppliers.xls
MISCELLANEOUS
vbaObjects.zip	VBA Experiments with Class Objects.	blog	ExcelCalcs
objTut01.xls
objTut02.xls
objTut03.xls
dataStruct.zip	VBA Experiments with Abstract Data Structures.	blog	ExcelCalcs
dataStruct00.xls
dataStruct01.xls
dataStruct02.xls
dataStruct03.xls
dataStruct04.xls
dataStruct05.xls
orgDataStru.xls
treeExperiments.xls
vbaTuts.zip	Excel/VBA Tutorials.	blog	ExcelCalcs
Node.dwg
NodeA.dwg
MyTest.txt
MyTest2.txt
TestNodes2.txt
vbaTut33.TXT
vbaTut00index.xls
vbaTut01.xls
vbaTut02.xls
vbaTut03.xls
vbaTut04.xls
vbaTut05.xls
vbaTut06.xls
vbaTut07.xls
vbaTut08.xls
vbaTut09.xls
vbaTut10.xls
vbaTut11.xls
vbaTut12.xls
vbaTut13.xls
vbaTut14.xls
vbaTut15.xls
vbaTut16.xls
vbaTut17.xls
vbaTut18.xls
vbaTut19.xls
vbaTut20.xls
vbaTut21.xls
vbaTut22.xls
vbaTut23.xls
vbaTut24.xls
vbaTut25.xls
vbaTut26.xls
vbaTut27.xls
vbaTut28.xls
vbaTut29.xls
vbaTut30.xls
vbaTut31.xls
vbaTut32.xls
vbaTut33.xls
vbaTut34.xls
vbaTut35.xls
vbaTut36.xls
vbaTut37.xls
vbaTut38.xls
vbaTut39.xls
vbaTut40.xls
vbaTut41.xls
vbaTut42.xls
vbaTut43.xls
vbaTut44.xls
vbaTut45.xls
vbaTut46.xls
vbaTut47.xls

The zip package can be downloaded free off charge from MiScion Pty Ltd: spreadsheet Bundle . MS Excel should automatically update the workbook links to the current folder. If create a subfolder of "My Documents" called eCalcs and below this create a folder called materials. The materials data files should be placed in this folder. The materials files are:

• struMtrl.mdb
• schStruMtrl.xls
• schTimberMatrl.xls

---

Revisions:

1. [26/5/2015] : Original Bundle Release
2. [11/6/2015] : Updated the zip file to include revised versions of workbooks which had previously been uploaded to ExcelCalcs. These mainly comprise of changes to the AS4600 and AS4100 workbooks, which now have a button to open the section library, and  also worksheet application parameters to enable the DAO functions to find the MS Access database of sections properties (this currently only required for AS4600.). For more information refer to : My spreadsheets DAO and 64 bit Windows 7. For those not using AS4600 there is also a alternate version of schTechLIB which does not have the references to Microsoft DAO 3.6 object library, this is named schTechLIBV2.
3. [01/02/2016] : Changed source of zip file from dropbox to MiScion Pty Ltd (the family business)

Automated Drawing List Update Acad LT (revised)

As indicated in earlier posts I use Acad LT, and automate using Excel/vba to generate AutoCAD script (.scr) file.

One of the most regularly used scripts is that for updating the drawing title blocks. This operates across multiple paperspace layouts and multiple files.

Whilst paperspace layouts can be beneficial they do have some disadvantages when it comes to repetitive detail across projects, consequently I have been tending to move back towards individual file for each drawing sheet, and lots of xref's, especially for workshop details. For example it is a lot easier to copy a file, and modify the detail, than messing around copying detail modifying and setting up new paperspace viewports. Other times it may be easier to copy layouts, and add some extra layers for some additional detail. Hence need to update drawing title blocks across multiple layouts and drawing files.

Last year I made a simple modifications, by writing the script file to a common default folder, and automatically launching Acad LT, compared to previously generating script in drawing folder and then dropping in Acad LT editor. At that time also added extra worksheets to allow different title blocks, to cover common variations: such as calc's sheets used for simple sketches, versus drawing sheet used for residential footings, and the typical drawing sheet for all other project types. To do that I also added look up tables which listed the attributes for each title block. Providing drop down lists to select which of drawings the title block script should be generated for. That was all working good, and saved a little bit of extra time over the previous version of the script.

But work shop detailing involves a lot of drawings and tend to get slightly lost in all the drawings. Also the batch of drawings did use two title blocks: proper drawing sheet and frame for the main part details and then a simple document control block for some steel sheet setouts. The current project however introduced the need for a larger sheet. Most part details are standard and on A4 sheets, but the larger building currently working on as parts which are too large to conveniently fit on A4, I can squeeze them onto A4, but have chosen to place on A3 instead.

So for the batch of drawings have three different title blocks which want to automatically update, and a problem working through all the files and details, to determine which exist and which are relevant.

So modified the Excel/vba script. It now permits each drawing to have a unique title block, on condition that it has attributes which belong to a common sets. The vba macro now checks if the attributes are in the title block, if so then writes the value from Excel to the Acad script (.scr), if not then skips to next attribute. Also the macro now checks if the drawing file exists before including in the script, if not then the cell is coloured red.

At one stage I also experimented with Hyperlinks to open the Acad drawing files from Excel worksheet, this didn't work to well because of need to keep paths updated. But now created a vba macro and short cut key (Ctrl-e), to open drawing file currently selected in the worksheet. This didn't work too well using the vba shell command as it opened each drawing in a separate instance of Acad LT. However a simple experiment with vbs, and determined that the windows scripting host (WSH), shell object run command was able to open files by association, whilst the vba shell command required the executable command. That is using vba I needed to build correct command line including reference to Acad LT as well as file name, whilst using WSH shell command only need to pass the drawing file reference. Therefore created a WScript.Shell object in Excel/vba.

So I can now get from Excel description of drawing file, to the actual Acad LT drawing. Now that is something I wanted to do for a while.

For now have potential to mesh my bill of materials (BoM), or product structure tree to workshop details, and otherwise build model in Excel. For can otherwise get lost figuring out which part files belongs to which part, and have I drawn all the necessary parts and counted them all. Sure I could buy building information model (BIM) software, but where's the fun in that. Plus BIM software is expensive and I don't have the demand for workshop detailing to justify its purchase. Programming, well that's just kind of play time.

I had experimented with XYplorer, attaching tags to part drawings, but problem with that, I need two sets of tags: one for local work on laptop, and another for files on shared drive in office. Additionally adding tags to files, produces an ever increasing database of tags which have to be scanned through. By using Excel tables, I am not adding to over head of using XYplorer, and I can add data fields as I choose on an as needs basis, sort and filter and otherwise connect to other data sources.

On BIM
One other objection I have to BIM, is that it is an enforced approach to building design, and that approach is built around 3D graphics, whilst the majority of people in the supply chain have no use of 3D graphics. Revisiting the concept of data as raw material, and information as data organised to assist decision and action, then the typical BIM software application, is a long way from being an information model. It is largely a data model BDM, and less than informative to other parties who don't want the graphics but do want to get at the data and present in formats which suit them, rather than formats that suit the authors and or users of  3D graphic software.

Consider that it is inappropriate to use a multi-million dollar flexible machining centre to make bolts and other high volume repetitive parts. It is preferable to have highly specialised machines to make bolts. The current BIM software tends towards being highly flexible, that makes it ill suited to more specialised purposes.

It is a common trend in software development that more and more features and flexibility are added, the problem is that something which previously took a few clicks now requires a multitude of irrelevant parameters to be set.

For example the modification I have just made to my spreadsheet, now requires I define the title block for each and every drawing, where as previously I only needed to identify the title block once. However, it is not a major problem because it is simple to copy cells in Excel, or to make one cell equal to another. It is that reason why I type project titles and drawing titles into Excel rather than directly into Acad.

By making software too flexible it then becomes necessary to expend time customising the software for something more specific and repetitive. The problem of creating a front end, to simplify input, is that there is a lot of over head associated with the flexibility. So whilst using an advanced flexible system may reduce development time, it does not produce a tool which is efficient. The resultant product uses more resources than necessary and operates slower than required.

Hence there is a need for custom tools. So comments like if not using the newest tools then behind the times, are largely nonsense. Should not be using the newest tools, but the tools most appropriate to the job at hand. A lot of modern software is becoming more video game than productive tool, whilst it may ease people getting familiar with the software and using, its not all that productive there after.

So some of these high end software vendors really need to pay more attention to the needs of the end-users rather than how they consider design and documentation should be carried out. There are still people producing workshop details freehand, and buildings plans freehand, that is people who are not using any form of drawing instruments and not drawing to scale: they produce simple concept sketches and that is all they need to get approval and to build. Drawing is a tool to solve problems, and many of those problems only need resolving by freehand concept sketches. So builders for example are not going to start using CAD, because drawing is not their business, they produce drawings as an aid, a means to an end. Whilst many modern architects, engineers and drafters are producing drawings as an end in itself: more concerned with document control than what is conveyed by the documents.

End-users buying BIM software also need to pay more attention to where they need productivity improvements. If 3D graphics contributes little value to an end-users activities then current array of BIM products probably of little value. That is do you really need a picture of an object to input all the other data and extract useful information about that object. If not then BIM is not a suitable solution, and other software likely to be more useful. For example MS Excel/ MS Access, or the array of MRP I, MRP II, software and various other specialist packages.

I go from Excel to Acad, because with Acad scripts (.scr) I can only really generate Acad drawings, there is little that I can do to extract Acad data other than extract block attributes, or export a DXF file, and extract data from that.

The first data for most things is symbolic, some kind of analogy, this then has to be expanded into graphics and other data. For example want a building or a machine. These are word symbols and not very specific, the definition thus has to be  refined until define something specific. This refinement can take place using more words, various kinds of charts and diagrams, or using pictorial graphics. Much can be done long before any graphics are produced, but seems in the modern world consultants dive straight into CAD drawings, when should have dismissed an idea almost immediately using simple freehand sketches.

A crazy world in which it seems only typed reports and CAD drawings seem to be accepted. Very wasteful.

Related Posts:

AutoCAD Speed Test
Automated Drawing List Update Acad LT (revised)

Cold-Formed Steel Shed Industry: part:#1 (Shed Framing Drawings)
Cold-Formed Steel Shed Industry: part:#2 (Shed Framing Drawings)

Cold-Formed Steel Shed Industry: part:#2

As explained previously an Excel/vba macro is used to generate an AutoCAD script which is written to a default folder, and then AcadLT is launched from vba using command line parameters to run the Acad script automatically as Acad loads. The model space output of the script is shown in Fig 1, and the paper space output shown in Figs 2 to 6.

Fig 1: Model Space output of script.

Fig 2: Paper Space output of script. Footing plan showing stiffened raft (not typically required).

Fig 3: Framing Plan & Member Schedule

Fig 4: Side (Front) and End Elevation (Right)

Fig 5: Side (back) and End Elevation (Left)

Fig 6: Detail Section of Portal Frame

At present the script doesn't modify the paper space layouts to match the paper size. This is largely because in the first instance it requires using "print" and adjusting the layout parameters and then cancelling the print command. It can crash if invalid paper size names and printer names are provided, so it was left out. Text is all placed in paper space, with exception of the grid labels which are written in model space. The input parameters allow varying the paper size, the scale, and forcing either one view per sheet or everything to a single sheet. The scale can also be selected to be calculated. Either way the vba macro will determine one of a few different preferred layouts, and attempt to use as few sheets as possible. All the parameters to define the structural frame can be varied. Spacing of frames, girts and purlins are assumed to be constant. Except for the simplest of buildings, usually after the script has run a great deal of manual editing is required to produce finished drawings for development approval.

Fig 7: Screen Capture of Time Script Takes.

As can be seen from the screen capture, Fig 7, the script takes less than 9 seconds to run, this is significant decrease on the 5 to 20 hours that may be required for drawing such stick diagrams from scratch. Another 5 to 40 hours may be required for drawing connection details and other relevant detail sections. Given that the shed industry typically does not produce formal drawings, only a freehand sketch on square ruled paper order form, taking some 10 to 60 minutes whilst salesperson talks to customer: collapsing the drafting time is important. Whilst the freehand sketch is suitable for a small garden shed, its not suitable for a 4000 sq.m industrial warehouse with office space. But people go to the shed suppliers on the assumption that they have solved all the problems before and have standard designs which can be modified. Whilst the industry advertises custom manufacture it cannot provide custom design. The industry relies heavily on the local council, requesting further information, before they go and get architectural and engineering input. This results in delays for the customer as issues of  non-compliance with building codes are resolved.

Whilst high end building information modelling (BIM) software may be useful for the task, it is too complex for sales people to be using at the point-of-sale, and with costs from $5000 to $25,000 (AUD) per license it is also far too expensive. {Though any shed supplier setting up own engineering staff and making  use of such software, has the potential to make it financially viable, taking advantage of the software to improve their product and increase sales.}

Whilst the suppliers run around from one consultant to another, requesting standard designs for one shed or a range of sheds, there is a need to develop low cost, highly product specific software which produces drawings, and structural calculation reports, along with material take-off's,  cost estimates, and work shop details, along with any CNC machine instructions if appropriate, to resolve the problems of not using standard designs correctly.

There is already precedent for such software with the nail plated timber roof truss manufacturers, however their software started in the wrong direction: it failed to provide adequate evidence-of-suitability and was proprietary. This made it difficult for council to check the adequacy of the proposed trusses, and there is still need for improvement, but there is now a guide line for such software, put out by Planning SA.

Minister’s Specification: SA A2.2 : Structural engineering software

The problem with such software is that it tends to only produce specifications, and it can do so in a short period of time, a few minutes. Compare this to a few hours to check all the different roof trusses in a typical house, using either manual methods or standard frame analysis software. It seems no consultants providing technical certification services has automated their standard frame analysis software for checking timber roof trusses. Similarly they also haven't produced automation for sheds, carports and verandahs. So the industry can do fast, but the checkers and certifiers are slow. The big question though is the industry fast because its not doing engineering checks, or because it has fast design tools, and have those design tools been checked and are they being used correctly. Hence developing and releasing the software not just a matter of writing source code. Hence these things tend to get part developed as useful in-house productivity tools rather than commercial products. But not everyone has the time to develop such tools in-house, and that causes hindrance, and delays, when at the certifier level. So tools need to be readily available to all, not just limited to manufacturers, possibly under a GPL, so that source code viewable by all.

Any case primary task at moment is to reduce the drafting effort, since calculation effort has largely been reduced already for the typical gable frame shed.

---

Related Posts:

Cold-Formed Steel Shed Industry: part:#1

Cold-Formed Steel Shed Industry: part:#2

Cold-Formed Steel Shed Industry: part:#3

PEB, PEMB, PMBS Cold-Formed Steel Sheds and Canopies #pt2

Height Versus Span Design charts for Steel Sheds

The Section Weights ...

Weight of Steel does Matter?

Kleinlogel Rigid Frame Formulas

Manufactured Structural Products And Simplified Wind Classification

Other Blogs:

Shed Design: pt#1 (Basic Procedure

AutoCAD Speed Test

As a simple test of the comparison between speed of manual CAD drafting and scripting (*.scr), a simple test can be carried out. This test comprises of drawing a rectangle and then diagonal lines and bisectors of the sides. All entities should be ordinary lines, no polylines or rectangles, and no drawing as such and exploding to ordinary lines. Running osnaps can be switched on to save time. I typically have osnaps switched off, it interferes with running scripts, and otherwise tends to waste time in manual drafting selecting the wrong points, so I typically select snaps manually, the right one at the right time. Anycase for the test I used running osnaps, because it is a situation where it clearly provides benefit rather than an hindrance. The dimensions of the rectangle are @10000,5000.

It should be noted that the larger the screen the longer the distance to travel from one corner to the other and therefore the longer the drawing time. So larger screens not altogether a benefit. Faster times can be achieved by reducing the size of the AutoCAD window, or by zooming to a fraction of the screen (eg. zoom 0.5x).

Fig 1: Screen image of finished drawing test.

{NB: click image to enlarge and scroll all images.}

Fig 2: Screen capture of time taken for manual drafting

The time taken with manual drafting is approx 26 seconds. With practice it may be possible to get the time down further. Starting out today it took 55 seconds, but for some reason I was typing the command "Line" rather than using the alias "L", also wasn't using running osnaps. But since I knew last time I did the test I did it in 26 seconds, I kept trying until could capture such time from screen. Faster  computers and faster operators may be able to get lower times, but unlikely to achieve the less than 1 second that the script takes to run.

Fig 3: Screen capture time taken by script, drag and drop onto CAD drawing.

Fig 4: Screen capture time taken when macro added to a toolbar button.

Not sure why but the script runs slower when called from a toolbar button than when script file is "drag and dropped" onto the drawing. However the button saves operator  time finding the script.

The script:

;---------------------------------

TIME RESET

LINE 0,0
0,5000
10000,5000
10000,0
C
LINE 0,0 10000,5000

LINE 0,5000 10000,0

LINE 5000,0 5000,5000

LINE 0,2500 10000,2500

ZOOM E
ZOOM s 0.5x
TIME

;---------------------------------

The button macro:

'_script speedTest1.scr 


Faster computers and larger monitors save time, but only when there is a great deal of interaction between the operator and the machine. To really save time and increase productivity need to get the computer to do the work, and a slow computer may be adequate for such purpose. If it takes a person 2 minutes to enter data, and the computer 1 second to respond, it does not make any perceptible difference if get a computer twice as fast to complete its task in 0.5 seconds. Its the 2 minutes of human interaction with the machine that needs to be reduced: and that is likely to become a political issue. There has to be some acceptable need to reduce the production time before effort gets applied to do so. After all what are you going to do with the free time if just reduce production time just because you can.

Related Posts:

Programming/Automating #Autocad LT
Automated Drawing List Update Acad LT (revised)

Cold-Formed Steel Shed Industry: part:#1 (Shed Framing Drawings)
Cold-Formed Steel Shed Industry: part:#2 (Shed Framing Drawings)

Cold-Formed Steel Shed Industry: part:#1

Sample drawings of framing plans for cold-formed steel shed, partially automated by the scripts(*.scr) mentioned in earlier blog, then extensively modified using manual CAD editing, using AcadLT 2000, to match the custom features of the project. Project is from a few years back, and drawing title blocks have been removed so as not to identify the project, client and supplier. The drawings have additional detail on them compared to that required for development approval, so as to assist with workshop detailing. The cold-formed shed industry typically does not produce drawings beyond scribble on the back of an order form: not for development approval and not for fabrication. The industry typically has salespeople and possibly estimators sketching out what they believe is required. The whole benefit of the cold-formed steel shed industry is that need little infrastructure, and simply need to fill in some purlin detail sheets and send of to local roll former of c-sections, and have a bundle of fabricated steel delivered straight to site depending on connection details. This typically fine for the smaller sheds but for larger warehouses with office space it is inappropriate.

In the past we typically worked with the suppliers and manufacturers and couldn't get them to change, very little interest in their product. Then  one day a steel erector turned up, he was unhappy about various issues with construction, and wanted to refine the design. Also turned out that supplier/manufacturers often failed to deliver all required parts for construction, and unable to get these parts from the suppliers on basis they contended that the parts not required. We recommended that the steel erector insist on workshop drawings being produced. The shed suppliers wouldn't provide, and workshop detailers not able to fit in with the nature of the shed industry. The result was the workshop detailing returned to my office, along with designing the sheds on a project by project basis, rather than the typical industry approach of having standard calculations and relying on local council to request further information to get calculations which match the proposed shed.

As long as the shed stays as a simple plain frame, then can analyse it using Kleinlogel formula in MS Excel, and the calculations are dropped to a few minutes. The time consuming effort is producing the framing plans for development approval, and the workshop details. Connection details are basically the same from one project to the next, and standard drawings simply need project name changing, though each new project may introduced additional detailing.

Now software like Autodesk Revit structural, or Tekla Structure, and other BIM  software, may be the ideal tool for such project: however they are far to expensive to justify given the amount of work involved and the relative simplicity of the structures. Also in terms of developing tools to improve point-of-sale decision making in the industry, tools like AutoCAD are too expensive to use as a graphics engine, whilst Multiframe is too expensive to use as an analysis engine. So MS Excel/VBA is typically the product to choose with possibly some low end CAD package, alternatively use the Excel shapes layer, and draw in Excel itself.

So slowly developing in-house tools to handle custom projects, whilst also developing tools which ultimately can be used by sales people at the point-of-sale. The objective is to reduce the problems caused, by bad design decisions at the point-of-sale. In particular the buildings that the industry can supply simply do not meet the needs of the buyers. But this is not identified until council rejects the suppliers development proposal, and requests further information, then everyone turns to consulting engineers to get calcs-for-council, as if that was all that was needed.

So the objective is to develop low cost automation tools based on simple parameters, which flags the need for custom engineering at the point-of-sale. Currently these buildings basically  sold like cars, except can ask for three of the wheels to be removed to cut costs and the sales person will say yes we can do that.

The real issue is developing a simply interface, at no point do want the sales-people operating a CAD package, but need to know the custom requirements for doors along the length of the building, and also know the different gable-end framing requirements. Also need to expand beyond the simple gable, to allow for double span, and the American barn type structure (gable, with lean-to each side).

So currently have a collection of different tools written in Excel/VBA, also some of which I originally wrote in Turbo C and others in Delphi. A part of development problem is deciding on application language, a great deal has now been written in Excel/VBA, but MS Access maybe better, and VB.net better again with respect to data storage and suitable user interface. In particular I can program a treeview in VB.net for my bill of materials (BOM) but not in VBA. On the otherhand I don't really like Basic programming language, its just that VBA is built into so many applications: and controlling anything and everything from Excel/VBA has been so convenient. For speed developing the Excel/VBA, and AutoCAD LT approach, with Microstran and Multiframe data file generation, seems to be the way to go, then slowly remove dependencies on other applications, and make stand alone. Part of which requires developing a 3D frame analysis program, already have 2D, but ultimately going to need it to be 3D.

Anycase currently finding all the bits and pieces cumbersome to use. So given that the purpose of this blog is to document the background as to how things develop, I thought I would document the current process, whilst I figure out in which direction to go and what to program next.

Fig:S01: Footing Layout

Fig:S02: Framing Plan

Fig:S03: Elevations:1

Fig:S04: Elevations:2

Fig:S05: Sections/ Portal Frames

Fig:S06: Gable End Wall Detail Section: Office End

Fig:S07: Gable End Wall Detail Section: Rear

Foot Note: Sample drawings printed to pdf file using pdfactory, then borders and title blocks removed, by taking snap shops using Bluebeam, and saving to jpeg using MS Paint, then file size reduced using Microsoft Office Picture Manager.

---

Related Posts:

Cold-Formed Steel Shed Industry: part:#2 : Dimension & Geometry (Acad LT)

Cold-Formed Steel Shed Industry: part:#3 : Summary of other requirements

Feasibility of Cold-formed Steel Shed (Simple Structural Software Application)

PEB, PEMB, PMBS Cold-Formed Steel Sheds and Canopies #pt2

Height Versus Span Design charts for Steel Sheds

The Section Weights ...

Weight of Steel does Matter?

Kleinlogel Rigid Frame Formulas

Manufactured Structural Products And Simplified Wind Classification

Other Blogs:

Shed Design: pt#1 (Basic Procedure)

Other Information:

Generic Connection Details for Cold-formed Steel Sheds and Canopies