Roman Religion

Table of Contents

1. Introduction

2. Teams and Leader Responsibilities

3. Design Components

4. Introductory Project

5. Project Selection Process

6. Analysis Report

7. Preliminary Design Review

8. Critical Design Review

9. Final Presentation

10. Conformity Inspection

I. Introduction

The purpose of the detail design class is to provide a design-build-test-operate experience for the student. The requirements for the project that the students select begin with the requirement that the project have a minimum of three subsystems, chosen as a subset of the subsystems used in the project from preliminary design. In addition, it must have more than one sub-assembly; there must be a subset of the requirements that are test-able (with our campus facilities); it must undergo a vibrations test according to the requirements specified by the chosen launch vehicle; and the structure must be tested to failure.

The design component consists of detailed drawings submitted in the context of the configuration management system defined under the Design folder in the Courses drive. More detail of the design component is given in the Design Components section.

The students are required to build their design. This enables them to understand the manufacturability of their paper concept. It also gives them the opportunity to see if their predictions on the performance of their system are good. The build process provides an opportunity for the students to see clearly what the integration issues are in bringing the various subsystems together.

The test component requires the students to write detailed test plans and to perform them with their design prototype. The project should have various subsystem tests as well as tests at the various phases of integration and finally, a fully integrated functionality test, which shows how the system as a whole operates.

The entire design must be supported by analysis based on work done in previous courses as well as on any new material they must learn for their specific design. The analysis section describes in more detail the types of specific analyses required.

II. Teams and Leader Responsibilities

The teams utilize the entire class and are divided into subsystem teams and an integration team. The integration team is composed of the team leaders from each subsystem team and the project lead is the team leader for this team. Each team must also have a person responsible for all the CAD drawings. The responsibilities of the integration team, project lead, team leads and the CAD person are defined below.

Integration Team:

This team is responsible for the system coming together. They must make sure that all integration issues are addressed early and are passed on to the appropriate team for resolution. They are responsible for the overall class budget and schedule (which are compiled based on the individual team budgets and schedules) and for ensuring that the overall budget and schedule are met.

The integration team must maintain the class budget and schedule and is responsible for writing and maintaining interface specifications. They are also responsible for determining the absolute dead-in-the-water due dates for project milestones.

The integration team and the team leaders will meet with the instructors once per week.

The team lead for integration is the project manager for the class.

The integration team is responsible for ensuring that all of the assembly bills of material and drawings are complete. They are also responsible making sure that all of the links work to the drawings or bills of material that they refer to.

This team is much more of a management team than a technical team, however, the team members must also be aware of the technical issues for their team.

Tools used are: Catia - assembly drawings; Microsoft Project - Class schedule; Excel - Budget, all part drawings, part lists, bills of materials (most of the configuration managed items); Paint - import from Catia into Paint (or Word) and place labels, and any other documentation onto assembly drawings; Microsoft Word - requirements document, test plans, test reports.

This team is also the group responsible for ensuring that the presentation comes off as a whole. Typically, each team will create their part of the presentation, however, the presentation must flow as a single project. The integration team is responsible for making this happen. This usually means that they need the team presentations at least one day in advance of the presentation. In general, they will introduce the presentation and conclude the presentation.

This team is responsible for ensuring that the conformity inspection will go well. They do this by doing their own version of the inspection and getting any issues resolved through the teams.

Changes to the design occur frequently through the design process. The integration team ensures that all of these changes are tracked and is the team that is on top of which change is the most current design. They are also responsible for making sure that the impact of any change proposed by one subsystem is understood and accommodated by the other teams.

The integration team is responsible for ensuring that all of the design components are correctly documented and submitted. This includes all test plans, requirements document, bills of material, assembly drawings, drawings, etc.

Team Leader Responsibilities

The team leader is responsible for maintaining the purpose and direction of the team. They must delegate tasks and maintain both the schedule for the team and negotiate the budget with the integration team.

The team leader is responsible for ensuring that all of the bills of material for subassemblies that the team is responsible for are complete; that all of the drawings are released; and that the bills of material link properly to all relevant drawings. They are also responsible for ensuring that