Professional Documents
Culture Documents
Document SPEC-0064
Revision A
REVISION SUMMARY:
SPEC-0064, Revision A ii
Systems Engineering Plan
Table of Contents
Preface ........................................................................................................1
1. SYSTEMS ENGINEERING ................................................................................... 2
1.1 DESIGN REQUIREMENTS FLOW DOWN ...................................................................... 2
1.2 CONCEPTUAL DESIGNS ........................................................................................... 2
1.3 INTERFACES ........................................................................................................... 2
1.4 ERROR BUDGETS.................................................................................................... 3
1.5 STANDARDS ........................................................................................................... 3
1.6 SPECIFICATIONS DOCUMENTS .................................................................................. 4
1.7 PERFORMANCE MODELING ...................................................................................... 4
1.8 QUALITY ASSURANCE PLAN .................................................................................... 4
1.9 ACCEPTANCE TEST PLANS ...................................................................................... 5
1.10 INTEGRATION PLANS ............................................................................................... 5
1.11 DOCUMENT CONTROL ............................................................................................. 5
2. SYSTEMS ENGINEERING DELIVERABLES....................................................... 8
2.1 PROJECT STARTUP DELIVERABLES .......................................................................... 8
2.2 CONCEPTUAL DESIGN REVIEW DELIVERABLES ......................................................... 8
2.3 PRELIMINARY DESIGN REVIEW DELIVERABLES.......................................................... 8
2.4 CRITICAL DESIGN REVIEW DELIVERABLES ................................................................ 9
3. SYSTEMS ENGINEERING DURING CONSTRUCTION AND IT&C .................. 10
3.1 CONFIGURATION MANAGEMENT AND CHANGE CONTROL ......................................... 10
3.2 QUALITY ASSURANCE AND QUALITY CONTROL PLAN EXECUTION ............................ 10
3.3 INTEGRATION TEST AND COMMISSIONING ............................................................... 10
Preface
The genesis of the first two sections of this document dates back to the writing of the ATST Design and
Development proposal to the National Science Foundation. Its original title was “Systems Engineering
Deliverables”. It has now been recast as part of a project “specification” (SPEC) document and
designated the “Systems Engineering Plan” as it continues to accurately reflect systems engineering
activities to date as well as those anticipated in the near future. Only a few minor changes have been
made to the original document during this recasting, mostly modifying terminology slightly to maintain
consistency with the nomenclature subsequently adopted by the ATST project.
Section three of this document is new. It describes systems engineering during the construction phase, as
the scope of the original “Systems Engineering Deliverables” was limited to the Design and Development
phase of the project. The roles and responsibilities of systems engineering during the construction phase
are summarized here, including references to other project documents that describe these aspects of
systems engineering in detail.
1. SYSTEMS ENGINEERING
Designing a facility as complex as the ATST requires concurrent engineering, i.e. the design and
development activities must proceed in parallel. As the designs evolve, there must be continuous
adjustment of requirements and rebalance of the interfaces between different subsystems. Also, during
the design and development phase the project will need to prepare procedures and plans that will be
required for the construction phase. To accomplish these goals in an efficient manner that ensures
technical success and controls cost and schedule, the project will have a strong systems-engineering
program. Systems engineering staff will work with project management, the scientific staff, and the other
engineers to accomplish the activities described below.
1.3 INTERFACES
Project Management will set up a division of responsibilities for the project. Based on the conceptual
designs, systems engineering will develop a matrix to define where interfaces exist between responsible
groups. Then interface control documents (ICDs) will be developed for each interface4.
An ICD is an agreement, essentially a contract, between two or more groups in the project. It may be
between two groups of project staff, or it may be between the project and a contractor or partner
organization. The document must not only define the interface, but also identify who does what. Each
ICD must be negotiated much like a contract would be. If a contractor will perform the work, the ICD
becomes part of the contract.
1
SPEC-0001 – The ATST Science Requirements Document, Rimmele, et al.
2
SPEC-0066 – Requirements Flowdown, Rob Hubbard
3
ICD N2 Chart
4
ICD Status Report
In general, ICDs cover optical, mechanical, electrical and software interfaces, as appropriate. All the
ICDs for a given subsystem should be controlled by the time of the preliminary design review (PDR) for
that subsystem.
A formal revision process will be set up to control changes to the ICDs. There will often be situations
where a change in an ICD affects the plans of several groups, including ones that may not have been part
of the original agreement. Therefore, as changes in ICDs are required, it is important that these changes
be communicated with all affected groups. In some cases, when an ICD is changed, a revision of
schedules, budgets or error budgets may be required.
1.5 STANDARDS
Systems engineering will work with the other engineering staff to develop hardware and software design
standards, documentation standards7, and standardized terminology8.
A simple example of a design standard is the need to define whether designs will be in English units or
metric units. Standards will be developed for both hardware and software to ensure the use of common
components, compatible subsystems, and a modular approach wherever possible. This is important to
help control life-cycle costs for the facility. These include operating costs, maintenance costs such as
staffing requirements and the quantity of spare parts required, and the cost to upgrade systems as new
technology becomes available.
Documentation standards will include standard drawing formats and file types, as well as standard
templates for project documents such as ICDs, integration plans, etc. Systems engineering will also
5
SPEC-0009 – ATST System Error Budgets, Rob Hubbard
6
DIQ CASE 1a, Diffraction Limited 500 nm; DIQ CASE 1b, Diffraction Limited 630 nm; DIQ CASE 2, Seeing
Limited On-disk; DIQ CASE 3, Seeing Limited Coronal
7
SPEC-0002 – Document Drawing and Control Plan, Ruth Kneale
8
SPEC-0012 – Glossary and Acronym List, Ruth Kneale
compile a listing of standardized names and definitions. When writing ICDs or contracts it is very
important that the terms used are clearly defined in a manner that is consistent across the entire project.
9
SPEC-0025, ATST Quality Assurance and Quality Control Plan, Rob Hubbard
10
SPEC-0065, QA/QC Requirements, Mark Warner and Rob Hubbard
The project quality assurance plan will be written by systems engineering, with technical assistance from
other engineering staff.
11
SPEC-0038 – ATST Commissioning Plan, Eric Hansen
• Error Budgets
• Technical Reports
• Drawings
• Quality Assurance Plan
• Acceptance Test Plans
• Integration Plans
In addition to the responsible engineer and engineering manager, systems engineering will sign approval
for release and revision of:
• Interface Control Documents
• Specifications Documents
• Drawings
• Quality Assurance Plan
• Acceptance Test Plans
• Integration Plans
Systems engineering will also coordinate the collection and control of documents required for reviews.
The following is a possible document set required for ATST reviews. This set should also be created for
every major system (telescope, each instrument, facility) review. Every subsystem should have the same
document set (and associated review) if possible, especially if the plan includes sending the design or the
development out for contract.
A. Design Review Generated Documents
1. Introduction/Committee/Charge/List of Deliverables
2. Design Review Product Overview
3. Committee Report
4. Response to the Committee
B. Systems Engineering Deliverables
1. Design Requirements Document (final at CoDR)
2. Interface Control Documents (final at PDR)
3. Test Plan and Procedures (final at CDR)
4. Error Budgets (final at CDR)
C. Engineering Team Deliverables
1. Design Document
(CoDR=Conceptual Design, PDR=Preliminary Design, CDR=Detailed Design)
2. Trade Studies
3. Prototypes
D. Project Management Deliverables
1. Work Breakdown Schedule