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 Peter Graham, ASEP

Courtney Wright

Sep 05, 2021

SEP Interview Template 2021 - Peter Graham photoThis interview was conducted in 2021.

Q1: Describe your current position/role.

I am a systems engineering consultant at The Energy Systems Catapult. My main responsibility is helping stakeholders in the public sector, primarily UK government departments, understand why and how to take a systems approach to solving problems around the UK energy system transition for net zero greenhouse gases.

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

  1. In 2019 I started my own business consulting in systems engineering. This was a calculated risk and a significant challenge. Over time, this became a genuine enabler to grow as both a person and a systems engineer. I increased my professional network, explored new challenges, and invested in my own personal development (including progressing to ASEP). I know I wouldn’t have achieved these things without the drive and opportunity of having my own business.
  2. I co-authored and presented a paper for the INCOSE UK Annual Systems Engineering Conference (ASEC) in 2020 called ‘Harambe: The Only Way to Net Zero’. I didn’t consider such an endeavor in the past but the learning process and the hard work was ultimately rewarding if a little cathartic at times. I’m proud to have an output that is available in the public domain and may go on to influence or inspire some activities that are related to its content.

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

Getting stakeholders to understand the concepts and principles of tackling problems with a systems perspective. Examples include subject matter language barriers or conflicts in working between problem space and solution space. In extreme cases, there is an active push back on taking a systems engineering approach because there is perceived to be no time and/or money. It is challenging to convince some stakeholders of the benefits that are afforded by systems engineering. We could do with more “off-the-shelf” and bitesize examples as a community to help overcome this.

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

Stick to the fundamental rule of always following your passion. It can be important to pay attention to trends in industry, skills, markets but don’t let those be the main drivers for your career decisions. Do what you love now, and the rest will fall into place over time. There is plenty scope in systems engineering to have a full and varied career which evolves over time.

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

I am the chair of the Energy Systems Interest Group which gives me regular engagement with INCOSE UK and its members. I am also a member of the MBSE interest group. In addition, I attend ASEC every year which helps networking and staying on top of the latest activities across the systems engineering community. Aside from that, I try to find the time to advance my knowledge through webinars or training courses or reading literature such as the INCOSE UK ‘Don’t Panic!’ series of books. Lastly, I find the volume and quality of online resources (e.g. SEBoK) ideal for continual learning. The challenge therefore, is reduced to finding self-motivation and time.

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

Achieving CSEP is my next milestone. Beyond that, I’d like to achieve CEng status which is also now offered by INCOSE UK. I also have a growing desire to contribute to systems engineering literature but I’m still working out in what form that would be and what level of commitment would be required.

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

I enjoy all forms of sports and actively participate in triathlon, golf, football and mountain biking. I also really enjoy live music and play the drums in an indie-rock band. I have a love of the outdoors too and find hill-walking or open water swimming is best to get me immersed in nature. It’s surprising that I can still claim these things as I have two young children who also occupy a lot of my time in the most amazing ways.

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

I felt I needed to consolidate my status as a systems engineer and demonstrate some credibility for my career path and personal achievements. Almost all other professions offer a similar step and, generally, the high performing people want that recognition (and generally it’s rewarded in other professions). The SEP initiative offers a great pathway for systems engineering practitioners and my hope is that as systems engineering continues to grow, so does the presence and recognition of SEP.

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

In some ways the impact is internalized. I don’t sense that industry nor individuals actively seek this out yet I feel more confident and more credible within myself when putting forward thoughts and/or arguments around systems engineering. The nature of achieving any level of SEP means you need to pass the knowledge exam and without doubt the push to achieve this has helped me understand systems engineering practices and processes much better than I would have if I hadn’t embarked upon SEP.

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

There are two surprising things emerging. One is how instantaneously the scope of problems, complexity and interoperability has lent itself to a systems engineering approach. So, the original concepts and methodologies of what we now know as systems engineering are becoming more and more relevant over time and significantly so in the past 5 years. The other major surprise is the recognition that systems engineering is receiving from those outside of the community e.g. non-practitioners, other industries, academia, and public sector. In the UK at least, this appears to be driven by large-scale, complex problems such as achieving net zero greenhouse gases by 2050 or the transition to autonomous vehicles.

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

Laser systems engineer, production team lead, and graduate technologist.

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

As a community of system engineering practitioners, we need to consider what the future holds, what sets us apart from others, and what is value-adding about systems engineering. The challenges I mention in Q3 are – in my opinion – a real barrier to adopting systems engineering on a larger scale. In doing so, we must remain pragmatic that it’s not a “one-size fits all” situation; so there may be occasions where systems engineering isn’t the most suitable approach.