Job Title: Controls Systems Engineer
Location: Fridley MN
Duration: Long Term
Job Description:
1. Application knowledge - Either have be able to quickly understand genset control systems high level application knowledge as a baseline skill set. Minimal set of skills is prior machinery control system development.
2. Knowledge of the systems V diagram phases and be able to utilize this process in the development of control systems.
a. Gather requirements from uses cases and interviews.
b. Review existing designs and create a full systems approach document that outlines how our system should be updated/modified to meet the new requirements.
i. Includes System/SW design documentation updates of baseboard control system and HMI interface updates Tools interface updates and manual updates.
ii. Includes Failure Mode Effects Analysis (FMEA) reviews to ensure safety and failure mode robustness.
iii. Hold design reviews for design and approach sign offs within a cross functional team including engineering leadership.
c. Coordinate updates with other cross functional team members for implementation
i. Work with software developers service teams and other cross functional teams that may need to be part of the implementation process that require support from the systems team.
d. Design level systems testing
i. Make test plans that verify systems designs are implemented correctly. Typically this is done on a bench setup.
ii. Either coordinate or perform execution of the test plan depending on circumstances.
iii. Analyze test results to ensure the results are passing tests. If issues are found log the issues and coordinate fixes as needed along with retesting.
iv. Complete testing to get a full set of passing test results closing all issues
e. Requirements level systems testing
i. Similar to the design level systems testing process above but this is verifying the systems level testing requirements which frequently will be done on machine/genset verifying performance requirements that bench testing may not be able to verify.
3. Safety - Be aware of safe machine operations/needs being able to test with potentially live 480V nearby while testing. Safety should be always considered.
4. Project management - Be able to know how to
a. make a schedule of their tasks
b. track to that schedule and
c. Escalate if off of schedule working with leadership to know how to mitigate any schedule gaps particularly if the critical path of the project is off schedule.
5. Team collaboration - Be able to work with a global team. Core development locations will include Minnesota and India so a flexible time zone alignment will be required.
6. Documentation & communication - must be able to
a. Communicate well - bring up and drive any topics that require discussion to gain alignment and clarity.
b. Documentation - A significant amount of systems engineering requires good documentation including meeting minutes design documents testing documentation etc.
7. Be located in the Fridley MN location since this role wont be 100% remote given the testing needs.
Job Title: Controls Systems Engineer Location: Fridley MN Duration: Long Term Job Description: 1. Application knowledge - Either have be able to quickly understand genset control systems high level application knowledge as a baseline skill set. Minimal set of skills is prior machinery contro...
Job Title: Controls Systems Engineer
Location: Fridley MN
Duration: Long Term
Job Description:
1. Application knowledge - Either have be able to quickly understand genset control systems high level application knowledge as a baseline skill set. Minimal set of skills is prior machinery control system development.
2. Knowledge of the systems V diagram phases and be able to utilize this process in the development of control systems.
a. Gather requirements from uses cases and interviews.
b. Review existing designs and create a full systems approach document that outlines how our system should be updated/modified to meet the new requirements.
i. Includes System/SW design documentation updates of baseboard control system and HMI interface updates Tools interface updates and manual updates.
ii. Includes Failure Mode Effects Analysis (FMEA) reviews to ensure safety and failure mode robustness.
iii. Hold design reviews for design and approach sign offs within a cross functional team including engineering leadership.
c. Coordinate updates with other cross functional team members for implementation
i. Work with software developers service teams and other cross functional teams that may need to be part of the implementation process that require support from the systems team.
d. Design level systems testing
i. Make test plans that verify systems designs are implemented correctly. Typically this is done on a bench setup.
ii. Either coordinate or perform execution of the test plan depending on circumstances.
iii. Analyze test results to ensure the results are passing tests. If issues are found log the issues and coordinate fixes as needed along with retesting.
iv. Complete testing to get a full set of passing test results closing all issues
e. Requirements level systems testing
i. Similar to the design level systems testing process above but this is verifying the systems level testing requirements which frequently will be done on machine/genset verifying performance requirements that bench testing may not be able to verify.
3. Safety - Be aware of safe machine operations/needs being able to test with potentially live 480V nearby while testing. Safety should be always considered.
4. Project management - Be able to know how to
a. make a schedule of their tasks
b. track to that schedule and
c. Escalate if off of schedule working with leadership to know how to mitigate any schedule gaps particularly if the critical path of the project is off schedule.
5. Team collaboration - Be able to work with a global team. Core development locations will include Minnesota and India so a flexible time zone alignment will be required.
6. Documentation & communication - must be able to
a. Communicate well - bring up and drive any topics that require discussion to gain alignment and clarity.
b. Documentation - A significant amount of systems engineering requires good documentation including meeting minutes design documents testing documentation etc.
7. Be located in the Fridley MN location since this role wont be 100% remote given the testing needs.
View more
View less