|
|
Child Level:
|
Level Naming Conventions IssuesWhy Conventions? Some object types have functional deliverable similarities. It makes sense to be able to grab the group as easily as an individual. It makes sense to structure the level naming in a way that parallels the logical grouping of objects. Clear conventions allow adding additional object types without causing bad downstream effects. For example, adding a new drainage level that conforms to the in-place convention would probably be processed properly by a Pen Table that targets groups rather than individual objects (see Pen Table Wildcarding). Deviating from Client or Global StandardsThere has to be benefitIf internal design and production is 95% of the project cost and conforming to deliverable standards can take less than 5%, optimizing the production environment makes clear sense. The challenge is to make sure that creating standard deliverables is quick, easy, and reliable. The primary hindrance to this is not conforming to internal production standards. Deviating from internal production standards causes problems in the conformance to client or global standards. Primary Manageable Issues for DeviationsPlottingConforming to Deliverable Standards should be very simple. Pen Tables should fully-acceptable plots without data structure translations. There are a small number of graphic characteristics that can be determined from plots:
Translation to Client's or Global Electronics StandardsBatch Mapping
|
|