M
M 
M






 



 



m
   m

NSWCCD Intergraph Corporation
ben.kassel@navy.mil ted.briggs@intergraph.com
 

 
 







 







 

Nobody really knows what data they want until
they need it, and then it may be too late. By
the time the need is identified, the source
is located, the formats are agreed upon,
the funding is obtained, and the software
is developed the need is overcome
by events.
Sometimes data exchange is required to support
a process within the shipyard. Sometimes data
exchange is required to support the
establishment of a virtual enterprise.
Sometimes data exchange is required to
deliver data to the Navy as part of a
contract deliverable.

M
  
M

 
M

M
 
M M

M



Assuming the product data For now the shipbuilding

exists, how do you get application protocols
it where it is needed? just are not available.
Native, IGES, STEP An interim approach
AP203, The for data exchange is
shipbuilding STEP needed immediately!
application protocols?

 m 




 ^
 


Ñ Proprietary format graphics

Ñ Proprietary format data
Ñ No linkage between data and graphics
Ñ EXPENSIVE, SLOW, UNTENABLE

ë
 #


 $
"

 
$$ 






!

" " M


Ñ STEP standard graphics

Ñ Attribute data, no product structure
Ñ inimal linkage between data and graphics
Ñ The beginning of the path

Ô
 

%

 




$


"

%
M

Ñ Single STEP standard file

Ñ Integrated product structure, graphics, and data
Ñ Parameterized components
Ñ Logical and geometric relationships

î
 u $
M




 



' (

)%


!& M


Ñ STEP standard graphics

Ñ STEP standard product structure
Ñ STEP standard properties
Ñ Linkage between product structure and graphics
Ñ Potential state of the art achievable today


 u $
M






AP203 or AP214 to define shape.

AP239 to define product structure and 1 2 3 4

the relationships between objects.
11 12 21 22 31 32 41 42 51

52

¦
 u $
M






Ñ Five year effort conducted in annual technically complete increments

Ñ 3-D product model data
Ñ Adjunct data
± Drawings
± anuals
± Shipcheck
± Engineering
Ñ Aggregation of product models and related data from individual
components to define:
± systems
± assemblies
± spaces
Ñ Long-term accessibility and interpretability of the archived digital data
by future generations
½
  
 
M*+
$
m,

Ñ The Fuel Oil System is treated in AP239 as a PART.

Ñ Each component in the system is treated in AP239 as a PART.
Ñ Basically a system can be a part and a part can be a system.
Ñ Systems and assemblies are fundamentally similar. They are an aggregation of parts.


"
%

R
 "
%

u
 67- @%-
%- u%%- =$-<-76


  >+*-?-0
F
8
A A A >+) >+'
u  uu
  >+)-?- 5  !0
F
89  u
A A >'
u 
!  "#$%& '' >'-?- 5  !0
F
8A A A
()*(+,
$   -.#/#%u#-&-0#-+- 67--.#-9#%B-#-$$G-<- @%-
%- %%- =$-76
1&&+&*2  >+3-?-0
F
8
 :A A A >+) >+
u   !

3
4u 5  4

! >+-?-0
F
8  !  uuu
A A A A  >,
 
>,-?-0
F
8  ! 9  u
A A >
 
>-?-0
F
8  !  A A
67-                       
  76 >-?-0
F
8  ! 
uH
u
A A A >+ >
67-7-7-7-7-7-7-7- 4
 -
8
 - 9u 8-7-7-7-7-
7-7-76 67- %#D-#-$$G-<- @%-
%- %%- =$-76
67---- -

-
-u - 5
:-

u -u-u - >,-?-0
F
8
 :A A A >+) >)+
u --76 >)+-?-0
F
8  !  uuu
A A A A  >)'
67----!
5-
-0 -9
u- 0 
- 
------------------ >)'-?-0
F
8  ! 9  u
A A >)*
76 >)*-?-0
F
8  !  A A
67-                        >),-?-0
F
8  ! 
uH
u
A A A >)+ >))
  76


 67--GI-/-D#-B#%B-#;-<%#D-76
67-#-/#-;<-/-=$-76 >,,-?-u 
 
 u
A A G%; >, >,)
>++-?-
  @%-
%- %%- =$ A >,+-?-u 
 
 
 uuu
A A 6*C-D#J )-
>+,-?-
9  u
A A >++ 6*- ,4C-"-C-G%- A  A A
>+'-?-
9u 8 uuu
A A A A  >+, >,)-?-u 
 
 

4  A A A >,+ >))
>,-?-u 
 
 

4  A A A >,+ >
67--.#-9#%B-76  
>-?-
 -.#-9#%B 6C-u -- u

.#-9#%B-+>-8
.- %#D- 
>-?-
9  u
 A > RR
>-?-
9u 8 uuu
 $-<$-
 "
%

Ñ The first slide could be animated to better show need for interim approach:
1. Show current approach with only a few links, mixed mode: IGES, STEP, X L, TXT, «
2 Overlay with the STEP-shipbuilding to-be world ± all links, using ship AP
3. Overlay with interim approach ± all links, AP 214 and AP 239
Ñ Product Structure ± bring in groups of object labeled by what they represent to the user ± system, part, component,
interface, connection
Ñ Need slide talking about PLCS ± use and promise of adoption, etc

R