Industry Insights
WEI’s Women in Energy Symposium and Celebrating American Business Women’s Day
September 22, 2017
Today is American Business Women’s Day. This day is about networking, celebrating broken barriers and looking ahead to further progression of working women. For me, this day is personal.
This day of recognition comes with WEI’s Women in Energy Symposium (WiES) just around the corner, Nov. 1-3. There, I will join a diverse mix of energy industry professionals in discussions around networking, recruitment and the state of women in the energy industry.
I will be speaking on the Sponsorship vs. Mentorship Panel with Nancy Arroyoavila of Pacific Gas & Electric, Kristin Stathis from Portland General Electric and Tim Swanson of FortisBC. I look forward to discussing the differences and similarities of these two aspects of career advancements. It is an important topic, yet it is somewhat surprising to me that we are still having this discussion.
I started engineering school 40 years ago, and we had the same conversations then that we are having now: How do we encourage more diversity in the industry? I wouldn’t have thought then that this would still be a challenge 40 years later. On one hand, the industry has changed dramatically and has seen so much improvement for women engineers. At the same time, there is much work left to do.
This is why mentoring and sponsoring is so vital.
For me, mentoring is about helping someone become their best self – helping them tap into their unique strengths – and giving those mentees resources. It’s a way to help other women hone their skills, see insights, and develop as people and leaders. The parallel to this – and just as important – is sponsoring. This is to be someone’s advocate, to champion their cause.
The purpose of today is “to bring together businesswomen of diverse occupations and to provide opportunities for them to help themselves and others grow personally and professionally through leadership; education, networking support and national recognition.”
I believe we have an opportunity to do just that. Women are now sprinkled throughout the male-dominated energy industry. Women in this industry have the opportunity to guide and inspire more female engineers. While some biases still do exist, there are ways to level the playing field. That’s where mentoring and sponsorships come in.
Hear more by tuning into the Sponsorship vs. Mentorship Panel on Nov. 2 and register for WiES here.
This day of recognition comes with WEI’s Women in Energy Symposium (WiES) just around the corner, Nov. 1-3. There, I will join a diverse mix of energy industry professionals in discussions around networking, recruitment and the state of women in the energy industry.
I will be speaking on the Sponsorship vs. Mentorship Panel with Nancy Arroyoavila of Pacific Gas & Electric, Kristin Stathis from Portland General Electric and Tim Swanson of FortisBC. I look forward to discussing the differences and similarities of these two aspects of career advancements. It is an important topic, yet it is somewhat surprising to me that we are still having this discussion.
I started engineering school 40 years ago, and we had the same conversations then that we are having now: How do we encourage more diversity in the industry? I wouldn’t have thought then that this would still be a challenge 40 years later. On one hand, the industry has changed dramatically and has seen so much improvement for women engineers. At the same time, there is much work left to do.
This is why mentoring and sponsoring is so vital.
For me, mentoring is about helping someone become their best self – helping them tap into their unique strengths – and giving those mentees resources. It’s a way to help other women hone their skills, see insights, and develop as people and leaders. The parallel to this – and just as important – is sponsoring. This is to be someone’s advocate, to champion their cause.
The purpose of today is “to bring together businesswomen of diverse occupations and to provide opportunities for them to help themselves and others grow personally and professionally through leadership; education, networking support and national recognition.”
I believe we have an opportunity to do just that. Women are now sprinkled throughout the male-dominated energy industry. Women in this industry have the opportunity to guide and inspire more female engineers. While some biases still do exist, there are ways to level the playing field. That’s where mentoring and sponsorships come in.
Hear more by tuning into the Sponsorship vs. Mentorship Panel on Nov. 2 and register for WiES here.
Si è verificato un errore nell'elaborarazione del modello.
The following has evaluated to null or missing:
==> authorContent.contentFields [in template "44616#44647#114455" at line 9, column 17]
----
Tip: It's the step after the last dot that caused this error, not those before it.
----
Tip: If the failing expression is known to legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing</#if>. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)??
----
----
FTL stack trace ("~" means nesting-related):
- Failed at: contentFields = authorContent.content... [in template "44616#44647#114455" at line 9, column 1]
----
1<#assign
2 webContentData = jsonFactoryUtil.createJSONObject(author.getData())
3 classPK = webContentData.classPK
4/>
5
6<#assign
7authorContent = restClient.get("/headless-delivery/v1.0/structured-contents/" + classPK + "?fields=contentFields%2CfriendlyUrlPath%2CtaxonomyCategoryBriefs")
8contentFields = authorContent.contentFields
9categories=authorContent.taxonomyCategoryBriefs
10authorContentData = jsonFactoryUtil.createJSONObject(authorContent)
11friendlyURL = authorContentData.friendlyUrlPath
12authorCategoryId = "0"
13/>
14
15<#list contentFields as contentField >
16 <#assign
17 contentFieldData = jsonFactoryUtil.createJSONObject(contentField)
18 name = contentField.name
19 />
20 <#if name == 'authorImage'>
21 <#if (contentField.contentFieldValue.image)??>
22 <#assign authorImageURL = contentField.contentFieldValue.image.contentUrl />
23 </#if>
24 </#if>
25 <#if name == 'authorName'>
26 <#assign authorName = contentField.contentFieldValue.data />
27 <#list categories as category >
28 <#if authorName == category.taxonomyCategoryName>
29 <#assign authorCategoryId = category.taxonomyCategoryId />
30 </#if>
31 </#list>
32 </#if>
33 <#if name == 'authorDescription'>
34 <#assign authorDescription = contentField.contentFieldValue.data />
35
36 </#if>
37
38 <#if name == 'authorJobTitle'>
39 <#assign authorJobTitle = contentField.contentFieldValue.data />
40
41 </#if>
42
43</#list>
44
45<div class="blog-author-info">
46 <#if authorImageURL??>
47 <img class="blog-author-img" id="author-image" src="${authorImageURL}" alt="" />
48 </#if>
49 <#if authorName??>
50 <#if authorName != "">
51 <p class="blog-author-name">By <a id="author-detail-page" href="/w/${friendlyURL}?filter_category_552298=${authorCategoryId}"><span id="author-full-name">${authorName}</span></a></p>
52 <hr />
53 </#if>
54 </#if>
55 <#if authorJobTitle??>
56 <#if authorJobTitle != "">
57 <p class="blog-author-title" id="author-job-title" >${authorJobTitle}</p>
58 <hr />
59 </#if>
60 </#if>
61 <#if authorDescription??>
62 <#if authorDescription != "" && authorDescription != "null" >
63 <p class="blog-author-desc" id="author-job-desc">${authorDescription}</p>
64 <hr />
65 </#if>
66 </#if>
67</div>
The following has evaluated to null or missing:
==> authorContent.contentFields [in template "44616#44647#114455" at line 9, column 17]
----
Tip: It's the step after the last dot that caused this error, not those before it.
----
Tip: If the failing expression is known to legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing</#if>. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)??
----
----
FTL stack trace ("~" means nesting-related):
- Failed at: contentFields = authorContent.content... [in template "44616#44647#114455" at line 9, column 1]
----
1<#assign
2 webContentData = jsonFactoryUtil.createJSONObject(author.getData())
3 classPK = webContentData.classPK
4/>
5
6<#assign
7authorContent = restClient.get("/headless-delivery/v1.0/structured-contents/" + classPK + "?fields=contentFields%2CfriendlyUrlPath%2CtaxonomyCategoryBriefs")
8contentFields = authorContent.contentFields
9categories=authorContent.taxonomyCategoryBriefs
10authorContentData = jsonFactoryUtil.createJSONObject(authorContent)
11friendlyURL = authorContentData.friendlyUrlPath
12authorCategoryId = "0"
13/>
14
15<#list contentFields as contentField >
16 <#assign
17 contentFieldData = jsonFactoryUtil.createJSONObject(contentField)
18 name = contentField.name
19 />
20 <#if name == 'authorImage'>
21 <#if (contentField.contentFieldValue.image)??>
22 <#assign authorImageURL = contentField.contentFieldValue.image.contentUrl />
23 </#if>
24 </#if>
25 <#if name == 'authorName'>
26 <#assign authorName = contentField.contentFieldValue.data />
27 <#list categories as category >
28 <#if authorName == category.taxonomyCategoryName>
29 <#assign authorCategoryId = category.taxonomyCategoryId />
30 </#if>
31 </#list>
32 </#if>
33 <#if name == 'authorDescription'>
34 <#assign authorDescription = contentField.contentFieldValue.data />
35
36 </#if>
37
38 <#if name == 'authorJobTitle'>
39 <#assign authorJobTitle = contentField.contentFieldValue.data />
40
41 </#if>
42
43</#list>
44
45<div class="blog-author-info">
46 <#if authorImageURL??>
47 <img class="blog-author-img" id="author-image" src="${authorImageURL}" alt="" />
48 </#if>
49 <#if authorName??>
50 <#if authorName != "">
51 <p class="blog-author-name">By <a id="author-detail-page" href="/w/${friendlyURL}?filter_category_552298=${authorCategoryId}"><span id="author-full-name">${authorName}</span></a></p>
52 <hr />
53 </#if>
54 </#if>
55 <#if authorJobTitle??>
56 <#if authorJobTitle != "">
57 <p class="blog-author-title" id="author-job-title" >${authorJobTitle}</p>
58 <hr />
59 </#if>
60 </#if>
61 <#if authorDescription??>
62 <#if authorDescription != "" && authorDescription != "null" >
63 <p class="blog-author-desc" id="author-job-desc">${authorDescription}</p>
64 <hr />
65 </#if>
66 </#if>
67</div>