ISO TC184/SC4/WG3/N540
AP230 Building Structural Frame: Steelwork
Issues Log
The following is a list of issues on the Building Structural Frame:
Steelwork AP.
Each issue is identified by a set of headings which have the following
purposes:-
- Issue Number:
Generated by the AP230 editor according to the following format: "CCC
DD-NN" - where CCC = country/ies, DD = Part number, and NN = Comment
number. Later iterations of the same issue are not recorded. Reviewers may
supply issues numbered according to systems of their own choosing, but
they should include reference to their country/ies.
EXAMPLE 1: USA/CAN 230-99
- Author: The
organization(s) or individual(s) raising the issue, or the organization
collating the issues for a group of organizations and/or individuals.
(optional)
EXAMPLE 2: AISC
- Document: The N
number for the version of the part to which the comments relate.
EXAMPLE 3: N123
- Clause: A selection
from clause/subclause number OR the annex number OR the word
"Introduction" OR the word "Forward"; followed by a
semi-colon; followed by a selection from the word "paragraph(s)"
together with the paragraph number(s) OR the word "note(s)"
together with the note number(s) OR the word "example(s)" together
with the example number(s) OR the word "figure(s)" together with
the figure number(s); followed by a semi-colon; followed by the
abbreviation "p" OR the abbreviation "pp" together
with the page number(s) (if AP230 is being reviewed as a paper document
rather than a WWW document). Multiple references should be separated by
commas.
EXAMPLE 4: Introduction; paragraphs 2, 6; pp i-ii.
EXAMPLE 5: 4.1; note 3; p 21.
- Classification:
major/minor, technical/editorial (optional)
EXAMPLE 6: minor, editorial
- Description: The
text of the issue to be raised.
EXAMPLE 7: The spelling of "organisation" does not conform
to STEP guidelines on use of the OED.
- Proposed Solution: A
suggested resolution of the issue made by the author(s). (optional)
EXAMPLE 8: Change spelling to "organization".
- Resolution:
Generated by the AP230 editor. While the issue remains unresolved, the
text "open" will appear. Once the issue has been resolved, this
text will be replaced by a description of the decision reached on the
issue, the reasons for that decision, and a description of any changes
made to the AP.
EXAMPLE 9: Spelling changed.
- Date issue raised:
The date on which the issue was generated by the author(s).
EXAMPLE 10: 1 April 1996
This page is maintained by M A Ward
Last updated 10 July 1996
To
the AP230 Project Home Page
To the Civil Engineering
Home Page
Issue Number: UK 230-00
Author: University of Leeds
Document: N486
Clause: G; figure G.27; p 72.
Classification: minor, technical
Description: The attribute notch_radius of the entity Notch has the
data-type plane_angle_measure.
Proposed Solution: The data-type plane_angle_measure should be replaced
with the data-type length_measure.
Resolution: Agreed.
Date issue raised: 10 February 1996
Issue Number: UK 230-01
Author: University of Leeds
Document: N486
Clause: G; figure G.13; p 58.
Classification: minor, technical
Description: The attributes last_name, first_name, middle_name, and
former_name of the entity Person have the data-type name. In order to bring the
ARM more into line with part 41, this should be changed.
Proposed Solution: Change all occurrences of the data-type name in the ARM
to the data type label.
Resolution: Agreed.
Date issue raised: 11 February 1996
Issue Number: UK 230-02
Author: University of Leeds
Document: N486
Clause: G; figure G13; p 58.
Classification: minor, technical
Description: The attribute middle_name of the entity Person is in the
singular. In order to bring the ARM more into line with part 41, this should be
changed. (see also issue 101)
Proposed Solution: Replace middle_name with middle_names.
Resolution: Agreed.
Date issue raised: 11 February 1996
Issue Number: UK 230-03
Author: University of Leeds
Document: N486
Clause: G; figure G.13; p 58.
Classification: minor, technical
Description: The attributes middle_name, prefix_titles, and suffix_titles of
the entity Person do not have list data-types. In order to bring the ARM more
into line with part 41, this should be changed. (see also issues 102 and 103)
Proposed Solution: Replace label with L [1:?] label.
Resolution: Agreed.
Date issue raised: 11 February 1996
Issue Number: UK 230-04
Author: University of Leeds
Document: N486
Clause: G; figures G.2-G.7, G.10-G.11, G.15-G.19, G.21, G.25-G.26,
G.28-G32, G.34; pp 47-52, 55-56, 60-64, 66, 70-71, 73-77, 79.
Classification: major, technical
Description: Many attributes currently have the data-type description. In
order to bring the ARM more into line with part 41, this should be changed.
Proposed Solution: The data-type description should be deleted from the
ARM, and all occurrences of description should be replaced with text.
Resolution: Agreed.
Date issue raised: 11 February 1996
Issue Number: UK 230-05
Author: University of Leeds
Document: N486
Clause: G; figures G.2, G.21, G.25, G.26, G.28, G34; pp 47, 66, 70, 71, 73,
79.
Classification: major, technical
Description: The entities -
- Assembly (attribute
assembly_type : assembly_usage),
- Analysis_result
(attribute analysis_result_type : analysis_res_type),
- Element_result (attribute
element_result_type : element_res_type),
- Elmnt_node_result (attribute
element_end_result_type : elmnt_node_res_type),
- Node_result (attribute
node_result_type : node_res_type),
- S_part (attribute
s_part_type : specific_part_type),
- Pseudo_prismatic_part
(attribute pseudo_pris_part_select : ppp_type),
- S_feature (attribute
s_feature_type : specific_feature_type),
- Prismatic_end_feature
(attribute prismatic_end_feature_type : pris_end_feat_type),
- P_joint_system (attribute
s_joint_system_type : specific_joint_system_type) and
- Geometric_representation
(attribute parametric_geom_type : parametric_geometry_type)
have sets of enumeration items which correspond exactly to their subtypes.
Moreover, these entities are abstract supertypes and could never be implemented
without the implementation of their subtypes. These "discriminators"
were inherited from the original IDEF1X version of the CIMsteel Integration
Standards and are now redundant.
Proposed Solution: Delete all the above attributes and associated
enumerated data-types from the ARM.
Resolution: Agreed.
Date issue raised: 12 February 1996
Issue Number: UK 230-06
Author: University of Leeds
Document: N486
Clause: G; figures G.3, G.6, G.18, G.19, G.21, G.32; pp 48, 51, 63, 64, 66,
77.
Classification: major, technical
Description: The entities -
- Design_assembly (attribute
da_type : design_assembly_use),
- Located_feature (attribute
loc_feat_use : feature_role),
- Basic_load_case (attribute
basic_load_case_type : blc_type),
- Element_load (attribute
element_load_select : element_load_type),
- Analysis_results_set
(attribute result_set_type : analysis_results_set_type),
- Group (attribute
group_type : group_select), and
- Assembly_group (attribute
assembly_group_type : asbly_grp_select)
have sets of enumeration items which correspond - by and large - to their
subtypes and the attributes concerned are somewhat redundant. On the other
hand, in each case, the enumeration provides an additional option (such as
"undefined") which is not represented by a subtype; and the entities
are not abstract supertypes and could be implemented without the implementation
of their subtypes.
Proposed Solution: Delete all the above attributes and associated
enumerated data-types from the ARM.
Resolution: Agreed. In spite of the fact that the enumerations are not
strictly redundant, this is an inelegant means of achieving the result desired.
Date issue raised: 15 May 1996
Issue Number: UK 230-07
Author: University of Leeds
Document: N486
Clause: G; figures G.15, G.19, G.31; pp 60, 64, 76.
Classification: major, technical
Description: Although the entities -
- Analysis (attribute
static_or_dynamic : analysis_type),
- Conc_node_load (attribute
node_load_select : node_load_type),
- Coord_system (attribute
coord_sys_type : coord_system_select), and
- Transformation (attribute
transformation_type : transf_type)
have no subtypes and are not abstract supertypes, the enumeration (for each
entity) provides only one option. These options do flag future extensions, but,
as the model stands, they are redundant.
Proposed Solution: Delete all the above attributes and associated
enumerated data-types from the ARM.
Resolution: Rejected. The ARM will be extended at some time in the future
and the existing enumeration options should be retained until then.
Date issue raised: 15 May 1996
Issue Number: UK 230-08
Author: University of Leeds
Document: N486
Clause: G; figure G.19; p 64.
Classification: minor, technical
Description: The entity Environmental_load has the attribute
envirnmntl_load_type : env_load_type. While this enumeration does appear to
provide an option not provided by the subtypes (the "undefined"
item), the entity in question is an abstract supertype. This means that the
enumeration item would not be implemented.
Proposed Solution: Delete the above attribute and associated enumerated
data-type from the ARM.
Resolution: Agreed.
Date issue raised: 15 May 1996
Issue Number: UK 230-09
Author: University of Leeds
Document: N486
Clause: G; figure G.34; p 79.
Classification: minor, technical
Description: The entity geometric_representation has the attribute
geometry_type : geometric_rep_type. While this is an abstract supertype and has
no subtypes corresponding to the enumeration, only one option is provided by
the enumeration. It is not clear that this serves any real purpose.
Proposed Solution: Delete the above attribute and associated enumerated
data-type from the ARM.
Resolution: Rejected, The ARM will be extended at some time in the future,
the existing enumeration option signals this fact and should be retained until
then..
Date issue raised: 15 May 1996
Issue Number: UK 230-10
Author: British Standards Institution
Document: N486
Clause: F; figures F.1-F.7; pp 38-44.
Classification: minor, editorial
Description: The lines used for ICOM arcs and for activity bounding boxes
in the AAM IDEF0 diagrams do not reproduce well.
Proposed Solution: Increase the weight of all lines used in the AMM IDEF0
diagrams.
Resolution: Agreed and implemented in N528.
Date issue raised: 21 June 1996
Issue Number: UK 230-11
Author: British Standards Institution
Document: N486
Clause: 4; notes 2, 3, 4; p 5.
Classification: minor, editorial
Description: The notes are incorrectly numbered and are not presented in
line with ISO guidelines.
Proposed Solution: The three notes should be numbered from 1-3, the full
stops should be replaced with dashes, and the three occurrences of the word
"NOTE" should be replaced by a single "NOTES" heading on
the line above the three notes.
Resolution: Agreed and implemented in N528.
Date issue raised: 21 June 1996
Issue Number: UK 230-12
Author: British Standards Institution
Document: N486
Clause: 4.1.1; note 5; 6.
Classification: minor, editorial
Description: The note is not presented in line with ISO guidelines.
Proposed Solution: The number for the note should be deleted and the full
stop should be replaced by a dash.
Resolution: Agreed and implemented in N528.
Date issue raised: 21 June 1996
Issue Number: UK 230-13
Author: British Standards Institution
Document: N486
Clauses: 4.1.2, 4.1.3, 4.1.4, 4.1.5, 4.1.6, 4.1.7, 4.1.8, 4.1.9, 4.1.10,
4.1.11; paragraphs 1, 1, 1, 1, 1, 1, 1, 1, 1; pp 7, 8, 10, 12, 13, 13, 14, 15,
17, 19.
Classification: minor, editorial
Description: The format of AAM activities is not consistent with that used
in clause 4.1.1, and the references to activities in the AAM have not been
completed and should, again to ensure consistency, be presented as they are in
clause 4.1.1.
Proposed Solution: Italicise all AAM activities referred to in clause 4 and
include references to those activities in the form of notes.
Resolution: Agreed and implemented in N528.
Date issue raised: 21 June 1996
Issue Number: UK 230-14
Author: British Standards Institution
Document: N528
Clause: F; figure F.4; p 43.
Classification: minor, technical
Description: There is no feedback from the produce concept design activity
to the manage overall design activity.
Proposed Solution: Create a link from box A22 to the overall design
feedback arrow.
Resolution: Agreed and implemented in N551.
Date issue raised: 3 July 1996
Issue Number: UK 230-15
Author: British Standards Institution
Document: N528
Clause: 2; paragraph 10; pp 2 3.
Classification: major, technical
Description: There is no explicit provision in AP230 for cambered beams.
Proposed Solutions: (1) Add a note to the AP document which signals intent
to include explicit provision for cambered beams. (2) Extend the AP230 data
model to include explicit provision for cambered beams.
Resolution: (1) Agreed and implemented in N551. (2) Agreed.
Date issue raised: 3 July 1996
Issue Number: UK 230-16
Author: British Standards Institution
Document: N528
Clause: 2; paragraph 10; pp 2 3.
Classification: major, technical
Description: There is no explicit provision in AP230 for composite
structures.
Proposed Solutions: (1) Add a note to the AP document which signals intent
to include explicit provision for shear studs. (2) Extend the AP230 data model
to include explicit provision for shear studs. (3) Extend the AP230 data model
to encompass composites.
Resolution: (1) Agreed and implemented in N551. (2) Agreed. (3) Rejected.
The modelling of composite structures is outside the scope of an AP devoted to
structural steelwork and deserves an AP in its own right.
Date issue raised: 22 July 1996
Issue Number: UK 230-17
Author: British Standards Institution
Document: N528
Clause: 2; paragraph 10; pp 2 3.
Classification: major, technical
Description: There is no explicit provision in AP230 for dynamic loading in
general and seismic loading in particular.
Proposed Solution: Add a note to the AP document which explains how seismic
loads are accommodated within the current data structures of AP230 (if
represented as equivalent static loads).
Resolution: Agreed and implemented in N551.
Date issue raised: 22 July 1996
Issue Number: USA 230-18
Author: AISC Committee
Version: N486
Clause: n/a
Classification: major, technical
Description: The level of detail in AP 230 is inappropriate. In U.S.
practice, it is excessive for about 97% of building projects (where most
exchanges occur within an organization) and insufficient for the other 3%
(power plants and heavily regulated structures).
Proposed solution: Perhaps, some editing would be appropriate, to make the
neutral file more manageable, but not reduce its usefulness.
Resolution: Rejected. The argument that the complete data model is too
unwieldy for most transaction within an organization is valid, but conformance
classes (which are overlapping subsets of the complete model) provide the
answer to this problem.
Date issue raised: 17 June 1996
Issue number: USA 230-19
Author: AISC Committee
Version: N486
Clause: n/a
Classification: major, technical
Description: Composite construction, a major component of steel
construction in the U.S. is not covered.
Proposed solution: Provide coverage of composite construction.
Resolution: See issue 16.
Date issue raised: 17 June 1996
Issue number: USA 230-20
Author: AISC Committee
Version: N486
Clause: G; figures G.5, G.19; pp 50, 64.
Classification: major, technical
Description: The factors for limit state design (load and resistance
factors) need definitions that accommodate U.S. (AISC) practice.
Proposed solution: Provide additional definitions and descriptions for U.S.
users.
Resolution: Open - seeking further clarification from US.
Date issue raised: 17 June 1996
Issue number: USA 230-21
Author: AISC Committee
Version: N486
Clause: G; figure G.35; p 80.
Classification: major, technical
Description: Section-profile attributes do not correspond directly to the
"dimensions" and "properties" in the AISC Manual of Steel
Construction.
Proposed solution: Provide an alternative which conforms to U.S. practice.
Resolution: Open - seeking further clarification from US.
Date issue raised: 17 June 1996
Issue number: USA 230-22
Author: AISC Committee
Version: N486
Clause: G; figure G.20; p 65.
Classification: major, technical
Description: Snow and wind load attributes do not agree with those in
ANSI/ASCE 7, which reflects U.S. practice. For example, factors S1 to S4 are
not used in the U.S.
Proposed solutions: (1) Provide an alternate conforming with U.S. practice.
(2) Provide a more general format.
Resolution: (1) Rejected. (2) Agreed. A more generic solution to the whole
issue of loading has been developed.
Date issue raised: 17 June 1996
Issue number: USA 230-23
Author: AISC Committee
Version: N486
Clause: G; figure G.19; p 64.
Classification: major, technical
Description: Earthquake loads are not covered.
Proposed solution: Provide for "equivalent static" earthquake
loads, in accordance with ANSI/ASE 7, to reflect U.S. practice.
Resolution: See issue 17
Date issue raised: 17 June 1996
Issue number: USA 230-24
Author: AISC Committee
Version: N486
Clauses: F, G; figures F.1-F.7, G.1-G.40; pp 38-44, 46-85.
Classification: major, editorial
Description: Better cross-referencing between Annexes F and G is needed. Specifically,
in Annex G there is no indication of which files in Annex F hold particular
entities. If this were done properly, the effectiveness of AP 230 would be
improved by providing a clearer understanding of the relationships. Also, Annex
F would serve as an overview, or "coarse" model, showing only inputs
and outputs. Annex G would provide the "fine" details regarding
information flows.
Proposed solution: Provide additional cross-referencing between Annexes F
and G.
Resolution: Rejected. Under ISO guidelines, Units of Functionality (Clause
4.1) are designed to provide the necessary cross referencing between Annexes F
and G.
Date issue raised: 17 June 1996
Issue number: USA 230-25
Author: AISC Committee
Version: N486
Clause: F; pp 31-44.
Classification: major, editorial
Description: A clear delineation is needed, separating the scope of AP 230
from the interactions that are outside its scope.
Proposed solution: Clearly indicate what is not covered by AP 230.
Resolution: Agreed. This is a mistake in N486. The definitions for
out-of-scope activities and data flows should have been tagged with asterisks.
Date issue raised: 17 June 1996
Issue number: USA 230-26
Author: AISC Committee
Version: N486
Clauses: F1.28, F1.60; paragraphs 1, 1; pp 33, 35.
Classification: minor, editorial
Description: While "overall structural design" produces the
"initial sizes of structural elements", the source of the final sizes
is not shown.
Proposed solution: Indicate the activity producing the final member sizes.
Resolution: Agreed. The definition for the "produce detail design
& prepare for production" activity will be amended to make this matter
more explicit.
Date issue raised: 17 June 1996.
Issue number: USA 230-27
Author: AISC Committee
Version: N486
Clause: G; pp 45-85.
Classification: major, technical
Description: This model, due to its size and complexity, is difficult to
review and may be difficult to implement.
Proposed solution: If feasible, attempt to modularize the model into
smaller chunks.
Resolution: See issue 18.
Date issue raised: 17 June 1996
Issue number: USA 230-28
Author: AISC Committee
Version: N486
Clause: G; figures G1.6-G1.7; pp 61-62.
Classification: minor, technical
Description: In addition to elastic restraints, a number of other boundary
conditions would be useful.
Proposed solutions: (1) Add member releases. (2) Add joint releases. (3)
Add constant-displacement boundary conditions.
Resolution: (1) Rejected. Member releases are provided for by the
"release" entity (Figure G.16). (2) Rejected. Joint releases are
provided for by the "boundary condition" entity (Figure G.17). (3)
Open. Seeking clarification of this term.
Date issue raised: 17 June 1996
Issue number: USA 230-29
Author: AISC Committee
Version: N486
Clause: G; figure G.4; p 49.
Classification: minor, technical
Description: There is no apparent means to transfer data representing a
special instruction to the fabricator, erector, or general contractor. Examples
are "ship loose", "temporary bracing", and "sequence
of welding".
Proposed solution: Provide capability to transmit special instructions.
Resolution: Partially agreed. "Special instuctions" have been
added as an attribute of manufacturing assembly. Assemblies can now have
"functional roles" (such as "temporary bracing"). Assembly
sequence is provided by the manufacturing assembly sequence attribute of
manufacturing assembly; sequence of welding could be implied (and inferred)
from the order of the list of trace segments which belong to a weld trace; and
sequence of bolting (or tightening) could be implied (and inferred) from the
order of the list of points which belong to a bolted joint system.
Date issue raised: 17 June 1996
Issue number: USA 230-30
Author: AISC Committee
Version: N486
Clause: G; figures G.18, G.19; pp 63, 64.
Classification: minor, technical
Description: There are no apparent provisions for loads applied over an
area or for formulas specifying live load reduction.
Proposed solution: (1) Add live load reduction. (2) Add area loads.
Resolution: (1) Rejected. Live load reduction is already catered for by the
"basic_load_case_factor" attribute of the "Basic_load_case"
entity (Figure G.19). (2) Agreed. (see also issue 22)
Date issue raised: 17 June 1996
Issue number: USA 230-31
Author: AISC Committee
Version: W3 draft Clause 4 material accompanying N486
Clause: 4.4.28
Classification: minor, editorial
Description: The following terms are not sufficiently defined: assembly
(1), design assembly (2), conformance class (3), and pseudo-prismatic part (4).
Proposed solution: Provide better definition of these terms.
Resolution: (1) Rejected. This is an abstract supertype (however, see
"Design_assembly"). (2) Agreed. A note will be provided which adds
clarification. (3) Rejected. Conformance class is an ISO expression which is
defined in other ISO documents. It cannot be defined within an AP. (4) Agreed.
A note - which includes a diagram - will be provided.
Date issue raised: 17 June 1996
Issue number: USA 230-32
Author: AISC Committee
Version: N486
Clause: G; figure G.11; p56.
Classification: minor, technical
Description: The attribute altitude requires a datum reference.
Proposed solution: Provide datum as an additional attribute relating to
altitude.
Resolution: Agreed
Date issue raised: 17 June 1996
Issue number: USA 230-33
Author: AISC Committee
Version: N486
Clause: G; figure G.35; p 80.
Classification: minor, technical
Description: Tubular sections are apparently not covered.
Proposed solution: Include tubular sections.
Resolution: Rejected. Circular tubular sections are covered by the
"Circle_sect" entity, and rectangular tubular sections are covered by
the "Rect_sect" entity.
Date issue raised: 17 June 1996
Issue number: USA 230-34
Author: AISC Committee
Version: N486
Clause: 1; paragraph 10; p3.
Classification: major, technical
Description: Plate girders or "non-standard fabricated beams",
which are currently outside the scope of AP 230, are commonly used and should
be included.
Proposed solution: Include plate girders.
Resolution: Agreed. The detailed information concerning plate girders and
fabricated items was covered by the "manufact_asbly" entity; but
manufacturing assemblies did not acquire the full set of attributes which can
be associated with conventional rolled members. The data model has been
modified to include compound members.
Date issue raised: 17 June 1996
Issue number: USA 230-35
Author: AISC Committee
Version: N486
Clause: 1; paragraph 10; p 2.
Classification: major, technical
Description: Curved members are not covered. They are needed for circular
platforms, bridges, etc.
Proposed solution: Include curved members.
Resolution: Agreed.
Date issue raised: 17 June 1996
Issue number: USA 230-36
Author: AISC Committee
Version: N486
Clause: 4.1.2; pp 7-8.
Classification: minor, technical
Description: Element stresses are missing. They are used to determine
structural adequacy.
Proposed solution: Add element stresses.
Resolution: Agreed.
Date issue raised: 17 June 1996
Issue number: USA 230-37
Author: AISC Committee
Version: N486
Clause: 4.1.10; pp 17-18.
Classification: minor, technical
Description: Surface condition classification is needed for slip critical
bolts, to conform with U.S. (AISC) practice.
Proposed solution: Add surface condition classification for slip critical
bolts.
Resolution: Agreed. Atrributes relating to surface preparation have been
added to the model.
Date issue raised: 17 June 1996
Issue number: USA 230-38
Author: AISC Committee
Version: N486
Clause: G; figure F.35; p80.
Classification: minor, technical
Description: No unique identifier is shown for the single angle section
instance.
Proposed solution: Provide a unique identifier attribute.
Resolution: Rejected. The "Angle_sect" entity inherits a unique
"section_id" from its "Section_profile" supertype.
Date issue raised: 17 June 1996
Issue number: USA 230-39
Author: AISC Committee
Version: N486
Clause: G; figure G.18; p 63.
Classification: minor, technical
Description: There is no apparent provision for partially distributed loads.
Proposed solution: Provide for partially distributed loads.
Resolution: Rejected. There is adequate provision for 1D distributed loads
- see "dist_load_length" and "distrib_el_ld_x_coord"
attributes of "Distributed_1d_elmnt_load" entity. The whole question
of 2D (area) loading is being pursued separately (see issue 22).
Date issue raised: 17 June 1996
Issue number: USA 230-40
Author: AISC Committee
Version: W3 draft Clause 4 material accompanying N486
Clause: 4.2.71
Classification: minor, technical
Description: In addition to design strength, it may be useful to capture
the mill-certified strength of members, when it is available.
Proposed solution: Add "certified material strength" as a member
attribute.
Resolution: Partially agreed. A more generic solution to the issue of
recording material strengths has been adopted.
Date issue raised: 17 June 1996
Issue number: USA 230-41
Author: AISC Committee
Version: N486
Clause: G; figure G.6; p51.
Classification: minor, technical
Description: The types of structural frames shown do not include
"moment resisting frame", a term commonly used in the U.S.
Proposed solution: Add "moment resisting frame".
Resolution: Rejected. The "sway-frame" attribute of the
"Struc_frame" entity provides adequate provision here. The definition
of this term will, however, be expanded to clarify matters.
Date issue raised: 17 June 1996
Issue number: USA 230-42
Author: AISC Committee
Version: N486
Clause: G; figure G.15; p60.
Classification: major, technical
Description: The attributes "analysis assumptions" (1),
"connection type" (2), and "element_sub_division" (3) are
set for the entire analysis. They should be assigned to specific sub parts of
the model.
Proposed solution: Provide an option to vary "analysis
assumptions" (1), "connection type" (2), and
"element_sub_division" (3) from one subpart to another.
Resolution: (1) Rejected. Analysis assumptions are an attribute of analysis
method (formally analysis) and this seems appropriate. (2) Agreed. Connection
type (ie "connection rigidity") is now an attribute of element node
connectivity. (3) Agreed. Element sub-division is now an attribute of element.
Date issue raised: 17 June 1996
Issue number: USA 230-43
Author: AISC Committee
Version: N486
Clause: G; figure G.3; p 48.
Classification: minor, technical
Description: Design criteria are apparently represented in text form only.
Are computable representations of design criteria also appropriate?
Proposed solution: If feasible, other representation methods for design
criteria should be included.
Resolution: Open. In principle, there is a case for accepting this
proposal. However, this would mean extension of the existing model to take
account of very large numbers of existing standards and practices around the
world. This would result in a very much more unwieldy model and would provide
very small benefits.
Date issue raised: 17 June 1996
Issue number: USA 230-44
Author: AISC Committee
Version: N486
Clause: Annex G
Classification: minor, technical
Description: "Date, time modified" is listed under both
"Steel structural frame" and "Instance group", apparently
an unnecessary redundancy.
Proposed solution: Adjust or justify present form.
Resolution: Partly agreed. Although modification of the "Instance_group"
entity will always imply modification of the
"Steel_structural_frame_file", the reverse implication does not hold.
The is, therefore, only partial redundancy. This section of the data model has
now been changed and a more elegant solution adopted.
Date issue raised: 17 June 1996
Issue number: USA 230-45
Author: AISC Committee
Version: N486
Clause: G; figure G.19; p64.
Classification: minor, editorial
Description: In U.S. practice, the term "live load" is used
instead of "imposed load".
Proposed solution: Replace "imposed load" with "imposed or
live load" throughout.
Resolution: Partially agreed. A more generic approach to loading has is
been adopted and the term "live load" has been adopted in place of
the term "imposed load" (see also issue 22).
Date issue raised: 17 June 1996
Issue number: USA 230-46
Author: AISC Committee
Version: N486
Clause: 1; paragraph 6; p 1.
Classification: minor, editorial
Description: The word "domestic" should be followed by "or
residential". The latter term is common in U.S. practice.
Proposed solution: Consider this modification.
Resolution: Partially agreed. The word "domestic" will be
REPLACED by the term "residential".
Date issue raised: 17 June 1996
Issue number: USA 230-47
Author: AISC Committee
Version: W3 draft Clause 4 material accompanying N486
Clauses: 4.2.35, 4.2.72.
Classification: minor, editorial
Description: To accommodate variations in terminology, "joint"
should be shown as a synonym for "node" (1) and "member" as
a synonym for "element" (2).
Proposed solution: Include these alternative terms.
Resolution: (1) Partially agreed. The definition of "node" will
be amended to acknowledge the fact that (what is referred to in the AP as) a
"node" can also be referred to as a "joint". (2) Partially
agreed. The definition of "element" will be amended to acknowledge
the fact that (what is referred to in the AP as) an "element" can
also be referred to as a "member".
Date issue raised: 17 June 1996
Issue number: USA 230-48
Author: AISC Committee
Version: N486
Clause: 4.1.3; paragraph 1; p8.
Classification: minor, editorial
Description: In the first paragraph (line 6), reference to serviceability
as the criterion for checking the adequacy of an initial design should be
stated, more accurately, as "strength and serviceability".
Proposed solution: Change "overall serviceability" to
"member strength and serviceability".
Resolution: Partially agreed. Change "overall serviceability
(principally deflection of the structure)" to "overall serviceability
(principally deflection of the structure) as well as individual member strength
and serviceability".
Date issue raised: 17 June 1996
Issue number: USA 230-49
Author: AISC Committee
Version: W3 draft Clause 4 material accompanying N486
Clause: 4.2.2
Classification: minor, editorial
Description: "static_or_dymanic" is misspelled. It should be
"static_or_dynamic".
Proposed solution: Correction
Resolution: Agreed.
Date issue raised: 17 June 1996
Issue number: USA 230-50
Author: AISC Committee
Version: W3 draft Clause 4 material accompanying N486
Clause: 4.2.10
Classification: minor, editorial
Description: "Decalres" should be spelled "Declares".
Proposed solution: Correct spelling.
Resolution: Agreed.
Date issue raised: 17 June 1996
Issue number: USA 230-51
Author: AISC Committee
Version: W3 draft Clause 4 material accompanying N486
Clause: 4.2.11
Classification: minor, editorial
Description: For consistency, "basic_load_label" should be
"basic_load_case_label".
Proposed solution: Consider revision.
Resolution: Agreed.
Date issue raised: 17 June 1996
Issue number: USA 230-52
Author: AISC Committee
Version: W3 draft Clause 4 material accompanying N486
Clause: 4.2.15
Classification: minor, editorial
Description: "...may consist a single" should read "...may
consist of a single".
Proposed solution: Consider revision.
Resolution: Agreed.
Date issue raised: 17 June 1996
Issue number: USA 230-53
Author: AISC Committee
Version: W3 draft Clause 4 material accompanying N486
Clause: 4.2.32
Classification: minor, editorial
Description: Regarding "Edge_chamfer", a sketch would be helpful.
Proposed solution: Provide sketch.
Resolution: Agreed.
Date issue raised: 17 June 1996
Issue number: USA 230-54
Author: AISC Committee
Version: W3 draft Clause 4 material accompanying N486
Clause: 4.2.62
Classification: minor, editorial
Description: "...load case participates to the Loading..." should
read "...load case participates in the Loading..."
Proposed solution: Consider revision.
Resolution: Agreed.
Date issue raised: 17 June 1996
Issue number: USA 230-55
Author: AISC Committee
Version: W3 draft Clause 4 material accompanying N486
Clause: 4.2.88
Classification: minor, editorial
Description: For consistency, "Pseudo_prismatic_part" should be
all lower case (not capitalized) throughout.
Proposed solution: Correct inconsistencies in style.
Resolution: Agreed.
Date issue raised: 17 June 1996
Issue number: USA 230-56
Author: AISC Committee
Version: N486
Clause: G; figure G.21; p66.
Classification: minor, editorial
Description: Under element result, the meaning of "x_increasing"
is not clear.
Proposed solution: Clarification of "x_increasing".
Resolution: Rejected. This term is adequately defined in clause 4.2.41.
Date issue raised: 17 June 1996
Issue number: USA 230-57
Author: AISC Committee
Version: N486
Clause: G; figure G.26; p71.
Classification: minor, editorial
Description: The abbreviation "procedural_feat" is confusing and
inconsistent with use of the whole word "feature" elsewhere.
Proposed solution: Replace "procedural_feat" with
"procedural_feature".
Resolution: Agreed
Date issue raised: 17 June 1996
Issue number: USA 230-58
Author: AISC Committee
Version: N486
Clause: F; figures F.3, F.6; pp 40, 43.
Classification: minor, editorial
Description: As "project brief" and "extended brief"
are terms not used in U.S. practice, the terms "working drawings",
(1) "project specifications", (2) and "contract documents"
(3) should be incorporated.
Proposed solution: Include alternative terminology.
Resolution: (1) Partially agreed. The term "working drawings" is
not a synonym for either the terms "project brief" or "extended
brief". Working drawings are included in "detailed designs". The
definition of this term will be amended to reflect this fact. (2) Rejected. The
term "contract documents" is not a synonym for either the terms
"project brief" or "extended brief". Contract documents are
covered by the term "project contract documents". (3) Rejected. The
term "contract documents" is not a synonym for either the terms
"project brief" or "extended brief". Project specifications
are covered by the term "project technical specifications".
Date issue raised: 17 June 1996
Issue number: Japan 230-59
Author: Yuichi Matsumoto
Version: N486
Clause: 1; paragraph 5; p3.
Classification: major, technical
Description: The scoping statement for 10303-230 specifically excludes
dynamic and cyclic loading - such as seismic loading. This is an important
consideration for Japan and other Pacific basin countries and has implications
for member design, connection design, detail design and fabrication.
Proposed solution: Extend the AP230 data model to include dynamic loading.
Resolution: Agreed (see issues 17 and 23).
Date issue raised: 8 October 1996
Issue number: Japan 230-60
Author: Yuichi Matsumoto
Version: N486
Clause: F; ; pp 31-44.
Classification: major, editorial
Description: The AAM requires greater clarification.
Proposed solution: Place the AAM before Clause 4 (Information Requirements)
in the AP document.
Resolution: Rejected. ISO guidelines prescribe the order and content of
clauses and annexes in an AP document (see also issue 124).
Date issue raised: 8 October 1996
Issue number: Japan 230-61
Author: Yuichi Matsumoto
Version: N486
Clauses: 4.1, F; ; pp 5-20 & 31-44.
Classification: major, editorial
Description: The relationship between the AAM and Units of Functionality
requires greater clarification.
Proposed solution: Include cross-referencing between UoFs and the AAM.
Resolution: Agreed and implemented in N528 (see also issue 113).
Date issue raised: 8 October 1996
Issue number: Japan 230-62
Author: Yuichi Matsumoto
Version: N486
Clauses: 4.2, 4.3, G; ; pp 21- & 45-85.
Classification: major, technical
Description: The current data model does not explicitly include reference
to structural elements (commonly referred to in design) such as
"column", "girder", "beam", "floor",
"wall" etc.
Proposed solutions: (1) Add the relevant subtypes to Struc_member. (2) Add
an suitable enumeration as an attribute of Struc_member.
Resolution: (1) Agreed. This approach was considered and rejected for the
original data model on the grounds that no satisfactory set of formal
definitions exist - for things like "column", "brace" and
"beam" - which are inclusive of all the things we might want to call
"columns", "braces" or "beams", and yet mutually
exclusive; nevertheless - in the interests of clarity - entities along these
lines have now been included as optional place-holders (with optional
attributes specifying wether these entities are subject to tensile or
compresive forces). (2) Rejected - subtypes mopre appropriate.
Date issue raised: 8 October 1996
Issue number: Japan 230-63
Author: Yuichi Matsumoto
Version: N486
Clauses: 4.2, 4.3; ; pp 21- .
Classification: major, editorial
Description: The written definitions for application objects and assertions
are complex and difficult to understand.
Proposed solution: Add diagrams (see also issue 153).
Resolution: Agreed.
Date issue raised: 8 October 1996
Issue number: Japan 230-64
Author: Yuichi Matsumoto
Version: N486
Clauses: 4.2, 4.3, G; ; pp 21- & 45-85.
Classification: major, editorial
Description: Application objects are arranged in alphabetical order and it
is difficult to relate them to the graphical data model.
Proposed solution: Use a functional ordering for the application objects in
clause 4.
Resolution: Rejected. ISO guidelines prescribe the order and content of
clauses and annexes in an AP document.
Date issue raised: 8 October 1996
Issue number: Finland 230-65
Author: Markku Heinisuo
Version: N486
Clauses: 4.2, 4.3, G; n/a, n/a, figures G.4, G.6, G.24, G.26; pp 21- , 49,
51, 70 & 71.
Classification: major, technical
Description: The current constellation of S_part, Located_part, S_feature,
and Located_feature objects works well for "one-off" parts and
generic parts; and for "one-off" features. The current model does
not, however, work well for generic features - such as when a construction
employs a large number of identical plates with a hole drilled through then
centre of each one.
Proposed solution: Change the model to allow for the definition of generic
features, thus: (1) Eliminate the link between Located_feature and
Located_part. Create Subtypes of Located_feature:
"Located_feature_located_on_S_part" and
"Located_feature_located_on_Located_part". Establish links between
Located_feature_located_on_S_part and S_part; and between
Located_feature_located_on_Located_part and Located_part; or thus (2)
Restructure the model in some other way to meet this concern.
Resolution: (1) Rejected. (2) Agreed.
Date issue raised: 2 October 1996
Issue number: Finland 230-66
Author: Markku Heinisuo
Version: N486
Clauses: 4.2, 4.3, G; n/a, n/a, figures G.14; pp 21- , 59.
Classification: major, technical
Description: The current Instance_group entity provides an inadequate
mechanism for dealing with versioning of information.
Proposed solution: Change the model to create a more sophisticated
mechanism for capturing different versions of the same information.
Resolution: Agreed.
Date issue raised: 2 October 1996
Issue number: Finland 230-67
Author: Markku Heinisuo
Version: N486
Clauses: 4.2, 4.3, G; n/a, n/a, figures G.14; pp 21- , 59.
Classification: minor or major (depending on solution chosen), technical
Description: Because the entity Instance_group has no id attribute, there
is no stable id for a group and no guarantee of referring to that group within
software that has imported a physical file.
Proposed solution: Create an identifying attribute for Instance_group.
Resolution: Open. (The whole question of ids for entities within the AP230
data model will need to be addressed)
Date issue raised: 2 October 1996
Issue number: Finland 230-68
Author: Markku Heinisuo
Version: N486
Clauses: 4.2, 4.3, G; n/a, n/a, figure G.32; pp 21- , 77.
Classification: major, technical
Description: The grouping mechanism provided by the "Group"
entity and its subtypes is too inflexible. A group of data - created for
whatever reason - may contain, as well as belong to, a number of other groups.
Proposed solution: Create a more flexible grouping mechanism.
Resolution: Agreed. Any group can now be related to any other group (or
groups) and this ralationship given a label - such as "belongs to" or
"includes".
Date issue raised: 2 October 1996
Issue number: Finland 230-69
Author: Markku Heinisuo
Version: N486
Clauses: 4.2, 4.3, G; n/a, n/a, figure G.4; pp 21- , 49.
Classification: minor, technical
Description: The current model allows for surface treatment to be applied
only to a manufacturing assembly and does not allow for the surface treatment
of individual parts of assemblies.
Proposed solution: Add a suitable attribute to the Located_part entity.
Resolution: Agreed.
Date issue raised: 2 October 1996
Issue number: Finland 230-70
Author: Markku Heinisuo
Version: N486
Clauses: 4.2, 4.3, G; n/a, n/a, figure G.4; pp 21- , 49.
Classification: minor, technical
Description: The current model allows for surface treatment to be applied
only to the entire surface of a manufacturing assembly and does not allow for
the surface treatment of a restricted area of the surface of an assembly.
Proposed solution: Create a suitable data structure for recording the area
over which a surface treatment is applied to an assembly.
Resolution: Agreed.
Date issue raised: 2 October 1996
Issue number: Finland 230-71
Author: Markku Heinisuo
Version: N486
Clauses: 4.2, 4.3; n/a, n/a; pp 21-.
Classification: minor or major (depending on solution chosen), technical
Description: The current model uses the back-slash as a separator in
identifiers for standard parts. This is an unfortunate choice, not least
because the back-slash is used in strings to signal the start of a non-ASCII
sequence of characters - such as Cyrillic characters.
Proposed solution: (1) Use a different separator. (2) Separate out the
various elements of the identifiers as separate attributes
Resolution: (1) Rejected. (2) Agreed.
Date issue raised: 2 October 1996.
Issue number: Finland 230-72
Author: Markku Heinisuo
Version: N486
Clauses: 4.2, 4.3, G; n/a, n/a, figure G.13; pp 21-, 58.
Classification: minor, technical
Description: The entity person has an identifying attribute for which
social security number is suggested. This is not allowed under Finnish law.
Proposed solution: Use a different identifier.
Resolution: Rejected. Social security number is simply given as an example.
Any kind of identifier may be used.
Date issue raised: 2 October 1996.
Issue number: Finland 230-73
Author: Markku Heinisuo
Version: N486
Clauses: 4.2, 4.3, G; n/a, n/a, figure G.25; pp 21-, 70.
Classification: minor, technical
Description: Polygonal plates may only be defined as rectangular plates
which have one or more straight cuts applied to them.
Proposed solution: Define polygonal plates in terms of nodes and lines - in
other words, use explicit geometry.
Resolution: Open.
Date issue raised: 2 October 1996.
Issue number: Finland 230-74
Author: Risto Latva
Version: N486
Clauses: 4.2, 4.3, G; n/a, n/a, figures G.4; pp 21- , 49.
Classification: minor or major (depending on solution chosen), technical
Description: The current model prevents two or more Located_part objects
from using the same id, and prevents two or more Manufact_asbly objects from
using the same id. The current model also ensures that the combination of
Located_part id and Manufact_asbly id is unique. What the current model does
not forbid (and ought to) is a Located_part and a Manufact_asbly having the
same id.
Proposed solutions: (1) Write a rule which prevents a Located_part and a
Manufact_asbly from having the same id. (2) Create an unique identifying attribute
for a top level entity in the data model which will be inherited by all
(relevant) entities in the model. (see also issue 167)
Resolution: Open. (The whole question of ids for entities within the AP230
data model will need to be addressed)
Date issue raised: 24 October 1996
Issue number: Finland 230-75
Author: Risto Latva
Version: N486
Clauses: 4.2, 4.3, G; n/a, n/a, figures G.4; pp 21- , 49.
Classification: major, technical
Description: If the current model is used to hold manufacturing data
relating to a building with repeating assemblies (such as a portal frame
building) the relevant Manufact_asbly object need only be populated once. If,
however, the current model were used to hold constructional data relating to a
building with repeating assemblies, each of those assemblies would need to be
located, and the relevant Manufact_asbly object would need to be populated many
times. This would result in the creation of a great deal of redundant
information.
Proposed solution: Change the model in such a way that the entity
Manufact_asbly is replaced by two entities: Specific_manufact_asbly and
Located_manufact_asbly. In other words, find a mechanism which is analogous to
that used by S_part and Located_part
Resolution: Agreed.
Date issue raised: 24 October 1996.
Issue number: Finland 230-76
Author: Risto Latva
Version: N486
Clauses: 4.2, 4.3, G; n/a, n/a, figures G.2; pp 21- , 47.
Classification: minor, technical
Description: There is a fundamental distinction - in design terms - between
assemblies produced in a manufacturing shop (and transported to site) and those
put together on site. The current "construction_stage" attribute (of
the Assembly entity) allows any text description to be inserted.
Proposed solution: Replace the current description attribute with an
enumeration of "site" and "shop" (1) or with site_assembly
and shop _assembly subtypes (2).
Resolution: (1) Rejected). (2) Agreed.
Date issue raised: 24 October 1996.
Issue number: UK 230-77
Author: University of Leeds
Version: Nnew
Clauses: 4.2.1.12; p 23.
Classification: minor, technical
Description: Address 1: The Address attribute "mail_stop" does
not accord with latest version of 10303-41 18.4.1 which substitutes
"internal_location".
Proposed solution: Replace the current mail_stop attribute with an
internal_location attribute.
Resolution: Agreed.
Date issue raised: 27 February 1997.
Issue number: US 230-78
Author: Bill Houston
Version: Nnew
Clause: 4.2; p ??.
Classification: major, technical
Description: Current provision for loading within AP230 does not accord
with US practice.
Proposed solution: Change the AP230 data-model to accommodate US practice.
Resolution: Open.
Date issue raised: 17 May 1996.
Issue number: UK 230-79
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: major, technical
Description:. The current data model for AP230 does not allow for the
definition of shapes made up of circular arcs and straight line segments.
Proposed solution: Incorporate such a mechanism into AP230.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-80
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: minor, technical
Description: The current data model for AP230 does not allow for the
definition of a partial factor of safety for materials.
Proposed solution: Create such an attribute for Material.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-81
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: major, technical
Description: The current data model for AP230 does not allow for the
definition of non-standard profiles.
Proposed solution: Extend the data-model to allow for non-standard
profiles.
Resolution: Agreed.
Date issue raised: 19 May 1997.
Issue number: UK 230-82
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: major, technical
Description: The current data model for AP230 does not allow for the
definition of sections which are made up of a number of standard (and
non-standard) profiles.
Proposed solution: Extend the current data model to include such a
mechanism.
Resolution: Agreed.
Date issue raised: 19 May 1997.
Issue number: UK 230-83
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: minor, technical
Description: The current data model for AP230 does not allow for the
definition of areas for calculation of shear deformation ("Ax"
and "Ay").
Proposed solution: Create such attributes for Section_profile.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-84
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: major, technical
Description: The current data model for AP230 does not allow for the
definition of C profiles, Z profiles, or rails.
Proposed solution: Extend the current data model to include such profiles.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-85
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: minor, technical
Description: The current data model for AP230 does not allow for the
definition of "trading weights" for prismatic sections.
Proposed solution: Create such an attribute for Section_profile.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-86
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: minor, technical
Description: The current data model for AP230 does not allow for the
definition of warping values in boundary conditions ("Mw").
Proposed solution: Create such an attribute for Boundary_condition.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-87
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: major, technical
Description: The current data model for AP230 does not allow for the
definition of tapered prismatic analytical elements (although they can be
treated as "stepped" elements in the current model).
Proposed solution: Extend the current data model to include explicit
provision for tapered prismatic analytical elements.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-88
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: major, technical
Description: The current data model for AP230 does not allow for the
definition of actions (loads) due to imperfections.
Proposed solution: Extend the current data model to include such provision.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-89
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: major, technical
Description: The current data model for AP230 does not allow for the
definition of exceptional actions (loads).
Proposed solution: Extend the current data model to include such provision.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-90
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: minor, technical
Description: The current data model for AP230 does not allow for the
definition of nodal action (load) displacements.
Proposed solution: Extend the current data model to include such provision.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-91
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: minor, technical
Description: The current data model for AP230 does not allow for the
definition of element actions (loads) due to temperature.
Proposed solution: Extend the current data model to include such provision.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-92
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: minor, technical
Description: The current data model for AP230 does not allow for the
definition of nodal reaction values for warping ("Mw").
Proposed solution: Create such an attribute for Support_reaction.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-93
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: major, technical
Description: The current data model for AP230 does not allow for the
definition of curved prismatic members.
Proposed solution: Extend the current data model to include such provision.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-94
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: major, technical
Description: The current data model for AP230 does not allow for the
definition of a full range of non-rectangular plates (although simply polygons
can be created by skew cutting corners from rectangular plates).
Proposed solution: Extend the current data model to include such provision.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-95
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: minor, technical
Description: The current data model for AP230 does not allow for the
explicit selection of surface treatments from a specified range.
Proposed solution: Add an appropriate enumeration to the existing data
model.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-96
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: major, technical
Description: The current data model for AP230 does not allow for the
definition of non-rectangular notches.
Proposed solution: Extend the current data model to include such provision.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-97
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: major, technical
Description: The current data model for AP230 does not allow for the
definition of countersunk holes.
Proposed solution: Add appropriate attributes to the Hole entity.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-98
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: major, technical
Description: The current data model for AP230 does not allow for the
explicit selection of different methods of hole cutting.
Proposed solution: Add an appropriate enumeration to the current data
model.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-99
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: major, technical
Description: The current data model for AP230 does not allow for the
definition of cold bends.
Proposed solution: Extend the current data model to include such provision.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-100
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: minor, technical
Description: The current data model for AP230 does not allow for the
explicit definition of the distance between two edge chamfers applied to a part
in preparation for a double sided weld.
Proposed solution: Add an appropriate attribute to Edge_chamfer.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-101
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: major, technical
Description: The current data model for AP230 does not provide an adequate range
of facilities for describing bolts according to codes and standards.
Proposed solution: Extend the current model to include a greater range of
attributes for capturing information relating to international codes and
standards.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-102
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: minor, technical
Description: The current data model for AP230 does not allow for the
definition of whether or not deformation is "permitted" in bolts
(further clarification is being sought - from the German Steel Construction
Association "DSTV" - on this issue).
Proposed solution: Add an appropriate attribute to the Bolt entity.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-103
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: minor, technical
Description: The current data model for AP230 and does not allow for the
definition of "a friction-grip value" ("my") (further
clarification is being sought - from the German Steel Construction Association
"DSTV" - on this issue).
Proposed solution: Add an appropriate attribute to the Bolt entity.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-104
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: minor, technical
Description: The current data model for AP230 does not allow for the
explicit definition of "effective bolt diameter" .
Proposed solution: Add an appropriate attribute to the Bolt entity.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-105
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: major, technical
Description: The current data model for AP230 does not allow for the
explicit definition of "bolt grip length".
Proposed solution: Add an appropriate attribute to the Bolt entity.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-106
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: minor, technical
Description: The current data model for AP230 does not allow for the
explicit selection of many different types of weld preparation and methodology
.
Proposed solution: Add an appropriate enumeration to the Weld entity.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-107
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: minor, technical
Description: The current data model for AP230 does not allow for the
explicit selection of different cross-sectional shapes of weld - concave,
convex etc.
Proposed solution: Add an appropriate enumeration to the Weld entity.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-108
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: major, technical
Description: The current data model for AP230 does not allow for the
definition of weld thickness.
Proposed solution: Add an appropriate attribute to the Weld entity.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-109
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: major, technical
Description: The current data model for AP230 and the CIS does not allow
for the explicit definition of the distance between individual seams in the
case of an intermittent weld.
Proposed solution: Extend the current model to include explicit provision
for intermittent welds and add an appropriate attribute.
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-110
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: major, technical
Description:
Proposed solution:
Resolution: Open.
Date issue raised: 19 May 1997.
Issue number: UK 230-111
Author: LU
Version: Nnew
Clause: 4.2; p ??.
Classification: major, technical
Description:
Proposed solution:
Resolution: Open.
Date issue raised: 19 May 1997.
This page is maintained by M A Ward
Last updated 7 August 1997
To the AP230 Project Home Page
To the Civil Engineering
Home Page