Finish Work Page
- Update copyright message to specify theme - Add hard & soft skills and project descriptions to work page - Comment out WIP research and projects pages of portfolio - Fix capitalization & plural of i18n IDs - Change "About Us" to "About Me" in navbar - Update generated html files
This commit is contained in:
Sravan Balaji
@@ -3,12 +3,12 @@ title: "Work Experience"
|
||||
---
|
||||
|
||||
{{< rawhtml >}}
|
||||
<!-- RIVIAN: ADAS Controls Internship (2020) -->
|
||||
<div class="row align-items-center">
|
||||
<div class="col-md-12">
|
||||
<hr>
|
||||
</div>
|
||||
</div>
|
||||
<!-- RIVIAN: ADAS Controls Internship (2020) -->
|
||||
<div class="row">
|
||||
<div class="col-md-6">
|
||||
<div class="row">
|
||||
@@ -18,12 +18,100 @@ title: "Work Experience"
|
||||
</a>
|
||||
</div>
|
||||
<div class="col-md-8">
|
||||
<div class="row">
|
||||
<div class="col-md-12">
|
||||
<h2><b>Rivian</b></h2>
|
||||
<h3>ADAS Controls Intern</h3>
|
||||
<h4>Remote</h4>
|
||||
<h5><i>June 2020 - August 2020</i></h5>
|
||||
<h2><b>Rivian</b></h2>
|
||||
<h3>ADAS Controls Intern</h3>
|
||||
<h4>Remote</h4>
|
||||
<h5><i>June 2020 - August 2020</i></h5>
|
||||
<p>
|
||||
<b>Hard Skills:</b>
|
||||
<ul>
|
||||
<li><a href="https://www.mathworks.com/products/matlab.html" target="_blank">MATLAB</a></li>
|
||||
<li><a href="https://www.mathworks.com/products/simulink.html" target="_blank">Simulink</a></li>
|
||||
<li>Atlassian Products - <a href="https://www.atlassian.com/software/jira" target="_blank">Jira</a>, <a href="https://www.atlassian.com/software/confluence" target="_blank">Confluence</a>, <a href="https://bitbucket.org/product/" target="_blank">Bitbucket</a></li>
|
||||
</ul>
|
||||
<b>Soft Skills:</b>
|
||||
<ul>
|
||||
<li>Public Presentation</li>
|
||||
<li>Design Documentation</li>
|
||||
<li>Professional Communication</li>
|
||||
</ul>
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="col-md-6">
|
||||
<div id="rivian-3">
|
||||
<div class="card section-bg">
|
||||
<!-- MIL TEST CASE GENERATION -->
|
||||
<div class="card-header">
|
||||
<a class="card-link" data-toggle="collapse" href="#mil_test_case_generation">
|
||||
<b>Model-In-Loop Test Case Generation</b>
|
||||
</a>
|
||||
</div>
|
||||
<div id="mil_test_case_generation" class="collapse" data-parent="#rivian-3">
|
||||
<div class="card-body">
|
||||
<p>
|
||||
<p><b>Problem</b></p>
|
||||
<p>
|
||||
Existing software components needed to be tested to ensure that requirements were being met.
|
||||
</p>
|
||||
<p><b>Task</b></p>
|
||||
<p>
|
||||
My job was to translate software component requirements into Model-in-Loop unit tests in Simulink.
|
||||
</p>
|
||||
<p><b>Result</b></p>
|
||||
<p>
|
||||
Created Model-in-Loop test cases for ~50 requirements using <a href="https://www.mathworks.com/products/simulink-test.html" target="_blank">Simulink test</a>. I was able to identify and resolve 7 issues at the model level to prevent them from reaching in-vehicle testing. To improve testing, I created a script to automatically run all test cases and generate a report for easy identification of issues. Also created documentation in <a href="https://www.atlassian.com/software/confluence" target="_blank">Confluence</a> to streamline future test case generation.
|
||||
</p>
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<!-- SIMULINK SOFTWARE INTEGRATION -->
|
||||
<div class="card-header">
|
||||
<a class="card-link" data-toggle="collapse" href="#simulink_software_integration">
|
||||
<b>Simulink Software Integration</b>
|
||||
</a>
|
||||
</div>
|
||||
<div id="simulink_software_integration" class="collapse" data-parent="#rivian-3">
|
||||
<div class="card-body">
|
||||
<p>
|
||||
<p><b>Problem</b></p>
|
||||
<p>
|
||||
Co-worker had developed a new algorithm that needed to be integrated into the Simulink environment for controls software.
|
||||
</p>
|
||||
<p><b>Task</b></p>
|
||||
<p>
|
||||
My job was to communicate with my co-worker to implement the algorithm using the existing signals, processing them, and resolving issues related to <a href="https://www.mathworks.com/products/simulink-coder.html" target="_blank">Simulink Coder</a> C/C++ code generation.
|
||||
</p>
|
||||
<p><b>Result</b></p>
|
||||
<p>
|
||||
I was able to identify and suggest modifications to the algorithm to work within the limitations of <a href="https://www.mathworks.com/products/simulink-coder.html" target="_blank">Simulink Coder</a>. Learned about embedded systems, computing limitations, and how to increase software efficiency to prevent processing time delay.
|
||||
</p>
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<!-- TESTING DATA PROCESSING -->
|
||||
<div class="card-header">
|
||||
<a class="card-link" data-toggle="collapse" href="#testing_data_processing">
|
||||
<b>Testing Data Processing</b>
|
||||
</a>
|
||||
</div>
|
||||
<div id="testing_data_processing" class="collapse" data-parent="#rivian-3">
|
||||
<div class="card-body">
|
||||
<p>
|
||||
<p><b>Problem</b></p>
|
||||
<p>
|
||||
Vehicle testing data needed to be processed to evaluate performance against requirements and determine controls parameters to tune.
|
||||
</p>
|
||||
<p><b>Task</b></p>
|
||||
<p>
|
||||
My job was to modify existing data processing scripts to work with new test data.
|
||||
</p>
|
||||
<p><b>Result</b></p>
|
||||
<p>
|
||||
I was able to map the signals from new test data logs to work with the existing scripts and manually calculate intermediate signals that were not recorded. This allowed me to generate plots that could easily be compared to previous test runs. From these plots, I identified potential issues that could be investigated by the controls team.
|
||||
</p>
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
@@ -62,7 +150,7 @@ title: "Work Experience"
|
||||
<li>Network Communication</li>
|
||||
<ul>
|
||||
<li><abbr title="Transmission Control Protocol">TCP</abbr> and <abbr title="User Datagram Protocol">UDP</abbr></li>
|
||||
<li><a href="http://www.mqtt.org/new/wp-content/uploads/2009/06/MQTT-SN_spec_v1.2.pdf" target="_blank"><abbr title="MQ Telemetry Transport for Sensor Networks">MQTT-SN</abbr></a></li>
|
||||
<li><a href="https://mqtt.org/mqtt-specification/" target="_blank"><abbr title="MQ Telemetry Transport for Sensor Networks">MQTT-SN</abbr></a></li>
|
||||
</ul>
|
||||
</ul>
|
||||
<b>Soft Skills:</b>
|
||||
@@ -158,11 +246,11 @@ title: "Work Experience"
|
||||
<p>
|
||||
<b>Hard Skills:</b>
|
||||
<ul>
|
||||
<li>Python and Django Web Framework</li>
|
||||
<li><a href="https://www.python.org/" target="_blank">Python</a> and <a href="https://www.djangoproject.com/" target="_blank">Django Web Framework</a></li>
|
||||
<li><abbr title="REpresentational State Transfer">REST</abbr> <abbr title="Application Programming Interface">API</abbr></li>
|
||||
<li>Excel <abbr title="Visual Basic for Applications">VBA</abbr></li>
|
||||
<li><abbr title="Bill of Materials">BOM</abbr> Analysis</li>
|
||||
<li>Atlassian Products - Jira, Confluence, BitBucket</li>
|
||||
<li>Atlassian Products - <a href="https://www.atlassian.com/software/jira" target="_blank">Jira</a>, <a href="https://www.atlassian.com/software/confluence" target="_blank">Confluence</a>, <a href="https://bitbucket.org/product/" target="_blank">Bitbucket</a></li>
|
||||
</ul>
|
||||
<b>Soft Skills:</b>
|
||||
<ul>
|
||||
@@ -176,6 +264,84 @@ title: "Work Experience"
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="col-md-6">
|
||||
<div id="rivian-2">
|
||||
<div class="card section-bg">
|
||||
<!-- BILL OF MATERIALS ANALYSIS -->
|
||||
<div class="card-header">
|
||||
<a class="card-link" data-toggle="collapse" href="#bill_of_materials_analysis">
|
||||
<b>Bill of Materials Analysis</b>
|
||||
</a>
|
||||
</div>
|
||||
<div id="bill_of_materials_analysis" class="collapse" data-parent="#rivian-2">
|
||||
<div class="card-body">
|
||||
<p>
|
||||
<p><b>Problem</b></p>
|
||||
<p>
|
||||
Rivian had an existing process for analyzing bill of materials data that needed to be further developed and maintained.
|
||||
</p>
|
||||
<p><b>Task</b></p>
|
||||
<p>
|
||||
My job was to communicate with project management to determine and implement improvements to mass and cost analysis.
|
||||
</p>
|
||||
<p><b>Result</b></p>
|
||||
<p>
|
||||
I improved the existing Excel Macro to check for inconsistencies between parent and child items so mass and cost was not double counted. Additionally, improved the user interface by adding macro buttons to allow for quick filtering of pivot tables and highlight potential discrepancies.
|
||||
</p>
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<!-- INTERNAL WEBSITE -->
|
||||
<div class="card-header">
|
||||
<a class="card-link" data-toggle="collapse" href="#internal_website">
|
||||
<b>Internal Website</b>
|
||||
</a>
|
||||
</div>
|
||||
<div id="internal_website" class="collapse" data-parent="#rivian-2">
|
||||
<div class="card-body">
|
||||
<p>
|
||||
<p><b>Problem</b></p>
|
||||
<p>
|
||||
Requirements management in <a href="https://www.jamasoftware.com/" target="_blank">JAMA</a> was very much a manual process to check for inconsistent relationships between the different types of requirements.
|
||||
</p>
|
||||
<p><b>Task</b></p>
|
||||
<p>
|
||||
I proposed an automated system that would enforce relationships set by the systems engineering team and highlight issues that required manual intervention.
|
||||
</p>
|
||||
<p><b>Result</b></p>
|
||||
<p>
|
||||
I designed and implemented an internal-use website that collected and displayed data from business systems like <a href="https://www.jamasoftware.com/" target="_blank">JAMA</a>. This made use of <a href="https://www.jamasoftware.com/" target="_blank">JAMA</a>'s <abbr title="REpresentational State Transfer">REST</abbr> <abbr title="Application Programming Interface">API</abbr> to automatically pull requirements metadata and enforce the determined relational rules. Additionally integrated Bill of Materials analysis macro into website so users would receive the processed spreadsheet via email. Front-end design was written in HTML and back-end scripts were written in <a href="https://www.python.org/" target="_blank">Python</a> using the <a href="https://www.djangoproject.com/" target="_blank">Django Web Framework</a>.
|
||||
</p>
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<!-- IT Service Desk -->
|
||||
<div class="card-header">
|
||||
<a class="card-link" data-toggle="collapse" href="#it_service_desk">
|
||||
<b>IT Service Desk</b>
|
||||
</a>
|
||||
</div>
|
||||
<div id="it_service_desk" class="collapse" data-parent="#rivian-2">
|
||||
<div class="card-body">
|
||||
<p>
|
||||
<p><b>Problem</b></p>
|
||||
<p>
|
||||
Rivian's previous IT service desk in <a href="https://www.quest.com/products/kace-systems-management-appliance/" target="_blank">KACE Systems Management</a> had issues tracking the status of tickets resulting in an <abbr title="Service-level agreement">SLA</abbr> met percentage of ~75%.
|
||||
</p>
|
||||
<p><b>Task</b></p>
|
||||
<p>
|
||||
My job was to migrate the IT service desk to <a href="https://www.atlassian.com/software/jira" target="_blank">Jira</a> and improve the ticket tracking process.
|
||||
</p>
|
||||
<p><b>Result</b></p>
|
||||
<p>
|
||||
I created custom automation rules to assign tickets based on request type and location. Created queues and reports to track response time, workload, request types, and other metrics. These efforts resulted in an <abbr title="Service-level agreement">SLA</abbr> met percentage of ~95%.
|
||||
</p>
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<!-- RIVIAN: Vehicle Integration Intern (2017) -->
|
||||
@@ -218,6 +384,60 @@ title: "Work Experience"
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="col-md-6">
|
||||
<div id="rivian-1">
|
||||
<div class="card section-bg">
|
||||
<!-- REQUIREMENTS MANAGEMENT AND SYSTEM DIAGRAMS -->
|
||||
<div class="card-header">
|
||||
<a class="card-link" data-toggle="collapse" href="#requirements_management_and_system_diagrams">
|
||||
<b>Requirements Management and System Diagrams</b>
|
||||
</a>
|
||||
</div>
|
||||
<div id="requirements_management_and_system_diagrams" class="collapse" data-parent="#rivian-1">
|
||||
<div class="card-body">
|
||||
<p>
|
||||
<p><b>Problem</b></p>
|
||||
<p>
|
||||
Rivian needed an organized way of tracking interfaces between components and managing requirements.
|
||||
</p>
|
||||
<p><b>Task</b></p>
|
||||
<p>
|
||||
My job was to create system architecture models to help distribute and track requirements from the vehicle level to component level. Additionally, these requirements needed to be managed and distributed via DOORS Next Generation.
|
||||
</p>
|
||||
<p><b>Result</b></p>
|
||||
<p>
|
||||
I was able to speak with managers of various vehicle subsystems to understand cross-system signal interfaces. These conversations were translated to system architecture models so teams could understand what signals they are consuming and outputting. To aid in cross-team communication, I created custom report templates in DOORS Next Generation.
|
||||
</p>
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<!-- SIMULATION DATA ANALYSIS TOOL -->
|
||||
<div class="card-header">
|
||||
<a class="card-link" data-toggle="collapse" href="#simulation_data_analysis_tool">
|
||||
<b>Simulation Data Analysis Tool</b>
|
||||
</a>
|
||||
</div>
|
||||
<div id="simulation_data_analysis_tool" class="collapse" data-parent="#rivian-1">
|
||||
<div class="card-body">
|
||||
<p>
|
||||
<p><b>Problem</b></p>
|
||||
<p>
|
||||
Rivian had collected simulation test data and needed to see the effect of changing vehicle parameters on performance metrics, without re-running expensive tests.
|
||||
</p>
|
||||
<p><b>Task</b></p>
|
||||
<p>
|
||||
My job was to develop a tool that could translate the collected data into a simple user interface to analyze how to optimize vehicle performance.
|
||||
</p>
|
||||
<p><b>Result</b></p>
|
||||
<p>
|
||||
I designed and developed a GUI program in Java that provided the user with sliders for the input vehicle parameters. The tool would then interpolate the performance metrics from the collected points using a neural network determined multi-variate function. The GUI tool then outputs plots showing the effect of changing each input on the projected performance output.
|
||||
</p>
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="row align-items-center">
|
||||
|
||||
Reference in New Issue
Block a user