Search
Full Menu and site Navigation

Program meetings typically 2nd Tuesday of month
Time: 6:00-7:00 CST
Food & networking at 5:30

Physical Locations

*Bell Helicopter
*L-3- Arlington
*L-3- Greenville
*Lockheed Martin Aero- Fort Worth
*Lockheed Martin MFC- Grand Prairie
*Raytheon- McKinney
*Abbott


Check out presentations from previous North Texas INCOSE Chapter Meetings!

Presentations can be found here

Board meetings typically 1st Tuesday of month
Time: 5:30-6:00 CST



Chapter Event Calendar

Remote Program Access
 
Teams (Video/Audio) - Click here to join the meeting. 
Contact INCOSE North Texas Chapter  ntxinfo @ incose dot net to be added to our meeting emails.
The meetings are not recorded. Presentation are posted in the library and resources during the following weekend if we receive the presentation.


Upcoming Chapter Events

Chapter Meeting April 13

Digital Engineering (DE): The Next Chapter of MBSE by Paul White

Remote Program Access: Teams (Video/Audio)
Join on your computer or mobile app

Abstract:  

What is digital engineering (DE)? How does DE relate to MBSE? In this presentation, we will show how DE is the next chapter of MBSE. We will talk about the Office of the Secretary Defense’s (OSD) Digital Engineering Strategy, released in June 2018. We will discuss the goals of the DES and how you can implement DE in your current and future systems engineering efforts. This presentation is for those who would like an introduction to DE.  


Bio

Paul White is the ICBM GBSD Digital Engineering Branch Lead for BAE Systems at Hill Air Force Base, Utah. He has worked previously at Kihomac, Astronautics Corporation of America, L-3 Harris, and Raytheon. He has 20 years of experience in the aerospace industry.

Paul has been an INCOSE member since 2007 serving in various top leadership roles in the North Texas (Dallas - Fort Worth) Chapter, Chicagoland Chapter, and Wasatch (Utah) Chapter.  He is the current president of the Wasatch Chapter.  Paul has been a leader in the annual Great Lakes Regional Conference (GLRC) since 2012 including conference chair for the 6th and 8th conferences.  He served as the conference chair for the first annual Western States Regional Conference (WSRC) in Ogden in 2018; and he serves on the WSRC Steering Committee for 2019 and beyond. He was awarded the INCOSE Outstanding Service Award in 2019. He serves as the Deputy Assistant Director of Technical Events in INCOSE's Technical Operations organization.

He has a graduate certificate in Systems Engineering and Architecting from the Stevens Institute of Technology, a Master of Science degree in Computer Science from Texas A&M University-Commerce, and a Bachelor of Science degree in Computer Science from Texas A&M University.  He is a Certified Systems Engineering Professional (CSEP) through INCOSE. 

 


Chapter Meeting March 9

Using Architecture and MBSE to Develop Validated Requirements by Dr. Ron Carson

Remote Program Access: Teams (Video/Audio)
Join on your computer or mobile app

Abstract:  Requirements incompleteness and ambiguity continue to plaque many organizations.  The introduction of MBSE provides an opportunity to relate the structure of the architecture model to the structure of requirements, and synchronize the data between them.
In this presentation we demonstrate how to use model-based systems engineering and the related architecture to develop and validate requirements of all types. We first describe the structure of different types of requirements and map the requirements elements, e.g., function, to elements of the architecture in the MBSE model. We show how these requirements elements map to specific data elements in a particular MBSE tool for all possible types of requirements. Finally, we show how this method enables validation of the requirements from the architecture.
Attendees will gain an understanding of how to integrate their organizational requirements development and MBSE architecture activities by mapping the data elements between them and integrating these into their MBSE tools.  

Bio
:  Dr. Ron Carson is an Adjunct Professor of Engineering at Seattle Pacific University, an Affiliate Assistant Professor in Industrial and Systems Engineering at the University of Washington, a Fellow of the International Council on Systems Engineering and a certified Expert Systems Engineering Professional. 
He retired in 2015 as a Technical Fellow in Systems Engineering after 27 years at The Boeing Company. He is the author of numerous articles regarding requirements analysis and systems engineering measurement. He has been issued six US patents in satellite communications, and two patents regarding “Structured Requirements Generation and Assessment”.
 

 



Chapter Meeting February 9

Innovation and national security by Dr. Tina P. Srivastava
 

Remote Program Access: Teams (Video/Audio)
Join on your computer or mobile app

Abstract: Dr. Srivastava will discuss innovation and national security, focusing on two key challenges: participation and secrecy. The participation challenge is about providing adequate incentives to potential innovators, and we will discuss challenges to incentivizing participants and how to overcome them. We will discuss IP policies, innovation contests, and incentivizing employees within a company, so business leaders can learn how to incentivize their own employees, and also how they can open up the innovation process to enable broader diversity in innovation by applying open innovation strategies to overcome technology hurdles. The secrecy challenge is about technology innovation for national security where secrecy can be an obstacle. Dr. Srivastava is passionate about technology innovation and in particular, how we can harness it to further national security and competitiveness -- for example, targeted innovation to land an astronaut on the moon, or develop stealth machinery for cyber defense. But secrecy in classified environments sometimes makes it hard to recruit and innovate. We will discuss how to navigate various contracting and legal channels. We will also discuss government programs and policies related to technology innovation and government contracting.

Bio
:  Dr. Tina P. Srivastava has served on INCOSE’s Board of Directors and received the INCOSE Inaugural David Wright Leadership Award in 2014 for technical and interpersonal competencies in the practice of system engineering as a means for solving the great challenges of our planet. She is a lecturer at MIT in the areas of aerodynamics, aviation, complex systems, and technology road mapping and selection. She is also the author of Innovating in a Secret World, featured by MIT. Dr. Srivastava co-chairs the PM-SE Integration Working Group and is one of the authors and editors of the book Integrating Program Management and Systems Engineering. As an innovator, entrepreneur, and technology expert, Tina’s experience spans roles as Chief Engineer of electronic warfare programs at Raytheon to cofounder of a venture-backed security startup. She is an FAA-certified pilot and instructor of MIT’s Pilot Ground School course. Dr. Srivastava earned her PhD in Strategy, Innovation, and Engineering, a Masters in System Design and Management, and a Bachelors in Aeronautics and Astronautics, all from MIT.

 


Chapter Meeting January 12

North Texas 2021 by Justin C' de Baca

Location: Virtual (see chapter newsletter and top of this page for connection information)

Abstract: I will be using this meeting to cover a number of things for the 2021 year. Material will include:

  • Promotion of INCOSE IW2021
  • Impact of INCOSE 2020 report
  • INCOSE NTX's Road to Gold Status in 2021
  • Overview of TEAMS for members
We are hoping to get this year off to a great start, and this meeting will be a great place to discuss where we are heading and take any questions from our members.

Bio: Justin is our chapter president this year.

 



All Events

Interview with Kerry Lunney, ESEP

Courtney Wright

Sep 30, 2021

This interview was conducted in 2021.
SEP Interview - Kerry Lunney photo
Q1: Describe your current position/role.

Kerry is currently a Country Engineering Director / Chief Engineer at Thales Australia, based in Sydney. In this role she provides technical leadership and governance on bids and projects, delivers technical training programs, and participates on the Technical Board of Thales Australia.  She often undertakes personal intervention in different business units or on projects as required and is strong in forming and animating networks of key stakeholders, engaging with relevant actors at country level, Group level and external to Thales. In addition to this role, Kerry is currently the President of INCOSE, completing the 2nd year of her two-year term, after serving as the Asia-Oceania Director and President-Elect in the preceding years. Kerry is a Fellow of Engineers Australia with a status of Engineering Executive and Chartered Professional Engineer, is a member of IEEE, and is a certified INCOSE ESEP.

Q2: What are one or two of your proudest professional accomplishments?

Kerry was quite excited to have been the first individual certified as an INCOSE ESEP in Australia. Additionally, she served as the INCOSE Symposium Chair in 2001 when it was held in Australia. Kerry described this experience as being fun and rewarding having run a conference for 500-900 people over the course of 3 ½ days. Reinforcing the significance of this career highlight, Kerry was recognized (over the phone) by one of her ESEP panelists as having been the 2001 INCOSE Symposium Chair! Another example of accomplishments was the development and delivery of complex Data Centers in Sri Lanka and Thailand, where Kerry was able to have a significant impact on the organization, management, total systems engineering, and risk mitigation approaches resulting in a successfully deliver a working system to her customers.

But at the top of the list was the honor to serve as President of INCOSE.

Q3: What is the biggest challenge you face as a Systems Engineer?

Kerry explains that, quite frankly, the biggest challenge being a Systems Engineer is that most people don’t understand what a Systems Engineer does, and hence the importance of such a role to facilitate a successful outcome in delivering a system solution.  Likewise, it is not a role that can be largely taught in educational institutions.  Yes, the foundations and many problem-solving approaches and techniques can, but to be a good Systems Engineer takes more than that. It takes education and experience to get everyone on the same page with respect to systems engineering. Finally, although the term “Systems Engineering” was primarily conceived out of the Defense world, many who practice the core Systems Engineering processes and disciplines don’t know they are actually doing systems engineering.

Q4: What advice do you have for individuals starting their career as a Systems Engineer?

Kerry believes Systems Engineering is a good field with lots of opportunity. Based on the trends within industry and advancements in technology, there are many more integrated systems these days and/or going that way in the near-future. For individuals starting their career as Systems Engineers, Kerry recommends focusing on a depth or expertise in a specific engineering discipline first. Once proficient, they should then expand with other disciplines that interest them to help become aware of other facets of the system. That being said, Kerry feels that acquiring experience is essential to build from a formal educational basis. Additionally, she also cautions Systems Engineers from getting caught up being a specialist and getting pigeon holed in only one or two Systems Engineering work areas – one should not lose focus of the entire system when considering any one aspect. Kerry also advises that disruptive technologies are always those items that pop up out of the blue and a good Systems Engineer must think how they will impact / disrupt modern systems. Therefore, a Systems Engineer must stay current with emerging trends in the industry and be prepared to work hard. Finally, a Systems Engineer must have soft skills in addition to technical skills as there are many situations where one must work with groups of people with all types of backgrounds, expertise, and interest in the overall system.

Q5: How do you continue to learn about SE? What professional development activities do you do?

In addition to her career commitments and responsibilities, Kerry also enjoys volunteering in INCOSE and also in the Australian Chapter, the Systems Engineering Society of Australia (SESA), where she served as President from 2008-2009.  Kerry also reads as much as she can (e.g., INCOSE’s website, publications, Working Group minutes / deliverables) to stay current on technology and the latest SE practices, and looks for opportunities at work to be part of a larger technical community.  What can be discussed and learned from colleagues worldwide can be very insightful.  Kerry also makes time to simply talk to specialists, experts, and others in the industry as that typically yields the most beneficial insights to helpful and relevant SE practices. Kerry also attends lectures, conferences, and technical / industry group events as much as her busy schedule allows.

Q6: What are the next career goals you want to achieve?

Although extremely accomplished in her professional career, Kerry hopes to one day make time to write a novel but weave through it a systems perspective – matching fiction with fact with future. She would also like to continue holding technical leadership roles at the senior/executive level and tackle difficult problems. Similarly, loving her roles as a Technical Leader, Kerry wishes to someday give back to the younger generation through mentoring, supporting educational programs and providing expert guidance on one or two key technical challenges of the future. Kerry will eventually and gradually retire someday.

Q7: What are some of your hobbies/interest outside of work?

Special interests outside of SE include walking her dog Max, reading the occasional fiction novel, camping, playing the piano, cycling, swimming, body surfing, scuba diving, and many other outdoor activities in the vicinity of the beach.

Q8:  Are there any other final comments you would like to make?

Systems Engineering can have many different meanings to other professionals.  It is very broad in its adaptation across different industries and can be very complex. But because of this it can open many doors for the individual to progress through his/her career. No other technical field can provide the exposure to other technical fields in different domains across various industries.  It is a great field to either progress in or to use as a jumping board to move into another area of expertise.

Q9:  Why did you decide to get the SEP certification?

Kerry had been considering to apply for SEP certification but the catalyst was actually through her employer Thales. At that time, Thales was looking to put through a number of candidates from around the world to strengthen the organization’s expertise in systems engineering and to be recognized as holding this expertise. As a result, Kerry moved forward with her application, initially for CSEP level but while gathering all her material to support her application she realized she could qualify for ESEP, and the rest is history.

Q10:  How does the SEP certification impact your professional career?

It is not clear if the SEP certification has impacted Kerry’s career.  It certainly has not had any negative effect, quite the opposite.  The SEP qualification often has to be explained but it is always well received.  As a result, Kerry is starting to see the recognition grow in Australia. It does place you apart from your colleagues, so that is positive.  And for Kerry it was great to be the first person in Australia to obtain this qualification.

Q11:  What has surprised you in the past five years related to systems engineering?

What has surprised Kerry over the past five years is that there is a growing need for better system solutions with the increasing inter-dependencies and inter-connectedness, yet we are still having the challenge of being recognized for our expertise to work these system solutions.  They are opposing elements in the same ecosystem. It is almost as if there is an identity crisis for Systems Engineers.  Kerry noted that in-roads are being made and our position has improved over the five years but she thought we would have advanced further by now.

Q12:  What job titles have you had other than “Systems Engineer?”

  • Systems Design Lead
  • Systems Engineering Manager
  • Principal Systems Engineer
  • Chief Systems Engineer
  • Systems Project Manager
  • Chief Engineer
  • Technical Lead
  • Technical & Engineering Director
  • Technology General Manager
  • Engineer Grade 1
  • Engineer Grade 2
  • Software Quality Engineer
  • Engineering Manager
  • Project XYZ Engineering Manager
  • Engineering Process Manager
  • Joint Architecture Group Leader
  • System Architect
  • Solution Engineering Manager
  • Project Design Authority