PostFrame Manager Help

User Modified INI Files

A number of INI (system control) files are or can be user edited. A brief synopsis of each follows:

BCREATE.INI --
```
Is keeping posts between wings a default behaviour? (Yes/No)
NO
```
The default behaviour of PostFrame Manager is to assume an open wall between wings; i.e. an open floor plan (set this to YES.) For many Ag structures the idea is that the main wing is a self-contained structure and additional wings are mono sheds (e.g. equipment storage.)
```
Use the MATRIX.CMC file to spec building defaults
NO
```
See below regarding Matrix.INI
```
Basis for max length of Roofing Steel in ft.
30
```
On a large span the roof length (ridge to eave) may be longer than the longest steel panels you can obtain. This setting specifies the longest length.
```
Do we subtract truss span?, If yes, remainder inches of span/12 = trigger (typically 3"), then how many inches do we subtract?
YES,3,3
```
This is included for builders who use the interior dimension rather than exterior.
```
Basis for max length of Siding Steel in ft.
24
```
As per above, the longest piece of steel available for siding use.
```
Lateral Offset (decimal inches, e.g. 1.5 = 1 1/2")
0
```
Movement of trusses from "standard" positions to fine-tune truss spacing for purlin landings.
```
Basis for downspout area for downspout count -- sq in per sq ft
.04
```
When calculating guttering and downspouts, the general method is to calculate the mumber of square inches of throat opening per square foot of roofing. This however will vary depending on local code which in turn is based on annual rainfall and rates (i.e. avg inches/hr.) The number in this section is a multiplier allowing you to get this adjusted to your local conditions. When PostFrame Manager calculates the downspouts, it will look at the throat size (e.g. 2x3 or 4x4, 4x6, etc.) specified to calculate the number of downspouts needed.
```
Slider Doors are calculated separately (YES/NO)
YES
Slider Door default profile
1
Slider Door default type
1
```
Slider doors can be be calculated such that the opening is ignored where it concerns the siding being applied; that is, the same material that would be applied to siding is instead applied to the door. On the other hand some builders prefer to construct slider doors with contrasting color. Overall control of slider door construction can be found in \cmcfiles\sliders.cmc.
```
Large Format Printer Draw Control Pkg Name (if any):
drawfile.dpk
Large Format printer command string:
Image2PDF.exe -output myfile.pdf -image cbpage*.jpg
```
For those with large format printers or plotters, PostFrame Manager drawings output can be directed to a programmable PDF file such that it contains individual drawings and composite pages (e.g. all 4 elevation views on a single large page.)
```
Force changes in walls via menu selection to apply to all walls:
NO
```
This setting is largely superceded by newer menu additions.
```
Allow Site Grade?
YES
```
This setting allows or disallows post depth correction to be handled by the Site Grade window.
```
Force 2' grid?
NO
```
This is a setting used for builders who either generally specialize in very large buildings or who limit their building to 2' increments.
```
Use Cut Purlin Optimization for Std Purlins?
YES
```
This setting allows you to micromanage purlin lumber somewhat, depending of course on the building layout. When PostFrame Manager applies purlins, the general rule is to lay equal lengths at the end of each run. On the other hand there are those who will only build buildings of a certain hand optimised size; this setting then is used to bypass the normal layout scheme in favor of one whereby the first and last pieces of lumber applied to a run are split from a common size.
An example of this is using 4' truss spacings and 1' endwall overhang; a 14' piece of lumber can be cut at 5' and 9' and theoretically save a dollar or two per run. This however only really works at all for a building that is 100% a multiple of 4' units AND has an odd number of bays. Make it 40' long and it fails, although it can work for a 44' unit. This is an optimization where truly your mileage will vary.
```
costrb
Cost
markuprb
Markup
```
These are the labels applied to the Cost and Markup radio buttons beneath the pricing scroll window. Note that changing the radio button setting from Markup to Cost shows a different price.

Whether you choose these to appear or not is governed by the SetPctg applet and will depend on your daily use. If you're using this in front of customers, you might want to consider showing end user price only.
```
Copy saved files to here for email:
c:\bizportz\temprep
```
This is largely for the use of dealers (or for when you grow large enough to have dealers) such that the user saves the datafile for the project and can then have an known location to email the datafile(s) to the main office for final approval.
```
Slider doors disp at CL on column plan drawing (Yes or No)
YES
OH doors disp at CL on column plan drawing (Yes or No)
YES
"Other" doors disp at CL on column plan drawing (Yes or No)
YES
```
Door reference positions on floorplan drawings vary by county and builder; this setting lets you denote whether the door position is relative to the centerline or inside face of a bordering post.
```
Shortcut posts/walls for endwall/sidewall (Yes or No)
NO
```
This is largely superceded by menu system additions.
```
Draw Ctrl Sales Mode
16
```
PostFrame Manager can be operated in Sales mode or Post-Sale mode, with the general assumption that drawings necessary to make a sale usually are elevations and a general floorplan, and Post-Sale mode generally includes all drawings for construction crew use. If your sales method requires more drawings as your way of doing things, please contact us and we'll give you the numeric code for the drawings you need in Sales mode.
```
Allow Elev Dwgs to Offset Roof Ridge (Yes or No)
NO
```
The standard way of illustrating a side view of an elevation is to draw the roof gable end straight up and down. Some people prefer to angle the roof peak slightly inward to lend a quasi-3D effect. This setting controls that drawing aspect.
```
Utilize Environment Control Service (Yes/No)
YES
```
This setting allows for a small applet to move files in and out automatically based on the Mask setting. The idea here is that the Mask can be thought of as a template of sorts and the files moved in and out are those that support that particular style.
```
Utilize Customer Specific Information When Available (Yes/No)
YES
```
For Sales mode PostFrame Manager can collect customer data (e.g. name, address, etc.) so that quotations are automatic when the Reports menu item is accessed.
```
Building Height Limit
20
```
This allows you to limit the elevation height, essentially the height from grade to the bottom of the top chord.
```
Include Markup on Quotes (Yes/No)
YES
```
There are two sorts of quotes that can be generated in that non-markup may be used for purchase by a dealer from a supplier, and markup would be the quote used for the dealer's customer.
```
Compress Fastener Audit Data (Yes/No)
YES
```
PortFrame Manager creates an audit file that specifies what materials get used and where as a way for you to verify that the Materials List is correct. Fasteners can be listed by area used, and this list can grow accordingly. Compressing this data groups like fasteners so that these are not separated by placement.
```
Gable Trim Offset Addition (inches)
0
```
PostFrame Manager is very accurate when calculating the amount of trim needed for any need. On the other hand, there are a couple of situations where this is undesired. Some builders like to add an extra amount to gable fascia to form a better drip; this setting is used to do this.
```
DB truss finding algorithm (1 = old 2 = new)
1
```
How you use this setting will depend on the quality of data you use to hold truss information and the count of usable trusses vs what your sales staff may quote. For example, some builders do not buy trusses with built in overhangs; they create one with a bolted-on "tail" attached to the Top Chord. This means that overhang is ignored in that the system will locate the closest truss to the loading parameters. This can be a hit or miss proposition for overall accuracy if you don't have enough trusses to cover load conditions. Other builders assume all trusses have a 36" or so overhang and then cut the actual overhang in the field to fit. This has the same general problem. In the "1" or "old" mode, the system will either locate the exact truss specified or report a miss.
Bear in mind that this may be tricker than you suspect. Take a look at this picture:

When connecting wings together, the standard truss (depicted in orange) that is used to define a 24" OH on both sidewalls will become necessarily modified to lose one OH (depicted in blue.) Note the perimeter walls of the primary wing shown in bright green; the blue truss necessarily ends there. Using the "1" setting, the truss data will have to have a price associated with both versions of the truss to be able to yield the correct price. In the "2" or "new" setting, you would look up the "closest match" truss for both, hopefully one that either has 36" on each end or 0" on each end requiring a "rafter tail."
```
Fascia Override for no OH (1 = override 0 = leave alone)
1
```
On hung purlin roofs with no sidewall overhang, this sets 1st purl as fascia.
```
Allow support posts above doors (Yes/No)
YES
If support posts above doors is NO, what is the size (in ft) trigger?
16
```
Placing a large opening in a sidewall will result in a gap at least as wide as the door from the top of the door to the elevation height. In normal operation, placeholder posts are positioned where the original posts were prior to the installation of the door. The purpose of this is to allow you to continue to use shorter pieces of lumber and form a rigid wall for the application of siding. These sit atop the door header and extend to the std post height. This is the default behaviour.

On the other hand, there are builders who presume this to be more expensive and maintain that wall rigidity can be maintained well enough depending on the door size. Here, you can set the default or override it, specifying the door/opening size trigger before you think posts are necessary.
```
"Grade" offset (inches)
0
```
This is essentially the backfill slab grade within the building perimeter and is the offset from the system's grade level. There is more here:
Concepts and Definitions
calist.ini -- List of numerical labor categories and text descriptors.
check.ini -- Yes or No for autocheck of duplicate SKU data upon program startup. This is useful primarily when first setting up the system to look for duplicate numbering.
defbbf.ini -- When reporting and doing quotes, this INI controls where on the page (or if) an item is reported. This is useful for those who like to use static pictures showing "typical detail" and the values are filled in per job.
dwgpen.ini -- RGB value of color of pen used for drawings. For mono laser printers etc set to 0,0,0 (black.) For those with color plotters (e.g. 11" x 17" format) a bluish color that mimics blueprint colors may be easier on the eyes. Finding the best RGB color is simpler if you use the Paint applet that comes with windows (Go to Colors|Edit Colors...|Define Custom Colors.)
dwgtitle.ini -- This is the text that shows on each of the drawings produced.
eyectl.ini -- Control of eyebows (see Eyebrows And Porches)
fastcats.ini -- This controls categories of fastener use related to the mnemonic system. The format is mnemonic, description, numerical fastener types that are can be used, and a brief description of how the calculation is made.
```
PST;posts/columns-non-embedded;10,11;Qty=per post
```
freight.ini -- Controls freight calculations.
grade.ini -- Default offset values (left top right bottom) used for site grade.
labormne.ini -- A list of labor mnemonics and categories used for analysis reporting in Reporter)
matrix.ini and matrix2.ini -- These files aren't really user editable, but they're included on this list merely because the concept is important. PostFrame Manager has the ability to auto-adjust ALL settings on the fly based on span/load/height. The idea is that the engineering suitable for shorter spans changes necessarily for longer spans and/or heights and/or loads. Using the Matrix, you can draw e.g. 24x40 and get by with say 4x4 posts, but a structure that is 40x60 may require 6x6 posts. Via these INI files, you can cause PostFrame Manager to auto-select these and any other engineering values as needed. The true value of the Matrix becomes more apparent if you hire sales staff with copies of this software on laptops; you can insure that field quotations are accurately engineered.
menuperm.ini -- This file contains little-used Wing Menu items.
menusys.ini -- This file conrols what you see on the Wing Menu. The underlying idea is that you have control over what appears on the menu, the values you can choose from, and even where they appear. Your menu is custom to your needs.
panels.ini -- Controls the placement of steel panels regarding how over and underlap is configured on longer roofs.
PCTG.INI -- Controls how job cost information aappears. There is an applet that manipulates this file.