RP Development Status Coordination (DS N)
Phase B-C
Cluster Content | Status s=started a=agreed c=closed
Product requirements |
general implementation requirements (weight, gen. environmental, recycling, etc.) | A
pre-defined parts | A
functional content (FC) | A
range of functions: number + structure | A
interfaces | A
available space for components | A
required versions | A
diagnosis requirements | A
quality requirements | A
acceptance conditions | A
sample schedule | A
Product solution, implementation and production process |
variant specification | A
functional architecture | A
hardware architecture (system level) e.g. block diagram | A
software architecture (system level) | A
hardware architecture (component level) block diagrams | A
software architecture (component level) | A
investment | A
unit price | A
Configuration and change management |
planned system/software configurations, e.g. depicted as a variant tree. | A
compatibility between system/software functions, e.g. this is important to determine whether configurations are even allowable. | S
configuration of all components clearly agreed (hardware, controller software, test software, application data) | A
status overview version assignment | A
Release notes = information that applies to this special configuration, for example content, history, etc. | A
Product, production process and design process quality management |
risk evaluation of the various planned work packages | A
FMEA results | A
results of process audits about the development sequence | A
QA monitoring and management of control activities | A
Results of current design status reviews | A
Validierungsergebnisse | S
results of computer simulation | A
calculation results | A
Project management |
resource planning (availability, qualifications incl. any pending changes in the personnel situation) | A
definition of sub-suppliers and service providers | C
defined delivery status with scope (work packages) and due dates | A
completion status of the various work packages | A
adherence to or failure to meet scheduled deadlines, e.g. monitoring using milestone trend analysis | A
staying within or exceeding planned costs | A
allocation of, for example, material/production costs, overhead cost ratio, etc. | A
project organisation (e.g. responsibility matrix, interfaces), area of responsibility, rules of cooperation | A
information and communication rules like reporting (form, frequency), data communication paths and tools | A