ppt课件-v i r g i n i a( s s n774) class submarine（v我r g n(s s n774)类潜水艇）.pptVIP

* * * Applications interfaced to LEAPS FKS * Applications interfaced to LEAPS Navy Common Cost Model * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * DISTRIBUTION STATEMENT A : Approved for public release; distribution is unlimited DISTRIBUTION STATEMENT A : Approved for public release; distribution is unlimited Ship Product Model Data Exchange Ben Kassel Naval Surface Warfare Center Carderock Division * 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. Who wants product data… What data do they want …  When do they want it? AP 215? AP 216? AP 227? AP 218? AP 214? AP 239? IFC? PDF? NATIVE? 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. Assuming the product data exists, how do you get it where it is needed? Native, IGES, STEP AP203, The shipbuilding STEP application protocols? For now the shipbuilding application protocols just are not available. An interim approach for data exchange is needed immediately! * Product Model data is the combination of 3D geometry and non-graphic attributes to define ship objects such as a piece of equipment, deck, bulkhead, etc. Product Model data can be organized to define interim products and ultimately the entire ship. Advocates anticipate substantial economies from Product-Model-based design, construction, and service-life support activities due to better integration and reduction of engineering effort to locate, verify, and transform information. Part System Definition (Caterpillar 3512, Starboard Main Engin