Method and system for parameterized modeling of reinforcing steel bars of prefabricated parts of expressways

Abstract

The invention relates to the technical field of prefabricated part modeling, in particular to an expressway prefabricated part steel bar parametric modeling method and system, and the method comprises the following specific steps: in a three-dimensional design platform, classifying expressway prefabricated parts according to the structural features of the prefabricated parts, and forming a unified part parameter set; forming a standard verification rule base based on the entity data model; in the three-dimensional design platform, a parameterized geometric template is established based on the steel bar host contour family, the key size in the geometric template is bound with the unified component parameter set, and a steel bar arrangement algorithm is called to generate a steel bar three-dimensional model of the prefabricated component; in the generation or updating process of the steel bar three-dimensional model, the standard verification rule base is called based on the current component parameters, standard verification is conducted on the key steel bar parameters, and the verification result is used for prompting or controlling the steel bar three-dimensional model. According to the method, the steel bar parameterization method of the prefabricated parts can be unified, and real-time standard checking is achieved.

Description

Technical Field

[0001] This invention relates to the field of precast component modeling technology, specifically to a method and system for parametric modeling of steel reinforcement in precast highway components. Background Technology

[0002] In highway construction, precast components are widely used due to their controllable quality and rapid construction. As the core load-bearing component of precast components, the accuracy and efficiency of their design are crucial. With the popularization of BIM (Building Information Modeling) technology, 3D design has become an industry trend. However, current mainstream BIM modeling software (such as Revit) suffers from incomplete component libraries and insufficient specialization when dealing with the diverse and unique precast components specific to the highway industry. Designers often need to rely on secondary development tools such as Dynamo and Python for parametric design, but these solutions still have limitations.

[0003] Currently, the most similar implementation to this invention is "a parametric modeling method for precast component reinforcement based on the Revit+Dynamo platform". This method has been demonstrated in academic papers and engineering practices. For example, parametric creation of bridge main structure and reinforcement models has been achieved through Revit+Dynamo; and automated creation of reinforcement has been achieved for precast small box girders through Revit+Dynamo software.

[0004] This approach utilizes Revit as the model carrier and graphics platform, and employs the Dynamo visual programming tool to define key dimensions of components (such as beam height and web thickness) as driving parameters by writing logic scripts. When these parameters change, the Dynamo scripts drive the Revit API (Application Programming Interface) to automatically regenerate or modify the reinforcement model. This method achieves parametric driving of the reinforcement model to a certain extent, reducing repetitive modeling work.

[0005] The Revit+Dynamo scheme mentioned above has the following significant drawbacks: the modeling of various precast components (T-beams, small box girders, circular culverts, cover plates, and drainage ditches) is done independently, without a unified method for parametric reinforcement; the modeling is out of sync with the JTG standard, relying on manual verification of clear distances, anchorage lengths, etc., resulting in a high error rate. Summary of the Invention

[0006] Based on the above description, the present invention provides a method and system for parametric modeling of steel reinforcement in precast components for highways, which can unify the parametric method of steel reinforcement in precast components and realize real-time standard verification.

[0007] On the one hand, the technical solution of the present invention to solve the above-mentioned technical problems is as follows: a method for parametric modeling of steel reinforcement in precast components for highways, comprising the following specific steps:

[0008] In the 3D design platform, highway prefabricated components are classified according to their structural characteristics, abstracted into a family of steel reinforcement host contours, and parameters reflecting the geometry of the components and the arrangement of steel reinforcement are extracted to form a unified set of component parameters.

[0009] Based on the entity data model, a parameter data structure is established for the component parameter set, and according to the relevant highway bridge and culvert specifications, the binding clauses in the specifications are expressed as specification verification rules corresponding to the parameter data structure, thus forming a specification verification rule library;

[0010] In the 3D design platform, a parametric geometric template is established based on the rebar host contour family. The key dimensions in the geometric template are bound to the unified component parameter set, and the rebar layout algorithm is called to generate the 3D model of the rebar of the prefabricated component.

[0011] During the generation or updating of the 3D model of the reinforcing steel, the standard verification rule library is called based on the current component parameters to perform standard verification on key reinforcing steel parameters, and the verification results are used to prompt or control the 3D model of the reinforcing steel.

[0012] Through the above technical solution, various precast components of highways are abstracted into a family of steel reinforcement host contours, a unified parameter set is constructed, and the parameters are mapped to the standard clauses into a machine-readable rule base. This enables geometric modeling, steel reinforcement layout and standard verification to be linked in a closed loop within the same three-dimensional platform. This achieves unified parametric modeling and real-time standard verification of steel reinforcement for multiple types of precast components, significantly reducing omissions, mismatches and non-standard issues caused by manual modeling and manual review, and improving design efficiency and model reliability.

[0013] Based on the above technical solution, the present invention can be further improved as follows.

[0014] Furthermore, when performing a type analysis on the aforementioned precast highway components,

[0015] Precast T-beams, precast small box girders, precast circular culverts, precast cover plates, and precast drainage ditch components are respectively sorted into corresponding steel reinforcement host profile families. The steel reinforcement host profile family is defined as the concrete geometry that constitutes the body of the precast component and is used to define the spatial boundary of the steel reinforcement arrangement.

[0016] A unified naming rule for the profile families of steel reinforcement hosts of different precast components and a unified naming rule for geometric variables are adopted.

[0017] For each type of rebar host profile family, its geometric characteristics and the inherent rules of rebar arrangement are further analyzed.

[0018] For the host profile family of precast T-beams, identify and model typical steel reinforcement categories such as top slab longitudinal reinforcement, web stirrups, and horseshoe reinforcement;

[0019] For the host profile family of precast circular culverts, identify and model typical steel reinforcement categories of spiral and longitudinal bars;

[0020] The above-mentioned rebar categories are then associated with the corresponding rebar host profile families in the form of category identifiers.

[0021] Furthermore, when extracting driveable design variables from the geometric features and reinforcement arrangement rules of various reinforcement host profile families, the design variables are divided into two categories: geometric variables and reinforcement parameters. The geometric variables include at least one or more of the following: total member length, beam height, web thickness, flange width, pipe diameter, and wall thickness. The reinforcement parameters include at least one or more of the following: reinforcement grade, reinforcement diameter, reinforcement spacing, protective layer thickness, anchorage length, and hook angle. The reinforcement host profile family to which each variable belongs and the variable type are explicitly marked in the unified member parameter set.

[0022] The geometric variables and reinforcement parameters are associated with the mandatory constraint parameters in the relevant specifications. This includes at least mapping the lower limit of the net spacing of reinforcement, the lower limit of the thickness of the concrete cover of reinforcement, the lower limit of the anchorage length of reinforcement, and the bending construction parameters of reinforcement to the corresponding clauses in the aforementioned specifications. In the parameter data structure, the corresponding specification clause number and the allowed value range are recorded for each variable, which serves as the basic data source for constructing the specification verification rule base.

[0023] In one step, geometric templates are created for each type of rebar host profile family using the Geometry API of the 3D design platform.

[0024] Furthermore, all key dimensions in the geometric template are parametrically controlled by geometric variables, so that the geometric template of the precast T-beam is completely determined by the geometric variables of beam height, flange width, web thickness, and diaphragm spacing, and the geometric template of the precast circular culvert is completely determined by the geometric variables of pipe diameter, wall thickness, and segment length.

[0025] The Parameter API of the 3D design platform is invoked to associate the geometric variables with the corresponding reinforcement parameters, so that any modification to the geometric variable or reinforcement parameter can simultaneously drive the linkage change of the host concrete geometry and reinforcement layout logic, and automatically reconstruct the precast component model with different sizes and reinforcement schemes under the drive of a unified parameter set.

[0026] Furthermore, when constructing and invoking the rebar layout algorithm based on the code verification rule base, the code verification rule base shall include at least the following types of rules:

[0027] Spatial positioning rules used to describe the arrangement of longitudinal reinforcement along the length of a member;

[0028] Used to describe the spatial positioning rules for stirrups that vary along the height of a member or within a local area of ​​a member;

[0029] Used to describe the spatial positioning rules of spiral reinforcement along the winding path of the pipe body;

[0030] The spatial positioning rules associate the coordinates of the reinforcement arrangement with reinforcement parameters such as the total length of the component, beam height, web height, pipe diameter, and reinforcement spacing in the form of parametric expressions. It further includes parameter linkage rules to describe how reinforcement parameters such as the number of stirrups, the length of the stirrup reinforcement zone, the number of longitudinal reinforcement bars in the top slab, and the number of spiral reinforcement rings in the circular culvert automatically adjust when the geometric variables of beam height, web thickness, and flange width change. The above rules are solidified in the rule base in the form of functional relationships or logical expressions to uniformly manage the spatial arrangement logic and parameter linkage relationships of reinforcement in various types of precast components.

[0031] Furthermore, when converting the normative constraints into algorithmic logic in the rule base, at least the clauses "the clear spacing of the main reinforcing bars shall not be less than their diameter and shall not be less than 25mm" and "the anchorage length of the reinforcing bars shall not be less than the La value specified in the standard" are represented as inequality constraints with parameters such as the diameter of the reinforcing bars, the thickness of the protective layer, and the grade of the stressed reinforcing bars as independent variables. An independent logical node or rule entry is established for each normative constraint in the normative verification rule base. During the normative verification process, different normative clauses are called and verified one by one.

[0032] Furthermore, when establishing the parameter data structure based on the entity data model, EC Schema or an equivalent entity model is used to define entity classes for the rebar host profile family, geometric variables, rebar parameters, and rule entries in the rule base. The relationships between entities are used to record "which geometric variables and rebar parameters a certain rule entry applies to" and "which rule entries a certain rebar host profile family should use". By traversing the entity relationships, a subset of rules applicable to the current component type and parameter combination is automatically selected, stored in association, and uniformly called in the parameter data structure and rule base.

[0033] Secondly, the technical solution of the present invention to solve the above-mentioned technical problems is as follows: a parametric modeling system for reinforcing steel bars of precast highway components, characterized in that it includes:

[0034] The host profile family definition module is used to classify highway precast components in the 3D design platform. It abstracts the concrete geometry that constitutes the body of the precast component into a steel reinforcement host profile family, and extracts parameters reflecting the geometry of the component and the arrangement of the steel reinforcement from each steel reinforcement host profile family to form a unified set of component parameters applicable to a variety of precast components.

[0035] The parameter and specification mapping module is used to establish a parameter data structure for the unified component parameter set based on the entity data model.

[0036] Based on the relevant design and construction specifications for highway bridges and culverts, the binding clauses in the specifications are expressed as specification verification rules corresponding to the parameter data structure, thus forming a specification verification rule library;

[0037] The parametric modeling module is used to call the Geometry API of the 3D design platform, establish a parametric geometric template based on the rebar host contour family, parametrically bind the key dimensions in the geometric template with the unified component parameter set, and automatically calculate the 3D coordinates of the rebar based on the rebar layout algorithm driven by the standard verification rule library to generate the 3D model of the rebar of the precast component.

[0038] The automatic verification module is used to obtain the current component parameters from the unified component parameter set and the three-dimensional model of the steel reinforcement when the three-dimensional model of the steel reinforcement is generated or updated. It calls the standard verification rule library to perform standard verification on key parameters such as the clear spacing of the steel reinforcement, the anchorage length, the bending structure, and the thickness of the protective layer. The steel reinforcement components that do not meet the standard are presented on the three-dimensional design platform interface in the form of graphic highlighting and text prompts.

[0039] The module for calculating cutting length and exporting data is used to calculate the cutting length of each steel bar component based on the three-dimensional model of the steel bar after the steel bar has passed the specification verification. It then exports the steel bar statistical results and cutting data in the form of a table file or a structured data file for use in steel bar processing and construction.

[0040] The above technical solution integrates host profile family definition, parameter and specification mapping, parametric modeling, automatic specification verification, and cutting length calculation and data export into the same system. This achieves an integrated process from parameter definition, 3D rebar modeling, specification verification to processing cutting data output, reducing manual data transfer and secondary entry between multiple software and formats, improving data consistency in the design-verification-processing stages, reducing rebar processing error rate, and accelerating the design and implementation process of precast components for highways.

[0041] Furthermore, the host profile family definition module is configured as follows:

[0042] Different types of precast highway components, such as precast T-beams, precast small box girders, precast circular culverts, precast cover plates, and precast drainage ditches, are classified into corresponding steel reinforcement host profile families. A unified profile family naming rule and a unified geometric variable naming rule are adopted for the steel reinforcement host profile families of different precast components.

[0043] Furthermore, the host profile family definition module is configured to: for each type of rebar host profile family, analyze its geometric characteristics and the inherent rules of rebar arrangement, identify typical rebar categories such as top slab longitudinal bars, web stirrups, horseshoe reinforcement bars in precast T-beams, and spiral bars and longitudinal bars in precast circular culverts, and associate the above rebar categories with the corresponding rebar host profile families in the form of category identifiers.

[0044] Meanwhile, the design variables extracted from each rebar host profile family are divided into two main categories: geometric variables and rebar parameters.

[0045] The geometric variables include at least one or more of the following: total member length, beam height, web thickness, flange width, pipe diameter, and wall thickness.

[0046] The steel reinforcement parameters include at least one or more of the following: steel reinforcement grade, steel reinforcement diameter, steel reinforcement spacing, protective layer thickness, anchorage length, and hook angle.

[0047] The unified component parameter set explicitly labels the rebar host profile family and variable type of each variable to support unified parameter management and automatic selection of rebar layout mode for multiple precast component types.

[0048] Furthermore, the parameter and specification mapping module is configured to: associate the geometric variables and reinforcement parameters in the unified component parameter set with the mandatory constraint parameters in the relevant specifications, at least to correspond one-to-one with the lower limit of the net spacing of reinforcement, the lower limit of the thickness of the concrete cover of reinforcement, the lower limit of the anchorage length of reinforcement, and the bending construction parameters of reinforcement with the corresponding clauses in the above specifications, and record the corresponding specification clause number and the allowed value range for each variable in the parameter data structure;

[0049] Furthermore, the parameter and specification mapping module adopts EC Schema or an equivalent entity data model, defining entity classes for the rebar host profile family, geometric variables, rebar parameters, and rule entries in the specification verification rule base. Through the association relationship between entities, it records "which geometric variables and rebar parameters a certain rule entry applies to" and "which rule entries a certain rebar host profile family should use". This enables the automatic specification verification module to automatically select the applicable rule subset based on the association relationship between entities when performing rebar modeling and specification verification for different types of precast components, so that the parameter data structure is associated with the rule base for storage and unified retrieval.

[0050] Compared with the prior art, the technical solution of this application has the following beneficial technical effects:

[0051] 1. For various precast components such as T-beams, small box girders, and circular culverts, a modeling system of "reinforcement host contour family + unified component parameter set" is proposed. The Geometry / Parameter API is used to achieve unified driving of geometric dimensions and reinforcement parameters, so that different component types, different sizes and reinforcement schemes can be quickly reconstructed and reused under the same parameter framework, significantly reducing the workload of repeated modeling and modification.

[0052] 2. Explicitly map geometric variables and reinforcement parameters to the code clauses, establish a code verification rule base using entity data model, and solidify constraints such as clear spacing of reinforcement, anchorage length, and bending structure with inequalities and logical expressions, so that the system can automatically select rule subsets according to component type and parameter combination and check them one by one in real time, so as to realize the machine readability, refinement and easy maintenance and updating of code requirements;

[0053] 3. The three-dimensional coordinates of longitudinal bars, stirrups, and spiral bars are automatically calculated through spatial positioning rules and parameter linkage rules. After the specifications are verified, the cutting length and steel bar statistics are directly calculated and the data is exported. The parameter definition, three-dimensional modeling, specification verification and processing data generation are integrated into an integrated process, reducing the rate of omissions, non-compliance and processing errors, and improving the overall efficiency and quality of highway precast component design and construction. Attached Figure Description

[0054] Figure 1 This is a flowchart of the parametric design process for prefabricated components according to the present invention;

[0055] Figure 2 This is a flowchart of the parametric modeling and specification verification process of the present invention;

[0056] Figure 3 This is a schematic diagram of the parametric modeling interface for the prefabricated small box girder component of the present invention;

[0057] Figure 4 This is a schematic diagram of the parametric design interface for the precast small box girder reinforcement of the present invention;

[0058] Figure 5 This is a schematic diagram of the parametric modeling interface for the precast T-beam of the present invention;

[0059] Figure 6 This is a schematic diagram of the parametric design interface for the precast T-beam reinforcement of the present invention;

[0060] Figure 7 This is a schematic diagram of the parametric modeling interface for the prefabricated circular culvert of the present invention;

[0061] Figure 8 This is a schematic diagram of the parametric design interface for precast circular culvert reinforcement according to the present invention.

[0062] Figure 9This is a schematic diagram of the parametric modeling interface and reinforcement model of the precast cover plate of the present invention;

[0063] Figure 10 This is a schematic diagram of the parametric design interface for the precast cover plate covering the reinforcing steel reinforcement of the present invention.

[0064] Figure 11 This is a schematic diagram of the parametric modeling interface for the prefabricated drainage ditch cover of the present invention;

[0065] Figure 12 This is a block diagram of the parametric modeling system for reinforcing steel bars in precast highway components according to the present invention.

[0066] Figure 13 This invention relates to a method for parametric modeling of reinforcing steel bars in precast highway components.

[0067] Figure 14 This is a flowchart illustrating the parametric modeling and rule-driven reinforcement generation process of the present invention.

[0068] Figure 15 This is a schematic diagram of the automatic verification and material export process / results of the present invention. Detailed Implementation

[0069] To facilitate understanding of this application, a more complete description will be provided below with reference to the accompanying drawings, which illustrate embodiments of the present application. However, the present application can be implemented in many different forms and is not limited to the embodiments described herein. Rather, these embodiments are provided so that the disclosure of this application will be more thorough and complete.

[0070] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of this application.

[0071] Example 1: Reference Figures 1-15 This paper presents a method for parametric modeling of steel reinforcement in precast highway components. The method is based on the Bentley OpenRoads Designer 3D highway design platform and its MicroStation SDK. It is deployed in the internal environment of design units via C# / C++ plugins. It is used to complete parametric modeling, automatic specification verification, and data export of steel reinforcement in commonly used precast highway components (precast T-beams, small box girders, circular culverts, cover plates, drainage ditch cover plates, etc.) within the same platform.

[0072] The method in this embodiment generally includes the following steps: S1 Precast component type analysis and reinforcement host profile family establishment; S2 Design variable extraction and unified component parameter set construction; S3 Parameter data structure and entity data model establishment, and mapping with specification clauses; S4 Geometric template creation and parameter binding based on reinforcement host profile family; S5 Reinforcement layout algorithm based on rule base to generate 3D reinforcement model; S6 Automatic specification verification and model control during reinforcement generation; S7 Automatic selection and expansion of rule subsets using entity association.

[0073] The steps are explained below.

[0074] I. Analysis of Precast Component Types and Establishment of Reinforcement Host Profile Families

[0075] 1.1 Precast Component Type Classification: In engineering projects, the system first reads the component list from the route, bridge, and drainage models, and standardizes the classification of common precast components. The component type dictionary includes at least: precast T-beams (TypeCode="TBEAM"); precast small box girders ("BOXGIRDER"); precast circular culverts ("CIRCULARCULVERT"); precast cover plates and cover plates covering slabs ("SLABCOVER"); and linear slab components such as precast drainage ditch covers ("DRAINCOVER"). Each component instance is mapped to the above TypeCode through the type field or section identification result; new components that are not yet supported can be initially classified as "OTHER" and added to the type dictionary by the designer. The component type dictionary is stored in the form of a configuration file or database table, recording the type code, name, applicable code number, typical geometric range, and default reinforcement layout mode, providing a foundation for the subsequent establishment of the host profile family.

[0076] 1.2 Establishment of Rebar Host Family: In this embodiment, each standard component type corresponds to a Rebar Host Family, which is essentially an abstraction of "the geometry of the concrete body and its reference system" and is used to define the three-dimensional spatial boundary of the rebar arrangement.

[0077] Precast T-beam Host_TBeam: In OpenRoads Designer, a parametric section consisting of a top plate, web, bottom plate, and diaphragms is drawn based on the standard cross-section at mid-span. A three-dimensional concrete solid is obtained by stretching along the beam length or sweeping along the route. The top plate tension zone reference surface, web centerline, bottom plate edge line, and diaphragm center surface are defined on the solid for reinforcement positioning. The geometric solid and its reference surfaces / lines, local coordinate systems, etc., are encapsulated into a host profile family Host_TBeam.

[0078] Precast small box girder Host_BoxGirder: Establish double-layer section lines of outer contour (top plate, bottom plate, outer web) and inner contour (box cavity); stretch to form a hollow box girder solid; set reinforcement layout reference surfaces on the inner surface of the top plate, the inner surface of the bottom plate, and the inner side of the web; encapsulate as a host contour family Host_BoxGirder.

[0079] Precast circular culvert Host_CircularCulvert: In the local coordinate system, establishes inner and outer circular sections with the culvert centerline as the axis, and the inner circle radius... outer circle radius ;Sweep along the culvert axis to generate a hollow cylinder;Define the center circle and path curve of the spiral reinforcement and longitudinal reinforcement between the inner and outer walls;Encapsulate as Host_CircularCulvert.

[0080] Precast cover plates and drainage ditch cover plates Host_SlabCover and Host_DrainCover: For rectangular plates or grooved sections, establish the cross-sectional profiles such as plate thickness, plate width, groove depth, and web thickness; stretch along the length of the component to obtain a plate-shaped or groove-shaped solid; set the top surface, bottom surface, side walls, etc. as reference surfaces for reinforcement layout; encapsulate as the corresponding host profile family.

[0081] In the data structure, each host profile family records at least: HostID, TypeCode, 3D geometric entity reference, key reference surface / reference line set, and default local coordinate system, thereby ensuring that the 3D coordinates of all subsequent reinforcement bars are within the geometric boundary and consistent with the concrete entity.

[0082] 1.3 Unified naming of host contour families and geometric variables: To support unified processing of multiple components, this embodiment adopts a unified naming rule for host contour families and their geometric variables: host contour family names are named in the format of "Host_ + type abbreviation", such as Host_TBeam, Host_CircularCulvert, etc.; geometric variables uniformly use English abbreviations and underscores, such as: L_total (total component length), H_beam (beam height), B_flange (flange width), T_top (top plate thickness), T_web (web plate thickness), D_inner (inner diameter), T_wall (wall thickness), L_seg (segment length), etc.; variables with the same physical meaning strictly reuse the same variable name in different host contour families, which facilitates the unified parameter set and general algorithm calls.

[0083] The system automatically verifies naming conventions when creating host profile families and variables to avoid branching judgments in subsequent rules and algorithms.

[0084] 1.4 Typical Reinforcement Category Identification and Host Binding: After completing the concrete ontology abstraction, this embodiment analyzes engineering drawings and experience databases to identify typical reinforcement categories for each component and establishes associations with the host profile family. For Host_ TBeam recognition: Top slab longitudinal reinforcement Rebar_TopLongitudinal; Web stirrups (including reinforced and regular zones) Rebar_WebStirrup; Support zone horseshoe reinforcement Rebar_HaunchBar. Identification of Host_CircularCulvert: Spiral reinforcement (Rebar_Spiral); Longitudinal reinforcement (Rebar_Longitudinal). For Host_BoxGirder, Host_ SlabCover, Host_DrainCover: Identify categories such as top slab main reinforcement, bottom slab main reinforcement, distribution reinforcement, stirrups, or web reinforcement. Each reinforcement category is stored as a "reinforcement category entity," containing RebarClassID, HostID, stress / structural role, placement direction, reference face / line, and suggested diameter and spacing range. There is a one-to-many relationship between the host profile family and the reinforcement categories: when a host profile family is instantiated, all its reinforcement categories are automatically loaded, forming a "reinforcement placement template" for that component type.

[0085] II. Design Variable Extraction and Construction of a Unified Component Parameter Set

[0086] 2.1 Classification Principles of Design Variables: In this embodiment, quantities that have a substantial impact on geometric shape, reinforcement layout, and code verification are defined as "design variables," and are limited to parameters that can be input by designers, passed in from upstream calculation programs, or derived by the system according to rules. Design variables are divided into two main categories: Geometric Parameters: describing component dimensions, cross-sectional shape, and spatial location; Rebar Parameters: describing rebar grade, diameter, spacing, protective layer, anchorage, and bending details, etc.

[0087] 2.2 Geometric Variables of Each Host Profile Family

[0088] The precast T-beam Host_TBeam has typical geometric variables including: L_total, H_beam, B_flange, T_top, T_web, N_web, S_web, B_bottom, T_bottom, S_diaph, etc., which are used to uniquely determine the T-beam cross section and the arrangement of the diaphragms.

[0089] The precast small box girder Host_BoxGirder has typical variables including: L_total, H_outer, T_top, T_bottom, T_web_outer, T_web_inner, B_cell, H_cell, S_diaph, etc., which are used to determine the box girder geometry and overall stiffness.

[0090] The prefabricated circular culvert Host_CircularCulvert typically includes variables such as D_inner, T_wall, L_seg, and optional parameters such as burial depth, angle between the axis and the route, which are used to determine the cross-section of the culvert and the length of each segment.

[0091] Precast cover plates and drainage ditch cover plates, including L_total, B_slab, T_slab, T_web, H_channel, etc., are used to determine the plate thickness and channel cross-section.

[0092] The aforementioned geometric variables record their names, physical meanings, and reference planes / lines in the host profile family entity, thus providing a basis for the positioning of geometric templates and reinforcing bars.

[0093] 2.3 Reinforcing bar parameter extraction and structured organization. The reinforcing bar parameters include at least: Reinforcing bar grade: SteelGrade; Reinforcing bar diameter: BarDiameter_*, such as BarDiameter_TopLong, BarDiameter_WebStirrup, BarDiameter_Spiral, etc.; Reinforcing bar spacing: BarSpacing_*, such as BarSpacing_TopLong, BarSpacing_Stirrup_Dense, BarSpacing_Stirrup_Normal, BarSpacing_Spiral; Cover thickness: CoverThickness_*, such as CoverThickness_Top, CoverThickness_Bottom, CoverThickness_Inner, CoverThickness_Outer; Anchorage and lap length: AnchorLength_*; Bending construction parameters: HookAngle, HookLength, BendRadius, etc.

[0094] A "Rebar Category" field, RebarClass, has been added to the parameters, such as Rebar_TopLongitudinal, Rebar_WebStirrup, and Rebar_Spiral, to facilitate filtering by category. Different parameter values ​​are used for the same type of rebar in different sections (e.g., the end reinforced zone and the middle regular zone), managed separately by splitting them into different parameter items.

[0095] 2.4 Unified Component Parameter Set and Attribute Labeling: All geometric variables and reinforcement parameters are uniformly stored in the "Unified Component Parameter Set," which can be implemented through a database table or a collection of in-memory objects. Each parameter entity must contain at least: ParamName, DisplayName, ParamType (Geometry / Rebar); HostFamily (to which the host profile family or Global), RebarClass (optional); Value, DefaultValue, Unit, ValueType, MinValue, MaxValue; and CodeClauseID, ConstraintType, etc., which are related to the specification.

[0096] The system explicitly labels each parameter with ParamType and HostFamily, and can automatically filter parameter subsets based on the host profile family when instantiating components; it also pre-fills relevant parameter clause numbers and allowed value ranges to provide basic data for rule base construction.

[0097] During the project instantiation phase: After the designer selects the component type, the system filters the applicable geometric variables and reinforcement parameters for the component from a unified parameter set by HostFamily, and adds a common parameter with Scope = Global; the filtering results are copied as the parameter set of the component instance, with initial values ​​from default values ​​or upstream structural calculation results; the designer modifies the parameter values ​​in the interface, and the system writes them back in real time and verifies the validity of the data.

[0098] The geometric modeling module, the reinforcement layout module, and the specification verification module all access the above parameter set through a unified interface to ensure consistent data sources and avoid contradictions caused by multiple data entries.

[0099] III. Parameter Data Structure and Canonical Mapping

[0100] 3.1 Entity Data Model Structure: This embodiment adopts EC Schema or equivalent entity model to unify the modeling of "host profile family - parameters - code rules". Core entities include: rebar host profile family entity ECClass_RebarHostFamily; geometric parameter entity ECClass_GeometryParam; rebar parameter entity ECClass_RebarParam; and code rule entity ECClass_CodeRule.

[0101] Entities are connected through association classes: ECRel_HostHasParam: host profile family - parameter; ECRel_HostUsesRule: host profile family - rule; ECRel_RuleAffectsParam: rule - parameter.

[0102] By traversing these associations, the parameter set and rule set of any host profile family can be automatically obtained.

[0103] 3.2 Mapping of Standard Clauses and Parameters: For the mandatory clauses in standards such as JTG 3362-2018 and JTG / T 3650-2020, this embodiment extracts the clauses and establishes the correspondence between the clauses and parameters. The key points include: clear spacing of main reinforcement bars, spacing of stirrups; thickness of protective layer; anchorage length, lap length; bending structure and hook length; special structural requirements (additional reinforcement in the support area, etc.).

[0104] For each clause:

[0105] 1. Identify the physical quantities appearing in the clauses and map them to GeometryParam or RebarParam in the unified parameter set (e.g., "net Spacing_MainBar" for "main reinforcement clear distance").

[0106] 2. Enter the corresponding CodeClauseID in the parameter entity;

[0107] 3. If a fixed lower / upper limit exists, enter AllowedMin / AllowedMax and set CheckMode;

[0108] 4. If it is a combined inequality (such as "not less than its diameter, and not less than 25mm"), retain the clause number in the parameter layer and give the specific function expression in the rule layer.

[0109] In this way, the parameter set naturally carries the mapping relationship between "parameters and clauses", and the rule base only needs to build executable rules based on these mappings.

[0110] 3.3 Specification Rule Entities and Execution: Each specification constraint, spatial layout, or parameter linkage relationship corresponds to a rule record in the CodeRule entity, including: RuleID, RuleName, RuleType (CodeConstraint / SpatialLayout / ParamLinkage); CodeClauseID (required for CodeConstraint); ExpressionType and Expression (stores DSL formulas or expression trees); TargetHosts and TargetParams (applicable host profile families and parameter name lists); and optional EnvFilter, CodeVersion, Severity, MessageTemplate, etc.

[0111] When a rule is executed, the rule engine retrieves values ​​from a unified parameter set according to TargetParams, binds them to expression variables, evaluates them, and obtains Boolean results and intermediate calculated values. If a rule is not met, a violation record is generated and used for highlighting and report export.

[0112] IV. Geometry Template Creation and Parameter Binding

[0113] 4.1 Geometric Template Modeling Principles: In this embodiment, a geometric template is created for each host contour family within the 3D design platform. The geometric template uses a local coordinate system as a reference and forms a concrete solid through a 2D parametric section sketch and 3D extrusion / sweep. All key dimensions are driven by geometric variables from a unified parameter set.

[0114] Design goal: Given a set of geometric variables, the concrete geometry of the component can be uniquely determined; when the geometric variables change, the Geometry API is called to automatically recalculate the constraints and complete the solid reconstruction without manual modification of the graphics.

[0115] 4.2 Example of T-beam geometric template

[0116] Taking Host_TBeam as an example: Define a local coordinate system O–X–Y–Z at the mid-span (X along the beam length, Y along the transverse direction, Z vertically upward), and establish reference planes such as the cross section, top plate, bottom plate, and web centerline;

[0117] Create a cross-sectional sketch Sketch_TBeam on the cross-sectional plane, draw the bottom plate, web, and flange contours, and bind all dimensional constraints (such as B_bottom, T_bottom, T_web, B_flange, T_top, H_beam) to a unified parameter set using the expression Param["..."].

[0118] Stretch the cross section along the X direction to form a beam; calculate the position of the transverse diaphragm according to S_diaph, stretch it to form a transverse diaphragm and combine it with the beam;

[0119] The reference surface of the tension zone of the top plate, the neutral axis of the web, and the outline of the horseshoe zone are predefined in the geometric template for subsequent reinforcement positioning.

[0120] 4.3 Example of a circular culvert geometry template: For Host_CircularCulvert: Generate a spatial curve Axis_Culvert based on the culvert design axis, and define a cross-sectional plane along the axis; create a circular sketch Sketch_Circle on the cross-sectional plane, where the inner circle radius D_inner / 2 and the outer circle radius D_inner / 2 + T_wall are both controlled by parameters; define the radii of the spiral reinforcement and longitudinal reinforcement centers between the inner and outer circles, for example... Sweep the cross-section sketch along the length L_seg of Axis_Culvert or the total length of multiple sections to generate a three-dimensional hollow cylinder, and reserve a joint reference plane on the end face of the segment.

[0121] 4.4 Parameter Binding and Linkage: In the Parameter API, a parameter object is created for each geometric variable, and a binding relationship is established with the geometric constraints. For example, the expression for the section height constraint is Param["H_beam"]; the pipe inner diameter constraint is Param["D_inner"].

[0122] When designers modify parameters, the Parameter API updates the unified parameter set, the Geometry API resolves the sketch constraints and reconstructs the solid, and simultaneously updates the positions of reference faces / lines in the host profile family. The linkage between geometric variables and reinforcement parameters (such as "the number of stirrups increases when the beam height increases") is not written to the geometry template, but is stored in the rule base as ParamLinkage rules, for example:

[0123] ;

[0124] When H_beam, L_total, etc. change, the linkage rules are first executed to calculate derived parameters such as L_dense and N_stirrup, and then the rebar layout algorithm and 3D model are updated.

[0125] V. Reinforcement Layout Algorithm Based on Rule Base

[0126] 5.1 Overall Approach: The rebar layout logic is driven by a rule base, rather than being hard-coded in the program. For each component instance, the system selects the following rules from the rule base based on HostID and RebarClassID: SpatialLayout: calculates the three-dimensional coordinates of the rebar; ParamLinkage: calculates derived parameters (such as quantity and length); CodeConstraint: can be used to preset lower limits, spacing, etc. before layout.

[0127] The process is as follows: Read parameters → Execute linkage rules → Generate rebar coordinates according to spatial positioning rules → Write rebar entity.

[0128] 5.2 Example of longitudinal reinforcement spatial positioning, taking Rebar_TopLongitudinal as an example, the relevant parameters include L_total, B_flange, CoverThickness_Top, BarDiameter_TopLong, BarSpacing_TopLong, N_topLong, etc. Beam length direction: The x-coordinates of the start and end points of the longitudinal reinforcement are respectively... The anchorage length is calculated according to the anchorage rules.

[0129] Lateral flange: Starting point of tension edge stiffener ;

[0130] When simplifying the uniform arrangement, the first Transverse coordinates of the longitudinal reinforcement: ;

[0131] Vertical elevation: ;

[0132] Final The three-dimensional coordinates of the start and end points of the longitudinal reinforcement are respectively and .

[0133] 5.3 Example of stirrup spatial positioning: For the web stirrups Rebar_WebStirrup, the beam length is divided into an end-reinforced zone and a middle regular zone. The typical linkage rule is as follows: Number of stirrups in the single-end reinforced zone: Number of stirrups in the middle: The total quantity is .

[0134] The position of the center of each stirrup in the X direction is calculated recursively based on the spacing of the reinforced zone and the regular zone. Within the cross section, the center line of the closed rectangle is determined according to the flange width, beam height, slab thickness and protective layer thickness, and the three-dimensional stirrup curve is obtained by translating along the X direction.

[0135] 5.4 Example of spatial positioning of spiral reinforcement, for spiral reinforcement of circular culvert Rebar_Spiral: number of derived turns: ;

[0136] Radius of the center circle: ;

[0137] In the local linear coordinate system (X along the tube axis), the parametric equation of the helix is: ;

[0138] Discrete parameters A series of points are obtained and a three-dimensional curve of the spiral reinforcement is generated. For the curve axis, a local coordinate system can be established on the axis to map the (y,z) coordinates to each section.

[0139] VI. Algorithmic Representation and Rule-by-Rule Verification of Normative Constraints

[0140] 6.1 Constraint Types and Abstractions. Common specification constraints include: numerical upper and lower limits, such as the lower limit of the clear spacing of main reinforcement bars, the minimum thickness of the protective layer, and the maximum spacing of stirrups; combined inequalities, such as "the clear spacing of main reinforcement bars shall not be less than its diameter and shall not be less than 25mm"; functional constraints, such as the changes in anchorage length and lap length with the grade, diameter, and stress state of the reinforcement bars; and logical constraints, such as the combined requirements of hook angle and hook length.

[0141] In this embodiment, each clause is abstracted into at least one CodeRule, whose expression evaluation result is "pass / fail".

[0142] 6.2 Typical Normative Constraint Expression

[0143] Main reinforcement clear spacing constraint, parameters involved: NetSpacing_MainBar, BarDiameter_MainBar. The rule expression is: ;

[0144] Protective layer thickness constraint, parameters: CoverThickness_Top, EnvClass. The rule expression is: ;in Obtained by looking up the environmental category in the table.

[0145] Anchoring length constraint, parameters: AnchorLength_MainBar, SteelGrade_MainBar, BarDiameter_MainBar, StressState. The rule expression is:

[0146] ;

[0147] The bending construction constraint involves the following parameters: HookAngle, HookLength, and BarDiameter. Example expression: ;

[0148] 6.3 Item-by-item verification process: After the 3D model of the reinforcing bars is generated or updated, the specification verification module performs the following steps: ① Determine the HostID and RebarClassID of the reinforcing bars; ② Use ECRel_HostUsesRule to select a subset of CodeConstraint type rules applicable to the current component from the rule base; ③ For each rule, obtain the participating parameter name through ECRel_RuleAffectsParam and read the current value from the unified parameter set; ④ Bind the parameter value to the rule expression for evaluation to obtain the pass / fail result; ⑤ For failed rules, generate a violation record, recording the rule number, clause number, current value and allowed value, and generate a prompt message based on MessageTemplate; ⑥ Highlight the violating reinforcing bars in the 3D interface and use different colors according to the severity; ⑦ Support exporting verification reports, classifying and summarizing violation records by component, rule or clause, which can be used as the basis for model submission and review.

[0149] VII. Automatic selection of rule subsets based on entity association

[0150] 7.1 Automatic Rule Subset Selection Algorithm: When instantiating a component type (e.g., a T-beam), the system automatically selects an applicable rule subset based on entity relationships: It locates the host contour family entity Host_TBeam based on the TypeCode and obtains its HostID; it searches for records in ECRel_HostUsesRule where HostID = Host_TBeam to obtain the applicable rule set {Rule_i}; it filters the set by RuleType according to the application scenario (reinforcement layout or specification verification) to obtain the required SpatialLayout, ParamLinkage, or CodeConstraint subsets; and it combines the CodeVersion, Active, and Priority fields to handle the priority of specification versions and enterprise standards. The entire process does not rely on hard-coded condition judgments but entirely on entity relationships.

[0151] 7.2 Parameter subset binding with rules: For each selected rule Rule_i: the set of parameter IDs that the rule applies to is obtained through ECRel_RuleAffectsParam; then, the geometric parameters and rebar parameters that belong to the current HostID are filtered out through ECRel_HostHasParam; forming a binding structure of "RuleID–TargetParams–HostID", which is used by the rule engine to directly retrieve values ​​from the unified parameter set by name.

[0152] In this way, the rule engine only needs to retrieve values ​​according to the binding structure and execute the expression, without having to explicitly specify "which parameters this rule uses" in the code.

[0153] 7.3 Unified Invocation and Extension in Different Processes: The automatic selection mechanism based on entity association is used in multiple processes: When a component instance is created: Load all rule subsets of the component type and execute the linkage rules to calculate the initial derived parameters; When parameters are modified: Select relevant rules to re-evaluate and update the reinforcement layout and verification results based on the HostID and the modified parameter; When performing batch verification: Group by component type and share rule subsets and parameter selection logic for components with the same HostID to improve efficiency.

[0154] When adding a new component type or a new specification clause, it is only necessary to: add the corresponding host profile family entity and its parameters; add a rule entry in CodeRule and specify the applicable host profile family and parameters through the association relationship; the main algorithm still follows the unified process of "look up the rule based on HostID - look up the parameter based on RuleID - evaluate", so as to achieve non-intrusive extension of new components and new rules.

[0155] Through the above embodiments, this invention, supported by a unified parameter set, entity data model, and rule base, achieves parametric modeling of reinforcement bars for various types of precast components in highways. The geometric template and reinforcement layout are driven by the same parameter system, and standard clauses are transformed into executable rules and automatically verified during the modeling process. This improves modeling efficiency, ensures compliance with reinforcement specifications, and facilitates expansion and maintenance.

[0156] Example 2: Reference Figures 1-15A parametric modeling system for reinforcing steel bars in precast highway components is deployed on a highway professional 3D design platform (such as Bentley OpenRoads Designer or an equivalent platform) and runs as a plug-in or integrated module. Through the collaboration of several functional modules, the system achieves parametric modeling of reinforcing steel bars in various precast highway components, automatic specification verification, and export of cutting data. The system generally includes: a host profile family definition module, a parameter and specification mapping module, a parametric modeling module, an automatic specification verification module, and a cutting length calculation and data export module. All of these modules can be executed by software program instructions on a general-purpose server or engineer's workstation, or they can be divided into multiple sub-modules or implemented in the same program unit as needed.

[0157] I. Host Profile Family Definition Module

[0158] 1. Overall Module Functions: The Host Profile Family Definition module runs within the 3D design platform and is responsible for: identifying and classifying the types of precast highway components; abstracting the concrete geometry of various components into steel reinforcement host profile families; extracting design variables reflecting the geometric shape and steel reinforcement layout characteristics from each steel reinforcement host profile family to form basic parameters in a unified component parameter set; uniformly managing the naming rules for host profile families and geometric variables; identifying typical steel reinforcement categories in each component and associating them with host profile families using category identifiers. Through this module, the system can establish a unified "host geometry + parameters + steel reinforcement category" abstraction for various precast components, providing a structured foundation for subsequent parametric modeling and specification verification.

[0159] 2. Component classification and establishment of reinforcement host profile families

[0160] The host profile family definition module pre-sets a component type dictionary, classifying commonly used prefabricated components in highway engineering into: prefabricated T-beams; prefabricated small box girders; prefabricated circular culverts; prefabricated cover plates and cover plate covering plates; prefabricated drainage ditch cover plates, etc.

[0161] The system categorizes each component instance into the aforementioned standard component types based on the component type field, cross-sectional form, or component family name in the design file, and then creates a corresponding reinforcement host profile family for each. For precast T-beams, The host profile family is a three-dimensional concrete shape and its local coordinate system consisting of a top plate, a web plate, a bottom plate, and transverse diaphragms. For precast small box girders, The host profile family is a hollow beam solid composed of a box-shaped outer profile and a cavity inner profile. For precast circular culverts, The host profile family consists of hollow cylinders with annular cross-sections formed by sweeping along the tube axis. For precast cover plates and drainage ditch covers, The host profile family consists of plate-shaped or trough-shaped concrete entities.

[0162] Each rebar host profile family entity record includes: profile family identifier (HostID), corresponding component type, 3D geometric entity reference, key reference surfaces and reference lines, and host local coordinate system. This information is used to constrain the spatial boundaries of the rebar arrangement.

[0163] 3. Unified naming rules and variable classification: To support unified management of multiple components, the host profile family definition module has built-in unified profile family naming rules and geometric variable naming rules: Host profile family names use a unified prefix "Host_" followed by a type abbreviation, such as Host_TBeam, Host_BoxGirder, Host_CircularCulvert, etc.; Geometric variables in the host profile families of steel reinforcement for different precast components use standardized names, such as: Component total length: L_total; Beam height / component height: H_beam or H_outer; Web thickness: T_web; Flange width: B_flange; Pipe diameter (inner diameter): D_inner; Wall thickness: T_wall, etc.

[0164] The module will divide the design variables extracted from each rebar host profile family into two main categories: Geometric variables: It includes at least one or more of the following: total length of the component, beam height, web thickness, flange width, pipe diameter, and wall thickness, used to determine the geometry of the concrete body and the range of space where the reinforcing steel can be arranged; Reinforcing bar parameters: It includes at least one or more of the following: steel bar grade, steel bar diameter, steel bar spacing, protective layer thickness, anchorage length, and hook angle, used to control the specifications and arrangement of steel bars.

[0165] When constructing a unified set of component parameters, the host profile family definition module explicitly labels each variable with: the host profile family identifier of the rebar (e.g., Host_TBeam, Host_CircularCulvert); and the variable type (geometric variable / rebar parameter).

[0166] In this way, the system can adopt unified parameter naming and classification rules across multiple component types, and automatically select the applicable parameter subset based on the host contour family in subsequent algorithms, thereby achieving unified parameter management and automatic selection of rebar layout mode.

[0167] 4. Typical Reinforcement Category Identification and Association: The host profile family definition module further analyzes the geometric characteristics and inherent rules of reinforcement arrangement for each type of reinforcement host profile family, identifies typical reinforcement categories, and establishes associations with the host profile families. For example, for the precast T-beam host profile family, it identifies: longitudinal reinforcing bars in the top slab, stirrups in the web (including end reinforcement and middle conventional reinforcement), and horseshoe reinforcement in the support area. For the precast circular culvert host profile family, it identifies: spiral reinforcement and longitudinal reinforcement. The module assigns category identifiers (such as Rebar_TopLongitudinal, Rebar_WebStirrup, Rebar_HaunchBar, Rebar_Spiral, Rebar_Longitudinal) to the above typical reinforcement categories and binds the category identifiers to the corresponding host profile families through data tables or entity association relationships. In this way, when the system models the reinforcement of a host profile family instance, it can automatically load the associated reinforcement category templates and then automatically select the appropriate reinforcement arrangement mode.

[0168] II. Parameter and Specification Mapping Module

[0169] 1. Overall module function: The parameter and specification mapping module is used to: establish a parameter data structure for a unified set of component parameters based on the entity data model; associate the geometric variables and reinforcement parameters in the unified set of component parameters with the mandatory constraint parameters in the design and construction specifications of highway bridges and culverts; express the constraint clauses in the specifications as specification verification rules corresponding to the parameter data structure, forming a specification verification rule library; and record the parameter range of the rule entries and the applicability relationship between the rule entries and the host contour family through the relationship between entities, providing a basis for the automatic selection of rule subsets for the automatic specification verification module.

[0170] 2. The correlation between parameters and mandatory specification parameters: The parameter-specification mapping module first analyzes the unified component parameter set and identifies parameters that need to be subject to mandatory specification constraints. These parameters mainly include: parameters related to the lower limit of the clear spacing of reinforcing bars, such as the clear spacing of main reinforcing bars and the spacing of stirrups; parameters related to the lower limit of the thickness of the concrete cover, such as the concrete cover of the tension zone of the top slab, the concrete cover of the tension zone of the bottom slab, and the inner and outer concrete covers of pipes; parameters related to the lower limit of the anchorage length of reinforcing bars, such as the anchorage length of main reinforcing bars and the lap length; and parameters related to the bending structure of reinforcing bars, such as the hook angle, hook length, and bending radius.

[0171] The module maps the above parameters to the corresponding clauses in the specification one by one, and records the following for each variable in the parameter data structure: the corresponding specification clause number (CodeClauseID); the allowed value range given by the specification (AllowedMin, AllowedMax, or interval), and for functional constraints, the calculation method identifier; and the constraint type (lower limit only, upper limit only, upper and lower limits, combined inequalities, etc.).

[0172] Through this mapping, the unified component parameter set not only includes the engineering meaning and value range of the parameters, but also explicitly carries the relationship between the parameters and the standard provisions, providing a direct data source for the subsequent construction of the standard verification rule base.

[0173] 3. Entity Data Model (EC Schema) and Rule Entity Mapping: The parameter and specification mapping module uses EC Schema or an equivalent entity data model, defining the following entity classes at the data level:

[0174] Reinforcement host profile family entity: records host profile family identifier, component type, geometric template reference, etc.;

[0175] Geometric variable entity: Records the geometric variable name, unit, default value, host contour family, corresponding specification clause number, and allowed value range, etc.;

[0176] Reinforcement parameter entity: Records the reinforcement parameter name, its host profile family and reinforcement category, unit, default value, corresponding code clause number and allowed value range, etc.

[0177] Standard validation rule entry entity: records rule number, rule type (standard constraint, parameter linkage, spatial layout), corresponding standard clause number, expression, applicable parameters, and host profile family, etc.

[0178] Based on this, the module records the relationships between entities:

[0179] "Which geometric variables and reinforcement parameters does a certain rule entry apply to?": By defining the association class between the rule entry entity and the parameter entity, it is clear which parameter values ​​need to be read for verification or calculation for each rule;

[0180] "Which rule entries should be used for a certain steel reinforcement host profile family": By defining the association relationship between the host profile family entity and the rule entry entity, the rule subset applicable to different component types is clarified.

[0181] When the automatic verification module performs reinforcement modeling or standard verification on a precast component, it only needs to automatically traverse the set of rule entries and the set of parameters corresponding to the rule entries from the entity data model according to the host contour family corresponding to the component. This establishes a mapping relationship of "current component - applicable rule subset - required parameter subset", realizing the association storage and unified calling of parameter data structure and rule base.

[0182] III. Parametric Modeling Module

[0183] 3.1 Module Positioning and Input / Output: The parametric modeling module resides within the 3D design platform, serving as the core execution unit connecting the "host contour family + unified component parameter set + standard verification rule base". Its main inputs include:

[0184] The host profile family definition module outputs: host profile family identifier HostID; geometry template reference GeometryTemplateRef; list of identified rebar classes RebarClassList; and the geometry variables and rebar parameters of the current component instance in the unified component parameter set.

[0185] The parameter and specification mapping module provides: parameter linkage rules (RuleType=ParamLinkage) associated with the current host contour family in the rule base; and rebar spatial layout rules (RuleType=SpatialLayout).

[0186] The module outputs: the updated host concrete 3D geometric entity; the corresponding 3D model of the reinforcing steel (3D reinforcing steel members grouped by steel type); and the parameter attributes attached to each reinforcing steel entity (diameter, spacing, anchorage length, member to which it belongs, rule to which it belongs, etc.), for subsequent specification verification and material cutting calculation.

[0187] 3.2 Geometric Template Loading and Parameter Binding Process

[0188] (1) Template loading: When the user selects "Insert prefabricated component" in the project or edits the parameters of an existing component, the parametric modeling module first loads the geometric template object corresponding to the HostID from the geometric template library according to the component type and HostID. The template object stores geometric construction information such as cross-section sketch, stretch / sweep path, and diaphragm arrangement.

[0189] (2) Parameter binding: The module binds the geometric variables in the unified component parameter set to the dimensional constraints in the geometric template one by one through the Parameter API provided by the 3D platform.

[0190] For named dimensions in the section sketch (such as d_H_beam, d_B_flange, d_T_web), establish expression bindings: d_H_beam.Expression = Param["H_beam"]; d_B_flange.Expression = Param["B_flange"], etc.

[0191] For stretch / sweep lengths (such as L_total, L_seg), bind to the path length parameter;

[0192] The spacing of repetitive components such as diaphragms and pipe sections is bound to variables such as S_diaph and L_seg.

[0193] When a geometric variable in the parameter set is updated, the Parameter API triggers the template to be resolved, the cross-section sketch recalculates the node coordinates, and then the 3D solid is automatically reconstructed.

[0194] 3.3 Reinforcement parameter calculation driven by parameter linkage rules: After the geometric template is updated, the parametric modeling module calls the rule entry with RuleType set to ParamLinkage from the rule base. A typical process is as follows:

[0195] Starting from the current HostID in the entity data model, obtain the complete set of applicable ParamLinkage rules through the "host profile family - rule entry" relationship;

[0196] The rule expressions are executed according to the dependency order between rules (e.g., calculate the length of the encrypted area first, then calculate the number of stirrups), and the geometric variables and rebar parameters referenced in the corresponding expressions are all read from a unified parameter set;

[0197] The derived parameters obtained (such as L_dense, N_stirrup, N_topLong, N_spiral, etc.) are written back to the unified component parameter set.

[0198] After execution, the steel reinforcement parameters in the unified component parameter set reflect the quantity and arrangement section information of steel reinforcement under the current geometric conditions and in accordance with the predetermined arrangement logic, thus preparing for the execution of spatial positioning rules.

[0199] 3.4 Spatial positioning and 3D solid generation of reinforcing bars: The parametric modeling module then calls the rule entry with RuleType set to SpatialLayout to calculate the 3D layout coordinates for each type of reinforcing bar. Specifically, this includes:

[0200] Longitudinal reinforcement arrangement: Calculate the start and end x coordinates of the longitudinal reinforcement based on L_total and anchorage length parameters; calculate the y coordinate of each longitudinal reinforcement based on B_flange, protective layer thickness, longitudinal reinforcement spacing or piecewise function of densified / normal section; calculate the z coordinate based on beam height and top / bottom protective layer thickness; finally form the three-dimensional coordinate pair of the start and end points of each longitudinal reinforcement, and generate a straight or bent three-dimensional steel reinforcement entity according to design requirements.

[0201] Stirrup arrangement: Based on the length of the end reinforcement zone, the length of the regular zone, and the spacing parameters calculated according to the linkage rules, determine the center position of each stirrup along the beam length direction; calculate the rectangular outline of the stirrup core on the cross-sectional plane according to the web position, plate thickness, and protective layer thickness; copy the cross-sectional outline at each center position to form a closed three-dimensional reinforcement curve.

[0202] Arrangement of spiral reinforcement and longitudinal reinforcement (circular pipe culvert): Using the parametric equation of the spiral line, the discrete points of the spiral reinforcement are calculated with D_inner, T_wall, protective layer thickness, and pitch as independent variables; combined with the local coordinate system of the pipe axis, the spiral line points are mapped to space to generate the three-dimensional curve of the spiral reinforcement; the longitudinal reinforcement is arranged along the pipe axis at equal angles or equal intervals, and the cross-sectional position is determined according to the radius of the reinforcement center circle.

[0203] Other types of reinforcement: For the main reinforcement of the cover plate, distribution reinforcement, and main reinforcement of the top and bottom slabs of the small box girder, the coordinates are calculated and the three-dimensional reinforcement entity is generated in a similar manner.

[0204] When generating 3D steel reinforcement entities, the module adds attribute fields to each steel reinforcement object: HostID, RebarClassID, diameter, spacing, length, version number of the parameter to which it belongs, and key parameter values ​​involved in the layout, etc., to provide a basis for specification verification and material cutting calculation.

[0205] 3.5 Interactive Update and Incremental Reconstruction Mechanism: When designers modify component parameters on the 3D platform interface (e.g., change beam height, length of the reinforced zone, thickness of the protective layer): The parametric modeling module listens for parameter change events, first updates the corresponding parameter values ​​in the unified component parameter set; calls the geometric template reconstruction process to update the concrete entity shape; calls the ParamLinkage rule to recalculate the affected reinforcement parameters (e.g., number of stirrups, number of spiral turns, etc.); executes the SpatialLayout rule on the affected reinforcement categories to update the 3D geometry of the corresponding reinforcement entity (preferably only recalculating the affected area to improve efficiency); and notifies the automatic code verification module to perform immediate or delayed code verification on the updated reinforcement.

[0206] Through the above process, the parametric modeling module realizes fully automatic or semi-automatic rebar model reconstruction driven by a unified parameter set, adapting to the batch adjustment needs of component size and reinforcement scheme.

[0207] IV. Standardize the automatic verification module

[0208] 4.1 Module Responsibilities and Timing: The automatic specification verification module is primarily responsible for converting specification clauses into a rule base and performing compliance checks at various critical moments during the generation or updating of the reinforcement model. Its triggering methods include: automatically performing a full component check after the initial reinforcement generation of a new component; performing a partial check on the affected area after designers modify key parameters and complete reinforcement recalculation; and performing a complete check and generating a check report before the model is submitted for review and before material export.

[0209] 4.2 Parameter and Measured Value Acquisition: Before verification, the module first acquires the parameters and necessary measured geometric quantities of the current component:

[0210] Read the geometric variables and reinforcement parameters related to the specifications from the unified component parameter set, such as: design clear spacing of main reinforcement, design protective layer thickness, design anchorage length, design angle of hook, etc.

[0211] For situations requiring verification using three-dimensional geometric measurements (e.g., actual clear distance, actual protective layer thickness): Calculate the distance from the core of the reinforcing bar to the outer surface of the concrete based on the spatial relationship between the reinforcing bar entity and the host concrete surface using the geometric calculation API of the three-dimensional design platform; measure the distance between the cores of adjacent reinforcing bars on the same cross section to obtain the actual clear distance; calculate the actual bending angle and hook length of the bent reinforcing bar.

[0212] The measured values ​​and the design values ​​in the parameter set can be used simultaneously to evaluate the rule expression, ensuring that the verification results reflect both whether the parameter configuration is standardized and the actual geometric state of the three-dimensional entity.

[0213] 4.3 Automatic selection of applicable rule subsets: The automatic verification module does not hardcode "which clauses apply to a certain component" in the code, but automatically selects the applicable rule subset through the association relationship in the entity data model: the applicable rule set is obtained from the "host profile family - rule entry" relationship based on the HostID to which the rebar belongs; if the verification is grouped by rebar category, the rules are further filtered based on the RebarClassID of the rebar entity record and the applicable category in the rule entry; old or backup rules that should not be effective are filtered out by combining the code version (CodeVersion), rule activation status (Active) and priority (Priority); finally, a "list of rules to be executed" for the current component or the current rebar category is formed.

[0214] 4.4 Rule evaluation and violation record generation: For the selected rule list, the automatic verification module evaluates and records the results for each rule: For each rule, the TargetParams list is read from the rule entry entity;

[0215] Retrieve the corresponding value from the unified component parameter set and the measured value cache according to the parameter name;

[0216] Bind parameter values ​​to variables in the regular expression and call the expression evaluation engine to calculate;

[0217] If the expression result is "satisfied", then record that the rule has been passed, and optionally perform a pass count;

[0218] If the expression result is "not satisfied," indicating a violation of the corresponding specification clause, a violation record is generated. The record includes: the identifier of the violating steel reinforcement component (e.g., reinforcement ID, component name, location description); rule number RuleID, corresponding specification clause number CodeClauseID; the names of the parameters involved in the verification and their current values; the allowed values ​​calculated based on the expression (e.g., RequiredMin, RequiredMax); the violation type and severity (Error / Warning); and the Chinese prompt text formatted by MessageTemplate.

[0219] Violation records are uniformly stored in the "Standard Verification Result Table" and a reference relationship is established with the engineering model to support subsequent highlighting and report export.

[0220] 4.5 Graphical Highlighting and Interactive Prompts: The automatic verification module for standards uses violation records to visually identify relevant reinforcing bars in the 3D design platform. For violations of mandatory clauses (Error), the reinforcing bar entity is rendered as a highlighted red and displayed first in the model view. For violations of recommended clauses or internal control clauses (Warning), yellow or other colors can be used for differentiation. When a user selects a violating reinforcing bar, the system displays detailed violation information in the attribute panel or pop-up window, including the clause number, current value, allowed value, and modification suggestions. It supports filtering and displaying violating components in the view by component, clause, or rule type, facilitating designers to handle each violation individually.

[0221] 4.6 Verification Strategy and Process Control: The automatic verification module can be configured with different process strategies according to project needs. Forced passage strategy: If an Error-level violation exists, exporting material cutting data or submitting it for review is prohibited. Designers are required to adjust the parameters and re-verify them. Early warning strategy: Exporting and submitting are permitted when a Warning-level violation exists, but it must be clearly identified in the verification report for the reviewer's decision-making. Incremental verification strategy:When only some parameters change, only the affected steel reinforcement sections or components are locally checked, improving calculation efficiency. Through this mechanism, the automatic verification module effectively embeds the code provisions into the parametric modeling process, achieving integrated design and verification without changing the designers' work habits.

[0222] V. Material Cutting Length Calculation and Data Export Module

[0223] 5.1 Module Location and Input / Output: The module for calculating cutting length and exporting data is located at the end of the modeling process. Its prerequisite is that the relevant reinforcing bars have passed the constraint check of the automatic specification verification module (at least no Error-level violations). Its main inputs include: a 3D model of the reinforcing bars (containing the 3D geometry and additional attributes of each reinforcing bar); host profile family information (used to determine the component and location to which the reinforcing bars belong); and parameters related to cutting from the unified component parameter set (such as hook construction coefficients and optional bending adjustment values).

[0224] The output includes: the cutting length of each rebar; a summary statistical table by category, diameter, length, etc.; and a rebar cutting list and rebar summary table generated in tabular or structured data file format.

[0225] 5.2 Reinforcing bar geometry path extraction and length calculation: For each reinforcing bar entity, the cutting length calculation process includes:

[0226] For straight or polygonal reinforcing bars, the vertex sequence (P0, P1, …, Pn) of the reinforcing bar centerline is extracted; for curved reinforcing bars (such as spiral bars and circular arc bends), the platform's geometry API is called to obtain their parametric curve representation or discretize them into multiple straight lines with sufficient precision.

[0227] Length calculation, fold the line segment, according to ; Calculate the total length; For circular arc segments or spiral segments, the length can be directly integrated according to the parametric expression, or the accurate value can be obtained by using the "curve length" function provided by the platform; For steel bars with hooks or bends, the length of the hook part is also added to the total length by using the curve length function or by converting it according to the specifications (e.g., 10d, 12d).

[0228] Optional bending adjustment: If bending adjustment values ​​during processing need to be considered, the module can be configured with a "bending coefficient table" according to specifications or enterprise standards to correct the length of the bending part; the corrected length can be recorded separately as the "processing blanking length" field.

[0229] The final calculation results are attached to the cutting record of each steel bar in the form of fields such as "theoretical length" and "processing length".

[0230] 5.3 Reinforcement Grouping and Statistical Logic: After calculating the length of each reinforcement bar, the module groups and summarizes the reinforcement bars. Common grouping dimensions include: reinforcement diameter, reinforcement type (top slab longitudinal reinforcement, web stirrups, spiral reinforcement, etc.), component number, span number, hole number, pouring section or construction section, and length range (optional).

[0231] The statistical process includes: clustering the rebar records by grouping key, such as (component number + rebar diameter + rebar shape); counting the number of rebars, total length, and single length under each group; marking rebars of completely equal length and the same specifications as "batch processing" groups; saving the statistical results as a "rebar statistics result table" and establishing a one-to-many relationship with the original rebar records to facilitate tracing the specific rebar corresponding to each statistical item.

[0232] 5.4 Data Export Format and Field Design: To meet the needs of processing plants and construction units, the material cutting length calculation and data export module supports multiple export formats:

[0233] Spreadsheet files (such as Excel): Each row corresponds to a combination of rebar specifications or a single rebar (configurable); commonly used fields include: component number, location (span number, mileage), rebar type, diameter, single length, number of bars, total length, rebar shape code, hook type, remarks, etc.; "Violation Explanation" and "Remarks" columns can be added to the same file to highlight precautions in design and processing.

[0234] Structured data files (such as CSV, XML, JSON): suitable for integration with enterprise MES, ERP or CNC equipment systems for steel bar processing; field content is consistent with tabular files, and the format is machine-parseable structured data; optional simplified information of the three-dimensional geometry of the steel bars (such as coordinate sequences or shape template numbers) can be included to support visual verification.

[0235] Reinforcement Summary Report: This report summarizes the reinforcement usage of all precast components at the project level; it also calculates the total weight and length by component type, diameter, and category, providing a basis for material planning and cost control.

[0236] 5.5 Association with Specification Verification Results and Host Information: During the export process, the module will also associate the reinforcing bars with the following information: host profile family and component number (to facilitate on-site processing and binding according to components); specification verification result summary (e.g., whether there are warning level prompts related to this component); version number or revision number (reflecting which parameter adjustment model this cutting list corresponds to).

[0237] Through the above-mentioned correlation, the construction unit can track the design status corresponding to each batch of material cutting data, reducing on-site rework caused by version errors or omissions.

[0238] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for parametric modeling of reinforcing steel bars in precast highway components, characterized in that, The specific steps include the following: In the 3D design platform, the precast components of highways are classified according to their structural characteristics, abstracted into a family of steel reinforcement host contours, and parameters reflecting the geometry of the components and the arrangement of steel reinforcement are extracted to form a unified set of component parameters. Based on the entity data model, a parameter data structure is established for the component parameter set, and according to the relevant highway bridge and culvert specifications, the binding clauses in the specifications are expressed as specification verification rules corresponding to the parameter data structure, thus forming a specification verification rule library; In the 3D design platform, a parametric geometric template is established based on the rebar host contour family. The key dimensions in the geometric template are bound to the unified component parameter set, and the rebar layout algorithm is called to generate the 3D model of the rebar of the prefabricated component. During the generation or updating of the 3D model of the reinforcing steel, the standard verification rule library is called based on the current component parameters to perform standard verification on key reinforcing steel parameters, and the verification results are used to prompt or control the 3D model of the reinforcing steel.

2. The method for parametric modeling of reinforcing steel bars in precast highway components according to claim 1, characterized in that, When performing type analysis on the aforementioned precast highway components, Precast T-beams, precast small box girders, precast circular culverts, precast cover plates, and precast drainage ditch components are respectively sorted into corresponding steel reinforcement host profile families. The steel reinforcement host profile family is defined as the concrete geometry that constitutes the body of the precast component and is used to define the spatial boundary of the steel reinforcement arrangement. A unified naming rule for the profile families of steel reinforcement hosts of different precast components and a unified naming rule for geometric variables are adopted. For each type of rebar host profile family, its geometric characteristics and the inherent rules of rebar arrangement are further analyzed. For the host profile family of precast T-beams, identify and model typical steel reinforcement categories such as top slab longitudinal reinforcement, web stirrups, and horseshoe reinforcement; For the host profile family of precast circular culverts, identify and model typical steel reinforcement categories of spiral and longitudinal bars; The above-mentioned rebar categories are then associated with the corresponding rebar host profile families in the form of category identifiers.

3. The method for parametric modeling of reinforcing steel bars in precast highway components according to claim 1, characterized in that, When extracting driveable design variables from the geometric features and reinforcement layout rules of various reinforcement host profile families, the design variables are divided into two categories: geometric variables and reinforcement parameters. The geometric variables include at least one or more of the following: total member length, beam height, web thickness, flange width, pipe diameter, and wall thickness. The reinforcement parameters include at least one or more of the following: reinforcement grade, reinforcement diameter, reinforcement spacing, protective layer thickness, anchorage length, and hook angle. The reinforcement host profile family to which each variable belongs and the variable type are explicitly marked in the unified member parameter set. The geometric variables and reinforcement parameters are associated with the mandatory constraint parameters in the relevant specifications. This includes at least mapping the lower limit of the net spacing of reinforcement, the lower limit of the thickness of the concrete cover of reinforcement, the lower limit of the anchorage length of reinforcement, and the bending construction parameters of reinforcement to the corresponding clauses in the aforementioned specifications. In the parameter data structure, the corresponding specification clause number and the allowed value range are recorded for each variable, which serves as the basic data source for constructing the specification verification rule base.

4. The method for parametric modeling of reinforcing steel bars in precast highway components according to claim 1, characterized in that, Geometric templates are created for each type of rebar host profile family using the Geometry API of the 3D design platform. Furthermore, all key dimensions in the geometric template are parametrically controlled by geometric variables, so that the geometric template of the precast T-beam is completely determined by the geometric variables of beam height, flange width, web thickness, and diaphragm spacing, and the geometric template of the precast circular culvert is completely determined by the geometric variables of pipe diameter, wall thickness, and segment length. The Parameter API of the 3D design platform is invoked to associate the geometric variables with the corresponding reinforcement parameters, so that any modification to the geometric variable or reinforcement parameter can simultaneously drive the linkage change of the host concrete geometry and reinforcement layout logic, and automatically reconstruct the precast component model with different sizes and reinforcement schemes under the drive of a unified parameter set.

5. The method for parametric modeling of reinforcing steel bars in precast highway components according to claim 1, characterized in that, When constructing and invoking the rebar layout algorithm based on the code verification rule base, the code verification rule base shall include at least the following types of rules: Spatial positioning rules used to describe the arrangement of longitudinal reinforcement along the length of a member; Used to describe the spatial positioning rules for stirrups that vary along the height of a member or within a local area of ​​a member; Used to describe the spatial positioning rules of spiral reinforcement along the winding path of the pipe body; The spatial positioning rules associate the coordinates of the reinforcement arrangement with reinforcement parameters such as the total length of the component, beam height, web height, pipe diameter, and reinforcement spacing in the form of parametric expressions. It further includes parameter linkage rules to describe how reinforcement parameters such as the number of stirrups, the length of the stirrup reinforcement zone, the number of longitudinal reinforcement bars in the top slab, and the number of spiral reinforcement rings in the circular culvert automatically adjust when the geometric variables of beam height, web thickness, and flange width change. The above rules are solidified in the rule base in the form of functional relationships or logical expressions to uniformly manage the spatial arrangement logic and parameter linkage relationships of reinforcement in various types of precast components.

6. The method for parametric modeling of reinforcing steel bars in precast highway components according to claim 1, characterized in that, When converting the normative constraints into algorithmic logic in the rule base, at least the clauses "the clear spacing of the main reinforcement shall not be less than its diameter and shall not be less than 25mm" and "the anchorage length of the reinforcement shall not be less than the La value specified in the standard" shall be expressed as inequality constraints with parameters such as the diameter of the reinforcement, the thickness of the protective layer, and the grade of the stressed reinforcement as independent variables. An independent logical node or rule entry shall be established for each normative constraint in the normative verification rule base. During the normative verification process, different normative clauses shall be called and verified one by one.

7. The method for parametric modeling of reinforcing steel bars in precast highway components according to claim 1, characterized in that, When establishing the parameter data structure based on the entity data model, EC Schema or an equivalent entity model is used to define entity classes for the rebar host profile family, geometric variables, rebar parameters, and rule entries in the rule base. The relationships between entities are used to record "which geometric variables and rebar parameters a certain rule entry applies to" and "which rule entries a certain rebar host profile family should use". By traversing the entity relationships, a subset of rules applicable to the current component type and parameter combination is automatically selected, stored together, and uniformly called in the parameter data structure and rule base.

8. A parametric modeling system for reinforcing steel bars in precast highway components, characterized in that, include: The host profile family definition module is used to classify highway precast components in the 3D design platform. It abstracts the concrete geometry that constitutes the body of the precast component into a steel reinforcement host profile family, and extracts parameters reflecting the geometry of the component and the arrangement of the steel reinforcement from each steel reinforcement host profile family to form a unified set of component parameters applicable to a variety of precast components. The parameter and specification mapping module is used to establish a parameter data structure for the unified component parameter set based on the entity data model. Based on the relevant design and construction specifications for highway bridges and culverts, the binding clauses in the specifications are expressed as specification verification rules corresponding to the parameter data structure, thus forming a specification verification rule library; The parametric modeling module is used to call the Geometry API of the 3D design platform, establish a parametric geometric template based on the rebar host contour family, parametrically bind the key dimensions in the geometric template with the unified component parameter set, and automatically calculate the 3D coordinates of the rebar based on the rebar layout algorithm driven by the standard verification rule library to generate a 3D model of the rebar of the precast component. The automatic verification module is used to obtain the current component parameters from the unified component parameter set and the three-dimensional model of the steel reinforcement when the three-dimensional model of the steel reinforcement is generated or updated. It calls the standard verification rule library to perform standard verification on key parameters such as the clear spacing of the steel reinforcement, the anchorage length, the bending structure, and the thickness of the protective layer. The steel reinforcement components that do not meet the standard are presented on the three-dimensional design platform interface in the form of graphic highlighting and text prompts. The module for calculating cutting length and exporting data is used to calculate the cutting length of each steel bar component based on the three-dimensional model of the steel bar after the steel bar has passed the specification verification. It then exports the steel bar statistical results and cutting data in the form of a table file or a structured data file for use in steel bar processing and construction.

9. The parametric modeling system for reinforcing steel bars of precast highway components according to claim 8, characterized in that, The host profile family definition module is configured as follows: Different types of precast highway components, such as precast T-beams, precast small box girders, precast circular culverts, precast cover plates, and precast drainage ditches, are classified into corresponding steel reinforcement host profile families. A unified profile family naming rule and a unified geometric variable naming rule are adopted for the steel reinforcement host profile families of different precast components. Furthermore, the host profile family definition module is configured to: for each type of rebar host profile family, analyze its geometric characteristics and the inherent rules of rebar arrangement, identify typical rebar categories such as top slab longitudinal bars, web stirrups, horseshoe reinforcement bars in precast T-beams, and spiral bars and longitudinal bars in precast circular culverts, and associate the above rebar categories with the corresponding rebar host profile families in the form of category identifiers. Meanwhile, the design variables extracted from each rebar host profile family are divided into two main categories: geometric variables and rebar parameters. The geometric variables include at least one or more of the following: total member length, beam height, web thickness, flange width, pipe diameter, and wall thickness. The steel reinforcement parameters include at least one or more of the following: steel reinforcement grade, steel reinforcement diameter, steel reinforcement spacing, protective layer thickness, anchorage length, and hook angle. The unified component parameter set explicitly labels the rebar host profile family and variable type of each variable to support unified parameter management and automatic selection of rebar layout mode for multiple precast component types.

10. The parametric modeling system for reinforcing steel bars of precast highway components according to claim 8, characterized in that, The parameter and specification mapping module is configured to associate the geometric variables and steel reinforcement parameters in the unified component parameter set with the mandatory constraint parameters in the relevant specifications, and at least the lower limit of the net spacing of steel reinforcement, the lower limit of the thickness of the protective layer of steel reinforcement, the lower limit of the anchorage length of steel reinforcement, and the steel reinforcement bending construction parameters are mapped one-to-one with the corresponding clauses in the above specifications, and the corresponding specification clause number and the allowed value range are recorded for each variable in the parameter data structure. Furthermore, the parameter and specification mapping module adopts EC Schema or an equivalent entity data model to define the rebar host profile family, geometric variables, and rebar parameters. and in the standard validation rule base The rule entries define entity classes respectively. Through the relationship between entities, the system records "which geometric variables and reinforcement parameters a certain rule entry applies to" and "which rule entries should be used for a certain reinforcement host profile family". This enables the automatic verification module to automatically select the applicable rule subset based on the relationship between entities when performing reinforcement modeling and standard verification for different types of precast components. This allows the parameter data structure to be associated with and stored in the rule base for unified access.

Images