DBIntegrity PDF
DBIntegrity PDF
Copyright
Copyright 2000-2011 Intergraph Corporation. All Rights Reserved. Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement; contains confidential and proprietary information of Intergraph and/or third parties which is protected by copyright law, trade secret law, and international treaty, and may not be provided or otherwise made available without proper authorization from Intergraph Corporation. Portions of this software are owned by Spatial Corp. 1986-2010. All Rights Reserved.
Terms of Use
Use of this software product is subject to the End User License Agreement ("EULA") delivered with this software product unless the licensee has a valid signed license for this software product with Intergraph Corporation. If the licensee has a valid signed license for this software product with Intergraph Corporation, the valid signed license shall take precedence and govern the use of this software product. Subject to the terms contained within the applicable license agreement, Intergraph Corporation gives licensee permission to print a reasonable number of copies of the documentation as defined in the applicable license agreement and delivered with the software product for licensee's internal, non-commercial use. The documentation may not be printed for resale or redistribution.
Trademarks
Intergraph, the Intergraph logo, PDS, SmartPlant, FrameWorks, I-Convert, I-Export, I-Sketch, SmartMarine, IntelliShip, INtools, ISOGEN, MARIAN, SmartSketch, SPOOLGEN, SupportManager, and SupportModeler are trademarks or registered trademarks of Intergraph Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows are registered trademarks of Microsoft Corporation. ACIS is a registered trademark of SPATIAL TECHNOLOGY, INC. Infragistics, Presentation Layer Framework, ActiveTreeView Ctrl, ProtoViewCtl, ActiveThreed Ctrl, ActiveListBar Ctrl, ActiveSplitter, ActiveToolbars Ctrl, ActiveToolbars Plus Ctrl, and ProtoView are trademarks of Infragistics, Inc. Incorporates portions of 2D DCM, 3D DCM, and HLM by Siemens Product Lifecycle Management Software III (GB) Ltd. All rights reserved. Gigasoft is a registered trademark, and ProEssentials a trademark of Gigasoft, Inc. VideoSoft and VXFlexGrid are either registered trademarks or trademarks of ComponentOne LLC 1991-2009, All rights reserved. Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle Corporation and/or its affiliates. Tribon is a trademark of AVEVA Group plc. Alma and act/cut are trademarks of the Alma company. Other brands and product names are trademarks of their respective owners.
Contents
Preface ........................................................................................................................................................ 23 SmartMarine 3D Documentation Set .................................................................................................... 24 Documentation Comments ................................................................................................................... 27 SmartMarine 3D and Oracle ................................................................................................................. 28 What's New in Database Integrity ............................................................................................................ 29 Understanding Database Integrity ........................................................................................................... 31 Workflow for Addressing Database Integrity ......................................................................................... 33 Database Integrity Custom Commands ................................................................................................ 35 Check Database Integrity...................................................................................................................... 35 Database Integrity ................................................................................................................................. 36 Check Data Consistency Dialog Box .............................................................................................. 37 Check Database Integrity ............................................................................................................... 38 Schedule Check Data Consistency Task Using Batch Services .................................................... 38 Clean a Database ................................................................................................................................. 39 Clean Database Dialog Box ........................................................................................................... 39 Find Objects by Report ......................................................................................................................... 40 Run Database Administration Processes (Matrix) ................................................................................ 41 CommonApp .............................................................................................................................................. 43 Control point does not have a parent .................................................................................................... 43 Hierarchy filter with missing Adapter ProgId ......................................................................................... 44 Invalid number of related objects .......................................................................................................... 44 LineFeature doesn't have minimum number of TurnPoints .................................................................. 45 Name rule AE is not associated to a named item ................................................................................. 45 Note does not have a parent................................................................................................................. 46 Only one as-built object allowed in a model ......................................................................................... 46 PointFeature has no TurnPoint associated with it ................................................................................ 47 Sketch3d is not associated to SketchByPointsAE ................................................................................ 48 Sketch3d Point is not associated to a TurnPoint .................................................................................. 48 SketchByPointsAE is not associated to Sketch3d ................................................................................ 49 SketchByPointsAE requires minimum two input points ........................................................................ 49 TurnPoint can have one or two LineFeatures associated with it .......................................................... 50 TurnPoint is not associated to a Point .................................................................................................. 51 WBS Item does not have a parent ........................................................................................................ 51 WBS Project does not have a parent .................................................................................................... 52 Common Route .......................................................................................................................................... 53 Added port with no object connected .................................................................................................... 53 Attach connection without 2 ports ......................................................................................................... 53 Branch feature not at end of leg............................................................................................................ 54 Branch Feature with no corresponding Along Leg Feature .................................................................. 54 Connection associated with only one port ............................................................................................ 55 Connection has relation to Specification ............................................................................................... 55
Contents
Connection Item missing relation to catalog part .................................................................................. 56 Connection Item missing relation to the object ..................................................................................... 56 Connection Items not associated to the owner part.............................................................................. 57 Connection not associated with a port .................................................................................................. 58 Connection not associated with a run ................................................................................................... 58 Connection not connected to correct parent ......................................................................................... 59 Connection not having valid connection size ........................................................................................ 59 Connection PG/AS not same as connected parts or owner ................................................................. 60 Dormant Part associated to the Feature ............................................................................................... 60 End/Branch/Turn feature not a Terminating Feature of the leg ............................................................ 61 Feature not associated with a Leg ........................................................................................................ 61 Feature not associated with a run ......................................................................................................... 62 Feature with branch parent function did not generate part occurrence ................................................ 63 Feature with component Function did not generate component occurrence ....................................... 63 Feature with end leg function did not generate component occurrence ............................................... 64 Feature with user specified parts did not generate part occurrence..................................................... 65 Feature with zero outer diameter .......................................................................................................... 65 Feature without UserSpecifiedPart Relation ......................................................................................... 66 Inline feature & Branch Feature belong to same leg ............................................................................ 67 Intermediate End Feature and Connected Intermediate End Feature generating part ........................ 67 Invalid Zero Length Straight Feature .................................................................................................... 68 Leg with features belonging to multiple runs ........................................................................................ 68 Leg with no associated features ........................................................................................................... 69 Need to remove the RelConnectionAndPartOcc between the cableocc and the Distribconn ............................................................................................................................................ 69 No connection items generated by the connection ............................................................................... 70 Objects with invalid cross sectional parameters ................................................................................... 70 Parent Connection is generating Non-BoltSet Connection Items ......................................................... 71 Part and Feature data is not matching .................................................................................................. 72 Part not associated with a feature......................................................................................................... 72 Part not associated with a run............................................................................................................... 73 PipeSurfaceMount Feature without Attach Connection ........................................................................ 73 Ports with no association to Parts ......................................................................................................... 74 Route part missing relation with ports ................................................................................................... 74 Route part occurrence with missing relation to Catalog part ................................................................ 75 Route part occurrence with missing relation to Material Control Data .................................................. 75 Route part occurrence with wrong made relation name ....................................................................... 76 Route part occurrence with wrong permission group or approval status.............................................. 76 Run with no feature that has an entry in the Spatial Index table (Range) ............................................ 77 Run without specification ...................................................................................................................... 78 Run without system parent ................................................................................................................... 78 Straight feature generating a mating part ............................................................................................. 79 Straight feature not generating stock part occurrence .......................................................................... 79 SurfaceMount Feature not connected to Inline Feature ....................................................................... 80 Tap Feature with no association to Tapped Feature ............................................................................ 80 Turn Feature Angle is very small .......................................................................................................... 81 Turn feature missing primary leg association ....................................................................................... 81 Turn Feature not associated to two legs ............................................................................................... 82 Common Space ......................................................................................................................................... 83 Active Entity has no Space Geometry associated with it ...................................................................... 83 Hierarchical Loop Detected ................................................................................................................... 83 Space Association Active Entity has no Graphic Object....................................................................... 84
Contents
Space Association Active Entity has no Space Entity associated to the Graphic Object ..................... 85 Space Boolean Operator does not have a Space Geometry ............................................................... 85 Space Boolean Operator is not connected to Space By Boolean Active Entity ................................... 86 Space By Boolean Active Entity is not connected to Space Boolean Operator ................................... 86 Space By Path Active Entity does not have Path ................................................................................. 87 Space By Path Active Entity has no CrossSection ............................................................................... 88 Space By Plane and Offset Active Entity does not have the Fence input Points ................................. 88 Space By Plane and Offset Active Entity does not have the Reference Plane .................................... 89 Space By Points Active Entity has no input Points ............................................................................... 89 Space By Primitive Active Entity has no Geometry .............................................................................. 90 Space Entity does not have a Catalog Part .......................................................................................... 90 Space Entity does not have Range ...................................................................................................... 91 Space Entity does not have Space Geometry ...................................................................................... 92 Space Geometry has no Active Entity associated with it ...................................................................... 92 Space Geometry is not connected to any Space Entity........................................................................ 93 Space Object does not have Local coordinate system ......................................................................... 93 Space object has two parents ............................................................................................................... 94 SpaceChild does not have a Parent ..................................................................................................... 94 SpatialOrientation is not connected to a Space Object or Sketch3d object ......................................... 95 Common Structure .................................................................................................................................... 97 Bad StructPortSelector permission group ............................................................................................. 97 Missing relation between Structcutoutcontour object and openingtype object ..................................... 98 Opening without any OpeningType relation .......................................................................................... 98 Orphaned Sketched Cutout Contour not related to CutoutAE .............................................................. 99 Orphaned Structural connection is not associated to any port (IJPort) ................................................ 99 Sketched Cutout Contour is not associated to any symbol ................................................................ 100 Sketched Cutout Contour is not related to SketchWireBodyOutput geometry ................................... 100 StandAlone Struct Generation Active Entity has no parent input ....................................................... 101 StandAlone Struct Operation Active Entity has no Operand input ..................................................... 101 StandAlone Struct Port not associated to a StructPortSelector AE .................................................... 102 StandAlone StructGenericEntity not associated to a Struct Generic Geometry ................................. 103 StandAlone StructPortSelector not associated to a StructGenericEntity............................................ 103 Compartmentation ................................................................................................................................... 105 Compart By Path Active Entity does not have Path Object ................................................................ 105 Compart By Path Active Entity has no Sketch CrossSection Object .................................................. 106 Compart By Points Active Entity has no input Points ......................................................................... 106 Compart By Primitive Active Entity has no Compart Geometry.......................................................... 107 Compart Entity has no Compart Geometry......................................................................................... 108 Compart Geometry has no Compart Entity ......................................................................................... 108 Compart Geometry has no Geometry ................................................................................................. 109 Compart Geometry has no Space CreationAE ................................................................................... 109 CompartBoolOperator has no Compart Geometry or Geometry ........................................................ 110 CompartBoolOperator has no CompartByBooleanAE Object ............................................................ 111 CompartBoundByFace has no CompartByBound object ................................................................... 111 CompartBoundByFace has no CompartByBound or CompartBySplit ................................................ 112 CompartBoundByFace has no Geometry ........................................................................................... 112 CompartByBooleanAE has no CompartBoolOperator ........................................................................ 113 CompartByBooleanAE has no CompartGeometry Object .................................................................. 113 CompartByBound has no Compart Geometry .................................................................................... 114 CompartByBound has no CompartByBoundFace Object ................................................................... 115
Contents
CompartByBound is associated with the temporary geometry ........................................................... 115 CompartByImport Active Entity has no Compart Geometry ............................................................... 116 CompartByImportAE has no Point object ........................................................................................... 116 CompartByPathAE has no Compart Geometry .................................................................................. 117 CompartByPoints has no Compart Geometry object .......................................................................... 118 CompartByPrimitive has no CompartShapeDef object ....................................................................... 118 CompartGeometry has no CompartBySplitAE .................................................................................... 119 CompartSplitAE has no CompartBoundByFace ................................................................................. 119 CompartSplitAE has no CompartGeometry ........................................................................................ 120 CompartSplitAE is associated with the temporary geometry.............................................................. 121 Spatial Load Combination object has no parent(Load Folder) object ................................................ 121 Spatial Load Folder object has no Parent (Configure Project Root or Load Folder) object ................................................................................................................................................... 122 Spatial Load object has no Compart Geometry object ....................................................................... 122 Spatial Load object has no Parent object ........................................................................................... 123 Core........................................................................................................................................................... 125 Error on symbol internal object ........................................................................................................... 125 Error on symbol relation ...................................................................................................................... 126 Generic SmartPlant Error .................................................................................................................... 126 Graphic object is an orphan ................................................................................................................ 127 Object has an unexpected relation ..................................................................................................... 128 Object has invalid geometry................................................................................................................ 128 Object is not accessible ...................................................................................................................... 129 Object naming error ............................................................................................................................ 129 SmartPlant Error : Cardinality violation in design basis relation ......................................................... 130 SmartPlant Error : Dead object or correlation wrong .......................................................................... 130 SmartPlant Error : Multiple objects with the same name .................................................................... 131 SmartPlant Error : Multiple view files with same name ....................................................................... 132 SmartPlant Error: Multiple objects with the same name ..................................................................... 132 The object does not exist but another object has a relation to it ........................................................ 133 The proxy does not have a parent; therefore, it cannot find its source............................................... 134 The proxy exists but is not connected to any other object .................................................................. 134 Drawings and Reports ............................................................................................................................ 137 Blob in the DocumentData object table is not valid ............................................................................ 137 Child Property object's approval status or permission group does not match with the parent Property Object ........................................................................................................................ 137 Doc Output Mgr has duplicate data documents.................................................................................. 138 Document Output Manager object has duplicate generated document relations ............................... 139 Document Output Manager object's approval status or permission group does not match with the owning SnapIn or Sheet object................................................................................... 139 DocumentData object's approval status or permission group does not match with Document Output Manager ................................................................................................................. 140 Drawing Issue object's approval status or permission group does not match with Property Object Child .......................................................................................................................... 141 Drawing Key Plan View object's approval status or permission group does not match with Drawing View object .................................................................................................................... 141 Drawing object has duplicate relations ............................................................................................... 142 Drawing Revision object's approval status or permission group does not match with Property Object Child .......................................................................................................................... 143
Contents
Drawing View Info object's approval status or permission group does not match with Drawing View object ........................................................................................................................... 143 Drawing View object's approval status or permission group does not match with Drawing Sheet object .......................................................................................................................... 144 Drawing View on Drawing Component Template has Overrides ....................................................... 145 Drawing Volume object's approval status or permission group does not match with Drawing View object ........................................................................................................................... 146 Element Broker object's approval status or permission group does not match with Drawing View object ........................................................................................................................... 147 Missing Filter on Drawings by QueryManager with children ............................................................... 148 Property object's approval status or permission group does not match with Drawing Sheet or SnapIn .................................................................................................................................. 148 PropertyChild entity has no parent PropertyObject ............................................................................ 149 PropertyObject has no associated SnapIn or Sheet ........................................................................... 150 Report object's approval status or permission group does not match with View Generator object ................................................................................................................................. 150 Report Template object's approval status or permission group does not match with Drawing View object ........................................................................................................................... 151 Sheet entity has no associated parent SnapIn ................................................................................... 152 SnapIn entity has no associated parent .............................................................................................. 152 SnapIn entity has no associated PropertyObject ................................................................................ 153 Snapshot view is not associated to a volume ..................................................................................... 154 Template Manager object's approval status or permission group does not match with Parent Drawing Type or Sheet............................................................................................................ 154 Template Mgr object has no parent Snapin or Sheet ......................................................................... 155 Template Sheet is corrupted ............................................................................................................... 156 Equipment and Furnishings ................................................................................................................... 157 Assembly Constraint is not associated to a part occurrence .............................................................. 157 Cable Nozzle does not have proper orientation values ...................................................................... 158 Conduit Nozzle does not have proper orientation values ................................................................... 158 Design Equipment has Invalid Range ................................................................................................. 159 Equipment does not have a system parent ........................................................................................ 159 Equipment has DBL_UNDEFINED values persisted for CG value .................................................... 160 Equipment is not associated to a part ................................................................................................. 161 Equipment or Equipment component does not have a coordinate system ........................................ 162 Equipment ports do not have a parent ................................................................................................ 163 Error code 58 - unspecified error description ...................................................................................... 163 Invalid WCGProperties for the object that has valid weight and CG .................................................. 164 Nozzle is not associated to an EFCorrelation object .......................................................................... 165 Orphaned Nozzle ................................................................................................................................ 165 Permission Group of the object is different from the Parent Object ................................................... 166 Permission Group of the shape is different from the corresponding Smart Equipment ..................... 166 Shape does not have an equipment parent ........................................................................................ 167 Smart Equipment has a missing relation with symbol sub system ..................................................... 168 Smart Item associated to Equipment has different permission group ................................................ 168 Geometry and Topology ......................................................................................................................... 171 Cannot enclose void to construct a solid ............................................................................................ 171 Cannot stitch and orient the given surface bodies .............................................................................. 172 Model body has no topology ............................................................................................................... 172 Model body is self-intersecting............................................................................................................ 173
Contents
Model geometries do not intersect ...................................................................................................... 173 Model geometries do not overlap........................................................................................................ 174 Unexpected failure in GeomOperations module ................................................................................. 174 Grids ......................................................................................................................................................... 177 Coordinate System contains some Planes/Cylinders at same position.............................................. 177 Object does not have the requested data ........................................................................................... 178 Object does not have the requested relation ...................................................................................... 180 Object has invalid geometry................................................................................................................ 182 Hangers and Supports ............................................................................................................................ 183 Active entity with no Leg ..................................................................................................................... 183 Active entity with no outputs ............................................................................................................... 183 Active entity with no supported entities ............................................................................................... 184 Component without WBSProjectChild and WBSItemChild ................................................................. 184 Connection without support ................................................................................................................ 185 Corrupted Hanger Connections .......................................................................................................... 185 Duplicate relations exist in the database ............................................................................................ 186 Hierarchical Loop Detected ................................................................................................................. 187 Joint exists without a support .............................................................................................................. 187 Occurrence Assembly without part ..................................................................................................... 188 Orphaned Hanger Port(s) ................................................................................................................... 188 Support as an assembly child, but not being a parent ........................................................................ 189 Support Component with no Support .................................................................................................. 189 Support exists without active entity ..................................................................................................... 190 Support exists without joint ................................................................................................................. 190 Support has no components ............................................................................................................... 191 Support not associated to a definition ................................................................................................. 191 Support without CoordinateSystem .................................................................................................... 192 Support without Name ........................................................................................................................ 192 SupportPort without Support ............................................................................................................... 193 SupportPort without SupportComponent ............................................................................................ 193 Wrong ComponentToSupportedPort Relation .................................................................................... 194 Hole Management .................................................................................................................................... 195 The Approved hole is missing a relationship to the structure part being cut ...................................... 195 The catalog fitting is missing a connection to the pipe part ................................................................ 196 The center flange is missing a connection to the pipe part ................................................................ 196 The hole has an invalid application value ........................................................................................... 197 The hole has an invalid cut status value ............................................................................................. 198 The hole has an invalid fitting type value ............................................................................................ 198 The hole has an invalid status value ................................................................................................... 199 The sketched hole is missing the relationship to its outline ................................................................ 199 The hole is missing the clearance rule to be used.............................................................................. 200 The hole is missing the fitting selection rule to be used ..................................................................... 201 The object should be in the HoleManagement PermissionGroup ...................................................... 201 The pipe part is missing a connection to the fitting ............................................................................. 202 The sketched hole is missing the relationship to its outline ................................................................ 203 Interference Checking ............................................................................................................................. 205 Bad part Interference has no part ....................................................................................................... 205
Contents
Interference has only one part and not in Todo List ........................................................................... 206 Molded Forms .......................................................................................................................................... 207 A Beam does not have a related BeamSystemAE ............................................................................. 207 A BracketByPlane PlateSystem does not have a ReferenceCollection to its symbol ........................ 208 A BracketByPlane PlateSystem does not have the necessary two points defined ............................ 208 A BracketByPlane PlateSystem has too many points defined ........................................................... 209 A BracketByPlane PlateSystem has too many relationships to ReferenceCollections ...................... 210 A BracketByPlane PlateSystem's point is not an input to the symbol ................................................ 210 A connection has less than two ports ................................................................................................. 211 A Connection has more than 2 Ports associated to it ......................................................................... 212 A CreatePlatePartAE does not have a related plane.......................................................................... 212 A CreatePlatePartAE does not have any related trim boundaries ...................................................... 213 A Design- or Planning-split operation exists with no related operand ................................................ 214 A Design- or Planning-split operation with a seam has less than two results .................................... 214 A Design- or Planning-split operation without a seam does not have one result ............................... 215 A Flanged Plate AE exists without a relationship to a Plate ............................................................... 216 A Flanged Plate exists without a symbol for the flange ...................................................................... 216 A Flanged Plate exists without the start or end points defined ........................................................... 217 A Flanged Plate exists without updated output................................................................................... 218 A GeneratePlatePart_AE does not have a related PlateSystem ........................................................ 219 A LandCrvPoint does not have a related PointOnSurfByTwoCoords_AE .......................................... 219 A LandCrvTableAE does not have related LandCrvPoints ................................................................. 220 A Landing Curve AE does not have the Parent0 relationship ............................................................ 221 A Landing Curve AE does not have the Parent1 relationship ............................................................ 221 A Landing Curve AE does not have the Parent2 relationship ............................................................ 222 A LandingCurve ActiveEntity does not have a related base curve ..................................................... 223 A LandingCurve ActiveEntity does not have a related geometry ....................................................... 223 A Name has not been defined for this object ...................................................................................... 224 A Plate bound operation exists with no related operand .................................................................... 225 A Plate bound operation exists with no related result ......................................................................... 225 A plate bound to another plate is missing the connection .................................................................. 226 A Plate could be missing a sketched boundary .................................................................................. 228 A Plate cutout operation exists with no related operator .................................................................... 229 A plate part does not have a related PlatePartReportData object ...................................................... 229 A Plate system exists with no related planning split or light part ........................................................ 230 A PlateGeometry does not have a related PlanningSplitAE ............................................................... 231 A PlateGeometry object exists without having a related ActiveEntity or Structural Entity ............................................................................................................................................................ 231 A PlatePartGeometry does not have a related CreatePlatePart_AE.................................................. 232 A PlateSystem does not have a related MoldedSpec......................................................................... 233 A PlateSystem exists with less than 3 or more than 5 shared attributes ............................................ 234 A point for BracketByPlane is not related to a PlateSystem ............................................................... 235 A point for BracketByPlane is not related to a PlateSystem or any other object ................................ 235 A PointOnSurfByTwoCoords_AE does not have a related base plate ............................................... 236 A profile does not have a related child connection ............................................................................. 237 A profile part does not have a related ProfilePartReportData object .................................................. 237 A Profile split ActiveEntity does not have a related profile system ..................................................... 238 A Profile system exists with no related planning split or light part ...................................................... 239 A ProfilePartCreation does not have a related base plate .................................................................. 239 A ProfilePartCreation does not have a related profile part ................................................................. 240 A ProfilePartGeneration_AE does not have a related plate system ................................................... 241 A ProfilePartGeneration_AE does not have a related PlateGeometry ............................................... 242
Contents
A ProfilePartGeneration_AE does not have a related profile system ................................................. 243 A ProfilePartGeometry does not have a related ActiveEntity ............................................................. 243 A ProfileSystem does not have a related Plate .................................................................................. 244 A ProfileSystem exists with a connection on its end port that is split ................................................. 245 A ProfileSystem exists with less than 3 or more than 6 shared attributes .......................................... 245 A ProfileSystemAE does not have a related ProfileSystemRegion .................................................... 246 A RefCurveOnSurface does not have a related PlateSystem ............................................................ 247 A ReferenceCollection for BracketByPlane is not related to a PlateSystem ...................................... 247 A ReferenceCollection for BracketByPlane is not related to a PlateSystem or any other object ................................................................................................................................................... 248 A SeamPoint AE does not have a related SeamPointGeometry ........................................................ 249 A SeamPoint does not have a related SeamPointGeometry.............................................................. 249 A SeamPointAE does not have a related profile system .................................................................... 250 A SeamPointAE does not have a related surface............................................................................... 251 A SeamPointOffsetAE does not have a related LandingOffset .......................................................... 251 A split ActiveEntity does not have a related Seam ............................................................................. 252 A StiffenerPart exists that is related to more than one StructPortAE ................................................. 253 A StructPort exists without a related StructPortAE ............................................................................. 253 A StructPort exists without a related system ...................................................................................... 254 A StructPortAE exists without having related geometry ..................................................................... 255 A Structural Connection exists that is not in the SystemHierarchy..................................................... 256 A system does not have a related child part ....................................................................................... 257 Alternate Point has no relation to the ProfileByTable AE anymore .................................................... 258 An ActiveEntity does not have a related plate operand ...................................................................... 259 An ActiveEntity exists with no related operand ................................................................................... 259 An ActiveEntity exists with no related result ....................................................................................... 260 An ActiveEntity exists with no related result and no operand ............................................................. 261 An EdgeReinforcement does not have a related LandCrvER_AE ..................................................... 261 An IJShellMoldedConventions Attribute Bag found on non-hull plate ................................................ 262 An object does not have a related LandingCurve ............................................................................... 263 An object does not have a related material ........................................................................................ 263 An object does not have a related PlateGeometry ............................................................................. 265 An object does not have a related PlateGeometry nor a parent system ............................................ 265 An object does not have a related profile symbol ............................................................................... 266 An object does not have a related StructPort_AE .............................................................................. 267 An object exists that is not in the SystemHierarchy ............................................................................ 267 An opening occurrence does not have a related PlateCutoutAE ....................................................... 268 An opening occurrence has relationships that point to different struct geometry ............................... 269 An unnecessary relationship exists in the database ........................................................................... 269 Beam axis rule type not defined.......................................................................................................... 270 Beam does not have an orientation .................................................................................................... 270 Beam Orientation does not have Flip U defined ................................................................................. 271 Beam Orientation does not have Flip V defined ................................................................................. 272 BracketByPlane PlateSystem is not an input to the symbol's ReferenceCollection via StructSymbolInput2 ............................................................................................................................. 272 BracketByPlane PlateSystem's ReferenceCollection has no symbol inputs ...................................... 273 BracketByPlane PlateSystem's ReferenceCollection is not related to a ReferenceCollection for the symbol .................................................................................................... 274 BracketByPlane PlateSystem's symbol is not a BracketByPlane symbol .......................................... 274 BracketByPlane PlateSystem's PlaneByOffset PlateGeometry is not an input to the symbol's ReferenceCollection ............................................................................................................. 275 Cannot get Cross Section Symbols for Profiles and Beams .............................................................. 276 Design- or Planning-split operation without a seam does not have one result ................................... 277
10
Contents
Duplicate PlateBound_OPER3 relationships exist between the same two objects ............................ 277 Duplicate ShpStrDesignHierarchy relationships exist between the same two objects ....................... 278 EdgeReinforcement is missing Attribute ............................................................................................. 279 Extra/Orphaned group monitors exist ................................................................................................. 279 Hull Plate System does not have Shell Molded Conventions defined ................................................ 280 LinearExtrusion AE does not have a retrievable MotherCurve ........................................................... 281 No Geometry filename is stored with an object that has imported geometry ..................................... 281 Object has multiple structural naming Hierarchy Parent relationships ............................................... 282 Object has multiple structural naming reference controllers (active entities) ..................................... 283 Object is related to a port with a bag of bytes--should be related to connectable port ....................... 283 Orphaned SructPlane3d objects ......................................................................................................... 284 PlaneBy2PtsProjDir_AE does not have a related Frame Axis ........................................................... 285 PlaneBy2PtsProjDir_AE does not have a related Plane .................................................................... 285 PlaneBy2PtsProjDir_AE does not have related Normal Vector .......................................................... 286 PlaneBy2PtsProjDir_AE does not have related Points On Surface ................................................... 287 PlaneBy2PtsProjDir_AE output Plane is not related to a landing curve ............................................. 287 Plate has no dimensions ..................................................................................................................... 288 Plate LinearExtrusion AE is missing its Mother Curve........................................................................ 290 Plate Part has no dimensions ............................................................................................................. 290 Plate System cannot be used as a seam boundary ........................................................................... 291 Plate System does not have Molded Conventions defined ................................................................ 292 PlatePart has no Geometry associated to it ....................................................................................... 293 PlatePartGeometry is missing active entity and is unable to update .................................................. 293 PlatePartGeometry is missing CreatePlatePart_AE and is unable to Update .................................... 294 PlateSystem does not have its IJPlate attributes set .......................................................................... 295 PlateSystem has no PlatePart via GraphicsMap ................................................................................ 295 Profile by Projection is missing its Sketched curve............................................................................. 296 Profile leaf system is not on PartGeneration_OPER relationship....................................................... 297 ProfileKnuckle does not have a related ProfileLanding Curve ........................................................... 297 ProfileSystem active entity is not related to a trace curve or a beam geometry................................. 298 ProfileSystem is not related to the Design nor the Planning Split AEs ............................................... 299 ProfileSystem or an EdgeReinforcement System does not have a relationship to a ProfileSystem active entity .................................................................................................................. 299 Rotation Angle is not set for Beam ..................................................................................................... 300 Seam by Projection AE is missing its Sketched curve........................................................................ 301 Seam by Projection is missing its Sketched curve ............................................................................. 301 Seam does not have a related SeamLandCurve ................................................................................ 302 SeamAE does not have a related CSeamLandCrv ............................................................................ 303 SeamByTable_AE does not have a related LandCrvPoints ............................................................... 303 SeamGeometry_AE does not have related Plate Entity ..................................................................... 304 SeamGeometry_AE does not have a related Seam Entity ................................................................. 304 SeamIntersection_AE does not have a related PlateGeometry ......................................................... 305 SeamLandCrv does not have a related Generation/StructOperation AE ........................................... 305 SeamOffset_AE does not have a related LandingOffset .................................................................... 306 SeamOffset_AE does not have a related PlateGeometry .................................................................. 306 SeamProject_AE does not have a related PlateGeometry................................................................. 307 Secondary class object in CoreSpatialIndex table.............................................................................. 307 Shared Attribute found on object that does not require it ................................................................... 308 StructContinuity type/priority not being set on a Root System ........................................................... 309 Structural Port exists without relating to a Connectable Business Object .......................................... 310 System-derived part missing parent system - needs user attention ................................................... 310 The Logical Connection does not have the user class set ................................................................. 311 The object should be in the MoldedForms PermissionGroup ............................................................. 312
11
Contents
The root logical connection is using a leaf system port instead of a root system port ....................... 312 There is a duplicate relationship between the same two objects ....................................................... 313 Unnecessary object is added to the To Do List .................................................................................. 314 Molded Forms Permission Group Messages ...................................................................................... 314 CreateCollar_AE PG does not match with CollarPart PG ............................................................ 314 CreatePlatePart_AE PG does not match with Plate Part PG....................................................... 315 Custom Component PG does not match PG of Sketched Feature .............................................. 316 Cut_AE PG does not match Feature PG ...................................................................................... 316 Design/Planning Split_AE PG does not match with System PG .................................................. 317 Detailing AE PG does not match with Plate Part PG ................................................................... 318 Edge Treatment PG does not match PG of parent (Part/Edge Feature) ..................................... 318 Feature Definition Point (Input) PG does not match with Feature PG ......................................... 319 Feature Definition Point (Output) PG does not match with Feature PG ...................................... 320 Free end cuts PG does not match Part PG .................................................................................. 320 HierarchyNamingAE PG does not match PG of Relation Destination ......................................... 321 Last Geometry PG does not match PG of the Object .................................................................. 322 NameRuleAE PG does not match PG of Relation Destination .................................................... 322 Operation_AE PG does not match with Plate System PG ........................................................... 323 PartReportData PG does not match with Part PG ....................................................................... 323 PG of Feature on FreeEndCut does not match with Part PG ...................................................... 324 PG of Geometry after Operation_AE does not match with PG of Seam ...................................... 325 PG of Geometry after ProfilePartGeneration_AE does not match with PG of Profile Part ............................................................................................................................................... 325 PG of LC created by seams does not match with the Parent PG ................................................ 326 PG of PlatePartGeometry after CreatePlatePart_AE does not match with PG of Plate Part ...................................................................................................................................... 327 PG of Seam LandCrvBound_AE does not match with PG of Plate Part ...................................... 327 Plate Knuckle PG does not match with Plate System PG............................................................ 328 PlateBound_AE / PlateCutOut_AE InPut Geometry PG does not match with Plate System PG ................................................................................................................................... 329 PlateBound_AE / PlateCutOut_AE PG does not match with Plate System PG........................... 329 PlateCutOut_AE InPut Geometry PG does not match with Plate System PG ............................. 330 PlateCutOut_AE PG does not match with Plate System PG ....................................................... 331 PlatePartGeometry PG does not match with Plate Part PG ........................................................ 331 Profile Knuckle PG does not match with Profile System PG........................................................ 332 ProfileKnuckle LandingCurve does not match with Profile System PG ....................................... 333 ProfilePartGeneration_AE PG does not match with Profile Part PG ........................................... 333 ProfileTrim_AE PG does not match PG of Profile Struct Feature ................................................ 334 Seam landing offset PG does not match with PG of Seam.......................................................... 335 Seam Operation_AE PG does not match with PG of Seam ........................................................ 335 SeamGeometry_AE PG does not match with Seam PG ............................................................. 336 Sketch feature PG does not match with Part PG ......................................................................... 337 SketchReferenceCol PG does not match PG of Sketched Feature ............................................. 337 StdPlateSystemNamingAE PG does not match PG of StdPlateSystem ...................................... 338 StrikeSplit_AE PG does not match with SeamSeamPoint PG ..................................................... 339 The AC PG does not match the Part PG...................................................................................... 339 The Beam Point3d PG does not match with Beam Stand Alone Part PG ................................... 340 The BeamAssoc Point PG does not match with BeamSystem PG .............................................. 341 The BeamGeneration_AE PG does not match with Beam Stand Alone Part PG ........................ 341 The BeamGeneration_AE PG does not match with BeamSystem PG ........................................ 342 The BeamLandCurve_Input PG does not match with BeamSystem PG ..................................... 343 The BeamLandingCrv PG does not match with BeamSystem PG .............................................. 343
12
Contents
The BeamStandAlonePart_AE PG does not match with Beam Stand Alone Part PG ...................................................................................................................................................... 344 The BeamSystem_AE PG does not match with Beam System PG ............................................. 345 The BracketByPlane definition point PG does not match the BracketByPlane PG ..................... 345 The BracketByPlane definition ReferenceCollection PG does not match the BracketByPlane PG ...................................................................................................................... 346 The child LC PG does not match with the root LC PG ................................................................. 347 The collar PG does not match Part PG ........................................................................................ 347 The feature PG does not match with its part PG .......................................................................... 348 The IntersectionAE PG does not match with Feature PG ............................................................ 349 The LandCrvBound_AE PG does not match with BeamSystem PG ........................................... 349 The Landing Curve PG does not match with Standalone Stiffener PG ....................................... 350 The Landing Offset PG does not match with Profile System PG ................................................. 351 The LandingCrvBound_AE PG does not match with Profile System PG ..................................... 351 The LandingCrvPoint PG does not match with Profile System PG .............................................. 352 The LandingCrv_AE PG does not match with ProfileSystem PG ................................................ 353 The LandOffset does not match with Edge Feature PG .............................................................. 353 The leaf part PG does not match the root part PG ....................................................................... 354 The Leaf ProfileLandCrv PG does not match with Leaf ProfileSystem PG ................................. 355 The Leaf ProfileSys Region PG does not match with Leaf Profile System PG............................ 355 The Leaf ProfileSystem_AE PG does not match with Leaf ProfileSystem PG ............................ 356 The leaf system PG does not match root system PG .................................................................. 357 The OffsetPt_AE does not match with Edge Feature PG ............................................................ 357 The Opening PG does not match root system PG ....................................................................... 358 The PG of Chamfer does not match with Part PG ....................................................................... 359 The PG of PC on AC does not match Parent PG ........................................................................ 359 The PG of PhysicalConnection on Collar does not match with Part PG ...................................... 360 The PG of PhysicalConnection on Feature does not match with Part PG ................................... 361 The PointOnGeom_AE PG does not match with Feature PG...................................................... 361 The PointOnSurfByTwoCoords_AE PG does not match with Profile System PG ....................... 362 The ProfileLandCrv PG does not match with ProfileSystem PG.................................................. 363 The ProfileLandCrvInPut PG does not match with Profile System PG ........................................ 364 The ProfilePartCreation PG does not match with StandAloneStiffener PG ................................. 365 The ProfilePartPath PG does not match with StandAlone Stiffener PG ...................................... 366 The ProfileSysRegion PG does not match with ProfileSystem PG .............................................. 367 The ProfileSystem_AE PG does not match with Profile System PG ........................................... 367 The Ref Curve PG does not match root system PG .................................................................... 368 The root LC PG does not match with the dependent system....................................................... 369 The rule-based features PG does not match Part PG ................................................................. 369 The Seam PG does not match root system PG ........................................................................... 370 The SharedAttEntityBag PG does not match with Parent PG...................................................... 371 The ShpStrEdgeFeatOffPt_OUT does not match with Edge Feature PG ................................... 371 The Symbol PG does not match the BeamSystem PG ................................................................ 372 The Symbol PG does not match with Beam StandAlone Part PG ............................................... 373 The Symbol PG does not match with ProfileSystem PG ............................................................. 373 The Symbol PG does not match with StandAloneStiffener PG.................................................... 374 The TrackPoint3D PG does not match with Feature PG ............................................................. 375 The Tripping Assoc Point PG does not match with Profile System PG ....................................... 375 The WireBody2 PG does not match with ProfileSystem PG ........................................................ 376 The WireBody2 PG does not match with StandAlone Stiffener PG ............................................. 377 Piping ........................................................................................................................................................ 379 Feature has an Offline relation without a HasTapFeature relation ................................................... 379
13
Contents
Non-spool object with SpoolHierarchy relation to ConfigProjectRoot................................................. 380 Planning.................................................................................................................................................... 381 An Assembly has itself as a parent in the AssemblyHierarchy........................................................... 381 Block Assemblies must have topological blocks underneath ............................................................. 382 Common part group is not implemented ............................................................................................. 382 Migration to V6.1 should have removed all objects in the PLANNGAssemblyReportData table .................................................................................................. 383 Planning Block Assembly is above the B0 Block ................................................................................ 383 Planning Block Assembly is at the same level as the B0 Block ......................................................... 384 The intersection object is related to a system instead of a part .......................................................... 385 The object should be in the Planning PermissionGroup ..................................................................... 385 The PLANNGAssemblyBase table is missing the BlobSize column .................................................. 386 The PLANNGAssemblyBase table is missing the ConnectivityInfo column ....................................... 387 There is more than one B0 block inside the DB ................................................................................. 387 There is more than one parent in the DB for a child Assembly .......................................................... 388 Project Management ............................................................................................................................... 389 Access Control Rule is not associated to Permission Group ............................................................. 389 Database is not associated to any plant ............................................................................................. 389 Detected unassociated Location object .............................................................................................. 390 Folder is not associated to the parent Folder ..................................................................................... 390 Invalid relationship between the Workspace Explorer root and the plant in the site database ............................................................................................................................................. 391 Model database has more than one site occurrence for catalog ........................................................ 392 Model has multiple ProxyOwners (site) for projectdb ......................................................................... 392 Multiple ConfigProjectRoot objects exists in the model ...................................................................... 393 Permission Group contains duplicate Access Control Rules .............................................................. 393 Permission Group has multiple relations with Folder Parent .............................................................. 394 Permission Group is not associated to a Folder ................................................................................. 394 Permission Group is not associated to a Location.............................................................................. 395 Plant is not associated to Plants root .................................................................................................. 396 Reference Data ........................................................................................................................................ 397 Object does not have the requested relation ...................................................................................... 397 Object does not have the requested simple relation........................................................................... 400 Object has an unexpected relation ..................................................................................................... 402 Route Cable .............................................................................................................................................. 405 Cable feature not associated with cable leg ....................................................................................... 405 Cable feature not associated with cable run ....................................................................................... 405 Cable has no cable part in the catalog ............................................................................................... 406 Cable is not connected to any equipment ........................................................................................... 406 Cable Leg not associated with Cable Feature .................................................................................... 407 Cable occurrence not associated with cable feature .......................................................................... 408 Cable occurrence not associated with cable run ................................................................................ 408 Cable run not associated with any cable feature ................................................................................ 409 Cable run not associated with cable occurrence ................................................................................ 410 EntryExit not connected to leg ............................................................................................................ 411 Marker not connected to feature ......................................................................................................... 411 Marker Not connected to leg ............................................................................................................... 412
14
Contents
Segment not associated to any boundary .......................................................................................... 412 Segment not connected to any cableway Feature.............................................................................. 413 Segment not connected to any leg ..................................................................................................... 413 Ship Drawings and Reports.................................................................................................................... 415 AE (Arrangement)/Broker that has the Querystring of elements in Model exists without a ShipDwgView ................................................................................................................................... 415 AE (Hulllines)/Broker that has the Querystring of elements in Model exists without a ShipDwgView ...................................................................................................................................... 415 AE (scantling by volume)/Broker that has the Querystring of elements in Model exists without a ShipDwgView ...................................................................................................................... 416 AE (ShellExpansion)/Broker that has the Querystring of elements in Model exists without a ShipDwgView ...................................................................................................................... 416 dbo.SHIPDWGShellExpSystem table is not created .......................................................................... 417 dbo.SHIPDWGXMLStorage table is not created ................................................................................ 418 DrawingViewGenerator exists without a Dwg View ............................................................................ 418 Missing Column 'dTimeLastGenerated' in table dbo.SHIPDWGShellExpSy ..................................... 419 Missing Column 'dVolumeThicknessNeg' in table dbo.SHIPDWGScantlingByVolumeAE ................................................................................................ 419 ShellExpansionAE exists without Hull Plate input .............................................................................. 420 ShellExpansionAE exists without BaseCurve Input ............................................................................ 421 Shell expansion AE Exists without plate geometry ............................................................................. 421 ShipDwg Table does not exist in Catalog ........................................................................................... 422 ShipDwgView exists without a Dwg Sheet ......................................................................................... 423 ShipDwgView/MetaShipDwgView exists without a Dwg View............................................................ 423 TemplateSnapIn exists without a TemplateMgr .................................................................................. 424 The object should be in the ShipDrawings PermissionGroup ............................................................ 424 Ship Reference Data................................................................................................................................ 427 ConventionPlatePort missing relation with PlatePosition ................................................................... 427 ConventionPlatePosition Missing Relation with MoldedConventionSpec .......................................... 428 ConventionSpec missing Relation with MoldedFormSpec ................................................................. 429 ProfileMoldedConvention missing relation with Plate port .................................................................. 430 Structural Analysis .................................................................................................................................. 431 Analysis Model has more than one boundary condition folder ........................................................... 431 Analysis Model has more than one load combination folder .............................................................. 432 Analysis Model has more than one member folder ............................................................................ 433 Analysis Model is missing its association to the model ...................................................................... 433 Analysis Model is missing its boundary condition folder ..................................................................... 434 Analysis Model is missing its load combination folder ........................................................................ 435 Analysis Model is missing its member folder ...................................................................................... 435 Analysis WSE folder has no parent .................................................................................................... 436 Boundary condition is not associated to a member part ..................................................................... 437 Duplicate naming rule assigned to a boundary condition ................................................................... 437 Duplicate naming rule assigned to a load ........................................................................................... 438 Duplicate naming rule assigned to a load case .................................................................................. 438 Duplicate naming rule assigned to a load combination ...................................................................... 439 Duplicate naming rule assigned to an analysis model ........................................................................ 440 Load associated to more than one load case ..................................................................................... 440 Load associated to more than one member ....................................................................................... 441
15
Contents
Load case does not have a parent load case folder ........................................................................... 441 Load combination has a factor to a load case that does not exist ...................................................... 442 Load combination has no assigned load cases .................................................................................. 443 Load has a force or moment magnitude of 0 ...................................................................................... 443 Load not assigned to a member part .................................................................................................. 444 Load not associated to a load case .................................................................................................... 444 Load relative position is not between 0 and 1 ..................................................................................... 445 Multiple boundary conditions are assigned to the same end of a member part ................................. 445 There is more than one analysis load case folder .............................................................................. 446 There is more than one unassigned members folder ......................................................................... 447 Structural Detailing ................................................................................................................................. 449 A BeamPart does not have BeamPartProfileGeometry relationship .................................................. 449 A BeamPart does not have GUIDBeamPartOrientation relationship.................................................. 450 A CollarPart does not have the AssemblyMembersR relation ............................................................ 450 A CollarPart does not have the CollarDefiningData relation ............................................................... 451 A CollarPart does not have the CollarPlateData relation .................................................................... 452 A CreateCollar_AE does not have a related PlatePartGeometry ....................................................... 452 A detailed PlatePartGeometry does not have a related AE ................................................................ 453 A PlateStrakingSplit_AE does not have a SurfaceBody ..................................................................... 454 A profile Part does not have a related ProfilePartCreation ................................................................. 454 A ProfilePart does not have a related GeneratePlatePart_AE ........................................................... 455 A ProfilePart does not have a related ProfilePartGeometry ............................................................... 456 A ProfilePartCreation does not have a related ProfilePartPath .......................................................... 456 A ProfilePartCreation does not have a related ProfilePartGeometry.................................................. 457 A ProfilePartPath does not have a related ProfilePartCreation .......................................................... 458 A ProfileTrim_AE does not have the ProfileTrim_OPER1 relation ..................................................... 458 A SketchFeature does not have an OutputColl .................................................................................. 459 A SmartPlate does not have a related CreatePlatePart_AE .............................................................. 460 A straking Seam does not have a related StrakingSplit_AE ............................................................... 460 A Struct/Sketch Feature is missing its Cut or ProfileTrim Operator .................................................... 461 Active Entity with no physical connections as input ............................................................................ 462 An ActiveEntity does not have a Part ................................................................................................. 462 An ActiveEntity does not have a related PartGeometry...................................................................... 463 An object does not have a related CreatePlatePartAE ....................................................................... 464 An object does not have a related DReferencesCollection ................................................................ 464 An object does not have a related PlatePartGeometry ...................................................................... 465 Cut operation missing input geometry ................................................................................................ 466 Edgetreatment with no edge connected to it ...................................................................................... 466 Edgetreatment with zero length .......................................................................................................... 467 Physical Connection Active entity with no outputs .............................................................................. 468 Physical Connection Active entity without any inputs ......................................................................... 468 Physical connection has multiple symbols .......................................................................................... 469 Physical connection only has dummy symbol .................................................................................... 469 Split Point Active entity with no outputs .............................................................................................. 470 Split Point Active Entity with no RefFace as input .............................................................................. 471 Split point exists without active entity ................................................................................................. 471 The object should be in the StructDetail PermissionGroup ................................................................ 472 Too many flavors have been created for non-symbol objects ............................................................ 473 Structural Manufacturing ........................................................................................................................ 475 Assembly Margin does not have Assembly ........................................................................................ 475
16
Contents
Assembly Margin parent does not have Assembly margin child ........................................................ 475 BuiltUp Profile Nestdata does not have MfgProfile ............................................................................. 476 Incorrect UpToDate column in StrMfgUpdateInfo table ...................................................................... 476 Input-Added MfgPin does not have PinJig active entity ..................................................................... 477 Manufacturing children without parent ................................................................................................ 478 Manufacturing definition does not have port ....................................................................................... 478 Manufacturing objects without parent ................................................................................................. 479 Manufacturing SmartOccurrence without part input ........................................................................... 479 Marking Lines active entity without any reference object as input ...................................................... 480 Marking Lines active entity without any output ................................................................................... 480 Marking line active entity without detailed part as input...................................................................... 481 Marking line does not have Parent ..................................................................................................... 481 MfgBevel does not have Geom2D ...................................................................................................... 482 MfgHitachi object does not have MfgPlatePart ................................................................................... 482 MfgPlateCreation active entity does not have DetailPlatePart as Input ............................................. 483 MfgPlateCreation active entity does not have SmartOccurrence Object............................................ 483 MfgPlateMarking Settings object does not have MfgPlateCreation active entity ............................... 484 MfgPlatePart active entity does not have MfgPlatePart...................................................................... 485 MfgPlatePart does not have MfgPlatePart active entity...................................................................... 485 MfgPlateProcess Settings object does not have MfgPlateCreation active entity ............................... 486 MfgProfile Part does not have MfgProfileCreation active entity ......................................................... 486 MfgProfileCreation active entity does not have DetailPlatePart as Input ........................................... 487 MfgProfileCreation active entity does not have MfgProfilePart .......................................................... 487 MfgProfileCreation active entity does not have SmartOccurrence object .......................................... 488 MfgProfileMarking Settings object does not have MfgProfileCreation active entity ........................... 488 MfgProfileProcess Settings object does not have MfgProfileCreation active entity ........................... 489 Oblique margin does not have port ..................................................................................................... 490 PinJig active entity does not have Input-Supported plate ................................................................... 490 PinJig active entity does not have output Jig ...................................................................................... 491 PinJig active entity does not have Seams with 'ButtAndSeam' relation ............................................. 491 Shrinkage Active entity does not have detailed part as input ............................................................. 492 Shrinkage Active entity without Output ............................................................................................... 492 Shrinkage Active entity without Primary Axis ...................................................................................... 493 Shrinkage Active entity without Primary port ...................................................................................... 493 Shrinkage Active entity without Secondary Axis ................................................................................. 494 Shrinkage Active entity without Secondary port ................................................................................. 494 Shrinkage object with secondary factor but no secondary direction ................................................... 495 Shrinkage output without active entity ................................................................................................ 495 System marks do not have relation to MfgGeom3d or MfgGeom2d .................................................. 496 System marks are on 2D relation but do not have MfgGeom2d ......................................................... 496 System marks are on 3d relation but do not have MfgGeom3d ......................................................... 497 Template active entity does not have Input Sketching Plane ............................................................. 497 Template active entity without output ................................................................................................. 498 Template active entity without plate input ........................................................................................... 498 Template active entity without Process and Marking settings ............................................................ 499 Template has invalid child ................................................................................................................... 499 TemplateMarking Settings without active entity.................................................................................. 500 TemplateProcess Settings without active entity ................................................................................. 500 TemplateSet object without active entity ............................................................................................ 501 The object should be in the StructManufacturing PermissionGroup .................................................. 502 Structural Manufacturing Permission Group and Approval Status Messages .................................... 502 Added Pin's Approval Status does not match with Pin Jig's Approval Status .............................. 504 Added Pin's Permission Group does not match with Pin Jig's Permission Group ....................... 505
17
Contents
Assembly margin child's Approval Status does not match with Assembly Margin's Approval Status ............................................................................................................................ 505 Assembly margin child's Permission Group does not match with Assembly Margin's Permission Group ......................................................................................................................... 506 Base Control Line Symbol's Approval Status does not match with Template's Approval Status ............................................................................................................................ 506 Base Control Line Symbol's Permission Group does not match with Template's Permission Group ......................................................................................................................... 507 Base plane's Approval Status does not match with Template's Approval Status ........................ 507 Base plane's Permission Group does not match with Template's Permission Group ...................................................................................................................................................... 508 Manufacturing parts under Plate part or Profile part do not have same Approval Status............................................................................................................................................ 509 Manufacturing parts under Plate part or Profile part do not have same Permission Group ............................................................................................................................................ 509 MarkingLineData's Approval Status does not match with Marking Line's Approval Status............................................................................................................................................ 510 MarkingLineData's Permission Group does not match with Marking Line's Permission Group ......................................................................................................................... 510 MfgBevel object's Approval Status does not match with MfgPlate/MfgProfile's Approval Status ............................................................................................................................ 511 MfgBevel object's Permission Group does not match with MfgPlate/MfgProfile's Permission Group ......................................................................................................................... 511 MfgDefinition's Approval Status does not match with Pin Jig's Approval Status ......................... 512 MfgDefinition's Permission Group does not match with Pin Jig's Permission Group ...................................................................................................................................................... 513 MfgGeneralHitachi's Approval Status does not match with MfgPlatePart's Approval Status............................................................................................................................................ 513 MfgGeneralHitachi's Permission Group does not match with MfgPlatePart's Permission Group ......................................................................................................................... 514 MfgGeomchild's Approval Status does not match with MfgGeomParent's Approval Status............................................................................................................................................ 514 MfgGeomchild's Permission Group does not match with MfgGeomParent's Permission Group ......................................................................................................................... 515 MfgNestData object's Approval Status does not match with MfgProfilePart's Approval Status ............................................................................................................................ 515 MfgNestData object's Permission Group does not match with MfgProfilePart's Permission Group ......................................................................................................................... 516 MfgSystemMark3D object's Approval Status does not match with MfgProfile's Approval Status ............................................................................................................................ 517 MfgSystemMark3D object's Permission Group does not match with MfgProfile's Permission Group ......................................................................................................................... 517 Pin Jig active entity's Approval Status does not match with Pin Jig's Approval Status............................................................................................................................................ 518 Pin Jig active entity's Permission Group does not match with Pin Jig's Permission Group ............................................................................................................................................ 518 Plate creation active entity's Approval Status does not match with MfgPlatePart's Approval Status ............................................................................................................................ 519 Plate creation active entity's Permission Group does not match with MfgPlatePart's Permission Group ......................................................................................................................... 519 Profile creation active entity's Approval Status does not match with MfgProfilePart's Approval Status ............................................................................................................................ 520
18
Contents
Profile creation active entity's Permission Group does not match with MfgProfilePart's Permission Group .............................................................................................. 521 Shrinkage active entity's Approval Status does not match with Shrinkage's Approval Status ............................................................................................................................ 521 Shrinkage active entity's Permission Group does not match with Shrinkage's Permission Group ......................................................................................................................... 522 Sketch Template Line Symbol's Approval Status does not match with Template's Approval Status ............................................................................................................................ 522 Sketch Template Line Symbol's Permission Group does not match with Template's Permission Group ......................................................................................................................... 523 SmartOccurrence object's Approval Status does not match with MfgPlatePart's Approval Status ............................................................................................................................ 523 SmartOccurrence object's Approval Status does not match with MfgProfilePart's Approval Status ............................................................................................................................ 524 SmartOccurrence object's Approval Status does not match with Template's Approval Status ............................................................................................................................ 525 SmartOccurrence object's Permission Group does not match with MfgPlatePart's Permission Group ......................................................................................................................... 525 SmartOccurrence object's Permission Group does not match with MfgProfilePart's Permission Group ......................................................................................................................... 526 SmartOccurrence object's Permission Group does not match with Template's Permission Group ......................................................................................................................... 526 Symbol's Approval Status does not match with Marking Line's Approval Status ......................... 527 Symbol's Permission Group does not match with Marking Line's Permission Group ...................................................................................................................................................... 527 SystemMark2D object's Approval Status does not match with MfgProfile's Approval Status............................................................................................................................................ 528 SystemMark2D object's Permission Group does not match with MfgProfile's Permission Group ......................................................................................................................... 529 Template active entity's Approval Status does not match with Template's Approval Status............................................................................................................................................ 529 Template active entity's Permission Group does not match with Template's Permission Group ......................................................................................................................... 530 Structure ................................................................................................................................................... 531 Assembly connection does not have a cutting plane .......................................................................... 531 Assembly connection does not have an associated feature ............................................................... 532 Assembly connection feature is incorrectly related to member part ................................................... 532 Assembly connection is missing a relation to the supported members end port ................................ 533 Assembly connection is missing one or more of its custom plate parts ............................................. 534 Assembly connection is missing one or more related axis ports ........................................................ 535 Assembly connection missing relation to supported member part end port ....................................... 535 Assembly connection missing relation to supporting member part .................................................... 536 Assembly connection missing relation to supporting member part end port ...................................... 537 Axis joint copy property flag is not zero or the point on value is not -1.0............................................ 537 Can Rule exists in CORESpatialIndex ................................................................................................ 538 Can Rule missing aggregated GCMacro ............................................................................................ 539 Can Rule missing aggregated point .................................................................................................... 539 Can Rule missing Member System input ............................................................................................ 540 Door or Window is missing its mating constraint ................................................................................ 540 Door or Window is missing its opening ............................................................................................... 541 End frame connection missing a relation to the supporting member joint .......................................... 542 Equipment foundation component does not have a relation to its parent........................................... 543
19
Contents
Equipment foundation exists without Equipment ................................................................................ 543 Equipment foundation material is missing .......................................................................................... 544 Footing material is missing ................................................................................................................. 544 Footing without sufficient supporting members .................................................................................. 545 Frame connection associated to more than one member part end port ............................................. 546 Frame connection found that is unrelated to a member system ......................................................... 546 Frame connection is missing its reference collection ......................................................................... 547 Frame connection missing its reference collection relation to the member system ........................... 548 Frame connection without member part end port relation .................................................................. 548 Handrail exists without its geometry ................................................................................................... 549 Handrail is not associated to HandrailAE ........................................................................................... 550 HandrailAE is not associated to Handrail ........................................................................................... 550 Invalid Knuckle type ............................................................................................................................ 551 Invalid neighbor part count .................................................................................................................. 551 Joint found that is unrelated to a member system .............................................................................. 552 Leg not split ......................................................................................................................................... 552 Member end port associated to more than one Frame Connection ................................................... 553 Member part axis end port found with invalid properties .................................................................... 554 Member part cutLength is zero ........................................................................................................... 554 Member part does not have an attached cross section occurrence ................................................... 555 Member part generator missing .......................................................................................................... 556 Member part has more than one attached cross section definition .................................................... 557 Member part has more than one attached cross section occurrence................................................. 557 Member part has more than one material definition ........................................................................... 558 Member part has no attached catalog cross section definition ........................................................... 558 Member part has no attached material definition................................................................................ 559 Member part is missing a start or end port ......................................................................................... 560 Member part is missing its end ports .................................................................................................. 561 Member part not attached to member part generator ......................................................................... 561 Member part solid geometry missing .................................................................................................. 562 Member system axis end port (at end) is related to more than one axis joint .................................... 562 Member system axis end port (at start) is related to more than one axis joint ................................... 563 Member system can be point on to only one member system ........................................................... 564 Member system end port found with invalid properties ...................................................................... 564 Member system exists without any member parts.............................................................................. 565 Member system is missing a start or end port .................................................................................... 566 Member system is missing its attached wirebody............................................................................... 566 Member system is missing its end ports ............................................................................................. 567 Member system missing one or more frame connections .................................................................. 567 Member system Type property cannot be 0 ....................................................................................... 568 Member system TypeCategory property cannot be 0......................................................................... 569 Mismatched relations .......................................................................................................................... 570 Missing Knuckle .................................................................................................................................. 570 More than one assembly connection is attached to the end port of a member part ........................... 571 No frame connection found on end of member system ...................................................................... 571 Object not in the same permission group as its parent....................................................................... 572 One or more outputs of a Designed Member exist in a different Permission Group .......................... 573 Opening without any OpeningType relation ........................................................................................ 574 Orphan can ......................................................................................................................................... 574 Orphan can rule .................................................................................................................................. 575 Orphaned Cross section symbol occurrences having no relationships to any objects....................... 575 Orphaned structure member part along port ...................................................................................... 576 Orphaned structure member part end port ......................................................................................... 577
20
Contents
Orphaned structure member system end port .................................................................................... 577 Port face selector is missing its root contour ...................................................................................... 578 Port face selector is missing its source object .................................................................................... 578 Port face selector root contour is not unique ...................................................................................... 579 Port face selector source object is not unique .................................................................................... 580 Reference collection for a FrameConnection uses unexpected relation ............................................ 580 Reference Collection for an unsupported Frame Connection contains more than one element ............................................................................................................................................... 581 Slab entity catalog type reference is not unique ................................................................................. 582 Slab entity composition reference is not unique ................................................................................. 582 Slab entity is missing its catalog type reference ................................................................................. 583 Slab entity is missing its composition ................................................................................................. 583 Slab entity is missing its composition reference ................................................................................. 584 Slab layer catalog type reference is not unique .................................................................................. 584 Slab layer composition is not unique .................................................................................................. 585 Slab layer is missing its catalog type reference .................................................................................. 585 Slab layer is missing its composition .................................................................................................. 586 Slab Without Any Slab Assembly Connection .................................................................................... 586 Slab Without Supporting Object .......................................................................................................... 587 Stair or Ladder has more than one related bottom plane ................................................................... 588 Stair or Ladder has more than one related reference plane or edge .................................................. 589 Stair or Ladder has more than one related top plane or edge ............................................................ 590 Stair or Ladder is missing its bottom supporting plane ....................................................................... 591 Stair or Ladder is missing its top supporting plane or edge ................................................................ 591 Stair or Ladder is not associated to its AE .......................................................................................... 592 StairAE is not associated to Stair or Ladder ....................................................................................... 593 Structure SmartOcc related objects with missing flavor relation ........................................................ 593 Surface frame connection is missing its reference collection relation to the surface ......................... 594 Wrong reference collection relation to member for end port @end .................................................... 595 Wrong reference collection relation to member for end port @start ................................................... 595 Systems and Specifications ................................................................................................................... 597 Missing relationship for Correlated object ........................................................................................... 597 Object does not have a parent ............................................................................................................ 598 Object has more than one parent ....................................................................................................... 599 Object is the parent of itself ................................................................................................................ 600 System does not have a parent .......................................................................................................... 601 System has more than one parent ...................................................................................................... 602 System has unneeded NamingParent relation ................................................................................... 603 System is the parent of itself ............................................................................................................... 603 Index ......................................................................................................................................................... 605
21
Contents
22
Preface
This document is a database integrity guide for Intergraph SmartMarine 3D. The purpose of this document is to describe the database integrity messages for the different tasks in the software.
23
Preface
Administrative Guides
SmartMarine 3D Installation Guide - Provides instructions on installing and configuring the software. Project Management User's Guide - Provides instructions for setting up the databases, creating permission groups, backing up and restoring project data, assigning access permissions to the model, defining and managing locations for Global Workshare, and version migration. SmartMarine 3D Global Workshare Guide - Provides instructions for setting up the software and the databases to work in a workshare environment. SmartMarine 3D Interference Checking Guide - Provides information on installing, configuring, and using the interference detection service. SmartMarine 3D Integration Reference Guide - Provides information about installing, configuring, and using SmartMarine 3D in an integrated environment. SmartMarine 3D Interpreting Human Piping Specifications - Provides information about how to interpret human piping specifications so that you can create the corresponding piping specification in the software. SmartMarine 3D Export to PDMS - Provides information about how to export model data from SmartMarine 3D to PDMS. Specific guidelines relating to best practices and known limitations of the export functionality are also included. SmartMarine 3D Point Cloud Reference - Provides information for referencing point cloud files provided by point cloud vendors in SmartMarine 3D. SmartMarine 3D Troubleshooting Guide - Provides information on how to resolve errors that you may encounter in the software by documenting troubleshooting tips, error messages, and to do list messages. SmartMarine 3D Plant Design System (PDS) Guide - Provides all information needed to use PDS with SmartMarine 3D. Topics include referencing active PDS projects in SmartMarine 3D, exporting PDS data and importing that data into SmartMarine 3D, and converting PDS reference data to SmartMarine 3D reference data. SmartPlant 3D/SmartMarine 3D Programmer's Guide - Provides information about custom commands, naming rules, and symbol programming.
User's Guides
Catalog User's Guide - Provides information about viewing, editing, and creating reference data and select lists (codelists). Common User's Guide - Provides information about defining workspaces, manipulating views, and running reports.
24
Preface
Compartmentation User's Guide - Provides instruction for placing volume objects such as compartments and zones in the model. Electrical User's Guide - Provides information about routing electrical cable, cableway, cable tray, and conduit. Equipment and Furnishings User's Guide - Provides information about placing equipment. Geometry Analysis and Repair User's Guide - Provides instructions for importing and exporting model data, checking the data against a defined set of requirements, and repairing the data. Grids User's Guide - Provides instructions for creating coordinate systems, elevation grid planes, vertical grid planes, radial cylinders, radial planes, grid arcs, and grid lines. Hangers and Supports User's Guide - Provides instructions on placing piping, duct, and cableway supports in the model. Hole Management User's Guide - Provides instructions for placing, reviewing, and approving holes in a structure. HVAC User's Guide - Provides instructions for routing HVAC duct. Molded Forms User's Guide - Provides instructions for placing hull, bulkheads, major openings, stiffeners, and other major components of a ship's frame in the model. Orthographic Drawings User's Guide - Provides information about creating and managing orthographic drawings. Piping Isometric Drawings User's Guide - Provides information about creating and managing piping isometric drawings. Piping User's Guide - Provides instructions for routing pipe and placing valves, taps, and pipe joints. Planning User's Guide - Provides instructions about defining the assembly hierarchy (production bill of material) by creating blocks, assemblies, and by specifying the assembly sequence. Reports User's Guide - Provides information about creating and managing spreadsheet reports. Space Management User's Guide - Provides instructions for placing space objects such as areas, zones, interference volumes, and drawing volumes in the model. Structural Analysis User's Guide - Provides instructions for defining loads, load cases, load combinations, and the importing and exporting of analytical data. Structural Detailing User's Guide - Provides instructions for creating, detailing, and maintaining the structural members of a Ship. Structural Manufacturing User's Guide - Provides instructions for creating and maintaining manufacturing objects such as templates, jigs, and margins. Structure User's Guide - Provides instructions for placing structural members such as: beams, columns, slabs, openings, stairs, ladders, equipment foundations, and handrails. Systems and Specifications User's Guide - Provides instructions for creating systems and selecting which specifications are available for each system type.
25
Preface
Electrical Reference Data Guide - Provides information about electrical cable, cableway, cable tray, and conduit reference data. Electrical 3D Symbols Reference - Provides information about the cable tray and conduit 3D symbols that are available. Equipment and Furnishings Reference Data Guide - Provides information about equipment reference data. Equipment 3D Symbols Reference - Provides information about the equipment, equipment component, design shapes, and design aides 3D symbols that are available. Hangers and Supports Reference Data Guide - Provides information about hangers and supports reference data. Hangers and Supports 3D Symbols Reference - Provides information about the hanger and support 3D symbols that are available. Hole Management Reference Data Guide - Provides information about hole reference data. HVAC Reference Data Guide - Provides information about HVAC reference data. HVAC 3D Symbols Reference - Provides information about the HVAC 3D symbols that are available. SmartMarine 3D Reference Data Guide - Provides instructions about the Bulkload utility, codelists, and the reference data common to several disciplines. Piping Reference Data Guide - Provides information about piping reference data including piping specifications, piping specification rules, piping parts, and piping symbols. Piping 3D Symbols Reference - Provides information about the piping 3D symbols that are available. Space Management Reference Data Guide - Provides information about space management reference data. Structure Reference Data Guide - Provides information about structural reference data. Structure 3D Symbols Reference - Provides information about the stair, ladder, footings, and equipment foundation 3D symbols that are available. SmartMarine 3D Structural Reference Data Overview - Provides an overview of the SmartMarine 3D structural reference data library.
ISOGEN Guides
Symbol Keys Reference Guide - Provides information about the symbol keys for isometric drawings. This guide is from Alias, the makers of ISOGEN.
26
Preface
Documentation Comments
We welcome comments or suggestions about this documentation. You can send us an email at: [email protected].
27
Preface
28
Preface
29
Preface
30
SECTION 1
See Also
Workflow for Addressing Database Integrity (on page 33)
31
32
SECTION 2
33
Cleaning Errors
If the action on the report is To Be Removed or To Be Repaired, run the Clean Database custom command to delete or clean the object. For more information about deleting and cleaning objects, see Clean a Database (on page 39). When a database integrity error is logged against an object, the software specifies an ActionOID that denotes the object on which a possible correction will be performed. The Clean Database command performs its cleaning action on this object referred to by the ActionOID. This object may be the object in error, or it may be a related object. An example is when a weld is in error, but the update to correct the problem needs to be done on the related connection. After you fix a problem, be sure to check that it is solved and that no new problems have been created. Re-run the Database > Integrity command and the DB Integrity reports, and then check the results.
See Also
Database Integrity Custom Commands (on page 34)
34
If you are working in Project Management, you can run this command as a custom command or with the Database > Integrity command. If you are working in the host, you can run this command as a custom command using Tools > Custom Commands.
Clean Database
Find Object by SP3DFindObjectByReport.FindO Highlights the selected object (from a OID bjects report) in a graphic view. You choose a previously run report, highlight a row in the report, and then the selected object highlights in the active graphic view. This command only works for reports that return OIDs.
See Also
Workflow for Addressing Database Integrity (on page 33)
35
Four example reports for Diagnostic Clean Database Issues are delivered. Reports can be created persistently in the Drawings and Reports task and scheduled in the Drawing Batch server to run periodically after a scheduled DBI check.
Database Integrity
Database > Integrity - Runs directly on a database (Site, Catalog, Model, or Reports) and creates records for the objects that need to be cleaned. After you scan the database for problems, you can use the Tools > Run Report command in the Common task to review the errors that the Database > Integrity command generated. In addition, you can use the Submit Job button on the Check Data Consistency Dialog Box (on page 37) to access Batch Services to check integrity at times when the server may be less busy. For information on setting up Batch Services, see Batch Services Quick Start Guide. You can run this command for several different reasons: To check the database for objects with integrity problems To confirm that objects have been deleted or cleaned To check for new problems For more information on database integrity, see the Database Integrity Guide.
36
Check database - Lists the names of the possible databases to check. If you selected a Ship in the Project Management hierarchy prior to running the command, the list shows the Catalog, Model, Reports, and Site databases associated with that Ship. If you selected a Catalog in the hierarchy, the list only shows the Catalog database. You can check more than one database in the list. Checking - Shows the progress information for the command after you click Run. Basic check - Specifies that you want to run a faster database check that checks for the most common problems. The Basic check could be run on a regular basis. Full check - Specifies that you want to run a deep integrity check that checks for any type of problem. The Full check can take much longer to complete than the Basic check. The Full check could be run when an uncommon problem is encountered or, for example, once a week. Submit Job - Opens the Schedule [Task] dialog box so you can schedule this process. Run - Starts the command for database integrity checking for the selected databases. This button also creates a text file in the same TEMP folder as your log files. This text file contains a command with the parameters for running the Database Integrity command from the command line with the same parameters and options as used interactively. If only one database is selected, the text file name format is DbIntegrityCommandLine-<DbName>.txt. If more than one database is selected, the text file name format is DbIntegrityCommandLine-<ShipName>.txt. Exit - Closes the dialog box.
37
Four example reports for Diagnostic Clean Database Issues are delivered. Reports can be created persistently in the Drawings and Reports task and scheduled in the Drawing Batch server to run periodically after a scheduled DBI check.
38
Clean a Database
In some cases, cleaning objects will cause a loss of data. Before working through this procedure, you should try to find a matching error message in this document. In the What You Should Do section of each error topic, there may be some steps that will easily fix the problem without loss of data. Before running this command, make a backup of all the databases using the Backup command in Project Management. You can later provide this backup to Intergraph if further analysis is necessary. In order to clean objects, you must have access to the objects. You must have Full Control on all permission groups in order to delete the objects. 1. Start the software. 2. Click Tools > Custom Commands. 3. Click Add on the dialog box. 4. In the Command ProgID box, type SP3DCleanDatabaseCmd.CCheckObj. 5. In the Command name box, type text such as Clean Database. 6. Click OK on the Add Custom Command dialog box. 7. Select the command name, and then click Run. 8. On the Clean Database dialog box, specify the type of database in the Database type box. 9. In the grid, select the object(s) to clean and click Clean Now. You can select multiple objects by holding SHIFT or CTRL while clicking the objects. You can sort the columns on the dialog box by clicking the column headings. Click Select All or Clear All to select or clear all the rows. 10. When the process finishes, click View Log to review the log file. It is possible that the cleaning operation was not successful. Review the log file for more information. You do not need to have the objects with errors loaded in the workspace for this command to work. However, if the objects are not in the workspace, you will not graphically see the result of running the command when you refresh the workspace. The Clean Database command cannot repair objects in nonworking approval state and objects owned by another GWC location.
39
See Also
Workflow for Addressing Database Integrity (on page 33)
40
Process 1
Bulkload Sync Project model Manageme with nt Backup Catalog Bulkload Synchronize model with Catalog Regenerate Report DB Yes Risk No No No No
Bulkload
Risk
DB Maintenanc e
Database Integrity Slow Clean DB Command DB Maintenance Check Fragmentation Risk No Yes Yes
Backup
Yes Yes
No No No No Yes
Report Extraction
Legend
Yes - Processes can be run concurrently with no risks or performance impact. No - Processes cannot be run concurrently. Risk - Processes can be run concurrently, but there are risks involved.
41
42
SECTION 3
CommonApp
This section contains CommonApp database integrity messages.
Severity
Crucial.
Detailed Description
A control point should have a parent for it to exist. A control point cannot exist by itself without a parent.
Possible Cause
Coding or data model propagation errors in an earlier version.
Possible Impacts
A control point created without a parent is useless and cannot be used further.
43
CommonApp
5. Use the Select by Filter command with the newly created Comp1 to select all control points that do not have a parent. 6. Delete all of the control points that do not have a parent.
Severity
High
Detailed Description
There is a hierarchy filter with a missing Adapter ProgId. This Hierarchy filter object will be repaired if possible when you run the Clean Database command.
Possible Cause
Coding or data model propagation errors in an earlier version.
Possible Impacts
The Filter object becomes orphaned.
Severity
High.
Detailed Description
This error is currently associated with Sketch3d objects. As of now, we know that a Sketch3d object cannot be standalone. It must have a relation to some other entity (other than its internal entities). However, due to incorrect propagations in the data model, the Sketch3d entity may remain in the data model, whereas, the outer object may get deleted. The script detects this error and logs it with the above error message.
Possible Cause
Data model propagation errors in an earlier version.
44
Severity
High.
Detailed Description
LineFeature does not have the minimum number of TurnPoints. The line feature should have at least two turn points. This object stores and manages data for connectivity between two or more points in sketch. The LineFeature object represents a line or arc connecting some TurnPoints.
Possible Cause
Coding or data model propagation errors in an earlier version.
Possible Impacts
Line Feature cannot be modified. It also cannot be used for other sketch constructions.
Severity
High.
Detailed Description
This error is reported when there is no relation between either NameRuleAE and Named Item, or if the relationship between the NameRuleAE and NameRuleHolder is missing.
45
Possible Impacts
Should not have any impact apart from zombie objects in the database.
Severity
High.
Detailed Description
The note is not associated to any Parent Object.
Possible Cause
In the Model database, all the notes should be related to a parent object.
Possible Impacts
Should not have any impact.
Severity
Crucial.
Detailed Description
One and only one WBSProject can be defined as As-Built in a model. Multiple projects cannot be defined as As-Built.
46
Possible Impacts
Only one WBSProject can be defined as As-Built in a model. If multiple projects are defined as As-Built, then it is an error condition.
Severity
High.
Detailed Description
PointFeature has no TurnPoint. Point Feature is defined for each TurnPoint. The point features are None, Bend, Cornice, and Chamfer.
Possible Cause
Coding or data model propagation errors in an earlier version.
Possible Impacts
Modification of the PointFeature object is not possible.
47
CommonApp
Severity
High.
Detailed Description
Sketch3d is not associated to SketchByPointsAE.
Possible Cause
Coding or data model propagation errors in an earlier version.
Possible Impacts
The resultant object may not be visible in the graphic view. Modification of the resultant object is not possible.
Severity
High.
Detailed Description
Sketch3d Point is not associated to a TurnPoint. The TurnPoint is used for storing/retrieving the index of a point associated with it and the flag indicating whether the point is an assoc point or not. This object may again be connected with a PointFeature object and/or a set of LineFeature objects.
Possible Cause
Coding or data model propagation errors in an earlier version.
Possible Impacts
The resultant object may not be visible in the graphic view. Modification of the resultant object is not possible.
48
Severity
High.
Detailed Description
SketchByPointsAE is not associated to Sketch3d.
Possible Cause
Coding or data model propagation errors in an earlier version.
Possible Impacts
Object becomes orphaned.
Severity
High.
Detailed Description
SketchByPointsAE does not have minimum required input Points.
Possible Cause
Coding or data model propagation errors in an earlier version.
49
Severity
High.
Detailed Description
TurnPoint has an improper number of LineFeatures. A Line Feature object represents a line or arc connecting some TurnPoints.
Possible Cause
Coding or data model propagation errors in an earlier version.
Possible Impacts
The resultant object may not be visible in the graphic view. Modification of the resultant object is not possible.
50
CommonApp
Severity
High.
Detailed Description
TurnPoint is not associated to a Point. This TurnPoint object is used for storing/retrieving the index of point associated with it and the flag indicating whether the point is an assoc point or not. This object is again connected with a Point Feature object and/or a set of Line Feature objects.
Possible Cause
Coding or data model propagation errors in an earlier version.
Possible Impacts
The TurnPoint object becomes orphaned.
Severity
Crucial.
Detailed Description
WBS Item does not have a parent. A WBS Item cannot exist without a parent.
Possible Cause
Coding or data model propagation errors in an earlier version.
Possible Impacts
A WBS Item without a parent cannot exist, and it cannot be used for any further processing.
51
CommonApp
3. Create a properties filter with the following parameters. (Name this filter Filter2.) In the Object type used as the basis for property identification box, select WBSItems. In the Relationship box, select WBSHierarchy - WBSParent. In the Related object box, select WBSProjects. In the Display properties in this category box, select Standard. Select Project Purpose as the property. Set the operator to =. Set the value to Project. Select Project Purpose <> Project in the second row of the grid. Select the Match Any radio button. 4. Create a Compound Filter with the following combination: Filter1 AND Not Filter2. Name this filter Comp1. 5. Use the Select by Filter command with the newly created Comp1 to select all WBS Items that do not have a parent. 6. Delete all of the WBS items that do not have a parent.
Severity
Crucial.
Detailed Description
WBS Project does not have a parent. A WBS project cannot exist without a parent.
Possible Cause
Coding or data model propagation errors in an earlier version.
Possible Impacts
A WBS project without a parent cannot exist, and it cannot be used for any further processing.
52
SECTION 4
Common Route
This section contains Common Route database integrity messages.
Severity
Normal.
Detailed Description
The port is not connected to any part.
Possible Cause
Unknown. The cause may be a Permission Group problem where the parts associated with a port (and leaving the port) are deleted.
Possible Impacts
You may not be able to access the port properties. Reports may not have the right information.
Severity
High.
Detailed Description
An attach connection that is not connected to two ports exists.
Possible Cause
Unknown.
53
Severity
Crucial
Detailed Description
A route branch feature should only exist at the end of a leg. In this case a branch feature was found not at the legs end.
Possible Cause
Previous versions of software incorrectly created this situation.
Possible Impacts
Modification of neighborhood route network may not work correctly.
Severity
Crucial.
Detailed Description
A Branch feature should always have an Along Leg Feature associated with it, but in this case it happened that the Branch feature was created or left alone without any association to an Along Leg feature.
Possible Cause
Unknown.
54
Severity
High.
Detailed Description
A Route connection always connects two ports (of two different parts).
Possible Cause
Unknown.
Possible Impacts
The Drawings and Reports task will not have the right information.
Severity
Crucial.
Detailed Description
There is a relation existing between a Piping Connection object and a specification in the catalog. This relation is obsolete and is no longer needed.
Possible Cause
Using old version of the software which created this relation.
55
Severity
High
Detailed Description
A piping connection item object (gasket, boltset, or clamp) in the model is missing the relation to a catalog part.
Possible Cause
Part was deleted from the catalog.
Possible Impacts
Modeling may not be correct because some data, such as the width of the gasket, is not available. Also reports may be missing data.
Severity
High.
Detailed Description
The connection item is not related to any connection.
Possible Cause
When a connection item is not in Working status, and the other connected part is deleted, this case may arise.
56
Severity
High.
Detailed Description
All connection items (welds, bolt sets, gaskets) should have an owner part. A weld typically will appear under an owner part in the Workspace Explorer. When a connection item does not have an owner part, then it might not be brought into the workspace. One way that we can reach these objects is by navigating from the Relationships tab of the Connection Properties dialog box. Another way is to define a filter using the object type and then selecting the connection items in the model.
Possible Cause
Sometimes a part occurrence is deleted, and due to permission boundaries, the connection items are left alone. The connection associated to this connection item is placed in the To Do List.
Possible Impacts
A weld shows up underneath the model root. Reports that are generated do not show the proper owner for the connection items (such as a weld). The ownership report of the Connection Items is wrong, especially for ones that are on the boundary of the Pipelines, as there is no owner for this bolt set object.
57
Common Route
Severity
Crucial.
Detailed Description
A connection should be associated with two ports. In this case, it is not associated with any ports.
Possible Cause
Unknown. This situation is rare.
Possible Impacts
The Drawings and Reports task will not have the right information. The connection is not useful.
Severity
High.
Detailed Description
A Route connection should always be associated with a run.
Possible Cause
Unknown.
Possible Impacts
The Drawings and Reports task will not have the right information.
58
Common Route
Severity
High.
Detailed Description
A Route connection always connects two ports. The connection is also directly connected to one of the two connected parts. In this case, it is connected to a different part.
Possible Cause
Unknown.
Possible Impacts
The Drawings and Reports task will not have the right information.
Severity
High.
Detailed Description
For some types of piping connections, there is a gap between two connected parts. One example is a gap to take into account a weld gasket. In this case, the gap (or size of the connection) will be invalid.
Possible Cause
Unknown.
Possible Impacts
The Drawings and Reports task will not have the right information.
59
Severity
Crucial.
Detailed Description
The connection's permission group/approval status should be the same as the permission group/approval status of one of the parts that it connects. Or, it should at least be the same as its owner (run or logical distribution connection).
Possible Cause
Unknown.
Possible Impacts
You may not be able to modify or delete the connection.
Severity
Normal.
Detailed Description
The part is connected to a feature that has a dormant relation.
Possible Cause
Unknown.
Possible Impacts
The Drawings and Reports task will not have the right information.
60
Severity
Fatal.
Detailed Description
In the route data model, the feature types (End, Branch, and Turn) should be the first and last features of a path leg. If they happen to be in the middle of a path leg, the software, which is not designed to handle such configurations, will have problems. You should report the situation immediately, and provide the workflow that caused it.
Possible Cause
This error arises due to a software problem.
Possible Impacts
Modification behaviors could fail.
Severity
Crucial.
Detailed Description
A feature should always be associated with at least one leg. In this case, the feature is not related to any leg.
Possible Cause
Unknown.
61
Severity
Crucial.
Detailed Description
All route features must be associated to their parent run objects. If the features are not associated to the run, then they will not be brought into the workspace by normal means. However, you always have the ability to bring them into the workspace using the Object Type property.
Possible Cause
In earlier versions (prior to Version 3.0), selecting a feature and changing the run could result in this error, especially when the run to which the feature is being moved is a read-only run. However, this problem has been identified in the route code and has been fixed since then. This error should not occur in Version 4.1 or beyond.
Possible Impacts
You are not able to modify the feature (assuming you had brought the feature into the workspace using Object Type filters). Examples: Moving the feature or changing the type (short code) from GATE to BALL does not work.
62
Common Route
Feature with branch parent function did not generate part occurrence
Message
Feature with branch parent function did not generate part occurrence.
Severity
High.
Detailed Description
An along leg feature with a branch parent function (with the exception of the Cableway ALF) should generate a component occurrence, and the feature did not generate this occurrence.
Possible Cause
This problem may be due to a missing part in the catalog data, or it may be because of a permission group problem. The Route solver may not have completed all the processing due to other problems.
Possible Impacts
The run is invalid because the feature does not have a component occurrence. This situation may impact Reports.
Severity
High.
Detailed Description
A feature with a component function should generate a component occurrence, and the feature did not generate this occurrence.
Possible Cause
The Route solver may not have completed all the processing due to other problems.
63
Feature with end leg function did not generate component occurrence
Message
Feature with end leg function did not generate component occurrence.
Severity
High.
Detailed Description
A feature with an end leg function should generate a component occurrence, and the feature did not generate this occurrence.
Possible Cause
This problem may be due to a missing part in the catalog data, or it may be because of a permission group problem. The Route solver may not have completed all the processing due to other problems.
Possible Impacts
The run is invalid because the feature does not have a component occurrence. This situation may impact Reports.
64
Common Route
Feature with user specified parts did not generate part occurrence
Message
Feature with user specified parts did not generate part occurrence.
Severity
High.
Detailed Description
A feature with a component function should generate a component occurrence, and the feature did not generate this occurrence.
Possible Cause
This problem may be due to a missing part in the catalog data, or it may be because of a permission group problem. The Route solver may not have completed all the processing due to other problems.
Possible Impacts
The run is invalid because the feature does not have a component occurrence. This situation may impact Reports.
Severity
High.
Detailed Description
For piping and conduit, the route software uses the outside diameter of the feature for display purposes. When the value is zero at display time, the software tries to get the same information from the run (the run gets it from the default stock part for the corresponding NPD, NPDUnitType, and so forth).
Possible Cause
The error could be due to a software bug. We have identified various cases where this error was reproducible, and those cases have been fixed.
65
Severity
High.
Detailed Description
All duct path features with parts should have the XUserSpecified relation set on them. The software checks those features for this relation and flags the features (IJRtePathFeat) in error with a High severity and ReCompute action.
Possible Cause
Unknown.
Possible Impacts
You may not be able to modify the duct features. Also, the reports generated may not be correct.
66
Common Route
Severity
Fatal.
Detailed Description
According to the data model, the branch feature leg should be different from the inline features leg. In this case, the branch feature leg and the Inline feature leg are the same.
Possible Cause
Unknown. This situation could be due to a software problem.
Possible Impacts
This problem may result in an erroneous network of legs.
Intermediate End Feature and Connected Intermediate End Feature generating part
Message
Intermediate End Feature and Connected Intermediate End Feature generating part.
Severity
High.
Detailed Description
According to the design, only one IEF can generate base components/parts. We will allow one feature to generate the base and another to generate the mating parts.
Possible Cause
This problem might occur when the rules followed for part generation fail.
Possible Impacts
The reports generated may not be valid.
67
Common Route
Severity
Normal.
Detailed Description
The feature length is zero. This feature probably also generates a pipe part, which may or may not be of the same length. In reality, a straight feature can never be less than the minimum pipe length defined in the catalog data.
Possible Cause
Generally occurs due to a software problem. However, there have been instances when it was determined that the catalog data did not define the "Minimum Pipe length rule," in which case the software would create a "minimum pipe length" between Female & Male Components to take care of incompatible ends.
Possible Impacts
The part should be ignored if found in a drawing or report.
Severity
High
Detailed Description
In the Route data model, all features of a leg must belong to the same run. In this case, a leg was found which has features in two or more runs.
Possible Cause
Unknown.
68
Severity
Normal.
Detailed Description
A Route leg should always have features.
Possible Cause
Unknown.
Possible Impacts
No impact. A Route leg is not a first class Business Object, so this error cannot affect anything.
Need to remove the RelConnectionAndPartOcc between the cableocc and the Distribconn
Message
Need to remove the RelConnectionAndPartOcc between the cableocc and the Distribconn
Severity
Crucial
Detailed Description
The Route part occurrence object is missing one or more relations to part objects.
Possible Cause
Unknown.
69
Severity
Normal.
Detailed Description
This error message affects Piping only as only Piping has associated connection items. Depending on the type of connection, some connection items such as welds, gaskets, or bolts should be associated with the connection. No To Do Record is associated with the connection or the connected parts/features.
Possible Cause
This problem often occurs when one of the close features has an associated To Do Record. Because of this problem, the semantic that gets the connection items has not been triggered.
Possible Impacts
The Drawings and Reports task will not have the right information.
Severity
High.
Detailed Description
Cableway and duct ends, turns, branch features, and duct ports should have valid cross section parameters. An example is when the width is less than the distance tolerance.
70
Possible Impacts
The network is erroneous, and the objects may not display properly.
Severity
High.
Detailed Description
A Parent Connection, generally created between two flanges can only generate a "BoltSet" object. If it generates other connection items, then this problem occurs.
Possible Cause
Unknown. This situation may be due to a software problem.
Possible Impacts
The Drawings and Reports task will not have the right information.
71
Common Route
Severity
High
Detailed Description
The value of the Type property of the Piping feature does not match the value of the Type property of the related base part.
Possible Cause
An error in an earlier version of SmartMarine 3D software did not set the parts property correctly.
Possible Impacts
Reports generated using the Type property of the part will be incorrect.
Severity
Crucial.
Detailed Description
A Route Part has lost its relationship to its run.
Possible Cause
Unknown.
Possible Impacts
In certain cases, this error may prevent some modifications of the run.
72
Common Route
Severity
High.
Detailed Description
A Route Part has lost its relationship to its run.
Possible Cause
Unknown.
Possible Impacts
The Drawings and Reports task and filters will not have the right information.
Severity
High.
Detailed Description
A pipe surface-mounted feature exists without an attach connection.
Possible Cause
Unknown.
Possible Impacts
You may not be able to modify the surface-mounted feature. Also, the reports generated may not be correct.
73
Common Route
Severity
Normal.
Detailed Description
A port is not connected to any part.
Possible Cause
Sometimes a part occurrence is deleted, but due to permission boundaries, the ports are still left.
Possible Impacts
The reports generated may be incorrect.
Severity
High
Detailed Description
The route part occurrence object is missing one or more relations to part objects.
Possible Cause
Unknown
Possible Impacts
Possible problems in modeling and in the placement of hangers.
74
Common Route
Severity
High
Detailed Description
The route part occurrence in the model does not have the required relation to the part definition in the Catalog.
Possible Cause
Part object is missing from the Catalog.
Possible Impacts
Display and modification of the affected feature will be limited until the situation is corrected. You will not be able to generate Isometric drawings if this relation is missing.
Severity
High
Detailed Description
Beginning with Version 2009 (8.0), all piping part occurrence objects must have a relation to the Material Control Data object in the Catalog. This object is missing that relation.
Possible Cause
1. Material Control Data object is missing from the Catalog. 2. Part object is missing from the Catalog
Possible Impacts
You will not be able to generate Isometric drawings if this relation is missing
75
Severity
High.
Detailed Description
The relationship between the part occurrence and the catalog part is not using a name proxy (the name of the part in catalog), but instead is using its OID.
Possible Cause
A possible cause was identified and fixed in 4.0.24.
Possible Impacts
The Drawings and Reports task will not have the right information. Also, if the catalog part is bulk loaded again, the relationship will be lost.
Severity
High.
Detailed Description
All the route part occurrences in the database should belong to the same Permission Group or Approval Status of the associated features. The software attempts to synchronize them such that these objects are in the same Permission Group or Approval Status. When they are not in same Permission Group or Approval Status, it can break the software and un-necessary connections get created, causing confusion.
76
Possible Impacts
Users might not be able to delete the features/runs. Two part occurrences that are adjacent to each other might not have connections between them. Hence they may not have proper connection items (such as welds, etc) in some cases.
Run with no feature that has an entry in the Spatial Index table (Range)
Message
Run with no feature that has an entry in the Spatial Index table (Range).
Severity
Normal.
Detailed Description
A run that has no feature should not have a range.
Possible Cause
A problem existed in the code in V4.0.x that could lead to this condition. The problem was fixed in 4.1.x, so this problem should only show up on V4.0 migrated models.
Possible Impacts
The run has an invalid range, so operations based on ranges could be affected (for example, queries or fitting windows).
77
Common Route
Severity
Normal.
Detailed Description
All runs (pipe/duct/conduit/cableway) must have a specification associated to them. Because the specification dictates the part selection (rule defined), it is very important that a run has a relation to a specification.
Possible Cause
After creating runs in the Model database, the user may have deleted the specifications in the catalog. The user can run the Synchronize Model with Catalog command in the Project Management task, and then the runs are added to the To Do List.
Possible Impacts
Users will not be able to modify such runs. Attempting to modify such runs will result in To Do records. The solver will create To Do records for the run or features based on the type of modification.
Severity
Crucial.
Detailed Description
A run should always have a parent system (a pipeline).
Possible Cause
Unknown.
Possible Impacts
Any modification of the run will fail.
78
Severity
Fatal.
Detailed Description
A straight feature should never generate a mating part.
Possible Cause
Unknown. This situation could be due to a software problem.
Possible Impacts
The Drawings and Reports task will not have the right information.
Severity
High.
Detailed Description
A straight feature should always generate a stock part occurrence.
Possible Cause
The Route solver may not have completed all the processing due to other problems.
Possible Impacts
The run is invalid because a straight feature does not have a stock part occurrence. This situation may impact Reports.
79
Severity
High.
Detailed Description
A surface-mounted feature is not connected to an inline feature.
Possible Cause
Unknown.
Possible Impacts
You may not be able to modify the surface-mounted feature. Also, the reports generated may not be correct.
Severity
Normal.
Detailed Description
A tap feature should always be associated with a tapped feature.
Possible Cause
Unknown. In a delete scenario, the tapped feature might have been deleted, leaving only a tap feature.
Possible Impacts
You may not be able to modify the tap feature. Also, the reports generated may not be correct.
80
Severity
Normal.
Detailed Description
The turn feature has a very small angle (less than 0.1 degree).
Possible Cause
This problem may be caused while you are routing, for example, when directly keying in coordinates, or when snapping nozzles that are not exactly aligned. Another case is when the Route solver finds other problems that prevent processing to fix the topology.
Possible Impacts
Modifying runs with very small turns can have unpredictable results.
Severity
Fatal.
Detailed Description
A turn feature will always be associated to two legs. One leg will be associated to the turn feature as the primary leg. In this case, this primary leg relation is not set.
Possible Cause
This situation might occur because of a software problem.
Possible Impacts
You may not be able to access the turn feature properties. This turn feature may have to be deleted.
81
Severity
Crucial.
Detailed Description
A turn feature must have two associated legs for the software to work properly. For example, the bend angle of the turn feature is computed using these two legs.
Possible Cause
Unknown. This problem may have arisen during a delete operation, when the network is routed using different permission groups.
Possible Impacts
You may not be able to access the turn feature properties. The turn feature may have to be deleted.
82
SECTION 5
Common Space
This section contains Common Space database integrity messages.
Severity
High.
Detailed Description
Active Entity has no Space Geometry associated with it. The AE holds the reference (through a relation) about the inputs for construction. Because the AE has become orphaned, this object is not selectable or displayable in a graphic view or in the Workspace Explorer.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
No impact. Orphaned object remains in the database.
Severity
High.
Detailed Description
Space and Space Child objects are connected through the Space Hierarchy relation. The hierarchy is such that all the objects are connected to the project root. In a healthy database, no
83
Common Space
loop exists in the hierarchy. However, in this case, the database integrity script has detected a space hierarchical loop in the Model database for the space objects.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
The objects may not display in the Workspace Explorer and graphic view, as the object is not connected to the project root.
Severity
High.
Detailed Description
Space Association Active Entity has no Graphic Object. The Active Entity object will be created when a graphic object is connected with a Space object. This object stores the transformation matrix of the graphic object. The matrix will be used for the transformation of the associated space object.
Possible Cause
Coding or data model propagation errors in an earlier version.
Possible Impacts
The space cannot be used for further association.
84
Common Space
Space Association Active Entity has no Space Entity associated to the Graphic Object
Message
Space Association Active Entity has no Space Entity associated to the Graphic Object.
Severity
High.
Detailed Description
Space Association Active Entity has no Space Entity associated to the Graphic Object. The Active Entity object will be created when a graphic object is connected with a Space object. This object stores the transformation matrix of the graphic object. The matrix will be used for the transformation of the associated space object.
Possible Cause
Coding or data model propagation errors in an earlier version.
Possible Impacts
No impact.
Severity
High.
Detailed Description
Space Boolean Operator does not have Space Geometry. The Space Geometry holds the graphic representation of the space object. It forwards all the display-related query interfaces to graphic representation.
Possible Cause
Coding or data model errors in an earlier version.
85
Severity
High.
Detailed Description
Space Boolean Operator is not connected to Space By Boolean Active Entity. SpaceByBoolAE is responsible for holding the construction spaces.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
SpaceBoolOperator object becomes orphaned.
Severity
High.
Detailed Description
Space By Boolean Active Entity is not connected to a Space Boolean Operator. Space Bool Operator stores the operation type (MergeSpace/BoundBySpace) and index. Space Bool Operator connects the SpaceByBooleanAE and SpaceGeometry.
86
Possible Impacts
Modification of the resultant volume is not possible.
Severity
High.
Detailed Description
Space By Path Active Entity does not have a Path. Path is the Sketch3D path and is one of the inputs to the SpaceByPathAE for placing a volume along a path.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Editing of the path is not possible.
87
Common Space
Severity
High.
Detailed Description
Space By Path Active Entity does not have a Cross Section. Cross Section is one of the inputs to the SpaceByPathAE to place a volume along a path. Cross Section will be one of two types: 1) a Visual Basic symbol with parameters controlled from the catalog, or 2) Sketch 3D, controlled using the Profile Sketch.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Modification of the cross section attributes (like dimensions) is not possible.
Space By Plane and Offset Active Entity does not have the Fence input Points
Message
Space By Plane and Offset Active Entity does not have the Fence input Points.
Severity
High.
Detailed Description
A Space By Plane and Offset Active Entity does not have Fence input Points.
Possible Cause
Coding or data model errors in an earlier version.
88
Space By Plane and Offset Active Entity does not have the Reference Plane
Message
Space By Plane and Offset Active Entity does not have the Reference Plane.
Severity
High.
Detailed Description
A Space By Plane and Offset Active Entity does not have a Reference Plane.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Modification is not possible.
Severity
High.
Detailed Description
Space By Points Active Entity has no input Points.
Possible Cause
Coding or data model errors in an earlier version.
89
Severity
High.
Detailed Description
Space By Primitive Active Entity has no Geometry. Geometry is the output from the SpaceByPrimitiveAE.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Object will not be seen in the graphic view. Modification will not be possible.
Severity
High.
Detailed Description
Space Entity does not have a Catalog Part connected to it.
Possible Cause
Coding or data model errors in an earlier version.
90
Severity
High.
Detailed Description
Space Entity does not have a Range (no data). No entry has been found in CoreSpatialIndex table.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Geometry will be invalid. There is no other impact.
91
Common Space
Severity
High.
Detailed Description
Space Entity does not have SpaceGeometry. The Space Geometry of the Space object contains all the necessary graphical representation information. Due to this error, the space object will not have a graphic representation.
Possible Cause
Coding or data model propagation errors in a previous version.
Possible Impacts
The Space object will not be seen in a graphic view. However, you can select it in the Workspace Explorer. The default modification command is activated, since the construction inputs and the geometry are not attached to it.
Severity
High.
Detailed Description
Space Geometry has no Active Entity associated with it. This active entity is responsible for getting the inputs for the construction.
Possible Cause
Coding or data model errors in an earlier version.
92
Severity
High.
Detailed Description
Space Geometry is not connected to any Space Entity. The Space Entity is necessary to manipulate all the information and data for different types of spaces. The space geometry provides the graphical representation information.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Object becomes orphaned and will not be seen in the Workspace Explorer or in a graphic view. No other impact.
Severity
Normal.
Detailed Description
A space object does not have a local coordinate system.
Possible Cause
Coding or data model propagation errors in an earlier version.
93
Severity
Normal.
Detailed Description
A space object has more than one space parent or design parent.
Possible Cause
Coding or data model propagation errors in an earlier version.
Possible Impacts
No impact. You can see the object under more than one parent in the Workspace Explorer.
Severity
High.
Detailed Description
Space Child does not have a Parent.
Possible Cause
Coding or data model propagation errors in an earlier version.
94
Severity
High.
Detailed Description
SpatialOrientation stores the local orientation of the Space object and has relationships with the SpaceGenericEntity object and Sketch3D object.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
The object becomes orphaned and will not be seen in the Workspace Explorer or in a graphic view. No other impact.
95
Common Space
96
SECTION 6
Common Structure
This section contains SmartMarine 3D Common Structure database integrity messages.
Severity
Low.
Detailed Description
The StructPortSelector is in an invalid permission group. The StructPortSelector is not a first class business object, but it is used by structure business objects in order to expose ports. This object actually makes the link between a port and its source geometry. As opposed to ports, StructPortSelectors are placed in a permission group. The problem related to this DB integrity error is that the StructPortSelector is in a permission group that is different from the business object permission group.
Possible Cause
This error appears because in some cases the StructPortSelector is created dynamically and placed by default in the current permission group.
Possible Impacts
Related business objects that expose ports may not be able to be deleted.
97
Common Structure
Severity
Crucial.
Detailed Description
An Opening has no relation to an OpeningType object which defines some particular properties for the Opening; for example, Cutting Limit.
Possible Cause
Copying/Pasting an Opening.
Possible Impacts
At edit time, an Opening which does not go through all of the structure on which it is applied will not have the correct Cutting Limit value ("Through All" instead of "User Defined").
Severity
Crucial.
Detailed Description
An Opening has no relation to an OpeningType object which defines some particular properties for the Opening; for example, Cutting Limit.
Possible Cause
Copying/Pasting an Opening.
Possible Impacts
At edit time, an Opening which does not go through all of the structure on which it is applied will not have the correct Cutting Limit value ("Through All" instead of "User Defined").
98
Severity
High.
Detailed Description
The relationship relating the cutout BO operator to the cutout active entity is missing.
Possible Cause
Unknown.
Possible Impacts
This orphaned cutout no longer cuts the Structural geometry on which it is applied.
Severity
Low.
Detailed Description
A connection is connected to the ports exposed by the connected business objects. There must be at least one connected port, so that the connection geometry can be evaluated.
Possible Cause
Unknown.
Possible Impacts
There is a standalone connection in the model with no connected objects.
99
Severity
Crucial.
Detailed Description
The relationship (named "FromOutputColltoPutputs") between the 3-D curve defining the cutout shape and the symbol's output collection is missing in the model.
Possible Cause
Unknown.
Possible Impacts
The cutout can no longer be edited or deleted. It must be removed from the model.
Severity
High.
Detailed Description
The relationship relating the cutout BO operator to the 3-D curve defining its geometry is missing in the model.
Possible Cause
Unknown.
100
Severity
Low.
Detailed Description
The role of the generation active entity is to supply the first geometry state of a graphic business object. If no parent is connected, the graph of geometries cannot be updated.
Possible Cause
Unknown.
Possible Impacts
The related business object display does not correspond to its real geometrical state.
Severity
Low.
Detailed Description
An operation has been disconnected from the geometrical graph of a business object. There is no operand geometry connected.
101
Possible Impacts
The related business object display does not correspond to its real geometrical state.
Severity
Low.
Detailed Description
A port is not connected to its source object. For instance, a face port has been disconnected from the solid geometry it is extracted from. The problem is that other objects can depend on this port.
Possible Cause
Unknown
Possible Impacts
Dependent objects may not be able to update their geometry correctly.
102
Common Structure
Severity
Low.
Detailed Description
The object has no related geometry. In other words, the graphic entity has no graphic to display.
Possible Cause
Unknown.
Possible Impacts
The related business object is not visible in the graphic view.
Severity
Low.
Detailed Description
The StructPortSelector is not a first class business object, but it is used in the geometries graph of a business object in order to expose its ports. This object actually makes the link between a port and its source geometry. So the problem is similar to the one represented by the Orphaned Struct Port error.
Possible Cause
Unknown.
Possible Impacts
Dependent objects may not be able to update their geometry correctly.
103
104
Compartmentation
SECTION 7
Compartmentation
This section contains Compartmentation database integrity messages.
Severity
High.
Detailed Description
Compart By Path Active Entity does not have a Path. This Path is the Sketch3D path and is one of the inputs to the CompartByPathAE for placing a volume along a path.
Possible Cause
Coding or data model errors.
Possible Impacts
Editing of the path is not possible.
105
Compartmentation
Severity
High.
Detailed Description
Compart By Path Active Entity does not have a Cross Section. The Cross Section is one of the inputs to the CompartByPathAE to place a volume along a path. The Cross Section will be one of two types: 1) a Visual Basic symbol with parameters controlled from the catalog, or 2) Sketch 3D, controlled using the Profile Sketch.
Possible Cause
Coding or data model errors.
Possible Impacts
Modification of the cross section attributes (such as dimensions) is not possible.
Severity
High.
Detailed Description
Compart By Points Active Entity has no input Points.
Possible Cause
Coding or data model errors.
106
Severity
High.
Detailed Description
Compart By Primitive Active Entity has no Compart Geometry. Compart Geometry is the output from CompartByPrimitiveAE.
Possible Cause
Coding or data model errors.
Possible Impacts
The object is not seen in the graphic view. Modification is not possible.
107
Compartmentation
Severity
High.
Detailed Description
Compart Entity does not have Compart Geometry. The Compart geometry of the Compart object has all the graphical representation information. Due to this error, the Compart object will not have a graphic representation.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
The Compart object will not be seen in a graphic view. However, it can be selected from the Workspace Explorer. However, the default modification command is activated, because the construction inputs and the geometry are not attached to it.
Severity
High.
Detailed Description
Compart Geometry is not connected to Compart Entity. The Compart Entity is necessary to manipulate all the information and data for the different types of Compartments. Compart Geometry provides the graphical representation information.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
The object becomes orphaned and will not be seen in the Workspace Explorer as well as in the graphic view. No other impact.
108
Severity
High.
Detailed Description
Compart Geometry does not have Geometry. The Compart geometry of the Compart object has all the graphical representation information.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
The object remains as orphaned in the database.
Severity
High.
Detailed Description
The Compart Geometry is not connected to the Space CreationAE. This active entity is responsible for getting the inputs for the construction.
Possible Cause
Coding or data model errors.
109
Severity
High.
Detailed Description
Compart Boolean Operator does not have Compart Geometry. The Compart Geometry holds the graphic representation of the Compart object. It forwards all the display-related query interfaces to the graphic representation.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
This object is not visible in the graphic view. Modification of the resultant Compartment is not possible.
110
Compartmentation
Severity
High.
Detailed Description
CompartBoolOperator is not connected with CompartByBooleanAE. CompartByBooleanAE is responsible for holding the construction of Compartments.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
The CompartBoolOperator object becomes orphaned.
Severity
High.
Detailed Description
CompartBoundByFace is not connected to CompartByBound.
Possible Cause
Coding or data model errors.
Possible Impacts
Modification is not possible.
111
Severity
High.
Detailed Description
The CompartBoundByFace has no CompartByBound or CompartBySplit. The CompartBoundByFace holds the reference (through a relation) about the inputs for construction. Because the CompartBoundByFace has become orphaned, this object is not selectable or displayable in a graphic view or in the Workspace Explorer.
Possible Cause
Coding or data model errors.
Possible Impacts
Modification is not possible.
Severity
High.
Detailed Description
CompartBoundByFace is not associated with Geometry as input.
Possible Cause
Coding or data model errors.
112
Severity
High.
Detailed Description
The CompartByBoolean Active Entity is not connected to a CompartBoolOperator, which stores the operation type (MergeCompartment/BoundByCompartment) and index. CompartBoolOperator connects the CompartByBooleanAE and CompartGeometry.
Possible Cause
Coding or data model errors.
Possible Impacts
Modification of the resultant volume is not possible.
Severity
High.
Detailed Description
The CompartByBoolean Active Entity has no CompartGeometry associated with it. The CompartByBooleanAE holds the reference (through a relation) about the inputs for construction.
113
Compartmentation
Because the CompartByBooleanAE has become orphaned, this object is not selectable or displayable in a graphic view or in the Workspace Explorer.
Possible Cause
Coding or data model errors.
Possible Impacts
No impact. The orphaned object remains in the database.
Severity
High.
Detailed Description
CompartByBound has no Compart Geometry associated with it. CompartByBound holds the reference (through a relation) about the inputs for construction. Because CompartByBound has become orphaned, this object is not selectable or displayable in a graphic view or in the Workspace Explorer.
Possible Cause
Coding or data model errors.
Possible Impacts
No impact. The orphaned object remains in the database.
114
Compartmentation
Severity
High.
Detailed Description
CompartByBound is not connected with a CompartByBoundFace object.
Possible Cause
Coding or data model errors.
Possible Impacts
Modification is not possible.
Severity
High.
Detailed Description
The CompartbyBound Active Entity has Geometry associated with it through the relation ByFacesAmbiguity. The CompartbyBound holds the reference (through a relation) about the inputs for construction.
Possible Cause
Coding or data model errors.
Possible Impacts
No impact. The orphaned object remains in the database.
115
Severity
High.
Detailed Description
CompartByImport Active Entity has no Compart Geometry associated with it. CompartByImportAE holds the reference (through a relation) about the inputs for construction. Because CompartByImportAE has become orphaned, this object is not selectable or displayable in a graphic view or in the Workspace Explorer.
Possible Cause
Coding or data model errors.
Possible Impacts
No impact. The orphaned object remains in the database.
Severity
High.
Detailed Description
CompartByImportAE has no input points.
Possible Cause
Coding or data model errors.
116
Severity
High.
Detailed Description
CompartByPath Active Entity has no Compart Geometry associated with it. CompartByPathAE holds the reference (through a relation) about the inputs for construction. Because CompartByPathAE has become orphaned, this object is not selectable or displayable in a graphic view or in the Workspace Explorer.
Possible Cause
Coding or data model errors.
Possible Impacts
No impact. The orphaned object remains in the database.
117
Compartmentation
Severity
High.
Detailed Description
CompartByPoints Active Entity has no Compart Geometry associated with it. CompartByPointsAE holds the reference (through a relation) about the inputs for construction. Because CompartByPointsAE has become orphaned, this object is not selectable or displayable in a graphic view or in the Workspace Explorer.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
No impact. The orphaned object remains in the database.
Severity
High.
Detailed Description
CompartByPrimitive has no CompartShapeDef object as input.
Possible Cause
Coding or data model errors.
Possible Impacts
Modification of the object is not possible.
118
Severity
High.
Detailed Description
The CompartGeometry has no CompartBySplitAE associated with it. The CompartGeometry holds the reference (through a relation) about the inputs for construction. Because the CompartGeometry has become orphaned, this object is not selectable or displayable in a graphic view or in the Workspace Explorer.
Possible Cause
Coding or data model errors.
Possible Impacts
No impact. The orphaned object remains in the database.
Severity
High.
Detailed Description
The CompartSplitAE Active Entity has no CompartBoundByFace associated with it. The CompartSplitAE holds the reference (through a relation) about the inputs for construction. Because the CompartSplitAE has become orphaned, this object is not selectable or displayable in a graphic view or in the Workspace Explorer.
119
Possible Impacts
No impact. The orphaned object remains in the database.
Severity
High.
Detailed Description
The CompartSplitAE Active Entity has no CompartGeometry associated with it. The CompartSplitAE holds the reference (through a relation) about the inputs for construction. Because the CompartSplitAE has become orphaned, this object is not selectable or displayable in a graphic view or in the Workspace Explorer.
Possible Cause
Coding or data model errors.
Possible Impacts
No impact. The orphaned object remains in the database.
120
Compartmentation
Severity
High.
Detailed Description
The CompartSplitAE Active Entity has Geometry associated with it through the relation Computedgeometry. The CompartSplitAE holds the reference (through a relation) about the inputs for construction.
Possible Cause
Coding or data model errors.
Possible Impacts
No impact. The orphaned object remains in the database.
Severity
High.
Detailed Description
Spatial Load Combination object is not connected to its Load Folder object.
Possible Cause
Coding or data model errors.
Possible Impacts
Modification is not possible.
121
Spatial Load Folder object has no Parent (Configure Project Root or Load Folder) object
Message
Spatial Load Folder object has no Parent (Configure Project Root or Load Folder) object.
Severity
High.
Detailed Description
Load Folder object is not connected to its Configure Project Root or Load Folder object.
Possible Cause
Coding or data model errors.
Possible Impacts
Modification is not possible.
Severity
High.
Detailed Description
Spatial Load object is not connected to its Compart Geometry. The geometry for the load object is not available.
Possible Cause
Coding or data model errors.
122
Severity
High.
Detailed Description
Spatial Load object is not connected to its parent object (Load Combination).
Possible Cause
Coding or data model errors.
Possible Impacts
Modification is not possible.
123
Compartmentation
124
SECTION 8
Core
This section contains Core database integrity messages.
Severity
High if the error occurs in the Model database. Harmless if it occurs in the Catalog.
Detailed Description
This error is an internal error that causes a user object to be inaccessible to any computation or modification.
Possible Cause
In the Model: The error is internal, and development needs to investigate. In the Catalog: The object is completely inaccessible; therefore, the error is harmless.
Possible Impacts
An object might appear impossible to modify. It might be impossible to get the properties of the object.
See Also
Clean a Database (on page 39)
125
Core
Severity
High if the error occurs in the Model database or in the Catalog.
Detailed Description
This error is an internal error that causes a user object to be inaccessible to any computation or modification.
Possible Cause
A Symbol has failed to reconnect to some internal objects. This situation is most likely to happen if a copy or calculation happened when one of the objects created or referenced by the Symbol is unavailable, leaving the Symbol in an incomplete state. It can also happen when there is a problem with permissions or when a server or DLL is not available.
Possible Impacts
An object might appear impossible to modify. It might be impossible to get the properties of the object.
Severity
High.
Detailed Description
This error indicates that there is retrieved information that violates some condition, otherwise unspecified, in the data model. Further research or other documentation is required to find the cause of the problem.
126
Possible Impacts
This will depend on the nature of the data in the model.
Severity
Low.
Detailed Description
These objects with range information are not related to anything, and could cause performance issues if a query were made based on range.
Possible Cause
The object was saved in an invalid state.
Possible Impacts
With many orphan geometry objects in the database, performance could be affected for a query based on range.
See Also
Clean a Database (on page 39)
127
Core
Severity
Low.
Detailed Description
An object has too many relations of the same type with another object. This situation is not supposed to occur.
Possible Cause
Internal error.
Possible Impacts
There may be a very small performance impact when accessing that object.
Severity
High.
Detailed Description
The object has an invalid range or another invalid geometric property.
Possible Cause
The object was saved in an invalid state.
Possible Impacts
The object will not be able to display itself. In the case of invalid range, it could create a false interference checking report.
128
Core
2. Run the Clean Database custom command, and select the objects in error.
Severity
Medium.
Detailed Description
The object exists in the database, but it is not possible to bring that object into memory while modeling.
Possible Cause
Internal error. Development needs to investigate.
Possible Impacts
Such phantom objects can appear in reports and therefore lead to false reporting results.
See Also
Clean a Database (on page 39)
Severity
Crucial
Detailed Description
Moniker name of object is incorrect.
Possible Cause
After upgrading a database, the Database > Integrity command reports objects with the incorrect moniker name.
Possible Impacts
Cleaning the database modifies the moniker name of the object.
129
See Also
Clean a Database (on page 39)
Severity
High.
Detailed Description
This error indicates that there is retrieved information that violates cardinality rules.
Possible Cause
A typical cause of this error is a bug in an upstream application. More rarely, there is an unforeseen workflow that the SmartPlant adapter is not prepared to handle.
Possible Impacts
Comparison between design basis objects and model objects may show that correlation is not possible, or that correlation is not established. Also, partial data loss can occur. The data associated with a shared object may not be associated to a model object.
Severity
High.
Detailed Description
This error indicates that there is retrieved information that is not connected to any drawing or other document.
130
Possible Impacts
Database will be bloated with unused data.
Severity
High.
Detailed Description
This error indicates that there is retrieved information in which a single name resolves to multiple objects stored in the model.
Possible Cause
A typical cause of this error is a bug in an upstream application. More rarely, there is an unforeseen workflow that the SmartPlant adapter is not prepared to handle.
Possible Impacts
The most likely impact is that two-dimensional drawings will be incorrectly displayed because multiple objects that represent items in the drawings overlap. The wrong drawing can be displayed. This situation is due to an incorrect correlation between the retrieved design basis object and the model object. The model object may be correlated to an older duplicate object. There is no way to identify which object is correct, so both duplicate objects must be removed.
131
Core
Severity
High.
Detailed Description
This error indicates that there is retrieved information in which duplicate or conflicting information is stored.
Possible Cause
A typical cause of this error is a bug in an upstream application. More rarely, there is an unforeseen workflow that the SmartPlant adapter is not prepared to handle.
Possible Impacts
The most likely impact is that two-dimensional drawings will be incorrectly displayed because multiple objects that represent items in the drawings overlap. Multiple drawings with the same name are persisted in the model. There is no way to identify which view is correct, so both must be removed.
Severity
Crucial
Detailed Description
A duplicate generic end data record exists in the database.
Possible Cause
After upgrading a database, the Database > Integrity command reports the duplicate records.
Possible Impacts
Cleaning the database deletes the duplicate records.
132
See Also
Clean a Database (on page 39)
The object does not exist but another object has a relation to it
Message
The object does not exist but another object has a relation to it.
Severity
Medium.
Detailed Description
An object has been deleted or was never committed in the database, but other objects still have a relation to that object.
Possible Cause
Internal error. Development will investigate.
Possible Impacts
Some objects might not find an expected related object, and some failures can occur. In general, objects are robust enough to deal with such a missing relation.
133
Core
The proxy does not have a parent; therefore, it cannot find its source
Message
The proxy does not have a parent; therefore, it cannot find its source.
Severity
Varies from High to Low.
Detailed Description
An internal relation between objects called Proxies has been broken. The proxy does not have a parent; therefore, it cannot find its source. Sometimes, an island of objects is not accessible. In that case, the error is harmless.
Possible Cause
This error is an internal error and will be investigated by a development team.
Possible Impacts
Some equipment items might not be able to find their parts.
Severity
Very Low.
Detailed Description
The proxy exists, but it is not connected to any other object. An internal object is completely inaccessible.
Possible Cause
No known cause. Development will investigate the situation.
134
135
Core
136
SECTION 9
Severity
Crucial.
Detailed Description
A file that was blobbed into the database is not usable. This problem can occur due to the deletion of the file after it was un-blobbed to the disk and before blobbing the modified file.
Possible Cause
A workflow that creates this problem has not been identified yet.
Possible Impacts
You may lose some manually placed labels or dimensions, and user graphics modifications.
Child Property object's approval status or permission group does not match with the parent Property Object
Message
Child Property object's approval status or permission group does not match with the parent Property Object.
Severity
Critical.
137
Possible Cause
Unknown.
Possible Impacts
This problem can potentially stop an update or delete operation on the drawing sheet.
Severity
Crucial.
Detailed Description
The drawing generation process creates one or more files known as DocumentData objects, such as Update Log, User Graphics, View Monikerization File, and Exclude/Hidden Objects. The DocumentData objects are stored in the model database, related to the Document Output Manager collection, and used (with the exception of Update Log) to regenerate the drawing on successive updates. Each file is given a unique name and is retrieved by name. It is very important that these DocumentData objects remain uniquely named within the Document Output Manager.
Possible Cause
Unknown.
Possible Impacts
When you open, edit, or update an existing drawing, redundantly named DocumentData objects can lead to the incorrect drawing object being chosen. The drawing file retrieved from the database may also not be the latest revision of that file. This situation could lead to incorrect results when viewing or updating the drawing because the contents of that drawing file may not be properly synchronized with the model.
138
Severity
Crucial.
Detailed Description
The Document Output Manager object has redundant relations with the generated document (DocumentData object). There should be one and only one of these relationships.
Possible Cause
This problem is caused by creating the same relation between the same set of objects without verifying the existence of the relation.
Possible Impacts
When you open, edit, or update an existing Drawing, the redundant relationship existence can lead to the incorrect Drawing object being chosen, and the Drawing file retrieved from the database may not be the latest revision of that file. This situation could lead to incorrect results when viewing or updating and then viewing the Drawing because the contents of that Drawing file may not be properly synchronized with the model.
Document Output Manager object's approval status or permission group does not match with the owning SnapIn or Sheet object
Message
Document Output Manager object's approval status or permission group does not match with the owning SnapIn or Sheet object.
Severity
Critical.
Detailed Description
A Drawing Output Manager object's Approval Status or Permission Group does not match that of the owning SnapIn or Drawing Sheet object. By design, a Drawing Output Manager object must have the same approval status and permission group values as that of the owner object.
139
Possible Impacts
This problem can potentially stop an update or delete operation on the SnapIn or Drawing Sheet.
DocumentData object's approval status or permission group does not match with Document Output Manager
Message
DocumentData object's approval status or permission group does not match with Document Output Manager.
Severity
Critical.
Detailed Description
A Drawing Document Data object's Approval Status or Permission Group does not match that of the Drawing Document Output Manager object. By design, a Document Data object must have the same approval status and permission group values as that of the owner object (Drawing Document Output Manager object).
Possible Cause
When the approval status value of the Document Output Manager was changed (due to the user changing the approval status of Drawing Sheet), the value did not propagate to the Document Data objects.
Possible Impacts
This problem can potentially stop an update or delete operation on the drawing sheet. For example, say that the Document Data objects are in Permission Group 1, and Drawing Sheet and Document Output Manager are in Permission Group 2. If the user does not have permission on Permission Group 1, then he cannot update or delete the drawing sheet object.
140
Drawing Issue object's approval status or permission group does not match with Property Object Child
Message
Drawing Issue object's approval status or permission group does not match with Property Object Child.
Severity
Critical.
Detailed Description
A Drawing Issue object's Approval Status or Permission Group does not match with that of the Property Child object. By design, an Issue object must have the same approval status and permission group values as that of the parent property child object.
Possible Cause
Unknown.
Possible Impacts
This problem can potentially stop a delete or update operation on the drawing sheet or SnapIn.
Drawing Key Plan View object's approval status or permission group does not match with Drawing View object
Message
Drawing Key Plan View object's approval status or permission group does not match with Drawing View object.
Severity
Critical.
Detailed Description
A Key Plan View object's Approval Status or Permission Group does not match with that of the View object. By design, a key plan view object must have the same approval status and permission group values as that of the parent View object.
Possible Cause
Unknown.
141
Severity
High.
Detailed Description
A Drawing object has redundant relations with other objects in the relation's tables.
Possible Cause
This problem is caused by creating the same relation between the same set of objects without verifying the existence of the relation.
Possible Impacts
None.
142
Drawing Revision object's approval status or permission group does not match with Property Object Child
Message
Drawing Revision object's approval status or permission group does not match with Property Object Child.
Severity
Critical.
Detailed Description
A Drawing Revision object's Approval Status or Permission Group does not match with that of the Property Child object. By design, a Revision object must have the same approval status and permission group values as that of the parent property child object.
Possible Cause
Unknown.
Possible Impacts
This problem can potentially stop a delete or update operation on the drawing sheet or SnapIn.
Drawing View Info object's approval status or permission group does not match with Drawing View object
Message
Drawing View Info object's approval status or permission group does not match with Drawing View object.
Severity
Critical.
Detailed Description
A View Info object's Approval Status or Permission Group does not match with that of the View object. By design, a view info object must have the same approval status and permission group values as that of the parent View object.
143
Possible Impacts
This problem can potentially stop a delete or update operation on the drawing sheet.
Drawing View object's approval status or permission group does not match with Drawing Sheet object
Message
Drawing View object's approval status or permission group does not match with Drawing Sheet object.
Severity
Critical.
Detailed Description
A View object's Approval Status or Permission Group does not match with that of the Sheet object. By design, a View object must have the same approval status and permission group values as that of the parent Sheet object.
Possible Cause
Unknown.
Possible Impacts
This problem can potentially stop a delete or update operation on the drawing sheet.
144
Severity
Fatal
Detailed Description
This message identifies a drawing view on a drawing component template sheet that has overrides. A drawing view on a template sheet should never have overrides. The software uses overrides to track the differences between the view on the template and the view on the generated drawing. In cases where the properties of a generated view have been modified to be different than those of the template view, the generated view has corresponding overrides to keep track of the changes.
Possible Cause
A workflow that causes this corruption has not been identified.
Possible Impacts
Updating drawings beneath this component yields unexpected results due to the overrides that exist on the template.
145
Drawing Volume object's approval status or permission group does not match with Drawing View object
Message
Drawing Volume object's approval status or permission group does not match with Drawing View object.
Severity
Critical.
Detailed Description
A Volume object's Approval Status or Permission Group does not match with that of the View object. By design, a volume object must have the same approval status and permission group values as that of the related View object.
Possible Cause
Unknown.
Possible Impacts
This problem can potentially stop a delete or update operation on the drawing sheet or volume.
146
Element Broker object's approval status or permission group does not match with Drawing View object
Message
Element Broker object's approval status or permission group does not match with Drawing View object.
Severity
Critical.
Detailed Description
An Element Broker object's Approval Status or Permission Group does not match with that of the View object. By design, an Element Broker object must have the same approval status and permission group values as that of the parent View object.
Possible Cause
Unknown.
Possible Impacts
This problem can potentially stop a delete or update operation on the drawing sheet.
147
Severity
Crucial
Detailed Description
A Drawing by Query Manager requires a filter in order to update a set of drawings. Without this filter, the drawings associated with this Drawing by Query Manager cannot be updated.
Possible Cause
The object filter associated with the Drawing by Query Manager has been deleted or become erroneous.
Possible Impacts
Any drawings that are associated with the Drawing by Query Manager and missing filter cannot be updated.
Property object's approval status or permission group does not match with Drawing Sheet or SnapIn
Message
Property object's approval status or permission group does not match with Drawing Sheet or SnapIn.
Severity
Critical.
Detailed Description
A Drawing Property object's Approval Status or Permission Group does not match that of the owning Drawing Sheet or SnapIn object. By design, a Property object must have the same approval status and permission group values as that of the owner object (Drawing Sheet or SnapIn object).
Possible Cause
When the approval status value of the Drawing Sheet or SnapIn was changed, the value did not propagate to the Property object.
148
Severity
Low.
Detailed Description
A Drawing PropertyChild object has no relationship with its parent PropertyObject. This relationship is used to expand the flexibility of the PropertyObject to allow user customization. This Drawing PropertyChild is an orphaned object.
Possible Cause
Tables or entries in a table in the Model database may have been deleted or become erroneous. An error may have occurred when creating or deleting a Drawing SnapIn while in the Drawings and Reports task. If you have recently migrated the software to work with a later version, an error may have occurred in the migration process.
Possible Impacts
This object will not be referenced again. There is no negative impact if the database entries for this object remain in the Model database.
149
Severity
Low.
Detailed Description
A Drawing PropertyObject has no relationship with its parent. This relationship is used to store and retrieve property values for objects in the Drawings and Reports task. This Drawing PropertyObject is an orphaned object.
Possible Cause
Tables or entries in a table in the Model database may have been deleted or become erroneous. An error may have occurred when creating or deleting a Drawing SnapIn while in the Drawings and Reports task. If you have recently migrated the software to work with a later version, an error may have occurred in the migration process.
Possible Impacts
This object will not be referenced again. There is no negative impact if the database entries for this object remain in the Model database.
Report object's approval status or permission group does not match with View Generator object
Message
Report object's approval status or permission group does not match with View Generator object.
Severity
Critical.
Detailed Description
A Report object's Approval Status or Permission Group does not match with that of the View Generator object. By design, a Report object must have the same approval status and permission group values as that of the parent View generator object.
Possible Cause
Unknown.
150
Report Template object's approval status or permission group does not match with Drawing View object
Message
Report Template object's approval status or permission group does not match with Drawing View object.
Severity
Critical.
Detailed Description
A Report Template object's Approval Status or Permission Group does not match with that of the View object. By design, a Report Template object must have the same approval status and permission group values as that of the parent View object.
Possible Cause
Unknown.
Possible Impacts
This problem can potentially stop a delete or update operation on the drawing sheet or view.
151
Severity
Low.
Detailed Description
A Drawing Sheet object has no relationship with its parent Drawing SnapIn. This relationship is used in organizing drawings (Drawing Sheets) in the hierarchy in the Management Console and Detail View in the Drawings and Reports task. This Drawing Sheet is an orphaned object.
Possible Cause
Tables or entries in a table in the Model database may have been deleted or become erroneous. An error may have occurred when creating or deleting a drawing (Drawing Sheet) or deleting a Drawing SnapIn while in the Drawings and Reports task. If you have recently migrated the software to work with a later version, an error may have occurred in the migration process.
Possible Impacts
This object will not be referenced again. There is no negative impact if the database entries for this object remain in the Model database.
Severity
Low.
Detailed Description
A Drawing SnapIn object has no relationship with its parent Drawing SnapIn. This relationship is the mechanism for how the hierarchy in the Management Console in the Drawings and Reports task is displayed. This Drawing SnapIn is an orphaned object.
Possible Cause
Tables or entries in a table in the Model database may have been deleted or become erroneous. An error may have occurred when creating or deleting a Drawing SnapIn while in the Drawings and Reports task. If you have recently migrated the software to work with a later version, an error may have occurred in the migration process.
152
Severity
Fatal.
Detailed Description
A Drawing SnapIn object has no relationship with a Drawing PropertyObject. The Drawing PropertyObject is used to store and retrieve all user properties (displayed by right-clicking and choosing Properties). This relationship is mandatory for the correct operation of a Drawing SnapIn. Without it, the Drawing SnapIn will not be usable in the Drawings and Reports task.
Possible Cause
Tables or entries in a table in the Model database may have been deleted or become erroneous. An error may have occurred when creating or deleting a Drawing SnapIn while in the Drawings and Reports task. If you have recently migrated the software to work with a later version, an error may have occurred in the migration process.
Possible Impacts
The Drawing SnapIn identified by this message is not usable in the Drawings and Reports task. Any drawings that are located under this SnapIn may be incorrect or irretrievable. No new drawings can be created underneath this Drawing SnapIn.
153
Severity
Crucial.
Detailed Description
A Drawing snapshot view has no relationship with a Drawing volume. This relationship is needed to identify the area to be drawn.
Possible Cause
The volume was unintentionally deleted.
Possible Impacts
The view can no longer be updated.
Template Manager object's approval status or permission group does not match with Parent Drawing Type or Sheet
Message
Template Manager object's approval status or permission group does not match with Parent Drawing Type or Sheet.
Severity
Critical.
Detailed Description
The Template Manager object's Approval Status or Permission Group does not match with the owning Drawing Type or Drawing Sheet object. The Template Manager holds the information of the template. By design, a Template Manager object must have the same approval status and permission group values as that of the owner object (Drawing Type for Volume and Orthographic Database Query Drawings, Drawing Sheer for Composed Drawings).
Possible Cause
When the Approval Status or Permission Group value of the parent Snapin/Sheet was changed, the value did not propagate to the Template Manager object.
154
Severity
High.
Detailed Description
Creation of a Spatial drawing component or a composed drawing also results in the creation of a Template Manager object. This Template Manager stores the templates used for the creation of drawings. For a Spatial drawing component, the Template Manager stores the template created by Edit Template. For a Composed drawing, the Template Manager stores Border and Layout templates associated with a Composed drawing. A Template Manager object without a Spatial drawing component or Composed drawing serves no purpose, and must be deleted.
Possible Cause
Unknown, but not a common occurrence.
Possible Impacts
None.
155
Severity
Fatal.
Detailed Description
A Drawing Component has a corrupted template. As defined by the Drawings Data Model, the Drawings Volume component must have a template. A template usually has one or more Smart Frames that contain the graphics to be created on an update operation. These Smart Frames are linked indirectly to Drawing View objects, which store all the information of the Smart Frames (view definition). The link between the Smart Frames and the drawing view has been lost. This means that the Drawings application cannot regenerate the drawings on an update operation because necessary information is missing.
Possible Cause
A workflow that causes this problem has not been identified yet.
Possible Impacts
Once the template sheet is corrupted, it becomes unusable: A volume cannot be associated to the corrupted component. This means that a new drawing cannot be created. Existing drawings under this volume component will not produce the correct results on an update operation. Copies of the corrupted template will be corrupted too.
156
SECTION 10
Severity
High, Medium, Low.
Detailed Description
Assembly Constraint (relationship) object is not related to an equipment item anymore.
Possible Causes
The cause is currently unknown.
Possible Impacts
Some commands may not work properly. Possible erroneous or inaccurate Equipment reports.
157
Severity
Normal.
Detailed Description
Cable nozzles should have the proper orientation vectors declared. The orientation vectors should not be persisted as NULL values as we specify 1,0,0 for orientation and 0,1,0 for radial orientation vectors (DistribPortType_CABLE).
Possible Cause
Undetermined workflow in the Place Nozzle command.
Possible Impacts
The cable nozzle might be displayed incorrectly.
Severity
Normal.
Detailed Description
Conduit nozzles should have proper orientation vectors declared. The orientation vectors should not be persisted as NULL values as we specify 1,0,0 for orientation and 0,1,0 for radial orientation vectors (DistribPortType_CONDUIT).
Possible Cause
Undetermined workflow in the Place Nozzle command.
Possible Impacts
The conduit nozzle might be displayed incorrectly.
158
Severity
Normal.
Detailed Description
A Design Equipment with no children (no Shape or Standard Equipment) is not supposed to have any range stored in the CORESpatialIndex(range) table. The DB integrity scripts check to see if there is any Design Equipment with no children, but with an entry in the range table.
Possible Cause
Prior to Version 4.1, the design equipment range with no children was stored in the range table. This problem was fixed in V4.1, but existing data was not migrated. This script will report them in the DBIntegrity report.
Possible Impacts
This situation could cause problems in range calculations. This situation places unnecessary entries in the range table.
Severity
High.
Detailed Description
The equipment is not related to its system parent anymore. This situation is unexpected.
Possible Causes
The cause at run-time is currently unknown. The cause could be external, for example, database manipulation.
159
Severity
High.
Detailed Description
The equipment has Double, Undefined values persisted for the center-of-gravity (CG) values.
Possible Cause
The cause could be that the values of the CG properties (wet and dry) are persisted with the C/C++ definition for NULL instead of SQL NULL.
Possible Impacts
If the values of the CG properties (wet and dry) are persisted with DBL_UNDEFINED values instead of SQL NULL, any query that has these columns will cause an overflow error on SQL Server 2005.
160
Severity
Crucial.
Detailed Description
The part definition in the catalog for the standard equipment or in the model for the design equipment has been deleted. Standard Equipment If Synchronize has not been run, the equipment is not put in the To Do List. For this reason, a simple re-bulkload of the part (with the same name, same input parameters, and same outputs) will reconnect the part. If Synchronize has been run, the equipment is in the To Do List. No reconnection is possible even if the part is re-created in the catalog. Solid Edge Equipment with flavors in the Catalog: The equipment may also have its flavor deleted. After you refresh the workspace, a line and a circle appear instead of the missing graphic definition. Solid Edge or VB Equipment with flavors in the Model: The correct graphic always appears. Designed Equipment This situation should not happen. Please contact Intergraph Process, Power & Marine Support.
Possible Causes
The part in the catalog has been deleted by the Bulkload utility. The error may be the result of unsupported catalog manipulations. The error may be the result of an improper backup restore procedure.
Possible Impacts
The Definition tab of the property pages will be absent. Some commands may work incompletely. Equipment reports may be erroneous or inaccurate (if they include part attributes). Filters or style rules behavior may be unexpected (if they filter on part attributes). If the equipment has been copied to the catalog, the impact is unknown.
161
Severity
High.
Detailed Description
The equipment does not have a coordinate system. When you select the equipment, the coordinate system (yellow color) does not appear.
Possible Causes
The cause is currently unknown.
Possible Impacts
Some commands may work incompletely. Impossible to get an active coordinate system using PinPoint when selecting equipment graphically. Possible erroneous or inaccurate equipment reports. Impact on shape placement.
162
Severity
High.
Detailed Description
The port is not related to an equipment anymore.
Possible Causes
The cause is currently unknown.
Possible Impacts
Some commands may work incompletely. Equipment reports may be erroneous or inaccurate.
Severity
High.
Detailed Description
A shape has an invalid range.
Possible Cause
This problem occurs when migration asks for the range of one of the shapes that are imported from a SAT file. Historically, some SAT file imports have generated this kind of shape. The SAT file import process has now been improved to prevent creating such shapes, but the existing shapes will still log these errors.
Possible Impacts
The shapes are no longer usable. They cannot be selected or located. It is not possible to repair these shapes.
163
Invalid WCGProperties for the object that has valid weight and CG
Message
Invalid WCGProperties for the object that has valid weight and CG.
Severity
Crucial.
Detailed Description
The column WCGProperties contains invalid equipment or equipment components, although the weight and center of gravity (CG) are valid.
Possible Cause
If any one of the weight or CG values is not defined, then the WCGProperties column persists with DBL_UNDEFINED values.
Possible Impacts
If the values of the WCGProperties (wet and dry) are persisted with DBL_UNDEFINED values, then the parent system will not display the weight and CG values in the property dialog box. However, the weight and CG of its child is defined.
164
Severity
Crucial.
Detailed Description
Objects do not have the expected related objects. The EF Correlation-related functionality fails.
Possible Cause
This situation may have been caused by deleting objects selected by a filter based on the Correlation Status property. Other related objects will be in an erroneous state.
Possible Impacts
None.
Orphaned Nozzle
Message
Orphaned Nozzle.
Severity
High.
Detailed Description
The nozzle does not have any relationships.
Possible Cause
Undetermined workflow in the Place Nozzle command.
Possible Impacts
This is not a nozzle that has lost its relationships. It is an extra nozzle that may be undesirably displayed or reported by spatial filters.
165
Severity
High.
Detailed Description
The permission group of equipment children should be same as that of the parent equipment.
Possible Cause
Copying the children of design equipment to another design equipment in a different permission group. Then, the children in the design equipment do not have the same permission group as that of its parent design equipment.
Possible Impacts
This problem prevents the deletion of the equipment because you do not have permission to delete the child.
Permission Group of the shape is different from the corresponding Smart Equipment
Message
Equipment Unspecified Error 2 (Permission Group of the shape is different from the corresponding Smart Equipment).
Severity
Crucial.
Detailed Description
The permission group of a shape should be the same as the corresponding smart equipment.
Possible Cause
Copying the shapes of design equipment to another design equipment in a different permission group. Then, the shape in the design equipment does not have the same permission group as that of its parent design equipment.
166
Severity
Normal.
Detailed Description
The shape is not related to a design equipment parent anymore. This situation is unexpected.
Possible Causes
The cause is currently unknown.
Possible Impacts
Some commands may work incompletely. Equipment reports may be erroneous or inaccurate. It is impossible to retrieve equipment using filters and style rules based on systems.
167
Severity
Crucial.
Detailed Description
Smart Equipment should have a relationship with its corresponding symbol sub system.
Possible Cause
This problem is observed when a few equipment parts are added and then later, the equipment parts are removed from the catalog. The parts are in the To Do List, with messages that the part from reference data is missing. If you add the same part again, the relationship between the smart equipment and its symbol sub system is not re-created.
Possible Impacts
The placement of the equipment (compute of the symbol) fails.
Severity
Crucial.
Detailed Description
The permission group of a Smart Item should be same as the Equipment with which it is associated when the Smart Item is in the model.
Possible Cause
A possible cause could be that a repair operation on a Design Equipment created a unique Smart Item that was assigned to the current Permission Group. The Smart Item is related to Design Equipment, and the permission groups are different.
168
169
170
SECTION 11
Severity
Low.
Detailed Description
Cannot enclose void to construct a solid from the given set of face geometries (represented as standalone sheets). Applications are expected to handle the well-defined error code MODELTOPOLOGY_E_CANNOTENCLOSEVOID.
Possible Cause
The given set of face geometries is not consistent to produce a closed solid within the distance tolerance.
Possible Impacts
None if the calling code (such as Structure semantics) is properly managing returned error codes from Geometry and Topology.
171
Severity
Medium.
Detailed Description
Cannot stitch and consistently orient the given surface bodies. Calling applications are expected to handle the MODELTOPOLOGY_E_CANNOTSTITCH and MODELTOPOLOGY_E_CANNOTORIENT error codes.
Possible Cause
The input surface bodies cannot stitch and consistently orient within the distance tolerance.
Possible Impacts
None if the calling code (such as Structure semantics) is properly managing returned error codes from Geometry and Topology.
Severity
Low.
Detailed Description
Structure semantics calling the Geometry and Topology Boolean APIs should handle the well-defined HRESULT error code MODELTOPOLOGY_E_NULLBODY.
Possible Cause
In the context of Boolean APIs, a result with no topology (such as a null model body) is returned if the tool body is greater than the blank body (also known as material).
Possible Impacts
None if the calling code is handling MODELTOPOLOGY_E_NULLBODY properly.
172
Severity
Low.
Detailed Description
The given model body is self-intersecting (for example, a RAD2d collection of segments translated as a single wireframe body). Calling applications are expected to handle the MODELTOPOLOGY_E_SELFINTERSECTION error code.
Possible Cause
For example (in the case of a 3-D wireframe model body translated from RAD2d), ill-defined values for a parametric symbol can cause self-intersection between edges.
Possible Impacts
None if the calling code (such as Structure semantics) is properly managing returned error codes from Geometry and Topology.
Severity
Low.
Detailed Description
Structure semantics calling the Geometry and Topology intersection API should handle the well-defined HRESULT error code MODELTOPOLOGY_E_NOINTERSECTION.
Possible Cause
The input model geometries do not intersect.
Possible Impacts
None if the calling code is handling MODELTOPOLOGY_E_NOINTERSECTION.
173
Severity
Low.
Detailed Description
Structure semantics calling the Geometry and Topology common geometry API should handle the well- defined HRESULT error code MODELTOPOLOGY_E_NOOVERLAP.
Possible Cause
The input model geometries do not have common geometry within the distance tolerance.
Possible Impacts
None if the calling code is handling MODELTOPOLOGY_E_NOOVERLAP properly.
Severity
High.
Detailed Description
An unexpected failure occurred within the GeomOperations module of Geometry and Topology. This situation is unexpected.
Possible Cause
The cause is currently unknown.
Possible Impacts
None if the calling code (such as Structure semantics) is properly managing returned error codes from Geometry and Topology.
174
175
176
SECTION 12
Grids
This section contains Grids database integrity messages.
Severity
High.
Detailed Description
Some Planes/Cylinders on the axis of the Coordinate System are at the same position.
Possible Cause
Unknown.
Possible Impacts
Unable to copy/paste the Coordinate System. Unable to edit those Planes/Cylinders.
177
Grids
select entity.oid, namedItem.strName, entity.position from GRDSYSSPGElevationPlane as entity join XZAxisCS as cs on entity.oid = cs.oidDestination join CORENamedItem as namedItem on namedItem.oid = entity.oid where cs.oidOrigin = '{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}'; For the R-axis: select entity.oid, namedItem.strName, entity.position from GRDSYSSPGRadialPlane as entity join XRAxisCS as cs on entity.oid = cs.oidDestination join CORENamedItem as namedItem on namedItem.oid = entity.oid where cs.oidOrigin = '{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}'; For the C-axis: select entity.oid, namedItem.strName, entity.position from GRDSYSSPGRadialCylinder as entity join XCAxisCS as cs on entity.oid = cs.oidDestination join CORENamedItem as namedItem on namedItem.oid = entity.oid where cs.oidOrigin = '{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}';
Severity
Crucial for: Coordinate System: GRDSYSSPGCoordinateSystem (Object OID starting with 00046CD1). Ship Coordinate System: GRDSYSSPGShipCoordinateSystem (Object OID starting with 00046CD7). Grid Plane: GRDSYSSPGGridPlane (Object OID starting with 00046CD4). Elevation Plane: GRDSYSSPGElevationPlane (Object OID starting with 00046CD3). Radial Plane: GRDSYSSPGRadialPlane (Object OID starting with 00046CD8). Radial Cylinder: GRDSYSSPGRadialCylinder (Object OID starting with 00046CD9). Axis For Ruler: GRDSYSSPGAxisForRuler (Object OID starting with 00046CD2). Grid Arc: GRDSYSSPGGridArc (Object OID starting with 00046CDA). High for: Coordinate System: GRDSYSSPGCoordinateSystem (Object OID starting with 00046CD1). Grid Plane: GRDSYSSPGGridPlane (Object OID starting with 00046CD4). Elevation Plane: GRDSYSSPGElevationPlane (Object OID starting with 00046CD3). Radial Plane: GRDSYSSPGRadialPlane (Object OID starting with 00046CD8). Radial Cylinder: GRDSYSSPGRadialCylinder (Object OID starting with 00046CD9). Normal for: Grid Plane: GRDSYSSPGGridPlane (Object OID starting with 00046CD4). Elevation Plane: GRDSYSSPGElevationPlane (Object OID starting with 00046CD3). Radial Plane: GRDSYSSPGRadialPlane (Object OID starting with 00046CD8). Radial Cylinder: GRDSYSSPGRadialCylinder (Object OID starting with 00046CD9).
178
179
Grids
Axis should be C (5). This error has a Crucial severity. NestingLevel should be Primary (1), Secondary (2), or Tertiary (3). This error has a High severity. Angle should be 0. This error has a Normal severity. RotationAxis should be 0. This error has a Normal severity. InternalFlag should be either 0 or ShowAllGridLine (0x1). This error has a Normal severity. Axis For Ruler: Axis should be X (1), Y (2), Z (3), R (4), or C (5). This error has a Crucial severity. Grid Arc: ArcQuadrant should be pXpY (1), pXmY (2), mXmY (4), or mXpY (8). This error has a Crucial severity.
Possible Cause
Values were changed directly in the database.
Possible Impacts
For the error with Crucial severity, the object may not work properly. For the error with High severity, the object could have a local problem. For the error with Normal severity, there is no impact to the user.
Severity
Fatal for: Grid Plane: GRDSYSSPGGridPlane (Object OID starting with 00046CD4). Elevation Plane: GRDSYSSPGElevationPlane (Object OID starting with 00046CD3). Radial Plane: GRDSYSSPGRadialPlane (Object OID starting with 00046CD8). Radial Cylinder: GRDSYSSPGRadialCylinder (Object OID starting with 00046CD9). Grid Line: CORELine3d (Object OID starting with 00046CD5). Grid Line Intersection AE: COREBaseClass (Object OID starting with 00046CD6). Grid Arc: GRDSYSSPGGridArc (Object OID starting with 00046CDA). Grid Arcs Intersection AE: COREBaseClass (Object OID starting with 00046CDB). Normal for: Axis For Ruler: GRDSYSSPGAxisForRuler (Object OID starting with 00046CD2).
180
Possible Cause
Unknown.
Possible Impacts
For the errors of Fatal severity, the object will not work properly. For the errors of Normal severity, there is no impact to the user.
181
Grids
Severity
High.
Detailed Description
The Coordinate System does not have the correct vectors.
Possible Cause
The matrix stored in the database contains invalid values that result in a bad vector orientation.
Possible Impacts
Unable to use the Coordinate System.
182
SECTION 13
Severity
High.
Detailed Description
Active entity does not have a route leg object associated.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Cannot modify the support object.
Severity
High.
Detailed Description
Support active entity does not have an output support object.
183
Possible Impacts
No impact. Orphaned object remains in the database.
Severity
High.
Detailed Description
Active entity does not have a supported entity (pipe/HVAC/cableway/and so on) associated.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Modification of the resultant support object will generate an error.
Severity
High.
Detailed Description
Component without WBSProjectChild and WBSItemChild.
184
Possible Impacts
The software will not work properly in an integrated environment.
Severity
High.
Detailed Description
Connection object exists without a parent support object.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Connection object becomes orphaned.
Severity
High.
Detailed Description
There are two types of hanger connection objects: Intermediate connection objects are related to support components. External connection objects are related to route objects. The hanger connection object also has a relation to the route object.
185
Possible Cause
Some workflows in the route task may have caused the connection to lose its relation to the route object.
Possible Impacts
Hanger connections will be recreated the next time the support object is recomputed if the connections do not exist or if they do not have the required relations. This DBI script detects and repairs the hanger connections at an early stage before the support object is recomputed.
Severity
High.
Detailed Description
Duplicate relations exist between a set of two objects in the database.
Possible Cause
This problem is caused by creating the same relation between the same set of objects without verifying the existence of the relation.
Possible Impacts
None.
186
Severity
High.
Detailed Description
A support and its children are connected through the SupportHasComponents relationship. If there is more than one of these relationships, a hierarchical loop will be detected.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
The object may not display in the Workspace Explorer and graphic view, as it is not connected to the project root.
Severity
High.
Detailed Description
Support joint object becomes orphaned without a support object.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
HgrJoint object becomes orphaned.
187
Severity
High.
Detailed Description
Occurrence assembly does not have a part associated in the catalog.
Possible Cause
De-synchronization between the catalog and model. The support definition might have been deleted in the catalog.
Possible Impacts
You will not be able to select the support object and view the properties.
Severity
Normal.
Detailed Description
Hanger port was created but it is not related to a parent object.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
The hanger port becomes orphaned.
188
Severity
High.
Detailed Description
On the Assembly tab (in the Workspace Explorer), the support is an assembly child, but no object is associated with it as an assembly child.
Possible Cause
Coding or data model propagation errors in an earlier version.
Possible Impacts
The software will not be able to list the assembly child associated with a certain support.
Severity
Crucial.
Detailed Description
Support component does not have a parent support associated with it.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Support component becomes orphaned. You cannot view the Properties dialog box of the support component.
189
Severity
High.
Detailed Description
Support does not have an active entity associated, although the support is the output of the active entity.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Getting the support object properties is not possible. Modification will not be possible.
Severity
High.
Detailed Description
Support exists without a joint. Typically this will happen for the design support.
Possible Cause
Coding or data model errors in an earlier version.
190
Severity
Crucial.
Detailed Description
Support does not have any associated support component object.
Possible Cause
Coding or data model propagation errors in an earlier version.
Possible Impacts
Support does not work properly, and reports do not generate proper results.
Severity
High.
Detailed Description
A placed support is not able to find the associated support definition in the catalog.
Possible Cause
The cause may be de-synchronization between the catalog and model. The support definition might have been deleted in the catalog.
Possible Impacts
You will not be able to select the support object and view the properties.
191
Severity
High.
Detailed Description
A support exists without an associated local coordinate system.
Possible Cause
A model from a previous version was not properly migrated.
Possible Impacts
The support location for supports created with the Place Support by Structure command will not be reported.
Severity
High.
Detailed Description
Support object does not have a name.
Possible Cause
Coding or data model propagation errors in an earlier version.
Possible Impacts
Unable to modify the name of the support.
192
Severity
High.
Detailed Description
Support port object exists without a parent support object.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Support port object becomes orphaned.
Severity
High.
Detailed Description
Support port object exists without a parent support component object.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Support port object becomes orphaned.
193
Severity
Crucial.
Detailed Description
A ComponentToSupportedPort relation exists between the support and RouteOccur instead of RouteFeature
Possible Cause
Unknown.
Possible Impacts
Modification of the resultant support object will generate an error.
194
SECTION 14
Hole Management
This section contains Hole Management database integrity messages.
The Approved hole is missing a relationship to the structure part being cut
Message
The Approved hole is missing a relationship to the structure part being cut.
Severity
Crucial.
Detailed Description
To be able to place the hole on the To Do List when a planning seam or straking seam is applied to the structure, a new relationship was needed between the hole and the structure part being cut. This relationship is missing from the hole in error.
Possible Cause
The hole may have been created in an older version of the software, and the migration command failed to create the relationship.
Possible Impacts
If a planning seam or straking seam is applied to the structure being cut, the hole will not be placed on the To Do List.
195
Hole Management
Severity
Crucial.
Detailed Description
To allow a fitting placed by Hole Management to be spooled, a connection must exist between the pipe part and the fitting. The fitting for the hole in error is missing the connection to the pipe part that allows it to be spooled along with the pipe part.
Possible Cause
The hole may have been created in an older version of the software, and the migration command failed to create the connection.
Possible Impacts
If the connection does not exist, then the catalog fitting cannot be spooled with the pipe part.
Severity
Crucial.
Detailed Description
To allow a fitting placed by Hole Management to be spooled, a connection must exist between the pipe part and the fitting. The center flange of the hole in error is missing the connection to the pipe part that allows it to be spooled along with the pipe part.
196
Possible Impacts
If the connection does not exist, then the center flange cannot be spooled with the pipe part.
Severity
Crucial.
Detailed Description
The hole application property has an invalid value. This property is codelisted, and a value outside of the range of the codelist has been stored.
Possible Cause
While this situation has been seen to happen only once, it is currently unknown how this problem can occur.
Possible Impacts
The rules and smart occurrences used to generate the hole may not pick the proper settings.
197
Hole Management
Severity
Fatal.
Detailed Description
The hole cut status property has an invalid value. This property is codelisted, and a value outside of the range of the codelist has been stored.
Possible Cause
While this situation has been seen to happen only once, it is currently unknown how this problem can occur.
Possible Impacts
The hole cannot be cut. This situation may also prevent the user from opening the property pages for the hole to set a valid value.
Severity
Crucial.
Detailed Description
The hole fitting type property has an invalid value. This property is codelisted, and a value outside of the range of the codelist has been stored.
Possible Cause
While this situation has been seen to happen only once, it is currently unknown how this problem can occur.
Possible Impacts
The wrong type of fitting may be created. This situation may also prevent the user from opening the property pages for the hole to set a valid value.
198
Severity
Fatal.
Detailed Description
The hole status property has an invalid value. This property is codelisted, and a value outside of the range of the codelist has been stored.
Possible Cause
While this situation has been seen to happen only once, it is currently unknown how this problem can occur.
Possible Impacts
The hole cannot be cut. This situation may also prevent the user from opening the property pages for the hole to set a valid value.
Severity
Crucial.
Detailed Description
To support future enhancements, the hole should always have a relationship to the root system of the structure it is to cut. The hole in error has a relationship to a leaf system instead.
199
Possible Impacts
Future enhancements will fail.
Severity
Fatal.
Detailed Description
A clearance rule is used to help determine the size of the hole to be cut. The relationship to a clearance rule is missing from the hole in error.
Possible Cause
While this situation has been seen to happen only once, it is currently unknown how this problem can occur as long as clearance rules are bulk loaded into the catalog.
Possible Impacts
The geometry of the hole cannot be generated without a clearance rule. This situation will prevent any cut from being placed on the structure.
200
Hole Management
Severity
Crucial.
Detailed Description
The property to use a fitting selection rule has been set on the hole in error, and there is no relationship to a fitting selection rule.
Possible Cause
While this situation has been seen to happen only once, it is currently unknown how this problem can occur as long as fitting selection rules are bulk loaded into the catalog.
Possible Impacts
The proper fitting will not be created when the hole is cut.
Severity
High.
Detailed Description
There is a Permission Group for Hole Management objects. This object should be in the Hole Management Permission Group, but it is not.
Possible Cause
The object may have been created prior to the creation of the Hole Management Permission Group.
Possible Impacts
Unknown.
201
Severity
Crucial.
Detailed Description
To allow a fitting placed by Hole Management to be spooled, a connection must exist between the pipe part and the fitting. The pipe part is missing the connection to the fitting of the hole in error that allows the fitting to be spooled along with the pipe part.
Possible Cause
The hole may have been created in an older version of the software, and the migration command failed to create the connection.
Possible Impacts
If the connection does not exist, then the fitting cannot be spooled with the pipe part.
202
Hole Management
Severity
Fatal.
Detailed Description
A new relationship was added between the hole and the outline sketched by the user. The hole in error can no longer access the outline through the expected relationship.
Possible Cause
The hole may have been created in an older version of the software, and the migration command failed to create the new relationship.
Possible Impacts
The geometry of the hole is represented by the outline that the user has sketched. If the relationship is missing, then the hole cannot be cut.
203
Hole Management
204
SECTION 15
Interference Checking
This section contains Interference Checking database integrity messages.
Severity
High.
Detailed Description
The interference object does not have a part associated to it. The DBIntegrity report includes this message when an invalid part in the database is deleted, and Interference Checking does not remove the type of interference associated with it.
Possible Causes
The DBIntegrity report was generated while Interference Checking was running and not completed. Interference Checking could not delete the associated interference when the invalid part was deleted.
Possible Impacts
The Interference Checking reports and the list view may not show the same results. Reports may show some interferences that are not possible to find or locate in the model.
205
Interference Checking
Severity
High.
Detailed Description
The interference object is not associated with both the interfering objects. The interference is not in the To Do list.
Possible Cause
When an interfering object was deleted, the interference object associated to it was not automatically deleted.
Possible Impacts
The interference list view and reports on interferences may not show the same results. Reports may show some interferences that are not visible in the interference list view.
206
SECTION 16
Molded Forms
This section contains Molded Forms database integrity messages.
Severity
Crucial.
Detailed Description
A beam does not have a related beam system active entity (AE): Missing the GeometryToBeam relationship to BeamSystem_AE for BeamSystem.
Possible Cause
Unknown.
Possible Impacts
Unknown.
207
Molded Forms
Severity
Crucial.
Detailed Description
A BracketByPlane PlateSystem requires a ReferenceCollection, which provides links to the symbol information. The ReferenceCollection has relationships to the symbol inputs and other classes required to properly create the plate system and its geometry.
Possible Cause
Unknown.
Possible Impacts
The display of the PlateSystem may not be correct. This problem can affect other related objects.
A BracketByPlane PlateSystem does not have the necessary two points defined
Message
A BracketByPlane PlateSystem does not have the necessary two points defined.
Severity
Crucial.
Detailed Description
A BracketByPlane PlateSystem requires two points for proper placement on the identified supports.
Possible Cause
Unknown.
208
Severity
Crucial.
Detailed Description
A BracketByPlane PlateSystem requires two points for proper placement on the identified supports. In this case, there are more than two points defined.
Possible Cause
Unknown.
Possible Impacts
The geometry and display of the PlateSystem will not be correct. This problem can affect other related objects.
209
Molded Forms
Severity
Crucial.
Detailed Description
A BracketByPlane PlateSystem requires a ReferenceCollection, which provides links to the symbol information. In this case, there are too many relationships, so the right one may not always be used. The ReferenceCollection has relationships to the symbol inputs and other classes required to properly create the plate system and its geometry.
Possible Cause
Unknown.
Possible Impacts
The display of the PlateSystem may not be correct. This problem can affect other related objects.
Severity
Crucial.
Detailed Description
A BracketByPlane PlateSystem requires two points for proper placement on the identified supports. These points must also be inputs to the symbol. The relationship to the symbol is missing.
210
Possible Impacts
The geometry and display of the PlateSystem will not be correct. This problem can affect other related objects.
Severity
Crucial.
Detailed Description
A connection has less than two ports: Missing one or more ConnHasPorts relationship(s) to StructPort for StructPhysicalConnection, AssemblyConnection, StructConnection. In other words, the connection does not have two ports.
Possible Causes
Unknown.
Possible Impacts
Unknown.
211
Molded Forms
Severity
Crucial.
Detailed Description
A Connection has more than two ports associated to it. There are more than the required two ConnHasPorts relationship(s) to StructPort for StructPhysicalConnection, AssemblyConnection, and StructConnection. Cases have been found where one of the ports has two identical relationships to the connection.
Possible Causes
Unknown.
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
A create plate part active entity (AE) does not have a related plane: Missing the StructGeometryHasPorts relationship to IJStructGeometry (various) for StructPort_AE.
Possible Cause
Unknown.
212
Severity
Crucial.
Detailed Description
A create plate part active entity (AE) does not have any related trim boundaries: Missing the TrimBoundaries relationship to various for CreatePlatePart_AE not related to SmartPlates. The SmartPlates may have "natural" boundaries.
Possible Cause
Unknown.
Possible Impacts
None.
213
Molded Forms
Severity
High.
Detailed Description
A design split or a planning split is missing its operand. The operand is a required input and is typically a Plate or Profile System.
Possible Causes
Unknown.
Possible Impacts
A loose end exists in the model.
A Design- or Planning-split operation with a seam has less than two results
Message
A Design- or Planning-split operation with a seam has less than two results.
Severity
Fatal.
Detailed Description
Design-split operations or planning-split operations that have seams (not connections or seam points) as inputs and that are not classified as penetrations per their connections require more than one result.
214
Possible Impacts
Improper part development.
A Design- or Planning-split operation without a seam does not have one result
Message
A Design- or Planning-split operation without a seam does not have one result.
Severity
Fatal.
Detailed Description
A Design split operation or Planning split operation does not have one seam, indicating that there is no split to be performed. In such cases, the split operation (AE) should have one and only one geometry as a result.
Possible Causes
Unknown.
Possible Impacts
Improper part development.
215
Molded Forms
Severity
Normal.
Detailed Description
An orphaned Flanged Plate Active Entity exists without a relationship to a plate being flanged.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
Crucial.
Detailed Description
A Plate (Bracket) associated to a Flanged Plate Active Entity does not have an association to a symbol defining the flange.
Possible Cause
Unknown.
Possible Impacts
The flange will not be processed, and errors may occur.
216
Molded Forms
3. If the problem still exists and the plate is as expected (needed), report the situation to SmartMarine 3D Support. Revisions may be necessary.
Severity
Crucial.
Detailed Description
A Plate (Bracket) associated to a Flanged Plate Active Entity and a symbol is missing the relationship to the start or end points.
Possible Cause
Possible causes include: Symbol inputs not correctly defined. Transaction aborted during definition of the Flanged Plate. Unknown.
Possible Impacts
The flange will not be processed, and errors may occur.
217
Molded Forms
Severity
Crucial.
Detailed Description
A Plate (Bracket) associated to a Flanged Plate Active Entity does not have its output properly updated.
Possible Cause
Possible causes include: Symbol was not defined properly. Compute did not complete. Unknown.
Possible Impacts
The flange will not be processed, and errors may occur.
218
Molded Forms
Severity
Crucial.
Detailed Description
A generate plate part active entity (AE) does not have a related plate system: Missing the GeneratePlatePart_OPRND relationship to PlateSystem for GeneratePlatePart_AE.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
A landing curve point does not have a related point on surface by the two coordinates active entity (AE): Missing the PointOnSurface relationship to PointOnSurfByTwoCoords_AE for CLandCrvPoint.
Possible Cause
Unknown.
219
Severity
Fatal.
Detailed Description
Points defining the landing curve are missing for the Profile or Seam by Table: Missing the DefPoints relationship to CLandCrvPoint for LandCrvTable_AE.
Possible Cause
Unknown.
Possible Impacts
Unknown.
220
Molded Forms
Severity
Crucial.
Detailed Description
A landing curve active entity (AE) does not have the Parent0 relationship. Possible situations: Missing the LandCrvIntParent0 relationship to IJSurfaceBody (various) for LandCrvIntersect_AE. Missing LandCrvOffParent0 relationship to IJSurfaceBody (various) for LandCrvOffset_AE. Missing LandCrvProjParent0 relationship to IJSurfaceBody (various) for LandCrvProject_AE.
Possible Causes
Unknown.
Possible Impacts
Unknown.
Severity
Crucial.
Detailed Description
A landing curve active entity (AE) does not have the Parent1 relationship: Missing the LandCrvIntParent1 relationship to IJSurfaceBody (various) for LandCrvIntersect_AE
221
Molded Forms
Missing LandCrvOffParent1 relationship to IJSurfaceBody (various) for LandCrvOffset_AE.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
Crucial.
Detailed Description
A landing curve active entity (AE) does not have the Parent2 relationship: Missing the LandCrvProjParent2 relationship to IJSurfaceBody (various) for LandCrvProject_AE.
Possible Cause
Unknown.
Possible Impacts
Unknown.
222
Molded Forms
Severity
Fatal.
Detailed Description
There is no definition of the base curve: Missing the LandCrvBase relationship to WireBody2 for LandCrvIntersect_AE, LandCrvOffset_AE, LandCrvProject_AE, LandCrvTable_AE, LandCrvER_AE.
Possible Cause
Unknown.
Possible Impacts
The user cannot manipulate the object itself or other objects related to it.
Severity
Crucial.
Detailed Description
A landing curve active entity (AE) does not have a related geometry: Missing the resultant generated geometry (GeometryGeneration_RSLT1 relationship) to LandCurve, ProfileLandCrv, or ProfilePartPath for LandCrvIntersect_AE, LandCrvOffset_AE, LandCrvProject_AE, LandCrvTable_AE, LandCrvER_AE
223
Possible Impacts
None.
Severity
Normal.
Detailed Description
The object has not been given a name.
Possible Cause
A Naming Rule may not have been identified for the parent system or is not available. A user may have overridden the Naming Rule and then removed the name.
Possible Impacts
The object without a name may be difficult to work with.
224
Molded Forms
Severity
Fatal.
Detailed Description
The Plate bound operation (OID begins with 0010A1F0) does not have an operand.
Possible Cause
Unknown.
Possible Impacts
The user cannot manipulate the object itself or other objects related to it.
Severity
Crucial.
Detailed Description
A plate bound operation (OID begins with 0010A1F0) exists with no related result.
Possible Cause
Unknown.
225
Severity
Crucial.
Detailed Description
A plate bound to another plate is missing the connection to the bounding object. The plate system in the database will likely fail in detailing due to Molded Forms modeling errors.
226
Another cause of this message is a plate system having another plate system in its boundary list that is not actually used as a boundary. This situation can only occur when a sketched boundary does not cross all necessary boundaries, and as a result, some boundaries are not used. TR56504 was filed for this condition.
Possible Impacts
1. If the bounded plate system does not have a connection to the bounding object, the part cannot be successfully detailed. 2. Additional plate systems may have been added to the boundary list.
227
Molded Forms
Severity
Crucial.
Detailed Description
A Plate could possibly be missing a sketched boundary. The check finds bounded plates on the To Do List and reports them if they do not have a relationship to a sketch. The plate may or may not require a sketch. The check was created in support of TR 104211. If necessary, you can verify the problem of a bounded plate by determining if this condition existed in a backup database, preferably one that was created prior to the last date modified of the plate or its PlateBound_AE (operation).
Possible Cause
Unknown. It is thought that ungrouping and regrouping may be the cause.
Possible Impacts
The plate will not update correctly.
228
Molded Forms
Severity
Crucial.
Detailed Description
A Plate cutout operation exists with no related operator: Missing the PlateCutout_OPER1 relationship to the Sketch (reference proxy symbol) information for PlateCutout_AE. To facilitate TR 104211, the current DB Integrity check has been changed to post the Plate cutout operation (PlateCutout_AE) with an action of DELETE. In order to make it more convenient for finding and posting such cases, this particular query has been moved to the CheckAEWithSketches.sql file.
Possible Cause
Unknown.
Possible Impacts
When the sketch information for an opening on a Plate is missing, it is no longer possible to update parts on the plate system or place new openings.
Severity
Crucial.
Detailed Description
Missing the GeometryGeneration_RSLT1 relationship to LandCurve, ProfileLandCrv, or ProfilePartPath for LandCrvIntersect_AE, LandCrvOffset_AE, LandCrvProject_AE, LandCrvTable_AE.
229
Possible Impacts
The weight and center of gravity may not be calculated and will be invalid because the report data does not exist.
Severity
Crucial.
Detailed Description
A Plate system exists with no relationship to a planning-split active entity nor to a design-split active entity: Missing StructOperation_OPRND relationship to PlatePlanningSplit_AE for leaf PlateSystem and missing a relationship to the CPlateDesignSplit_AE.
Possible Cause
Unknown.
Possible Impacts
Unknown.
230
Molded Forms
Severity
Crucial.
Detailed Description
A plate geometry does not have a related Planning Split active entity (AE): Missing the StructOperation_RSLT1 relationship to PlatePlanningSplit_AE for the light PlateGeometry of the PlatePart. Or to GeneratePlatePart_AE for the new immediate_thickening code.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
High.
Detailed Description
The Plate geometry (OID begins with 0010A1F3) does not have a relationship to an Entity (Plate System, ProfileSystem, PlatePart) or as an input to an appropriate Active Entity (AE).
231
Possible Impacts
Based on recent findings, there should be no impact to the user.
Severity
Crucial.
Detailed Description
A plate part geometry for a StandAlone PlatePart does not have a related create plate part active entity (AE): Missing the GeometryGeneration_RSLT1 relationship to CreatePlatePart_AE for PlatePartGeometry on standalone plate.
Possible Cause
Unknown.
Possible Impacts
The user cannot manipulate the object itself or other objects related to it. The plate part cannot be displayed graphically. The weight and center of gravity will be invalid.
232
Molded Forms
Severity
High.
Detailed Description
A plate system does not have a related molded specification: Missing the SystemHasSpec relationship to SiteProxy (IJDMoldedSpec) for root plate systems.
Possible Causes
This error occurs under two conditions. Condition 1 (Refer to What You Should Do, Action 1): The first condition occurs when plate systems are assigned as children to other plate systems, and the plate system hierarchy is more than three layers deep. The following graphic shows a plate system hierarchy with too many levels. Plate systems inherit properties like Molded Specification, Material, and Thickness from their parents. The data integrity checks only go up two levels looking for a root plate system to obtain the Thickness property. Thus, if the plate system is deeper than two levels below the root, no thickness property is found by the integrity check.
Condition 2 (Refer to Refer to What You Should Do, Action 2): The second condition occurs when a plate system is created as the child of another plate system and later moved to a different location in the hierarchy where it becomes a root plate system. These plate systems will not have a Molded Specification or any material properties assigned.
Possible Impacts
Thickening and display of light parts will fail. Referencing to the far side will not be accurate. Placing equipment may be done at the wrong location.
233
Molded Forms
The weight and center of gravity may not be calculated and will be invalid.
Severity
Crucial.
Detailed Description
A Plate System exists with less than three or more than five shared attributes.
Possible Cause
Unknown.
Possible Impacts
None.
234
Molded Forms
Severity
High.
Detailed Description
A point found on the relationship used for defining a BracketByPlane PlateSystem is not related to a PlateSystem. In this case, the point is related to other objects; therefore, no action is required.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
Normal.
Detailed Description
A point found on the relationship used for defining a BracketByPlane PlateSystem is not related to a PlateSystem. In this case, the point is not related to any other objects other than the one that was supposed to be a PlateSystem. Because the point is not providing any expected information, you should delete the point.
Possible Cause
Unknown.
235
Severity
Fatal.
Detailed Description
A point on surface by two coordinates active entity (AE) does not have a related base plate: Missing the RefSurface relationship to PlateSystem for PointOnSurfByTwoCoords_AE.
Possible Cause
Unknown.
Possible Impacts
Unknown.
236
Molded Forms
Severity
Crucial.
Detailed Description
A profile does not have a related child connection: Missing the SystemHierarchy relationship to a StructConnection for root ProfileSystem, root EdgeReinforcementSystem. This situation verifies that a connection is being made for stiffening profile systems and edge reinforcement with their stiffened objects.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
Crucial.
Detailed Description
Missing the ReportData relationship to ProfilePartReportData for StandAloneStiffenerPart and un-split (EdgeReinforcementProfilePart, StiffenerPart, BeamPart). "Un-split" in this case means it is STRUCT_ACTIVATED.
Possible Cause
Copying a system before Version 4.
237
Severity
Fatal.
Detailed Description
A profile split active entity (AE) does not have a related profile system: Missing the StructOperation_OPRND relationship to IJStructGeometry (ProfileSystem, EdgeReinforcementSystem and BeamSystem) for ProfileDesignSplit_AE.
Possible Cause
Unknown.
Possible Impacts
The user cannot manipulate the object itself or other objects related to it.
238
Molded Forms
Severity
Crucial.
Detailed Description
A Profile system exists with no related planning split and/or light part geometry. The Profile System should be an input to the PlanningSplit AE. The PlanningSplit AE should have a light part geometry as output.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
A ProfilePartCreation does not have a related base plate: Missing the BasePlateSurface relationship to (PlateSystem, StandAlonePlatePart) for ProfilePartCreation.
239
Possible Impacts
The user cannot manipulate the object itself or other objects related to it.
Severity
Fatal.
Detailed Description
A profile part creation does not have a related profile part: Missing the SDInputGeometry relationship to (EdgeReinforcementProfilePart, StandAloneStiffenerPart) for ProfilePartCreation.
Possible Cause
Unknown.
Possible Impacts
The user cannot manipulate the object itself or other objects related to it.
240
Molded Forms
Severity
Crucial.
Detailed Description
A profile part generation active entity (AE) does not have a related plate system. There are two relationships between the stiffener part and the plate system information. The PlateSubSystems_OPER relationship to Plate Parts is used to track when the thickness of any stiffened plate parts has changed so that the profile position can be re- evaluated. The StiffenedPlateGeometry_OPER relationship to the plate system geometries is used (after making the planning split) to track when the outlines of the stiffened parts have changed so that the parts cross can be re-evaluated. Both of these relationships are important for keeping the profile part in the correct location as the plate model is changed. In other words, these relationships are required to make sure a stiffener part location responds properly when the thickness of the stiffened parts is changed. This error has a defined automatic action, which is to recompute the affected stiffener part. This will re- create the correct relationships and update the position of the stiffener to account for plate thickness. This message only applies to stiffeners. It should not appear for a beam.
Possible Causes
This problem could be an indication that part of the migration from Version 6.1 to Version 7 was not performed or was unsuccessful. Version 7 introduced the new relationship StiffenedPlateGeometry_OPER and changed the type of object connected through PlateSubSystems_OPER. There are no other known causes for this problem.
Possible Impacts
The primary impact of this problem is that the stiffener may not respond correctly if the thickness of the stiffened plate is changed and the stiffener is on the thickness side of the plate.
241
Molded Forms
5. Re-run the Check Database Integrity custom command and the DBIntegrity report. 6. If the object is still posted, contact SmartMarine 3D Support.
Severity
Crucial.
Detailed Description
The ProfilePart Generation requires a light part geometry as input. The PlateGeometry is actually the representation of light profile geometry: Missing StructOperation_OPRND relationship to PlateGeometry for ProfilePartGeneration_AE.
Possible Cause
Unknown.
Possible Impacts
Unknown.
242
Molded Forms
Severity
Crucial.
Detailed Description
A profile part generation active entity (AE) does not have a related profile system: Missing the PartGeneration_OPER relationship to (ProfileSystem, BeamSystem, ProfileEdgeReinforcement) for ProfilePartGeneration_AE.
Possible Causes
Unknown.
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
ProfilePartGeometry does not have a related ActiveEntity: Missing StructGeometryHasPorts relationship to IJStructGeometry (various) for StructPort_AE.
Possible Cause
Unknown.
243
Severity
Crucial.
Detailed Description
A profile system does not have a related plate: Missing the PlateAttributesForProfile relationship to Plate for ProfileSystemAE on root profiles. The test for this situation looks at ProfileSystemAE and verifies that the case is only reported on ProfileSystems and not Beams, because Beams do not support PlateAttributesForProfile.
Possible Cause
Unknown.
Possible Impacts
Unknown.
244
Molded Forms
Severity
Crucial.
Detailed Description
A profile system exists with a connection on its end port that is split.
Possible Cause
A profile bounded by a plate that is split at the same location as the end port of the profile.
Possible Impacts
None.
Severity
Crucial.
Detailed Description
A profile system exists with less than three or more than six shared attributes.
Possible Cause
Unknown.
Possible Impacts
None.
245
Severity
Crucial.
Detailed Description
Case 1: Profile System A profile system active entity (AE) does not have a related profile system region. Case 2: Beam A profile system active entity (AE) does not have a related BeamSystemAxis.
Possible Cause
Unknown.
Possible Impacts
Unknown.
246
Molded Forms
Severity
Crucial.
Detailed Description
A Reference curve is not associated to a parent Plate System: Missing SystemHierarchy relationship to PlateSystem for RefCurveOnSurface.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
High.
Detailed Description
A ReferenceCollection, which typically provides links to the symbol information for a BracketByPlane PlateSystem, is not related to a PlateSystem. In this case, the ReferenceCollection appears to have relationships to other objects. and therefore. you should not delete the ReferenceCollection at this time.
Possible Cause
Unknown.
247
Severity
Normal.
Detailed Description
A ReferenceCollection, which typically provides links to the symbol information for a BracketByPlane PlateSystem, is not related to a PlateSystem. In this case, the ReferenceCollection is not related to any other objects other than the one that was supposed to be a PlateSystem. Because the point is not providing any expected information, you should delete the point.
Possible Cause
Unknown.
Possible Impacts
Unknown.
248
Molded Forms
Severity
Fatal.
Detailed Description
A SeamPoint active entity does not have a related seam point geometry: Missing GeometryGeneration_RSLT1 relationship to SeamPointGeometry for SeamPointIntersect_AE, SeamPointOffset_AE.
Possible Cause
Unknown.
Possible Impacts
The object will not display. A split will not work properly due to the Seams missing geometry.
Severity
Fatal.
Detailed Description
A seam point does not have a related seam point geometry: Missing the StructToGeometry relationship to SeamPointGeometry for SeamPoint.
Possible Cause
Unknown.
249
Severity
Fatal.
Detailed Description
A seam point active entity (AE) does not have a related profile system. Possible situations: Missing the SeamPoint_Int_Profile relationship to (ProfileSystem, EdgeReinforcementSystem or BeamSystem) for SeamPointIntersect_AE. Missing the SeamPointOffsetProfile relationship to (ProfileSystem, EdgeReinforcementSystem or BeamSystem) for SeamPointOffset_AE.
Possible Causes
Unknown.
Possible Impacts
The user cannot manipulate the object itself or other objects related to it.
250
Molded Forms
Severity
Fatal.
Detailed Description
A seam point active entity (AE) does not have a related surface. Possible situations: Missing the SeamPoint_Int_Surface relationship to various for SeamPointIntersect_AE. Missing the SeamPointOffsetSource relationship to various for SeamPointOffset_AE.
Possible Causes
Unknown.
Possible Impacts
The user cannot manipulate the object itself or other objects related to it.
Severity
Crucial.
Detailed Description
A seam point offset active entity (AE) does not have a related landing offset: Missing the SeamPointOffsetValue relationship to LandingOffset for SeamPointOffset_AE.
Possible Cause
Unknown.
Possible Impacts
Unknown.
251
Severity
High.
Detailed Description
Straking split requested with no straking seam identified: Missing StructSplit_OPER1 relationship to Seam or SeamPoint for PlateStrakingSplit_AE, ProfileDesignSplit_AE or ProfileStrakingSplit_AE. Testing for this situation is not required for other types of splits because other types of objects will be used in the near future.
Possible Cause
Unknown.
Possible Impacts
Unknown.
252
Molded Forms
Severity
Crucial.
Detailed Description
A stiffener part exists that is related to more than one StructPortAE (active entity).
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
High.
Detailed Description
A StructPort exists without a related StructPortAE. You should delete the StructPort in the model.
Possible Cause
Unknown.
Possible Impacts
Unknown.
253
Molded Forms
2. Supply all information possible that may have led to this situation, and submit this information along with the backup to SmartMarine 3D Support. 3. Delete the StructPort object using one of the following methods: Select the object in the Workspace Explorer, and delete it. Run the Clean Database custom command to delete the object.
Severity
Fatal.
Detailed Description
A StructPort exists without a related system.
Possible Cause
Unknown.
Possible Impacts
The user cannot manipulate the object itself or other objects related to it.
254
Molded Forms
Severity
Crucial.
Detailed Description
A structural port active entity (AE) exists without having related geometry: Missing the StructGeometryHasPorts relationship to IJStructGeometry (various) for StructPort_AE.
Possible Cause
Unknown.
Possible Impacts
Cases found were for CollarParts, PlateParts and StiffenerParts. In the cases examined, another StructPort_AE was available and properly related to Geometry, Ports, and Parts. Therefore, it is recommended to delete or remove the StructPort_AE that is in error. It is possible that the bad StructPort_AE is being returned to code that is attempting to use it, since related items were also found on the To Do List, for example, unnamed collar parts and MfgParts.
255
Molded Forms
Severity
Normal.
Detailed Description
A Structural Connection exists that is not in the SystemHierarchy: Missing SystemHierarchy relationship for Struct Connection, AssemblyConnection, StructPhysicalConnection.
Possible Cause
The objects associated with this message are all connections that were left behind when the connection's parent plate system was deleted. The database integrity scripts have been updated to delete these connections when they are found.
Possible Impacts
None.
256
Molded Forms
Severity
Crucial.
Detailed Description
A system does not have a related child part. For a plate system: Missing the SystemHierarchy relationship to a PlatePart for leaf PlateSystem and the PlateSystem is not related to CPlateDesignSplit_AE Active Entity. In some instances, the plate part existed, but was disassociated from the Plate System in the SystemHierarchy. See the previous bullet point: For a plate system. For plates, a check is made on whether the part is in the graphics map. If not, it is posted as PlateSystem has no PlatePart via GraphicsMap (on page 295). This check has been commented out because it adds significant time (minutes and possibly hours) when running the Check Database Integrity command. If this check is required, it can be uncommented out in the ShipStructureRelationsCheck.sql file. For a profile system: Missing SystemHierarchy relationship to StiffenerPart for leaf ProfileSystem (that is, the ProfileSystem is not related to CProfileDesignSplit_AE). For an edge reinforcement system: Missing SystemHierarchy relationship to EdgeReinforcementProfilePart for leaf EdgeReinforcementSystem (that is, EdgeReinforcementSystem not related to CProfileDesignSplit_AE). For a beam system: Missing the SystemHierarchy relationship to BeamPart for leaf BeamSystem (that is, the BeamSystem not related to CProfileDesignSplit_AE). For an edge reinforcement profile part: Missing the SystemHierarchy relationship to EdgeReinforcementSystem for generated EdgeReinforcementProfilePart.
Possible Causes
Unknown. In some cases (for Plate Systems), the Plate Part existed and needed to be reassigned as a child of the System.
Possible Impacts
Unknown.
257
Molded Forms
1. Find the part in the DBIntegrity report that does not have the proper parent system. You can open the model, and in the Molded Forms task, attempt to find the part. It may be up one level in the hierarchy. 2. If the part is found, go to the Systems and Specifications task, and reassign the part to the appropriate parent system. 3. Re-run the Check Database Integrity command and the DBIntegrity report. 4. If the object is still posted, contact SmartMarine 3D Support. For other cases: 1. Open the model. 2. In the Molded Forms task, select the object and modify it, if necessary. Or, select the object and perform a re-compute to update it. 3. Re-run the Check Database Integrity command and the DBIntegrity report. 4. If the object is still posted, contact SmartMarine 3D Support.
Severity
Normal.
Detailed Description
There is an orphaned point in the database.
Possible Cause
The code at one time did not properly delete unused alternative points for the ProfileByTable command.
Possible Impacts
None.
258
Molded Forms
Severity
Fatal.
Detailed Description
The PlateDesignSplit active entity (AE) does not have a related plate as input (operand).
Possible Cause
Unknown.
Possible Impacts
The user cannot manipulate the object or objects in relation to the active entity.
Severity
High.
Detailed Description
Missing the StructOperation_OPRND relationship to PlateGeometry for GeneratePlatePart_AE, PlateCutout_AE.
Possible Cause
Unknown.
Possible Impacts
Unknown.
259
Severity
Fatal.
Detailed Description
An active entity exists without a related result: Missing the StructOperation_RSLT1 relationship to PlateGeometry PlatePlanningSplit_AE, ProfilePlanningSplit_AE, PlateDesignSplit_AE, PlateCutout_AE.
Possible Cause
An example of this problem is when a ProfilePlanningSplit_AE does not have a result representing the light EdgeReinforcementProfilePart when the ERSystem is on a closed contour.
Possible Impacts
The user cannot properly manipulate the object itself or other objects related to it.
260
Molded Forms
Severity
Fatal.
Detailed Description
An active entity exists without a related result: Missing the StructOperation_RSLT1 relationship to PlateGeometry PlatePlanningSplit_AE, ProfilePlanningSplit_AE, PlateDesignSplit_AE, PlateCutout_AE. The active entity is also missing its related (input) operand.
Possible Cause
Unknown.
Possible Impacts
The user cannot manipulate the object itself or other objects related to it.
Severity
Crucial.
Detailed Description
An EdgeReinforcement does not have a related LandCrvER_AE: Missing ERAttributes relationship to LandCrvER_AE for unsplit EdgeReinforcementSystem and standalone EdgeReinforcementProfilePart.
261
Possible Impacts
None.
Severity
Crucial.
Detailed Description
Shared attributes, which are based on the IJShellMoldedConventions interface, have been created for or shared with objects that are not shell plate types.
Possible Cause
The underlying cause of this error is that shared attributes were created for the IJShellMoldedConventions interface on non-shell plates. The software placed the interface GUID in the CoreBaseClass, CoreRelationOrigin, and StructSharedBag tables. To correct the problem, the interface GUID must be deleted from those tables. This problem was identified by TR-125621: DB Integrity shows plate systems w/o molded conventions.
Possible Impacts
None.
262
Molded Forms
Severity
Fatal (for Seams). Crucial (for Profiles).
Detailed Description
An object does not have a related landing curve: Missing StructToGeometry relationship to LandCurve for Seam, RefCurveOnSurface Missing StructOperation_RSLT1 relationship to various (ProfileLandCrv and BeamLandingCurve) -- for ProfileDesignSplit_AE
Possible Cause
Unknown.
Possible Impacts
The user cannot manipulate the object itself or other objects related to it.
Severity
Crucial.
Detailed Description
An object does not have a related material: Missing SystemHasMaterial relationship to SiteProxy (IJDMaterial) for Root plate systems, root beam system, standalone beam part, CollarPart, Standalone EdgeReinforcementProfilePart, StandAloneStiffenerPart.
Possible Cause
This error occurs under two conditions.
263
Molded Forms
Condition 1 (Refer to What You Should Do, Action 1): The first condition occurs when plate systems are assigned as children to other plate systems, and the plate system hierarchy is more than three layers deep. The following graphic shows a plate system hierarchy with too many levels. Plate systems inherit properties like Molded Specification, Material, and Thickness from their parents. The data integrity checks only go up two levels looking for a root plate system to obtain the Thickness property. Thus, if the plate system is deeper than two levels below the root, no thickness property is found by the integrity check.
Condition 2 (Refer to What You Should Do, Action 2): The second condition occurs is when a plate system is created as the child of another plate system and later moved to a different location in the hierarchy where it becomes a root plate system. These plate systems will not have a Molded Specification or any Material properties assigned.
Possible Impacts
Thickening and display of light parts will fail. Referencing to the far side will not be accurate. Placing equipment may be done at the wrong location. The weight and center of gravity may not be calculated and will be invalid.
264
Molded Forms
4. If the object is still posted, contact SmartMarine 3D Support.
Severity
Fatal.
Detailed Description
An object does not have a related (plate) geometry: Missing the StructToGeometry relationship to plate geometry for the plate system.
Possible Cause
Unknown. The object should be posted on the To Do List.
Possible Impacts
If the object is not available in the Workspace Explorer hierarchy, it cannot be manipulated.
Severity
Fatal.
Detailed Description
An object does not have a related (plate) geometry: Missing the StructToGeometry relationship to plate geometry for the plate system and light part (Plate Part, StiffenerPart, Beam Part, and EdgeReinforcementProfilePart). The object is also missing its parent system. The object should be posted on the To Do List.
265
Possible Impacts
If the object is not available in the Workspace Explorer, it cannot be manipulated.
Severity
High.
Detailed Description
An object does not have a related profile symbol: Missing ProfileSymbol relationship to Symbol for ProfileSystemAE for root profilesystems, standalone BeamPart, standalone EdgeReinforcementProfilePart, Standalone StiffenerPart.
Possible Causes
Cross sections are not loaded into the catalog. Symbols are not compiled or registered on the computer. Symbols were not loaded in catalog. Symbol was deleted.
Possible Impacts
No display. The weight and center of gravity may not be calculated and will be invalid.
266
Molded Forms
Severity
High.
Detailed Description
A Plate Part's geometry or a Profile Part's last geometry does not have a relationship to a StructPort active entity (AE), which allows it to have connections or be selected.
Possible Cause
Unknown.
Possible Impacts
The user cannot make connections or select the object for referencing.
Severity
Normal.
Detailed Description
An object exists that is not in the system hierarchy: Missing SystemHierarchy relationship for Plate System, Profile System, Struct Connection, Seam, SeamPoint, Beam System, BeamPart, SmartPlate, CollarPart, EdgeReinforcementProfilePart, StandAloneStiffenerPart, StructFeature, SketchFeature, PlatePart, StiffenerPart.
Possible Cause
Unknown.
Possible Impacts
None.
267
Severity
Crucial.
Detailed Description
An opening occurrence does not have a related plate cutout active entity (AE): Missing the StructOperation_RSLTocc relationship to PlateCutout_AE for StructOpeningOccurrence.
Possible Cause
Unknown.
Possible Impacts
Unknown.
268
Molded Forms
Severity
Crucial.
Detailed Description
An opening occurrence has relationships that point to different struct geometry. In other words, an opening occurrence has paths that point to different struct geometry. For example, the plate geometry found at the end of OpeningOcc operation should match the plate geometry found at the end of StructPortResult.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
Normal.
Detailed Description
A temporary ProfileCopyOrder relationship was left behind in the database. This relationship is only required during an actual copy of a Profile. Therefore, it should be removed from the database.
Possible Cause
This situation usually happens when a profile copy has failed.
269
Severity
High.
Detailed Description
There is a beam system that does not have the beam axis rule type.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
High.
Detailed Description
A beam system does not have an orientation defined.
Possible Cause
Unknown.
270
Severity
High.
Detailed Description
A beam orientation does not have the Flip U defined.
Possible Cause
Unknown.
Possible Impacts
Unknown.
271
Molded Forms
Severity
High.
Detailed Description
A beam orientation does not have the Flip V defined.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
Crucial.
Detailed Description
A BracketByPlane PlateSystem must be an input to the symbol's ReferenceCollection. The symbol needs information from the PlateSystem. This information is passed to the symbol via the StructSymbolInput2 relationship to the symbol's ReferenceCollection.
Possible Cause
Unknown.
272
Severity
Crucial.
Detailed Description
A BracketByPlane PlateSystem's ReferenceCollection has no symbol inputs, which is the collection's primary use.
Possible Cause
Unknown.
Possible Impacts
The geometry and display of the PlateSystem will not be correct. This problem can affect other related objects.
273
Molded Forms
Severity
Crucial.
Detailed Description
A BracketByPlane PlateSystem's ReferenceCollection is not related to a ReferenceCollection for the symbol. The ReferenceCollection's primary purpose is to provide symbol information about a PlateSystem.
Possible Cause
Unknown.
Possible Impacts
The geometry and display of the PlateSystem will not be correct. This problem can affect other related objects.
Severity
Crucial.
Detailed Description
A BracketByPlane PlateSystem's symbol must be of type BracketByPlane. In this case, the symbol is not defined as a BracketByPlane symbol.
Possible Cause
Unknown.
274
Severity
Crucial.
Detailed Description
A BracketByPlane PlateSystem's PlaneByOffset PlateGeometry must be an input to the symbol's ReferenceCollection. The symbol needs information from this geometry.
Possible Cause
Unknown.
Possible Impacts
The geometry and display of the PlateSystem will not be correct. This problem can affect other related objects.
275
Molded Forms
Severity
Crucial.
Detailed Description
Missing ProfileSystemSection relationship to SiteProxy for ProfileSystemAE for root profilesystems, standalone BeamPart, standalone EdgeReinforcementProfilePart, Standalone StiffenerPart. Uses the XprofileSystemSection view.
Possible Causes
Cross sections were not loaded into the catalog. Symbols are not compiled or registered on the machine. Symbols were not loaded in the catalog. Symbol was deleted.
Possible Impacts
The object will not display. The weight and center of gravity will be invalid.
276
Molded Forms
Design- or Planning-split operation without a seam does not have one result
Message
Design- or Planning-split operation without a seam does not have one result.
Severity
Fatal.
Detailed Description
A design-split operation or planning-split operation does not have one seam, indicating that there is no split to be performed. In such cases, the split operation (AE) should have one and only one geometry as a result.
Possible Cause
Unknown.
Possible Impacts
The object cannot be split.
Severity
High.
Detailed Description
A duplicate PlateBound_OPER3 relationship exists between a PlateBound Active Entity and an input object to that active entity. The PlateBound_OPER3 relationship is used exclusively for leaf profile systems. This relationship should contain all of the leaf profile systems associated with a root profile system on the PlateBound_OPER2 relationship.
277
Possible Impacts
Unknown. But there is a potential for problems.
Severity
Crucial.
Detailed Description
A duplicate ShpStrDesignHierarchy relationship exists between a parent and child. This relationship is very important and is used in the System view of the Workspace Explorer. The relationship can be between a parent leaf plate system and a child plate part.
Possible Cause
Unknown. This problem was found on active entities for brackets.
Possible Impacts
Unknown. It is possible that the software will behave in a strange way in this situation. So this problem must be corrected.
278
Molded Forms
6. If the object is still posted, contact SmartMarine 3D Support.
Severity
Crucial.
Detailed Description
The Edge Reinforcement properties such as offset and position were not set properly on the Edge Reinforcement root system.
Possible Cause
Unknown.
Possible Impacts
Plates may not be properly updated.
Severity
Crucial
Detailed Description
Extra group monitors exist For a single group criterion, more than one group monitor was created for it. Orphaned group monitors exist A group monitor was created, but it is not related to any part. If duplicated group monitors exist, one of them will be posted to be repaired. If orphaned group monitors exist and no duplicated group monitor exists, one of orphaned group monitors will be posted to minimize the entries in the DB.
Possible Cause
Unknown
279
Hull Plate System does not have Shell Molded Conventions defined
Message
Hull Plate System does not have Shell Molded Conventions defined.
Severity
Crucial.
Detailed Description
The shell molded conventions are not specified for a plate system of type Hull.
Possible Cause
Unknown.
Possible Impacts
Plates and stiffeners might fail during processing. This situation can affect stiffener orientation and properties controlled by the default values for molded conventions.
280
Molded Forms
Severity
Fatal.
Detailed Description
The naming of symbol information used to create the Linear Extruded Plate must be consistent. For example, the RelationshipName of the First ProxyOwner needs to be the same as the RelationshipName for the StructContour in the FromOutputColltoOutputs.
Possible Cause
Unknown.
Possible Impacts
The user cannot manipulate the objects or objects related to it.
Severity
Crucial.
Detailed Description
There is an imported plate system with an invalid geometry file name.
Possible Cause
Unknown.
281
Severity
Normal.
Detailed Description
The test for this database integrity problem checks for multiple StructHierarchyNamingAEs related to a Structural object (for example, a plate) via the StructNamingHierarchyParent relationship. In the 04.01.08 build, Root PlateSystems have a StructHierarchyNamingAE for each SubSystems PlatePart. Therefore, testing for this problem is not currently active.
Possible Cause
Unknown.
Possible Impacts
No visible impact.
282
Molded Forms
Severity
Normal.
Detailed Description
Multiple StructNamingReference AEs are related to an Object.
Possible Cause
When two concurrent users add a deck at the same grid plane, both users will see that the grid has no naming AE associated to it. When this situation happens, there are two PlateSystemNamingAEs related to the grid via the StructNamingReference relationship.
Possible Impacts
No visible impact.
Severity
Fatal.
Detailed Description
Objects should not be related to ports with bags of bytes (BOB). The bag of bytes can change, and therefore binding to a port whose moniker has a bag of bytes can fail. The object should be related to a connectable port.
Possible Cause
The client allows users to select ports with bags of bytes in many instances. The client has been fixed to prevent this situation from happening, but it is possible that these relationships could have existed in the past or that there are certain cases that were overlooked where the user will still be able to select one of these BOB ports.
283
Severity
High.
Detailed Description
Some StructPlane3d objects and their corresponding PlaneByOffset_AEs and PlaneValues are not related to any other first class objects and are not required.
Possible Cause
Prior to V6, StructPlane3d objects and their corresponding PlaneByOffset_AE and PlaneValue objects were created but not properly deleted when the plates using them were deleted.
Possible Impacts
None expected.
284
Molded Forms
Severity
Crucial.
Detailed Description
The active entity for a plane created by two points and projection direction does not have a base plane (frame axis) for defining the projection direction. The relation PlaneBy2PtsProjDirBasePlane to FrameAxis for PlaneBy2PtsProjDir_AE is missing.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
Crucial.
Detailed Description
The active entity for a plane created by two points and projection direction does not have a base plane (frame axis) for defining the projection direction. The relation PlaneBy2PtsProjDirBasePlane to FrameAxis for PlaneBy2PtsProjDir_AE is missing.
Possible Cause
Unknown.
285
Severity
Crucial.
Detailed Description
The active entity for a plane created by two points and projection direction does not have an output normal vector for creating the plane. The relation PlaneBy2PtsProjDirNormal to Line for PlaneBy2PtsProjDir_AE is missing.
Possible Cause
Unknown.
Possible Impacts
Unknown.
286
Molded Forms
Severity
Crucial.
Detailed Description
The active entity for a plane created by two points and projection direction does not have an output normal vector for creating plane. The relation PlaneBy2PtsProjDirNormal to Line for PlaneBy2PtsProjDir_AE is missing.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
Crucial.
Detailed Description
The plane that is an output of the active entity for a plane created by two points and projection direction does not have an associated landing curve. The relation LandCrvIntersectionPlane to LandCrvTable_AE or the relation SeamLandCrvIntPlane to SeamTable_AE is missing.
Possible Cause
Unknown.
287
Severity
Crucial.
Detailed Description
Missing the PlateHasDimensions relationship to SiteProxy (IJDPlateDimensions) for root plate systems, StandalonePlatePart, SmartPlate, and CollarPart. Some Root PlateSystems are children of other Root PlateSystems. (The code now goes up two levels.) In this message, "dimensions" refers to thickness.
Possible Cause
This error occurs under two conditions.
288
Molded Forms
Condition 1 (Refer to What You Should Do, Action 1): The first condition occurs when plate systems are assigned as children to other plate systems, and the plate system hierarchy is more than three layers deep. The following graphic shows a plate system hierarchy with too many levels. Plate systems inherit properties like Molded Specification, Material, and Thickness from their parents. The data integrity checks only go up two levels looking for a root plate system to obtain the Thickness property. Thus, if the plate system is deeper than two levels below the root, no thickness property is found by the integrity check.
Condition 2 (Refer to Refer to What You Should Do, Action 2): The second condition occurs is when a plate system is created as the child of another plate system and later moved to a different location in the hierarchy where it becomes a root plate system. These plate systems will not have a Molded Specification or any Material properties assigned.
Possible Impacts
Thickening and display of light parts will fail. Referencing to the far side will not be accurate. Placing equipment may be done at the wrong location. The weight and center of gravity may not be calculated and will be invalid.
289
Molded Forms
4. If the object is still posted, contact SmartMarine 3D Support.
Severity
Crucial.
Detailed Description
Plate LinearExtrusion AE (operation) is missing its Mother Curve.
Possible Cause
Unknown.
Possible Impacts
The Plate will not process properly.
Severity
Crucial.
Detailed Description
Missing the PlateHasDimensions relationship to SiteProxy (IJDPlateDimensions) for StandalonePlatePart, SmartPlate, CollarPart.
Possible Cause
Unknown.
Possible Impacts
Thickening will fail. Referencing to the far side will not be accurate.
290
Molded Forms
The weight and center of gravity (CG) may not be calculated and will be invalid.
Severity
Crucial.
Detailed Description
In V6, only Seams can be used as boundaries. So, this test finds seams that still have plates as a boundary.
Possible Cause
Prior to V6, the plate being split was added as a boundary to the seam in order to provide solutions to an ambiguous case. Any object posted because of this situation was probably created in SmartMarine 3D prior to V6 and did not get properly converted.
Possible Impacts
The Seam will not be properly represented and may have difficulties being revised.
291
Molded Forms
Severity
Crucial.
Detailed Description
The Molded Conventions are not set on a Root Plate System.
Possible Cause
Unknown.
Possible Impacts
Plates and Stiffeners may fail during processing. This situation could affect Stiffener orientation and properties controlled by the default values for molded conventions.
292
Molded Forms
Severity
Fatal.
Detailed Description
There is a plate part without geometry associated to it. An example of this problem is PlateParts that are only associated to ReportData. The PlateParts do not have a parent system. In this case, deletion of the part is recommended.
Possible Cause
Unknown.
Possible Impacts
The plate part cannot be displayed graphically. The weight and center of gravity will be invalid. The user cannot manipulate the object itself or other objects related to it.
Severity
Fatal.
Detailed Description
A Plate Part is reported as having its geometry missing its active entity. This situation causes the geometry to not be updated as needed.
Possible Cause
Unknown.
293
Severity
Fatal.
Detailed Description
There is a plate part whose geometry has no active entity and therefore cannot be updated: Missing the StructOperation_RSLT1 relationship to (GeneratePlatePart_AE, PlateStrakingSplit_AE, SDCutAE, PlateFinalTrim_AE, or ChamferCut_AE) for detailed PlatePartGeometry.
Possible Cause
Unknown.
Possible Impacts
The user cannot manipulate the object itself or other objects related to it. The geometry will not be updated.
294
Molded Forms
Severity
Crucial.
Detailed Description
The Plate properties were not set properly. These properties include the Plate Type (Hull, Deck, BulkHead), the Tightness (NonTight, WaterTight), and the naming rule.
Possible Cause
Unknown.
Possible Impacts
Plates may not be properly updated.
Severity
Crucial.
Detailed Description
A Plate System is missing its PlatePart via the System Hierarchy and via the Graphics mapping.
Possible Cause
Unknown.
Possible Impacts
Unknown.
295
Molded Forms
3. Delete the object using one of the following methods: Select the object in the Workspace Explorer, and delete it. Run the Clean Database custom command to delete the object.
Severity
High.
Detailed Description
A Profile System created by projection is missing its two-dimensional sketched curve or the output collection for the contour. Case 1: In the few cases found with the two-dimensional sketched curve missing, it was also posted on the To Do List and posted for "A profile does not have a related child connection" and "A Profile system exists with no related planning split or light part" in the DBIntegrity table. The second posting recommends deletion of the object. Case 2: In most cases found, the problem was with the sketched curve missing its output collection. The profile systems appeared normal in the Workspace Explorer and in the graphic view. One can select the profile and modify it without any noticeable problems. Making any change to the projected sketched curve will correct the situation, and the next time the Check Database Integrity is run, it will be resolved. Developer Info: The symbol does have a ToDo record associated with it, which is not visible to the current user. Also, ASSERTs are noted in Debug mode when attempting to access and edit the profile.
Possible Cause
Unknown.
Possible Impacts
In case 1, the profile will not be displayable, be able to be detailed, or be manufactured.
296
Molded Forms
Severity
Crucial.
Detailed Description
Profile leaf system is not on the PartGeneration_OPER relationship with ProfilePartGeneration_AE.
Possible Causes
Models migrated from earlier versions to v5 or later tend to have this problem. The root system is not replaced with the leaf system on this relationship when the model is migrated.
Possible Impacts
The profile part may have incorrect geometry.
Severity
Crucial.
Detailed Description
A ProfileKnuckle requires an association to a Profile Landing Curve. This ProfileKnuckle is missing this relationship.
Possible Cause
Unknown.
Possible Impacts
Unknown.
297
Severity
Fatal.
Detailed Description
The profile system active entity (AE) is not related to a trace curve or a beam geometry. Possible situations: Missing ProfileSystemTrace relationship to ProfileLandCrv for ProfileSystemAE. Must also account for those ProfileSystemAE related to Beams on GeometryToBeam. They do not have ProfileSystemTraces.
Possible Cause
Unknown.
Possible Impacts
The user cannot manipulate the object itself or other objects related to it.
298
Molded Forms
ProfileSystem is not related to the Design nor the Planning Split AEs
Message
ProfileSystem is not related to the Design nor the Planning Split AEs.
Severity
Crucial.
Detailed Description
A profile system exists with no related design or planning split active entities. The profile system is most likely missing a child system or its part in the system hierarchy.
Possible Cause
Unknown.
Possible Impacts
Unknown.
ProfileSystem or an EdgeReinforcement System does not have a relationship to a ProfileSystem active entity
Message
ProfileSystem or an EdgeReinforcement System does not have a relationship to a ProfileSystem active entity.
Severity
Fatal.
Detailed Description
Either the ProfileSystem or the EdgeReinforcementSystem does not have a relationship to the ProfileSystemAE, preventing it from having geometry.
Possible Cause
Unknown.
299
Severity
High.
Detailed Description
A rotation angle is not set for the beam.
Possible Cause
Unknown.
Possible Impacts
Unknown.
300
Molded Forms
Severity
Crucial.
Detailed Description
A Seam by Projection Active Entity (operation) is missing its two-dimensional sketched curve. Another check will post the actual seam with its name.
Possible Cause
Unknown.
Possible Impacts
The Seam will not process properly.
Severity
High.
Detailed Description
A Seam by projection is missing its two-dimensional sketch curve or the output collection for the contour. Case 1: In the few cases found with the two-dimensional sketched curve missing, it was also posted on the To Do List. Case 2: In most cases found, the problem was with the sketched curve missing its output collection. The seam appeared normal in the Workspace Explorer and in the graphic view. One can select the seam and modify it without any noticeable problems. Making any change to the projected sketched curve will correct the situation, and the next time the Check Database Integrity is run, it will be resolved.
301
Molded Forms
Developer Info: The symbol does have a ToDo record associated with it, which is not visible to the current user. Also, ASSERTs are noted in Debug mode when attempting to access and edit the seam.
Possible Cause
Unknown.
Possible Impacts
In case 1, the seam will not display nor can it be used for splitting.
Severity
Fatal.
Detailed Description
The Seam does not have a relationship to its landing curve geometry. The Seam may be on the To Do List and could be repaired from there.
Possible Cause
Unknown.
Possible Impacts
Unknown.
302
Molded Forms
Severity
Fatal.
Detailed Description
The Seam Active Entity (SeamIntersect_AE, SeamOffset_AE, SeamProjection_AE, SeamByTable_AE) is missing its relationship to the Seam Landing Curve. A curve needed to be defined.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
There is a missing DefiningPoints relationship to CLandCrvPoint for SeamProject_AE. The points are required to define the seam by table. The Seam may be on the To Do List and could be repaired from there.
Possible Cause
Unknown.
Possible Impacts
Unknown.
303
Severity
Fatal.
Detailed Description
The SeamGeometry_AE is missing the relationship to the Plate being split. Because this object is not a first class object, the only action the user can do is delete it. If this error is a significant problem, and the SeamGeometry_AE has a relationship to its Seam, it may be possible for a routine to be created to fix the situation.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
The SeamGeometry_AE is missing the relationship to its first class object, the Seam. Because this object is not a first class object, the only action the user can do is delete it.
Possible Cause
Unknown.
304
Severity
Fatal.
Detailed Description
The SeamIntersection_AE is missing the relationship to the Plate or the PlatePart Base Surface Geometry being split. Because this object is not a first class object, the only action the user can do is delete it.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
The Seam Landing Curve is missing its relationship to either a generation AE or a Struct Operation. Because the curve does not know how it was created, it also does not know what to provide to the user; therefore, deleting it is the only expected option.
305
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
The SeamOffset_AE is missing the relationship to the value for the Landing curve offset.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
The SeamOffset_AE is missing the relationship to the Plate or the PlatePart Surface Geometry being split. This situation may be repairable.
306
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
The SeamProject_AE is missing the relationship to the Plate or the PlatePart Surface Geometry being split.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
Normal.
Detailed Description
A secondary class object should not be in CoreSpatialIndex. This situation might cause performance issues because the spatial index is used for in the filter functionality.
307
Possible Impacts
The primary impact of this problem is in the performance of the software.
Severity
Crucial.
Detailed Description
Shared Attributes, which are based on interfaces, have been created for or shared with objects that do not support the required interface. Typically, if a database has one case, it actually has many. Therefore, when this situation is found, a non-object is noted in the database as requiring repair instead of overwhelming the user by reporting each case found. Shared Attributes were found in the database for Logical, Assembly, and Physical Connections. These objects should not have any Shared Attributes. Stiffener and EdgeReinforcement objects were found to have Shared Attributes that are only required on Plates. Refer to TR64821, TR64495, and TR70360 (enhance the check for Shared attributes to make sure the interface is supported by the object.)
Possible Cause
Unknown. Code has been written to minimize this situation from happening in the future.
Possible Impacts
Some plates were unable to be selected and modified because their child profile systems had a relationship to the Plate's Shared Attributes defined by the IJPlate interface (TR84021). Property pages for other classes may have similar problems.
308
Severity
Crucial.
Detailed Description
The Structural Continuity for Ship Type (Continuous, Intercostal) or its priority is not set on a Root Plate, Stiffener, or Edge Reinforcement System.
Possible Cause
Unknown.
Possible Impacts
Plates and Stiffeners may fail during processing, especially in Struct Detailing where the Rules are used. The Physical Connections for profiles penetrating plates would be the prime problem.
309
Molded Forms
Severity
Fatal.
Detailed Description
A structural port exists without relating to a connectable business object.
Possible Cause
Unknown.
Possible Impacts
The user cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
A part that is defined by its parent's geometry is missing its parent. It could be a plate or profile part that is missing its Parent Plate or Profile System.
Possible Cause
TR 73385 has highlighted how this situation can occur. A PlatePart can be left behind if its parent PlateSystem was deleted while the PlatePart has an approval status of Approved.
Possible Impacts
Parts that should not exist will appear in the Workspace Explorer tree view and in the user interface.
310
The Logical Connection does not have the user class set
Message
The Logical Connection does not have the user class set.
Severity
Fatal.
Detailed Description
The logical connection has not had the proper user class set by the system.
Possible Cause
Unknown.
Possible Impacts
The Logical Connection will not be updated properly.
311
Molded Forms
Severity
High.
Detailed Description
There is a Permission Group for Molded Forms objects. This object should be in the Molded Forms Permission Group, but it is not.
Possible Cause
The object may have been created prior to the creation of the Molded Forms Permission Group.
Possible Impacts
Unknown.
The root logical connection is using a leaf system port instead of a root system port
Message
The root logical connection is using a leaf system port instead of a root system port.
Severity
Fatal.
Detailed Description
Improvements made to the logical connections require that the root logical connection be associated with ports of root systems and not leaf systems. The logical connection in error still has a relationship to a leaf system instead of a root system.
Possible Cause
The database may not have been migrated properly.
312
Severity
Normal.
Detailed Description
A duplicate relationship exists between objects.
Possible Cause
Unknown. But, this problem has been found for the ShipStructure hierarchy (parent child in tree view) relationships and for the Plate Bound operators 3 (PlateBound_OPER3) relationship. If you have ideas on how this problem happens, please share them with SmartMarine 3D Support.
Possible Impacts
Unknown. But, there is a potential for problems.
313
Molded Forms
Severity
High.
Detailed Description
When swapping Hulls with Permission groups to prevent updates to Molded forms, Logical connections are being placed on the To Do List. These Logical Connections cannot be removed from the To Do List even when permissions are given to Molded Forms, and the Logical Connection is updated via the To Do List window. Therefore, these objects need to be removed from the To Do List table using a tool.
Possible Cause
When swapping Hulls with Permission groups to prevent updates to Molded forms, Logical connections are being placed on the To Do List.
Possible Impacts
Too many items on the To Do List that cannot be removed directly by the user.
Severity
High.
Detailed Description
The CreateCollar_AE permission group does not match the CollarPart permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
314
Severity
High.
Detailed Description
The CreatePlatePart_AE permission group does not match the Plate Part permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
315
Molded Forms
Severity
High.
Detailed Description
The Custom Component permission group does not match the permission group of the Sketched Feature.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
The Cut_AE permission group does not match the Feature permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
316
Severity
High.
Detailed Description
The Design/Planning Split_AE permission group does not match the System permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
317
Molded Forms
Severity
High.
Detailed Description
The Detailing AE permission group does not match the Plate Part permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
The Edge Treatment permission group does not match the permission group of the parent (Part/Edge Feature).
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
318
Severity
High.
Detailed Description
The Feature Definition Point (Input) permission group does not match the Feature permission group.
Possible Cause
Unknown.
Possible Impacts
Type what can happen because of this problem.
319
Molded Forms
Severity
High.
Detailed Description
The Feature Definition Point (Output) permission group does not match the Feature permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
The Free end cuts permission group does not match the Part permission group. The profile's free end cuts permission group does not match the Profile part.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
320
Severity
High.
Detailed Description
The HierarchyNamingAE permission group does not match the permission group of the Relation Destination.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
321
Molded Forms
Severity
High.
Detailed Description
The Last Geometry permission group does not match the permission group of the Object.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
The NameRuleAE permission group does not match the permission group of the Relation Destination.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
322
Severity
High.
Detailed Description
The Operation_AE permission group does not match the Plate System permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
The PartReportData permission group does not match the Part permission group.
323
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
The permission group of the Feature on the FreeEndCut does not match the Part permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
324
Molded Forms
Severity
High.
Detailed Description
The permission group of Geometry after Operation_AE does not match the permission group of the Seam.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
The permission group of Geometry after ProfilePartGeneration_AE does not match the permission group of the Profile Part.
Possible Cause
Unknown.
325
Severity
High.
Detailed Description
The permission group of logical connection created by seams does not match the Parent permission group.
Possible Cause
The object may have been created before the creation of the Molded Forms Permission Group.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
326
Molded Forms
Severity
High.
Detailed Description
The permission group of PlatePartGeometry after CreatePlatePart_AE does not match the permission group of the Plate Part.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
The permission group of Seam LandCrvBound_AE does not match with the permission group of the Plate Part.
Possible Cause
Unknown.
327
Severity
High.
Detailed Description
The Plate Knuckle permission group does not match with the Plate System permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
328
Molded Forms
PlateBound_AE / PlateCutOut_AE InPut Geometry PG does not match with Plate System PG
Message
PlateBound_AE / PlateCutOut_AE InPut Geometry PG does not match with Plate System PG.
Severity
High.
Detailed Description
The PlateBound_AE / PlateCutOut_AE InPut Geometry permission group does not match the Plate System permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
The PlateBound_AE / PlateCutOut_AE permission group does not match the Plate System permission group.
Possible Cause
Unknown.
329
Severity
High.
Detailed Description
The PlateCutOut_AE InPut Geometry permission group does not match the Plate System permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
330
Molded Forms
Severity
High.
Detailed Description
The PlateCutOut_AE permission group does not match the Plate System permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
The PlatePartGeometry permission group does not match with the Plate Part permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
331
Molded Forms
2. In the software, click Tools > Custom Commands, and run the Clean Database custom command. 3. Select the object(s) to be repaired. 4. Click Clean Now. 5. Re-run the Check Database Integrity custom command and the DBIntegrity report. 6. If the object is still posted, contact SmartMarine 3D Support.
Severity
High.
Detailed Description
The Profile Knuckle permission group does not match with the Profile System permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
332
Molded Forms
Severity
High.
Detailed Description
The ProfileKnuckle LandingCurve permission group does not match the Profile System permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
The ProfilePartGeneration_AE permission group does not match the Profile Part permission group.
Possible Cause
Unknown.
333
Severity
High.
Detailed Description
The ProfileTrim_AE permission group does not match the permission group of the Profile Struct Feature.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
334
Molded Forms
Severity
High.
Detailed Description
The Seam landing offset permission group does not match with the permission group of the Seam.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
The Seam Operation_AE permission group does not match the permission group of the Seam.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
335
Molded Forms
2. In the software, click Tools > Custom Commands, and run the Clean Database custom command. 3. Select the object(s) to be repaired. 4. Click Clean Now. 5. Re-run the Check Database Integrity custom command and the DBIntegrity report. 6. If the object is still posted, contact SmartMarine 3D Support.
Severity
High.
Detailed Description
The SeamGeometry_AE permission group does not match the Seam permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
336
Molded Forms
Severity
High.
Detailed Description
The Sketch feature permission group does not match with the Part permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
The SketchReferenceCol permission group does not match the permission group of the Sketched Feature.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
337
Severity
High.
Detailed Description
The StdPlateSystemNamingAE permission group does not match the permission group of the StdPlateSystem.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
338
Molded Forms
Severity
High.
Detailed Description
The StrikeSplit_AE permission group does not match the SeamSeamPoint permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
The assembly connection permission group does not match the part permission group. The permission group of the assembly connection should be the same as the part (dependant part) permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
339
The Beam Point3d PG does not match with Beam Stand Alone Part PG
Message
The Beam Point3d PG does not match with Beam Stand Alone Part PG.
Severity
High.
Detailed Description
The Beam Point3d permission group does not match the Beam Stand Alone Part permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
340
Molded Forms
Severity
High.
Detailed Description
The BeamAssoc Point permission group does not match the BeamSystem permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
The BeamGeneration_AE PG does not match with Beam Stand Alone Part PG
Message
The BeamGeneration_AE PG does not match with Beam Stand Alone Part PG.
Severity
High.
Detailed Description
The BeamGeneration_AE permission group does not match the Beam Stand Alone Part permission group.
Possible Cause
Unknown.
341
Severity
High.
Detailed Description
The BeamGeneration_AE permission group does not match the BeamSystem permission group.
Possible Cause
Unknown.
Possible Impacts
Type what can happen because of this problem.
342
Molded Forms
Severity
High.
Detailed Description
The BeamLandCurve_Input permission group does not match the BeamSystem permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
The BeamLandingCrv permission group does not match the BeamSystem permission group.
Possible Cause
Unknown.
343
The BeamStandAlonePart_AE PG does not match with Beam Stand Alone Part PG
Message
The BeamStandAlonePart_AE PG does not match with Beam Stand Alone Part PG.
Severity
High.
Detailed Description
The BeamStandAlonePart_AE permission group does not match the Beam Stand Alone Part permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
344
Molded Forms
Severity
High.
Detailed Description
The BeamSystem_AE permission group does not match with the Beam System permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
The defining points needed for the BracketByPlane plate system have a different Permission Group (PG) than that of the BracketByPlane plate system. The defining points need to have the same permission group as the plate system.
Possible Cause
Unknown.
345
Severity
High.
Detailed Description
The defining ReferenceCollection, which provides symbol information needed for the BracketByPlane plate system, has a different Permission Group (PG) than that of the BracketByPlane plate system. The ReferenceCollection must have the same permission group as the plate system.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
346
Molded Forms
Severity
High.
Detailed Description
The child logical connection's permission group does not match the root logical connection's permission group.
Possible Cause
Unknown.
Possible Impacts
Type what can happen because of this problem.
Severity
High.
Detailed Description
The collar's permission group does not match the part's permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
347
Severity
High.
Detailed Description
The feature's permission group does not match its part's permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
348
Molded Forms
Severity
High.
Detailed Description
The IntersectionAE (Active Entity) for the Feature's Definition Point does not have a Permission Group that matches the Feature's Permission Group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
The LandCrvBound_AE permission group does not match the BeamSystem permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
349
Severity
High.
Detailed Description
The Landing Curve permission group does not match the Standalone Stiffener permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
350
Molded Forms
Severity
High.
Detailed Description
The Landing Offset permission group does not match the Profile System permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
The LandingCrvBound_AE permission group does not match the Profile System permission group.
Possible Cause
Unknown.
351
Severity
High.
Detailed Description
The LandingCrvPoint permission group does not match the Profile System permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
352
Molded Forms
Severity
High.
Detailed Description
The LandingCrv_AE permission group does not match the ProfileSystem permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
The LandOffset does not match the Edge Feature permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
353
Severity
High.
Detailed Description
The leaf part's permission group does not match the root part's permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
354
Molded Forms
Severity
High.
Detailed Description
The Leaf ProfileLandCrv permission group does not match the Leaf ProfileSystem permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
The Leaf ProfileSys Region PG does not match with Leaf Profile System PG
Message
The Leaf ProfileSys Region PG does not match with Leaf Profile System PG.
Severity
High.
Detailed Description
The Leaf ProfileSys Region permission group does not match the Leaf Profile System permission group.
Possible Cause
Unknown.
355
Severity
High.
Detailed Description
The Leaf ProfileSystem_AE permission group does not match the Leaf ProfileSystem permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
356
Molded Forms
Severity
High.
Detailed Description
The leaf system permission group does not match the root system permission group. When the root system permission group is changed to another permission group, the leaf system is not also changed to the new permission group.
Possible Cause
The object may have been created before the creation of the Molded Forms permission group.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
The OffsetPt_AE permission group does not match the Edge Feature permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
357
Severity
High.
Detailed Description
The Opening permission group does not match the root system permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
358
Molded Forms
Severity
High.
Detailed Description
The permission group of the Chamfer does not match Part permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
The permission group of a physical connection on an assembly connection does not match the Parent permission group.
Possible Cause
Unknown.
Possible Impacts
Type what can happen because of this problem.
359
Severity
High.
Detailed Description
The permission group of a PhysicalConnection on a Collar does not match the Part permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
360
Molded Forms
Severity
High.
Detailed Description
The permission group of a PhysicalConnection on a Feature does not match the Part permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
The PtOnGeom_AE (ActiveEntity) for the Feature's Definition Point belongs to a Permission Group that is different from the Feature's Permission Group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
361
Severity
High.
Detailed Description
The PointOnSurfByTwoCoords_AE permission group does not match the Profile System permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
362
Molded Forms
Severity
High.
Detailed Description
The ProfileLandCrv permission group does not match the ProfileSystem permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
363
Molded Forms
Severity
High.
Detailed Description
The ProfileLandCrvInPut permission group does not match the Profile System permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
364
Molded Forms
Severity
High.
Detailed Description
The ProfilePartCreation permission group does not match the StandAloneStiffener permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
365
Molded Forms
Severity
High.
Detailed Description
The ProfilePartPath permission group does not match the StandAlone Stiffener permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
366
Molded Forms
Severity
High.
Detailed Description
The ProfileSysRegion permission group does not match the ProfileSystem permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
The ProfileSystem_AE permission group does not match the Profile System permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
367
Severity
High.
Detailed Description
The Ref Curve permission group does not match the root system permission group. For example, the permission group for the reference curves of the hull does not match the permission group for the hull.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
368
Molded Forms
Severity
High.
Detailed Description
The permission group of the root logical connection does not match the permission group of the dependent system. The permission group of the root logical connection should be the same as the permission group of the dependent part.
Possible Cause
The object may have been created before the creation of the Molded Forms permission group.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
The permission group for rule-based features does not match the Part permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
369
Severity
High.
Detailed Description
The Seam permission group does not match the root system permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
370
Molded Forms
Severity
High.
Detailed Description
The permission group of the SharedAttEntityBag does not match with its parent permission group. The parent may be a root system, leaf system, or a part.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
The ShpStrEdgeFeatOffPt_OUT permission group does not match the Edge Feature permission group.
Possible Cause
Unknown.
371
Severity
High.
Detailed Description
The Symbol permission group does not match the BeamSystem permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
372
Molded Forms
Severity
High.
Detailed Description
The Symbol permission group does not match the Beam StandAlone Part permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
Severity
High.
Detailed Description
The Symbol permission group does not match the ProfileSystem permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
373
Severity
High.
Detailed Description
The Symbol permission group does not match the StandAloneStiffener permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
374
Molded Forms
Severity
High.
Detailed Description
The TrackPoint3D permission group does not match the Feature permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
The Tripping Assoc Point PG does not match with Profile System PG
Message
The Tripping Assoc Point PG does not match with Profile System PG.
Severity
High.
Detailed Description
The Tripping Assoc Point permission group does not match the Profile System permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
375
Severity
High.
Detailed Description
The WireBody2 permission group does not match the ProfileSystem permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
376
Molded Forms
Severity
High.
Detailed Description
The WireBody2 permission group does not match the StandAlone Stiffener permission group.
Possible Cause
Unknown.
Possible Impacts
You cannot manipulate the object itself or other objects related to it.
377
Molded Forms
378
SECTION 17
Piping
This section contains Piping database integrity messages.
Severity
Crucial.
Detailed Description
Pipe end or turn feature which has an offline relation should also have a HasTapFeature relation.
Possible Cause
Unknown.
Possible Impacts
Any modification of the object will fail.
379
Piping
Severity
High.
Detailed Description
Non-spool object should not have a relation with ConfigProjectRoot.
Possible Cause
Unknown.
Possible Impacts
Any modification of the object will fail.
380
SECTION 18
Planning
This section contains Planning database integrity messages.
Severity
Fatal.
Detailed Description
The assembly has itself as a parent in the AssemblyHierarchy. The assembly may not be visible on the Assembly tab of the Workspace Explorer.
Possible Cause
It was possible at one time to drag and drop an assembly on top of itself.
Possible Impacts
There is a potential for infinite loops. Due to relationship limitations, the assembly may disappear from the Assembly tab of the Workspace Explorer and will no longer have a direct or indirect relationship to the B0 block.
381
Planning
Severity
Normal: Should not impact the user.
Detailed Description
Block assemblies must have blocks in them. During the creation of block assemblies, the software checks to ensure that invalid block assemblies are not created. However, block assemblies can be emptied without removing blocks.
Possible Cause
The cause is removal of all blocks from a block assembly.
Possible Impacts
This situation should have no impact on the end user.
Severity
Fatal.
Detailed Description
The common part group has been deprecated and is no longer needed. Lingering data in the database associated with common part groups could cause data model errors.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Common groups are not valid anymore and, as such, will not be able to report the correct information to the user. Also, any data that exists could cause fatal data model errors.
382
Migration to V6.1 should have removed all objects in the PLANNGAssemblyReportData table
Message
Migration to V6.1 should have removed all objects in the PLANNGAssemblyReportData table.
Severity
Normal: Should not affect the user.
Detailed Description
The PLANNGAssemblyReportData table should have been tombstoned and all objects on it removed during migration. If this operation did not occur properly, it could cause asserts for builds registered in Debug mode, and may have negative impacts on other operations that are scheduled to be implemented in the future.
Possible Cause
This situation could be caused by improper migration to V6.1 or errors during migration that were not properly handled.
Possible Impacts
This problem should have no impact on the end user at this time.
Severity
Normal: Should not impact the user.
Detailed Description
Block assemblies are the only object that the end user is allowed to drag and drop blocks into. In the past, the B0 block has been dropped into a block assembly. B0 must remain the child of the project root for numerous reasons.
Possible Cause
The cause is dragging and dropping the B0 block into a block assembly.
383
Severity
Normal: Should not impact the user.
Detailed Description
Block assemblies must be the children of a block. Block assemblies with this error, however, are children of the project root, as B0 is.
Possible Cause
The cause is drag and drop errors.
Possible Impacts
This problem should have no impact on the end user.
384
Planning
Severity
Fatal.
Detailed Description
With the implementation of split notification, the Planning intersection object can now be properly migrated as parts are split with planning seams. When a part is split, the associated intersection object no longer needs to be moved to the system. The intersection object in error still has a relationship with a system instead of a part.
Possible Cause
The intersection object may have been created in an older version of the software, and the migration command failed to modify the relationship.
Possible Impacts
The adding and removing of planning splits may fail.
Severity
High.
Detailed Description
There is a Permission Group for Planning objects. This object should be in the Planning Permission Group, but it is not.
Possible Cause
The object may have been created prior to the creation of the Planning Permission Group.
385
Severity
Crucial.
Detailed Description
The implementation of Copy Similar functionality in V6 required the addition of several new tables in the Model and Catalog databases. The new tables are created in a V5 database during migration. The PLANNGAssemblyBase table does not have the new BlobSize field.
Possible Cause
Migration to V6 of a database created on an earlier version was not performed or was not successful.
Possible Impacts
The Copy Similar functionality will not work.
386
Planning
Severity
Crucial.
Detailed Description
The implementation of Copy Similar functionality in V6 required the addition of several new tables in the Model and Catalog databases. The new tables are created in a V5 database during migration. The PLANNGAssemblyBase table does not have the new ConnectivityInfo field.
Possible Cause
Migration to V6 of a database created on an earlier version was not performed or was not successful.
Possible Impacts
The Copy Similar functionality will not work.
Severity
Crucial.
Detailed Description
There is more than one root block (B0). All programmatic design decisions were based on having only one root block (B0).
Possible Cause
This error could be caused by several users entering Planning at nearly the same time, when the B0 block had not yet been created.
387
Severity
Fatal.
Detailed Description
An Assembly has been located that has more than one parent. An Assembly should always have only one parent.
Possible Cause
Programmatic error or failure during database commit.
Possible Impacts
There is the potential for an infinite loop.
388
SECTION 19
Project Management
This section contains Project Management database integrity messages.
Severity
Low.
Detailed Description
The Access Control Rule object is not related to the Permission Group object anymore.
Possible Cause
This error is reported under the following circumstances: 1. When the corresponding permission group is deleted for unknown reasons. 2. Deletion of model. Due to some design constraints, access control rules are not cleaned up when deleting the model. This situation will be corrected in future releases.
Possible Impacts
None.
Severity
Fatal.
Detailed Description
Database is not related to a plant in the Site database.
389
Possible Impacts
Database will be inaccessible. If the database belonged to a model that was deleted, then the severity of the problem is very low. In this case, there is no impact. Users can ignore this error.
Severity
Fatal.
Detailed Description
Location information is not associated to the project collection object.
Possible Cause
The cause is currently unknown.
Possible Impacts
Location information will be inaccessible. This Location cannot be used as part of a global workshare configuration setup.
Severity
Fatal, High.
Detailed Description
This error is reported when there is no relation between Folder and Folder Child or Folder and Folder parent.
390
Possible Impacts
The hierarchy of folders and permission groups in the Model and Catalog databases might be inaccessible, and hence cannot be seen in the Project Management task. The Model and Catalog databases will be inaccessible if the parent folder is missing.
Invalid relationship between the Workspace Explorer root and the plant in the site database
Message
Invalid relationship between the Workspace Explorer root and the plant in the site database.
Severity
Fatal.
Detailed Description
The Workspace Explorer root is not connected to the model in the Site database.
Possible Cause
The cause is currently unknown.
Possible Impacts
Batch processing of drawings will fall. The Define Workspace command will also fail.
391
Project Management
Model database has more than one site occurrence for catalog
Message
Model database has more than one site occurrence for catalog.
Severity
Crucial.
Detailed Description
There are currently two different attachments to a catalog in the model database. A model database can only be attached to one catalog.
Possible Cause
A temporary memory corruption on a client workstation might create the situation on an older version of the software. The current version of the software does stricter error checking to avoid that type of corruption.
Possible Impacts
Some objects might not be synchronized or copied properly. Some catalog specifications might not be retrieved properly.
Severity
Fatal.
Detailed Description
This error is reported when the Model database has more than one Proxy Owner for the Site database.
Possible Cause
The cause is unknown.
Possible Impacts
This situation will cause various problems when users define the workspace or create filters.
392
Severity
Fatal.
Detailed Description
This error is reported when the Model database has more than one Config Project Root object.
Possible Cause
The cause is unknown.
Possible Impacts
This situation will cause various problems when users define the workspace or create filters.
Severity
Fatal.
Detailed Description
This error is reported when multiple Access Control Rules with identical role names are associated to a Permission Group.
Possible Cause
The cause is unknown.
Possible Impacts
The Edit > Permissions command does not work.
393
Severity
Crucial.
Detailed Description
This error is reported either when a permission group is related to more than one folder parent or when a permission group is related to one folder parent more than one time.
Possible Cause
This situation can happen due to unexpected errors when permission groups are moved from one folder parent to another folder parent. In all other circumstances, the cause is unknown.
Possible Impacts
Trying to modify any object in the model gives errors. If you select the problematic permission group in the project environment, the software displays an application error.
Severity
High.
Detailed Description
Permission Group is orphaned.
Possible Cause
The cause is currently unknown.
394
Severity
High.
Detailed Description
Permission Group is not associated to a Location object.
Possible Cause
The cause is currently unknown.
Possible Impacts
The permission group might be visible and editable in the Project Management task, but may not appear in the dropdown box that lists all the available permission groups in the modeling tasks. If the model under which this permission group resides is replicated as part of a global workshare configuration, then the replicated setup may not work properly.
395
Project Management
Severity
High.
Detailed Description
This error is reported when there is no relation between Project Root (Plant) and Project Collection (Plant Root) object.
Possible Cause
The error can happen when there are unexpected errors when creating a model. In all other circumstances, the cause is unknown.
Possible Impacts
If the Project Root object does not have a relation with the project collection object, then the model will not be visible in the Project Management task. The corresponding model will be inaccessible.
396
SECTION 20
Reference Data
This section contains Reference Data database integrity messages.
Severity
The severity of the error depends on the type of object for which this error has occurred. Please see the section Detailed Description for the level of severity for each type of object.
Detailed Description
This error is reported under the following circumstances: 1. For all Outfitting Cross-sections that are not related to an outfitting cross- section definition: Severity - High 2. For all orphaned pipe ports in the database that are not associated with any parts: Severity Low 3. For all Name Rule Holder objects that are not associated with a class node object: Severity High 4. For all Insulation Thickness rule objects that are not related to an Insulation spec: Severity Low. 5. For all Allowable Insulation Thickness objects that are not related to an Insulation material: Severity - Low.
Possible Cause
This situation can happen when there are unexpected errors when editing the data using the Bulkload utility. Under normal circumstances, modification of data using the Bulkload utility will, if necessary, automatically propagate changes to objects that are related to the data. If there is an unexpected error while modifying the data, it can result in some associated objects getting left behind as orphans in the database.
Possible Impacts
Error with Outfitting Cross-Section: This error will impact users when they go into the HVAC and Electrical modeling tasks. If this relation is missing, then the software cannot get to these outfitting cross-section objects. Because the Reference data APIs will not be able to get to these objects, users cannot place ducts in these sizes. These objects will not be visible in the Catalog task, either. Error with orphaned pipe ports: These are just orphaned entries in the database. No Impact. Error with Name Rule Holder objects: This error will impact users when they are modeling objects. In order to get the Name rule that is associated with the type of object that they are
397
Reference Data
modeling, the association between the class node and the Name Rule Holder is necessary. If this relation is missing, then the software cannot use the Name Rule to generate a new name for the object that is being modeled. Error with Insulation Thickness Rule and Allowable Insulation Thickness objects: This error means that the software will not be able to access the insulation data, even though the data actually resides in the database. This error will impact users when they attempt to assign an insulation thickness to the objects that were placed in the model.
8. 9.
10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20.
398
Reference Data
21. Locate all the workbooks that contain the CableWaySpec, CableWayNominalSizes, and CableWayBendRadius sheets. Type A in the first column of all the rows on the sheets. 22. Start the Bulkload utility. 23. Select all the workbooks that were modified. 24. Specify the server, database, log file, and other details on the dialog box. 25. For the bulkload mode, select Add, modify, or delete records in existing catalog. 26. Click Load. Bulkload will create the objects and also update the references to the outfitting cross-sections that were created. Error with Name Rule Holder objects: The problem can be addressed by using the Bulkload utility to re-create the Name Rule Holder objects. 1. Open the Excel workbook that contains the NamingRules sheet, which contains the data for the Name Rules. In the set of data that is delivered with the software, this data can be found in the GenericNamingRules.xls workbook. 2. On this sheet, type A in the first column of all the rows. 3. Start the Bulkload utility. 4. In the Excel Files box, specify the workbook that was modified. 5. Specify the server, database, schema, and other details on the dialog box. 6. For the bulkload mode, select Add, modify, or delete records in existing catalog. 7. Click Load. Bulkload will attempt to re-create all the entries on the sheet. Error with Insulation Thickness Rule objects: The problem can be addressed by using the Bulkload utility to re-create the data. 1. Open the Excel workbook that contains the InsulationThicknessTable sheet, which contains the data for the Insulation Thickness Rule. In the set of data that is delivered with the software, this data can be found in the InsulationData.xls workbook. 2. On the sheet, type D in the first column of all the rows that define the thickness values. Be sure to leave out the rows that define a spec name. 3. Start the Bulkload utility. 4. In the Excel Files box, specify the workbook that was modified. 5. Specify the server, database, schema, and other details on the dialog box. 6. For the bulkload mode, select Add, modify, or delete records in existing catalog. 7. Click Load. Bulkload will delete all the thickness objects from the database. 8. Re-open the Excel sheet that was modified. 9. This time, replace the D in the first column with A. 10. Start the Bulkload utility. 11. In the Excel Files box, specify the workbook that was modified in the previous step. 12. Specify the server, database, schema, and other details on the dialog box. 13. For the bulkload mode, select Add, modify, or delete records in existing catalog. 14. Click Load. Bulkload will re-create all the thickness objects in the database. This process will re-create the relations that were reported as missing by the database integrity scripts. Error with Allowable Insulation Thickness objects: The problem can be addressed by using the Bulkload utility to re-create the data. 1. Open the Excel workbook that contains the InsulationMaterial sheet, which contains the data for the Allowable Insulation Thickness Rule. In the set of data that is delivered with the software, this data can be found in the InsulationData.xls workbook.
399
Reference Data
2. On this sheet, type D in the first column of all the rows that define the thickness values. Be sure to leave out the rows that define a material type and density. 3. Start the Bulkload utility. 4. In the Excel Files box, specify the workbook that was modified. 5. Specify the server, database, schema, and other details on the dialog box. 6. For the bulkload mode, select Add, modify, or delete records in existing catalog. 7. Click Load. Bulkload will delete all the thickness objects from the database. 8. Re-open the Excel sheet that was modified. 9. This time, replace the D in the first column with A. 10. Start the Bulkload utility. 11. In the Excel Files box, specify the workbook that was modified in the previous step. 12. Specify the server, database, schema, and other details on the dialog box. 13. For the bulkload mode, select Add, modify, or delete records in existing catalog. 14. Click Load. Bulkload will re-create all the thickness objects in the database. This process will re-create the relations that were reported as missing by the database integrity scripts.
Severity
The severity of the error depends on the type of object for which this error has occurred. Please see the Detailed Description section for the level of severity for each type of object.
Detailed Description
This error is reported under the following circumstances: 1. For all Catalog Roots that do not have a parent: Severity - Low 2. For all Piping commodity filters that are not related to any piping materials class: Severity Low 3. For all parts that are not related to any part class: Severity - Low 4. For all orphaned SymboldefHelper objects that are not associated with any Parts, cross sections, or StructFeatureOrJoint objects: Severity - Low. 5. For all HVAC Permissible Thickness Objects that are not associated with an HVAC material: Severity - Low
Possible Cause
This situation can happen when there are unexpected errors when editing the data using the Bulkload utility. Under normal circumstances, modification of data using the Bulkload utility will, if necessary, automatically propagate changes to objects that are related to the data. If there is an unexpected error while modifying the data, it can result in some associated objects getting left behind as orphans in the database.
400
401
Reference Data
Error with HVAC Permissible Thickness objects: The problem can be addressed by using the Bulkload utility to re-create the HVAC Permissible Thickness objects. 1. Open the Excel workbook that contains the PermissibleDuctThickness sheet, which contains the data for the HVAC Permissible Thickness objects. 2. Create a workbook containing only this sheet. 3. Start the Bulkload utility. 4. In the Excel Files box, specify the new workbook that was created in step 1. 5. Specify the server, database, schema, and other details on the dialog box. 6. For the bulkload mode, select Delete and replace records in existing catalog. 7. Click Load. Bulkload will then delete and re-create all the HVAC Permissible Thickness objects in the database.
Severity
The severity of the error depends on the type of object for which this error has occurred. Please see the Detailed Description section for the level of severity for each type of object.
Detailed Description
This error is reported under the following circumstances: A: A Catalog Root object that has a relation with Class Node: Severity - Crucial B: For pipe parts that have a relation to more than one commodity piping material control data object: Severity - Crucial
Possible Cause
A: This error is reported when one of the hierarchical nodes (objects from ClassNodeType sheet) is related directly to the Catalog Root (top node in the Catalog task, which is represented by the name of the catalog), instead of its respective hierarchy Root node. B: This error is reported when the Catalog database contains pipe parts that have a relation to more than one commodity piping material control data object. This situation can happen when the material control data-pipe component semantic (which is triggered when the part is created) encounters an unexpected error. Incorrect data on the PipingCommodityMatlControlData sheet will lead to such an error. An example is when multiple entries on the PipingCommodityMatlControlData sheet have identical contractor commodity codes, but overlapping first size and/or second size ranges.
Possible Impacts
A: Error with Catalog Root: If the Catalog Root object has a relation with any of the hierarchy nodes (class nodes), then sometimes nothing will come up under the top root node in the Catalog task. B: Error with pipe parts: This error will impact users when they go into the Piping task. One or more of the reference data APIs will return an error code when encountering a piping part that is related to more than one piping commodity material control data object.
402
403
Reference Data
404
SECTION 21
Route Cable
This section contains Route Cable database integrity messages.
Severity
Crucial.
Detailed Description
All cable features should be associated with a leg. This feature is not associated with any leg.
Possible Cause
Unknown.
Possible Impacts
You may not be able to modify the cable path.
Severity
Crucial.
Detailed Description
All cable features must be associated to their parent run objects. If the features are not associated to the run, then they will not be brought into the workspace by normal means. However, you always have the ability to bring them into the workspace using the Object Type property.
Possible Cause
In earlier versions (prior to Version 3.0), selecting a feature and changing the run could result in this error, especially when the run to which the feature is being moved is a read-only run.
405
Route Cable
However, this problem has been identified in the route code and has been fixed since then. This error should not occur in Version 4.1 or beyond.
Possible Impacts
You are not able to modify the feature (assuming you had brought the feature into the workspace using Object Type filters).
Severity
Crucial.
Detailed Description
Cable should always be associated to the catalog part.
Possible Cause
Catalog part may not be available.
Possible Impacts
You may not be able to view the cable.
Severity
Crucial.
Detailed Description
A cable run has been found in the database with no relationships to equipment. In its nominal state, a cable is expected to connect two pieces of equipment.
Possible Cause
Most likely, this situation was caused as a result of the deletion of one or both of the pieces of equipment to which the cable was related. Check your cable schedule to determine what
406
Route Cable
equipment the cable is supposed to connect, and verify that both pieces of equipment still exist in the Model database. If they do, the cable can be re-connected to them. If not, either the equipment must be re-created and the cable re- connected, or the cable should be deleted. This error should be accompanied by an entry on the To Do List.
Possible Impacts
The reported length of this cable cannot be assumed to be accurate because it does not account for the length required to attach to equipment. Also, reports on the cable will not properly list its equipment connections.
Severity
Normal.
Detailed Description
A Cable Leg should always have Features.
Possible Cause
Unknown.
Possible Impacts
No impact. A Route leg is not a first class Business Object, so this error will not affect anything.
407
Route Cable
Severity
Crucial.
Detailed Description
A Cable part has lost its relationship to its Feature.
Possible Cause
Unknown.
Possible Impacts
The Drawings and Reports task and filters will not have the right information.
Severity
High.
Detailed Description
A cable part has lost its relationship to its run.
Possible Cause
Unknown.
Possible Impacts
The Drawings and Reports task and filters will not have the right information.
408
Route Cable
Severity
Fatal.
Detailed Description
A cable run has been found in the model that has no cable path features related to it. In other words, the cable run has no design children. It has no end features with which to connect to equipment and no segment features that can be associated with a cableway or conduit run, nor does it have any path legs associated with it that can be used to connect the segments or the two pieces of equipment. At a minimum, a cable run should have three features associated with it: two end features and one path leg. As the cable is routed, more features will be added. At no time should a cable run have no features associated with it. Note that the type of features identified as missing is not identifiable in the graphical tasks (even when they do exist). These objects are utilized internally to create and manage the path of a cable run.
Possible Cause
This situation is highly unusual. It most likely occurs due to some interruption of the algorithm during a commit when the child relationships are not written to the Model database.
Possible Impacts
This cable run cannot be routed nor does it know what equipment it is connecting. It cannot be cleaned. It must be destroyed and re-created.
409
Route Cable
Severity
Crucial.
Detailed Description
A cable run has been found in the Model database without an associated part in the Catalog.
Possible Cause
Most likely, the part was deleted from the Catalog database, or some error occurred while accessing the Catalog database during a commit operation. Note that, unlike other routing applications, a cable run has one (and only one) catalog part associated to it.
Possible Impacts
The cable has no part information. It cannot report any part information either on the Properties dialog box or in MTO reports. Further, the software has no mechanism for reporting the weight and CG of the cable, so this information will not be included in weight and CG reports. Consult your cable schedule to determine the part number that should be utilized with this cable. Verify that the part number exists in the Catalog being used by this Model database and, if it does, modify the cable such that it once again points to the given part number. If the part number does not exist in the Catalog database, it should be added to it.
410
Route Cable
Severity
Fatal.
Detailed Description
EntryExit should always be connected to a leg.
Possible Cause
This situation might be due to a permission group problem.
Possible Impacts
Modification of the cable path may not be possible.
Severity
Crucial.
Detailed Description
A marker should always be connected to a leg.
Possible Cause
This situation might have occurred because of permission boundaries.
Possible Impacts
The Drawings and Reports task will not have the right information.
411
Route Cable
Severity
Crucial.
Detailed Description
A marker should always be connected to a leg.
Possible Cause
This situation might have occurred because of permission boundaries.
Possible Impacts
The Drawings and Reports task will not have the right information.
Severity
Crucial.
Detailed Description
A cable segment should always be associated with some boundary.
Possible Cause
This situation might be due to a permission group problem.
Possible Impacts
Modification of the cable path may not be possible.
412
Route Cable
Severity
Fatal.
Detailed Description
A cable segment should always be associated with some feature.
Possible Cause
This situation might be due to a permission group problem.
Possible Impacts
Modification of the cable path may not be possible.
Severity
Fatal.
Detailed Description
A cable segment should always be associated with a leg.
Possible Cause
This situation might be due to a permission group problem.
Possible Impacts
Modification of the cable path may not be possible.
413
Route Cable
414
SECTION 22
AE (Arrangement)/Broker that has the Querystring of elements in Model exists without a ShipDwgView
Message
AE (Arrangement)/Broker that has the Querystring of elements in Model exists without a ShipDwgView.
Severity
Fatal.
Detailed Description
A detailed description of the problem is not currently available.
Possible Cause
The cause of this problem is unknown.
Possible Impacts
The functionality of Ship Drawings will be impaired.
AE (Hulllines)/Broker that has the Querystring of elements in Model exists without a ShipDwgView
Message
AE (Hulllines)/Broker that has the Querystring of elements in Model exists without a ShipDwgView.
Severity
Fatal.
Detailed Description
A detailed description of the problem is not currently available.
415
Possible Impacts
The functionality of Ship Drawings will be impaired.
AE (scantling by volume)/Broker that has the Querystring of elements in Model exists without a ShipDwgView
Message
AE (scantling by volume)/Broker that has the Querystring of elements in Model exists without a ShipDwgView.
Severity
Fatal.
Detailed Description
A detailed description of the problem is not currently available.
Possible Cause
The cause of this problem is unknown.
Possible Impacts
The functionality of Ship Drawings will be impaired.
AE (ShellExpansion)/Broker that has the Querystring of elements in Model exists without a ShipDwgView
Message
AE (ShellExpansion)/Broker that has the Querystring of elements in Model exists without a ShipDwgView.
Severity
Fatal.
416
Possible Cause
The cause of this problem is unknown.
Possible Impacts
The functionality of Ship Drawings will be impaired.
Severity
Fatal.
Detailed Description
New tables were added to handle the shell expansion system. Specifically, the SHIPDWGShellExpSystem table was added. The migration of a V5 database to V6 added these tables to the database.
Possible Cause
Version migration did not get accomplished properly.
Possible Impacts
You cannot create a Shell Expansion system (mesh).
417
Severity
Fatal.
Detailed Description
New tables were added to handle generic storage. Specifically, the SHIPDWGXMLStorage table was added. The migration of a V5 database to V6 added these tables to the database.
Possible Cause
Version migration did not get accomplished properly.
Possible Impacts
You cannot create any drawings using the "Drawings by Ruleset" workflow.
Severity
Fatal.
Detailed Description
A detailed description of the problem is not currently available.
Possible Cause
The cause of this problem is unknown.
Possible Impacts
The functionality of Ship Drawings will be impaired.
418
Severity
Fatal.
Detailed Description
In order to support shell expansion drawings, a new persistent property is added. A migration script is necessary to handle this change for existing Model databases. The migration script adds a new column called dTimeLastGenerated and sets its value to "dTimeLastGenerated." Also, this script modifies the GET and SET stored procedures.
Possible Cause
Database changes have occurred, and the migration to a higher version was not done or else failed.
Possible Impacts
Shell expansion drawings in Ship Drawings will not appear correctly.
Severity
Fatal.
Detailed Description
For Scantlings by Volume to support different thickness values, a new persistent property is added.
419
Possible Cause
Database changes have occurred, and the migration to a higher version was not done or else failed.
Possible Impacts
New functionality will be unavailable. Attempts to use the Scantlings by Volume functionality will fail.
Severity
Fatal.
Detailed Description
A detailed description of the problem is not currently available.
Possible Cause
The cause of this problem is unknown.
Possible Impacts
The functionality of Ship Drawings will be impaired.
420
Severity
Fatal.
Detailed Description
A detailed description of the problem is not currently available.
Possible Cause
The cause of this problem is unknown.
Possible Impacts
You will be unable to create a Shell Expansion Mesh for the Plate.
Severity
Fatal.
Detailed Description
A new relation with IJPlateGeometry is added to the Shell Expansion AE, replacing the relation with IJPlate. The migration of a Version 6 database to Version 6.1 adds this relation in the place of the old relation.
Possible Cause
Version migration does not occur properly.
Possible Impacts
The functionality of shell expansion drawings in Ship Drawings will not work.
421
Severity
Fatal.
Detailed Description
The Catalog database does not contain the tables for the different active entities of the Ship Drawings task. You can use a DB Integrity script to check the Catalog database. When this script is run on the existing Catalog, if any of the tables does not exist, the software reports errors and associated information such as severity, action, and so forth. The script also provides a fix, an SQL file, to create the missing tables.
Possible Cause
The CatalogDB.dat file delivered with the software does not contain the Ship Drawings tables.
Possible Impacts
During the migration process, errors might be generated while the Catalog is being upgraded.
422
Severity
Fatal.
Detailed Description
A detailed description of the problem is not currently available.
Possible Cause
The cause of this problem is unknown.
Possible Impacts
The functionality of Ship Drawings will be impaired.
Severity
Fatal.
Detailed Description
A detailed description of the problem is not currently available.
Possible Cause
The cause of this problem is unknown.
Possible Impacts
The functionality of Ship Drawings will be impaired.
423
Severity
Fatal.
Detailed Description
A detailed description of the problem is not currently available.
Possible Cause
The cause of this problem is unknown.
Possible Impacts
The functionality of Ship Drawings will be impaired.
Severity
High.
Detailed Description
There is a Permission Group for Ship Drawings objects. This object should be in the Ship Drawings Permission Group, but it is not.
Possible Cause
The object may have been created prior to the creation of the Ship Drawings Permission Group.
Possible Impacts
Unknown.
424
425
426
SECTION 23
Severity
High.
Detailed Description
A MoldedConventionPlatePort object lost its relation with a MoldedConventionPlatePosition object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
427
Severity
High.
Detailed Description
A MoldedConventionPlatePosition object lost its relation with MoldedConventionSpec.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
428
Severity
High.
Detailed Description
A MoldedConventionSpec object is missing its relation with a MoldedFormSpec object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
The software displays an error message when you try to change MoldedConventions (Thickness Direction, PlatePosition, Primary Orientation, Secondary Orientation, and so forth) of Plate Systems on their Properties dialog boxes.
429
Severity
High.
Detailed Description
A ProfileMoldedConvention object lost its relation with a MoldedConventionPlatePort object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
430
SECTION 24
Structural Analysis
This section contains Structural Analysis database integrity messages.
Severity
Crucial.
Detailed Description
Analysis Model has more than one boundary condition folder.
Possible Cause
If two or more boundary condition folders exist under a single analysis model, the relationship between the boundary condition folder and its analysis model is not accessible. Failure to access this folder will not be detected when a new boundary condition is created, resulting in the creation of a second boundary condition folder.
Possible Impacts
During the operation of exporting the analysis model, the software may fail to detect that the boundary conditions under the additional folders are actually associated to the analysis model. The software will not export these boundary conditions.
431
Structural Analysis
Severity
Crucial.
Detailed Description
Analysis Model has more than one load combination folder.
Possible Cause
If two or more load combination folders exist under a single analysis model, the relationship between the load combination folder and its analysis model is not accessible. Failure to access this folder will not be detected when a new load combination is created, resulting in the creation of a second load combination folder.
Possible Impacts
During the operation of exporting the analysis model, the software may fail to detect that the load combinations under the additional folders are actually associated to the analysis model. The software will not export these load combinations to the analysis export file.
432
Structural Analysis
Severity
Crucial.
Detailed Description
Analysis Model has more than one member folder.
Possible Cause
When the filter associated with the Analysis Model is applied, the members are associated to the analysis model's member folder. If the member folder relationship to the Analysis Model is inaccessible at the time the filter is applied, the software may 1) create another member folder under the Analysis Model and 2) associate the members to this new member folder instead of the existing one.
Possible Impacts
Exporting the analysis model to analysis will likely fail, and the output members to the analysis export file may contain the incorrect set of members.
Severity
Fatal.
Detailed Description
Analysis Model is missing its association to the model.
433
Possible Impacts
The Analysis Model is no longer valid and must be removed. It is likely that there are no visual clues that the Analysis Model exists because it will not appear on the Analysis tab of the Workspace Explorer.
Severity
Normal.
Detailed Description
Analysis Model is missing its boundary condition folder.
Possible Cause
It is unknown how the boundary condition folder may have gotten removed because the user has no direct means of deleting one of these folders without deleting the parent Analysis Model.
Possible Impacts
No impact. Users are not required to have boundary conditions; therefore, no boundary condition folder implies that no boundary conditions were defined.
434
Structural Analysis
Severity
Normal.
Detailed Description
Analysis Model is missing its load combination folder.
Possible Cause
It is unknown how the load combination folder may have gotten removed because the user has no direct means of deleting one of these folders without deleting the parent Analysis Model.
Possible Impacts
No impact. Users are not required to have load combinations; therefore, no load combination folder implies that no load combinations were defined.
Severity
Normal.
Detailed Description
Analysis Model is missing its member folder.
Possible Cause
It is unknown how the member folder may have gotten removed because the user has no direct means of deleting one of these folders without deleting the parent Analysis Model.
Possible Impacts
No impact. Users are not required to have members associated to an Analysis Model; therefore, no member folder implies that no members are associated to this Analysis Model.
435
Severity
Crucial.
Detailed Description
A boundary condition, load combination, or member folder does not have an associated Analysis Model. Or, a load case folder or unassigned members folder does not have an association to the model.
Possible Cause
It is not known what may have caused this situation. Normally, when an Analysis Model or plant or ship model is removed, the folders are removed too. The permissions on the parent Analysis Model or plant or ship model will match those of its associated folders; therefore, one cannot delete the parent of an analysis folder without deleting the folders themselves.
Possible Impacts
The folder and its contents are orphaned and will not be visible in any of the provided views. These folders have no parents; therefore, they cannot be loaded into the workspace and will not affect any of the analysis operations including export.
436
Structural Analysis
Severity
Normal.
Detailed Description
Boundary conditions are normally related to the ends of member parts. However, this particular boundary condition has no such relation.
Possible Cause
It is likely that this boundary condition is on the To Do List. Its associated member part was removed, but the boundary condition could not be removed because the user removing the member part lacked permission to remove the boundary condition too.
Possible Impacts
Unknown.
Severity
Crucial.
Detailed Description
The name of a boundary condition may be defined by the user or generated by a naming rule. If a naming rule generates the name, only one naming rule can be assigned to the boundary condition.
437
Possible Impacts
Unknown.
Severity
Crucial.
Detailed Description
The name of a load may be defined by the user or generated by a naming rule. If a naming rule generates the name, only one naming rule can be assigned to the load.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
Crucial.
Detailed Description
The name of a load case may be defined by the user or generated by a naming rule. If a naming rule generates the name, only one naming rule can be assigned to the load case.
438
Possible Impacts
The Structural Analysis task will not be affected by these additional naming rules except that the name of the load case will not be generated correctly, resulting in load cases with the same name. Warning messages will be logged to the export log if an attempt is made to export these load cases during an export model operation; hence, third-party structural analysis packages will not be able to accept two or more load cases with the same name.
Severity
Crucial.
Detailed Description
The name of a load combination may be defined by the user or generated by a naming rule. If a naming rule generates the name, only one naming rule can be assigned to the load combination.
Possible Cause
Unknown.
Possible Impacts
Unknown.
439
Structural Analysis
Severity
Crucial.
Detailed Description
The name of an analysis model may be defined by the user or generated by a naming rule. If a naming rule generates the name, only one naming rule can be assigned to the analysis model.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
High.
Detailed Description
A one-to-one relationship exists between a load and a load case; therefore, a load cannot be associated to two or more load cases.
Possible Cause
During the editing of a load, a different load case was selected to be assigned to the load without the software removing the original load case association. This failure to remove the original relationship was undetected during the edit, and the operation was completed successfully.
Possible Impacts
It is unknown what impact this situation will have on the edit commands because the commands that operate on loads expect only one associated load case. The Export Analytical Model command would either fail or produce an incorrect output file.
440
Severity
High.
Detailed Description
A load has a single parent member that governs its position; therefore, a load that is associated to more than one member is ambiguous.
Possible Cause
It is unknown what could cause such a condition because the edit command for a load fails if such a condition is established.
Possible Impacts
The edit load command will fail, and the export of the analysis model will fail too.
Severity
High.
Detailed Description
Load cases have a parent load case folder assigned to a plant or ship model. A load case cannot exist in the model without this association to this load case folder.
441
Possible Impacts
The load case will be ignored; hence, the loads associated to the load case will also be ignored.
Load combination has a factor to a load case that does not exist
Message
Load combination has a factor to a load case that does not exist.
Severity
High.
Detailed Description
A load combination is comprised of load case and factor pairs. In this instance, there is a factor but no load case.
Possible Cause
The load combinations control the permissions on the factors associated to the load cases. If a load case is deleted but the permissions on the load combination do not allow the modification of the load combination, it will result in the load combination appearing on the To Do List with a factor to a non-existent load case.
Possible Impacts
The load combination cannot be exported to analysis until this problem is corrected.
442
Structural Analysis
Severity
Normal.
Detailed Description
The load combination does not have any load cases added to it.
Possible Cause
Load cases which were previously added to the load combination have been deleted.
Possible Impacts
No impacts to the user.
Severity
Normal.
Detailed Description
A concentrated load is not allowed to have a magnitude of 0, and a distributed load is not allowed to have both end magnitudes of 0.
Possible Cause
The user interface will not allow load magnitudes to be zero (except for one end of a varying load); therefore, code outside of the software would have had to set the load magnitudes to 0.
Possible Impacts
None. The load is simply ignored.
443
Structural Analysis
Severity
Normal.
Detailed Description
A load exists without being associated to a member part.
Possible Cause
This situation can be caused by a user having access rights to remove a member but no access rights to remove its loads. The member part is deleted, and the load appears in the To Do List.
Possible Impacts
None. The load is simply ignored.
Severity
Normal.
Detailed Description
A load exists but does not have an associated load case.
Possible Cause
When deleting a load case, the software did not remove all the loads associated to a load case. The loads are listed on the To Do List as loads without a load case.
Possible Impacts
Loads will not update graphically until they are assigned a valid load case. Also, these loads will be ignored for the analysis export.
444
Severity
High.
Detailed Description
Relative positioned, concentrated, and distributed loads must be positioned along a member such that the fractional distance along the member can only be a value greater than or equal to 0 and less than or equal to 1.
Possible Cause
Unknown.
Possible Impacts
The load will be ignored when exporting the analysis model.
Multiple boundary conditions are assigned to the same end of a member part
Message
Multiple boundary conditions are assigned to the same end of a member part.
Severity
High.
Detailed Description
Only one boundary condition can exist at the end of a member part; however, a particular member part has two or more boundary conditions assigned.
Possible Cause
The most likely cause of this problem is a copy and paste operation, which does not prevent multiple boundary conditions from being pasted to the end of a member part.
445
Severity
High.
Detailed Description
More than one load case folder exists under the model node.
Possible Cause
Unknown.
Possible Impacts
The Export Analytical Model command will not export the load cases correctly because it will only recognize one of the load case folders.
446
Structural Analysis
Severity
High.
Detailed Description
More than one unassigned members folder exists under the model node.
Possible Cause
Two users simultaneously created the first analysis models, and two unassigned member folders were created.
Possible Impacts
Members with loads but not assigned to analysis models will appear beneath one or the other unassigned member folders. It will most likely just cause confusion as to which folder a member will appear under. This situation should not impact the software in any way.
447
Structural Analysis
448
SECTION 25
Structural Detailing
This section contains Structural Detailing database integrity messages.
Severity
Crucial.
Detailed Description
A Stand Alone Beam Part has no Geometry associated to it: Missing BeamPartProfileGeometry relationship to BeamStandAlonePart_AE for standalone BeamPart.
Possible Cause
Unknown.
Possible Impacts
Object will not display or highlight. The weight and center of gravity (CG) may not be calculated and will be invalid.
449
Structural Detailing
Severity
Crucial.
Detailed Description
A beam part does not have GUID beam part orientation relationship: Missing the GUIDBeamPartOrientation relationship to BeamStandAlonePart_AE for standalone BeamPart.
Possible Cause
Unknown.
Possible Impacts
The user cannot manipulate the object itself or other objects related to it. The weight and center of gravity (CG) may not be calculated and will be invalid.
Severity
Fatal.
Detailed Description
A collar part does not have the assembly membersR relationship: Missing the AssemblyMembersR relationship to StructPhysicalConnection for CollarPart.
Possible Cause
Unknown.
450
Severity
Fatal.
Detailed Description
A collar part does not have the collar defining data relation: Missing the CollarDefiningData relationship between the CollarPart and its CreateCollar_AE.
Possible Cause
Unknown.
Possible Impacts
Unknown.
451
Structural Detailing
Severity
Fatal.
Detailed Description
A collar part does not have the collar plate data relation: Missing the CollarPlateData relationship between the Collar Part and its CreateCollar_AE.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
Crucial.
Detailed Description
A collar part is missing its geometry. A create collar active entity (AE) does not have a related plate part geometry: Missing the GeometryGeneration_RSLT1 relationship between the CreateCollar_AE and its resultant PlatePartGeometry.
452
Possible Impacts
The object will not display or highlight. The weight and center of gravity (CG) may not be calculated and will be invalid.
Severity
Crucial.
Detailed Description
A Plate Part Geometry is missing a relationship to an Active Entity. The Geometry exists but is not related to an SDCutAE, PlateFinalTrim_AE, ChamferCut_AE, GeneratePlatePart_AE, PlateStrakingSplit_AE via the StructOperation_RSLT1 relationship.
Possible Cause
Unknown.
Possible Impacts
Unknown.
453
Structural Detailing
Severity
Crucial.
Detailed Description
A plate straking split active entity (AE) does not have a surface body: Missing the StructOperation_RSLT2 relationship to SurfaceBody2 for PlateStrakingSplit_AE.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
A StandAlone EdgeReinforcementProfilePart or a StandAloneStiffenerPart is missing its Cross Section information on its IJDProfileSection interface: Missing the SDInputGeometry relationship to ProfilePartCreation for standalone EdgeReinforcementProfilePart, StandAloneStiffenerPart.
Possible Cause
Unknown.
Possible Impacts
The object will not display or highlight.
454
Structural Detailing
The weight and center of gravity (CG) may not be calculated and will be invalid.
Severity
Fatal.
Detailed Description
A profile part does not have a related generate plate part active entity (AE): Missing the TrimGeometry relationship to GeneratePlatePart_AE for standalone EdgeReinforcementProfilePart.
Possible Cause
Unknown.
Possible Impacts
The edge reinforcement will not be manageable.
455
Structural Detailing
Severity
Fatal.
Detailed Description
A profile part does not have a related profile part geometry: Missing the StructToGeometry relationship to ProfilePartGeometry for detailed StiffenerPart, detailed and standalone BeamPart, detailed and standalone EdgeReinforcementProfilePart, StandAloneStiffenerPart.
Possible Cause
Unknown.
Possible Impacts
The object will not display or highlight. The weight and center of gravity (CG) may not be calculated and will be invalid.
Severity
Crucial.
Detailed Description
A profile part creation does not have a related profile part path: Missing the InputLandingCurve relationship to ProfilePartPath for ProfilePartCreation. The StandAlone ProfilePart does not have geometry.
456
Possible Impacts
The object will not display or highlight. The weight and center of gravity (CG) may not be calculated and will be invalid.
Severity
Fatal.
Detailed Description
A profile part creation does not have a related profile part geometry: Missing the GeometryGeneration_RSLT1 relationship to ProfilePartGeometry for ProfilePartCreation.
Possible Cause
Unknown.
Possible Impacts
The object will not display or highlight. The weight and center of gravity (CG) may not be calculated and will be invalid.
457
Structural Detailing
Severity
Fatal.
Detailed Description
A profile part path (a landing curve) does not have a related profile part creation: Missing the InputLandingCurve relationship to ProfilePartCreation for ProfilePartPath.
Possible Cause
Unknown.
Possible Impacts
The edge reinforcement will not be manageable. Deleting this object should have no impact.
Severity
Crucial.
Detailed Description
The profile is not being trimmed properly.
Possible Cause
Unknown.
458
Severity
Crucial.
Detailed Description
A Sketch feature does not have an OutputColl: Missing the FromOutputColltoOutputs relationship to OutputColl for SketchFeature.
Possible Cause
Unknown.
Possible Impacts
Unknown.
459
Structural Detailing
Severity
Fatal.
Detailed Description
A SmartPlate does not have a related create platePart active entity (AE): Missing the PlateDefiningData relationship between the SmartPlate and its CreatePlatePart_AE.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
High.
Detailed Description
A straking seam does not have a related straking split active entity (AE). Possible situations: Missing the StructSplit_OPER1 relationship to PlateStrakingSplit_AE for straking seams. Missing the StructSplit_OPER1 relationship to ProfileStrakingSplit_AE for straking seam point.
Possible Cause
Unknown.
460
Severity
Fatal.
Detailed Description
A StructFeature or Sketch Feature should either be related to a Cut operator (the SDCutAE via the SDCut_OPER1) or to a Trim operator (the ProfileTrim_AE via the ProfileTrim_OPER1): Missing the SDCut_OPER1 relationship to SDCutAE or ProfileTrim_OPER1 for StructFeature, SketchFeature.
Possible Cause
Unknown.
Possible Impacts
The object will not display or highlight. The weight and center of gravity (CG) may not be calculated and will be invalid.
461
Structural Detailing
Severity
High.
Detailed Description
SplitPoint Active entity with no Physical connections as input (nothing to split): Missing the PhysicalConnectionToSplit relationship to IJStructGeometry for IJSplitPoint_AE. Physical Connection Active Entity with no Physical Connections as input: Missing StructOperation_OPRND to IJPhyConSplitEntity for IJStructGeometry.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
An active entity (AE) does not have a part. Missing the StructOperation_OPRND relationship to PlatePart for PlateStrakingSplit_AE. Missing the StructOperation_OPRND relationship to StiffenerPart for ProfileStrakingSplit_AE.
Possible Cause
Unknown.
462
Severity
Fatal.
Detailed Description
An active entity (AE) does not have a related part geometry. Missing the StructOperation_RSLT1 relationship to ProfilePartGeometry for ProfileTrim_AE, ProfileStrakingSplit_AE. Missing StructOperation_RSLT1 relationship to PlatePartGeometry for PlateStrakingSplit_AE Missing Part Geometry for the Cut Operation Missing StructOperation_RSLT1 relationship to (PlatePartGeometry, ProfilePartGeometry) for SDCutAE Missing the StructOperation_OPRND relationship to ProfilePartGeometry for ProfileTrim_AE. The ProfileTrim AE does not have the ProfilePart Geometry as input via the StructOperation_OPRND.
Possible Cause
Unknown.
Possible Impacts
The object will not display or highlight. The weight and center of gravity (CG) may not be calculated and will be invalid.
463
Structural Detailing
Severity
Fatal.
Detailed Description
A StandAlone PlatePart or a SmartPlate is missing its CreatePlatePartAE: Missing the CreatePlatePart_OPRND relationship to CreatePlatePart_AE for Standalone Plate part, SmartPlate.
Possible Cause
Unknown.
Possible Impacts
The object will not display or highlight. The weight and center of gravity (CG) may not be calculated and will be invalid.
Severity
Fatal.
Detailed Description
An object does not have a related DReferences collection. Missing the ReferencesCollectionToSymbolRelation relationship to DReferencesCollection for SmartPlate, CollarPart, StructFeature, StructPhysicalConnection. Missing relationship to symbol for StandAlonePlateParts, Features, and Physical Connections.
464
Possible Impacts
The object will not display or highlight. The weight and center of gravity (CG) may not be calculated and will be invalid.
Severity
Fatal.
Detailed Description
A Detailed PlatePart, StandAlonePlatePart, SmartPlate, or a CollarPart is missing a relationship to its geometry: Missing the StructToGeometry relationship to PlatePartGeometry for StandalonePlatePart, SmartPlate, CollarPart, and detailed plate part. In some instances, the part exists with no other relationship. In this case, the part should be deleted.
Possible Cause
Unknown.
Possible Impacts
The object will not display or highlight. The weight and center of gravity (CG) may not be calculated and will be invalid.
465
Structural Detailing
2. Supply all information possible that may have led to this situation, and submit this information along with the backup to SmartMarine 3D Support. 3. Delete the object using one of the following methods: Select the object in the Workspace Explorer, and delete it. Run the Clean Database custom command to delete the object.
Severity
Fatal.
Detailed Description
A cut operation is missing required input geometry: Missing the StructOperation_OPRND relationship to (PlatePartGeometry, ProfilePartGeometry) for SDCutAE.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
An Edge treatment exists, but it is not related to an edge, and therefore needs to be deleted.
466
Possible Impacts
Unknown.
Severity
High.
Detailed Description
An Edge treatment exists, but it has zero length. You should either delete or modify the edge treatment.
Possible Cause
Unknown.
Possible Impacts
Unknown.
467
Structural Detailing
Severity
High.
Detailed Description
Physical connection Active Entity does not have any outputs: Missing XStructOperation_RSLT1 relationship to IJPhyConSplitEntity for IJStructGeometry.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
High.
Detailed Description
Physical connection Active Entity does not have a Split point or Seam as input: Missing StructSplit_OPER1 relationship to IJGeometry for IJPhyConSplitEntity.
Possible Cause
Unknown.
Possible Impacts
Unknown.
468
Severity
Crucial.
Detailed Description
A physical connection has multiple symbols.
Possible Cause
Unknown.
Possible Impacts
The user may not be able to open the Properties dialog box for the physical connection. Cannot manufacture the corresponding part.
Severity
Crucial
Detailed Description
A physical connection only has one symbol, and it is a dummy symbol associated with a dummy selection rule.
469
Possible Impacts
The user will not be able to open the Properties dialog box for the physical connection. Cannot manufacture the corresponding part.
Severity
High.
Detailed Description
SplitPoint Active entity with no outputs (SplitPoint): Missing the GeomGenRSLT1 relationship for IJSplitPoint_AE.
Possible Cause
Unknown.
Possible Impacts
Unknown.
470
Structural Detailing
Severity
High.
Detailed Description
SplitPoint Active entity with no Reference Face as input: Missing the ReferenceFace relationship for IJSplitPoint_AE.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
Crucial.
Detailed Description
Split Point not related to an Active Entity: Missing the GeomGenRSLT1 relationship for IJSplitPoint_AE.
Possible Cause
Unknown.
Possible Impacts
Unknown.
471
Severity
High.
Detailed Description
There is a Permission Group for Struct Detailing objects. This object should be in the Struct Detail Permission Group, but it is not.
Possible Cause
The object may have been created prior to the creation of the Struct Detail Permission Group.
Possible Impacts
Unknown.
472
Structural Detailing
Severity
Normal.
Detailed Description
Flavors allow an object to have different symbolic display geometries. In the case of assembly connections, free end cuts, and hole Smart Occurrences, there is no symbolic display stored; the display is geometrically available. Note that the bulkload files for these classes lack symbols. Therefore, these objects can relate to the same flavor. Currently, there are tens of thousands of flavors in the database for these objects. The software can exhibit performance issues when users work with objects dealing with flavors, for example, during a copy-paste operation. The goal is to minimize the number of flavors for the classes noted. This goal can be accomplished by running the Database > Integrity command (full check) and then running the Clean Database custom command.
Possible Cause
The software created a unique flavor for each instance of an assembly connection, free end cut, or hole Smart Occurrence.
Possible Impacts
The primary impact of this problem is in the performance of the software.
473
Structural Detailing
474
SECTION 26
Structural Manufacturing
This section contains Structural Manufacturing database integrity messages.
Severity
Fatal.
Detailed Description
An Assembly margin does not have an Assembly, although the Assembly Margin is a child of the Assembly.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
An Assembly Margin parent does not have an Assembly margin child.
475
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
The BuiltUp Profile Nestdata does not have a MfgProfile.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Unknown.
Severity
High.
Detailed Description
The UpToDate column in the StrMfgUpdateInfo table is incorrect.
476
Possible Impacts
Cannot support more statuses for manufacturing objects.
Severity
Fatal.
Detailed Description
An Input-Added MfgPin does not have a PinJig active entity through the 'InputAddedMfgPin' relation.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Unknown.
477
Structural Manufacturing
Severity
Crucial
Detailed Description
The manufacturing object does not have any parent, and it is left as an orphan in the model database. When this object is seen in the workspace navigator, it is hooked parallel to the project configuration root instead of the corresponding plate part or profile part.
Possible Cause
Unknown
Possible Impacts
The manufacturing object is left in the work space as an orphan, and it is difficult to modify. The object might not be considered as manufacturing data if it is margin, marking, or shrinkage.
This command displays a dialog box that lists the objects in error.
2. From the list, select the objects and repair them by clicking Clean Now.
Severity
High.
Detailed Description
Manufacturing definitions, which include CAssyMarginChild, CConstMargin, CMfgDefinition, CMfgMarkingLinesData, CMfgWeldCompensation, CObliqueMargin, CPositionShr, CScalingShr, CTemplateControlLine, and CTemplateLocationMark, do not have a port.
Possible Cause
Unknown.
Possible Impacts
Unknown.
478
Severity
Fatal.
Detailed Description
Manufacturing objects do not have a parent.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
Severity
Crucial.
Detailed Description
Manufacturing SmartOccurrence objects, which include CMfgPlateMarkingSettings, CMfgPlateProcessSettings, CMfgProfileMarkingSettings, CMfgProfileProcessSettings, CMfgTemplateMarkingSettings, and CMfgTemplateProcessSettings, are not connected to part input StructMfgSymbolInput relation.
Possible Cause
Coding or data model propagation errors.
479
Severity
High.
Detailed Description
Marking Lines active entity does not have a reference object as input.
Possible Cause
Unknown.
Possible Impacts
The related business object display does not correspond to its real geometrical state.
Severity
Fatal.
Detailed Description
Marking Lines active entity does not have any output.
Possible Cause
Unknown.
480
Severity
Fatal.
Detailed Description
Marking line active entity does not have a detailed part as input.
Possible Cause
Unknown.
Possible Impacts
The related business object display does not correspond to its real geometrical state.
Severity
Fatal.
Detailed Description
Marking line does not have a Parent.
Possible Cause
Coding or data model errors.
481
Severity
Fatal.
Detailed Description
A Manufacturing Bevel object does not have a Geom2D.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
A MfgHitachi object does not have a MfgPlatePart.
Possible Cause
Coding or data model errors in an earlier version.
482
Severity
Fatal.
Detailed Description
A MfgPlateCreation active entity does not have a DetailPlatePart as input.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
A MfgPlateCreation active entity does not have a SmartOccurrence object.
483
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
A MfgPlateMarking Settings object does not have a MfgPlateCreation active entity through the 'MfgPlateSettingsInput' relation.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Unknown.
484
Structural Manufacturing
Severity
Fatal.
Detailed Description
A MfgPlatePart active entity does not have a MfgPlatePart.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
A MfgPlatePart does not have a MfgPlatePart active entity.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Unknown.
485
Structural Manufacturing
Severity
Fatal.
Detailed Description
A MfgPlateProcess Settings object does not have a MfgPlateCreation active entity through the 'MfgPlateSettingsInput' relation.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
A MfgProfile Part does not have a MfgProfileCreation active entity.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Unknown.
486
Severity
Fatal.
Detailed Description
A MfgProfileCreation active entity does not have a DetailPlate Part as Input.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
A MfgProfileCreation active entity does not have a MfgProfilePart.
Possible Cause
Coding or data model errors in an earlier version.
487
Severity
Fatal.
Detailed Description
A MfgProfileCreation active entity does not have a SmartOccurrence object.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
A MfgProfileMarking Settings object does not have a MfgProfileCreation active entity through the 'MfgProfileSettingsInput' relation.
488
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
A MfgProfileProcess Settings object does not have a MfgProfileCreation active entity through the 'MfgProfileSettingsInput' relation.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Unknown.
489
Structural Manufacturing
Severity
Fatal.
Detailed Description
Oblique margin does not have a port.
Possible Cause
Coding or data model errors.
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
A PinJig active entity does not have an Input-Supported plate.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Unknown.
490
Structural Manufacturing
Severity
Fatal.
Detailed Description
A PinJig active entity does not have an output Jig.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Unknown.
PinJig active entity does not have Seams with 'ButtAndSeam' relation
Message
PinJig active entity does not have Seams with 'ButtAndSeam' relation.
Severity
Fatal.
Detailed Description
A PinJig active entity does not have Seams with the 'ButtAndSeam' relation.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Unknown.
491
Severity
High.
Detailed Description
Shrinkage Active entity does not have a plate part as input.
Possible Cause
Unknown.
Possible Impacts
The related business object display does not correspond to its real geometrical state.
Severity
Fatal.
Detailed Description
Shrinkage might have been applied without any shrinkage input values.
Possible Cause
Coding or data model errors.
Possible Impacts
Unknown.
492
Severity
High.
Detailed Description
Shrinkage object exists without a Primary Axis.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
Severity
High.
Detailed Description
Shrinkage object exists without a Primary port.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
The primary port object will not be seen in a graphic view.
493
Severity
High.
Detailed Description
Shrinkage object exists without a Secondary Axis.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
Severity
High.
Detailed Description
Shrinkage exists without a Secondary port.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
The Secondary port object will not be seen in a graphic view.
494
Severity
Fatal.
Detailed Description
A Shrinkage object has a non-zero secondary factor but no secondary direction.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
Shrinkage output does not have an active entity.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Unknown.
495
Severity
Fatal.
Detailed Description
System marks do not have a relation to MfgGeom3d or MfgGeom2d.
Possible Cause
Coding or data model errors.
Possible Impacts
Unknown.
Severity
High.
Detailed Description
System marks are on the 2D relation but do not have MfgGeom2d.
Possible Cause
Coding or data model errors.
496
Severity
High.
Detailed Description
System marks are on the 3d relation but do not have MfgGeom3d.
Possible Cause
Coding or data model errors.
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
A Template active entity does not have an Input Sketching Plane through the 'InputSketchingPlane' relation.
497
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
Template object exists without output.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
The Template object will not be seen in a graphic view.
Severity
Fatal.
Detailed Description
Template object exists without plate input.
498
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
Template object exists without Process and Marking tabs in the settings.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
A Template has an invalid child.
499
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
TemplateMarking Settings do not have an active entity.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
TemplateProcess Settings do not have an active entity.
500
Possible Impacts
Unknown.
Severity
Fatal.
Detailed Description
A Template does not have an associated active entity, although the Template is the output of an active entity.
Possible Cause
Coding or data model errors in an earlier version.
Possible Impacts
Unknown.
501
Structural Manufacturing
Severity
High.
Detailed Description
There is a Permission Group for Structural Manufacturing objects. This object should be in the Structural Manufacturing Permission Group, but it is not.
Possible Cause
The object may have been created prior to the creation of the Structural Manufacturing Permission Group.
Possible Impacts
Unknown.
502
Structural Manufacturing
Manufacturing parts under Plate part or Profile part do not have same Permission Group (on page 509) MarkingLineData's Approval Status does not match with Marking Line's Approval Status (on page 510) MarkingLineData's Permission Group does not match with Marking Line's Permission Group (on page 510) MfgBevel object's Approval Status does not match with MfgPlate/MfgProfile's Approval Status (on page 511) MfgBevel object's Permission Group does not match with MfgPlate/MfgProfile's Permission Group (on page 511) MfgDefinition's Approval Status does not match with Pin Jig's Approval Status (on page 512) MfgDefinition's Permission Group does not match with Pin Jig's Permission Group (on page 512) MfgGeneralHitachi's Approval Status does not match with MfgPlatePart's Approval Status (on page 513) MfgGeneralHitachi's Permission Group does not match with MfgPlatePart's Permission Group (on page 514) MfgGeomchild's Approval Status does not match with MfgGeomParent's Approval Status (on page 514) MfgGeomchild's Permission Group does not match with MfgGeomParent's Permission Group (on page 515) MfgNestData object's Approval Status does not match with MfgProfilePart's Approval Status (on page 515) MfgNestData object's Permission Group does not match with MfgProfilePart's Permission Group (on page 516) MfgSystemMark3D object's Approval Status does not match with MfgProfile's Approval Status (on page 516) MfgSystemMark3D object's Permission Group does not match with MfgProfile's Permission Group (on page 517) Pin Jig active entity's Approval Status does not match with Pin Jig's Approval Status (on page 518) Pin Jig active entity's Permission Group does not match with Pin Jig's Permission Group (on page 518) Plate creation active entity's Approval Status does not match with MfgPlatePart's Approval Status (on page 519) Plate creation active entity's Permission Group does not match with MfgPlatePart's Permission Group (on page 519) Profile creation active entity's Approval Status does not match with MfgProfilePart's Approval Status (on page 520) Profile creation active entity's Permission Group does not match with MfgProfilePart's Permission Group (on page 520) Shrinkage active entity's Approval Status does not match with Shrinkage's Approval Status (on page 521) Shrinkage active entity's Permission Group does not match with Shrinkage's Permission Group (on page 522) Sketch Template Line Symbol's Approval Status does not match with Template's Approval Status (on page 522) Sketch Template Line Symbol's Permission Group does not match with Template's Permission Group (on page 523) SmartOccurrence object's Approval Status does not match with MfgPlatePart's Approval Status (on page 523) SmartOccurrence object's Approval Status does not match with MfgProfilePart's Approval Status (on page 524) SmartOccurrence object's Approval Status does not match with Template's Approval Status (on page 524)
503
Structural Manufacturing
SmartOccurrence object's Permission Group does not match with MfgPlatePart's Permission Group (on page 525) SmartOccurrence object's Permission Group does not match with MfgProfilePart's Permission Group (on page 526) SmartOccurrence object's Permission Group does not match with Template's Permission Group (on page 526) Symbol's Approval Status does not match with Marking Line's Approval Status (on page 527) Symbol's Permission Group does not match with Marking Line's Permission Group (on page 527) SystemMark2D object's Approval Status does not match with MfgProfile's Approval Status (on page 528) SystemMark2D object's Permission Group does not match with MfgProfile's Permission Group (on page 528) Template active entity's Approval Status does not match with Template's Approval Status (on page 529) Template active entity's Permission Group does not match with Template's Permission Group (on page 530)
See Also
Understanding Database Integrity (on page 31)
Added Pin's Approval Status does not match with Pin Jig's Approval Status
Message
Added Pin's Approval Status does not match with Pin Jig's Approval Status.
Severity
Crucial.
Detailed Description
The approval status of the Added Pin object does not match the approval status of the Pin Jig object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
504
Structural Manufacturing
Added Pin's Permission Group does not match with Pin Jig's Permission Group
Message
Added Pin's Permission Group does not match with Pin Jig's Permission Group.
Severity
Crucial.
Detailed Description
The permission group of the Added Pin object does not match the permission group of the Pin Jig object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
Assembly margin child's Approval Status does not match with Assembly Margin's Approval Status
Message
Assembly margin child's Approval Status does not match with Assembly Margin's Approval Status.
Severity
Crucial.
Detailed Description
The approval status of the Assembly margin child object does not match the approval status of the Assembly Margin object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
505
Assembly margin child's Permission Group does not match with Assembly Margin's Permission Group
Message
Assembly margin child's Permission Group does not match with Assembly Margin's Permission Group.
Severity
Crucial.
Detailed Description
The permission group of the Assembly margin child object does not match the permission group of the Assembly Margin object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
Base Control Line Symbol's Approval Status does not match with Template's Approval Status
Message
Base Control Line Symbol's Approval Status does not match with Template's Approval Status.
Severity
Crucial.
Detailed Description
The approval status of the Base Control Line Symbol object does not match the approval status of the Template object.
Possible Cause
Coding or data model propagation errors.
506
Base Control Line Symbol's Permission Group does not match with Template's Permission Group
Message
Base Control Line Symbol's Permission Group does not match with Template's Permission Group.
Severity
Crucial.
Detailed Description
The permission group of the Base Control Line Symbol does not match the permission group of the Template object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
Base plane's Approval Status does not match with Template's Approval Status
Message
Base plane's Approval Status does not match with Template's Approval Status.
Severity
Crucial.
Detailed Description
The approval status of the Base plane object does not match the approval status of the Template object.
507
Possible Impacts
Unknown.
Base plane's Permission Group does not match with Template's Permission Group
Message
Base plane's Permission Group does not match with Template's Permission Group.
Severity
Crucial.
Detailed Description
The permission group of the Base plane object does not match the permission group of the Template object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
508
Structural Manufacturing
Manufacturing parts under Plate part or Profile part do not have same Approval Status
Message
Manufacturing parts under Plate part or Profile part do not have same Approval Status.
Severity
Crucial.
Detailed Description
The manufacturing parts under the plate part or profile part do not the same approval status.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
Manufacturing parts under Plate part or Profile part do not have same Permission Group
Message
Manufacturing parts under Plate part or Profile part do not have same Permission Group.
Severity
Crucial.
Detailed Description
The manufacturing parts under the plate part or profile part do not have the same permission group.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
509
MarkingLineData's Approval Status does not match with Marking Line's Approval Status
Message
MarkingLineData's Approval Status does not match with Marking Line's Approval Status.
Severity
Crucial.
Detailed Description
The approval status of the MarkingLineData object does not match the approval status of the Marking Line object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
MarkingLineData's Permission Group does not match with Marking Line's Permission Group
Message
MarkingLineData's Permission Group does not match with Marking Line's Permission Group.
Severity
Crucial.
Detailed Description
The permission group of the MarkingLineData object does not match the permission group of the Marking Line object.
Possible Cause
Coding or data model propagation errors.
510
MfgBevel object's Approval Status does not match with MfgPlate/MfgProfile's Approval Status
Message
MfgBevel object's Approval Status does not match with MfgPlate/MfgProfile's Approval Status.
Severity
Crucial.
Detailed Description
The approval status of the MfgBevel object does not match the approval status of the MfgPlate or MfgProfile objects.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
MfgBevel object's Permission Group does not match with MfgPlate/MfgProfile's Permission Group
Message
MfgBevel object's Permission Group does not match with MfgPlate/MfgProfile's Permission Group.
Severity
Crucial.
Detailed Description
The permission group of the MfgBevel object does not match the permission group of the MfgPlate or MfgProfile objects.
511
Possible Impacts
Unknown.
MfgDefinition's Approval Status does not match with Pin Jig's Approval Status
Message
MfgDefinition's Approval Status does not match with Pin Jig's Approval Status.
Severity
Crucial.
Detailed Description
The approval status of the MfgDefinition object does not match the approval status of the Pin Jig object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
512
Structural Manufacturing
MfgDefinition's Permission Group does not match with Pin Jig's Permission Group
Message
MfgDefinition's Permission Group does not match with Pin Jig's Permission Group.
Severity
Crucial.
Detailed Description
The permission group of the MfgDefinition object does not match the permission group of the Pin Jig object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
MfgGeneralHitachi's Approval Status does not match with MfgPlatePart's Approval Status
Message
MfgGeneralHitachi's Approval Status does not match with MfgPlatePart's Approval Status.
Severity
Crucial.
Detailed Description
The approval status of the MfgGeneralHitachi object does not match the approval status of the MfgPlatePart object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
513
MfgGeneralHitachi's Permission Group does not match with MfgPlatePart's Permission Group
Message
MfgGeneralHitachi's Permission Group does not match with MfgPlatePart's Permission Group.
Severity
Crucial.
Detailed Description
The permission group of the MfgGeneralHitachi object does not match the permission group of the MfgPlatePart object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
MfgGeomchild's Approval Status does not match with MfgGeomParent's Approval Status
Message
MfgGeomchild's Approval Status does not match with MfgGeomParent's Approval Status.
Severity
Crucial.
Detailed Description
The approval status of the MfgGeomchild object does not match the approval status of the MfgGeomParent object.
Possible Cause
Coding or data model propagation errors.
514
MfgGeomchild's Permission Group does not match with MfgGeomParent's Permission Group
Message
MfgGeomchild's Permission Group does not match with MfgGeomParent's Permission Group.
Severity
Crucial.
Detailed Description
The permission group of the MfgGeomchild object does not match the permission group of the MfgGeomParent object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
MfgNestData object's Approval Status does not match with MfgProfilePart's Approval Status
Message
MfgNestData object's Approval Status does not match with MfgProfilePart's Approval Status.
Severity
Crucial.
Detailed Description
The approval status of the MfgNestData object does not match the approval status of the MfgProfilePart object.
515
Possible Impacts
Unknown.
MfgNestData object's Permission Group does not match with MfgProfilePart's Permission Group
Message
MfgNestData object's Permission Group does not match with MfgProfilePart's Permission Group.
Severity
Crucial.
Detailed Description
The permission group of the MfgNestData object does not match the permission group of the MfgProfilePart object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
516
Structural Manufacturing
MfgSystemMark3D object's Approval Status does not match with MfgProfile's Approval Status
Message
MfgSystemMark3D object's Approval Status does not match with MfgProfile's Approval Status.
Severity
Crucial.
Detailed Description
The approval status of the MfgSystemMark3D object does not match the approval status of the MfgProfile object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
MfgSystemMark3D object's Permission Group does not match with MfgProfile's Permission Group
Message
MfgSystemMark3D object's Permission Group does not match with MfgProfile's Permission Group.
Severity
Crucial.
Detailed Description
The permission group of the MfgSystemMark3D object does not match the permission group of the MfgProfile object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
517
Pin Jig active entity's Approval Status does not match with Pin Jig's Approval Status
Message
Pin Jig active entity's Approval Status does not match with Pin Jig's Approval Status.
Severity
Crucial.
Detailed Description
The approval status of the Pin Jig active entity does not match the approval status of the Pin Jig.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
Pin Jig active entity's Permission Group does not match with Pin Jig's Permission Group
Message
Pin Jig active entity's Permission Group does not match with Pin Jig's Permission Group.
Severity
Crucial.
Detailed Description
The permission group of the Pin Jig active entity does not match the permission group of the Pin Jig.
Possible Cause
Coding or data model propagation errors.
518
Plate creation active entity's Approval Status does not match with MfgPlatePart's Approval Status
Message
Plate creation active entity's Approval Status does not match with MfgPlatePart's Approval Status.
Severity
Crucial.
Detailed Description
The approval status of the plate creation active entity does not match the approval status of the MfgPlatePart object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
Plate creation active entity's Permission Group does not match with MfgPlatePart's Permission Group
Message
Plate creation active entity's Permission Group does not match with MfgPlatePart's Permission Group.
Severity
Crucial.
Detailed Description
The permission group of the plate creation active entity does not match the permission group of the MfgPlatePart object.
519
Possible Impacts
Unknown.
Profile creation active entity's Approval Status does not match with MfgProfilePart's Approval Status
Message
Profile creation active entity's Approval Status does not match with MfgProfilePart's Approval Status.
Severity
Crucial.
Detailed Description
The approval status of the profile creation active entity does not match the approval status of the MfgProfilePart object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
520
Structural Manufacturing
Profile creation active entity's Permission Group does not match with MfgProfilePart's Permission Group
Message
Profile creation active entity's Permission Group does not match with MfgProfilePart's Permission Group.
Severity
Crucial.
Detailed Description
The permission group of the profile creation active entity does not match the permission group of the MfgProfilePart object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
Shrinkage active entity's Approval Status does not match with Shrinkage's Approval Status
Message
Shrinkage active entity's Approval Status does not match with Shrinkage's Approval Status.
Severity
Crucial.
Detailed Description
The approval status of the Shrinkage active entity does not match the approval status of the Shrinkage object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
521
Shrinkage active entity's Permission Group does not match with Shrinkage's Permission Group
Message
Shrinkage active entity's Permission Group does not match with Shrinkage's Permission Group.
Severity
Crucial.
Detailed Description
The permission group of the Shrinkage active entity does not match the permission group of the Shrinkage object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
Sketch Template Line Symbol's Approval Status does not match with Template's Approval Status
Message
Sketch Template Line Symbol's Approval Status does not match with Template's Approval Status.
Severity
Crucial.
Detailed Description
The approval status of the Sketch Template Line Symbol does not match the approval status of the Template.
Possible Cause
Coding or data model propagation errors.
522
Sketch Template Line Symbol's Permission Group does not match with Template's Permission Group
Message
Sketch Template Line Symbol's Permission Group does not match with Template's Permission Group.
Severity
Crucial.
Detailed Description
The permission group of the Sketch Template Line Symbol does not match the permission group of the Template.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
SmartOccurrence object's Approval Status does not match with MfgPlatePart's Approval Status
Message
SmartOccurrence object's Approval Status does not match with MfgPlatePart's Approval Status.
Severity
Crucial.
Detailed Description
The approval status of the SmartOccurrence object does not match the approval status of the MfgPlatePart object.
523
Possible Impacts
Unknown.
SmartOccurrence object's Approval Status does not match with MfgProfilePart's Approval Status
Message
SmartOccurrence object's Approval Status does not match with MfgProfilePart's Approval Status.
Severity
Crucial.
Detailed Description
The approval status of the SmartOccurrence object does not match the approval status of the MfgProfilePart object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
524
Structural Manufacturing
SmartOccurrence object's Approval Status does not match with Template's Approval Status
Message
SmartOccurrence object's Approval Status does not match with Template's Approval Status.
Severity
Crucial.
Detailed Description
The approval status of the SmartOccurrence object does not match the approval status of the Template object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
SmartOccurrence object's Permission Group does not match with MfgPlatePart's Permission Group
Message
SmartOccurrence object's Permission Group does not match with MfgPlatePart's Permission Group.
Severity
Crucial.
Detailed Description
The permission group of the SmartOccurrence object does not match the permission group of the MfgPlatePart object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
525
SmartOccurrence object's Permission Group does not match with MfgProfilePart's Permission Group
Message
SmartOccurrence object's Permission Group does not match with MfgProfilePart's Permission Group.
Severity
Crucial.
Detailed Description
The permission group of the SmartOccurrence object does not match the permission group of the MfgProfilePart object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
SmartOccurrence object's Permission Group does not match with Template's Permission Group
Message
SmartOccurrence object's Permission Group does not match with Template's Permission Group.
Severity
Crucial.
Detailed Description
The permission group of the SmartOccurrence object does not match the permission group of the Template object.
Possible Cause
Coding or data model propagation errors.
526
Symbol's Approval Status does not match with Marking Line's Approval Status
Message
Symbol's Approval Status does not match with Marking Line's Approval Status.
Severity
Crucial.
Detailed Description
The approval status of the Symbol object does not match the approval status of the Marking Line object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
Symbol's Permission Group does not match with Marking Line's Permission Group
Message
Symbol's Permission Group does not match with Marking Line's Permission Group.
Severity
Crucial.
Detailed Description
The permission group of the Symbol object does not match the permission group of the Marking Line object.
527
Possible Impacts
Unknown.
SystemMark2D object's Approval Status does not match with MfgProfile's Approval Status
Message
SystemMark2D object's Approval Status does not match with MfgProfile's Approval Status.
Severity
Crucial.
Detailed Description
The approval status of the SystemMark2D object does not match the approval status of the MfgProfile object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
528
Structural Manufacturing
SystemMark2D object's Permission Group does not match with MfgProfile's Permission Group
Message
SystemMark2D object's Permission Group does not match with MfgProfile's Permission Group.
Severity
Crucial.
Detailed Description
The permission group of the SystemMark2D object does not match the permission group of the MfgProfile object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
Template active entity's Approval Status does not match with Template's Approval Status
Message
Template active entity's Approval Status does not match with Template's Approval Status.
Severity
Crucial.
Detailed Description
The approval status of the Template active entity does not match the approval status of the Template object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
529
Template active entity's Permission Group does not match with Template's Permission Group
Message
Template active entity's Permission Group does not match with Template's Permission Group.
Severity
Crucial.
Detailed Description
The permission group of the Template active entity does not match the permission group of the Template object.
Possible Cause
Coding or data model propagation errors.
Possible Impacts
Unknown.
530
SECTION 27
Structure
This section contains Structure database integrity messages.
Severity
Crucial.
Detailed Description
Many of the assembly connections require a cutting plane to trim the supported member. When this error occurs, the cutting plane is missing from the assembly connection.
Possible Cause
Unknown.
Possible Impacts
Assembly connection will not compute properly. The connection will not be trimmed or coped to the supporting member.
531
Structure
Severity
Crucial.
Detailed Description
Many of the assembly connections have features to trim or cope the supported member. When this error occurs, the feature is missing from the assembly connection.
Possible Cause
Unknown.
Possible Impacts
Assembly connection will not compute properly. The connection will not be coped to the supporting member.
Severity
High.
Detailed Description
The assembly connection is not properly related to the feature of the assembly connection.
Possible Cause
Unknown.
532
Severity
Crucial.
Detailed Description
The relationship between the supported member part and the assembly connection does not exist. This relationship provides the proper compute order so that plate parts get generated after a cut operation occurs.
Possible Cause
Unknown.
Possible Impacts
Typically, plate parts will not appear at the correct location for gusset and corner-gusset type assembly connections.
533
Structure
Severity
Crucial.
Detailed Description
The identified assembly connection should have a generated custom plate part as its output (such as the base plate for the bottom of a column or the gusset for a gusset-type connection). It is highly likely that if this database message appears, the assembly connection is also in the To Do List as a result of an inconsistent geometric condition (for example, the supported and supporting members no longer intersect).
Possible Cause
Unknown.
Possible Impacts
No gusset plate or base plate will appear for the assembly connection.
534
Structure
Severity
Crucial.
Detailed Description
The identified assembly connection has a fixed number of relations that should exist between the assembly connection and the supported/supporting members. When this fixed number of relations is not as expected, this error occurs.
Possible Cause
Unknown.
Possible Impacts
It is highly probable that the assembly connection will not compute properly, so the cut or trim operation will not occur, and any generated plates will not be created.
Severity
Medium.
Detailed Description
The relationship between the assembly connection and the supported member end port does not exist.
535
Possible Impacts
The assembly connection will not compute properly, so any trim or cut operation on the supported member will not occur.
Severity
Crucial.
Detailed Description
The relationship between the supporting member part and the assembly connection does not exist.
Possible Cause
Unknown.
Possible Impacts
Computation of the assembly connection will not occur when the supporting member is modified.
536
Structure
Severity
Crucial.
Detailed Description
The relationship between the supporting member part end port and the assembly connection does not exist. All assembly connections must have a relationship to the supporting member part end port.
Possible Cause
Unknown.
Possible Impacts
Assembly connections will not compute properly (they will not be coped to the supporting member, or the plate parts of the assembly connection will not be generated).
Axis joint copy property flag is not zero or the point on value is not -1.0
Message
Axis joint copy property flag is not zero or the point on value is not -1.0.
Severity
Normal.
Detailed Description
The axis joint provides the connection between two member systems. When an axis joint is copied, the properties are altered to facilitate the copy; however, these properties should not be set persistently in the database.
537
Possible Impacts
The next graphical modification of the member systems connected to this axis joint may behave differently where all point-on member systems will maintain a relative distance along similar to how copy behaves.
Severity
Normal
Detailed Description
The Can Rule should not exist in the spatial index table.
Possible Cause
Unknown
Possible Impacts
Unknown
538
Structure
Severity
Normal
Detailed Description
The Can Rule's aggregated Geometric Construction macro object is missing.
Possible Cause
The can failed to compute correctly.
Possible Impacts
Unknown
Severity
Normal
Detailed Description
The Can Rule's aggregated point object is missing.
Possible Cause
The can failed to compute correctly.
Possible Impacts
Unknown
539
Structure
Severity
Normal
Detailed Description
The Can Rule exists, but it has no Member System input.
Possible Cause
The can is an orphan can.
Possible Impacts
Unknown
Severity
Normal.
Detailed Description
A door or window creates an opening on a support when the default surface of the door or window has a mating constraint with the support (for example, a slab or wall). There is an error if the opening exists while the mating constraint is missing.
Possible Cause
Unknown.
Possible Impacts
The door or window will not recompute properly.
540
Structure
3. 4. 5. 6. Open the model. Delete the door or window. Save the session. Refresh all session files that have a workspace including the door or window.
Severity
Normal.
Detailed Description
A door or window creates an opening on a support when the default surface of the door or window has a mating constraint with the support (for example, a slab or wall). There is an error if the opening is missing while the mating constraint exists.
Possible Cause
When the door or window is pasted with its support, and the constraint is not re-evaluated, the software will not recompute the door or window. In that case, you must recompute the door or window to re-create the opening. Otherwise, the door or window should be deleted.
Possible Impacts
The door or window will not recompute properly.
541
Structure
Severity
Crucial.
Detailed Description
An axis-end or axis-collinear frame connection is missing a relationship to the supporting member axis joint.
Possible Cause
Unknown.
Possible Impacts
Cannot properly copy an axis-end or axis-collinear connection when attempting to establish a new parent for the frame connection For example, copying/pasting the supported member of a collinear connection along with the collinear frame connection will not provide the user with the opportunity to choose the end of the supporting member system in which to establish the connectivity.
542
Structure
Severity
Crucial.
Detailed Description
Equipment foundation component must have a relation to the equipment foundation (parent).
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
Crucial.
Detailed Description
The purpose of an Equipment foundation is to support equipment. So, there is no point of the existence of a foundation without equipment, and hence it is orphaned.
Possible Cause
Unknown.
Possible Impacts
Unknown.
543
Structure
2. Open the model. 3. Delete the object.
Severity
Crucial.
Detailed Description
Every Equipment foundation must have one and only one related material that describes the material properties of the Equipment foundation.
Possible Cause
Unknown.
Possible Impacts
Any reports related to the material properties may fail.
Severity
Crucial.
Detailed Description
Every footing must have one and only one related material that describes the material properties of the footing.
Possible Cause
Unknown.
544
Severity
Crucial.
Detailed Description
For a single footing, the number of supporting members (inputs) must be one. For a combined footing, it must be two.
Possible Cause
Unknown.
Possible Impacts
Unknown.
545
Structure
Frame connection associated to more than one member part end port
Message
Frame connection associated to more than one member part end port.
Severity
Crucial.
Detailed Description
A frame connection should be associated to only one member part end port.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
Crucial.
Detailed Description
The lifetime of a frame connection is controlled by its member system; however, the frame connection did not get removed when the member system parent was deleted.
Possible Cause
Unknown.
546
Severity
Crucial.
Detailed Description
Frame connections are related to their supported members and supporting member via the reference collection. These relationships exist as specific types of relationships; however, a relationship exists to the Frame Connection across an unknown relationship.
Possible Cause
A custom frame connection was developed using an incorrect relationship between the member system and the frame connection reference collection. Another possible cause for this error is if the frame connections were migrated from Version 4.0 of the software. In Version 4.0, more general relations were being used between the frame connection and the member systems. These relations, however, were converted to more specific relations in Version 4.1. It is possible the version migration did not convert these relations properly.
Possible Impacts
The frame connection will not compute properly when the member system is manipulated.
547
Structure
Frame connection missing its reference collection relation to the member system
Message
Frame connection missing its reference collection relation to the member system.
Severity
Crucial.
Detailed Description
A frame connection is not related to its parent member system.
Possible Cause
Unknown.
Possible Impacts
A number of problems will most likely occur; for example, you will be unable to graphically select the frame connection to get to the end of a member system.
Severity
Crucial.
Detailed Description
Every frame connection should be associated to a member part end port. If this relationship is missing, it is a problem.
548
Possible Impacts
Unknown.
Severity
Crucial.
Detailed Description
Handrail must have a relation with its input (geometry).
Possible Cause
Unknown.
Possible Impacts
Handrail becomes orphaned.
549
Structure
Severity
Crucial.
Detailed Description
Handrail does not have a relation to its active entity.
Possible Cause
Unknown.
Possible Impacts
The resultant object may not be visible in the graphic view. Modification of the resultant object is not possible.
Severity
Crucial.
Detailed Description
HandrailAE is not associated to Handrail.
Possible Cause
Unknown.
Possible Impacts
Object becomes orphaned.
550
Structure
Severity
Normal
Detailed Description
The Can's knuckle type is set to Ignore or Bend, which are not valid for a Can.
Possible Cause
The can failed to compute correctly.
Possible Impacts
Unknown
Severity
Normal
Detailed Description
The Can rule split count does not match the neighbor part count.
Possible Cause
The can failed to compute correctly.
Possible Impacts
Unknown
551
Structure
Severity
Normal.
Detailed Description
An Axis Joint provides the logical connectivity between one or more structural member systems. The lifetimes of the axis joints are controlled by the connected member systems; hence, when the last member system connected to one of these axis joints is deleted, the joint is also deleted. For this error to occur, the axis joint was not removed when the last connected member system was removed.
Possible Cause
The axis joint should have been removed when: The last connected member system is removed. A member axis-along frame connection is modified to be an axis-end type frame connection causing two member systems to share a single axis joint.
Possible Impacts
This problem is benign and only indicates that the database contains data that needs to be removed.
Severity
Normal
Detailed Description
A Can exists on a member system, but that member system is not split at the Can's location like it should be.
Possible Cause
The parent member system is read-only.
552
Severity
Crucial.
Detailed Description
A member end port should be associated to only one frame connection. If the member end port has more than one related frame connection, it is a problem.
Possible Cause
Unknown.
Possible Impacts
Unknown.
553
Structure
Severity
Crucial.
Detailed Description
An end port of a member part maintains whether it is a start or end port. The properties on this end port conflict with the start and end of the member part.
Possible Cause
Unknown.
Possible Impacts
This error would not typically cause any immediate problems; however, downstream activities such as analysis would not be predictable if there are two start ports.
Severity
High.
Detailed Description
A member part has a cut length less than or equal to zero.
Possible Cause
The member part or system was manipulated such that the part axis is zero in length. This problem could have been due to a direct manipulation of the end of the member part, making the start and end point coincident, or as a result of an indirect modification that forced the ends of the member part to be coincident.
Possible Impacts
Unknown.
554
Severity
Crucial.
Detailed Description
Every member part must have only one related cross section occurrence that defines the projected profile for the initial solid geometry.
Possible Cause
In Version 4.0 of the software, a cross section services function was delivered that allows the ability to share the occurrence of an existing member part. This function is called PlaceCrossSectionOccurrence. By setting the third argument of this function to False, the developer can indicate that an existing cross section occurrence is to be used instead of creating a new one. The problem is that the developer cannot delete the cross section occurrence because it can (and will) delete the cross section occurrence out from under an existing member that shared the occurrence. This services function typically is used within hangers and supports, stairs, ladders, and handrail Visual Basic custom commands where the cross section was retrieved to produce a projection and then deleted.
Possible Impacts
The software cannot modify the member part that lost its cross section occurrence.
555
Structure
The steps to clean the VB commands to prevent this error from occurring again are: 1. Search all VB code for the function PlaceCrossSectionOccurrence. 2. For all located calls, change the third argument to True. 3. Verify that after the call to PlaceCrossSectionOccurrence, when you are done using the occurrence, you delete the occurrence from the database; otherwise, you will be leaving orphaned cross section occurrences in the database. 4. Rebuild your VB code.
Severity
High.
Detailed Description
The member part has an internal object called a generator that provides the functionality to construct the graphical part from the provided input axis and trim features. Having a member part without its generator would leave only the displayed member system and no graphical member part representation.
Possible Cause
Unknown.
Possible Impacts
No graphical manipulation of the member will be allowed.
556
Structure
Member part has more than one attached cross section definition
Message
Member part has more than one attached cross section definition.
Severity
Normal.
Detailed Description
Every part has an indirect relationship to its cross section definition in the catalog that provides the basic properties of the section. If a part has more than one related definition, it is ambiguous as to which cross section definition to use.
Possible Cause
Unknown.
Possible Impacts
Most likely, the properties of the member part cannot be reviewed.
Member part has more than one attached cross section occurrence
Message
Member part has more than one attached cross section occurrence.
Severity
Normal.
Detailed Description
Every member part has one cross section occurrence that defines the projected profile for the solid. A member part cannot have more than one cross section occurrence; otherwise, it is ambiguous as to which section to project along the axis to define the member part solid geometry.
557
Possible Impacts
Any manipulation of the member part will fail.
Severity
Medium.
Detailed Description
Every part may have one and only one material definition that defines the basic material properties of the member. If a part has more than one related definition, it is ambiguous as to which material definition to use.
Possible Cause
Unknown.
Possible Impacts
Unknown.
Severity
Normal.
Detailed Description
Every member part must have only one related cross section that describes the cross section properties of the member part.
558
Possible Impacts
Member property edit will fail.
Severity
Normal.
Detailed Description
Every member part must have one and only one related material that describes the material properties of the member part.
Possible Cause
A member part can be constructed without a material definition; therefore, it is plausible that a custom command exists where a member part was created without assigning it a material definition.
Possible Impacts
Any reports related to the material properties will fail.
559
Structure
5. In the Material box, choose a valid type. 6. Apply the properties, and exit the dialog box. To eliminate this problem from occurring again, locate the Visual Basic code that is allowing the member part to be created without a material. You will need to refer to the API help documentation as to the proper means of creating a member part and system and assigning the proper material and cross section. If you have no such code that is creating a member system, you will need to report the DB integrity problem to Intergraph Process, Power & Marine Support. A backup of your model will be needed to help determine the source of the problem.
Severity
High.
Detailed Description
Every member part has two end ports (one at the start and the other at the end). If one is missing, that is a problem.
Possible Cause
Unknown.
Possible Impacts
The software cannot establish assembly connections to the end of the member.
560
Structure
Severity
High.
Detailed Description
Every member part has two end ports (one at the start and the other at the end). If one is missing, that is a problem.
Possible Cause
Unknown.
Possible Impacts
The software cannot establish an assembly connection to the end of the member part.
Severity
High.
Detailed Description
A member system consists of one or more member parts. When the parts of a member system are missing, no graphic operation can occur on the member system.
Possible Cause
Unknown.
Possible Impacts
This member system has a database integrity problem and must be removed.
561
Severity
High.
Detailed Description
The solid geometry for the member part does exist.
Possible Cause
Unknown.
Possible Impacts
The member part will not display and is non-locatable.
Member system axis end port (at end) is related to more than one axis joint
Message
Member system axis end port (at end) is related to more than one axis joint.
Severity
Normal.
Detailed Description
The end of a member system can be related to only one axis joint. This axis joint defines the end location of the member system's logical axis.
562
Possible Impacts
Any manipulation of the member system will fail.
Member system axis end port (at start) is related to more than one axis joint
Message
Member system axis end port (at start) is related to more than one axis joint.
Severity
Normal.
Detailed Description
The start of a member system can be related to only one axis joint. This axis joint defines the start location of the member system's logical axis.
Possible Cause
Unknown.
Possible Impacts
Any manipulation of the member system will fail.
563
Structure
Severity
Normal.
Detailed Description
A member is allowed to be point onto another member, a surface, a point, a line, and so forth. However, one end of a member cannot be point onto more than one object.
Possible Cause
Unknown.
Possible Impacts
Modification of the offending member or the objects that it is point onto may cause the modification to falter and abort prematurely.
Severity
Crucial.
Detailed Description
The member system consists of three types of end ports: start, end, and along ports. The properties on the indicated port noted in the DB integrity script have inconsistent properties with how it is connected to the member system (the end port is related to the start of the member system, but the port indicates it is not at the start of the member system).
Possible Cause
Unknown.
564
Severity
High.
Detailed Description
The member system cannot exist without a member part, which provides the physical geometry for display and locate.
Possible Cause
Unknown.
Possible Impacts
The member part is broken beyond recovery so any manipulation of the system will fail.
565
Structure
Severity
High.
Detailed Description
Every member system has two end ports (one at the start and the other at the end). If one is missing, that is a problem.
Possible Cause
Unknown.
Possible Impacts
The software cannot connect other member systems to the end of the member.
Severity
High.
Detailed Description
The logical axis of a member system is described by a wirebody. The relation to the wirebody table is missing; hence, the member system does not have a logical axis and is incomplete.
Possible Cause
Unknown.
Possible Impacts
The software cannot manipulate the member system or part.
566
Severity
High.
Detailed Description
Every member system has two end ports (one at the start and the other at the end). If one is missing, that is a problem.
Possible Cause
Unknown.
Possible Impacts
The software cannot connect other members to the ends of the member system.
Severity
Normal.
Detailed Description
Every member system has a start and end frame connection. The lifetimes of these frame connections are controlled by the member system; hence, you cannot eliminate an end frame
567
Structure
connection unless you delete the member system. Therefore, a member system without a frame connection should not occur.
Possible Cause
Before Version 5 of the software, member systems without frame connections were allowed. Therefore, a migrated model can result in these messages. For a non-migrated model, this situation is abnormal and should not occur.
Possible Impacts
Commands that select a frame connection are affected. Examples of these commands include placement of members at the end of a member, assembly connection placement on a member system, and placement of analysis boundary conditions.
Manual Solution
1. Select the member system. 2. Click the Start and End frame connection buttons on the ribbon. The software creates new frame connections.
Automated Solution
1. Run the Clean Database custom command. 2. Select the member system(s) in error, and click Clean Now. The software creates new unsupported frame connections.
Severity
High.
Detailed Description
The type property on the member system has not been set. This property varies with the type category on the member. For example, a member system with type category of Beam would have a type of Beam, Purlin, Girder, Girt, or Joist.
Possible Cause
The likely cause of this error is that a custom command was written to place a member system, and the type property was not set on the member system.
568
Severity
High.
Detailed Description
The type category property on the member system has not been set. This property should have a value of Beam, Column, or Brace.
Possible Cause
The likely cause of this error is that a custom Visual Basic command/macro was written to place a member system, and the type category property was not set when the member system was created.
Possible Impacts
Without the type category property set on the member system, any member system that connects to this member system may not establish the correct frame connection when connection is By Rule.
569
Structure
Mismatched relations
Message
Mismatched relations
Severity
Normal
Detailed Description
The Can Rule is input to a Frame Connection whose Member System is not a contributing member of the Can Rule, or the Can Rule has a contributing member that has no Frame Connection in relation to the Can Rule.
Possible Cause
The can failed to compute correctly.
Possible Impacts
Unknown
Missing Knuckle
Message
Missing Knuckle
Severity
Normal
Detailed Description
The Can specifies that a cone exists, but there is no plate knuckle.
Possible Cause
A compute was delayed or the can data is out of date in the Catalog.
Possible Impacts
Unknown
570
Structure
3. Run the fix script when it is available.
More than one assembly connection is attached to the end port of a member part
Message
More than one assembly connection is attached to the end port of a member part.
Severity
Crucial.
Detailed Description
A member part may have only one assembly connection related to a given end of the member part because more than one assembly connection would compete for how the end of the member part is trimmed.
Possible Cause
Unknown.
Possible Impacts
The software will not allow more than one assembly connection to be connected to an end port of a member part. If this situation ever occurs, the last placed assembly connection will be disabled and its connectivity to the supported/supporting member systems will be severed. Therefore, the offending assembly connection should exist in the To Do List and is harmless to the existing data model.
Severity
Normal.
Detailed Description
Each member system must have a start and an end frame connection. The lifetimes of these frame connections are controlled by the member system; hence, you cannot eliminate an end frame connection unless you delete the member system. Therefore, a member system without a frame connection should not exist.
571
Possible Impacts
Commands that select a frame connection are affected. Examples of these commands include placement of members at the end of a member, placement of an assembly connections on a member system, and placement of analysis boundary conditions.
Manual Solution
1. Select the member system part. 2. On the ribbon, click the Start and End frame connection buttons to create new frame connections.
Automated Solution
1. Run the Clean Database custom command. 2. Select the member system(s) in error, and click Clean Now. The software creates new unsupported frame connections.
Severity
High.
Detailed Description
This internal object should inherit its permission group from its parent; however, the permission group does not match its parent's permission group.
Possible Cause
This problem is caused by a structural member part's failure to propagate to the graphic part generator or to its cross- section occurrence.
Possible Impacts
You might not be able to modify a structural member because the permission group of the secondary graphic part generator may not allow the manipulation of the member part graphics.
572
Severity
Medium
Detailed Description
The child plates that constitute the designed member are in a different permission group than the parent designed member object.
Possible Cause
You should only see this on a migrated database (before the fix for TR 167167, v08.01.36.0002 and earlier) if you changed the permission group of a designed member and then split that member. In that case, the new designed members will be in the correct permission group, but the plates will be in the active permission group.
Possible Impacts
Future modifications to the designed member or the plate systems could fail if the user does not have access to the plate system permission group.
573
Structure
Severity
Crucial.
Detailed Description
An Opening has no relation to an OpeningType object which defines some particular properties for the Opening; for example, Cutting Limit.
Possible Cause
Copying/Pasting an Opening.
Possible Impacts
At edit time, an Opening which does not go through all of the structure on which it is applied will not have the correct Cutting Limit value ("Through All" instead of "User Defined").
Orphan can
Message
Orphan can
Severity
Normal
Detailed Description
A rule based Can exists in the model, but there is no corresponding Can rule.
Possible Cause
A delete of the can failed.
Possible Impacts
Unknown
574
Structure
Severity
Normal
Detailed Description
A Can rule exists, but there is no corresponding Can in the model.
Possible Cause
A deletion of the can failed.
Possible Impacts
Unknown
Severity
Normal.
Detailed Description
Symbol occurrence objects in the database are orphaned as they do not have any relationships to the objects that created them.
Possible Cause
Some custom symbol objects that create cross section occurrences do not delete the occurrences after they have been used for creating projections. An example is in user symbol macros such as Stairs/Handrails that use the function PlaceCrossSectionOccurrence from CrossSectionServices in the SP3DStructGenericTools library.
Possible Impacts
Software performance degrades with a large number of these objects.
575
Severity
Normal.
Detailed Description
Whenever an assembly connection is placed along a supporting member, a relationship is established to the supported member via an along port on the member. When this error occurs, the along port of a part exists without its parent member part existing.
Possible Cause
Deleting a member part failed to propagate the delete operation to the along port, or it could be a permission problem where the object connected to the along port propagated a non-working status permission to the port such that it could not be deleted.
Possible Impacts
None.
576
Structure
Severity
Normal.
Detailed Description
Every member part has two end ports related to it (the end port at the start of the member and the end port at the end of the member). When the member part was deleted, one of the end ports was not deleted along with the member part.
Possible Cause
Deleting a member part failed to propagate the delete operation to one or more of its end ports.
Possible Impacts
None.
Severity
Normal.
Detailed Description
Every member system has two end ports related to it (the end port at the start of the member system and the end port at the end of the member system). When the member system was deleted, one of the end ports was not deleted along with the member system.
Possible Cause
Deleting a member system failed to propagate the delete operation to one or more of its end ports.
Possible Impacts
None.
577
Severity
High.
Detailed Description
A port face selector is an internal intermediary object between a structural slab and one of its bounding structural members. A root contour is an internal object and a parent of a port face selector but also a parent of a structural slab.
Possible Cause
The root contour has been deleted either by an unknown operation or by self-destruction triggered when all of its geometrical parents were deleted. Alternatively, the relationship between port face selector and its root contour has been deleted for an unknown reason.
Possible Impacts
The slab limited by this member will not correctly evaluate boundary offsets.
Severity
High.
Detailed Description
A port face selector is an internal intermediary object between a structural slab and one of its bounding structural members.
578
Structure
Currently, the source object of a port face selector is limited to a structural member.
Possible Cause
The source object has been deleted, but this delete operation was not propagated to the port face selector. Or, the relationship between the port face selector and its source object was deleted for an unknown reason.
Possible Impacts
The slab limited by this member will not correctly evaluate boundary offsets.
Severity
High.
Detailed Description
A port face selector is an internal intermediary object between a structural slab and one of its bounding structural members. A root contour is an internal object and a parent of a port face selector but also a parent of a structural slab. If a port face selector's root contour is not unique, this demonstrates a serious problem.
Possible Cause
A relationship between a port face selector and its root contour is instantiated more than one time, which can be the result of an automation problem or a copy and paste problem.
Possible Impacts
The slab limited by this member will not correctly evaluate boundary offsets.
579
Structure
Severity
High.
Detailed Description
A port face selector is an internal intermediary object between a structural slab and one of its bounding structural members. Currently, the source object of a port face selector is limited to a structural member.
Possible Cause
A relationship between a port face selector and its source object is instantiated more than one time, which can be the result of an automation problem or a copy and paste problem.
Possible Impacts
The slab limited by this member will not correctly evaluate boundary offsets.
Severity
Normal.
Detailed Description
A relationship exists to the frame connection reference collection that is not one of the well-known relations (such as the relations between the end ports of the supported/supporting member systems and the frame connection).
Possible Cause
More generalized relations were used in Version 4.0 of the software; hence, the version migration may not have migrated one of these relations correctly.
Possible Impacts
No visible problems will occur.
580
Reference Collection for an unsupported Frame Connection contains more than one element
Message
Reference Collection for an unsupported Frame Connection contains more than one element.
Severity
Normal.
Detailed Description
A relationship exists to the reference collection of a frame connection. Specific relationships have been defined to the frame connection; however, in this instance, a generic reference collection relationship exists.
Possible Cause
In Version 4.0 of the software, several of the relationships to the frame connection were generalized relations; however, in Version 4.1, all these relationships were made more specific. Therefore, if this error occurs, it is likely that the version migration of the frame connection did not perform properly.
Possible Impacts
Frame connections reported with this error may not copy properly if the reported frame connection is an axis-end or axis-collinear type frame connection.
581
Structure
Severity
High.
Detailed Description
The catalog type of a slab entity (the slab shown in the Workspace Explorer) is not unique anymore.
Possible Cause
A relationship between a slab entity and its catalog type is instantiated more than one time, which can be the result of an automation problem or a copy and paste problem.
Possible Impacts
The slab entity is either in error or has a database integrity problem.
Severity
High.
Detailed Description
The composition type of a slab entity (the slab shown in the Workspace Explorer) composition type is not unique anymore.
Possible Cause
A relationship between a slab entity and its catalog is instantiated more than one time, which can be the result of an automation problem or a copy and paste problem.
Possible Impacts
The slab entity is either in error or has a database integrity problem.
582
Structure
2. Locate the offending slab, and re-create it.
Severity
High.
Detailed Description
The catalog type of a slab entity (the slab shown in the Workspace Explorer) does not match a catalog entry anymore.
Possible Cause
The catalog type is not available in the catalog.
Possible Impacts
The slab entity is either in error or has a database integrity problem.
Severity
High.
Detailed Description
The composition relationship of a slab entity (the slab shown in the Workspace Explorer) does not exist anymore.
Possible Cause
The composition relationship or all slab layers have been deleted for an unknown reason.
Possible Impacts
The slab entity is either in error or has a database integrity problem.
583
Structure
2. Locate the offending slab, and select a type from the Composition dropdown list on the ribbon.
Severity
High.
Detailed Description
The composition of a slab entity (the slab shown in the Workspace Explorer) does not match a catalog entry anymore.
Possible Cause
The composition is not available in the catalog anymore.
Possible Impacts
The slab entity is either in error or has a database integrity problem.
Severity
High.
Detailed Description
The slab layer catalog type is not unique anymore.
Possible Cause
A relationship between a slab layer and its catalog is instantiated more than one time, which can be the result of an automation problem or a copy and paste problem.
Possible Impacts
The slab entity is either in error or has a database integrity problem.
584
Severity
High.
Detailed Description
The slab layer composition is not unique anymore.
Possible Cause
A relationship between a slab layer and its slab entity is instantiated more than one time, which can be the result of an automation problem or a copy and paste problem.
Possible Impacts
The slab entity is either in error or has a database integrity problem.
Severity
High.
Detailed Description
The slab layer catalog type does not match a catalog entry anymore.
Possible Cause
The catalog type is not available in the catalog anymore.
Possible Impacts
The slab entity is either in error or has a database integrity problem.
585
Structure
Severity
High.
Detailed Description
The slab layer composition relationship does not exist anymore.
Possible Cause
The composition relationship or slab entity has been deleted for an unknown reason.
Possible Impacts
The slab layer is orphaned.
Severity
Fatal
Detailed Description
No slab assembly connections are visible under the slab in the Workspace Explorer. This means the slab assembly connections are no longer in the database.
Possible Cause
All the slabs assembly connections have been interactively deleted.
Possible Impacts
The slab is missing key data and must be manually repaired to work as it was originally expected to for operations such as Copy, Move, and Mirror.
586
Structure
If the slab does not have boundaries: 1. Select new boundaries. 2. Click the green checkmark or Finish to regenerate the slabs assembly connections. If the slab does have boundaries: 1. De-select one boundary. 2. Select another object as the new specific boundary (a nearby grid line, for example). 3. Click the green checkmark or Finish. Repeat these steps for each boundary to regenerate slab assembly connections. If re-allocating boundaries does not correct the problem, the slab must be re-modeled.
Severity
Fatal
Detailed Description
No object is supporting the slab. To continue working, the slab keeps a local copy of the support information; however, this means that the slab may no longer work as originally expected in operations such as Copy, Mirror, and Move.
Possible Cause
The object supporting the slab has been deleted.
Possible Impacts
The slab must be manually repaired because it does not have all the support information it needs to function correctly.
These inputs will depend on what Plane Method was used to place the Slab (Coincident, Plane by # Points, and so forth).
If selecting a new support does not correct the problem, then the slab will have to be re-modeled.
587
Structure
Severity
Normal.
Detailed Description
A stair or ladder has multiple relationships to the bottom plane. The location of the stair or ladder depends on the inputs; therefore, more than one input would make the location of the ladder ambiguous.
Possible Cause
Unknown.
Possible Impacts
It is highly likely that one would not even notice a problem with the behavior of the ladder or stair because the first encountered input would be used, and any additional inputs would be ignored. However, it is plausible that if any of the inputs get modified, the ladder could compute its location based off a different input. The ladder would seem to move around unpredictably.
588
Structure
Stair or Ladder has more than one related reference plane or edge
Message
Stair or Ladder has more than one related reference plane or edge.
Severity
Normal.
Detailed Description
A stair or ladder has multiple relationships to a reference edge or plane. The location of the stair or ladder depends on the inputs; therefore, more than one input would make the location of the ladder ambiguous.
Possible Cause
Unknown.
Possible Impacts
It is highly likely that one would not even notice a problem with the behavior of the ladder or stair because the first encountered input would be used, and any additional inputs would be ignored. However, it is plausible that if any of the inputs get modified, the ladder could compute its location based off a different input. The ladder would seem to move around unpredictably.
589
Structure
Stair or Ladder has more than one related top plane or edge
Message
Stair or Ladder has more than one related top plane or edge.
Severity
Normal.
Detailed Description
A stair or ladder has multiple relationships to the top plane or edge. The location of the stair or ladder depends on the inputs; therefore, more than one input would make the location of the ladder ambiguous.
Possible Cause
Unknown.
Possible Impacts
It is highly likely that one would not even notice a problem with the behavior of the ladder or stair because the first encountered input would be used, and any additional inputs would be ignored. However, it is plausible that if any of the inputs get modified, the ladder could compute its location based off a different input. The ladder would seem to move around unpredictably.
590
Structure
Severity
Normal.
Detailed Description
A stair or ladder has relationships to its inputs: top edge, bottom plane, and an optional reference edge. The location of the stair or ladder depends on these inputs; therefore, if any one of the inputs is missing (bottom plane), the stair or ladder is orphaned.
Possible Cause
Deleting the original bottom plane geometry causes the stair or ladder to go to the To Do List, indicating the bottom reference plane is missing. As long as the stair or ladder remains on the To Do List, this error is not reported; however, if for some reason, the To Do List record is removed, then this problem is reported.
Possible Impacts
The stair or ladder will not recompute its size or position when its referenced geometry moves.
Severity
Normal.
Detailed Description
A stair or ladder has relationships to its inputs: top edge, bottom plane, and an optional reference edge. The location of the stair or ladder depends on these inputs; therefore, if any one of inputs are missing (top plane/edge), the stair or ladder is orphaned.
591
Possible Impacts
The stair or ladder will not recompute its size or position when its referenced geometry moves.
Severity
Crucial.
Detailed Description
A stair or ladder does not have a relation to its active entity (AE).
Possible Cause
Unknown.
Possible Impacts
The resultant object may not be visible in the graphic view. Modification of the resultant object is not possible.
592
Structure
Severity
Crucial.
Detailed Description
StairAE is not associated to Stair or Ladder.
Possible Cause
Unknown.
Possible Impacts
Object becomes orphaned.
Severity
Crucial.
Detailed Description
Every Structure SmartOccurrence has a relation between its flavor occurrence and the flavor for its selector logic. The majority of structure objects have a dummy selector; hence, if this relation is missing, it can be re-established if a similar flavor is found. This script detects such cases and provides a repair action that can be run against the database. You can run the repair with the Clean Database custom command.
Possible Cause
Not known.
Possible Impacts
This is only a detection script; hence, there is no known impact.
593
Surface frame connection is missing its reference collection relation to the surface
Message
Surface frame connection is missing its reference collection relation to the surface.
Severity
High.
Detailed Description
A surface-default frame connection is not related to a surface or plane.
Possible Cause
Unknown.
Possible Impacts
The member system will not move with the movement of the surface or plane to which it was originally attached.
594
Structure
Severity
Crucial.
Detailed Description
The relationship between the reference collection of a frame connection and the member end port is inconsistent with the connected end port (the frame connection is related to the member system end port, but the notification relationship is to the start of the member system).
Possible Cause
The Visual Basic frame connection macro that established the relationship has a problem. The relationship to the end port should be consistent with the end port properties.
Possible Impacts
The frame connection may not compute properly when the supporting member end is manipulated.
Severity
Crucial.
Detailed Description
The relationship between the reference collection of the frame connection and the member end port is inconsistent with the connected end port (the frame connection is related to the member system start port, but the notification relationship is to the end of the member system).
Possible Cause
The Visual Basic frame connection macro that established the relationship has a problem. The relationship to the start port should be consistent with the properties of the member port.
595
596
SECTION 28
Severity
High.
Detailed Description
A required EFWCorrelationToSP3D relationship is missing from an area system, unit system, or pipeline.
Possible Cause
The area system, unit system, or pipeline was created using a pre-V7 version of SmartMarine 3D.
Possible Impacts
Area systems, unit systems, or pipelines that are missing the EFWCorrelationToSP3D relationship cannot be correlated to objects in P&ID or PBS documents.
597
Severity
High.
Detailed Description
A child object has no parent/child relationship with a parent object.
Possible Cause
A serious and unexpected error has occurred, likely while changing the child object's parent.
Possible Impacts
The child object will not appear in the Workspace Explorer.
598
Severity
High.
Detailed Description
A child object has a parent/child relationship with more than one parent object.
Possible Cause
A serious and unexpected error has occurred, likely while changing the child object's parent.
Possible Impacts
Because the object does not have a proper parent/child relationship to a parent object in the database, it cannot be displayed in the Workspace Explorer or other tree views. Any branch of the system hierarchy below such an object will also not be displayed in the Workspace Explorer or other tree views. The broken object and any objects and parts in the branch below the broken object are lost from view by the user, even though they continue to exist in the database.
599
Severity
High.
Detailed Description
An object has a parent/child relationship with itself.
Possible Cause
A serious and unexpected error has occurred, likely while changing the child object's parent.
Possible Impacts
Because the object does not have a proper parent/child relationship to a parent object in the database, it cannot be displayed in the Workspace Explorer or other tree views. Any branch of the system hierarchy below such an object will also not be displayed in the Workspace Explorer or other tree views. The broken object and any objects and parts in the branch below the broken object are lost from view by the user, even though they continue to exist in the database..
600
Severity
High.
Detailed Description
A child system has no parent/child relationship with a parent system.
Possible Cause
A serious and unexpected error has occurred, likely while changing the child systems parent.
Possible Impacts
Because the system does not have a proper parent/child relationship to a parent system in the database, it cannot be displayed in the Workspace Explorer or other tree views. Any branch of the system hierarchy below such a system will also not be displayed in the Workspace Explorer or other tree views. The broken system and any systems and parts in the branch below the broken system are lost from view by the user, even though they continue to exist in the database.
601
Severity
High.
Detailed Description
A child system has a parent/child relationship with more than one parent system
Possible Cause
A serious and unexpected error has occurred, likely while changing the child system's parent.
Possible Impacts
Because the system does not have a proper parent/child relationship to a parent system in the database, it cannot be displayed in the Workspace Explorer or other tree views. Any branch of the system hierarchy below such a system will also not be displayed in the Workspace Explorer or other tree views. The broken system and any systems and parts in the branch below the broken system are lost from view by the user, even though they continue to exist in the database.
602
Severity
High.
Detailed Description
The delivered User Defined naming rule for system objects for versions prior to 2009.1 was creating this unnecessary relationship. Database Integrity scripts were provided with 2009.1 to detect this redundant relationship and delete them from model.
Possible Cause
Error in the delivered User Defined naming rule for system objects for versions prior to 2009.1.
Possible Impacts
Performance issues with certain operations such as Restore As Copy in the Project Management task.
Severity
High.
Detailed Description
A system has a parent/child relationship with itself.
Possible Cause
A serious and unexpected error has occurred, likely while changing the child system's parent.
Possible Impacts
Because the system does not have a proper parent/child relationship to a parent system in the database, it cannot be displayed in the Workspace Explorer or other tree views. Any branch of the system hierarchy below such a system will also not be displayed in the Workspace Explorer or other tree views. The broken system and any systems and parts in the branch below the broken system are lost from view by the user, even though they continue to exist in the database.
603
604
Index
A
A Beam does not have a related BeamSystemAE 207 A BeamPart does not have BeamPartProfileGeometry relationship 449 A BeamPart does not have GUIDBeamPartOrientation relationship 450 A BracketByPlane PlateSystem does not have a ReferenceCollection to its symbol 208 A BracketByPlane PlateSystem does not have the necessary two points defined 208 A BracketByPlane PlateSystem has too many points defined 209 A BracketByPlane PlateSystem has too many relationships to ReferenceCollections 210 A BracketByPlane PlateSystem's point is not an input to the symbol 210 A CollarPart does not have the AssemblyMembersR relation 450 A CollarPart does not have the CollarDefiningData relation 451 A CollarPart does not have the CollarPlateData relation 452 A connection has less than two ports 211 A Connection has more than 2 Ports associated to it 212 A CreateCollar_AE does not have a related PlatePartGeometry 452 A CreatePlatePartAE does not have a related plane 212 A CreatePlatePartAE does not have any related trim boundaries 213 A Design- or Planning-split operation exists with no related operand 214 A Design- or Planning-split operation with a seam has less than two results 214 A Design- or Planning-split operation without a seam does not have one result 215 A detailed PlatePartGeometry does not have a related AE 453 A Flanged Plate AE exists without a relationship to a Plate 216 A Flanged Plate exists without a symbol for the flange 216 A Flanged Plate exists without the start or end points defined 217 A Flanged Plate exists without updated output 218 A GeneratePlatePart_AE does not have a related PlateSystem 219 A LandCrvPoint does not have a related PointOnSurfByTwoCoords_AE 219 A LandCrvTableAE does not have related LandCrvPoints 220 A Landing Curve AE does not have the Parent0 relationship 221 A Landing Curve AE does not have the Parent1 relationship 221 A Landing Curve AE does not have the Parent2 relationship 222 A LandingCurve ActiveEntity does not have a related base curve 223 A LandingCurve ActiveEntity does not have a related geometry 223 A Name has not been defined for this object 224 A Plate bound operation exists with no related operand 225 A Plate bound operation exists with no related result 225 A plate bound to another plate is missing the connection 226 A Plate could be missing a sketched boundary 228 A Plate cutout operation exists with no related operator 229 A plate part does not have a related PlatePartReportData object 229 A Plate system exists with no related planning split or light part 230 A PlateGeometry does not have a related PlanningSplitAE 231 A PlateGeometry object exists without having a related ActiveEntity or Structural Entity 231 A PlatePartGeometry does not have a related CreatePlatePart_AE 232 A PlateStrakingSplit_AE does not have a SurfaceBody 454 A PlateSystem does not have a related MoldedSpec 233
605
Index
A PlateSystem exists with less than 3 or more than 5 shared attributes 234 A point for BracketByPlane is not related to a PlateSystem 235 A point for BracketByPlane is not related to a PlateSystem or any other object 235 A PointOnSurfByTwoCoords_AE does not have a related base plate 236 A profile does not have a related child connection 237 A profile Part does not have a related ProfilePartCreation 454 A profile part does not have a related ProfilePartReportData object 237 A Profile split ActiveEntity does not have a related profile system 238 A Profile system exists with no related planning split or light part 239 A ProfilePart does not have a related GeneratePlatePart_AE 455 A ProfilePart does not have a related ProfilePartGeometry 456 A ProfilePartCreation does not have a related base plate 239 A ProfilePartCreation does not have a related profile part 240 A ProfilePartCreation does not have a related ProfilePartGeometry 457 A ProfilePartCreation does not have a related ProfilePartPath 456 A ProfilePartGeneration_AE does not have a related plate system 241 A ProfilePartGeneration_AE does not have a related PlateGeometry 242 A ProfilePartGeneration_AE does not have a related profile system 243 A ProfilePartGeometry does not have a related ActiveEntity 243 A ProfilePartPath does not have a related ProfilePartCreation 458 A ProfileSystem does not have a related Plate 244 A ProfileSystem exists with a connection on its end port that is split 245 A ProfileSystem exists with less than 3 or more than 6 shared attributes 245 A ProfileSystemAE does not have a related ProfileSystemRegion 246 A ProfileTrim_AE does not have the ProfileTrim_OPER1 relation 458 A RefCurveOnSurface does not have a related PlateSystem 247 A ReferenceCollection for BracketByPlane is not related to a PlateSystem 247 A ReferenceCollection for BracketByPlane is not related to a PlateSystem or any other object 248 A SeamPoint AE does not have a related SeamPointGeometry 249 A SeamPoint does not have a related SeamPointGeometry 249 A SeamPointAE does not have a related profile system 250 A SeamPointAE does not have a related surface 251 A SeamPointOffsetAE does not have a related LandingOffset 251 A SketchFeature does not have an OutputColl 459 A SmartPlate does not have a related CreatePlatePart_AE 460 A split ActiveEntity does not have a related Seam 252 A StiffenerPart exists that is related to more than one StructPortAE 253 A straking Seam does not have a related StrakingSplit_AE 460 A Struct/Sketch Feature is missing its Cut or ProfileTrim Operator 461 A StructPort exists without a related StructPortAE 253 A StructPort exists without a related system 254 A StructPortAE exists without having related geometry 255 A Structural Connection exists that is not in the SystemHierarchy 256 A system does not have a related child part 257 Access Control Rule is not associated to Permission Group 389 Active Entity has no Space Geometry associated with it 83 Active entity with no Leg 183 Active entity with no outputs 183 Active Entity with no physical connections as input 462 Active entity with no supported entities 184 Added Pin's Approval Status does not match with Pin Jig's Approval Status 504 Added Pin's Permission Group does not match with Pin Jig's Permission Group 505 Added port with no object connected 53
606
Index
AE (Arrangement)/Broker that has the Querystring of elements in Model exists without a ShipDwgView 415 AE (Hulllines)/Broker that has the Querystring of elements in Model exists without a ShipDwgView 415 AE (scantling by volume)/Broker that has the Querystring of elements in Model exists without a ShipDwgView 416 AE (ShellExpansion)/Broker that has the Querystring of elements in Model exists without a ShipDwgView 416 Alternate Point has no relation to the ProfileByTable AE anymore 258 An ActiveEntity does not have a Part 462 An ActiveEntity does not have a related PartGeometry 463 An ActiveEntity does not have a related plate operand 259 An ActiveEntity exists with no related operand 259 An ActiveEntity exists with no related result 260 An ActiveEntity exists with no related result and no operand 261 An Assembly has itself as a parent in the AssemblyHierarchy 381 An EdgeReinforcement does not have a related LandCrvER_AE 261 An IJShellMoldedConventions Attribute Bag found on non-hull plate 262 An object does not have a related CreatePlatePartAE 464 An object does not have a related DReferencesCollection 464 An object does not have a related LandingCurve 263 An object does not have a related material 263 An object does not have a related PlateGeometry 265 An object does not have a related PlateGeometry nor a parent system 265 An object does not have a related PlatePartGeometry 465 An object does not have a related profile symbol 266 An object does not have a related StructPort_AE 267 An object exists that is not in the SystemHierarchy 267 An opening occurrence does not have a related PlateCutoutAE 268 An opening occurrence has relationships that point to different struct geometry 269 An unnecessary relationship exists in the database 269 Analysis Model has more than one boundary condition folder 431 Analysis Model has more than one load combination folder 432 Analysis Model has more than one member folder 433 Analysis Model is missing its association to the model 433 Analysis Model is missing its boundary condition folder 434 Analysis Model is missing its load combination folder 435 Analysis Model is missing its member folder 435 Analysis WSE folder has no parent 436 Assembly connection does not have a cutting plane 531 Assembly connection does not have an associated feature 532 Assembly connection feature is incorrectly related to member part 532 Assembly connection is missing a relation to the supported members end port 533 Assembly connection is missing one or more of its custom plate parts 534 Assembly connection is missing one or more related axis ports 535 Assembly connection missing relation to supported member part end port 535 Assembly connection missing relation to supporting member part 536 Assembly connection missing relation to supporting member part end port 537 Assembly Constraint is not associated to a part occurrence 157 Assembly margin child's Approval Status does not match with Assembly Margin's Approval Status 505 Assembly margin child's Permission Group does not match with Assembly Margin's Permission Group 506 Assembly Margin does not have Assembly 475 Assembly Margin parent does not have Assembly margin child 475 Attach connection without 2 ports 53 Axis joint copy property flag is not zero or the point on value is not -1.0 537
607
Index
B
Bad part Interference has no part 205 Bad StructPortSelector permission group 97 Base Control Line Symbol's Approval Status does not match with Template's Approval Status 506 Base Control Line Symbol's Permission Group does not match with Template's Permission Group 507 Base plane's Approval Status does not match with Template's Approval Status 507 Base plane's Permission Group does not match with Template's Permission Group 508 Beam axis rule type not defined 270 Beam does not have an orientation 270 Beam Orientation does not have Flip U defined 271 Beam Orientation does not have Flip V defined 272 Blob in the DocumentData object table is not valid 137 Block Assemblies must have topological blocks underneath 382 Boundary condition is not associated to a member part 437 BracketByPlane PlateSystem is not an input to the symbol's ReferenceCollection via StructSymbolInput2 272 BracketByPlane PlateSystem's PlaneByOffset PlateGeometry is not an input to the symbol's ReferenceCollection 275 BracketByPlane PlateSystem's ReferenceCollection has no symbol inputs 273 BracketByPlane PlateSystem's ReferenceCollection is not related to a ReferenceCollection for the symbol 274 BracketByPlane PlateSystem's symbol is not a BracketByPlane symbol 274 Branch feature not at end of leg 54 Branch Feature with no corresponding Along Leg Feature 54 BuiltUp Profile Nestdata does not have MfgProfile 476
C
Cable feature not associated with cable leg 405
Cable feature not associated with cable run 405 Cable has no cable part in the catalog 406 Cable is not connected to any equipment 406 Cable Leg not associated with Cable Feature 407 Cable Nozzle does not have proper orientation values 158 Cable occurrence not associated with cable feature 408 Cable occurrence not associated with cable run 408 Cable run not associated with any cable feature 409 Cable run not associated with cable occurrence 410 Can Rule exists in CORESpatialIndex 538 Can Rule missing aggregated GCMacro 539 Can Rule missing aggregated point 539 Can Rule missing Member System input 540 Cannot enclose void to construct a solid 171 Cannot get Cross Section Symbols for Profiles and Beams 276 Cannot stitch and orient the given surface bodies 172 Check Data Consistency Dialog Box 37 Check Database Integrity 35, 38 Child Property object's approval status or permission group does not match with the parent Property Object 137 Clean a Database 39 Clean Database Dialog Box 39 Common part group is not implemented 382 Common Route 53 Common Space 83 Common Structure 97 CommonApp 43 Compart By Path Active Entity does not have Path Object 105 Compart By Path Active Entity has no Sketch CrossSection Object 106 Compart By Points Active Entity has no input Points 106 Compart By Primitive Active Entity has no Compart Geometry 107 Compart Entity has no Compart Geometry 108
608
Index
Compart Geometry has no Compart Entity 108 Compart Geometry has no Geometry 109 Compart Geometry has no Space CreationAE 109 CompartBoolOperator has no Compart Geometry or Geometry 110 CompartBoolOperator has no CompartByBooleanAE Object 111 CompartBoundByFace has no CompartByBound object 111 CompartBoundByFace has no CompartByBound or CompartBySplit 112 CompartBoundByFace has no Geometry 112 CompartByBooleanAE has no CompartBoolOperator 113 CompartByBooleanAE has no CompartGeometry Object 113 CompartByBound has no Compart Geometry 114 CompartByBound has no CompartByBoundFace Object 115 CompartByBound is associated with the temporary geometry 115 CompartByImport Active Entity has no Compart Geometry 116 CompartByImportAE has no Point object 116 CompartByPathAE has no Compart Geometry 117 CompartByPoints has no Compart Geometry object 118 CompartByPrimitive has no CompartShapeDef object 118 CompartGeometry has no CompartBySplitAE 119 Compartmentation 105 CompartSplitAE has no CompartBoundByFace 119 CompartSplitAE has no CompartGeometry 120 CompartSplitAE is associated with the temporary geometry 121 Component without WBSProjectChild and WBSItemChild 184 Conduit Nozzle does not have proper orientation values 158 Connection associated with only one port 55 Connection has relation to Specification 55 Connection Item missing relation to catalog part 56 Connection Item missing relation to the object 56 Connection Items not associated to the owner part 57 Connection not associated with a port 58 Connection not associated with a run 58 Connection not connected to correct parent 59 Connection not having valid connection size 59 Connection PG/AS not same as connected parts or owner 60 Connection without support 185 Control point does not have a parent 43 ConventionPlatePort missing relation with PlatePosition 427 ConventionPlatePosition Missing Relation with MoldedConventionSpec 428 ConventionSpec missing Relation with MoldedFormSpec 429 Coordinate System contains some Planes/Cylinders at same position 177 Core 125 Corrupted Hanger Connections 185 CreateCollar_AE PG does not match with CollarPart PG 314 CreatePlatePart_AE PG does not match with Plate Part PG 315 Custom Component PG does not match PG of Sketched Feature 316 Cut operation missing input geometry 466 Cut_AE PG does not match Feature PG 316
D
Database Integrity 36 Database Integrity Custom Commands 35 Database is not associated to any plant 389 dbo.SHIPDWGShellExpSystem table is not created 417 dbo.SHIPDWGXMLStorage table is not created 418 Design Equipment has Invalid Range 159 Design- or Planning-split operation without a seam does not have one result 277 Design/Planning Split_AE PG does not match with System PG 317 Detailing AE PG does not match with Plate Part PG 318 Detected unassociated Location object 390
609
Index
Doc Output Mgr has duplicate data documents 138 Document Output Manager object has duplicate generated document relations 139 Document Output Manager object's approval status or permission group does not match with the owning SnapIn or Sheet object 139 Documentation Comments 27 DocumentData object's approval status or permission group does not match with Document Output Manager 140 Door or Window is missing its mating constraint 540 Door or Window is missing its opening 541 Dormant Part associated to the Feature 60 Drawing Issue object's approval status or permission group does not match with Property Object Child 141 Drawing Key Plan View object's approval status or permission group does not match with Drawing View object 141 Drawing object has duplicate relations 142 Drawing Revision object's approval status or permission group does not match with Property Object Child 143 Drawing View Info object's approval status or permission group does not match with Drawing View object 143 Drawing View object's approval status or permission group does not match with Drawing Sheet object 144 Drawing View on Drawing Component Template has Overrides 145 Drawing Volume object's approval status or permission group does not match with Drawing View object 146 Drawings and Reports 137 DrawingViewGenerator exists without a Dwg View 418 Duplicate naming rule assigned to a boundary condition 437 Duplicate naming rule assigned to a load 438 Duplicate naming rule assigned to a load case 438 Duplicate naming rule assigned to a load combination 439 Duplicate naming rule assigned to an analysis model 440 Duplicate PlateBound_OPER3 relationships exist between the same two objects 277 Duplicate relations exist in the database 186 Duplicate ShpStrDesignHierarchy relationships exist between the same two objects 278
E
Edge Treatment PG does not match PG of parent (Part/Edge Feature) 318 EdgeReinforcement is missing Attribute 279 Edgetreatment with no edge connected to it 466 Edgetreatment with zero length 467 Element Broker object's approval status or permission group does not match with Drawing View object 147 End frame connection missing a relation to the supporting member joint 542 End/Branch/Turn feature not a Terminating Feature of the leg 61 EntryExit not connected to leg 411 Equipment and Furnishings 157 Equipment does not have a system parent 159 Equipment foundation component does not have a relation to its parent 543 Equipment foundation exists without Equipment 543 Equipment foundation material is missing 544 Equipment has DBL_UNDEFINED values persisted for CG value 160 Equipment is not associated to a part 161 Equipment or Equipment component does not have a coordinate system 162 Equipment ports do not have a parent 163 Error code 58 - unspecified error description 163 Error on symbol internal object 125 Error on symbol relation 126 Extra/Orphaned group monitors exist 279
F
Feature Definition Point (Input) PG does not match with Feature PG 319 Feature Definition Point (Output) PG does not match with Feature PG 320 Feature has an Offline relation without a HasTapFeature relation 379 Feature not associated with a Leg 61 Feature not associated with a run 62
610
Index
Feature with branch parent function did not generate part occurrence 63 Feature with component Function did not generate component occurrence 63 Feature with end leg function did not generate component occurrence 64 Feature with user specified parts did not generate part occurrence 65 Feature with zero outer diameter 65 Feature without UserSpecifiedPart Relation 66 Find Objects by Report 40 Folder is not associated to the parent Folder 390 Footing material is missing 544 Footing without sufficient supporting members 545 Frame connection associated to more than one member part end port 546 Frame connection found that is unrelated to a member system 546 Frame connection is missing its reference collection 547 Frame connection missing its reference collection relation to the member system 548 Frame connection without member part end port relation 548 Free end cuts PG does not match Part PG 320
I
Incorrect UpToDate column in StrMfgUpdateInfo table 476 Inline feature & Branch Feature belong to same leg 67 Input-Added MfgPin does not have PinJig active entity 477 Interference Checking 205 Interference has only one part and not in Todo List 206 Intermediate End Feature and Connected Intermediate End Feature generating part 67 Invalid Knuckle type 551 Invalid neighbor part count 551 Invalid number of related objects 44 Invalid relationship between the Workspace Explorer root and the plant in the site database 391 Invalid WCGProperties for the object that has valid weight and CG 164 Invalid Zero Length Straight Feature 68
J
Joint exists without a support 187 Joint found that is unrelated to a member system 552
L
Last Geometry PG does not match PG of the Object 322 Leg not split 552 Leg with features belonging to multiple runs 68 Leg with no associated features 69 LinearExtrusion AE does not have a retrievable MotherCurve 281 LineFeature doesn't have minimum number of TurnPoints 45 Load associated to more than one load case 440 Load associated to more than one member 441 Load case does not have a parent load case folder 441 Load combination has a factor to a load case that does not exist 442 Load combination has no assigned load cases 443 Load has a force or moment magnitude of 0 443
G
Generic SmartPlant Error 126 Geometry and Topology 171 Graphic object is an orphan 127 Grids 177
H
Handrail exists without its geometry 549 Handrail is not associated to HandrailAE 550 HandrailAE is not associated to Handrail 550 Hangers and Supports 183 Hierarchical Loop Detected 83, 187 Hierarchy filter with missing Adapter ProgId 44 HierarchyNamingAE PG does not match PG of Relation Destination 321 Hole Management 195 Hull Plate System does not have Shell Molded Conventions defined 280
611
Index
Load not assigned to a member part 444 Load not associated to a load case 444 Load relative position is not between 0 and 1 445 Member part is missing its end ports 561 Member part not attached to member part generator 561 Member part solid geometry missing 562 Member system axis end port (at end) is related to more than one axis joint 562 Member system axis end port (at start) is related to more than one axis joint 563 Member system can be point on to only one member system 564 Member system end port found with invalid properties 564 Member system exists without any member parts 565 Member system is missing a start or end port 566 Member system is missing its attached wirebody 566 Member system is missing its end ports 567 Member system missing one or more frame connections 567 Member system Type property cannot be 0 568 Member system TypeCategory property cannot be 0 569 MfgBevel does not have Geom2D 482 MfgBevel object's Approval Status does not match with MfgPlate/MfgProfile's Approval Status 511 MfgBevel object's Permission Group does not match with MfgPlate/MfgProfile's Permission Group 511 MfgDefinition's Approval Status does not match with Pin Jig's Approval Status 512 MfgDefinition's Permission Group does not match with Pin Jig's Permission Group 513 MfgGeneralHitachi's Approval Status does not match with MfgPlatePart's Approval Status 513 MfgGeneralHitachi's Permission Group does not match with MfgPlatePart's Permission Group 514 MfgGeomchild's Approval Status does not match with MfgGeomParent's Approval Status 514 MfgGeomchild's Permission Group does not match with MfgGeomParent's Permission Group 515 MfgHitachi object does not have MfgPlatePart 482
M
Manufacturing children without parent 478 Manufacturing definition does not have port 478 Manufacturing objects without parent 479 Manufacturing parts under Plate part or Profile part do not have same Approval Status 509 Manufacturing parts under Plate part or Profile part do not have same Permission Group 509 Manufacturing SmartOccurrence without part input 479 Marker not connected to feature 411 Marker Not connected to leg 412 Marking line active entity without detailed part as input 481 Marking line does not have Parent 481 Marking Lines active entity without any output 480 Marking Lines active entity without any reference object as input 480 MarkingLineData's Approval Status does not match with Marking Line's Approval Status 510 MarkingLineData's Permission Group does not match with Marking Line's Permission Group 510 Member end port associated to more than one Frame Connection 553 Member part axis end port found with invalid properties 554 Member part cutLength is zero 554 Member part does not have an attached cross section occurrence 555 Member part generator missing 556 Member part has more than one attached cross section definition 557 Member part has more than one attached cross section occurrence 557 Member part has more than one material definition 558 Member part has no attached catalog cross section definition 558 Member part has no attached material definition 559 Member part is missing a start or end port 560
612
Index
MfgNestData object's Approval Status does not match with MfgProfilePart's Approval Status 515 MfgNestData object's Permission Group does not match with MfgProfilePart's Permission Group 516 MfgPlateCreation active entity does not have DetailPlatePart as Input 483 MfgPlateCreation active entity does not have SmartOccurrence Object 483 MfgPlateMarking Settings object does not have MfgPlateCreation active entity 484 MfgPlatePart active entity does not have MfgPlatePart 485 MfgPlatePart does not have MfgPlatePart active entity 485 MfgPlateProcess Settings object does not have MfgPlateCreation active entity 486 MfgProfile Part does not have MfgProfileCreation active entity 486 MfgProfileCreation active entity does not have DetailPlatePart as Input 487 MfgProfileCreation active entity does not have MfgProfilePart 487 MfgProfileCreation active entity does not have SmartOccurrence object 488 MfgProfileMarking Settings object does not have MfgProfileCreation active entity 488 MfgProfileProcess Settings object does not have MfgProfileCreation active entity 489 MfgSystemMark3D object's Approval Status does not match with MfgProfile's Approval Status 517 MfgSystemMark3D object's Permission Group does not match with MfgProfile's Permission Group 517 Migration to V6.1 should have removed all objects in the PLANNGAssemblyReportData table 383 Mismatched relations 570 Missing Column 'dTimeLastGenerated' in table dbo.SHIPDWGShellExpSy 419 Missing Column 'dVolumeThicknessNeg' in table dbo.SHIPDWGScantlingByVolumeAE 419 Missing Filter on Drawings by QueryManager with children 148 Missing Knuckle 570 Missing relation between Structcutoutcontour object and openingtype object 98 Missing relationship for Correlated object 597 Model body has no topology 172 Model body is self-intersecting 173 Model database has more than one site occurrence for catalog 392 Model geometries do not intersect 173 Model geometries do not overlap 174 Model has multiple ProxyOwners (site) for projectdb 392 Molded Forms 207 Molded Forms Permission Group Messages 314 More than one assembly connection is attached to the end port of a member part 571 Multiple boundary conditions are assigned to the same end of a member part 445 Multiple ConfigProjectRoot objects exists in the model 393
N
Name rule AE is not associated to a named item 45 NameRuleAE PG does not match PG of Relation Destination 322 Need to remove the RelConnectionAndPartOcc between the cableocc and the Distribconn 69 No connection items generated by the connection 70 No frame connection found on end of member system 571 No Geometry filename is stored with an object that has imported geometry 281 Non-spool object with SpoolHierarchy relation to ConfigProjectRoot 380 Note does not have a parent 46 Nozzle is not associated to an EFCorrelation object 165
O
Object does not have a parent 598 Object does not have the requested data 178 Object does not have the requested relation 180, 397 Object does not have the requested simple relation 400
613
Index
Object has an unexpected relation 128, 402 Object has invalid geometry 128, 182 Object has more than one parent 599 Object has multiple structural naming Hierarchy Parent relationships 282 Object has multiple structural naming reference controllers (active entities) 283 Object is not accessible 129 Object is related to a port with a bag of bytes--should be related to connectable port 283 Object is the parent of itself 600 Object naming error 129 Object not in the same permission group as its parent 572 Objects with invalid cross sectional parameters 70 Oblique margin does not have port 490 Occurrence Assembly without part 188 One or more outputs of a Designed Member exist in a different Permission Group 573 Only one as-built object allowed in a model 46 Opening without any OpeningType relation 98, 574 Operation_AE PG does not match with Plate System PG 323 Orphan can 574 Orphan can rule 575 Orphaned Cross section symbol occurrences having no relationships to any objects 575 Orphaned Hanger Port(s) 188 Orphaned Nozzle 165 Orphaned Sketched Cutout Contour not related to CutoutAE 99 Orphaned SructPlane3d objects 284 Orphaned Structural connection is not associated to any port (IJPort) 99 Orphaned structure member part along port 576 Orphaned structure member part end port 577 Orphaned structure member system end port 577 PartReportData PG does not match with Part PG 323 Permission Group contains duplicate Access Control Rules 393 Permission Group has multiple relations with Folder Parent 394 Permission Group is not associated to a Folder 394 Permission Group is not associated to a Location 395 Permission Group of the object is different from the Parent Object 166 Permission Group of the shape is different from the corresponding Smart Equipment 166 PG of Feature on FreeEndCut does not match with Part PG 324 PG of Geometry after Operation_AE does not match with PG of Seam 325 PG of Geometry after ProfilePartGeneration_AE does not match with PG of Profile Part 325 PG of LC created by seams does not match with the Parent PG 326 PG of PlatePartGeometry after CreatePlatePart_AE does not match with PG of Plate Part 327 PG of Seam LandCrvBound_AE does not match with PG of Plate Part 327 Physical Connection Active entity with no outputs 468 Physical Connection Active entity without any inputs 468 Physical connection has multiple symbols 469 Physical connection only has dummy symbol 469 Pin Jig active entity's Approval Status does not match with Pin Jig's Approval Status 518 Pin Jig active entity's Permission Group does not match with Pin Jig's Permission Group 518 PinJig active entity does not have Input-Supported plate 490 PinJig active entity does not have output Jig 491 PinJig active entity does not have Seams with 'ButtAndSeam' relation 491 PipeSurfaceMount Feature without Attach Connection 73 Piping 379
P
Parent Connection is generating Non-BoltSet Connection Items 71 Part and Feature data is not matching 72 Part not associated with a feature 72 Part not associated with a run 73
614
Index
PlaneBy2PtsProjDir_AE does not have a related Frame Axis 285 PlaneBy2PtsProjDir_AE does not have a related Plane 285 PlaneBy2PtsProjDir_AE does not have related Normal Vector 286 PlaneBy2PtsProjDir_AE does not have related Points On Surface 287 PlaneBy2PtsProjDir_AE output Plane is not related to a landing curve 287 Planning 381 Planning Block Assembly is above the B0 Block 383 Planning Block Assembly is at the same level as the B0 Block 384 Plant is not associated to Plants root 396 Plate creation active entity's Approval Status does not match with MfgPlatePart's Approval Status 519 Plate creation active entity's Permission Group does not match with MfgPlatePart's Permission Group 519 Plate has no dimensions 288 Plate Knuckle PG does not match with Plate System PG 328 Plate LinearExtrusion AE is missing its Mother Curve 290 Plate Part has no dimensions 290 Plate System cannot be used as a seam boundary 291 Plate System does not have Molded Conventions defined 292 PlateBound_AE / PlateCutOut_AE InPut Geometry PG does not match with Plate System PG 329 PlateBound_AE / PlateCutOut_AE PG does not match with Plate System PG 329 PlateCutOut_AE InPut Geometry PG does not match with Plate System PG 330 PlateCutOut_AE PG does not match with Plate System PG 331 PlatePart has no Geometry associated to it 293 PlatePartGeometry is missing active entity and is unable to update 293 PlatePartGeometry is missing CreatePlatePart_AE and is unable to Update 294 PlatePartGeometry PG does not match with Plate Part PG 331 PlateSystem does not have its IJPlate attributes set 295 PlateSystem has no PlatePart via GraphicsMap 295 PointFeature has no TurnPoint associated with it 47 Port face selector is missing its root contour 578 Port face selector is missing its source object 578 Port face selector root contour is not unique 579 Port face selector source object is not unique 580 Ports with no association to Parts 74 Preface 23 Profile by Projection is missing its Sketched curve 296 Profile creation active entity's Approval Status does not match with MfgProfilePart's Approval Status 520 Profile creation active entity's Permission Group does not match with MfgProfilePart's Permission Group 521 Profile Knuckle PG does not match with Profile System PG 332 Profile leaf system is not on PartGeneration_OPER relationship 297 ProfileKnuckle does not have a related ProfileLanding Curve 297 ProfileKnuckle LandingCurve does not match with Profile System PG 333 ProfileMoldedConvention missing relation with Plate port 430 ProfilePartGeneration_AE PG does not match with Profile Part PG 333 ProfileSystem active entity is not related to a trace curve or a beam geometry 298 ProfileSystem is not related to the Design nor the Planning Split AEs 299 ProfileSystem or an EdgeReinforcement System does not have a relationship to a ProfileSystem active entity 299 ProfileTrim_AE PG does not match PG of Profile Struct Feature 334 Project Management 389 Property object's approval status or permission group does not match with Drawing Sheet or SnapIn 148 PropertyChild entity has no parent PropertyObject 149 PropertyObject has no associated SnapIn or Sheet 150
615
Index
R
Reference collection for a FrameConnection uses unexpected relation 580 Reference Collection for an unsupported Frame Connection contains more than one element 581 Reference Data 397 Report object's approval status or permission group does not match with View Generator object 150 Report Template object's approval status or permission group does not match with Drawing View object 151 Rotation Angle is not set for Beam 300 Route Cable 405 Route part missing relation with ports 74 Route part occurrence with missing relation to Catalog part 75 Route part occurrence with missing relation to Material Control Data 75 Route part occurrence with wrong made relation name 76 Route part occurrence with wrong permission group or approval status 76 Run Database Administration Processes (Matrix) 41 Run with no feature that has an entry in the Spatial Index table (Range) 77 Run without specification 78 Run without system parent 78
S
Schedule Check Data Consistency Task Using Batch Services 38 Seam by Projection AE is missing its Sketched curve 301 Seam by Projection is missing its Sketched curve 301 Seam does not have a related SeamLandCurve 302 Seam landing offset PG does not match with PG of Seam 335 Seam Operation_AE PG does not match with PG of Seam 335 SeamAE does not have a related CSeamLandCrv 303 SeamByTable_AE does not have a related LandCrvPoints 303 SeamGeometry_AE does not have a related Seam Entity 304 SeamGeometry_AE does not have related Plate Entity 304
SeamGeometry_AE PG does not match with Seam PG 336 SeamIntersection_AE does not have a related PlateGeometry 305 SeamLandCrv does not have a related Generation/StructOperation AE 305 SeamOffset_AE does not have a related LandingOffset 306 SeamOffset_AE does not have a related PlateGeometry 306 SeamProject_AE does not have a related PlateGeometry 307 Secondary class object in CoreSpatialIndex table 307 Segment not associated to any boundary 412 Segment not connected to any cableway Feature 413 Segment not connected to any leg 413 Shape does not have an equipment parent 167 Shared Attribute found on object that does not require it 308 Sheet entity has no associated parent SnapIn 152 Shell expansion AE Exists without plate geometry 421 ShellExpansionAE exists without BaseCurve Input 421 ShellExpansionAE exists without Hull Plate input 420 Ship Drawings and Reports 415 Ship Reference Data 427 ShipDwg Table does not exist in Catalog 422 ShipDwgView exists without a Dwg Sheet 423 ShipDwgView/MetaShipDwgView exists without a Dwg View 423 Shrinkage Active entity does not have detailed part as input 492 Shrinkage Active entity without Output 492 Shrinkage Active entity without Primary Axis 493 Shrinkage Active entity without Primary port 493 Shrinkage Active entity without Secondary Axis 494 Shrinkage Active entity without Secondary port 494 Shrinkage active entity's Approval Status does not match with Shrinkage's Approval Status 521
616
Index
Shrinkage active entity's Permission Group does not match with Shrinkage's Permission Group 522 Shrinkage object with secondary factor but no secondary direction 495 Shrinkage output without active entity 495 Sketch feature PG does not match with Part PG 337 Sketch Template Line Symbol's Approval Status does not match with Template's Approval Status 522 Sketch Template Line Symbol's Permission Group does not match with Template's Permission Group 523 Sketch3d is not associated to SketchByPointsAE 48 Sketch3d Point is not associated to a TurnPoint 48 SketchByPointsAE is not associated to Sketch3d 49 SketchByPointsAE requires minimum two input points 49 Sketched Cutout Contour is not associated to any symbol 100 Sketched Cutout Contour is not related to SketchWireBodyOutput geometry 100 SketchReferenceCol PG does not match PG of Sketched Feature 337 Slab entity catalog type reference is not unique 582 Slab entity composition reference is not unique 582 Slab entity is missing its catalog type reference 583 Slab entity is missing its composition 583 Slab entity is missing its composition reference 584 Slab layer catalog type reference is not unique 584 Slab layer composition is not unique 585 Slab layer is missing its catalog type reference 585 Slab layer is missing its composition 586 Slab Without Any Slab Assembly Connection 586 Slab Without Supporting Object 587 Smart Equipment has a missing relation with symbol sub system 168 Smart Item associated to Equipment has different permission group 168 SmartMarine 3D and Oracle 28 SmartMarine 3D Documentation Set 24 SmartOccurrence object's Approval Status does not match with MfgPlatePart's Approval Status 523 SmartOccurrence object's Approval Status does not match with MfgProfilePart's Approval Status 524 SmartOccurrence object's Approval Status does not match with Template's Approval Status 525 SmartOccurrence object's Permission Group does not match with MfgPlatePart's Permission Group 525 SmartOccurrence object's Permission Group does not match with MfgProfilePart's Permission Group 526 SmartOccurrence object's Permission Group does not match with Template's Permission Group 526 SmartPlant Error Multiple objects with the same name 132 SmartPlant Error Cardinality violation in design basis relation 130 Dead object or correlation wrong 130 Multiple objects with the same name 131 Multiple view files with same name 132 SnapIn entity has no associated parent 152 SnapIn entity has no associated PropertyObject 153 Snapshot view is not associated to a volume 154 Space Association Active Entity has no Graphic Object 84 Space Association Active Entity has no Space Entity associated to the Graphic Object 85 Space Boolean Operator does not have a Space Geometry 85 Space Boolean Operator is not connected to Space By Boolean Active Entity 86 Space By Boolean Active Entity is not connected to Space Boolean Operator 86 Space By Path Active Entity does not have Path 87 Space By Path Active Entity has no CrossSection 88 Space By Plane and Offset Active Entity does not have the Fence input Points 88 Space By Plane and Offset Active Entity does not have the Reference Plane 89 Space By Points Active Entity has no input Points 89
617
Index
Space By Primitive Active Entity has no Geometry 90 Space Entity does not have a Catalog Part 90 Space Entity does not have Range 91 Space Entity does not have Space Geometry 92 Space Geometry has no Active Entity associated with it 92 Space Geometry is not connected to any Space Entity 93 Space Object does not have Local coordinate system 93 Space object has two parents 94 SpaceChild does not have a Parent 94 Spatial Load Combination object has no parent(Load Folder) object 121 Spatial Load Folder object has no Parent (Configure Project Root or Load Folder) object 122 Spatial Load object has no Compart Geometry object 122 Spatial Load object has no Parent object 123 SpatialOrientation is not connected to a Space Object or Sketch3d object 95 Split Point Active entity with no outputs 470 Split Point Active Entity with no RefFace as input 471 Split point exists without active entity 471 Stair or Ladder has more than one related bottom plane 588 Stair or Ladder has more than one related reference plane or edge 589 Stair or Ladder has more than one related top plane or edge 590 Stair or Ladder is missing its bottom supporting plane 591 Stair or Ladder is missing its top supporting plane or edge 591 Stair or Ladder is not associated to its AE 592 StairAE is not associated to Stair or Ladder 593 StandAlone Struct Generation Active Entity has no parent input 101 StandAlone Struct Operation Active Entity has no Operand input 101 StandAlone Struct Port not associated to a StructPortSelector AE 102 StandAlone StructGenericEntity not associated to a Struct Generic Geometry 103 StandAlone StructPortSelector not associated to a StructGenericEntity 103 StdPlateSystemNamingAE PG does not match PG of StdPlateSystem 338 Straight feature generating a mating part 79 Straight feature not generating stock part occurrence 79 StrikeSplit_AE PG does not match with SeamSeamPoint PG 339 StructContinuity type/priority not being set on a Root System 309 Structural Analysis 431 Structural Detailing 449 Structural Manufacturing 475 Structural Manufacturing Permission Group and Approval Status Messages 502 Structural Port exists without relating to a Connectable Business Object 310 Structure 531 Structure SmartOcc related objects with missing flavor relation 593 Support as an assembly child, but not being a parent 189 Support Component with no Support 189 Support exists without active entity 190 Support exists without joint 190 Support has no components 191 Support not associated to a definition 191 Support without CoordinateSystem 192 Support without Name 192 SupportPort without Support 193 SupportPort without SupportComponent 193 Surface frame connection is missing its reference collection relation to the surface 594 SurfaceMount Feature not connected to Inline Feature 80 Symbol's Approval Status does not match with Marking Line's Approval Status 527 Symbol's Permission Group does not match with Marking Line's Permission Group 527 System does not have a parent 601 System has more than one parent 602 System has unneeded NamingParent relation 603 System is the parent of itself 603 System marks are on 2D relation but do not have MfgGeom2d 496 System marks are on 3d relation but do not have MfgGeom3d 497
618
Index
System marks do not have relation to MfgGeom3d or MfgGeom2d 496 System-derived part missing parent system needs user attention 310 SystemMark2D object's Approval Status does not match with MfgProfile's Approval Status 528 SystemMark2D object's Permission Group does not match with MfgProfile's Permission Group 529 Systems and Specifications 597 The BeamGeneration_AE PG does not match with Beam Stand Alone Part PG 341 The BeamGeneration_AE PG does not match with BeamSystem PG 342 The BeamLandCurve_Input PG does not match with BeamSystem PG 343 The BeamLandingCrv PG does not match with BeamSystem PG 343 The BeamStandAlonePart_AE PG does not match with Beam Stand Alone Part PG 344 The BeamSystem_AE PG does not match with Beam System PG 345 The BracketByPlane definition point PG does not match the BracketByPlane PG 345 The BracketByPlane definition ReferenceCollection PG does not match the BracketByPlane PG 346 The catalog fitting is missing a connection to the pipe part 196 The center flange is missing a connection to the pipe part 196 The child LC PG does not match with the root LC PG 347 The collar PG does not match Part PG 347 The feature PG does not match with its part PG 348 The hole has an invalid application value 197 The hole has an invalid cut status value 198 The hole has an invalid fitting type value 198 The hole has an invalid status value 199 The hole is missing the clearance rule to be used 200 The hole is missing the fitting selection rule to be used 201 The intersection object is related to a system instead of a part 385 The IntersectionAE PG does not match with Feature PG 349 The LandCrvBound_AE PG does not match with BeamSystem PG 349 The Landing Curve PG does not match with Standalone Stiffener PG 350 The Landing Offset PG does not match with Profile System PG 351 The LandingCrv_AE PG does not match with ProfileSystem PG 353
T
Tap Feature with no association to Tapped Feature 80 Template active entity does not have Input Sketching Plane 497 Template active entity without output 498 Template active entity without plate input 498 Template active entity without Process and Marking settings 499 Template active entity's Approval Status does not match with Template's Approval Status 529 Template active entity's Permission Group does not match with Template's Permission Group 530 Template has invalid child 499 Template Manager object's approval status or permission group does not match with Parent Drawing Type or Sheet 154 Template Mgr object has no parent Snapin or Sheet 155 Template Sheet is corrupted 156 TemplateMarking Settings without active entity 500 TemplateProcess Settings without active entity 500 TemplateSet object without active entity 501 TemplateSnapIn exists without a TemplateMgr 424 The AC PG does not match the Part PG 339 The Approved hole is missing a relationship to the structure part being cut 195 The Beam Point3d PG does not match with Beam Stand Alone Part PG 340 The BeamAssoc Point PG does not match with BeamSystem PG 341
619
Index
The LandingCrvBound_AE PG does not match with Profile System PG 351 The LandingCrvPoint PG does not match with Profile System PG 352 The LandOffset does not match with Edge Feature PG 353 The leaf part PG does not match the root part PG 354 The Leaf ProfileLandCrv PG does not match with Leaf ProfileSystem PG 355 The Leaf ProfileSys Region PG does not match with Leaf Profile System PG 355 The Leaf ProfileSystem_AE PG does not match with Leaf ProfileSystem PG 356 The leaf system PG does not match root system PG 357 The Logical Connection does not have the user class set 311 The object does not exist but another object has a relation to it 133 The object should be in the HoleManagement PermissionGroup 201 The object should be in the MoldedForms PermissionGroup 312 The object should be in the Planning PermissionGroup 385 The object should be in the ShipDrawings PermissionGroup 424 The object should be in the StructDetail PermissionGroup 472 The object should be in the StructManufacturing PermissionGroup 502 The OffsetPt_AE does not match with Edge Feature PG 357 The Opening PG does not match root system PG 358 The PG of Chamfer does not match with Part PG 359 The PG of PC on AC does not match Parent PG 359 The PG of PhysicalConnection on Collar does not match with Part PG 360 The PG of PhysicalConnection on Feature does not match with Part PG 361 The pipe part is missing a connection to the fitting 202 The PLANNGAssemblyBase table is missing the BlobSize column 386 The PLANNGAssemblyBase table is missing the ConnectivityInfo column 387 The PointOnGeom_AE PG does not match with Feature PG 361 The PointOnSurfByTwoCoords_AE PG does not match with Profile System PG 362 The ProfileLandCrv PG does not match with ProfileSystem PG 363 The ProfileLandCrvInPut PG does not match with Profile System PG 364 The ProfilePartCreation PG does not match with StandAloneStiffener PG 365 The ProfilePartPath PG does not match with StandAlone Stiffener PG 366 The ProfileSysRegion PG does not match with ProfileSystem PG 367 The ProfileSystem_AE PG does not match with Profile System PG 367 The proxy exists but is not connected to any other object 134 The Ref Curve PG does not match root system PG 368 The root LC PG does not match with the dependent system 369 The root logical connection is using a leaf system port instead of a root system port 312 The rule-based features PG does not match Part PG 369 The Seam PG does not match root system PG 370 The SharedAttEntityBag PG does not match with Parent PG 371 The ShpStrEdgeFeatOffPt_OUT does not match with Edge Feature PG 371 The sketched hole is missing the relationship to its outline 199, 203 The Symbol PG does not match the BeamSystem PG 372 The Symbol PG does not match with Beam StandAlone Part PG 373 The Symbol PG does not match with ProfileSystem PG 373 The Symbol PG does not match with StandAloneStiffener PG 374 The TrackPoint3D PG does not match with Feature PG 375 The Tripping Assoc Point PG does not match with Profile System PG 375 The WireBody2 PG does not match with ProfileSystem PG 376 The WireBody2 PG does not match with StandAlone Stiffener PG 377 There is a duplicate relationship between the same two objects 313
620
Index
There is more than one analysis load case folder 446 There is more than one B0 block inside the DB 387 There is more than one parent in the DB for a child Assembly 388 There is more than one unassigned members folder 447 The proxy does not have a parent 134 Too many flavors have been created for non-symbol objects 473 Turn Feature Angle is very small 81 Turn feature missing primary leg association 81 Turn Feature not associated to two legs 82 TurnPoint can have one or two LineFeatures associated with it 50 TurnPoint is not associated to a Point 51
U
Understanding Database Integrity 31 Unexpected failure in GeomOperations module 174 Unnecessary object is added to the To Do List 314
W
WBS Item does not have a parent 51 WBS Project does not have a parent 52 What's New in Database Integrity 29 Workflow for Addressing Database Integrity 33 Wrong ComponentToSupportedPort Relation 194 Wrong reference collection relation to member for end port @end 595 Wrong reference collection relation to member for end port @start 595
621