Showing posts with label spreadsheets. Show all posts
Showing posts with label spreadsheets. Show all posts

Friday, July 24, 2015

Metamorphs Product Ideas

Various Product Ideas had over the years. So yet another check list for determining what I have actually pursued and otherwise released.


ProjectID Title
M001 Shed Design Charts
M002 Shed Design Manual
M003 PreFabricated Buildings Manual
M004 Kleinlogel Spreadsheets & Applications
M005 Utility Disk
M006 Easy Calculators
M007 Generic Details
M008 Component Design Tables
M009 Soil Heave & Geotechnical
M010 Online Engineering Services
M011 Stock Management
M012 Project Manager
M013 Conveyor Design - Mechanical Handling
M014 Pipe Profiler
M015 Wind Loading Calculators
M016 Beam Analysis & Design
M017 Carport Design: Prescriptive Solutions
M018 Plane Frame Analysis & Design
M019 Drawing Office & Document Manager
M020 Personnel Manager
M021 Program Writer
M022 Metamorph Calculator
M023 Program Converter
M024 File Manager
M025 Cosmos - engineering data management engine
M026 CADD Tools
M027 IE Toolbox
M028 Standard Forms
M029 Architectural Details & Floor Plans
M030 Multiframe Applications
M031 Library Manager
M032 Civil Engineering Scriptwriter for AutoCAD LT
M033 Preprocessor/Postprocessor for Lights
M034 Microstran Preprocessor/Postprocessor
M035 Canopy Design: Software for Custom Design
M036 Excel Application Model
M037 Experimental Frame Design (Shelter)
M038 ColdFormed Steel Design
M039 HotRolled Steel Design
M040 Timber Design
M041 Concrete Design
M042 Masonry Design
M043 Civil Engineering Toolbox
M044 Structural Engineering Toolbox
M045 Mechanical Engineering Toolbox
M046 Enterprise Ideas

Tuesday, May 26, 2015

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.mdbMS 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)

Monday, April 14, 2014

My spreadsheets DAO and 64 bit Windows 7

In process of reluctantly moving over to Windows 7, found a problem with my spreadsheets. Didn't want to change operating systems, but faulty power adapter connection forced me to get a new computer, that was about 18 months ago. Thus far the 64 bit Windows 7 computer been a good dust collector, as little installs on it, and it is otherwise slower than a wet weekend. What's with the spinning cursor, just execute the command already, instead of unnecessarily animating stuff: supposed to be a general purpose personal computing device not video game. Software developers seem to have lost the plot about what a personal computer is, and difference with a micro-computer and the importance of stable infrastructure. Not to put too fine a point on it but a virus is an annoying irritating piece of software which interrupts the users use of their computer: eg. Microsoft updates are a virus. All computer seems to have done for past 18 months is download updates: switch on to move software licenses, cannot do anything because updates need installing, runs out of battery power needs recharging, go do something else. Get more spare time, repeat same process, during which process seems to have got infected or otherwise messed up. Internet explorer dead, camera not functioning, and cannot install software for. Seems like may have to wipe clean and re-install from scratch. And there's all this rubbish about XP being defunct: its working perfect. Any way write more about operating systems and personal computers later.

Since I don't have 64 bit office, not even current for that matter (why would it need to be, I customize my own stuff), it seems that the Microsoft DAO 3.6 object library gets placed elsewhere. Normally it would be:

C:\Program Files\Common Files\microsoft shared\DAO\dao360.dll

On 64 bits using 32 bit software its likely to be:

C:\Program Files (x86)\Common Files\microsoft shared\DAO\dao360.dll

So to use my technical library will need to manually change the reference in the vba editor under tools references.

When first started with computers I avoided Microsoft products and stuck with Borland (Turbo Pascal, Turbo C, Quattro Pro, Paradox). I cannot go back down that path, but considering the free software options which are available on both Windows and Linux platforms. Start with them on Windows get used to them, and then move over to Linux. Zorin OS may be something worth looking at. There are a lot of problems to move over to Linux, from major applications (AutoCAD, Multiframe) to small utilities (xyplorer, beyond compare). But back in the early 1990's most high end graphical engineering software required a unix workstation: and likely a specific workstation like a Sun sparc. The problem being drivers for graphics, mice, and printers. At DOS every software developer needed to write drivers for their own application, and similarly with unix/Sun OS locked  to specific or limited range of hardware. MS Windows eliminated part of the problem, if the computer could run Windows then chances are could run specialist software.

The problem we have now though is not about supplying to meet needs, but changing stuff to acquire future income. Need and demand been satisfied, so what can be done to generate income tomorrow. I know, lets knock all the bridges down, along with the power stations and water filtration and pumping stations. Got a new fangled super material and I reckon it would be unsafe, a major national security risk, to keep all these things made out off that rubbishy concrete stuff. Whilst we're at it lets rip up those copper wires and optical fibre rubbish: you know the ones that connect the internet. And those tarmac, asphalt and concrete pavements they're ugly so lets get rid off them to: I'm sure we can think of something to replace them with, might but half defective and inferior. Wheels yeah, lets re-invent them, triangular ones they'd look good: wouldn't work, but who cares its change, and shouldn't resist change. There is just so much garbage on the internet about upgrading, and resistance to change. You do not destroy the heritage, the infrastructure the foundations on which everything is built.

Windows 8 apparently would be faster than Windows 7, and possibly fix the speed issue I have, but its likely more incompatible with the software I want to run. All I needed was new hardware. Software is expensive and bought progressively over the years: but having got, its not so easy to put aside and replace progressively.

On the other hand I did have a personal policy that engineering stuff I'm supposed to be able to do with pencil and paper, we should develop software in-house for and not depend on commercial software. So CAD or graphical editor is really only obstacle to moving to different operating system: most anything else just requires a compiler or spreadsheet.

However, there is no point to changing operating systems or application software if it is automatically updating on a regular basis. Once installed I expect the software to remain unchanged unless I find a problem with it. As for the internet and security, it is not necessary to be connected to the internet all the time, or have every device connected to the Internet.

We still operate DOS boxes because some software no longer available, or if new Windows version is available there is no benefit which would justify the expense, and otherwise doesn't function at Windows command prompt. I don't believe that kind of updating should have occurred, after all MS DOS ran from a 720 kbytye 3.5" floppy disk, so it should have been possible to fully accommodate in the 1 o 2 Gbyte bloat of the current Windows operating systems. From memory Sun OS had a full MS DOS installation which opened in a separate process window.

So it shouldn't be a problem to have an operating system which spawns different operating environments in isolated containers visually indicated  by windows. I think exists already and its called Unix.

Monday, April 07, 2014

Wind Loading Surface Roughness Length versus Terrain Category

A simple spreadsheet making use of AS1170.2:1989 Appendix E. This appendix provided formula for converting surface roughness length (z0) into terrain category and for region A the calculation of the terrain adjusted wind speed or otherwise the terrain category multiplier (Mz,cat).

AS1170.2 commentary contains a design chart which identifies various terrains and gives the surface roughness length (z0). From this chart it is apparent that most rural properties are not TC3 but also they are not TC2. By the use of z0 an intermediate terrain category can be calculated and more economical designs are possible.

The spreadsheet can be downloaded here: surfaceRoughnessLength.xls



Revisions:
[07/04/2014] Original
[23/04/2016] Changed download links to MiScion Pty Ltd Web Store

Wind Loading Risk Assessment

A simple spreadsheet which allows varying life expectancy and calculates the mean return period (R) for the regional wind speed. It is based on formula in Wind Loading of Structures by John Holmes.

It also attempts to map the calculated mean return period to the nearest building code of Australia (BCA) importance level, and return the associated mean return period for such. This part is limited to non-cyclonic regions: A and B.

The file can be downloaded here: windRiskAssessment2014.xls



Revisions:
[07/04/2014] Original
[23/04/2016] Changed download links to MiScion Pty Ltd Web Store

Wind Loading BCA Importance Levels

A simple spreadsheet that maps Building Code of Australia (BCA) importance levels against the annual probabilities of exceedance (actually mean return periods). Excel trend line facilities are then used to get a formula so that any mean return period can be mapped to an importance level.

Whilst AS1170.2 allows for any mean return period, the BCA has limitations, which are not always suitable, starting with the fact that the BCA is primarily about habitable buildings and anything which is not a habitable building becomes BCA class 10. However the BCA is not suitable for design of any structure classified as class 10. For example a garden shed or carport may be suitable to be designed to BCA volume 2, but a 600m high radio mast is not.

Additionally importance level 2, with mean return period (R) of 500 years is not suitable for all buildings, and then again an importance level of 1 (R=100 years) is not always suitable, therefore helpful to identify alternative importance levels: to show that have importance between 1 and 2.  For those who prefer importance levels.

The spreadsheet can be downloaded here. bcaImportanceLevels.xls



Revisions:
[07/04/2014] Original
[23/04/2016] Changed download links to MiScion Pty Ltd Web Store

Wednesday, March 12, 2014

Revised Links to downloads

The links to applications and MS Excel workbooks which were stored on the personal web space which came with my Internet access account have now been replaced with links using Dropbox. So the downloads should be available again.

Thursday, February 13, 2014

Plane Frame Analysis Front End Version 4

frontEndPFrame04.xls
Now converted the variables, used in the various plane frame analysis applications, from records to classes. This version of the front-end for cpframe.exe can read a data file into the variable, then store the contents of the variables to the worksheet. It can also read contents of the worksheet and store in the variables and then write the contents of the variables to a file.

In this way existing data files (.dat) can be opened and edited in Excel. Since reading a file into a workbook over writes the contents of the cells, its not a good idea to calculate the geometry or required loading in the worksheet cells, it is better to generate the model using vba which is the point of the exercise. Using the variables and data structures now defined can write vba code to build a model directly into those variables and by pass the worksheet. The worksheet was just used to verify can read and generate the file through the use of the variables. The file format of the output doesn't match the file read, as the original data files were generated by QPro. Once I had got QPro to generate data files which pframe could read, I didn't worry too much that the file didn't match the exact format of the files saved by pframe. When converted to Excel the format for numbers was taken from the format assigned to the Excel cells, this is no longer done, the format is now hard coded into the vba code. This was done because the file read macro first clears the cells, whilst this has been modified to only clear the contents, the macro can read data files larger than the maximum formatted data area (highlighted in yellow in worksheets) and therefore some format will need assigning to these extra records. The hard coded formats also closely match the original Pascal formats: not liking some of the original formats I have changed them with out affecting the ability of the original application to read the data (thus far).

From this point forward will need to move away from buttons in the worksheet. As far as I know, vba variables have a life as long as the execution of the macro. Thus when macro stops, the variables cease to be accessible, though the memory may not be cleared. This is the reason for storing the contents of the variables to the worksheet, and then reading back from the worksheet. Though I did read recently that global variables do retain values between vba calls: maybe. Before  including the subroutines for reading the data into the variables I did trial reading then writing without storing and retrieving from the worksheet first: the two buttons seemed to work. However I put that down to valid data still being in memory, and same chunk of memory being addressed when macro next macro run, in other circumstances the data may not be valid and may address different chunk of available memory. This is based on past experience with Excel 97, though at that time I admit not overly familiar with use of the Public keyword, so past failures to initialise variables via open workbook method may have been because of not having global variables: though that seems it would have complained about unknown variables and the initialisation wouldn't have worked. Not something I really want to test or rely on: so will assume that from one vba call to the next all variables are wiped. Besides, since making the test for this application, I have removed the global variables and made local to the main class.

So on the assumption that variables are wiped from one vba call to the next it is necessary to keep the vba code active, and to do that need to move buttons from worksheet to a vba form: and have the form retain control until all tasks complete. The alternative is to repeat large segments of initialisation code on each vba call. This latter approach was adopted for the wind loading functions contained in schTechLIB, each function calls subroutines which load arrays which are then searched for data: may have to revisit that and see if I can initialise once.

Another problem to be addressed is access to the variables external to the class in which they are defined. The variables are arrays and vba does not allow public arrays in the definition of a class. So whilst converting records into classes in Turbo Pascal and Delphi is relatively easy its cumbersome in vba. An alternative is to use collections in vba, these can be public, however these are highly likely to be incompatible with the analysis routines of plane frame. {Noting that idea is to incorporate plane frame in the code not shell out and pass data file to a console application. The console application is just a development tool, and not affected by any code I write for the front-end creating the model to be passed to the frame analysis. The first task is to auto-generate a valid structural model of a manufactured  structural product (MSP): not analyse it, that task comes later.}

If don't use collections then need to write property (Let, Get, Set) methods to access the individual elements of the arrays. At present only written one of the classes in Pascal, vb.net and vba, and use of collections keeps vba most similar to Pascal and vb.net.

So as to which is the better option I will work out as I attempt to gain access to the variables and define a structural model.

Structural Design
At the moment I assuming that structural design is split into three stages:

Stage1
Consists of creating the structural model:

  1. Dimension and Geometry
  2. Design Actions

Stage 2
Consists of Analysing the structure and determining the reactions and action-effects. The analysis used depends on the analysis used. The tools used for the analysis depends on the complexity of the analysis.

Stage 3
Consists of:

  1. Component sizing
  2. Connection Design
  3. Footing Design

However the whole process is not all that simple, as connections and footings themselves have their own components and may require repeating stage 1 to stage 3, using different analysis methods suited to the details of the component considered. That is steps 2 and 3 of stage 3 can be removed and these components considered as requiring their own structural models. {eg. connections modelled in isolation along with applied forces, using finite element method}

So cpframe only covers stage 2 for structures which can be modelled as plane frames. The front-end for cpframe covers stage 1, and the back-end covers stage 3. There is plenty of software available for stage 2 and stage 3: though not much choice for software covering Australian materials codes. It is stage 1 however where the problem lies with respect to rapid design of manufactured structural products (MSP). For simple MSP's a few simple calculations in a a spreadsheet will suffice for all stages, for more complex structures some analysis engine is required for stage 2. If using an analysis engine then a structural model needs to be built from simple user input. For structural frameworks the form of the structural model is relatively similar, for example I only need to add a few extra fields, add WriteArc methods to all the classes to export the model to a MicroStran .arc file. These methods I already have in classes specifically written for writing MicroStran files. {Pity I think MicroStran even needs to import the arc file. Otherwise could launch that instead of cpframe.}

So given that the data structures required to represent a structural model are relatively similar I can create my own data structures and use to create models for export to what ever structural software I choose. Note not concerned with picking up the dimension and geometry from a CAD model and adding loads to it: the dimension and geometry are to be auto-generated from a few simple parameters and no other variations permitted. If want other variations then export a model for import into general purpose structural analysis software. An MSP has a defined structural form and a limited set of parameters: if the structural form changes then it is no longer the off-the-shelf MSP. I don't see the purpose of software to permit design at point-of-sale (PoS) but to constrain the options available so that the customer knows they have just defeated the entire point and purpose of going to a supplier of MSP's: and consequently some significant period of design and engineering is not required. On the other hand want to make more customisable options available at the PoS. So that eventually get auto-generation of basic options and then manually edit more custom options: with the allowable editing constrained. {NB: Some advanced level CAD systems for more than 20 years now, have been able to define dimensions by mathematical expressions. For example the span can be set to twice the height. Plus various nodes or points can be used as constraints and references. However that doesn't necessarily equate to being able to increase quantity of components, such as varying the number of portal frames with the length of the building. Also in the building industry they don't pay to much attention to assemblies and sub-assemblies: so the building rather than being a series of portal frames becomes a forest of columns with a collection of rafters. Thus 3D modelling can change the perception of the structure: getting away from the sub-assemblies which make it up.}

Any case the focus at the moment is auto-generation of the structural model, and ultimately being able to analyse that model using various tools to get comparative checks on structural adequacy, so that independent technical checking is viable. In the past and even now, independent checking is a problem, the manufacturers use propriety software generate and check compliance in a few minutes and the city councils engineer certifying the structure may require a week to check the design using general purpose tools: or otherwise simply reading through the reports produced.

So my view is to provide the tools to the certifiers and general designers first for use with general purpose structural analysis tools. This in turn increases the potential for MSP's in the first place, and with MSP's comes the manufacturers desire to limit what the sales team can sell to keep the production economical. So go from the flexible to more and more constraints.



Download frontEndPFrame04.xls .

DISCLAIMER :
Users of the software must accept this disclaimer of warranty :
The software is supplied as is. The author disclaims all warranties, expressed or implied, including without limitation, the warranties of merchantability and of fitness for any purpose. The author assumes no liability for damages, direct or consequential, which may result from the use of the software.



Revisions:
[13/02/2014] Original

[23/04/2016] Changed download links to MiScion Pty Ltd Web Store