# Presentation: 246652

## Flying Cloud – Extreme Clipper Ship built by Donald McKay

**Flying Cloud – Extreme Clipper Ship built by Donald McKay**

**J. F. Skipper Ph.D.**
**Senior Consultant**
**VITECH Corporation**
- _[Jskipper@vitechcorp.com](mailto:Jskipper@vitechcorp.com)_
**831-224-8002**

**Design Visibility**

## Donald McKay: Businessman (1 of 4)

**Boston Shipyards:  Built clipper ships for the California gold trade:**
**Lightening**
**Great Republic**
**Sovereign Of The Seas**
**Flying Cloud  (1851: NY to SF in 89 days)**
**Operating Environment**
**Rewards: Fast ships were profitable (22 knots)**
**Risk: Loss of ship (cargo / passengers / crew) **
**Extreme seas (Equator / Cape Horn)**

## Donald McKay: Chief Design Engineer (2 of 4)

**Built Models to support innovative designs**
**Hull design**
**Mast / sail design**
**Clear Unambiguous Vision**
**Ship design**
**Ship construction**
**Ship operations**
**Design Reviews**
**6AM Every Morning **
**Decisions / communications were immediate**

## Donald McKay: Production Manager (3 of 4)

**Standards**
**Collaboration **
**Design / Build / Integration Process**
**Shipwrights (Master Craftsman / Apprentice)**
**Integration and Test**
**Design / Build: ****	****Donald McKay**
**Sea trials:   ****	****Captain Larkin McKay**

## Donald McKay: Transformed Vision into Design into Extreme Clipper Ship (4 of 4)

**Donald McKay: Transformed Vision into Design into Extreme Clipper Ship ****(4 of 4)**

**        **

**Footnote: Personal Tragedy**
**    ****- Patriotism, Politics and Poverty**

**Vision****	****	****	****	****	****Operations****	**
**   ****Models****	****	****	****          Sea Trials**
**      ****Systems Design ****	****	****       Captain and crews**
**         ****Detailed Design                         Integration and test**
**                                    ****Components**

**Chief Design Engineer:**
**Cognitive Dissonance**
**- Risks**
**- Design Reviews**

## Design Challenges of Today

**How do we obtain greater visibility of the design?**
**How do we obtain increased collaboration?**
**Design Team**
**Product Development Teams**
**Integration and Test**
**How do we achieve more design iterations?**
**How do we identify risk and focus key people on them to reduce the risks?**
**How do we decrease the time and costs of the engineering design-production process?**

## Solutions:

**Models**
**Product / Process / Scenarios/ I&T/**
**Visible (working models published, read only)**
**Support design / production  integration**
**Horizontal: Data  exchange - similar tools**
**Vertical: Data exchange – different levels**
**Executable**
**Standards**
**Design Maps**
**Test cases derived from scenarios**
**Specifications derived from models**

## 1.  Program Models

**1.1 Program Manager / Chief Design Engineer Conceptual Design**
**1.2 Systems Design **
**1.3 Detailed Design, Production, Integration and Test**
**1.4 Launch, Deliver, Operations and Maintenance**
**1.5  Aggregate Program Models**

## 1.1 Program Manager / Chief Design Engineer Conceptual Design

**Customer**
**Needs**

**Conceptual Design**

**Operating**
**Environment**

**Technology**

**Proven Subsystems**
**Technologies**

**Specialty**
**Engineering**

**Trade**
**Studies**

**Design**
**Strategies**

**Design**
**Process**

**Production**
**Process**

**Product**
**Concepts**

**Conceptual Design**

## 1.2 Systems  Design

**1.2 Systems  Design**

**Systems**
**Design**

**Operations**
**Scenarios**

**Program**
**Office**

**Schedule**

**Budgets**

**Vendors/Partners/**
**Suppliers**

**Process**
**Design**

**Produce**
**Design**

**Systems Design**

**Customer**
**Specifications**

**Suppliers**

**Reusable **
**Flight Certified  **
**Components**

**Note:**
**Collaboration Required**

## 1.3 Detailed Design, Production, Integration and Test

**1.3 Detailed Design, Production, ****Integration and Test**

**Detailed**
**Design**
**Disciplines**

**Mechanical**

**Software**

**Electronics**

**Communications**

**Integration**
**And Test**

**Maintain**
**Budgets and**
**Interfaces**

**Scenarios**

**Test Cases**

**Subsystems from **
**Subcontractors**

**Detailed Design **
**(Models Embedded in Tools)**

**Production**
**(Models Embedded  in Tools)**

**Testing**
**(Models Embedded in Tools)**

## 1.4 Launch, Delivery, Operations and Maintenance

**Remove from**
**Service**

**Product **
**Acceptance**

**Upgrades**

**Launch/Delivery**

**Operations**

**Maintenance**

**Simulators**
**Training**
**Documentation**

**Launch and Operations**

## 1.5 Aggregate Program Models

**1.5 Aggregate Program Models**

**Systems Design**

**Detailed Design**

**Integration and Test**

**Launch and Operations**

**Production**

**Program Office**

**REQUIRED:**
**-Executable Product Models**
**Tailored Process Models**
**Model Visibility**
**-Information Exchange**
**-Collaboration**
** **

**Launch and Operations**

**BOM**
**- Satellite**
**- Sensor Package**
**- Communications**
**Launch Facilities**

**Risks**

## 2. Product and Process Models

- 2.1  Scenarios (process models)
- 2.2  Product Models (deliverables)
- 2.3  Process Models (design / production process)

##         Note: All Programs Are Unique Fill in what you know, solve for what you do not know.

**New Challenges:  **
**John Kennedy: “Vision . . .send a man to the moon.”**
**New Technology: **
**Stealth-Kelly Johnson’s Skunk Works: (2 prototypes / 14 mo)                   - Flight control actuators from the F-111**
**	****- Flight control computer from the F-16**
**	****- Inertial navigation system from the B-52**
**	****- Servomechanisms from the F-15 and F-111**
**	****- Pilot’s seat from the F-16**
**Reverse Engineering : Circling Torpedoes**
**Specified Components: “Shall use Raytheon radars” **
**Fixed price bid on R & D: Early days of composites**

## 2.1  Scenarios (Executable Behavior)

**Use To Create:**
**Concept of **
**Operations**
**Design Issues**
**Risks**

## 2.2  Product Models

***verified by***

***verified by***

***Originating requirements***
***trace to behavior***

***Originating requirements***
***trace to physical components***

***Behavior is allocated to***
***physical components***

***verified by***

**- Object Browser**
**- Object DB**
**- Object Query Language**

## April 2003

*April 2003*

## Product Model

**Design Repository**

**Product Model**

**Integrity Checks:**
**-Requirements “trace to” Functions**** **
**Functions “allocated to” Components**
**Components “perform” Functions**
**Interfaces “connects” Components**
**-Items “carried by” Interfaces**
**Constraints,  Performance, Issues, Risks**
**Budgets**

## 2.3  Systems Engineering Process

**2.3  Systems Engineering Process**

**Primary Concurrent Engineering Activities At Each Layer**

**Source**
**Documents **

**Layer 1**
**(Draft 1)**

**Layer 2**
**(Draft 2)**

**Layer n**
**(Final **
**Specs.)**

**System Design Database**

**Specification & Report Generation**

**Iterate as Required**

**When Layer Completed**

**Iterate as Required**

**When Layer Completed**

_**Originating **_
_**Requirements Analysis**_

**System Design Database**

**Specification & Report Generation**

**System Design Database**

**Specification & Report Generation**

**Initial Requirements for this layer are embodied in the model passed from the prior layer**

**Initial Requirements for this layer are embodied in the model passed from the prior layer**

## Process Models

## 3. Standards – Used To Facilitate the Exchange of Information

**Systems Design**

**Detailed Design**

**Integration and Test**

**Launch and Operations**

**Production**

**Program Office**

**Launch and Operations**

**Risks**

**     **

**       **

**Program Information**
**- Design resides in multiple distributed DBs**
**Multiple tools / data formats**
**Required:**
**Standard terms**
**Standard conversion routines:**
**Vertical Exchange**
**Horizontal Exchange**
**	**

**Systems Eng AP233**

**Electronics AP210**
**CAD APXXX**
**Electrical XXXXX**

**JIM U’Ren**
**NEED HELP**
**LISTING  STDS**

## 4. Design Map – Used To Navigate The Program Structures

**4. Design Map – Used To Navigate The Program Structures**

**Systems Design**

**Detailed Design**

**Integration and Test**

**Launch and Operations**

**Production**

**Program Office**

**Launch and Operations**

**Risks**

**Requirements**

**Contract**

**WBS**

**Program**
**  ****Project**
**    ****Subproject**

**Organization**

**     ****Budgets**
**Planned     Actuals**

**       ****Schedules**
**Planned     Actuals**

**Work Packages**

**Product BOM**

**Notes:**
**Design Reviews **
**Design is Distributed**
**Map: navigation capability**
**Object network (not relational)**
** ****An Object Query Language is required**

**Documents and **
**Specifications**

**Process Models**

**Example:**
**Satellite **
**Radiation Study**

## 5. Specifications Generated From Models

**5. Specifications Generated From Models**

**Systems Design**

**Detailed Design**

**Integration and Test**

**Launch and Operations**

**Production**

**Program Office**

**Launch and Operations**

**Risks**

**     **

**       **

**SPECIFICATIONS**
**Requirements Document**
**Concept Of Operations**
**SEMP**
**Process Models**
**Product BOM**
**Object Models**
**Risks**
**Issues**
**Constraints**
**Performance Indices**
**Budgets (weight, power.  )**
**Test Plans**
**Interface Specifications**
**Detailed Design Specifications**
**Mechanical**
**Electrical**
**Software**
**Electronic**
**Suppliers**
**Partners**
**User procedures / operations**
** ****. . .**

**Note:**
**Required: Object Query Language**
**Navigate the models**
**Extract information**
**Map information to document outline and format**

## 6. Design Reviews

**6. Design Reviews**

**Systems Design**

**Detailed Design**

**Integration and Test**

**Launch and Operations**

**Production**

**Program Office**

**Launch and Operations**

**Risks**

**     **

**       **

**Schedules**
**Budgets**
**Program Compliance Rules**
**Issues**
**Risks**

**Requirements**
**Operation Scenarios**
**Design Models**
**Test Models**
**Budgets (power, weight, )**
**Interface Specifications**

**Hardware**
**  ****Part Numbers**
**  ****Diagrams**
**  ****Weights**
**  ****Volume**
**Software**
**  ****Packages**
**  ****Classes**
**  ****Methods**
**  ****Interfaces**
**Electronics**
**  ...**
**  ...**
**  **
**  **

**Design Reviews**
**Visible Models     (VITECH CORE2NET)**
** ****Interface Exchange Requirements (IERs)**
** ****Risks**

**I&T**
**  ****- Test Plans**
**  ****- Test Procedures**
**  ****- Test Results**
**   ****- Issues**

**Facilities**
**Materials**
**Skilled workers**
**Subcontractors**
**Process**

**IERs**

## 7. Design Iterations

**7. Design Iterations**

**Systems Design**

**Detailed Design**

**Integration and Test**

**Launch and Operations**

**Production**

**Program Office**

**Launch and Operations**

**Risks**

**     **

**       **

**Benefits:**
**Concurrency of Design**
**Improved Interfaces**
**Collaboration**
**Quality**
**Integrity**
**Risk**
**Reduce Time To Delivery**
**Reduced Program Costs**

## SUMMARY:  Design Visibility

- Flying Cloud: Extreme Clipper ship built by Donald McKay

**SUMMARY:  Design Visibility**

## Engineering Design Principles			(1 of 3)

**Model Driven Design**
**Program models**
**Operational Scenarios (executable)**
**Product Models (executable)**
**Process Models (executable)**
**Trade Studies (based upon executable models)**

## Engineering Design Principles 		    (2 of 3)

- Standards
- Facilitate Horizontal Information Transfer between Tools
- Facilitate Vertical Information Transfer between Tools
- Maps
- Distributed design exists in multiple tools and formats
- Required to navigate the aggregate program
- Risks
- Integral to the product and process models
- Produce Specifications From Models
- Text documents  not generated from models typically do not represent the current design

## Engineering Design Principles 		(3 of 3)

- Information Exchange Requirements (Interfaces)
- Program data should be “posted” (visible)
- IERs are bi-directional
- IERs must be provided in context
- IERs must be provided continuously as the design evolves
- The capability to concurrently view multiple design models (product and process)  is required
- Allows PM/CDE to focus upon RISKS
- Frequent design iterations leads to:
- quality,
- Integrity of both the product and process, and
- reduction of both program time and costs

## Design Visibility:  Discussion

**Design Visibility:  Discussion**

**        **

**Vision****	****	****	****	****	****Operations****	**
**   ****Models****	****	****	****          Sea Trials**
**      ****Systems Design ****	****	****       Captain and crews**
**         ****Detailed Design                         Integration and test**
**                                    ****Components**