Market Survey - Draft CAD BIM Specifications.pdf
PDF 261 KB Posted
- Attached to
- Computer Aided Engineering Graphics (CAEG) â Building Information Modeling (BIM) Software and Professional Services Federal contract opportunity
- Solicitation number
- 16148
About this file
Market Survey - Draft CAD BIM Specifications (pdf)
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Market Survey - Draft Statement of Work.pdf | ||
| Market Survey - Draft EDMS Specifications.pdf | ||
| Market Survey - Draft CAD BIM Specifications.pdf | ||
| Technical Reference Model Information Technology Standards.xls | XLS spreadsheet | |
| Business Declaration Form.doc | DOC document | |
| Business Declaration Form.doc | DOC document | |
| Technical Reference Model Information Technology Standards.xls | XLS spreadsheet | |
| Market Survey - Draft Statement of Work.pdf | ||
| Market Survey - Draft EDMS Specifications.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
SpecificationsSpecificationsSpecificationsSpecifications forforforfor
Computer Aided Design & Drafting (CADD)Computer Aided Design & Drafting (CADD)Computer Aided Design & Drafting (CADD)Computer Aided Design & Drafting (CADD)
Building Information Modeling (BIM)Building Information Modeling (BIM)Building Information Modeling (BIM)Building Information Modeling (BIM) Software Software Software Software
1. 1. 1. 1. Scope:Scope:Scope:Scope: The Federal Aviation Administration (FAA) uses Computer-Aided Design and Drafting (CADD) software to manage their existing buildings and facilities nationwide and in American territories. The FAA has been using the technology since the early 1990’s to reduce their drafting backlog and provide support for other analytical requirements. The current CADD software has been able to meet the FAA’s current needs, however, future efficiencies are needed to offset the increase in workload and the anticipated reduction in the workforce brought on by reductions in funding. The current CADD software will continue to be needed for existing facilities. The FAA will need to evolve to improve productivity for all new facilities (towers and next generation facilities) to accommodate the changing workload. The FAA is seeking to sustain current CADD operations while evolving to accommodate industry embraced Building Information Modeling (BIM) solutions. These capabilities will be utilized nationally within the FAA.
2. Applicable Documents2. Applicable Documents2. Applicable Documents2. Applicable Documents
2.1 2.1 2.1 2.1 GeneralGeneralGeneralGeneral The documents listed below form a part of this specification and are applicable to the extent described in this document.
2.2 2.2 2.2 2.2 Government DocumentsGovernment DocumentsGovernment DocumentsGovernment Documents
2.2.1 FAA-STD-002; US Department of Transportation, Federal Aviation
Administration Standard Engineering Drawing Preparation & Support
2.2.2 FAA-Order-1800.66 Configuration Management Policy
2.2.3 FAA-Order-1370.84 Internet Services
2.2.4 FAA-Order-6000.55B National Facility Drawing Library Procedures
2.2.5 Attachment A, FAA Building Information Modeling (BIM) Requirements
2.2.6 Attachment B, FAA Current Asset Management Tools List
2.32.32.32.3 SSSStandardstandardstandardstandards and other documentsand other documentsand other documentsand other documents
2.3.1 US National CAD Standards (Current version 5.0)
2.3.2 National BIM Standards-United States
3. Requirements3. Requirements3. Requirements3. Requirements
3.1 3.1 3.1 3.1 General SpecificationsGeneral SpecificationsGeneral SpecificationsGeneral Specifications
Software requirements are specified in this section. The following functional requirements are all inclusive in the software and must be construed as exclusive of other approaches to providing the same capability through an alternative means. All software must be fully supported, documented and maintained by the contractor.
3.2 3.2 3.2 3.2 Performance Specification Performance Specification Performance Specification Performance Specification
3.2.1 3.2.1 3.2.1 3.2.1 System/Resource RequirementsSystem/Resource RequirementsSystem/Resource RequirementsSystem/Resource Requirements
3.2.1.13.2.1.13.2.1.13.2.1.1 Client Client Client Client Workstation Workstation Workstation Workstation RequirementsRequirementsRequirementsRequirements
3.2.1.1.1 Must be compatible with the current version of Windows in use at FAA.
3.2.1.1.2 Must work on FAA standard desktop & laptop configurations.
3.2.1.1.3 Must be compatible with the current version of FAA supported web browsers for desktop and mobile devices.
3.2.1.1.4 Must support browser based help files.
3.2.1.1.5 Must be compatible with the current version of FAA’s knowledge sharing networking tools (i.e. Microsoft SharePoint).
3.2.13.2.13.2.13.2.1....2222 ServerServerServerServer RequirementsRequirementsRequirementsRequirements
3.2.1.2.1 Must be compatible with the FAA’s current version of Windows
Server.
3.2.1.2.2 Must provide network license capability.
3.2.1.2.3 Must provide license checkout for remote clients.
3.2.1.2.4 Must have license pooling functionality.
3.2.1.2.5 Must support remote administration.
3.2.1.2.6 Must meet FAA recommended server specifications.
3.2.1.2.7 Must work in a networked environment.
3.2.1.2.8 Must work over a wide area network.
3.2.1.2.9 Should have the ability to be loaded and function on virtual servers.
3.2.13.2.13.2.13.2.1....3333 Solution DeliverySolution DeliverySolution DeliverySolution Delivery
3.2.1.3.1 Must provide silent installation ready client software that is compatible with the FAA’s current installation software.
3.2.1.3.2 Must support manual installation of client software.
3.2.23.2.23.2.23.2.2 Computer Aided Design and Drafting (Computer Aided Design and Drafting (Computer Aided Design and Drafting (Computer Aided Design and Drafting (CADCADCADCADD)D)D)D) Application Application Application Application
RequirementsRequirementsRequirementsRequirements
3.2.2.13.2.2.13.2.2.13.2.2.1 Geometric Shapes & Lines RequirementsGeometric Shapes & Lines RequirementsGeometric Shapes & Lines RequirementsGeometric Shapes & Lines Requirements
3.2.2.1.1 Must as a minimum have the capability to accept coordinate data, provide for two-dimensional input, and provide geometric construction capabilities including but not limited to creation of lines, arcs, circles, quadrilaterals and ellipses.
3.2.2.1.2 Must accept or reject, highlight, reference, and append with a Z dimension X-Y coordinate data through the on-screen cursor or cross-hairs.
3.2.2.1.3 Must construct, extend and truncate a straight line between two
(X-Y-Z) points in space that interfaces or intersects with an existing object on the same or geometrically related plane.
3.2.2.1.4 Must construct a smooth curve through a series of specified data points.
3.2.2.1.4.1 Must construct a straight or curved line parallel to a given line or curve at a given distance.
3.2.2.1.4.2 Must generate single lines and double lines with at least six specified line widths or more.
3.2.2.1.4.3 Must generate dashed lines and centerlines with at least six user-specified line widths and parameters that specify spacing and length of line elements.
3.2.2.1.4.4 Must generate at least six different user-defined lines containing user-defined symbols and spacing in accordance with FAA-STD-
002.
3.2.2.1.4.5 Must support the assignment of transparency and priority to elements.
3.2.2.23.2.2.23.2.2.23.2.2.2 GrGrGrGrids, Coordinates & Cross Hatchingids, Coordinates & Cross Hatchingids, Coordinates & Cross Hatchingids, Coordinates & Cross Hatching RequirementsRequirementsRequirementsRequirements
3.2.2.2.1 Must construct grids to user specifications.
3.2.2.2.2 Must work within a polar coordinate system.
3.2.2.2.3 Must construct radial grids to user specifications.
3.2.2.2.4 Must display superimposed grid or a set of orthogonal axes overlaid on the screen.
3.2.2.2.5 Must support design files using multiple layers/levels or equivalent that meet the current version of FAA-STD-002 and must be expandable to meet layer/level or equivalent requirements of US National CAD standard.
3.2.2.2.6 Must allow users to enclose areas with color, cross hatching, systematic spacing, and user-defined boundaries in accordance with the current version of FAA-STD-002.
3.2.2.2.7 Must exclude user defined boundaries that are not to be filled.
3.2.2.2.8 Must measure angles, distances, areas, based on actual coordinate values in the data set.
3.2.2.2.9 Must locate coordinates of specified points based on actual coordinate values in the data set with double precision accuracy.
3.2.2.33.2.2.33.2.2.33.2.2.3 Graphics Graphics Graphics Graphics RequirementsRequirementsRequirementsRequirements
3.2.2.3.1 Must rotate a graphical element or group of graphical elements about a specified center of rotation through a specified angle.
3.2.2.3.2 Must snap two or more geometric shapes to a common point.
3.2.2.3.3 Must mirror a graphical element or group of graphical elements about a specified plane.
3.2.2.3.4 Must generate graphics/text data and modify it on any specified overlay.
3.2.2.3.5 Must allow for user defined preferences for graphical display on dual monitors.
3.2.2.43.2.2.43.2.2.43.2.2.4 Text, DimensionsText, DimensionsText, DimensionsText, Dimensions, Editi, Editi, Editi, Editing, Menusng, Menusng, Menusng, Menus & Symbol Libraries& Symbol Libraries& Symbol Libraries& Symbol Libraries
RequirementsRequirementsRequirementsRequirements
3.2.2.4.1 Must identify elements for modification including searching by key words.
3.2.2.4.2 Must edit design file information including but not limited to text, symbols, dimensions and tabular data.
3.2.2.4.3 Must support exporting and importing of title block information to ProjectWise and relational databases.
3.2.2.4.4 Must provide the capability to initiate automatic dimensioning and annotation.
3.2.2.4.5 Must support the ability to create FAA specific custom menus & capability switches.
3.2.2.4.6 Must allow users to create personal symbol libraries.
3.2.2.4.7 Must store, modify, and/or delete symbols via keyboard and/or menu input.
3.2.2.4.8 Must accommodate the use of custom menus & macros.
3.2.2.4.9 Must insert & edit text in design files and modify characters within text strings.
3.2.2.4.10 Must have the following capabilities.
3.2.2.4.10.1 Must write natively to .dgn and .dwg files,
3.2.2.4.10.2 Must create .pdf & .tif files from .dgn &.dwg files.
3.2.2.4.10.3 Must reference .pdf and .tif files.
3.2.2.53.2.2.53.2.2.53.2.2.5 DDDDesign fileesign fileesign fileesign file Analysis Analysis Analysis Analysis & Man& Man& Man& Manipuipuipuipulation lation lation lation RequirementsRequirementsRequirementsRequirements
3.2.2.5.1 Must perform engineering, algebraic and mathematical calculations.
3.2.2.5.2 Must permit copying of a predetermined portion of an existing file into another file.
3.2.2.5.3 Must permit the user to revert back to the source file when finished copying the entire file or elements of the file into a new file.
3.2.2.5.4 Must be capable of combining the new file with the source file to form one continuous homogenous file.
3.2.2.5.5 Must provide the following visual capability in design files.
3.2.2.5.5.1 Must support multi-view presentations with a minimum four (4) views per display, and any combination, magnification, reduction, or rotation of any view.
3.2.2.5.5.2 Must combine individual elements together so that they are recognized as one element.
3.2.2.5.6 Must allow for files to be referenced into drawings in accordance with the current version of FAA-STD-002.
3.2.2.6 3.2.2.6 3.2.2.6 3.2.2.6 Design Design Design Design FFFFile ile ile ile Graphics Graphics Graphics Graphics Display OutputDisplay OutputDisplay OutputDisplay Output RequirementsRequirementsRequirementsRequirements
3.2.2.6.1 Must allow a design file to be displayed in a 2D and 3D space.
3.2.2.6.2 Must allow a design file to be displayed with a user defined linear scale.
3.2.2.6.3 Must allow users to pan or zoom in and out of a design file while maintaining graphics quality.
3.2.2.6.4 Must allow a user to dynamically move elements out of the design file using the copy feature.
3.2.2.6.5 Must render solid objects.
3.2.2.7 Design file Design file Design file Design file Line Line Line Line Display OutputDisplay OutputDisplay OutputDisplay Output RequRequRequRequirementsirementsirementsirements
3.2.2.7.1 Must allow for snapping to endpoints, midpoints, tangents, and user defined points on lines, arcs, and circles.
3.2.2.7.2 Must allow for user defined display areas.
3.2.2.7.3 Must allow for user defined displays of selected overlays.
3.2.2.7.4 Must allow for partial deletion of lines, arcs, and/or circles.
3.2.2.7.5 Must allow the user to automatically hide or remove lines.
3.2.2.7.6 Must allow the user to create or define dashed lines automatically.
3.2.2.7.7 Must allow the user to control the line type scale.
3.2.2.3.2.2.3.2.2.3.2.2.8888 Design Design Design Design FilFilFilFile e e e Plot & HardcopyPlot & HardcopyPlot & HardcopyPlot & Hardcopy OutpOutpOutpOutputututut RequirementsRequirementsRequirementsRequirements
3.2.2.8.1 Must allow the user to specify the scale and plot extents.
3.2.2.8.2 Must allow users to create non graphic reports on FAA printers.
3.2.2.8.3 Must support batch printing or plotting.
3.2.2.8.4 Must support FAA defined plot styles.
3.2.2.8.5 Must be certified to be compatible with FAA printers and plotters.
3.2.3.2.3.2.3.2.2222....9 3D Interface9 3D Interface9 3D Interface9 3D Interface RequirementsRequirementsRequirementsRequirements
3.2.2.9.1 Must model solids in 3D.
3.2.2.9 2 Must perform the following functions.
3.2.2.9.2.1 3D design and drafting functions (i.e., part, tool, and fixture design).
3.2.2.9.2.2 Customization of menus, macros and symbols.
3.2.2.9.2.3 Customization of surface element definitions and manipulations.
3.2.2.9.3 Must calculate, locate and manipulate the following 3D surface elements or parts.
3.2.2.9.3.1 Bounded planes, circular cylinders, and circular truncated cones,
3.2.2.9.3.2 Ruled surfaces, surfaces of revolutions.
3.2.2.9.3.3 Defined 3D objects (sculptured surfaces).
3.2.2.9.3.4 Specified angle of rotation about an axis for an element in 3D space.
3.2.2.9.3.5 Modified vertex position in the boundary of a constructed ruled surface.
3.2.2.9.3.6 Intersection between a plane and a design element.
3.2.2.9.3.7 Combined properties for objects of intersection.
3.2.2.9.3.8 Multi-discipline clash detection.
3.2.33.2.33.2.33.2.3 Building Building Building Building IIIInformation Modeling nformation Modeling nformation Modeling nformation Modeling ((((BBBBIM) IM) IM) IM) Application RequirementsApplication RequirementsApplication RequirementsApplication Requirements
3.2.33.2.33.2.33.2.3.1 .1 .1 .1 BuildingBuildingBuildingBuilding Information Model Development RequirementsInformation Model Development RequirementsInformation Model Development RequirementsInformation Model Development Requirements
3.2.3.1.1 Must process parametric information image & data files.
3.2.3.1.2 Must accommodate and provide tailoring of business rules, i.e.
customized algorithms, logic, compliance requirements, etc.
3.2.3.1.3 Must design, create, review, measure and validate BIM models.
3.2.3.1.4 Must manipulate BIM models and Objects.
3.2.3.1.5 Must perform engineering analysis for building design and construction disciplines called out in the current version of FAA-
STD-002.
3.2.3.1.6 Must access data connected to the parametric objects.
3.2.3.23.2.3.23.2.3.23.2.3.2 BBBBIMIMIMIM Management Management Management Management & Administrative & Administrative & Administrative & Administrative RequirementsRequirementsRequirementsRequirements
3.2.3.2.1 Must provide a collaborative design workflow with multiple users and multiple disciplines.
3.2.3.2.2
3.2.3.2.3 Must provide referencing of other models/drawings and images.
3.2.3.2.4 Must support Configuration Management workflows and support version control.
3.2.3.2.5 Must automatically update 3D view when 2D plans are updated, both 2D plans and 3D models must work within a captive environment.
3.2.3.2.5.1 Must have configurable time-out features.
3.2.3.3.2.3.3.2.3.3.2.3.3333 Compatibility Compatibility Compatibility Compatibility RequirRequirRequirRequireeeementsmentsmentsments
3.2.3.3.2.3.3.2.3.3.2.3.3333.1.1.1.1 Compatibility Requirements with Document Management Compatibility Requirements with Document Management Compatibility Requirements with Document Management Compatibility Requirements with Document Management SystemSystemSystemSystem
3.2.3.3.1.1 Must be compatible with FAA’s deployed version of Electronic
Document Management System, i.e. Bentley ProjectWise for document production.
3.2.3.3.2.3.3.2.3.3.2.3.3333....2222 Compatibility Compatibility Compatibility Compatibility Requirements with Requirements with Requirements with Requirements with the the the the FAAFAAFAAFAA’s ’s ’s ’s GISGISGISGIS toolstoolstoolstools
3.2.3.3.2.1 Must be compatible with the FAA’s current GIS tools utilizing geographic coordinates contained in the Information models to identify location on a map.
3.2.3.3.2.2 Must support bidirectional information exchange between Information models and GIS tools.
3.2.3.3.2.3.3.2.3.3.2.3.3333....3333 Compatibility Compatibility Compatibility Compatibility Requirements with Asset Management Requirements with Asset Management Requirements with Asset Management Requirements with Asset Management
ToolsToolsToolsTools
3.2.3.3.3.1 Must be compatible with the FAA’s current project scheduling & resource tools.
3.2.3.3.3.2 Must create associations between the model and tasks.
3.2.3.3.3.3 Should add and edit parent and child tasks.
3.2.3.3.3.4 Must interface with the FAA’s Microsoft Office suite of tools.
3.2.3.3.3.5 Must interchange facility asset and location information, in accordance with the current version of FAA BIM guidelines to the FAA’s asset management tool(s).
3.2.3.3.2.3.3.2.3.3.2.3.3333....4444 Compatibility Compatibility Compatibility Compatibility Requirements with Facility Management Requirements with Facility Management Requirements with Facility Management Requirements with Facility Management
ToolsToolsToolsTools
3.2.3.3.4.1 Have the ability to link and add facility data to the models components and validate contained data.
3.2.3.3.4.2 Ability to import image & data files from open source Computer Aided Facility Management (CAFM) \ Computer Maintenance
Monitoring System (CMMS) databases.
3.2.3.3.4.3 Must be compatible with third party applications using industry neutral standards to transfer facility data and building geometry to Facility Management applications.
3.2.3.3.53.2.3.3.53.2.3.3.53.2.3.3.5 Compatibility with other analytical toolsetsCompatibility with other analytical toolsetsCompatibility with other analytical toolsetsCompatibility with other analytical toolsets
3.2.3.3.5.1 Must perform collision/clash detection or be compatible with industry standard tools.
3.2.3.3.5.2 Must be compatible with industry standard analysis tools and use industry neutral standards, like xml for the transfer of data.
3.2.3.3.5.3 Must be compatible with industry standard cost estimating and accounting tools and use industry neutral standards for the transfer of data.
3.2.3.33.2.3.33.2.3.33.2.3.3 Import/Export RequirementsImport/Export RequirementsImport/Export RequirementsImport/Export Requirements
3.2.3.4.1 Must import 2D extraction drawings that comply with FAA-STD 002.
3.2.3.4.2 Must import 3D models from other industry-standard
visualization tools.
3.2.3.4.3 Should import images & information from an Open Database Connectivity (ODBC) Database.
3.2.3.4.4 Must import information with FAA supported mobile devices from remote locations.
3.2.3.4.5 Must import 2D & 3D laser scan file formats.
3.2.3.4.6 Must export 3-D models through a standard interface to other industry-standard visualization tools.
3.2.3.4.7 Must export images & information to an ODBC Database
3.2.3.4.8 Must export Construction Operations Building information exchange (COBie) data.
3.2.3.4.9 Must export information to FAA supported mobile devices from remote locations.
3.2.3.4.10 Must export to DXF, PDF, DGN, and DWG.
3.2.3.3.2.3.3.2.3.3.2.3. 5555 OOOOutpuutpuutpuutput Requirementst Requirementst Requirementst Requirements
3.2.3.5.1 Must render presentation quality 3D models.
3.2.3.5.2 Must provide visualization of the model as a wireframe, shaded, or realistic view.
3.2.3.5.3 Should generate reports on parametric information (image & data) analysis results in text & graphical formats.
3.2.3.5.4 Must generate 2D drawings that can be formatted to comply with the current version of FAA-STD-002.
3.2.3.2.3.2.3.2.3.3.3.3.6 6 6 6 InformationInformationInformationInformation ExchangesExchangesExchangesExchanges
3.2.3.6.1 Must comply with the Construction Operations Building information exchange (COBie).
3.2.3.6.2 Should comply with the Specifications Property information exchange (SPie).
3.2.3.6.3 Should support Lifecycle information exchange (LCie).
3.2.3.73.2.3.73.2.3.73.2.3.7 IFCIFCIFCIFC
3.2.3.7.1 Must import and export its native models to Industry Foundation
Class (IFC) models.
3.2.3.7.2 Must support the current (IFC) version.
3.2.3.7.3 Must support changes to the IFC export and information sharing.
3.2.3.83.2.3.83.2.3.83.2.3.8 BBBBIM Adaptation RequirementsIM Adaptation RequirementsIM Adaptation RequirementsIM Adaptation Requirements
3.2.3.8.1 Must execute both imperial and metric standards.
3.2.3.8.2 Must hyperlink with websites, PDFs, word documents, etc.
3.2.3.8.3 Must have the capability to customize Application Program Interface.
3.2.3.8.4 Must allow for tailoring of customized business rules, i.e.
algorithms, logic, compliance requirements, etc.
3.2.3.93.2.3.93.2.3.93.2.3.9 BBBBIM Scalability RequirementsIM Scalability RequirementsIM Scalability RequirementsIM Scalability Requirements
3.2.3.9.1 Must provide scaling requirements to meet demand.
3.2.3.9.2 Must be compatible within an enterprise/cloud environment.
4. 4. 4. 4. Quality Assurance ProvisionsQuality Assurance ProvisionsQuality Assurance ProvisionsQuality Assurance Provisions
4.1 Quality assurance must be validated for each of the requirements using one of the following methods; inspection, demonstration or analysis.
4.2 Software must be tested and certified to meet the requirements of release management software.
4.3 Software must meet compatibility testing requirements of FAA’s standard desktop and laptop components.
5555. . . . Preparation & Preparation & Preparation & Preparation & DDDDeliveryeliveryeliveryelivery::::
5.1 The software must be downloadable from a secure web site and received through physical media like a USB Drive or DVD.
5.2 User manuals and training manuals must define complete details for operation of the software and be delivered in the vendor’s format.
File details come from the government source that posted it. Updated .