| 1 | | = Systems Manual: 2537 Guide to Systems Engineering |
| | 1 | = Systems Manual: 2537 Guide to Systems Engineering = |
| | 2 | |
| | 3 | == What’s in a Name? == |
| | 4 | The systems engineer/lead is a nebulous but well-defined role: at first glance, the job descriptions are vague and unclear, but anyone who has been a (good) systems engineer immediately is able to grasp the boundaries of the role and realize precisely what things fall into the domain of the systems lead and what falls only into their sphere of concern, but not their sphere of influence. If you don’t understand a part of the role, ask a mentor! Most have worked with or as a systems engineer, even if they’re not in the technical field (read: don’t be afraid to ask even NEMO mentors about this technical role). |
| | 5 | |
| | 6 | The systems engineer is primarily responsible for the successful execution of projects from start to finish, especially the main robot project; this is a technical position, wherein they manage all aspects of the entire project (but not certain logistical aspects--this is covered by the project manager). |
| | 7 | |
| | 8 | == Explicit Responsibilities == |
| | 9 | There are some parts of the job that are spelled out specifically: |
| | 10 | * developing the robot design |
| | 11 | * managing design through tools such as CAD, BOM, etc. |
| | 12 | * maintaining interfaces/interface specifications |
| | 13 | * space allocations |
| | 14 | * field of view allocations |
| | 15 | * ports/IO list |
| | 16 | * discovering and dealing with systemic problems as they arise (except those that are the responsibility of the project manager) |
| | 17 | * risk analysis/mitigation/trees |
| | 18 | * critical path diagrams (to look for single point of failures, etc.) |
| | 19 | |
