Line 4: |
Line 4: |
| <br> | | <br> |
| {{Tree chart/start|align=center|summary= Combined RobotX Team}} | | {{Tree chart/start|align=center|summary= Combined RobotX Team}} |
− | {{Tree chart| | | | | | | |SI| | | | |SI=[[File:Male-2.jpg|center|124px]]<big>'''Marine Science'''<br>[[Subsystems Integrator]]</big>}} | + | {{Tree chart| | | | | | | |SI| | | | |SI=[[File:Male-2.jpg|center|124px]]<big>'''[[Marine Science & Technology | Marine Science]]'''<br>[[Subsystems Integrator]]</big>}} |
| {{Tree chart/end}} | | {{Tree chart/end}} |
| + | |
| + | ==Core Competency== |
| + | *Create Direction, Alignment and Commitment |
| + | *Critical thinking and problem solving |
| + | *Excels at decision-making |
| + | *Primary consultant to Leadership and Planning |
| + | *Recommends Conflict resolution |
| + | *Engages in negotiation |
| + | *High Degree of Adaptability |
| + | *Stress Tolerant |
| | | |
| ==Goals== | | ==Goals== |
| ===Integration Design, Build, and Test Plan=== | | ===Integration Design, Build, and Test Plan=== |
− | *The Project Management(PM) and Systems integrator are responsible for planning, managing, and executing the Integration process. | + | *The Project Management(PM) and Systems integrator (SI) are responsible for planning, managing, and executing the Integration process. |
| *Projects that develop an integration plan have a high degree of success. | | *Projects that develop an integration plan have a high degree of success. |
| *The plan defines the stages of integration, during which system elements are successively integrated to form higher level elements, and eventually the finished RobotX platform. | | *The plan defines the stages of integration, during which system elements are successively integrated to form higher level elements, and eventually the finished RobotX platform. |
| *The integration plan includes descriptions of the required teams, test standards, testing methods, and integration schedule. | | *The integration plan includes descriptions of the required teams, test standards, testing methods, and integration schedule. |
| + | |
| + | ==Technical Assessment responsibilities== |
| + | *Establish event-driven technical planning |
| + | *Identify Test measures and Metrics assessing design success |
| + | *Identify performance measures and Metrics assessing technical progress |
| + | *Determine risk and develop mitigation strategies |
| + | *Propose changes in the technical approach to address risk mitigation |
| + | *Continually measure technical readiness of the RobotX platform |
| | | |
| ====Integrated Test Plan==== | | ====Integrated Test Plan==== |
| *includes design baseline evaluation | | *includes design baseline evaluation |
− | *# critical design parameters | + | *# identifying critical design parameters |
− | *# performance threshholds | + | *# setting performance threshholds |
| *individual Subsystems test plans | | *individual Subsystems test plans |
− | *# suitability tests | + | *# interface tests |
| + | *# functional tests |
| *# effectiveness tests | | *# effectiveness tests |
| *platform performance test plan | | *platform performance test plan |
| *# MOE (measures of effectiveness) | | *# MOE (measures of effectiveness) |
− | *#* maximum operational time | + | *#* maximum time on range without operation intervention |
− | *#* operational goal accomplishment | + | *#* hardware operational goal accomplishment |
− | *# MOS (measures of suitability) | + | *#* AI operational goal accomplishment |
− | *#*subsystem Interoperability | + | *# MOF (measures of functionality) |
− | *#*mean time between operational failure | + | *#*subsystems Interoperability |
− | | + | *#*mean time between Interoperability failure |
− | ==Core Competency==
| |
− | *Create Direction, Alignment and Commitment
| |
− | *Critical thinking and problem solving
| |
− | *Excels at decision-making
| |
− | *Primary Leadership and Planning (leader of leaders)
| |
− | *Leads Conflict resolution
| |
− | *High Degree of Adaptability
| |
− | *Stress Tolerant
| |
− | *Engages in contract negotiation
| |
− | | |
− | ==Technical Assessment responsibilities==
| |
− | *Establish event-driven technical planning
| |
− | *Identify measures and metrics
| |
− | *Identify performance measures assessing technical progress
| |
− | *Determine risk and develop mitigation strategies
| |
− | *Propose changes in the technical approach to address risk mitigation
| |
− | *Continually measure technical readiness of the RobotX platform
| |
| | | |
| == Primary Management Roles and Responsibilities == | | == Primary Management Roles and Responsibilities == |
| ===Requirements Management=== | | ===Requirements Management=== |
− | Requirements are the foundation of the program and requirements management process helps ensure delivery of capability that meets intended mission performance objectives.<br> | + | '''Requirements''' are the foundation of the project and requirements management process helps ensure delivery of capability that meets intended mission performance objectives.<br> |
− | Performance objectives are identified in operational terms at the system level during implementation of the Requirements Definition and Requirements Analysis processes.<br> | + | Performance objectives are identified in operational terms at the system level during implementation of the '''Requirements''' Definition and '''Requirements''' Analysis processes.<br> |
| The Subsystems Integrator has these '''Requirements Management''' responsibilities: | | The Subsystems Integrator has these '''Requirements Management''' responsibilities: |
− | *maintain a current and approved set of requirements | + | *maintain a current and approved set of '''Requirements''' |
− | *thoughtful analysis and management of requirements insuring for system sustainability | + | *thoughtful analysis and management of '''Requirements''' insuring for subsystem integration and system performance |
− | *synchronization with the program’s Configuration Management process to mitigate unintended or unanticipated consequences due to change | + | *synchronization with the program’s Configuration Management process to mitigate unintended consequences due to project change |
| *rigorous documentation of changes to the system performance specification | | *rigorous documentation of changes to the system performance specification |
| | | |
| ===Process Responsibilities=== | | ===Process Responsibilities=== |
− | *tracks requirements changes and maintains traceability of the system performance specification and delivered capability | + | *tracks '''Requirements''' changes and maintains traceability of the system performance specification and capabilities |
− | *traces the high-level requirements down to the system elements through the lowest level of the design as the system design evolves to lower levels of detail | + | *traces the high-level '''Requirements''' down to the system elements through the lowest level of the design as the system design evolves to lower levels of detail |
− | *establishes and maintains a Requirements Traceability Matrix (RTM) | + | *establishes and maintains a '''Requirements''' Traceability Matrix (RTM) |
− | *#capturing all requirements in the system performance specification | + | *#capturing all '''Requirements''' in the system performance specification |
| *#documenting their decomposition/derivation and allocation history | | *#documenting their decomposition/derivation and allocation history |
| *#document rationale for all entries and changes | | *#document rationale for all entries and changes |
− | *work with PM to track cost, schedule, and performance impacts associated with requirement changes and/or growth | + | *work with Project Management Team to track cost, schedule, and performance impacts associated with '''Requirements''' changes |
| | | |
| ===Risk Management=== | | ===Risk Management=== |
Line 98: |
Line 100: |
| **performance | | **performance |
| **physical | | **physical |
− | *consists of interrelated functions that maintain consistency between product configuration information | + | *consists of interrelated functions that maintain consistency between project configuration information |
− | #Personnel
| |
| #Responsibilities and Resources | | #Responsibilities and Resources |
− | #Training requirements
| |
| #Administrative meeting guidelines including a definition of procedures and tools | | #Administrative meeting guidelines including a definition of procedures and tools |
| #Baselining processes | | #Baselining processes |
| #Configuration control and Configuration status accounting | | #Configuration control and Configuration status accounting |
− | #Naming conventions | + | #Naming conventions |
| #Audits and Reviews | | #Audits and Reviews |
| #Configuration Identification | | #Configuration Identification |
| #Configuration Change Management | | #Configuration Change Management |
− | #Configuration Status Accounting | + | #Configuration Status Accounting |
− | #Configuration Verification and Audit
| |
| | | |
| ===Interface Management=== | | ===Interface Management=== |
| *careful interface documentation ensures proper '''function''' and '''interoperability''' | | *careful interface documentation ensures proper '''function''' and '''interoperability''' |
| *ensures that all the development teams document all internal and external interface requirements | | *ensures that all the development teams document all internal and external interface requirements |
− | *documents Requirements changes in accordance with the Configuration Management Plan | + | *documents '''Requirements''' changes in accordance with the Configuration Management Plan |
| *communicates interface information to team counterparts responsible for affected systems and system elements | | *communicates interface information to team counterparts responsible for affected systems and system elements |
| *drives coherent testing to verify expected performance and eventually operational performance | | *drives coherent testing to verify expected performance and eventually operational performance |