Final Technical Report Section I Technical Status Report

Final Technical Report DATE: 10/27/2009

Section I Technical Status Report

Technology Investment Agreement 2007-376 between

the Advanced Technology Institute (ATI) and

Bender Shipbuilding and Repair Co., Inc. for

Second Tier Shipyard Design Enhancement Project III

Bender Shipbuilding and Repair Co., Inc. Austal USA, Inc.

Bollinger Shipbuilding Marinette Marine

Northrop Grumman Ship Building Todd Pacific Shipyards

VT Halter Marine Elliot Bay Design Group

Genoa Design International Gibbs & Cox

Murray & Associates, Ltd. ShipConstructor Software, Inc.

ShipConstructor Software USA, Inc. Autodesk

Art Anderson & Associates

Approved for public release; distribution is unlimited

Data included in this report is considered Category B Government Purpose Rights

AGREEMENT NO: 2007-376 Page2

2/1/2012

Project Overview Bender Shipbuilding and Repair Company, Inc. presented a collaborative effort, the third and final phase of the Second Tier Shipyard Design Enhancement Project. The objective of this project was to continue to develop the design software of choice amongst the second tier shipyards (ShipConstructor) with enhancements to streamline and maximize the efficiency of the previous efforts undertaken to fully integrate the design solution. Bender Shipbuilding led the project team with the continued participation of eight shipyards and four design agents all of whom have independently selected ShipConstructor as their product modeling software. The shipyard team represents the core of second-tier shipyards in the U.S., and further includes NGSS Avondale. Bollinger Shipyard, Marinette Marine and Austal USA are all second-tier shipyards using ShipConstructor on the LCS program. NGSS has used ShipConstructor on the Navy LHR-8 project Deepwater designs. The design agents represent the core group of design contractors used by the collaborating shipyards. The shipyards functioned as a steering committee to define in detail the requirements of the software changes and improvements at a higher level than the proposal. The shipyards and design agents acted as beta testers of the various modules as they were developed and released for testing. The success of the past phases of the STSDEP has shown that the largest single collaborative effort by U.S. shipyards to enhance their capabilities was extremely successful, and warranted another effort to further enhance and integrate the design software in response to needs expressed by the participating shipyards. The shipyards involved in this project have identified a need for the tools specified in the Software Improvement Plan in order to enhance their bottom line by making the engineering effort more efficient, better integrated, faster and cheaper.

Project Goals and Objectives This was the second phase of the STSDEP III project. The phase proceeded with the software development for the integration of AutoDesk’s Inventor Software and ShipConstructor, as well as creating a Component Model Library. The overall objectives of this project were:

• Develop a common library of equipment models using standardized design methods and terminology that will be available to all team members. This task involved all of the shipyards and design agents, along with AutoDesk and SSIUSA. The effort used a combination of ShipConstructor and AutoDesk Inventor to develop a library of equipment and outfitting components that can be shared by all project participants, significantly decreasing design time on subsequent projects. The models were developed using a standardized design methodology and standard, CPC based terminology.

• Develop a direct interface between AutoDesk Inventor and ShipConstructor equipment databases so that Inventor is an integrated equipment development tool. AutoDesk, SSI and SSIUSA spearheaded the effort to accomplish the task. The task focused on using the ShipConstructor API to develop the interface. The task goal is to allow ship designers to develop equipment and component models using the powerful parametric tools in AutoDesk Inventor and have the parts instantly integral into in the ShipConstructor database and automatically populated into the Equipment module.


2/1/2012

Technical Progress This is the Final Technical Status report for the subject agreement. Technical efforts and major developments for the period September 20, 2008 through October 27, 2009 include:

• Completed the Project Website

• Executed AutoDesk Inventor Training Classes

• Completed development of the Component Model Library web site

• Finalized Integration efforts between Inventor and SSI’s Equipment module

Major Developments

Component Model Library The Component Model Library was designed to be a repository for users to upload, download, and comment on shipyard part models. The library is a web driven application that is accessible to registered users through a web browser. The database on the server will hold the models, reference documents and their attributes as defined by the Common Parts Catalog. The web application has an interface to the CML where users are able to search for models and share ideas with other users on any particular part. The figure below shows the overall CML Workflow diagram.

Figure 1 Concept CML Web Site Workflow

Web Site Workflow Models created in ShipConstructor, AutoCAD, or Autodesk Inventor are given specific attributes by the user when they are uploaded to the website. These attributes are defined through the CPC, which is located on the same web server as the host CML. When a user uploads a design, they are required to drill down through the CPC part design class to find the appropriate


2/1/2012

descriptor for the part along with the associated attributes. After the design is uploaded, other users will be able to search for this part through keyword searching or category browsing. Models can be downloaded through the site and imported into ShipConstructor with all of their attributes that were predefined. Registered users are able to browse the CML freely, and to view and make comments on specific files or any of their revisions. Activities include the ability to upload files and make revisions on any of their already existing files with revision comments. Moderators will be created for managing the users and models uploaded. These moderators will be able to create other moderators, validate uploaded designs, and have access to recent activity logs. The concept will follow the same scheme as Wikipedia, where the users are mostly self regulated, and written collaboratively by volunteers allowing articles to be changed by almost anyone with access to the Web site. http://en.wikipedia.org

CML Website After a long process of development, the website has been launched. The web application’s user interface has been created and modified during the milestone period. The way in which a user navigates through the site continues to develop and be modified. The website’s template has been designed and is being implemented on every page of the CML. The Figure below shows the updated website user interface and CML home web page

http://cml.shipconstructor.com

Figure 2 CML Website Homepage

http://en.wikipedia.org/

http://cml.shipconstructor.com/


2/1/2012

Figure 3 CML Web Login / Registration

As noted in previous reports, guests are able to register with the site and become users in the database. A login system has also been created for users to validate themselves and to store personal data in the database. The Figure above shows the user interface for the CML Login/ Registration screen.

Figure 4 CML Admin/ Management Interface

A user management system has also been constructed allowing for the creation of users and administrators. Administrators can be created through the database and have access to an Administrator section for content management. The Figure above shows the Administrator interface. The library has provided an avenue to apply integration and compatibility with the Common Parts Catalog (CPC) core functionality. The actual part entry forms now require certain basic


2/1/2012

part definition information to be filled out before a valid part can be uploaded. The required data input fields are to allow alignment with CPC data. This ensures that at least the minimum information is available to satisfy the CPC definitions.

Figure 5 Appling CPC Attributes

This figure shows one possible hierarchy of the CPC to determine where a particular part may fall. Required attributes are denoted in red. Once the user determines the location in which his part falls, a form is generated with fields for every attribute listed as shown in the Figures below.

Figure 6 CPC Required Fields

Figure 7 Upload Form Generated from CPC Figure 8 Non-Attribute Field in the Upload Form


2/1/2012

The Figures above provide one example of the possible forms generated according to where the part exists in the CPC hierarchy. Multiple documents and the related description can be uploaded along with the part drawing. If the user wishes to upload more than three documents about a part, the user can edit the part and upload more documentation or delete existing documentation.

Figure 9 Component Part Listing

The Figure above describes the part listing of all the parts currently in the CML. Parts listed here, by default, will be sorted according to last upload date as shown. Primarily the users will be able to browse the parts through a part list such as this, or through the CPC part class hierarchy if desired. The user will be able to sort the listing according to part name, author name, or date uploaded. A search bar at the top allows users to search for parts based on part name and description. The Figure below is an example of a search result.

Figure 10 Listing Returned After a Search


2/1/2012

This functionality required that the basic CPC backend hierarchy be copied into the CML database along with the other CML specific tables. The entire CPC part class hierarchy tables as well as the Data Element Dictionary (DED) tables were parsed and included as part of the core CML databases. Along with these tables, the specific CML tables were created when they contained valid user data and valid CML part data. The CML specific part data was interpreted from the ShipConstructor equipment item requirements for data. Those fields that ShipConstructor would require for a valid equipment part were considered “required” for the CML as well. Data that had a corollary between ShipConstructor and CPC were combined into a single definition.

Figure 11 CML Part Page

The Figure above displays a part page with related revision history of the particular part. The revision history is tracked in the database currently, along with the user information (who


2/1/2012

uploaded the revision, when, the type and size of the uploaded file). Included below revision history area is the part attribute data. As noted, parts that are in red on the list are there for CPC part compliance. The website database contains the full CPC data hierarchy. The hierarchy provides the ability for the user to upload any other CPC specific information they want as well. All valid attributes are available for a given part based on its location in the part hierarchy. There is a download button on this page to provide the ability to actually retrieve this part from the website for local use. In this same section, users can attach any type of documentation they feel should be included with the part. This can be any type of basic document (pdf, doc, txt, and dwg). If there are documents attached to the part, a download button will be available for the documents as well as the actual part. Just below the user information is a section to rate the given part. This is available on a per-user basis, allowing all users to rate any given part as they see fit. The edit link allows the logged-in user to modify any information for the part without having to upload the data itself (that is what revisions are for). The part page provides a list of who edited the part and at what time. The list allows all users to know who was responsible for the included information. This attribute is useful for giving credit for good information, as well as for tracking down the source of erroneous information, assigning some responsibility for the content. The edit page looks very similar to the upload page except for all of the preexisting data in the fields. Existing documentation can be deleted and new documentation can be uploaded.

Figure 12 Edit Page with Attribute Info Figure 13 Edit Page (continued)

The Figures above are examples of an attributes’ DED definition that provides: a description, input instructions, and examples of data that might be inserted into the attribute field. The user can view this information just by clicking on the attribute name.


2/1/2012

Figure 14 Help and Support Pages

The Help and Support page seen above is designed to assist the user with all aspects of the website that they might have questions about. Every web page has a help section that describes the available features on that page. There is also a Frequently Asked Questions (FAQ) page to address the most common issues. The Contact page allows users to get queries and/or suggestions directly to the CML website staff. Preliminary talks focused on the use of Inventor as the base to create the new components for the model library. However, the project team has decided that the work required to allow the use of Inventor to create the components would only be accomplished at the end of this project, as it would not allow the required time to model the equipment. The majority of the components must and will be modeled in ShipConstructor’s Equipment module. One of the benefits going forward with the use of this tool allows reuse of equipment modeled in Inventor and translated into ShipConstructor.


2/1/2012

Help will be provided through the support page of the site, which describes how the site should be used. A “Frequently Asked Questions” section, or FAQ, will be provided under the support page as well as a list of important contacts regarding the CML. Feedback from the project members also indicated the desire to upload any type of equipment drawings such as: a plain AutoCAD drawing file, a complete ShipConstructor equipment export file, or a stripped down ShipConstructor equipment export file (without end connection location/type information). There has also been implemented the ability to upload a full ShipConstructor equipment export file, and to generate stripped ShipConstructor and plain AutoCAD files for download. Total number of downloads of a part has been implemented as well. Feedback from the project members also included other functionality that was not essential to the core operation of the site, but is being worked on as time permits: Thumbnail images of the uploaded component files are not available yet, but are planned. Printer-friendly pages are currently available, but have not been fully formatted yet to produce well structured output (the part pages can still be printed fine, but may not be structured fully by default). Manufacturer version tracking numbers have not been implemented yet, but this data can be located in the CPC attribute information for parts.

Component Model “Wish List” During the Joint Project Meeting in New Orleans, the team was requested to compile a list of parts that could be uploaded to the website. The project goal was to upload 1000 component models into the data base. Currently there are 1187 components uploaded. The associated figure displays a number of component models that have been targeted as potential “wish list” items.

Figure 15 Example Equipment Models


2/1/2012

Inventor / ShipConstructor Integration The Second Tier Shipyard Design Enhancement Program funded the development of a direct interface between Autodesk Inventor and ShipConstructor equipment database so that Inventor is an integrated equipment development tool. Autodesk, SSI and SSIUSA were tasked to accomplish the goal. The task focused on using ShipConstructor’s API (Application Programming interface) to develop the interface. The goals allow CAD designers to develop equipment and component models using the powerful parametric tools within Autodesk Inventor and have the parts incorporated in the ShipConstructor database and automatically populated into the Equipment module of ShipConstructor.

Completed Project Tasks: Develop Best Practices Document October 2008 Develop Training AVI’s of Inventor Course October 2008 Design Integration Architecture October 2008 Develop Prototype Inventor Module November 2008 Provide Installation Guide and Install Support November 2008 Deliver Inventor Training December 15, 2008 Develop Prototype Integration Module December 19, 2008

Populate Component Model Library August 31, 2009 Demonstrate Integration Module August 31, 2009 Support is on-going, and will continue for NSRP users as they use Inventor to model parts that get added to the Component Model Library. This Inventor modeling support continued through December 2008 and January 2009. The data format for exchange between ShipConstructor and Inventor has been defined and developed in Inventor leveraging existing functionality from ShipConstructor software. The interface has been tested to validate the desired functionality of ShipConstructor launching Inventor with the desired part from the ShipConstructor Catalog.

Inventor Software Distribution As mentioned in the section above, Autodesk has provided the “cost shared” Inventor software to the project. Autodesk provided installation and training guide documentation for use by the project participants. ShipConstructor was provided the information as well, and posted it on the NSRP project management website for download at anytime by any of the project team members.

Inventor Training The Inventor component “wish list” provides Autodesk Inventor trainers with a list of components that are relevant to real ship design needs. Autodesk developed a specific training curriculum tailored to this focused approach, and initiated the training plan by region.


2/1/2012

Installation Guide Avatech Solutions produced a guide for the installation of Autodesk Inventor and supporting programs. This document outlines each step necessary to install the software and set up the workspace environment for all modeling tasks. An Avatech Solutions application engineer will also provide web-based support for the installation process on pre-determined days that will be announced to all participants via email.

Figure 16 Instructional DVD for Inventor by Avatech Solutions

Inventor Training Tutorial Avatech Solutions worked with Autodesk to support the development of the custom Inventor / ShipConstructor interface. Avatech Solutions participated in the testing and model creations processes for this new application. The tutorial provided contains over nine (9) hours of video. For advanced CAD users the nine hours of content requires at least 18 hours of learning.


2/1/2012

Figure 17 Advanced Inventor Training Documentation

Best Practices The “Best Practices” document outlined the basic modeling processes for the Inventor application. The document contains recommendations for creating simplified versions of shipboard components and detailed descriptions of customized templates and drawing standards. This document was used as one of the instructional manuals for the customized training.

Training Summary The NSRP – Inventor Core Concepts class was delivered in three locations across the country to shipbuilders representing eight different shipyards. The class covered the basic functionality of Autodesk Inventor and the advanced processes of creating shipboard components to support a national shipbuilding library. The best practices for creating shipboard components was delivered during this training . All students participated in modeling equipment examples based upon these practices. All students seemed to adapt to and embrace the parametric modeling process of Autodesk Inventor. The students understood the advantages of using Inventor along with AutoCAD and ShipConstructor to produce the manufacturing models and designs.

Web Based Support Avatech Solutions has provided Web-Based support sessions for all users. The first web-based support sessions focused on the installation of the Inventor application. Follow-up sessions tracked the designer’s progress after the training class. The support was delivered on a scheduled basis using the Avatech Solutions’ Webex account.

Inventor /ShipConstructor Integration Interface The integration has been developed to allow Inventor and ShipConstructor to provide feedback to each other. The software communicates parameters and key attributes from ShipConstructor to Inventor. The interface has been developed to work with Autodesk Inventor 2009 and drive the class functions for ShipConstructor’s API.

System Architecture Overview

Figure 18 High Level Flow Chart


2/1/2012

Use Cases

Figure 19 Inventor Use Cases

Realized Benefits to Industry and Navy The benefit to industry and the Navy can be seen first by cost and schedule benefits with the increased usage of the ShipConstructor Software in second tier, commercial shipyards. However, many shipyards have moved or are moving toward the use of ShipConstructor on Navy projects. These include:

° Austal (LCS) ° Lockheed Martin lead (LCS) ° NGSB ° VT Halter ° Bollinger (Coast Guard)

ShipConstructor software is also used at NGSS on the Coast Guard’s NSC hulls one and two as well as many other IRAD projects in shipyards. Improving the software used on these projects, the result should help reduce the designing and modeling costs associated with these vessels for the Navy. The development of a common library of equipment and outfitting models using standardized design methods and terminology is now available to all team members. The collaboration of all shipyards and design agents, along with AutoDesk and ShipConstructor USA, resulted in a library of parts that can be utilized in future projects, with the potential to significantly reduce the design time required on subsequent projects. The project will help increase the use of the CPC, while standardizing the attributes the vendors supply to shipyards and design groups. With a common goal, the level of CAD will increase as will commonality across platforms.

Technology Transfer The project provided technology transfer during the NSRP Joint Panel meeting that was held December 10th – 11th, 2008 in New Orleans, LA.

Cost Issues Final Cost Share numbers will be reported in the Closeout Documents.


2/1/2012

Project Summary Although the project has experienced some road-blocks, it has progressed to completion. The Inventor deployment, training, and support have been completed. All of the module integration work for the Inventor / ShipConstructor module has been completed and is ready for final delivery. The activation of Component Model Library website has been another key accomplishment. The final content has been installed into the Component Model Library website.


2/1/2012

Section II Business Status Report

Technology Investment Agreement 2007-376 between

the Advanced Technology Institute (ATI) and

Bender Shipbuilding and Repair Co., Inc. Second Tier Shipyard Design Enhancement Project III

Agreement Summary Information Total Amount of the Agreement: $9,510,241 Total Estimated NSRP ASE Project Funding of the Agreement: $4,420,000 Total Estimated Recipient Cost Share: $5,090,241 Total Funds Obligated: $4,420,000

Project Resource/Cost Information: The following resources/costs are applicable to this project for the period December 20, 2008 through October 27, 2009:


2/1/2012

Man Hour and Material Costs

Status of Man Hours, Material & Personnel - Phase II

Company

Man Hours Provided

This Period **

Cumulative Man Hours Provided **

Significant Material

Costs This Period

Cumulative Material

Costs

List of Personnel Working This

Period

Bender 575 6031 261 19,920 Veith, Schimmer,

Garlotte, Branch SSI 0 20105 SSIUSA 454 6134 Roberts, David,

Bollinger 46.3 106.3 480 3792.45 Fanguy, Knight,

Matherne, Clement

Marinette

Marine 0 680

NGSS 0 3687 0 15,256 VT Halter 0 1560 0 Todd Pacific 0 1214 0 Austal USA 0 640 0 Gibbs & Cox 0 1432 0

Elliot Bay

Design 0 1086 0

Murray & Associates

0 1248 0 1500

Genoa Design 0 1500 0

Art Anderson

Assoc. 0 1660 0

AutoDesk 0 1824 0 UW - Marinette 0 640 0

Univ. of South

Alabama 0 640 0 0

Atlantic Marine 0 615 0


2/1/2012

Status of Milestones

STATUS of MILESTONESRevised on 10-27-2009

PHASE MILESTONE

NUMBER

1 1Kick-Off Meeting w/Mtg Minutes and Required Project Plans - 100%

1 2 Software Development Interim Status Report #1 - 100%

1 3Quarterly Technical and Business Project Status Report #1 - 100%






1 9Phase Final Technical and Business Project Status Report - 100%

Phase II





2 14 Software Development Interim Status Report #7 - 100% a. Component Model Library Module b. Autodesk Inventor Integration Module

2 15Quarterly Technical and Business Project Status Report #7 100%

2 16 Phase II Final Technical and Business Project Statu 100% 100% a. Deliver Component Model Library Module b. Deliver Autodesk Inventor Integration Module c. Project Report Template

07-376 NSRP ASE Second Tier Shipyard Design Enhancement Project III

Percentage Completed

During this Period

Cumulative Percentage Completed MILESTONES and ASSOCIATED

DELIVERABLES

AGREEMENT NO: 2007-376

2/1/2012

*IR&D matching funds should be identified separately and not included in the Overhead line.

Interest Earned $ N/A

Cost Share Provided by Project ParticipantsCost share in the amount of -$ is provided for this reporting period.

Cumulative cost share to date for the project is 5,090,241$

Type A Type B Cumulative Cumulative Cumulative Total

Resource Type Private Sector Private Sector Public Sector less (Federal Sources) (Non-Federal Sources) participant provided Public Sector Matching Funds Matching Funds funding provided funding

Cash - (including donations from state or local governments) Examples include the outlay of funds to support the proposed statement of work through the acquisition of material or equipment and paying company cash for subcontractor labor or consultant cost. 43,740$ 158,465$ 202,205$ Labor costs - associated with allowable labor cost categories that are not billed directly to program funds (e.g., SP Panel members) 25,815$ 93,526$ 119,341$ Expenses - associated with allowable labor cost categories that are not billed directly to program funds (e.g., ECB member travel) 3,500$ 3,500$

Overhead - (excluding labor related fringe benefits) General and Administrative ServicesSBIR and STTR in accordance with Government guidelines 750,000$ 750,000$ IR&D - (Internal Research and Development) 26,000$ 26,000$ M&PE - (Manufacturing and Production Engineering)Estimated Implementation Costs for activities specifically included in participant proposals

Use of Existing equipment - (estimated fair market value)Use of Existing software - (estimated fair market value) $181,927 $3,457,468 3,639,395$

$5,597 $344,203 349,800$ Intellectual property - (market value)Space - (land or buildings)

Totals 1,007,079$ 4,083,161$ -$ 5,090,241$ *IR&D matching funds should be identified separately and not included in the Overhead line.

The following summarizes the cumulative cost share provided for this project by category:

Participant-Provided Resources

Funding Resources

In-Kind Resources

AGREEMENT NO: 2007-376 Page 21

2/1/2012