Construction

• F.ProjectInformation.ConstructionType - Future - Values derived from project setup questionnaire (Automation)

• F.ProjectInformation.ExteriorFinishMaterials - Future - Values derived from project setup questionnaire (Automation)

• F.ProjectInformation.NumberOfLevels - Future - Values derived from project setup questionnaire (Automation)

• F.ProjectInformation.RoofType - Future - Values derived from project setup questionnaire (Automation)

• F.ProjectInformation.StructuralMaterials - Future - Values derived from project setup questionnaire (Automation)

Identity Data

• F.ProjectInformation.Architect.Address - Used for Value visible in project team section of the F.Index title block, sheet A1.01

• F.ProjectInformation.Architect.Name  - Used for Value visible in project team section of the F.Index title block, sheet A1.01

• Organization Name - System Family Built-in Instance Parameter, do not use. (can not be removed)

• Organization Description - System Family Built-in Instance Parameter, do not use. (can not be removed)

• Building Name - System Family Built-in Instance Parameter, do not use. (can not be removed)

• Author - System Family Built-in Instance Parameter, do not use. (can not be removed)

• Workset - System Family Built-in Instance Parameter, do not use. (can not be removed)

• Edited by - System Family Built-in Instance Parameter, do not use. (can not be removed)

• Design Option - System Family Built-in Instance Parameter, do not use. (can not be removed)

• F.ProjectInformation.Organization.Address - Shared Parameter - text based user input - used for project team section on index title block for sheet A1.01

• F.ProjectInformation.SecondaryInformation - Shared Parameter - text based user input - used for secondary information placed under 'Project Name' on index title block for sheet A1.01

IFC Parameters

• IfcSite GUID - System Family Built-in Instance Parameter, do not use. (can not be removed)

• IfcBuilding GUID - System Family Built-in Instance Parameter, do not use. (can not be removed)

• IfcProject GUID - System Family Built-in Instance Parameter, do not use. (can not be removed)

General

• F.ProjectInformation.01.Dist.Date - F.ProjectInformation.15.Dist.Date - Shared Parameter - text based user input - tied to 'Set Distributions' tag labels in the title block

• F.ProjectInformation.01.Dist.Desc - F.ProjectInformation.15.Dist.Desc - Shared Parameter - text based user input - tied to 'Set Distributions' tag labels in the title block

• F.ProjectInformation.Accessibility - Brokaw TBD

• F.ProjectInformation.ApprovalRequirements - Brokaw TBD

• F.ProjectInformation.County - Shared Parameter - text based user input - tied to 'F.Jurisdiction' tag label in the title block

• F.ProjectInformation.GoverningRegulations - Brokaw TBD

Route Analysis

• Route Analysis Settings - System Family Built-in Instance Parameter, do not use. (can not be removed)

Other

• Project Issue Date - System Family Built-in Instance Parameter, do not use. (can not be removed)

• Project Status - System Family Built-in Instance Parameter, do not use. (can not be removed)

• Client Name - Shared Parameter - text based user input - used for project team section on index title block for sheet A1.01

• Project Address - Shared Parameter - text based user input - used for project information section on index title block for sheet A1.01

• Project Name - Shared Parameter - text based user input - tied to 'F.Title' tag label on title block

• Project Number - Shared Parameter - text based user input - tied to 'F.Project.Number' tag label on title block

• F.ProjectInformation.Client.Address - Shared Parameter - text based user input - used for project team section on index title block for sheet A1.01

• F.ProjectInformation.MEP.Address - Shared Parameter - text based user input - used for project team section on index title block for sheet A1.01

• F.ProjectInformation.MEP.Name - Shared Parameter - text based user input - used for project team section on index title block for sheet A1.01

• F.ProjectInformation.Project.Description - Shared Parameter - text based user input - used for project information section on index title block for sheet A1.01

• F.ProjectInformation.ProjectType - Brokaw TBD

• F.ProjectInformation.Structural.Address - Shared Parameter - text based user input - used for project team section on index title block for sheet A1.01

• F.ProjectInformation.Structural.Name - Shared Parameter - text based user input - used for project team section on index title block for sheet A1.01

Family Selection

• Verify AHJ requirements regarding submission sheet size. Check with Studio Director/Project Manager/Director Of Permitting Services.

• 30x42 default size

• 20x36 & 36x48 optional. Before using a match line in large projects or changing the scale of your plans verify if 36x48 may be used. 

Sheet Name

• Reference CDs > Sheet Index 

Sheet Number

• Reference CDs > Sheet Index 

F.Sheets.PlotDate (Optional)

• Optional use as a plot/printed date

Date/Time Stamp

• System Family Built-in Instance Parameter, do not use. (can not be removed)

Sheet Issue Date

• System Family Built-in Instance Parameter, do not use. (can not be removed)

Drawn By

• System Family Built-in Instance Parameter, do not use. (can not be removed)

Checked By

• System Family Built-in Instance Parameter, do not use. (can not be removed)

Designed By

• System Family Built-in Instance Parameter, do not use. (can not be removed)

Approved By

• System Family Built-in Instance Parameter, do not use. (can not be removed)

Divider VS DividerOriginal

• Not used on A1.01, Uncheck box for both.

Type

• The Title Block on A1.01 Title Sheet is not the same as all other sheets, and is specific to the Index Sheet.

  • Select the "F.Index" type within the title block family.

• If not a Florida Titleblock, coordinate State selection type parameter yes/no check box for the F.Index type only.

Grid

• F.Grid.6x5 - (number of squares in each title block) TBD talk with Andrew

Accessibility Review

• This note should be added to any progress set of drawings that may be forwarded to a 3rd party consultant. There may be occasions where the client may wish to send out for 3rd party reviews prior to final documents, in which case, we would still have the "Progress Set - Not For Construction" turned on, but the second note turned off.

• This Drawing Issuance Does Not Include Sufficient Information to Perform Complete Accessibility and/or Envelope Review

Border

• The objects called Border are 4 Invisible lines that have a visibility parameter. They are on by default. This Parameter will be removed in a future phase.

Company Name

Index Project Name

Not For Construction (Optional)

• This text should be included on any progress set of drawings that are sent out of the office until we are ready to issue the drawings for plan review.

• Note reads: Progress Set - Not For Construction

State-AOR (Architect Of Record)

• 
  

• State-Company Registration

Creating and Managing the Issue History Schedule

The Issue History is a generic model schedule used to track project deliverables and revisions. While some items will be tied to actual Revit revisions, not all deliverables will require one. This schedule is required on the A1.01 Sheet for all projects. 

Please note: The A1.01 Sheet must still be included with every set distribution or revision submission—even if the sheet itself isn't being revised.

To get the sheet to appear in the revision set: place a revision cloud on the sheet itself and override its line color to white.
This ensures the revision is captured in the title block and that the sheet is included in the set.
The user must also update the corresponding entry in the Issue History schedule with the revision number (if applicable), date, and description.

1. Locating the Issue History Schedule

1.1. The "Issue History" schedule is located on sheet A1.01 - Title Sheet, Drawing Index & Issue History. The edit the schedule, locate the schedule under "Schedules/Quantities (all)", the schedule is called:

F.A1.Index.GenericModel.IssueHistory.Key

2. How to Fill Out the Schedule

A. Revision Column (F.GenericModel.ScheduleIssueHistory.DeltaTag)

If the deliverable is tied to a formal Revit Revision, input the corresponding revision number here.
Revit revisions must be created using:
View Tab → Sheet Issues/Revisions
Do not create fake or “dummy” revisions.
If the deliverable is not tied to a revision, leave this field blank.

B. Date Column (F.GenericModel.ScheduleIssueHistory.IssueDate)

Enter the deliverable date in this format:
MM/DD/YY
Example: 08/06/25
Please note: This field controls the sort order, so proper formatting is critical.

C. Description Column (F.GenericModel.ScheduleIssueHistory.IssueDescription)

This field is for labeling the deliverable. Please use a list of Forum Standard (drop-down below under "Additional Information")

Always confirm the correct title with your Project Captain, Project Manager, or Studio Director before entering.

1. Understand the Fields

1.1. Sheet Number: Automatically fills when sheets are created.
1.2. Sheet Name: Auto-populates when named. Use Forum-standard nomenclature. If creating a new name, consult your PM.
1.3. Current Revision: Auto-fills with latest revision. Do not use dummy values. See separate section below for consultant workflows.
1.4. F.A1.Index.Sheet.Discipline:

• For sheets in the main model: use ARCHITECTURAL SHEETS (all caps).

• For sheets linked in consultant models: use STRUCTURAL SHEETS, MECHANICAL SHEETS, ELECTRICAL SHEETS, PLUMBING SHEETS.

  1. This field is hidden in the final schedule.

• Fill this in by selecting all relevant sheets and applying the value in bulk from the Sheet List.

1.5. F.A1.Index.Sheet.Sequence:

• Controls grouping order within the schedule.

• Follow this standard:

  • 0 = Arch sheets before A5

  • 1 = Structural sheets

  • 2 = Arch sheets A5 and after

  • 3 = Plumbing sheets

  • 4 = Mechanical sheets

  • 5 = Electrical sheets

2A. Including Consultant Sheets in the Index (if Consultant Revit models are provided)

2A.1. Once consultant Revit files have been received and collaberation in the cloud, user will link consultant Revit files:

• Open a floor plan view

• Go to Manage Tab > Manage Links > Revit Links

• Add consultant models

2A.2. In Sheet List Properties > Fields tab:

• Check "Include elements in linked files"

Now all consultant sheets will display in the master sheet index.

2B. Consultant Workflow (If Consultant Revit Models Are Not Provided)

If consultant Revit models are not received, Forum will provide a discipline-specific Revit model for each consultant (e.g., one for Mechanical, one for Electrical, etc.). Each consultant is responsible for completing specific scope tasks within their assigned model so that the information can update live in our main file when linked.

The consultant must complete the following steps in their own model:

2B.1. Sheet Setup (from Step 1 Reference)

Consultants are responsible for filling out all sheet information within their provided model. This includes:

A. Sheet Number

B. Sheet Name

C. Current Revision

Revisions must be actual Revit revision clouds and not manually typed
Consultants must create their own revision entries (information to be provided by Forum) via:
View Tab → Sheet Issues/Revisions → Add Revision
Place revision clouds and tags directly on their sheets — these will auto-populate in the main model once linked

D. F.A1.Index.Sheet.Discipline

E. F.A1.Index.Sheet.Sequence

2B.2. Sheet List Visibility

Go to View > Schedules > Sheet List
Consultants should see the sheet list autofilled with their own sheets and revisions
No formatting is required; this will display correctly when linked into the main model

2B.3. Synchronize and Coordinate

For any exceptions or issues, please consult your Production Lead or BIM support.

Perspective Cover Sheet View (Using Camera)

This guide outlines the steps used to create a perspective cover view using a camera (instead of a standard 3D view) to produce a clean, composed image for placement on the A1.01 Cover Sheet. Note: this view has already been established as a standard in the X template and is named F.CoverSheet. The appropriate view template has also been applied. This document serves to explain how that setup was achieved. 

1. Create a Perspective Camera View

1.1. Open a Floor Plan View

Navigate to the main floor plan (ground level).

1.2. Place the Camera

On the top ribbon, go to:
View tab → 3D View → Camera
Click near the bottom-right corner of the building footprint in plan.
Drag your mouse outward to place the camera at a 45-degree angle from the building’s front-right face.
🧠 Pro tip: Place the camera about 100 feet in the X and Y directions from the building corner to get a good composition.

2. Apply the Correct View Template

2.1. Set View Template

Open the new perspective view generated by your camera.
In the Properties Panel, apply view template:
F.A100.Cover

Note: The scope box will be OFF for this view.

3. Adjust View Size for Sheet Placement

3.1. Drag View onto Sheet

Open A1.01 – Title Sheet, Drawing Index & Issue History
Drag the camera view from the Project Browser onto the sheet. The view  is called F.CoverSheet

3.2. Resize the Image

If the view appears too small or large on the sheet:

Select the placed view
On the top ribbon, under Modify | Viewports, click Size Crop
In the Size Crop window, check Scale (Lock Proportions)
Adjust either width or height based on how the building fits on the sheet

-Brokaw
For a  perspective:
use  Size Crop window to size the crop to the grid
Use walk to increase the size of the objects in the view
lock the view

4. Positioning the View on the Sheet

4.1. Default Placement

Align the bottom of the view with the second row of the cover sheet’s grid
The image should not overlap the "Project Information" and "Issue History" blocks on the right of the sheet

4.2. Alternate Layout for Large Projects

If the sheet index takes up multiple columns or space on the left:
The cover image may be cropped and positioned in the top-right corner of the sheet

5. Final Camera Settings

5.1. In the Camera View Properties Panel:

Projection Mode: Perspective
Eye Elevation: 5' 6"
Target Elevation: 5' 6"
Far Clip Active: Checked
Far Clip Offset: 500' 0"
Scope Box: None
View Template: F.A100.Cover

6. Finished Product

✅ What Success Looks Like:

A clean, non-distorted, perspective image of your building
Properly scaled to fit approx. 75% of the sheet width
Never overlapping the issue history and project info blocks
Adjusted for layout based on the number of sheet index columns (if sheet schedule needs to take over more of the cover page, the perspective should shift to the top-right corner of the sheet; the image should adjust size based on the sheets)

Place Holder

Type Selection

• Verify AHJ requirements regarding submission sheet size. Check with Studio Director/Project Manager/Director Of Permitting Services.

• The Title Block on A1.01 Title Sheet is not the same as all other sheets, and is specific to the Index Sheet.

  • Select the "F.Index" type within the title block family.

• 30x42 default size

  • 20x36 & 36x48 optional. Before using a match line in large projects or changing the scale of your plans verify if 36x48 may be used. 

Sheet Name

• Title Sheet, Sheet Index & Issue History

• CDs > Sheet Index 

Sheet Number

• A1.01

• CDs > Sheet Index 

Date/Time Stamp

Sheet Issue Date

• System Family Built-in Instance Parameter, user input text based

Drawn By

• System Family Built-in Instance Parameter, do not use. (can not be removed)

Checked By

• System Family Built-in Instance Parameter, do not use. (can not be removed)

Designed By

• System Family Built-in Instance Parameter, do not use. (can not be removed)

Approved By

• System Family Built-in Instance Parameter, do not use. (can not be removed)

Divider VS DividerOriginal

• Not used on A1.01, Uncheck box for both.