I am the knowledge manager and librarian for the NESDIS Documents Online Collaboration System (NESDOCS). This role involves maintaining all enterprise level documents; determination of inclusion of office and project level documents; and assurance that documents meet accessibility requirements. Another critical aspect to this work is configuration management. I actively ensure that people can only access the current version of documents while at the same time retaining legacy versions. The scope of these activities applies to nearly 80 documents, including essential policies, procedures, and plans. While I am in charge of NESDOCS, I do have two contractors who assist me in maintaining the website that allows individuals to access documents.I am the Configuration Change Request (CCR) Coordinator, shepherding new or modified documents from cradle to grave. This starts with helping individuals write a CCR, then presenting it and the document to the Configuration Control Board (CCB) Manager for recommendation to the CCB members. They then review the document and vote for approval. The CCB Chair determines the final concurrence, which results in the document becoming official. This process can take three to four months, and involves interaction with a wide variety of organizations. My relationship with all parties involved is excellent, and has reduced CCR approval times by approximately one month.I co-lead the process management of the NESDIS enterprise risk board (ERB) and risk pre-board. For the latter, I am a part of a group of deputy directors and risk managers that determine if a risk should be elevated to the enterprise level. This requires me to know what is happening in all offices so I can provide input if a risk needs to be elevated. For the former, I prepare the material that the OSAAP Deputy Director needs to present before the ERB.

Responsible for all ground terminals' availability analyses for the Laser Communications Relay Demonstration (LCRD) technology demonstration. These include deterministic and stochastic calculations, obtaining required data from multiple sources (component vendors, JPL, White Sands Complex, GSFC testing), and drafting of reports for each ground terminal. The final products are internal CDRL documentsLead RMA (Reliability, Maintainability, & Availability) Engineer for the Space Network Ground Segment Sustainment (SGSS) project. For this project I am responsible for writing all RMA requirements (detailed in the Mission Assurance Requirements Level 1 document); reviewing all RAM deliverables from the contractors (including CDRL documents); providing additional analyses to the Project Management Office when necessary; maintaining and adjusting safety & mission assurance (SMA) activities to the cadence of the project (cost and schedule)SECRET clearance for access to confidential documents, contractor sites, and government restricted installations.

I worked in the Office of Defects Investigation (ODI) of the National Highway Traffic Safety Administration (NHTSA). ODI is responsible for identifying and conducting investigations into alleged safety defects in motor vehicles and motor vehicle equipment.My responsibility was to analyze reliability, quality, and defects for the determination of unreasonable risk to motor vehicle safety. This quantitative analysis extended from the evaluation of initial owner complaints to internal issue evaluations (IE) to public investigations (PE). I considered engineering aspects of manufacturers’ service bulletins (TSB), trending reports, technical papers, and vehicle owner complaints (VOC). Identification of common-cause failures and safety defect patterns, and their associated investigations was an important part of my role.The primary output of my work was initiating manufacturers to issue TSB or official recalls (RQ), ensuring vehicle safety to consumers. Engineering methods were critical to accomplish this, but this was complemented by interaction and partnership with manufacturers and suppliers. When the manufacturer initiated a recall, I was responsible to evaluate it with respect to NHTSA collected data.I had relationships with government agencies, safety-related societies, and general industry to contribute and keep abreast of safety technology.I performed and managed aspects of my analyses using several proprietary software programs (however, some are built on commercial architecture used in other industries). I am fluent in the Microsoft Office suite, Lotus Notes, and other standard productivity software packages, and used these constantly. I regularly drafted reports, papers, and gave presentations to upper management, enabling them to make data-driven decisions.

As a member of the RAM-C department supporting the PMS 501/505 Littoral Combat Ship (LCS) program, I was responsible for being aware of ship critical failure modes, and performing quarterly updates to RAPTOR models in order to assess the performance of the fleet. Data for these models came from LCSRON, sea trials, and active duty. Results were validated using proven engineering methods and published quarterly as the program Reliability, Availability, & Maintainability (RAM) report.I was a key figure in the PMS 378T program for the next generation Navy aircraft carrier (Gerald Ford class). Besides being a standing member of the CVN 78 Developmental Testing Working Group, I was responsible for the collection of legacy systems' failure data (OARS) for use in RAPTOR models. In addition, I maintained the reliability block diagrams for the 10 new critical systems (including EMALS, JBD, AAG, AWE, and DBR). These models were used for evaluating the performance of new systems' testing results with respect to their requirements. (Actual performance of these systems is classified, but I am interested to see if my availability models were accurate).In order to perform my duties, I used a variety of software programs. I am an expert with the Microsoft Office suite (including Project and Visio) and used that constantly. I used RELEX, RAPTOR, and BlockSim for reliability block diagram models, and ExtendSim for process modelling.Noteworthy, is that within a matter of months I developed a working knowledge of naval systems in general and the LCS program in particular. Because of my quick grasp of this different industry (compared to space systems or motorcycle engineering), I was promoted to be a part of the aircraft carrier program, a more complex system than almost any other warfighter.

Responsible for reliability and risk asses ment as part of the Mission Assurance Services Contract II (MASC II and Safety & Mission Assurance Services (SMAS) contracts at NASA Goddard Space Flight Center (GSFC). This support was for spacecraft, satellite, ground system, and rocket system projects at various NASA centers (Goddard Space Flight Center, Ames Research Center, Jet Propulsion Laboratory).I was chosen to serve as the spacecraft reliability lead, answering directly to the CSO for a class D mission, LADEE ($100 million). I was responsible for reliability deliverables and assessments for all spacecraft sub-systems. I needed to interact with both NASA Ames Research Center engineers and spacecraft subcontractors (including international companies). In addition, I served on the Payload Safety Working Group (PSWG).I served as the spacecraft and mission systems / reliability engineer for a class C mission, ICESat-2 ($800 million). I was part of the systems engineering staff and was responsible for all reliability deliverables, in addition to any assessments requested of me (for example, being part of the fault management working group). I worked with the science team, the design engineers, ground systems team, and other specific individuals - the NASA version of an Integrated Product Team (IPT). I prepared various documents including program plans, which detailed milestones and schedules.Besides significant participation in the above two missions, I was involved with LDCM, MSL (Curiosity rover instrument suite), MAVEN ($650 million), JWST, ARES, and TIRS. I did not do any particular analysis for these missions - sometimes they were FMEA; other times it was reviewing a designers' PSA; even working with the systems engineering team to create a test regime that supported a PRA. The scope of my work depended on where the project was along its life-cycle timeline and what analyses were needed at that time.

Teamwork played a key role in my work. I worked closely with design engineers, systems engineers, mission operations, stakeholders, vendors, and scientists. Together we established requirements, perform analyses, and delivered those to the programs and projects of instruments, spacecraft, and missions. This work started at the concept definition phase and went all the way through launch and operations (SEP).Separate from my systems engineering duties, I performed reliability, availability, & maintainability (RAM) analyses for the projects I supported. I used a wide variety of tools and methods to accomplish my job – during vendor acquisition, design phase, operations, on-orbit anomaly resolution, and post-mission analysis. If necessary, I developed custom programs for analyses; if they already existed then I pushed myself to get up to speed.I have the most experience performing Failure Modes and Effects Criticality Analysis (FMECA) and Fault Tree Analysis (FTA). During testing and on operations I have used different Failure Reporting and Corrective Analysis System (FRACAS) programs, depending on the data sources. I worked closely with a team (requesting help from SME when necessary) to perform these latter activities. Other risk analysis and assessment tools I used daily included RELEX, Reliasoft, Weibull++, and Visio. These helped me perform Probabilistic Risk Assessments (PRA); reliability predictions and assessments; Parts Stress and Derating Analysis (PSA); and Worst Case Analysis (WCA).My work involved doing the above and also assessing reports from vendors and outside stakeholders. I have a critical eye for the work of others to make sure the product they deliver is quality and the results are acceptable for the program.My work involved writing reports and giving presentations to senior and project management. Sometimes these presentations included the financial implications of my assessments.

Instructor of freshmen and sophomore level mathematics courses, including Elementary Statistics.

I served as the engineering lead for the development, execution, and data application of customer use surveys. I was responsible for collecting Voice of the Customer (VOC) information and converting that information into project Reliability, Availability, and Maintainability (RAM) design requirements. These requirements were used at the project management level and then flowed down to the sub-system level and eventually to the component level. People consider me a subject matter expert on the use of Palisades Decision Tools suite and Monte Carlo simulations. My expertise was using probabilistic design methods (including Monte Carlo simulation) for setting design requirements and analysis of platform and system group engineering projects. These analyses helped deliver motorcycles to commerce with fewer warranty claims, less warranty costs, and longer lifetime beyond the warranty period. This last piece was part of the feedback loop of getting voice of the customer information. My work also provided critical design information for future products.I am familiar with standard statistic parameters, a wide variety of distribution types, various plot formats, comparison testing methods, interference calculations, regression and correlation, Monte Carlo simulation, and other data analysis and manipulation techniques. I am adept at taking deterministic equations and problems and analyzing them from a probabilistic point- of-view. I am consulted by many engineers for assistance with this design approach.Reliability and Customer Correlation provided guidance on failure mode identification, frequency and severity assignment, and controls identification. This was more than mere FMECA but an entire approach that aided the design, assembly, and service divisions. The department performed risk analyses and provided supporting data for the resolution of test anomalies.

I performed engineering design analyses using Monte Carlo simulations and other statistical techniques; these analyses helped deliver products to commerce. Deliverables were typically given to senior engineers but sometimes also presented to engineering leadership.An engineering database of customer usage data was in an elementary stage and I improved upon it. The database size contained information on over 10,000 data points. Data was more easily accessible and its structure allowed for future development – both in the amounts of data it could handle and how it could be retrieved.Being a leader and yet working with a team was key part of my largest tasks. I oversaw a police motorcycle data collection project that involved over 100 motorcycles from six different law enforcement agencies, including the Los Angeles Police Department (LAPD) and Florida Highway Patrol. I interfaced with Legal, Police and Fleet Sales, Engineering, police agency risk and legal departments, and actual motor officers. Data was used to set all reliability targets, fatigue design requirements, and extreme boundary conditions for some retail and all police Touring motorcycles.I was the primary instructor and curriculum creator for ECM (Engine Control Module) Database training course. This database was for evaluation of customer usage, engineering design, and warranty comparison. This internal course was offered 45 times over two years; over 275 employees took the course.

I provided support for the Manufacturing Engineering department by developing a project management program, integrated with the company’s SyteLine ERP system, which improved the Manufacturing Engineering department’s accountability and efficiency.

I was a participant in the NSF (National Science Foundation) Research Experience for Undergraduates program, and a member of the High Field Science Group that explored laser-matter interactions (nonlinear topics and ultrafast lasers).