Call for Abstracts

IMPORTANT DATES

Call for Abstracts Open: Monday 3 September 2018
Submission Deadline: Thursday 1 November 2018, 11:59pm AEDT
Notification of Acceptance: December 2018

Abstract Criteria

Prospective attendees should be able to get a good idea of the session from the title alone.

All submitted abstracts must meet all of the following requirements:

  • Abstracts must be submitted and presented in UK English
  • Text should be entered in sentence case
  • Your abstract will be submitted as plain text on the submission site (it is recommended that you copy and paste your abstract into the field provided).
  • Describe what will be presented, focusing on the material to be covered, and the benefits to the attendees
  • Identify whom the session is intended for, listing job titles etc.
  • Describe the style of presentation (Presentation vs. demo) and type (Strategic vs. Technical)

 

Along with submitting your abstract, you must also:

  • Review the 'Speaking Terms of Agreement' prior to submitting your abstract (this includes information on speaker entitlements)
  • Submit a biography (limited to 150 words), high quality photo (300 dpi) and high quality company logo (300 dpi) which will be used on our event website and app. If you company has a style guide that must accompany your logo, please ensure you attach a copy when submitting your abstract.
  • Provide a 50-word synopsis and (up to) a 500-word body of your abstract, used on the event website of accepted abstracts
  • Outline three (3) key learning objectives that attendees of your session will have learnt
  • Identify whom the session is intended for, listing job titles etc.
  • Confirm that at least one speaker will be registered to the event to present the submitted abstract.

After review of the submissions, we may contact you to suggest adjustments to your subject matter or mode of presentation, so that we can deliver a conference with the expected scope and quality of subject matter.

To ensure the quality of our conference, we maintain a limit of 3 presentations per speaker; however you are free to submit a greater number of abstracts for consideration if you wish.

Important Information

  • Submitted abstracts will be reviewed by the BILT Committee.
  • Abstracts will be approved on their merit, within the conference's time and resource constraints.
  • Successful applicants will present in either a 75 minute session or a 75 or 150 minute lab (these time frames are a guide only and are subject to change until the program is finalised). Applicants should indicate the preferred length of their planned session during abstract submission.
  • Sessions can take the form of labs, technical presentations, or facilitated discussions. Case studies demonstrating innovative or well-developed practice are welcomed and encouraged to be put forward as an abstract.
  • Feedback suggests that our delegates are becoming more experienced with use of software tools and as such are seeking more advanced sessions. Therefore, submitted abstracts should be classified as (and suitable for) Intermediate, Advanced, Expert, Guru or All Levels.

Session Formats

Presentation/Lecture
Speaker(s) present from front of room, usually accompanied by audio-visual. These types of sessions range from 'how to' through to real project case studies. Session size ranges from 20 - 100 delegates.

Lab
Delegates learn from the speaker using step-by-step live learning experiences, whilst sitting at a computer. There may be provision for a small gallery of additional delegates that bring their own laptops to follow the lab, but you are not required to give them assistance during the lab session. Session size would typically range from 20 - 40 delegates.

Discussions
This can be in the form of a workshop, roundtable or panel discussion, where a speaker facilitates on a specific topic or topics from those who attend.

Abstract Tags

During your submission we will ask you to select up to three tags, one primary, one secondary and one platform, which you believe best reflect the nature of your abstract.

Abstracts may be classified under any of the following tags:

Architecture

Business Strategy & Leadership

Change Management
- Implementation of change of any type, be it in people, processes or technology. May also cover soft skills and/or interpersonal subjects, human collaboration, people development etc.

Coding
- Software programming, development of plug-ins or standalone products, macros, scripts, use of APIs etc.

Computational Design
- Use of generative techniques to iterate designs, using the likes of Grasshopper, Dynamo

Construction
- Field-based construction activities; inclusive of pre-construction planning

Content
- Model content focused; content scoping, creation and/or management issues

Customisation/ Configuration
- System admin, hardware, deployments

Data Management
- Data definition, visualisation and analytics, Common Data Environment, use/admin/management of Common Data Environment and Electronic Document Management Systems; how to deal with legacy information transition; validation of deliverables etc.

DfMA
- Design for Manufacturing and Assembly

Fabrication, Assembly & Installation
- Construction means and methods; based on or off site

General

Infrastructure
- Transportation and other non-building project types, Project types beyond a single building or building complex: road, rail, power/energy, water and precinct/city scale
Legal/Commercial
- Contracts, Intellectual Property, Liability, Insurance, Professional Indemnity, BIM Protocols etc.

MEPF
- Services disciplines and/or trades, but may cross over with Infrastructure tag where emphasis on buildings may not be applicable

Model Management
- Modelling standards, methodology, model exchange, assembly and model validation

Operations & Maintenance
- Facility Management, Asset Management

Procurement
- Procurement of goods or services. May have some overlap with Project Management and Legal/Commercial tags

Project Controls
- Estimation, QTO, Cost Management, Risk Management

Project Management
- Project setup/configuration, project team selection, scope definition, information requirements, etc.

Project Planning
- Construction planning, 4D sequencing, logistics management

Simulation & Analysis

Structure
- Structural Engineering design discipline, but may also include Structural Subcontractors - steel detailers, fabricators, precast concrete etc.

Sustainability
- Life-cycle analysis, costing, building performance, environmental

Visualisation
- Graphical/geometry-based visualisation of project models; eg. presentation methods, real-time rendering environments, immersive tech like Augmented Reality, Virtual Reality or Mixed Reality.

Vendor Tags

Autodesk - Navisworks, Revit, Dynamo
Bentley - Speedicon, Auto Plant, Micro Station, Project Wise
Graphisoft - ARCHICAD
Multi-Vendor
Nemeschek - dRofus, Bluebeam, Solibri
Non-Vendor Specific
Open BIM
Other Vendor
Trimble - Tekla, Sketchup

Levels of Expertise

Speakers must ensure their nominated experience levels matches the content in their presentation.
See a full explanation of each level below:

Intermediate

A general understanding of concepts related to the presentation topic is assumed, but detailed understanding of the specific aspects covered in the topic is not. Delegates are expected to be comfortable with the software generally but may be new to the topic you are covering.

Advanced

The session is expected to explore specific, detailed, high-level and complex functionality and concepts that are, nevertheless, generally encapsulated within the existing capabilities of the program or tool. Delegates are expected to have a good working knowledge of the topic of the class, but not the experience to push it to the degree that is proposed within your session.

Expert

The session is expected to be innovative and forward thinking, exploring new areas and discussing best practice solutions. Delegates are expected to already have a very good knowledge of the subject and may often be other speakers, or people who could be speakers! There is unlikely to be a need to explain concepts, definitions and the like, but expect a potentially robust discussion from people who will know what they are talking about.

Guru
Says all that needs to be said, really: “You live on the raw, bleeding edge of what your software can do, and only smile when it screams in protest and spits out results even the developers said it couldn't manage. If you don’t believe you could be teaching this class, it may not be for you.” There is no such thing as too difficult or arcane for a guru class…
All Levels
These sessions tend to focus on general principals and concepts that do not require deep and/ or specific knowledge of tools. The sessions often take the form of forums, panel discussions and the like, but also include lecture style sessions with a more theoretical/ philosophical orientation.

General topics of interest

Case Studies
  • Large Projects
  • Small Projects
  • Urban Planning Projects... and every project in between
  • Success Stories
    • Architectural Projects
    • Engineering Projects (Any discipline)
    • Any Trade Contractor Projects
  • Renovations
  • Feasibility Studies
  • Collaboration
Software Solutions
  • New Tools* or features for BIM authoring platforms (Revit / ARCHICAD / Tekla / etc.)
  • Emerging Technologies*
  • ADSK Solutions
  • IFC Solutions
  • Interoperability with Other Design Applications*
  • Computational / Generative Design*
  • Workflow and Processes
  • Collaboration / Coordination*
  • Data Linking / Mining
  • Analysis*
  • Quantity Surveying / Estimating (5D)
  • Construction Planning / Scheduling (4D)
  • Documentation / Detailing*
  • Construction Administration
  • Life Cycle Analysis
  • Phasing*
  • Massing / Adaptive Points
  • Approaches to Modeling*
  • Multiple Model Strategies*
  • Mass Production in Construction
  • Prefabrication
  • Best Practices & Productivity
  • Gamification / Virtual Reality
  • Applications for new features / tools
  • Management
  • File Management
  • Content / Families*
  • Standards
  • QA / QC
  • Hardware / Virtualization
  • System Administration
  • Deployments Strategies
  • Project Management
  • Project Setup*
  • In-House Training (New and On-going)
  • API / Developer
  • Integrated Development Environments (including Dynamo)*
  • Languages*
  • Macros / Scripting*
  • Business Strategy
  • Organizational BIM Implementation
  • Adapting to Government Standards
  • Legal Issues
  • Intellectual Property
  • Risk
  • QA / QC
  • Human Resources
  • Industry / Governing Bodies
  • Application Expose for Practice Leaders
  • Project Delivery Methods
  • Proposals and Contracts
  • Insurance
  • Staffing and Workflows
  • Collaboration / Discussion Topics
  • Off the cuff (other)
  • Classic Screw-ups
  • Goofy / Unusual
  • *indicates particular interest for labs

    Labs should be directed to Advanced or higher users. The most effective labs feature a combination of demonstration and hands-on work (perhaps 1:3 or 1:4 proportion?), and the hands-on work focuses on only a very small area of the topic overall. The hands-on work takes longer than you think! If you can, please note who you would nominate as a lab assistant. Alternatively, we can help to arrange this at a later time.

    Remember that these topics represent only some of the areas of interest to the conference, and are neither exhaustive nor prescriptive! We value original and inventive ideas, so have a crack at it ...