Table of Contents
This project team will design, integrate and build a Portable Command Post system that will be deployed to on-site emergency or disaster locations where images, communications and data are needed. This system will need to access mission critical databases by using networks and communication servers. A PC that is optimized for viewing station command center information will need to be defined and integrated. Since this system will be utilized for on-site situations, this system must be portable, wireless and weather resistant. The communications will use broadband wireless networks. Internal components must be protected from adverse environmental conditions.
- Project Name
- Portable Command Post
- Project Number
- Open Architecture Control Systems
- Start Term
- End Term
- Faculty Guide
- Professor George Slack (EE dept)
- Faculty Consultant
- James Stefano (EE dept)
- Primary Customer
- Pictometry - Visual Intelligence TM
- Customer contact
- Charles Mondello,
- firstname.lastname@example.org, 585-486-0093
Project Readiness PackageThe P08371 Project Readiness Package.doc defines customer needs and expectations, project deliverables (including time frame), budget, and personnel / organizations affiliated with the project. It will serve as the primary source of information for students necessary during Phase 0 (Planning) to develop a SD I plan and schedule including specific deliverables and due dates. The Project Readiness Package will also support Faculty evaluation of project suitability in terms of depth, scope, and student / faculty resources by discipline.
|Team Member||Discipline||Role||email address|
|Rick Chadwick||ME||Team Leademail@example.com|
This outline for the posting of team created documents follows the general product development process presented in the textbook "Product Design and Development" by Ulrich and Eppinger.
Portions of the team documents have been prepared by a DPM student prior to the launch of this project. This information is intended to help get the team started with a first draft needs assessment and work breakdown structure. The team members can adapt this information as the project progresses.
Keep in mind that everything you include in this web tree is visible to the world and the general public. If you have documents that reflect work in progress, or contain data that has not been fully vetted, then it may be better to include those internal working documents in the private section of the web tree, or in the project repository proper, outside of the web tree. Note that anyone with Guest or higher memberhsip in your project can read your entire project repository. Anyone with an Editor or higher membership can makes changes to your repository. All Observer members can view, but not edit, the web portion of your repository.
These links provide a basic starting point for your team to prepare a comprehensive web site about your project.
After you get started on the project, you may want to replace these introductory paragraphs with a photograph of your team. Near the conclusion of your design project, you may also wish to include a photo of your finished product.
As you conclude the project, include links to all of your finished and fully polished documents here. The previous sections of the web site contain the entire design history of your project. This section contains the finished products. Add more links as needed.Layout of Parts in Case(pdf)