im Email not displaying correctly? View it in your browser, mat. - INCOSE Chesapeake Chapter erne - President's Point of View June begins a busy summer for our chapter. Our monthly membership meeting is coming up on Wednesday June 17, 2015 and will feature the Video, The Deming of America, a dramatic look at the origins of the process improvement movement. This video was originally produced for Television by Priscilla Petty. We use it with her Mr. George Anderson kind permission and wish to thank INCOSE CC President her for her continuing support of our george.anderson@incose.org educational programs. Closely following this meeting, we have our IBM System Architect with DODAF class being held in the Kossiakoff Center on Monday through Wednesday, June 29, 30 and July 1, 2015. This course is hands-on and is the best chance to actually become proficient in producing DoDAF, DM2 compliant architecture data models. The course is presented by AVNET, a licensed IBM training provider who provides training materials and a completion certificate. Breakfast and lunch menus are part of the tuition fee and are provided by Sodexo, the on-campus contract catering service. The class is limited to 12 persons so that the instructor, Edward Vail, can provide personal assistance to each student as they struggle with the sometimes confusing menus and other options of System Architect. (| completed this program last year and | speak from experience.) The Chapter is working as a partner with AVNET to bring this course to our area at lower cost and a convenient venue, and we hope our members who need this level of training will be ng June 201: E-Newsletter routs This is the monthly newsletter for INCOSE Chesapeake, a local chapter of INCOSE international. We are a not-for-profit organization dedicated to providing a forum for professionals practicing the art and science of Systems Engineering in the Northern & Ceniral Maryland & Southern Pennsylvania area.able to attend. The last event is the most important. We must prepare for the International Symposium being held 13-16 July at Seattle, WA. We have advertised Chesapeake shirts on the web site and encourage everyone, but especially those who are planning to attend, to purchase a shirt. This is to show your affliation as we are presented with the President's award for the unsurpassed performance of the Chapter mission in 2014. There is a two-week lead time so please act promptly. Challenge coins will also be available for purchase at the next, and subsequent, member meetings for those who want to further prepare themselves for attending the IS. (For those attending who do not have chapter shirts or coins, we have a requirement for several attendees to wear a large MD crab or Chesapeake heron costume as an alternative.) Other planning this month is directed toward making our Systems Engineering Professionals (SEP) reception a repeat success. This year, we are embracing our regional chapters, Washington Metro and Southern MD, in an attempt to reach out to more SEPs and potential candidates. As in past years, we welcome our partners in Government and industry and other engineering and professional societies to attend and enjoy an inspiring social event with featured speakers and an atmosphere of elegance that always delights and enhances our appreciation of this event. The reception is scheduled for Wednesday evening, the 26th of August 2015 at the Engineers Club of Baltimore. The online registration for the event will open early for your planning convenience. The SEP reception is not complete without announcing and honoring our new certified professionals. We will honor those who have attained the highest level of achievement, the Expert Systems Engineering Professional or ESEP. | am pleased to announce that we have two new ESEPs as of this writing, Myra Gross of Jovian Concepts was notified in January and Craig Tyler of Vencore was notified last month. We will be honoring them and any further additions at the Reception. ‘As we move through a busy summer, please remember important changes taking place affecting the practice of systems engineering. The biggest news this month is the release of two DoD supplements to the 1SO 15288:2015 standard. Among other things, these supplements require the use of the standard in DoD procurement processes. This is a significant change in DoD policy and a huge vote of confidence for the practice of systems engineering in general. We, of course, expected this, because of our January presentation by Gary Roedler, who played an important role in drafting the standard, In closing, | want to continue to urge everyone to become more involved Join INCOSE Today The Chesapeake Chapter is always looking for volunteers to speak at our upcoming meetings! Please contact our 2015 Programs Director, Glenn ‘Townson, if you would like the opportunity to speak or can recommend someone. ‘The Chesapeake Chapter of INCOSE is proud to recognize the following organizations for sponsoring our endeavours to expanding the understanding and appreciation of Systems Engineering in the local area: n | Hamiltor The Institute for Systems Research TE JAMES CLARE ‘% CyberCore TECHNOLOGIESin the systems engineering profession and to consider the benefits of spending some time helping the Chapter execute the important work that we graciously provide as a focus on, and example of, systems excellence. We believe that this contributes measurably to Maryland’s sustainment and growth. George Anderson ~ INCOSE Chesapeake Chapter President 17 June, 2015 (6:00pm — 8:00pm): The Deming of America; Produced for Television by Priscilla Petty Presentation: This video, originally produced for Television by Priscilla Petty, provides a dramatic look at the origins of the process improvement movement. Our nation must work once again to come out of our crisis. We're challenged by global and local events. But the proven strategies in this documentary can help our country transform and innovate. Dr. W. Edwards Deming is shown at his unrehearsed best at his home, at a seminar, and in thought-provoking specially selected segments from an all-day interview with Priscilla. Brief remarks from Fortune 100 CEOs, who learned from Deming, show how he affected their thinking about their lives and companies as he worked with them to effect the transformation. Inspiring. Produced in 1991 by Petty Consulting Productions. Click here for more details:(www.incose-cc,ora) Go to www.incose-cc.org/registratian/ to register Parsons Auditorium, Bidg 1 Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD (Map and Directions 9 JOHNS HOPKINS APPLIED PHYSICS LABORATORY faSci (9 Corporation’ JGYIAN BItrec vencorThe Institute for Revisiting the Wright Brothers and the Sound of Bells Systems George Anderson, ESEP JANES uae 3 June 2015 Apracticing systems engineer should consider approaching all projects 7 GROUP as having unknowns that will require in depth examination and perhaps new insights or understanding. There are a lot of knowledgeable subject matter experts (SME) available but few of them can help when the information or practice is obscure, little studied or just unknown. The se rco arrogance of assuming adequate knowledge to accomplish a task is a eringogsevice 7 constant engineering hazard dating back to at least the ancient Egyptians who at one point had the world's greatest building failure when an almost completed pyramid collapsed into a heap of dressed BSP stone blocks. The giant debris field stil exists today as an enduring ; reminder to do more thorough research on unknowns. [1] ‘S CyberCore TECHNOLOGIES We might be able to forget this 4640 year old disaster if more recent challenges were not so similar in the form of assuming adequate knowledge. | have worked on two projects that still amaze me as to the methods used and the types of critical knowledge involved. These involved the Wright brother's progress towards manned flight and the analysis of the sound of bells. Both subjects would not have been of interest to me had | not been given systems engineering tasks that required me to fully understand the technical details of these two somewhat different technologies. faScitor rare) JOHNS HOPKINS Figure 1: Meidum Pyramid APPLIED PHYSICS LABORATORY 2625 BC ‘The Wright brother's saga has been told many times but the latest work by historian David McCullough entitled, The Wright Brothers, is popular enough to become first on the NYT best selier list this week and inspire me to mention an example of their perseverance. | am informed on most of the Wright's technical advances having received my degree in Aerodynamics from an institution[2] that lies only a few hundred yards from Huffman Prairie—the Wright's first aircraft flight test facility after Kitty Hawk. Although there is much to admire and consider about the Wright's technical experimentation and development efforts, the point | especially want to highlight is their questioning of existing data on manned flight. They were so concerned that their early test flights were not consistent with existing data on the lifting forces of wings that they built their own wind tunnel. Using this tunnel, they spent hours testing wing shapes until they were sure that existing data was wrong. Before the Wright's tunnel, there were noestablished devices that could be used for measuring forces on the test wing specimens. My wind tunnel testing occurred in 1973. This was during a period when mathematical modeling of airflow over wings was heavily funded. News from the physical world that conflicted with the models was not welcome and there was a great deal of resistance to testing in general. Thanks to the example set by the Wright brothers, wind tunnels continued to provide real performance data that was used to design new aircraft and reduce risk. Today, we still have areas that are not well understood such as vortex flows, and some aspects of hypersonic flight. We also know little about the regime of microscopic flight (low Reynolds numbers) where many want to explore and develop unmanned micro vehicles. The problems faced by the Wrights are Co similar to many that we encounter today. Itis always true that you need to explore all the problem space to find what you don't know and make plans to deal with it, Like the captain on a ship, if you see an area of poorly charted waters you may avoid failure or uncertainty by circumnavigation. If you must sail in the unknown area prudence dictates that you study whatever information is available, make estimates and provide contingency plans for coping. The Wright brothers did not see the absence of a suitable tool to measure wing lift as an insurmountable barrier. They simply designed and developed their own. My other area of tracking the unknowns takes us to the much older technology of bells. Figure 2 The Wright Brothers Wind Tunnel on display at the USAF Museum, Dayton, OH Bells represent an ancient technology that continues to serve a variety of purposes in almost every culture. Bells were being made before any scientific analysis using modem instruments and theories existed. The sound of the bell was its primary distinguishing feature and a customer, or customers, purchasing a bell had very strong ideas what that sound should be. A few years ago, | was asked to oversee the founding of a sizable bell and assure its performance in my capacity as a test engineer. Why anyone thought | knew anything about bells says a lot about the management of the auto industry at that time, but also it may have more to do with the assumption that bells were just shapes of metal. | started my task with just that assumption and in several days of research was considerably humbled. | not only did not know how a bell was made, | did not know how the bell made its sounds, what they were, or how one controlled the process to achieve these sounds. ‘SMEs could not explain what they knew in enough technical detail for me to make any progress. | considered the explanation of tuning a bell especially baffling. Clearly, vencor This Newsletter is to serve our members and is open to all for contributions. Do you have an interesting idea for an article? A review of a new book related to engineering? Let us know, We'd love to hear about it. It may wind up in a future issue of our Newsle! Return to topI needed further study. Later, | understood one reason for my confusion was the terminology used by the few people who knew about bells. After all at that time, there were only three bell founders in the US and less than eight in Europe. Thankfully, the bell project was cancelled before my project was memorialized in a two-ton mass of copper-tin alloy scrap. What | had leamed in the meantime was considerable. The highlights were: + Acomplete course in sound measurement permitted me to understand how to test a bell’s sound pressure emissions and describe them in acceptable laboratory terms using calibrated and repeatable processes. * I learned the language of the bells. People who write about bells talk in the language of music, and early design rules of thumb further obscured this by using centuries old jargon probably made legitimate by medieval guilds protecting their art. * Tuning a bell almost always involves removing metal from the inside of a newly cast bell. + Removing metal from a bell may not always produce the desired result. * In 2015, there is more, but still incomplete, theory on precisely how bells produce their sound spectrum and what constitutes the best or most desirable sounds. [3] + Ihave learned that researchers have established that the bell sounds are not the total system under study. The human ear with its perceived pitch and aural harmonics alters the sound of the bell to another pitch heard by the brain's auditory receptors. [4] This effect is so significant that testing of humans in the loop has drastically changed the desirable spectral specifications for a bell Overall, | concluded that in the bell industry, nobody understood how to meet a customer's expectations. This was partly because there were no modern technical standards and partly because the customer was probably expecting the sound produced by another bell. Rules of thumb and proprietary secrets ruled the : industry and in the end you got a product _ Figure 3. The Ten Ton that at best was tuned to nominal sound Weight Berlin Freedom Bell spectrum. Customers bought from the most prestigious or oldest foundry and humbly accepted the product as delivered. A delivery specification, if such was involved, was typically vague as to spectral performance. This state of affairs led me to believe that our modern audio spectrum measurement capability was useless if the test specification was defective or not validated. Unlike the pyramid collapse, neither of my learning experiences produced immediate disaster. On the other hand, they taught me to bevery careful about unknowns. The Wright brothers inspired me to aggressively pursue knowledge and the short-lived bell project taught me not to depend completely on SMEs to completely fil the knowledge gap. Special knowledge is cumulative and has a way of helping in future projects and providing special satisfaction. | still enjoy reading about new discoveries in vortex flow and hearing the sounds of church bells on Sundays. Hear the Freedom Bell Ring: v=AxWInbQvexT [1] bttp://en.wikipedia.org/wiki/Meidum [2] The Air Force Institute of Technology, Wright-Patterson AFB, OH, Established 1919. [3] http://www, hibberts.co.uk/index.htm [4] Our Acoustic Environment, Frederick A. White, John Wiley & Sons, New York, 1975 ‘Return to top Elicitation and Analysis of Requirements Gary Wieboldt, ESEP 27 April 2015 In the classic system engineering Vee diagram, a keystone, earlyactivity in the process are requirements. The process consists of: Requirements Elicitation (get them) Requirements Analysis (can they be done?) Specification (document them) Requirements Validation and Verification (did you build the right thing and was the thing built right?) 5. Requirements Management (how do | change them?) PENS We believe in the mantra of a “complete but minimal’ set of requirements is important to prevent over complexity (hence reduced reliability, and a host of other issues like cost) of a system: agora. oF THe ]E[ now oun eaoouer Fnoovcr FEATURES Tawonnaces THAT EAGH OF YOU epderoose oF ‘DEMANDED. ‘GonrUextTy. | ‘Communication of requirements is key, so that all stakeholders and engineers know what product or service they are going to receive. They cannot be developed in a vacuum, heavy interaction, with all stakeholders are necessary to get good requirements.: Here | would like to focus on the difficulty in steps one and two: getting them (Requirements Elicitation) and understanding if they are doable (Requirements Analysis) Interpersonal relationships are Key in the first two steps: between customer and vendor and all the people who make up the consolidated team. The elicitation process is a system of people, interpersonal relationships, thoughts and ideas. in the elicitation phase it is key to not only identify stakeholders, but to clearly understand their roles and how you are going to manage their varied requests. As we elicit we occasionally perform in situ requirements analysis to understand the validity of consequences of the proposed requirements. ‘Sometimes this analysis has to be performed offline from the elicitation process due to the interrelationships and complexity of the requirements set. But there are times where during the elicitation phase obvious conflicts are present and need to be adjudicated.That brings us to this video: https: //www,youtube,com/watch? v=BKorPSSAqvg which, although a farse, does show how elicitation and analysis of requirements from different stakeholder views can make an engineer's job very difficult to accomplish. Especially if he/she is "An expert’, and the people around them are far from it. ‘Return to top. Seven (Plus or Minus Two) by Zane Scott George A. Miller died July 22, 2012 at age 92. He was truly a giant in the world of psychology. In 1956 he published an article in Psychological Review entitled "The Magical Number Seven, Plus or Minus Two: Some Limits on Our Capacity for Processing Information". His ideas were especially important because they were introduced into the stimulus-response world dominated by behavioral psychology. AS he developed his thought he posited an information processing theory of human cognition where behavior resulted from taking in and processing information instead of being the deterministic outcome of conditioned responses to external stimuli that behaviorists believed drove a person's behavior. This had paradigm-shifting implications for the field of psychology in general but perhaps the most important to the world of communications was his research showing that, while long term memory capacity was practically unlimited, the short term memory that we use to take in information for processing is essentially limited to seven “chunks’- plus or minus two- hence the tile of his article. Any attempt to hold more chunks in short term memory results in loss or degradation in the processing as with objects falling off an overloaded desktop, In a practical sense we do not have direct access to the unlimited long term memory when we communicate. We are only able to place chunks of information before our ‘receivers’ for reception into short term or “working” memory for processing, Therefore, we need to respect the existence of a short term memory limitation as we chunk our information and organize it for presentation. ‘There has been a great deal of work suggesting that the limit is different for different kinds of information and that the limit may be lower than seven. Some researchers have suggested four items and some three, but whatever the number there is now broad acceptance of the existence of the limit. For that we must tip our hats to Miler. ‘The next time we do a presentation we should pause to think of him and heed his work. Do our slides violate the principle of a limited workingmemory? Does our organization honor the principles behind chunking information for processing? We can all think of violators and their violations of these principles. Perhaps by remembering Miller we can avoid joining those ranks. We may not become slaves to the number three, or four or even seven but we can certainly avoid the numbers 20 and 30 and 50! ‘As we do so, we thank you George. May you rest in peace. © Vitech Corporation 2015, Reprinted by Permission Why Systems Engineers are Essential to Your Organization by John Thomas Asystems engineer is invaluable to an organization by preventing system problems from impacting the cost and schedule of programs. They rely on their technical and leadership skills to reduce the potential for rework associated with changes in design, interpretations with requirements, or confusion with the user's intent. They are the ones who pay attention to the system details and ensure the user, the buyer, and the investor are all satisfied with the project's outcome — which is the ultimate measure of success. Itis the systems engineers’ role to understand the intended use and ultimate purpose of the system, and then to clearly communicate the proper system design to component builders. This begins by translating the user's vision into information required by the architecture team to generate an optimal systems design. Itis followed by the systems engineer providing component builders with a translation of the architecture teams’ vision, along with the appropriate technical requirements for building each component within the system. Yet systems engineers know itis not enough simply to deliver a solution that works. To meet the user's highest expectations, they use their skills and insight to understand the user's perspective and to establish those expectations in the technical language of systems builder. Often, this involves helping the end-user think through a more complete definition of a successful outcome by producing missing details critical for influencing the systems design. Only when the systems engineer gets it right, will the user — as well as the investor and the buyer — completely embrace the result. ‘Systems engineers also recognize that they have to match what the architecture team is hoping to accomplish with what the componentbuilders can best provide. Through their leadership skills, the systems ‘engineer works toward an ideal balance between the user's vision, and a systems design that is easily implemented. When this balance is achieved, the systems engineer packages the builder information into three critical areas: 1) how the component must function; 2) how it needs to interface with the other components; and, 3) how it must adapt to the larger operational environment. When these “translation” activities occur correctly, the user's vision is achieved akin to providing a finely-tuned racing bike suitable for the Tour de France. When these activities are missing or poorly accomplished, the bike intended for the Tour de France may wind up with knobby tires and a heavy frame, not the ideal bike a rider needs in order to win. Across an organization's products or services, systems engineers also provide critical leadership for integrating the technical activities, They have skills to influence multidisciplinary teams to reach consensus on how the system solution should come together. As problem-solvers, they focus on outcome, not process. They ‘own’ the project: they don't start from the position that expensive rework or user dissatisfaction—or for that matter, a builder delivering less than ideal components—is someone else's responsibility. They step in and resolve the issue, often before most others even know the risk exists. As translators, systems engineers can prevent many of the system problems that tend to derail projects. As leaders, they deal with the complexity of those problems as they arise. This powerful set of skills, abilities and know-how is why systems engineers are a valuable resource to an organization, INCOSE_Fact Sheet_2_01.09.12, Reprinted by Permission Return to top Upcoming Events and Announcements + Click here to order your Chesapeake Chapter Shirt + June 17, 2015: Dinner Lecture - Movie Night: The Deming of America + June 29~ 1 July, 2015: Course on DoDAF 2.0 Modeling with IBM Rational ‘System Architect V.11.4; by AVNET's Ed Vail + July 15, 2015: Dinner Lecture — SE Consideration in the Design of ‘Autonomous Air, Ground, Surface and Undersea Vehicles; David Scheiat, Principal Professional Staff JHU/APL (Tentative) ‘+ August 19, 2015: Dinner Lecture ~ In Close Encounters We Mostly see Ourselves—The Origin of UFO Alien Faces; by Dr. Fred Malmstrom (Tentative) + August 26, 2015: Systems Engineering Professionals (SEP) Reception + Interested in Jobs Networking? Contact Mark Kaczmarek atie cece ee See Se eee ING SBE as aa re cor any comments or suggestions sbout this newsletter please e-mal our Preside George Anderson or our Communications eee coe —— Board of Director Officers, 2015 — President: Mr. Geerge Anderson Directors at Large Past President: Me. Erk DeVito Communications: Me. Pat Wiliams = President Elect: We. John Boeco Programs: Mr. Glenn Towson ~ Treasurer: Me. Kent DeJong Membership Commitoe: Gundars Osvalds ~ Secrtary: Me. Mark Kaczmarck Please use the Forward email link below so we can invite your friends to join our mailing list. Thanks in advance, INCOSE Chesapeake Chapter © 2015ant dsayig covet ewes ba, INCOSE Chesapeake —— E-Newsletter a Chapter President’s Point of View Lessons Learned and the Way Ahead | am honored to begin my service as the 2015 President of our Chesapeake INCOSE Chapter and am no stranger to the nature of the challenge. | have just attained the 4th year of service along the way to completing two non= consecutive presidential terms. ‘Mr. George Anderson While | am quite prepared to INCOSE CC President describe the many virtues of the george anderson@incase.org ©'ganization that we proudly serve, | thought it more beneficial to focus briefly on the overall scope of our recent activities, what we have learned and what paths of opportunity lay ahead for us. The Board of Directors (BOD) has worked hard over the past year to attract record attendances to our functions and embrace new initiatives. This was accomplished while honoring our commitment to follow INCOSE INTERNATIONAL’ best practices and promote Systems Engineering thinking to the local learned communities including other engineering societies, colleges and pre-college youths. Equally important was the improvement of a Taree and governance Foundation ther could support our desire to increase the scope and size of our programs and activities. We revamped our activity templates, did mini-analysis of expenditure patterns and conducted a formal audit of the Chapter's financial records. None of this could have been done without the dedicated assistance of our Associate Directors. ‘lessee bcorgeandersce/Destap2015jnuay-newsleter 245 12:27:09 PM] In Vol. 6 Issue 1 President's POV. © January21. 2015, DinneciLecture © Uncoming Events, This is the monthly newsletter for INCOSE Chesapeake, a local chapter ‘of INCOSE international. We are a not-for-profit organization dedicated to providing a forum for professionals practicing the art and science of Systems Engineering in the Northern & Central Maryland & Southern Pennsylvania area. (Wine Yodel S| | Apply Ontine Now | The Chesapeake Chapter is always looking for volunteers to speak at our upcoming meetings! Please contact our 2014 Programs Director, Dr Alex Paviak. if you would like the opportunity to speak fr can recommend someone. The Chesapeake Chapter of January 2015 Back + Forward to FriendThese individuals, serving at the invitation of the BOD, attended meetings and performed myriad invaluable services. Taken as a whole, their service has changed the landscape of our chapter and made possible a sense of optimism that many of us carry into the New Year. | think the BOD's recognition that they must attract and retain Associate Directors should be the first on our list of lessons learned in 2014. ‘At the end of the year, the President Elect prepares the Circle ‘Awards Submission Sheet to document the Chapter's concrete achievements as measured against INCOSE INTERNATIONAL criteria, During January 2015, an INCOSE committee will evaluate and rank all the INCOSE Chapters and determine who will receive awards for outstanding performance. < ‘Shapes Cnr i ae Re sere chaning tee | te ml fone Sonnac ——— = ae " een neon pete see | om = beeps se hase f= ‘soe | Chart 1. 2014 Chesapeake Chapter Circle Awards Submission. Based on the scores, three levels of awards are made-Bronze, Silver and Gold. Chesapeake has routinely scored in the Gold category and during 2010 was awarded the “Most Improved Chapter” Plaque. There is only one more distinction that is higher-the President's Award. This is presented annually to the INCOSE Chapter judged the most successful. We aspire to win this award and addressed the Circle criteria in our 2014 Operations Planning. See our claimed points in Chart 1 Briefly, the Circle award submission consists of 56 activities that are considered within scope of an INCOSE Chapter. A point system is described for accomplishing various elements of each activity. To validate claims, documentation must be submitted. For example, to validate the delivery of 12 newsletters a year, copies of the newsletters must be submitted. This might sound straightforward until | mention that this year Chesapeake submitted 156 items of proof. In spite of the size of this task, we believe that the effort made to attain a high score validates our success in performing our mission and promoting mutual support and respect in our local business and government ‘community. Sort of like an annual SO 9000 quality review. Based on our Circle Submission for 2014, | would offer further lessons (that | may have) learned: Sesiiserioer 2092015 neater m4 15 122709 PA) INCOSE is proud to recognize the following organizations for sponsoring our endeavours to expanding the understanding and appreciation of Systems Engineering in the local area’ eee The | Institute for Systems Re rch ‘A. JAMES CLARK ‘S CyberCore 9 JOHNS HOPKINS «JJ@VIAN + Lesson 2. Reinforce past success. Our SEP Reception set a oa record for attendance and for the first time had speakers from Government and INCOSE INTERNATIONAL. We have been doing this Reception since 2010 and could have Btec accepted the status quo as good enough. a + Lesson 3. Embrace new ideas. Video Teleconferencing and Streaming INTERNET video have moved from early adopters to must have-services. We now must make the interface | ths nerster st seve our mbes a with college campus groups and members who are distant certs eyo tae at from the meeting venue. The meeting as we know it and the metrics of success associated with attendance numbers | beck is w engceiog Lstushaas ed may have to be reexamined. love ter abou Riy wid pina fre + Lesson 4, The Chapter is necessarily a partner with the sue for Newser. industries that employ Systems Engineers. The maintenance of this mutual relationship is an ongoing task. The process ‘Return to ton of saying Thank You may make your meetings longer but it's important to the recipients. + Lesson 5. Certification Matters. It affects everyone associated with the process of training and those gaining the necessary experience and skills to qualify. Our chapter leads in the number of SEPS and we should be benefiting from these members’ knowledge, leadership qualities and industry savvy. After looking at the past, what lies ahead for the Chesapeake Chapter? * We are a volunteer non-profit organization that with the help of our industry and academic partners offers needed services to our membership and often to non-members in related technical fields. We should create an unambiguous open door to other professionals and vigorously encourage system thinking across disciplines. * I think that we must grow our professional offerings in the areas of training, certification and employment assistance. * Loffer that the newsletter is an underrated means of relating to our members and the larger technical community. Brief articles on relevant subjects as well as short book reports are always welcome to the readers and are a means of sharing new ideas. The absence of copy in a chapter of our size can reflect badly on our profession: + Our ESEPs and CSEPs must in general be seen in technical as well as elected leadership roles if certification is to maintain its credibility. + Last, we must demonstrate the value of certification as an integral part of being a professional SE and take responsibility for keeping the training materials relevant and accurate. If you have read this far-Thanks! If not, you will be hearing much of it from others. Please consider making a resolution to play a part in influencing the Chapter’s 2015 direction and participate in the areas that benefit you. Best Wishes for a Rewarding New Year. ‘es ersgeorgeandersn/Dettop 2015 january newsletter ial /4/5 12.27.09 PM]George Anderson - INCOSE Chesapeake Chapter President Return to ton 21 January, 2015 (6:00pm - 8:00pm): The Evolution of SE Standards and Practices - ISO/IEC/IEEE 15288 Presentation: Over the past decade, there are several key resources that have come to the forefront as the basis of knowledge, requirements and. guidance for systems engineering. These resources include ISO/IEC/IEEE 15288, System Life Cycle Processes; the INCOSE Systems Engineering Handbook; the Defense Acquisition Guide, Chapter 4; EIA 632, Engineering of a System; and recently the development of the Systems Garry Roedler, Lockheed Engineering Body of Knowledge Martin Fellow —_(SEBok). For the user of these resources, higher value would be obtained if they were consistent in terminology and concepts, and easily able to ‘support concurrent usage. The challenge is that the resources come from a number of different sources. This presentation will examine actions that have been taken or are planned to continue to evolve and harmonize this set. (Click ner for more detalls(ww,nsoss-csor8) Go to wwwincose-ccorg/registration/ to register Parsons Auditorium, Bldg 1 Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD Upcoming Events and Announcements * January 21, 2015: The Evolution of SE Standards and Practices - ISO/IEC/IEEE 15288 Based Harmonization Garry Roedler, Lockheed Martin Fellow Se serncrgeanderson/Destop201Sjnsay nese Sen 41S 1227-09 PM)* Interested in Jobs Networking? Look here ‘ese peorgeenderse/Destap 2015 jnay-newsetermlf2/4)5 12.7.0 PM)roxas 2015- (2- Newsleter DRAFT 05m aac inting nei INCOSE Chesape uncil o _ _ E-Newsletter february 2015 bak ake Chapter sring President's Point of ViewPlanning the Future - the 7% Solution In this first month of operations, I have already had the opportunity to talk with many Chapter members and am gratified to hear a number of {ideas that can help our chapter grow and ‘maintain our dearly won reputation for professional excellence. In addition to presiding over the monthly membership ‘meeting on January 21st, [attended the ‘Women in Systems Engineering (WISE) event ‘on January 30. Here I learned about upcoming STEM events and saw the prototype Logo that in my opinion places among the highest standards in hemldry. The use of the (wise) Ow! in the artwork is inspiring and I have asked Joanne Serelis to introduce the story in a later article. As the WISE progam schedule firms up, I am also looking forward to sceing calendars of coming events and supporting short articles on ongoing STEM activities such as robot wars. All ofthis effort deserves to reach the 1100 subscribers to our newsletter. I expect to be more focused this year on. ‘what we are doing and less about the past. However, I do want to share with everyone past artifacts that still affect who we are and where we may want to 0. The first of these is a health chart of last year’s event attendance that neludes the speakers. In my years (14) at Chesapeake, I have never seen this data presented to the membership 50 well. ‘Mr. George Anderson INCOSE CC President ‘george anderson@incose.arg ome sven ore crm mapa MANES | ie wie pa tree $ Seine Spur =| Somme woe =) Falorwary 15,2014 scar Thinking outs the bx cA avaeste ‘oon wo i ite ier eee Semin Malone Chart 1. 2014 Chesapeake Chapter Dinners and Lectures. In Vol. 6 Issue 2 This isthe monthly newsleter for INCOSE Chesapeake, a local chapter of NCOSE Intemational. We sea not-for profit ‘ovganization dedicated to providing a forum forprofesionals pc ticing the at and science of Systems Engincering inthe "Northem & Centaal Maryland & So Pennsylvania area (3 Join INCOSE Today! The Chesapeake Chapteris always looking for volunteers to speak at our upcoming meetings! Please contact our 2015 Progams Director, Glenn Tasason, ifyou would like the opportunity to speak ‘orcan recommend someone, ‘The Chesapeake Chapter of INCOSE is proud to recognize the following omanizations for sponsoring our endeavours to expanding the understanding and appreciation of Systems floC:AJsersPatick/DocumertsINCOSE-CCNesleters/2015015%20 5200220 5: 20Nowsleters200RAFTS20 mlsoc/205 120'8- (2. Newsletor DRAFT OS! ‘The second artifact is an analysis of our two surveys from last year that sought to measure member inputs in two areas. These were programs and the other ‘membership atributes. The entire analysis is posted to our operational documents section on the library pull-down menus on the Website. I would like to briefly highlight what I think are significant items on this report. For Progams: * The dominant chapter technical interests are: Agile, DoDAF Architecture and Cyber security. + Interest in CSEP certification is low. = Lean SE is an emerging area of interest. For Membership: 35% of respondents held the CSEP Certification. 37% of respondents have been members for less than 4 years. In 2014, 118 new members or tansfers from other chapters were gained, Response to training courses was high with 65% showing interest. Only 11% expressed interest in running for the Board of Directors, (BOD) while 50% showed some interest in serving as an associate Board Member hope that this information helps to clarify the basis on which the BOD plans to move forward and also to serve as a benchmark for our past achievements Before closing, I want to share the most important metric we currently have— ‘our 7% solution. In a year when most INCOSE Chapters in the United States had declining memberships, Chesapeake grew by 7%. Our membership in December 2013 was 375 and in December 2014, 402. This means that the number of departures was exceeded by the influx of new arrivals. Thank you all for caring, participating and making us successful beyond expectation, George Anderson - INCOSE Chesapeake Chapter Present ‘Return to top 18 February, 2015 (6:00pm - 8:00pm): SE Consideration in the Design of Autonomous Air, Ground, Surface and Undersea Vehicles Presentation: Air, ground, surface and undersea vehicles are currently being used in the home, to support business opemations, for space explom tion and by most of the world’s militares. The next genem tion of unmanned vehicles will be autonomous, with vehicles interpreting and responding to the complex ‘world in which they operate in real time. This talk discusses autonomous unmanned vehicle teams that are capable of opemting with, or ‘without, real-time human supervision. The benefits of unmanned vehicle autonomy, ‘methods for optimizing team structure and optimizing the relationship between David Scheidt, Principal autonomous unmanned vehicles and humans Professional Staff JHU/APL will be discussed as will hardware in-the-loop experiments involving autonomous air, ‘ground, surface and undersea vehicles. Engineering in the local area: i BAIL The . Institute for Systems Research TX. JAMES CLARK ELIASSEN S GROUP & Sero-na i Camber '\ CyberCore JOHNs HOPKINS ‘et JseraPatick/DoctmetsINCOSE. CCN ewlatis/2019/2015%20%2002%20-%zoNewsltia 5200R AFT 42005sozvants 2015 2- Newsleter DRAFT 05 ml (Click here for more details orwy jncoses E-Newsletter suis In Vol. 6 Issue 5 President's Point of ViewAwnings Up and Tulips Everywhere You know that winter is defeated when the tulips bloom and many of the older homes in Baltimore City break out their awnings. Awnings may not be the mass fashion statement that they were around the turn of the last century, however, their architectural statement and utility can still be welcome to those Mr. George Anderson s cor h INCOSE CC President who experience subliminal feelings ‘george.anderson@incose.org Of comfort when “under canvas” during a rainstorm. In contrast, modern aluminum or fiberglass substitutes are almost always This is the monthly newsletter for annoying. INCOSE Chesapeake, a local chapter of INCOSE International. We are a not-for-profit organization dedicated to providing a forum for professionals practicing the art and science of Systems Engineering in the Northern & Central Maryland & Southern Pennsylvania area. A real canvas awning is a fascinating system with an interesting life cycle. The fundamental concept also has a rich history dating back at least to the Roman Colosseum.[1] The Loane Brothers Company in Baltimore claims to have made the first awnings in America around 1850 from a pattern brought fromFrance.[2] In a tribute to the timelessness of the awning, the Loane Family is still in business today and their employees have erected my porch awning every spring for the last 15 years. ) Rigging an awning is a skill that | recognize is not easy to learn. Sails and awnings are similar in that their shape can only be established by adjusting tension on the supporting ropes. In contrast, modern structures typically replace the ropes with beams and trusses. These carry the loads in both tension and compression and need fewer adjustments over their lifetime. Notable examples of other early tension structures are the Wright Brothers first airplane, the Conestoga wagon, a suspension bridge and the bicycle wheel. As a Chapter, we want to avoid the mode of governance that resembles the tedious process of adjusting the ropes on a tension structure and, instead, create a robust administrative structure more attuned to and benefitting from our profession as systems engineers. | believe that the 2015 Chesapeake Chapter Operations Plan completed in April is the BOD’s rope reduction documentation. In this plan we are doing the systems engineering up front and providing a solid basis for the year’s activities. Here are some areas in the plan that | believe create a solid basis for making efficient and realistic progress: + A graphic that explicitly aligns our mission with goals, objectives, initiatives, and metrics. (Appendix A) * See also the Goals Grid to understand how the BOD has mapped the year's decision challenges. (Appendix A) + Updated Chapter needs. (Appendix B) If needs are not realized there will be no growth. + An explicit implementation schedule for duties and activities specifically required by the bylaws. These include the annual election of BOD members and the annual financial audit. Other items are the submission of the Circle award data and submission of reports to INCOSE INTERNATIONAL. + Last, a detailed budget that allocates discretionary amounts for each Director permitting flexible execution and allowing the BOD in session to concentrate on strategic issues. Join INCOSE Today ‘The Chesapeake Chapter is always looking for volunteers to speak at our upcoming meetings! Please contact our 2015 Programs Director, Glenn Townson. if you would like the opportunity to speak or can recommend someone. The Chesapeake Chapter of INCOSE is proud to recognize the following organizations for sponsoring our endeavours to expanding the understanding and appreciation of Systems Engineering in the local area: Booz | Mean The , Institute for Systems J “Research Seen 7 ELIASSEN 7 GROUP serco Bringing service to life ‘S CyberCore ECHNOLOGIES| could go on but my point is to remind everyone that the plan is always available on our web site and provides a comprehensive window into how we will operate. | sincerely hope that our members will not treat the plan like shelf ware because the Chapter cannot succeed if the BOD is the only group aware and engaged in 2015. In other news + The Honorable Stephen Welby is leaving the Deputy Assistant Undersecretary of Defense for Systems Engineering position and being nominated for Assistant Secretary of Defense for Research and Engineering. No word yet on his replacement. * The DoD Architecture Framework (DoDAF) version 2.02 has been updated as of January 31, 2015, to Change 1. My reading of the change suggests that there is a new author who is reinforcing the primacy of the Metamodel (DM2). + The Chapter ESEPS held a summit meeting on Saturday morning at the Engineers Club of Baltimore to discuss the state of Systems Engineering in MD. David Fadeley, our first Chesapeake ESEP was the meeting moderator. The meeting marked a historic first for INCOSE and the attendees intend to meet quarterly going forward. + WISE continues to have good attendance at their luncheon meetings. | attended the April 24, 2015 meeting along with Past President, Erik Devito and Treasurer, Kent de Jong. The program was a panel discussion featuring women who had succeeded as entrepreneurs and business owners. This was a very successful event and more details will be provided in an after action report by WISE. My closing thought for the month is to comment on a query that came my way recently. The question was: What is the target attendance number for our monthly meetings? The short answer is that our attendance rates are slowly rising cumulatively but vary each time with the speaker, weather, other events and the timeliness of our advertising. When we do everything well, we can expect a high of 50 and 25 when we do less. The attendees are not the same each time and we do have many walk-in guests. Also, we should realize that the monthly membership meeting is just our baseline service. Of more importance to the membership at large are our training courses, tutorials, and special events. These capture the special needs and interests of our members but at a higher attendance cost. For instance, we are planning a three day hands-on class for IBM Rational System Architect with DoDAF in June and the expected cost will run around $1800 including meals and training texts. Dr. Mark Maier presented his seminal tutorial on Architecture last year and | heard many laments from people who wished they had known about the course beforehand. Please check the web site and newsletter for our offerings and use our on-line registration. No ropes here! 9g JOHNS HopkINs PROTEUS Opsnarr JVIAN EMNTeEc new book related to engineering? Letus nase, We'd love to hear about. may wind upin a for an atte? A review of future isue of our Newsletter Return to top[1]https://www. youtube.com /watch?v=UtwG_ziYIOY) [2}http:/ /www.loanebros.com/aboutus/index.html) George Anderson ~ INCOSE Chesapeake Chapter President A SPECIAL ANNOUNCEMENT / May 3, 2015 | have received the important announcement from INCOSE INTERNATIONAL that the Chesapeake Chapter has won the 2014 President's ae Award for Outstanding Achievement. This President's Cup _ award is granted to one chapter each year that scores highest on the Circle Award submissions Clearly, this is a cause for celebration and individual reflection on how well we have demonstrated systems engineering best practices both in executing the Chapter’s mission and in the promotion of Systems Engineering education throughout the technical community in Maryland. Our 2014 President, Erik Devito, deserves singular praise for leading us to victory and providing innovation and inspiration along the way. Please join me in thanking Erik and all who supported him. Erik will accept the award at the INTERNATIONAL Symposium in July 2015, and | know he will want to see as many chapter members present as possible, Elsewhere in this issue we have an order page for purchasing embroidered Chesapeake Shirts for those attending. | also want to offer heartfelt thanks to our sponsors, employers, and customers who all share significant credit for going well beyond thecall of duty in providing the Chapter with the encouragement and resources to serve our customers. These services evolved from a program of continuous improvement and we even created exciting and innovative new ones. None of this is easy and many hours of volunteer service should and will be recognized as we move through our programs this year. Being number one has ramifications other than the sense of accomplishment that | hope everyone will surely feel. We are now the INCOSE Chapter to emulate. All our activities, processes, governance documents and the growing library of YouTube videos are already being scrut ed and analyzed. No pressure, but we need everyone to help keep our performance and can do attitude consistent with our image! Some call this eating your own dog food. Thanks everyone, and please consider attending the IS in July. Bagh Dhary George Anderson, President 20 May, 2015 (6:00pm - 8:00pm): The Hype and Realities of Additive Manufacturing Presentation: The vision of additive manufacturing, which is fueled by recent and significant media coverage in both the popular and scientific press, is a spectacular view of potential things to come. Some have said that additive manufacturing will usher in a new industrial revolution that will forever p.change manufacturing supply chains, " defense logistics, health care, and how consumers acquire manufactured goods. Highly-publicized examples of spectacular University Applied Parts made via additive manufacturing Physics Laboratory Pave led some to conclude that this future vision is a certainty. This vision must be tempered though, by the technical challenges that currently prevent John A. Slotwinski, Ph. ‘Additive Manufacturing Development Engineer at The Johns Hopkinsmore widespread adoption of the various additive manufacturing technologies. In this talk | will highlight recent successes in additive manufacturing, describe current technical challenges and related research to overcome those challenges, and try to separate what | believe to be the hype and reality in the future vision of additive manufacturing. (Click here for more detailse(usvw.incose-ec.or2) Go to www.incose-cc.org/registration/ to register Parsons Auditorium, Bldg 1 Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD {© Map and Directions A Few Uncomplimentary Thoughts on Systems by George Anderson | enjoy reading just about anything non- fiction that is either old or relates tomy SYSTEMANTICS broad technical interests. The only real How Systems Workcand exception to old books is the occasional Especially How They Fail textbook or manual. Not surprisingly over the years, | have acquired information Ai that | realize may be applicable to the ‘ practice of Systems Engineering. Not too long ago, a book entitled SYSTEMANTICSL1] came my way and presented a charmingly different discourse on the inherent limitations of systems. The author, John Gall, a medical /y, doctor and faculty member at the John Gall University of Michigan presented a series aia of rules, theorems and axioms to describe system behaviors His definition of systems included humans, but argued that generalized rules should apply equally to the other components as well. These would include structural entities such as governments,companies, airlines and the complex technology used to execute their operations. The strength of his work was in the examples he used to demonstrate the rules. Many, if not most, of the examples were negative in their view of systems capabilities or the ability to meet the designers’ requirements. His introductory words are: SYSTEMS IN GENERAL WORK POORLY OR NOT AT ALL (1:2) The discussions of system dysfunction were entertaining but at the same time represented a challenge to many things that | thought were settled principles of systems thinking. The challenge was delivered in a forthright series of statements that fundamentally said: systems did not perform in the way we expect, the system opposes its own proper function and the system does not do what it says it is doing. These statements meant little until the author presented specific examples. (1:92-93) For me, the best example dealt with meeting human needs. To paraphrase The goal was satisfying a desire for a fresh apple to eat. * In the non-system case, a person goes to an orchard and picks a fresh apple off the tree. + In the small system, a person buys an apple from a local merchant who gets the apples fresh from a local orchard perhaps 20 miles away. * Finally, the big system is the supermarket chain that receives apples from thousands of miles away that are picked green and are ripened using a controlled process during transit that produces an apple that does not taste as good as the orchard fresh one. (1:37) This is an example of Dr. Gall’s Operational Fallacy or: “The function performed by a system is not operationally identical to the function of the same name performed by a man.” And, “A function performed by a larger system is not operationally identical to the function of the same name as performed by a smaller system”. (1.35) An important final insight is: “....most of the things we human beings desire are non-systems things.” (1:37) cokes This is a very powerful idea that is not F always appreciated in designing large or complex systems and conversely explains ge the success of electronic systems gadgets such as GPS and Smartphones. At no point did the author express optimism that systems could actually be without problems or meet their full capability. For instance, he is an early discoverer of the maxim that: “A complexsystem can fail in an infinite number of ways”. (1:93) This is today related to Murphy's Law/2] or Metcalf's Law/3] and is the province of the Failure Modes & Effects (FMEA) methodology. In all, there are 32 Basic System Axioms, Theorems and Corollaries that comprise Dr. Gall’s science of SYSTEMANTICS. Of these, several would suggest positive rules for systems life cycle management. This strong bias towards the inherent limitations and misbehavior of systems is what makes this book stand out from others. Reading elsewhere, there are good design rules for technology, but when the human is placed in the system either as an individual or a group, most systems can become unstable and unpredictable. | am reminded of my participation in the design and development of the A-10 aircraft back about the time this book was published in 1975. The preliminary design of the aircraft was sound but the human factors design of the cockpit controls took a long time to sort out. There was a great debate over automatic or manual changeover of the primary and emergency flight control systems in the event of hydraulic failure. The systems designers employed all the arguments that are heard today for automation. The logistics and operations teams disagreed and supported a manual system. Today, we know that the automatic system was inherently a wrong solution. It took authority away from the pilot to choose the time of changeover and it was a source of what we would call today latent undetected failures. The manual system could be tested and, more importantly, the pilots were able to practice the flight control changeover during training flights. The automatic system did not have this feature and was activated using only the input from a single sensor. Years later in the Gulf War, a female A-10 pilot, Captain Campbell had a loss of hydraulic pressure due to a missile strike and used the system to recover the aircraft and fly to her home airfield. She praised the manual system as working just as she had practiced in training.[4] The message here would seem to support Dr. Gall’s Theorem that: New Systems Generate New Problems or Systems Should Not Be Unnecessarily Multiplied. Overall, SYSTEMANTICS is a thought provoking look at the negative side of systems behavior and although the book is out of print, it has a growing following on engineering blogs. There are also later works that continue to refine Dr. Gall’s rules and provide more examples of systems misbehavior. My example of the A-10 aircraft manual flight control reversion system is just one example of the application of systems thinking that | have gained through my own varied engineering experience. | may be motivated by Dr. Gall’s example to share more complexsystems stories in the future. In the meantime, | urge everyone to read Dr. Gall’s book, SYSTEMANTICS, and find insight or validation in your own concepts of systems thinking while considering that GREAT ADVANCES ARE NOT PRODUCED BY SYSTEMS DESIGNED TO PRODUCE GREAT ADVANCES. (1:93) [1] By John Galt, Quadrangle/The New York Times Book Company, Inc., 1975 ) [2] Stated as: If anything can go wrong- it will. [3] Metalf’s law states that the value of a network increases in proportion to the number of its nodes squared (N2). It also increases the complexity and failure modes by the same amount. ) [4] httos://www.voutube.com/watch?v=F9DBckCilSE) Where Is Arthur Fry by Zane Scott We often think of creativity as the ability to envision the need for something that we create to fill that need. This is the classic “inventor” scenario. But creativity can also be the vision to see new uses for something that already exists. Dr. Spencer Silver was a 3M Senior Research Chemist looking for a super-strong adhesive in his laboratory. Instead he produced a “low tack” adhesive that stuck with the application of pressure but, while it adhered with enough strength to hold paper in place, it was sufficiently weak to disengage without tearing the surfaces. In addition it would re-adhere repeatedly. Silver saw the new adhesive as a spray product that could be applied to surfaces (like bulletin /white boards) allowing them to hold documents pressed (posted) on them. He evangelized his idea within 3M but got nowhere until a fellow researcher, Art Fry, heard his pitch. Fry sang in his church choir and used little pieces of paper to mark the morning's hymns in his hymnbook. He saw Silver'sadhesive as a way to hold the bookmarks in place as he turned back and forth following the order of service. Instead of spraying the adhesive onto the receiving surface he applied a small amount to the bookmarks. They then stayed in place until intentionally removed at the end of the service. As they say, “The rest is history!" and after some additional development work Post-It Notes became a huge commercial success for 3M. The point is that this success needed not only the genius of the inventor, Dr. Spencer Silver, but the vision of the researcher, Arthur Fry, who saw the adhesive in a whole new way. In the systems engineering world we hold a powerful set of tools in our hands. Model-based systems engineering (MBSE) is a potent problem solving method especially in the company of a powerful tool like Vitech’s CORE®. We owe a great debt of thanks to the intellectual giants like Jim Long who positioned us in a place of such power over our problem space. But if we are to really unleash the true power of MBSE and its tools we need the Art Fry type vision that will allow us to see the method and tools in new ways. We need to recognize that Model-based Systems Engineering is really Model-Based Problem Solving! What does that mean? In general parlance the term engineering implies a tangible “things” focus. In fact, the dictionary tells us that engineering is “the art or science of making practical application of the knowledge of pure sciences, as physics or chemistry, as in the construction of engines, bridges, buildings, mines, ships, and chemical plants.” But the power of MBSE has a wider potential. Systems are not just physical. Read Peter Senge's Fifth Discipline or Russell Ackoff's Redesigning Society. Both provide an excellent look at systems and why they are not limited to the physical. Airplanes and tanks and submarines are systems- but so are healthcare delivery processes and regulatory structures. In an industry pointed primarily at a shrinking market sector we sorely need the “Art Fry" genius to leverage the “Spencer Silver" tools and methods we have at hand. It is a new way of seeing how we can serve customers and the new vision of who our customers might be that can expand our market space and economic possibilities. Are you out there Arthur Fry? © Vitech Corporation 2015, Reprinted by Permission HOW TO RECOGNIZE YOU HAVE A SYSTEMS PROBLEMby John Thomas As a senior manager, has this ever happened to you? A senior executive finds “herself” faced with a product that is incurring major cost overruns or schedule delays. When she asks what the problem is, she’s told, “The requirements keep changing.” Or perhaps she hears, “A system component has to be significantly redesigned.” These responses could be indications that there is a problem with product quality, choice of technology, or manufacturability difficulties. But there's just as much chance that the culprit is a system problem. To determine whether you do have a system problem, you need to perform three tests. These tests will show if delays and cost overruns are arising for one or two reasons. The first could be because the components of the product don't interface with each other as a system. This is analogous to putting together a child’s bike. If the parts in the box don't fit, then you won't have something that looks like a bike. The second could be due to incomplete requirements that went into building the components, which would result in a system not functioning as expected. In the bike example, even if the parts do fit, the bike may not work as intended. For instance, the bike doesn’t stop properly because the brakes don’t have proper contact with the wheels. Test #1: Are the complaints of changing requirements primarily coming from the component builders? If so, the team that is responsible for the system design has not finished their work (completion of the design or integrity of the design). As with the bike analogy, the team is continuing to finalize the design of the bicycle. And as it does, the team realizes that the gears ordered from the component builder will make it too difficult to pedal. Trying to get it right, the technical team changes its requirements to the gear manufacturer. Test #2: Are the cost overruns or schedule delays caused by the system not behaving as expected during system test-and- integration activities? If so, your technical team didn't have the time to ensure the interfaces were fully defined and properly described to the component builders. You might have components that fit together, but won’t function as intended. As with the bike, you finish the assembly and discover that a rider can only pedal backward, due to the incorrect interface between the crank, the gear and the brake. Test #3: Are the cost overruns and schedule delays arising becausethe user or investor is reporting that the system is not interacting with other systems as expected, and so expensive and time- consuming component fixes are needed to generate user or investor acceptance? The bike runs fine, but accessories, such as a standard aftermarket odometer, do not function properly. If your answer is “yes” to any of the preceding questions, then your delays and cost overruns are probably the result of a system problem, and the root of the issue is the components were acquired before the system design was completed. The component builders have only a portion of the critical information they need to build proper components that will work within the system. So the built components either will not interface with each other, or will not have the integrated capabilities that would allow the system to function as it should. This will result in components and integration activities having to be reworked, often at great cost. The risks associated with a system problem can be reduced if certain steps are taken before the project begins. If the senior executive is experiencing delays and cost overruns, she should ask herself: are there sufficient numbers of qualified system engineers, early enough, on the project? And equally important - do the systems engineers have the time to fully complete the design before the components are acquired? If not, the organization's programs will continually face delays and overruns. INCOSE_Fact_Sheet.1_12.16.11, Reprinted by Permission Return to top Upcoming Events and Announcements * May 20, 2015: Dinner Lecture - 3D Printing; John Slotwinski * Interested in Jobs Networking? Contact Mark Kaczmarek at mkaczmarekengr@comcast.net Te es aa ce ered rcp apenas raion isi Eos ee era Doe, csc cracks fare ig Mie oe ee E sess you st ouritcose chunoeais chan webate FOF aNY Comments or suggestions about this newsletter please e-mail our President, George Anderson or our Communications Director. Pat Williams. We value your feedback. Board of Director Officers, 2015- president: Mr. George Anderson~ Past President: Mr. Erik DeVito Directors at Large- communications: Mr. Pt Wilms Programs: Mr. Glenn Townsonim Email not displaying correctly? View it in your browser, mat. - INCOSE Chesapeake Chapter erne - President's Point of View June begins a busy summer for our chapter. Our monthly membership meeting is coming up on Wednesday June 17, 2015 and will feature the Video, The Deming of America, a dramatic look at the origins of the process improvement movement. This video was originally produced for Television by Priscilla Petty. We use it with her Mr. George Anderson kind permission and wish to thank INCOSE CC President her for her continuing support of our george.anderson@incose.org educational programs. Closely following this meeting, we have our IBM System Architect with DODAF class being held in the Kossiakoff Center on Monday through Wednesday, June 29, 30 and July 1, 2015. This course is hands-on and is the best chance to actually become proficient in producing DoDAF, DM2 compliant architecture data models. The course is presented by AVNET, a licensed IBM training provider who provides training materials and a completion certificate. Breakfast and lunch menus are part of the tuition fee and are provided by Sodexo, the on-campus contract catering service. The class is limited to 12 persons so that the instructor, Edward Vail, can provide personal assistance to each student as they struggle with the sometimes confusing menus and other options of System Architect. (| completed this program last year and | speak from experience.) The Chapter is working as a partner with AVNET to bring this course to our area at lower cost and a convenient venue, and we hope our members who need this level of training will be ng June 201: E-Newsletter routs This is the monthly newsletter for INCOSE Chesapeake, a local chapter of INCOSE international. We are a not-for-profit organization dedicated to providing a forum for professionals practicing the art and science of Systems Engineering in the Northern & Ceniral Maryland & Southern Pennsylvania area.able to attend. The last event is the most important. We must prepare for the International Symposium being held 13-16 July at Seattle, WA. We have advertised Chesapeake shirts on the web site and encourage everyone, but especially those who are planning to attend, to purchase a shirt. This is to show your affliation as we are presented with the President's award for the unsurpassed performance of the Chapter mission in 2014. There is a two-week lead time so please act promptly. Challenge coins will also be available for purchase at the next, and subsequent, member meetings for those who want to further prepare themselves for attending the IS. (For those attending who do not have chapter shirts or coins, we have a requirement for several attendees to wear a large MD crab or Chesapeake heron costume as an alternative.) Other planning this month is directed toward making our Systems Engineering Professionals (SEP) reception a repeat success. This year, we are embracing our regional chapters, Washington Metro and Southern MD, in an attempt to reach out to more SEPs and potential candidates. As in past years, we welcome our partners in Government and industry and other engineering and professional societies to attend and enjoy an inspiring social event with featured speakers and an atmosphere of elegance that always delights and enhances our appreciation of this event. The reception is scheduled for Wednesday evening, the 26th of August 2015 at the Engineers Club of Baltimore. The online registration for the event will open early for your planning convenience. The SEP reception is not complete without announcing and honoring our new certified professionals. We will honor those who have attained the highest level of achievement, the Expert Systems Engineering Professional or ESEP. | am pleased to announce that we have two new ESEPs as of this writing, Myra Gross of Jovian Concepts was notified in January and Craig Tyler of Vencore was notified last month. We will be honoring them and any further additions at the Reception. ‘As we move through a busy summer, please remember important changes taking place affecting the practice of systems engineering. The biggest news this month is the release of two DoD supplements to the 1SO 15288:2015 standard. Among other things, these supplements require the use of the standard in DoD procurement processes. This is a significant change in DoD policy and a huge vote of confidence for the practice of systems engineering in general. We, of course, expected this, because of our January presentation by Gary Roedler, who played an important role in drafting the standard, In closing, | want to continue to urge everyone to become more involved Join INCOSE Today The Chesapeake Chapter is always looking for volunteers to speak at our upcoming meetings! Please contact our 2015 Programs Director, Glenn ‘Townson, if you would like the opportunity to speak or can recommend someone. ‘The Chesapeake Chapter of INCOSE is proud to recognize the following organizations for sponsoring our endeavours to expanding the understanding and appreciation of Systems Engineering in the local area: n | Hamiltor The Institute for Systems Research TE JAMES CLARE ‘% CyberCore TECHNOLOGIESin the systems engineering profession and to consider the benefits of spending some time helping the Chapter execute the important work that we graciously provide as a focus on, and example of, systems excellence. We believe that this contributes measurably to Maryland’s sustainment and growth. George Anderson ~ INCOSE Chesapeake Chapter President 17 June, 2015 (6:00pm — 8:00pm): The Deming of America; Produced for Television by Priscilla Petty Presentation: This video, originally produced for Television by Priscilla Petty, provides a dramatic look at the origins of the process improvement movement. Our nation must work once again to come out of our crisis. We're challenged by global and local events. But the proven strategies in this documentary can help our country transform and innovate. Dr. W. Edwards Deming is shown at his unrehearsed best at his home, at a seminar, and in thought-provoking specially selected segments from an all-day interview with Priscilla. Brief remarks from Fortune 100 CEOs, who learned from Deming, show how he affected their thinking about their lives and companies as he worked with them to effect the transformation. Inspiring. Produced in 1991 by Petty Consulting Productions. Click here for more details:(www.incose-cc,ora) Go to www.incose-cc.org/registratian/ to register Parsons Auditorium, Bidg 1 Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD (Map and Directions 9 JOHNS HOPKINS APPLIED PHYSICS LABORATORY faSci (9 Corporation’ JGYIAN BItrec vencorThe Institute for Revisiting the Wright Brothers and the Sound of Bells Systems George Anderson, ESEP JANES uae 3 June 2015 Apracticing systems engineer should consider approaching all projects 7 GROUP as having unknowns that will require in depth examination and perhaps new insights or understanding. There are a lot of knowledgeable subject matter experts (SME) available but few of them can help when the information or practice is obscure, little studied or just unknown. The se rco arrogance of assuming adequate knowledge to accomplish a task is a eringogsevice 7 constant engineering hazard dating back to at least the ancient Egyptians who at one point had the world's greatest building failure when an almost completed pyramid collapsed into a heap of dressed BSP stone blocks. The giant debris field stil exists today as an enduring ; reminder to do more thorough research on unknowns. [1] ‘S CyberCore TECHNOLOGIES We might be able to forget this 4640 year old disaster if more recent challenges were not so similar in the form of assuming adequate knowledge. | have worked on two projects that still amaze me as to the methods used and the types of critical knowledge involved. These involved the Wright brother's progress towards manned flight and the analysis of the sound of bells. Both subjects would not have been of interest to me had | not been given systems engineering tasks that required me to fully understand the technical details of these two somewhat different technologies. faScitor rare) JOHNS HOPKINS Figure 1: Meidum Pyramid APPLIED PHYSICS LABORATORY 2625 BC ‘The Wright brother's saga has been told many times but the latest work by historian David McCullough entitled, The Wright Brothers, is popular enough to become first on the NYT best selier list this week and inspire me to mention an example of their perseverance. | am informed on most of the Wright's technical advances having received my degree in Aerodynamics from an institution[2] that lies only a few hundred yards from Huffman Prairie—the Wright's first aircraft flight test facility after Kitty Hawk. Although there is much to admire and consider about the Wright's technical experimentation and development efforts, the point | especially want to highlight is their questioning of existing data on manned flight. They were so concerned that their early test flights were not consistent with existing data on the lifting forces of wings that they built their own wind tunnel. Using this tunnel, they spent hours testing wing shapes until they were sure that existing data was wrong. Before the Wright's tunnel, there were noestablished devices that could be used for measuring forces on the test wing specimens. My wind tunnel testing occurred in 1973. This was during a period when mathematical modeling of airflow over wings was heavily funded. News from the physical world that conflicted with the models was not welcome and there was a great deal of resistance to testing in general. Thanks to the example set by the Wright brothers, wind tunnels continued to provide real performance data that was used to design new aircraft and reduce risk. Today, we still have areas that are not well understood such as vortex flows, and some aspects of hypersonic flight. We also know little about the regime of microscopic flight (low Reynolds numbers) where many want to explore and develop unmanned micro vehicles. The problems faced by the Wrights are Co similar to many that we encounter today. Itis always true that you need to explore all the problem space to find what you don't know and make plans to deal with it, Like the captain on a ship, if you see an area of poorly charted waters you may avoid failure or uncertainty by circumnavigation. If you must sail in the unknown area prudence dictates that you study whatever information is available, make estimates and provide contingency plans for coping. The Wright brothers did not see the absence of a suitable tool to measure wing lift as an insurmountable barrier. They simply designed and developed their own. My other area of tracking the unknowns takes us to the much older technology of bells. Figure 2 The Wright Brothers Wind Tunnel on display at the USAF Museum, Dayton, OH Bells represent an ancient technology that continues to serve a variety of purposes in almost every culture. Bells were being made before any scientific analysis using modem instruments and theories existed. The sound of the bell was its primary distinguishing feature and a customer, or customers, purchasing a bell had very strong ideas what that sound should be. A few years ago, | was asked to oversee the founding of a sizable bell and assure its performance in my capacity as a test engineer. Why anyone thought | knew anything about bells says a lot about the management of the auto industry at that time, but also it may have more to do with the assumption that bells were just shapes of metal. | started my task with just that assumption and in several days of research was considerably humbled. | not only did not know how a bell was made, | did not know how the bell made its sounds, what they were, or how one controlled the process to achieve these sounds. ‘SMEs could not explain what they knew in enough technical detail for me to make any progress. | considered the explanation of tuning a bell especially baffling. Clearly, vencor This Newsletter is to serve our members and is open to all for contributions. Do you have an interesting idea for an article? A review of a new book related to engineering? Let us know, We'd love to hear about it. It may wind up in a future issue of our Newsle! Return to topI needed further study. Later, | understood one reason for my confusion was the terminology used by the few people who knew about bells. After all at that time, there were only three bell founders in the US and less than eight in Europe. Thankfully, the bell project was cancelled before my project was memorialized in a two-ton mass of copper-tin alloy scrap. What | had leamed in the meantime was considerable. The highlights were: + Acomplete course in sound measurement permitted me to understand how to test a bell’s sound pressure emissions and describe them in acceptable laboratory terms using calibrated and repeatable processes. * I learned the language of the bells. People who write about bells talk in the language of music, and early design rules of thumb further obscured this by using centuries old jargon probably made legitimate by medieval guilds protecting their art. * Tuning a bell almost always involves removing metal from the inside of a newly cast bell. + Removing metal from a bell may not always produce the desired result. * In 2015, there is more, but still incomplete, theory on precisely how bells produce their sound spectrum and what constitutes the best or most desirable sounds. [3] + Ihave learned that researchers have established that the bell sounds are not the total system under study. The human ear with its perceived pitch and aural harmonics alters the sound of the bell to another pitch heard by the brain's auditory receptors. [4] This effect is so significant that testing of humans in the loop has drastically changed the desirable spectral specifications for a bell Overall, | concluded that in the bell industry, nobody understood how to meet a customer's expectations. This was partly because there were no modern technical standards and partly because the customer was probably expecting the sound produced by another bell. Rules of thumb and proprietary secrets ruled the : industry and in the end you got a product _ Figure 3. The Ten Ton that at best was tuned to nominal sound Weight Berlin Freedom Bell spectrum. Customers bought from the most prestigious or oldest foundry and humbly accepted the product as delivered. A delivery specification, if such was involved, was typically vague as to spectral performance. This state of affairs led me to believe that our modern audio spectrum measurement capability was useless if the test specification was defective or not validated. Unlike the pyramid collapse, neither of my learning experiences produced immediate disaster. On the other hand, they taught me to bevery careful about unknowns. The Wright brothers inspired me to aggressively pursue knowledge and the short-lived bell project taught me not to depend completely on SMEs to completely fil the knowledge gap. Special knowledge is cumulative and has a way of helping in future projects and providing special satisfaction. | still enjoy reading about new discoveries in vortex flow and hearing the sounds of church bells on Sundays. Hear the Freedom Bell Ring: v=AxWInbQvexT [1] bttp://en.wikipedia.org/wiki/Meidum [2] The Air Force Institute of Technology, Wright-Patterson AFB, OH, Established 1919. [3] http://www, hibberts.co.uk/index.htm [4] Our Acoustic Environment, Frederick A. White, John Wiley & Sons, New York, 1975 ‘Return to top Elicitation and Analysis of Requirements Gary Wieboldt, ESEP 27 April 2015 In the classic system engineering Vee diagram, a keystone, earlyactivity in the process are requirements. The process consists of: Requirements Elicitation (get them) Requirements Analysis (can they be done?) Specification (document them) Requirements Validation and Verification (did you build the right thing and was the thing built right?) 5. Requirements Management (how do | change them?) PENS We believe in the mantra of a “complete but minimal’ set of requirements is important to prevent over complexity (hence reduced reliability, and a host of other issues like cost) of a system: agora. oF THe ]E[ now oun eaoouer Fnoovcr FEATURES Tawonnaces THAT EAGH OF YOU epderoose oF ‘DEMANDED. ‘GonrUextTy. | ‘Communication of requirements is key, so that all stakeholders and engineers know what product or service they are going to receive. They cannot be developed in a vacuum, heavy interaction, with all stakeholders are necessary to get good requirements.: Here | would like to focus on the difficulty in steps one and two: getting them (Requirements Elicitation) and understanding if they are doable (Requirements Analysis) Interpersonal relationships are Key in the first two steps: between customer and vendor and all the people who make up the consolidated team. The elicitation process is a system of people, interpersonal relationships, thoughts and ideas. in the elicitation phase it is key to not only identify stakeholders, but to clearly understand their roles and how you are going to manage their varied requests. As we elicit we occasionally perform in situ requirements analysis to understand the validity of consequences of the proposed requirements. ‘Sometimes this analysis has to be performed offline from the elicitation process due to the interrelationships and complexity of the requirements set. But there are times where during the elicitation phase obvious conflicts are present and need to be adjudicated.That brings us to this video: https: //www,youtube,com/watch? v=BKorPSSAqvg which, although a farse, does show how elicitation and analysis of requirements from different stakeholder views can make an engineer's job very difficult to accomplish. Especially if he/she is "An expert’, and the people around them are far from it. ‘Return to top. Seven (Plus or Minus Two) by Zane Scott George A. Miller died July 22, 2012 at age 92. He was truly a giant in the world of psychology. In 1956 he published an article in Psychological Review entitled "The Magical Number Seven, Plus or Minus Two: Some Limits on Our Capacity for Processing Information". His ideas were especially important because they were introduced into the stimulus-response world dominated by behavioral psychology. AS he developed his thought he posited an information processing theory of human cognition where behavior resulted from taking in and processing information instead of being the deterministic outcome of conditioned responses to external stimuli that behaviorists believed drove a person's behavior. This had paradigm-shifting implications for the field of psychology in general but perhaps the most important to the world of communications was his research showing that, while long term memory capacity was practically unlimited, the short term memory that we use to take in information for processing is essentially limited to seven “chunks’- plus or minus two- hence the tile of his article. Any attempt to hold more chunks in short term memory results in loss or degradation in the processing as with objects falling off an overloaded desktop, In a practical sense we do not have direct access to the unlimited long term memory when we communicate. We are only able to place chunks of information before our ‘receivers’ for reception into short term or “working” memory for processing, Therefore, we need to respect the existence of a short term memory limitation as we chunk our information and organize it for presentation. ‘There has been a great deal of work suggesting that the limit is different for different kinds of information and that the limit may be lower than seven. Some researchers have suggested four items and some three, but whatever the number there is now broad acceptance of the existence of the limit. For that we must tip our hats to Miler. ‘The next time we do a presentation we should pause to think of him and heed his work. Do our slides violate the principle of a limited workingmemory? Does our organization honor the principles behind chunking information for processing? We can all think of violators and their violations of these principles. Perhaps by remembering Miller we can avoid joining those ranks. We may not become slaves to the number three, or four or even seven but we can certainly avoid the numbers 20 and 30 and 50! ‘As we do so, we thank you George. May you rest in peace. © Vitech Corporation 2015, Reprinted by Permission Why Systems Engineers are Essential to Your Organization by John Thomas Asystems engineer is invaluable to an organization by preventing system problems from impacting the cost and schedule of programs. They rely on their technical and leadership skills to reduce the potential for rework associated with changes in design, interpretations with requirements, or confusion with the user's intent. They are the ones who pay attention to the system details and ensure the user, the buyer, and the investor are all satisfied with the project's outcome — which is the ultimate measure of success. Itis the systems engineers’ role to understand the intended use and ultimate purpose of the system, and then to clearly communicate the proper system design to component builders. This begins by translating the user's vision into information required by the architecture team to generate an optimal systems design. Itis followed by the systems engineer providing component builders with a translation of the architecture teams’ vision, along with the appropriate technical requirements for building each component within the system. Yet systems engineers know itis not enough simply to deliver a solution that works. To meet the user's highest expectations, they use their skills and insight to understand the user's perspective and to establish those expectations in the technical language of systems builder. Often, this involves helping the end-user think through a more complete definition of a successful outcome by producing missing details critical for influencing the systems design. Only when the systems engineer gets it right, will the user — as well as the investor and the buyer — completely embrace the result. ‘Systems engineers also recognize that they have to match what the architecture team is hoping to accomplish with what the componentbuilders can best provide. Through their leadership skills, the systems ‘engineer works toward an ideal balance between the user's vision, and a systems design that is easily implemented. When this balance is achieved, the systems engineer packages the builder information into three critical areas: 1) how the component must function; 2) how it needs to interface with the other components; and, 3) how it must adapt to the larger operational environment. When these “translation” activities occur correctly, the user's vision is achieved akin to providing a finely-tuned racing bike suitable for the Tour de France. When these activities are missing or poorly accomplished, the bike intended for the Tour de France may wind up with knobby tires and a heavy frame, not the ideal bike a rider needs in order to win. Across an organization's products or services, systems engineers also provide critical leadership for integrating the technical activities, They have skills to influence multidisciplinary teams to reach consensus on how the system solution should come together. As problem-solvers, they focus on outcome, not process. They ‘own’ the project: they don't start from the position that expensive rework or user dissatisfaction—or for that matter, a builder delivering less than ideal components—is someone else's responsibility. They step in and resolve the issue, often before most others even know the risk exists. As translators, systems engineers can prevent many of the system problems that tend to derail projects. As leaders, they deal with the complexity of those problems as they arise. This powerful set of skills, abilities and know-how is why systems engineers are a valuable resource to an organization, INCOSE_Fact Sheet_2_01.09.12, Reprinted by Permission Return to top Upcoming Events and Announcements + Click here to order your Chesapeake Chapter Shirt + June 17, 2015: Dinner Lecture - Movie Night: The Deming of America + June 29~ 1 July, 2015: Course on DoDAF 2.0 Modeling with IBM Rational ‘System Architect V.11.4; by AVNET's Ed Vail + July 15, 2015: Dinner Lecture — SE Consideration in the Design of ‘Autonomous Air, Ground, Surface and Undersea Vehicles; David Scheiat, Principal Professional Staff JHU/APL (Tentative) ‘+ August 19, 2015: Dinner Lecture ~ In Close Encounters We Mostly see Ourselves—The Origin of UFO Alien Faces; by Dr. Fred Malmstrom (Tentative) + August 26, 2015: Systems Engineering Professionals (SEP) Reception + Interested in Jobs Networking? Contact Mark Kaczmarek atie cece ee See Se eee ING SBE as aa re cor any comments or suggestions sbout this newsletter please e-mal our Preside George Anderson or our Communications eee coe —— Board of Director Officers, 2015 — President: Mr. Geerge Anderson Directors at Large Past President: Me. Erk DeVito Communications: Me. Pat Wiliams = President Elect: We. John Boeco Programs: Mr. Glenn Towson ~ Treasurer: Me. Kent DeJong Membership Commitoe: Gundars Osvalds ~ Secrtary: Me. Mark Kaczmarck Please use the Forward email link below so we can invite your friends to join our mailing list. Thanks in advance, INCOSE Chesapeake Chapter © 2015sozazos 2015-7 - Newsleter DRAFT 05m Email not displaying corectiy? View it in vour browser. INCOSE Chesapeake Chapter oat vy - E-Newsletter ms Engir July 2015 + Back Issues. President's Point of View The best events of the year are yet to come! July marks the midpoint of our ‘chapter programs. Moving forward from the date of this writing, | am pleased to announce that the IBM System Architect with DoDAF class is beginning on Monday June 29 with 8 students. This course is hands-on and is the best chance to actually become proficient in producing DoDAF, DM2 data models. The course and instructor are the best available and we hope to fitin a repeat performance in the fall or early spring. We also plan to schedule an updated DODAF 2.02, (change 1) course in October. Dr. Drew Hamilton of Auburn University and TTC Seminars taught the class in August 2012.[1] We had a record enrollment (31) on this first event and many of these students are today employed as successful DoDAF architects. It would be a misfortune to miss out on training that would enhance your ability to qualify for a new SE position. Mr. George Anderson INCOSE CC President george,anderson@incose.org This month's membership meeting has been postponed from July 15th to July 22nd to allow for the retum of the 30 or so members who are attending the International Symposium in Seattle, WA. The meeting will feature a “Meet the Board of Directors” panel discussion. This is in tion of our fall elections and will, at minimum, address the challenges facing the chapter as we move forward into 2016. To set the tone for this event, | can share with you the results of our latest survey that shows Increased demand for our training offerings and little interest in running for chapter offices. This is a great opportunity to help shape our future by listening, learning and participating- hopefully in that order. The 2015 Elections for the Board of Directors (BOD) will be held in ‘September and the call for nominations is open until August 30, 2016. This year, we will vote to fil the programs and membership chairs as well as the new president elect, To volunteer or recommend a colleague, please contact the elections committee via the election page on the web site or email John Boccio, Kent de Jong or Erik Devito, In Vol. 6 Issue 7 This isthe monthly newsleter for INCOSE Chesapeake, a local chapter of INCOSE Intemational. We are a not- for-profit organization dedicated to providing a forum for professionals cling the art and science of ‘Systems Enginaering in the Northem & Central Maryland & Southem Pennsylvania area ‘The Chesapeake Chapter is always looking for volunteers to speak at our Upcoming meetings! Please contact our 2015 Programs Director, Glen Townson. If you would ike the ‘opportunity fo speak or ean recommend “len AdeersPabickdDoureisNCOSE-CCNewalatars/2015%20 200720 42INewslatier K2OORAFT¥2005 nl 1»roxas {2018-07 -Newslatr DRAFT 05m ‘The August meeting will feature an invited panel of International ‘Symposium participants who will discuss selected topics from this, event, Membership Director, Gundars Osvalds, is organizing and ‘moderating this event. ‘September will find us listening to a human factors engineering presentation by Dr. Amy Bayes and other faculty members from Johns Hopkins University. The presentation will be a preamble to a Saturday tutorial that will be scheduled soon after. They also have formal course offerings in the fall and hope to interest systems engineers in enrolling, ‘We will announce the tutorial as soon as a venue is established. Dr. Howard Eisner’s tutorial will be held on September 19, 2015, after being a weather casualty in February. A flyer will be coming out next month giving the time and location. He will continue his lecture series entitled: Thinking Outside the Box. View his last year's tutorial at: httos://www, youtube, com/watch?v=BUX4]Us5MdA The October and November meetings are reserved for large events. In October we are planning to have a joint PMI-INCOSE meeting featuring the Study on improving Integration of Program Management and ‘Systems Engingering.[2] The November meeting will focus on Systems Engineering Standards to include the DoD addendums to ISO 15288. Mark your calendars for August 26, 2015. Our 6th annual SEP reception vill take place at the Engineers Club of Baltimore. Honored guests include Ms. Courtney Wright, INCOSE Certification Chairman, Mr. Robert A. Gold, Director of the Engineering Enterprise within the Office of the Deputy Assistant Secretary of Defense for Systems Engineering (DASD(SE)) and Mike McNamee, Chief Systems Engineer, NSACSS. To promote broader participation, we are inviting SEPs from MD, VA, District of Columbia, DE, and Southern PA. Locally, we will again be pleased to invite our employers, CAB members and associate engineering societies.[3] ‘Another program being planned for August is a tour of the ‘Smithsonian's Udvar-Hazy Air and Space Museum near Dulles Airport. This is a family activity involving chartered buses, docents, and box lunches. What could go wrong! If you are interested, please make your comments on a blog sheet that Communications Director, Pat Wiliams, will put up on the Chapter Web site so we can gauge the level of interest and establish the resources needed. I now want to discuss the health of the Chapter at mid-year. Kent de Jong our treasurer will present the results of our audit committee's work at the July Membership meeting. We continue to do well, if somewhat behind schedule, and | want to remind the membership to attend and review our “report card" on how the BOD is executing the Chapter’s, financial program. This is a one-time event as we do not publish or release our audit results. Another important area is membership. Membership Director, Gundars Osvalds, is attempting to gauge the trend of our retention and new member statistics. We know that other chapters are having difficulties maintaining their memberships but our chapter last year had more new members than departures (or non- retentions). In mid-June we noted a report in the INCOSE Intemational Connect site that showed 348 members in the Chesapeake Chapter. This would be an attention getting number given our January strength of The Chesapeake Chapter of INCOSE is proud to recognize the following organizations for sponsoring our endeavours to ‘expanding the understanding and appreciation of Systems Engineering in the local area: The . slnstitute for Systems Research CLEAR oe (> ELIASSEN GROUP serco Bringing service to life SE, x erCor TECHNOLOGIES ‘le 1:ASeers Patrick DocimertsINCOSE-CCNewslaters2015%20- 92007420 U2INeslee%200RAFT%200 irlsorazois {2015- 07- Newslater DRAFT OS. 402 until we realize that last year we had a similar dip going into the ‘summer. We really cannot say how we are doing with membership until we see how the number trends over several months. Numbers represent only the measurement side of managing our membership. What are we currently doing about retaining and attracting new members? The answer is in two parts. First, when it comes to retention, | personally believe that the primary method of retaining members is to provide professional training and a forum professional presence and perhaps leadership opportunities in the engineering community. The second part is our efforts to bring in new members: Here, the BOD as a team carefully updates the Chapter TriFold each year to provide the best possible recruiting tool. We believe this handout describes our chapter, its goals, purpose and programs. If we could only get these into the hands of potential members all would be well. Each year, however, it appears as if our members consider distributing Trifolds as somebody else's business. | frequently notice that many Trifolds are left behind after an event and end up being deposited into the garbage often by our own members, | ask all of you to think twice before abandoning the Trifold as our recruiting medium. Handing a brochure to a colleague is absolutely the least that you can do to promote our chapter and the practice of systems engineering. Certainly we do more by manning booths at conferences, speaking engagements to other engineering societies and ‘so on, but, these opportunities cannot have a significant impact given the very few individuals that are available or wiling to support these ‘opportunities, | could get into the impact of declining membership on our services but with the increased awareness and cooperation of our current members, I believe that we can avoid or at least delay the contraction that appears to be affecting INCOSE International at large. This has been a long missive but it covers only the highlights of what we are doing. It’s all very complicated - even for systems engineers. Please make a commitment to attend our July 22nd meeting and help plan our future. [1]See After Action Report at: httn://www incose-cc,org/13-14= alig-understanding-and-using-the-new-dodaf-v-2-02/ [2]White Paper Presented at the 23rd INCOSE Annual International Symposium, Philadelphia, 2013, [3]Associate societies include: AOC, AIAA, IEEE, SAE and SES. Association of Old Crows (AOC), American Institute of Aeronautics and Asironautics (AIAA), Institute of Electrical and Electronics Engineers (IEEE), Society of Automotive Engineers (SAE), and the Standards Engineering Society (SES). George Andersan - INGOSE Chesapeake Chapter President 9 JOHNS HopKINSroxas {2015- 07-Newsletee DRAFT OStem! 22 July, 2015 (6:00pm - 8:00pm): A Panel Discussion with the INCOSE-Chesapeake Chapter Board of Directors Note, this is not a typo. Our regular monthly The meeting will be on the 4th Wednesday of insite for July (the 22nd) to accommodate our Systems members who are travelling to the INCOSE ys ib International Symposium in Seattle, _ Research _ Washington. Join us at 6PM on the 22nd p> A JAMES CLARK for some good food and fellowship, — followed by a panel discussion with your board of directors. Click here for more detailsiww wiincose-ce.ora) @CLEAREDGE Go to wwwsincose- to register Parsons Auditorium, Bldg 1 Johns Hopkins University Applied Physics Laboratory 71100 Johns Hopkins Road Map and Directions INCOSE Chesapeake Chapter 6 Annual Systems Engineering 4,6 Professionals Gala | Wednesday, August 26, 2015 —— reception to honor those who recently received a from INCOSE. Join us at: ae go 11 West Mount Vernon Place; Baltimore, MD 21201 JOHNS HOPKINS ‘Speakers and VIP guests include: Robert Gold, APPLIED PHYSICS LABORATORY Director, Deputy Assistant Secretary of Defense for ~ Systems Engineering DASD(SE); Mike McNamee, Chief Systems Engineer, NSA/CSS; and Courtney Wright, Program Manager, INCOSE Certification Program, ‘esc User ePaiciDocurertsNCOSE.CCNewslatiers!2015%20:%2007%20-%2tNewtia 4 200RAFT 2005 46roxas {2018- 07- Newaleter DRAFT 05m Cost: $45 per person. Pay online with er PayPal: Go to our Registration Page where 3 you can pay on line via credit card. y >>I << Robert A. Gold Daectr, DASDISE) Progra Manage, INCOSE Carifeston Pre Return to top The Definition of a True "Systems Engineering Professional" as Intended for INCOSE’s Multi-Level Certification Program John A. Thomas, ESEP INCOSE Past President ~ 2012 & 2013 ‘Senior Vice President & Chief System Engineer Booz Allen Hamilton (Retired) A Systems Engineering Professional‘, as itis intended for INCOSE’s mult-level certification program, refers to someone who has done more than simply pass a test. Itis someone who is seen by others as an experienced individual who finds a way to get the job done—no matter what obstacles and complications may arise. This is the expectation of someone who has earned an INCOSE certification. And the expectation is not one that can be taken lightly. This reputation for “getting the job done’ is precisoly how the Systems Engineering Professional (SEP) should be perceived by fellow leaders, and staff on a project. The program manager and other members of the leadership team facing a problem don’t have to ask, ‘Where's the systems engineer?" Because the systems engineer—the SEP—has already come to them and said, "Here's the problem, and here's how ''m solving it.” That is the standard the SEP is held to—by INCOSE, by the program leadership team, by all program participants. ‘Systems Engineering Professionals (SEPs) can break down barriers. They have a sense of empowerment—and the good judgement to know exactly where and how far they can push. Members of the leadership team know that a SEP will not be intimidated BMT eEc vencore™ This Newsletter is to serve our ‘mombors and is open to all for contributions. Do you have an interesting idea for an article? A review of a naw book related to engineering? Let us know. We'd love to hear about It. H may wind up in afuture issue of our Newsletter. ‘eC :AsserfPanitvDocamoresINCOSE- CCN enaletere/21S%20 %200T 2D %2INewsleter k20DRAFT%2005 inlros 20:5- O7-Newslotar DRAFT 05m by certain barriers—such as the belief that they are somehow crippled by the contract, by organizational policies, by technology, perhaps even by the leadership team itself. At the same time, the leadership team also knows that the SEP will not push hard in inappropriate places, like a bull in a china shop. A SEP is clear about what it means to be empowered, and how that power should be exercised. ‘Systems Engineering Professionals get the job done because they focus on outcome, not process. The program manager and other members of the leadership team know that when problems arise, SEPs will not retreat into strict compliance with checklists, or see the mere delivery of documents as a measure of success. As SEPs, they know that they can step out of the process role and tackle the larger problem—such as unexpected technology issues, flaws in acquisition strategy, or contradictory policies. Systems Engineering Professionals are collaborative, not competitive, ‘They recognize that program success is relevant to the program manager as well as the systems engineer, and cannot be achieved without an equal contribution from both. Collaboration means working together with others — even stakeholders from firms that normally are Viewed as the competition. The SEP knows how to facilitate the delicate negotiations between program participants that determine the success or failure of a project. Systems Engineering Professionals can solve problems because they understand the nuances and complex interrelationships inherent in a given situation. ‘Some systems engineers tend to see problems through only one lens, such as a technical perspective. Members of the leadership team know that the SEP has the ability to view problems though muttiple lenses simultaneously—to see, for example, how what outwardly looks like a mechanical engineering problem might be related to other issues such as training, policy, doctrine and organizational culture, The SEP also fully considers the perspectives of the program manager and the other members of the leadership team, so that the solution works on all levels. Each of these complexities and nuances must be understood and fully integrated, and the leadership team knows that the SEP can and will take the lead in resolving problems. ‘Systems Engineering Professionals get the job done because they ‘embrace respon: When problems arise, itis often not clear who has the responsibilty to solve them, making it easy to stand aside. Program managers and other members of the leadership team know that the SEP, rather than saying = “it's not my job,” instead will say, “I don’t know whether I'm the one to fix it or not, but 'm going to step in and try." The leadership team is confident that the SEP will say, “It is my responsibility. It is my job.” y. ‘Systems Engineering Professionals solve problems because their skills and knowledge are both deep and broad. ‘Some systems engineers may be reluctant to confront a problem, fearing they will be unable to work with others who have more knowledge and experience in a particular area, But even if SEPs lack certain expertise, they are able to ask the questions that uncover the fundamental nature of the problem. When dealing with others on a project, SEPs can push through technical details, cost and schedule ‘HoC:ASsorePatriek/DoctmertsINCOSE. CCN enslatore/2015%20 %2007%20-%2oNonsleterKIORAFTY:2005 mlsozaaons 12015- 07- Newsleter DRAFT Ohm constraints—even the inevitable office politics—to grasp the larger issues. The leadership team counts on SEPs to have this ability. Although some SEPs may not feel confident that they can meet all of these expectations, they need to know that this is how they are perceived—and they should use every opportunity to fully develop each capability I've shared above. INCOSE strongly believes that certification carries with it an exceptionally high standard of performance. A SEP should be seen as the kind of individual who can be counted on to get the job done, and who will meet whatever challenge comes their way to make the project a success. Program managers and other members of the leadership team—and INCOSE—expect nothing less. John Thomas is the Past President of the International Council on ‘Systems Engineering, an organization for systems engineers and the dissemination of systems engineering practices. He can be reached at president@incose.org. Return to ton Introducing Systems Engineering in the United States Air Force by George Anderson have always felt that some INCOSE descriptions surrounding the origins of systems engineering (SE) were incomplete and there was more to say on the subject. Attributing systems thinking to ancient ‘engineering achievements is fine but the relevant historical record does not, as not as far as | am able to learn, have any mention of a branch of learning, a discipline or a division of engineering effort concemed uniquely with the SE processes as we know them today. As we get into recent history, however, we do find documented evidence of modern SE practices dating back to at least 1948. (One example may be worth discussing to better SATE understand some of the precedents to our. 1 NZ AOA present concepts of SE. This is General Jimmy 1950/0) BG BOB Dooiitie’s remarks in his autobiography entitled, a “| Could Never Be So Lucky Again.[1] General Doolittle was a member of the USAF Scientific Advisory Board (SAB) at its inception in 1948 upon the USAF becoming a separate Military Service. In describing his experiences with the Sy SAB, he dedicates several paragraphs to SE. He Se] 2eains his explanation of the impact of SE in AF Ring eicratt and missile programs by stating “Introducing systems engineering was one of the SAB's more far-reaching and successful recommendations.” (1:475) A brief summary of his explanation is that SE was an important ‘managerial concept that got the process of designing aircraft out of the serial design process of building an airframe, then mating it to an engine and then testing to see how the whole performed. If it performed well ‘ei!C:U secPaticiDocunetsINCOSE. CCA wusaters/2015%20-200T%420-%.2oN ewer ZODRAETS5200 emt 8roxas 2018- OT- Nowsletor DRAFT 05. then the plane went into production without considering the intended payload requirements. The result was an aircraft that often failed to meet performance requirements after being loaded with bombs, bullets and electronic equipment. (1:475) General Doolittle sums up his discussion with words that I think speak tous directly in 2015: “This (pre SE) process was the absolute opposite of systems engineering, which enabled us to start many things at the same time and have them all come to the stage where they could be introduced into the complete vehicle ready to go at Just the right time. Of course, this concept was a tremendous gamble and it took people with courage to pull it off.” (1:475) Here we have the mention of courage in conjunction with the successful outcome of an SE process. I do not recall seeing that personal attribute mentioned so directly in any of my current SE reading. General Doolittle is probably speaking mainly of the managers and not the engineers when he talks about courage, but it clearly seems to be an attribute that applies and perhaps is essential to the practice of SE in general. Itis one thing to receive a set of instructions and proceed to create a product, and quite another to oversee the parallel development of several products that must work together. If the integration has not been done before, there is no “blueprint” and the systems engineer must provide a plan that is as yet untried and must be based on a general as well as specific technical understanding of all the systems involved. | submit that it takes courage to actually perform SE In today’s development or operational environment. We are typically faced with a shortage of adequately trained technical personnel and managers who too often collect deliverables with little concern for actual technical progress. In this setting, courage is a personal attribute that may enable of at least support the ability to manage uncertainty and provide confidence that the right technical courses of action are being identified and followed. | enjoyed reading about many of the other events that General Doolitie described in his autobiography. Taken as a whole, he had many accomplishments that make him stand out as spokesman for technical as well as operational achievement. He received the Congressional Medal of Honor in 1942 for leading the first bombing raid on f ae Tolyoata ime wnen the Figure 1, Lt. Col. Doolitie, Army Air Corps Nation's morale was at its (Second from left) with his B-26 crew just Lies. rior to launching from the aircraft carrier ‘Homet to bomb Tokyo on April 18, 1942. He was a race pilot inthe ‘His crew members are: (I. tor.) Lt. HA. 1930's, received one of the Potter, Navigator; SSgt P.J. Leonard, ‘avIC-UserePatic/DecunertsINCOSE CCI ansats'2015%20-92007%20-%.2cNewslaterX2ODRAFTS:200 5hroxanne 2015- OT- Nowsleter DRAFT OS first doctorates in Engineer/Gunner; Lt. RE. Cole, copilot; aeronautical engineering RA Braemer, Bombardier. from MIT and in WWI rose to the rank of Lt. General as a Bomber Group Commander in the famous 8th Air Force. He also had many technical achievements in aircraft development such as blind flying systems. He has received much recognition for many of these, but | believe his remarks about systems engineering has not received the attention it deserves. [1] | Could Never Be So Lucky Again, Gen. James H. “Jimmy" Doolittle wiih Carroll V. Glines, Bantam Books, New York, 1981 Retum to ton Upcoming Events and Announcements ‘+ July 22, 2015: Dinner Meeting - Panel Discussion with INCOSE-CC Board of Directors + August 19, 2015:Dinner Meeting - Pane! of International ‘Symposium Participants; moderated by Gundars Osvalds + August 26, 2015:Systems Engineering Professionals (SEP) Reception + September 16,2015:Dinner Meeting ~ Human Factors Engineering; by Dr. Amy Bayes and other faculty members from Johns Hopkins University + September 19, 2015: Tutorial - A continuation of Dr. Howard Eisner's "Thinking Outside the Box" + October 21, 2015:Combined PMI-INCOSE Dinner Meeting - Study on Improving Integration of Program Management and Systems Engineering + November 18, 2015:Dinner Meeting - Systems Engineering Standards to include the DoD addendums to ISO 15288 + Interested in Jobs Networking? Contact Mark Kaczmarek at mkaczmarekenar@comcast.net ‘Keep uaiutn he ntact rows and event, Fr aul about Now Sound of Ovals. Exot out oxen romourhionty Onnor yo pevousecures skoge Usama fe Beate of ming NCOSE, Cesk cut Syste Engineong edcclon ne ad sa. ‘Alte ond rare swat ou at i" IE Fererv ements or saoostone abot Ps rewebier pease era ou Scr, Gzore Anders or our emanations Dine Pat lam We vate your foo Board of Director Officers, 2015 Directors at Large Pretaant br George Aneron “cones te Pat Vas ster: ur ec bavi “SPregre: Hr Gen Tewnsen Sober Man Keer Please uso the Forward email link below so we can invite your friends fo join our mailing list. Thanks in advance. INCOSE Chesapeake Chapter © 2015 ‘leiI0:UsereParildDacurertuINCOSE.CCNewleters/2016%20-200T%20-%aoNeusaer KADRAETI52005 emtFrom: INCOSE Chesapeake Chapter To: xenis52 ‘Subject: August 2015 INCOSE Chesapeake Chapter Newsletter Date: Sat, Aug 1, 2015 11:46 pm Email not displaying correctly? View it in your browser Chesapeake Chapt August 2015 E-Newsletter President's Point of View All Glory is Fleeting? Arecord number of Chesapeake Chapter members attended the INTERNATIONAL ‘Symposium (IS) in Seattle (actually Bellevue) Washington on July 13-16, 2018. We accounted for about 30 of the 885 offically registered attendees and may even have achieved the largest chapter turnout of all. Our members purposely dispersed throughout the six simultaneously operating presentation rooms and made hard choices as to which of approximately ‘40 papers and panels that they attended each day. Mr. George Anderson INGOSE GC President Each morning began with a plenary session that included a keynote speaker. Four speakers in all delivered appropriate and relevant presentations. Included were a college president talking about systems engineering as { management too, a software engineer from Sweden urging speed to marke, a water resources engineer from South Africa who clarified the Importance of managing crtical infrastructure and a project manager who bul an astronomical observatory high in the Andes Mountains. Check with an attendee, as they have access to the video on their smartphones, if you want to see what you missed. The plenary sessions also served as the venue forthe annual awards to individuals and chapters. Steve Sutton, ESEP and former INCOSE-CC President received the Outstanding Service ‘Award on Tuesday, July 14, 2018, for making the ew International Web Site 2 reality. He worked for several years on the Communications Committee and richly deserves this recognition, Congratulations, Steve! Erik Devito, Chesapeake Chapter President in 2014, accepted the highly coveted President's ‘Award from INTERNATIONAL President, David Long on Wednesday, July 15, 2015, This award is presented annually to the INCOSE Chapter who scores the highest in the Circle Awards evaluation process. The award was earned for the year 2014 and was accompanied by the Gold Circle Award, that indicates the highest rating short of the President's Award. The purpose of the award Is to Figure 1. Stove Sutton receiving the Outstanding Achievement Award This is the monthly newsletter for INCOSE Chesapeake, a local chapter of INCOSE International. We are a not for-profit organization dedicated to providing a forum for professionals practicing the art and science of Systems Engineering in the Northern & Central Maryland & Southern Pennsylvania area. Join INCOSE Today ‘The Chesapeake Chapter is always looking for volunteers to speak at our upcoming meetings! Please contact our 2015 Programs Director, Glenn “Townson, if you would like therecognize chapters who execute the INCOSE mission with the highest success and is based on strict validation criteria, Figure 2. The President's Award for Chesapeake 2014 If Erk was smiling earlier, 17 of our team were available to celebrate in the Boeing Museum of Flight that evening. After enjoying a meal of steak and prawns, we all, posed to remind everyone at home that we are the World's Best Chapter for a year. Our frst challenge came earlier from Americas Director, Barklay Brown, who opined during the award presentation ceremony that we would not have won if the United Kingdom Chapter had not been disqualified because they had won last year. Barkley either did not know or did not care that the point spread was very close between the two chapters during the judging. That we can match a chapter more than twice our size in the quantity and quality of professional achievements should give everyone further reason to be proud. | know that allthis is exciting but Ihave more: We had at least two papers presented by Chesapeake members. Mark Walker and Gundars Osvalds {gave papers on MBSE and Agile respectively and these were well attended. The extracurricular fun included whale watching, visits to Seattle's Market, scenic tours in the mountains and the incredible Chihuly glass exhibit located beneath the Space Needle, See the obligatory photo c Figure 3. it was difficult, but wo were able to round up 17 of the 31 focal area SE's who were supposed to be at this party. An evening to remember for sure! Please consider attending the IS next year when it will be held in Edinburgh, Scotland. Papers on steam engines willbe especially welcomed and some of our wives are already checking out the tour guides to find the castle where the BBC series, Monarch of the Glen? , was recorded. opportunity to speak or can recommend ‘someone. ‘The Chesapeake Chapter of INCOSE is proud to recognize the following ‘organizations for sponsoring our endeavours to expanding the understanding and appreciation of Systems Engineering in the local area The Institute for SY stems i ee @CLEAREDGE serco Bringing service to life fecal ™% CyberCore TECHNOLOGIES[11'For over a thousand years Roman conquerors returning from the wars enjoyed the hhonor of triumph, a tumultuous parade. In the procession came trumpeters, musicians and strange animals from conquered territories, together with carts laden with treasure and captured armaments. The conquerors rode in a triumphal chariot, the dazed prisoners walking in chains before him. Sometimes his children robed in white stood ‘ith him in the chariot or rode the trace horses. A slave stood behind the conqueror holding a golden crown and whispering in his ear a warning: that all glory is fleeting." - George 8. Patton Jr. (2Intto ww boo. co.ukiscotlanditvimonarchy George Anderson - INCOSE Chesapeake Chapter President Return to top Dinner Meeting on 19 August, 2015 (6:00pm - 8:30pm): 2015 INCOSE International Symposium Review Panel ‘resentation: Lessons | jlearned will be shared irom 2015 INCOSE. [International Symposium presenters cross the globe by a panel of INCOSE-CC [ESEPs. The facilitator ffor this discussion will _jpe Gundars Osvalds (pictured here). There will be 60 minutes of panel presentations and discussions followed by 30 minutes of questions from the floor. Panelists: Gundars Osvalds, ESEP — The Future of DoDAF, What are the DoD and OMG plans? David Fadeley, ESEP — Practit Thinking to Epidemic Response. Jim Armstrong, ESEP — Education and Training, includes subject “Leaming SE by Teaching It David Alldredge, ESEP — SEP Certification using “INCOSE SE Handbook” 'V3.2.2 or V4, “Which version should [ use to take my SEP exam Larry Little, ESEP — Agile SE & SW Methodology, Applying Software Agile Methodology to Systems Engineering, Ellie Gianni, ESEP — The Future of Systems Engineering as presented in “INCOSE SE Vision 2025.” To inspire and guide the direction of SE across diverse stakeholder communities. ners Challenge, “Applying Systems >Ch Event Fl ‘< Go to www. incose-ce.org/revistration/ to register Parsons Auditorium, Bldg 1 Johins Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD e JOHNS HOPKINS vencor) a[S) Map and Directions Return to top 6th Annual Systems Engineering Professionals Gala Wednesday, August 26, 2015 Every year our Chapter puts on a dinner and reception to honor those who recently received a Systems Engineering Professional (SEP) certification from INCOSE. Join us at THE ENGINEERS CLUB AT THE G. [TJACOBS NV 11 West Mount Vernon Place: Baltimore, MD 21201 NSION Speakers and VIP guests include: Robert Gold, Director, Deputy Assistant Secretary of Defense for Systems Engineering DASD(SE): Mike MeNamee, Chief Systems Engineer, NSA/CSS; and Courtney Wright, Program Manager, INCOSE Certification Program Cost: $45 per person. Pay online with PayPal: Go to our Registration Page where you can pay on line via credit card, 22Dow << Retwrn to top Advancing Your System Engineering Career EP 12 & 2013 weer Booz Allen Hamilton John A. Thomas, INCOSE Past President Senior Vice President & Chief System Ei (Retired) Do you feel dissatisfied in your work asa system engineer? You feel your role is relegated to producing documents that nobody reads or cares about And though you may be managing large teams, your work activities aren’t generating a system that meets the strategic objectives of your stakeholders You want your system engineering work to be part of Something larger, but you don’t see hhow that’s possible. The demands and constraints of managers — whether program, acquisition or contract — fee! disempowering to you. So you're demoralized, and see no way out John Thomas The , 4 Institute for Systems * Research @CLEAREDGE (> EUASSEN 7 GROUP serco Bringing service to life ie = CyberCore TECHNOLOGIES 9 JOHNS HOPKINSIt does not have to be this way. These feelings are common to many system engineers. You might even say it’s the curse of a profession that has refined the use of processes to guide and leverage the work of the hundreds and often thousands of individuals needed to build large systems, But it doesn’t have to be this way. The work you do as a system engineer can be meaningful and usefull. You can be a key player in producing the real-world innovations and systems your stakeholders need to support their missions. And instead of feeling relegated to a marginal role, you can use your knowledge and experience to guide the project and the people involved — so the end result is, as much yours as anyone else’s, But you have to reach out for this. It is not going to come to you. You have to be willing to see your role as system engineer in a different light — to actually redefine your perspective of what you are in that role, You have to be willing to accept that the constraints that you believe have been placed upon you — by the program manager. by contracts, by anyone or anything else are not as real as you might think. Ifyou're willing to champion your own vision — and to see yourself operating ceniaS2 ptember 2015 INCOSE-CC Newsletter fed, Sep 9, 2015 11:33 pm Email not displaying correctly? View it in your browser INCOSE Chesapeake Chapter September 2015 > E-Newsletter pat + Forward to Friend President’s Point of View In Vol. 6 Issue 9 “Don’ 5 thing might + President's POV ‘Don’t look back. Something mig| PresidentsPOV | September 16, 2015, be gaining on you.”4 Dinner/Lecture The Board of Directors (BOD) resisted the urge to ‘September 19, 2015 De. rest on the wonderfully successful visit to the Howacd Eisner Tutorial INCOSE International Symposium in July and ‘Your SEP Certification will worked hard in August to organize the 6th Annual expire unless you act, by ‘SEP Reception at the Engineers Club in Baltimore. ‘Gundars Osvalds In spite of other diversions, last minute crises and ‘Upcoming Events a bit of performance anxiety, we chalked up another success for our Chapter’s unique way of, INCOSE 2c Mocijont promoting the INCOSE Systems Engineering spends teenth nemtetne fay Professionals (SEP) certification program. ICS prema eake Slots ciara george, anderson@incose.ora of INCOSE International. We are a not- Each year we have tried to improve the experience | {©r-Proft organization dedicated to and this year was no exception. The biggest change was to invite INCOSE SEPs from | Providing a forum for professionals all of the adjoining states and provide notification and information to them using email practicing the art and science of Given that this was our first invitation to this group, we conducted several email Systeme Engineering Io Ree Nertnein & Central Maryland & Southerncampaigns weekly before the event to make sure that we were reaching our audience. The response was positive with over 35% opening and reading the invitations. (We also conducted an email survey after the event for the attendees so that they could have a chance to complain if they felt that we had tried too hard with our email campaign.) Figure 1. A Speaker's View of the Mansions Ballroom Filled to Capacity The number in attendance was around 95 including the invited speakers and, for the first time, we had additions of three walk-ins plus a gentleman from Boston who stopped by on his return trip from Washington, DC. A tribute to our posters placed in lobbies and cafeterias! ‘We also added a new process to our ESEP recognition ceremony. The ESEPs who were in the audience were asked to come forward and form a receiving line to be the first to welcome the new ESEPs as they received their Chapter Recognition Certificates Pennsylvania area Join INCOSE Today ‘The Chesapeake Chapter is always looking for volunteers to speak at our upcoming meetings! Please contact our Programs Director at programs@incose-ce.org if you would like the opportunity to speak or can recommend someone. ‘The Chesapeake Chapter of INCOSE is proud to recognize the following organizations for sponsoring our endeavours to expanding the understanding and appreciation of ‘Systems Engineering in the local area: ecu The | Institute for ystems S search “A. JAMES CLARK| Figure 2. Chapter ESEPs congratulate their new fellows The after event survey of the attendees gave us good news and some advice. Those ‘who participated in the survey gave the Engineers Club high marks for value and liked the opportunity to hear the speakers and meet with them during the social hour. We also received constructive comments on our failure to individually honor each new Chapter ASEP and CSEP.2 In the past we have listed all new SEPs on Boards as well as slide shows. Perhaps in future events, time can be set aside for more formal recognitions. Other likes from the attendees were the seven Mansion tours and the Chocolate | Mousse Desert which was devoured long before the other selections according to this | year’s architect and planner of the event, Kent de Jong, CSEP, Treasurer. Thanks, Kent for doing all the worrying to make this event successful and we are all sorry that you did not get to the desert before it was all gone. Another important lesson learned was the answer to the last survey question that asked about attending next year. It was almost a unanimous “very likely" Kent and | and the entire BOD wholeheartedly thank those of you who took the survey for this vote of support! While it is satisfying to describe our Gala successes, | must now tum your attention to what | believe are the most important future concerns for the Chapter and its members. These are: The election of BOD officers, ASEP and CSEP certification | renewals, and membership recruiting and retention. @yCLEAREDG (> ELIASSEN 7 GROUP serco Bringing service to life ‘= CyberCore TECHNOLOGIES 9 JOHNS HOPKINS ADPLIED PHYSICS LABORATORYThe BOD nominating committee will soon want to announce the candidates running to fill the position of: ‘= President Elect = Programs Chair ‘| Membership Chair Before they can do this, however, they must have engaged candidates for each position to place on the ballot. Please support the work of the nominations committee and consider running or working with others to insure that our best Chapter talent is asked to run. The election process is one of the areas of our Chapter operation that historically has disappointed me the most. In my 15 years with the Chapter, | have yet to see any evidence of reasonable cooperation from the membership at large or any recognition of the importance of filing the BOD positions with motivated and capable persons. If this continues, we could possibly experience the departure of our qualified BOD members and eventually the Chapter could become a candidate for annexation. Please do your individual best to counter this seasonal complacency among our normally dedicated and supportive membership. ‘An outstanding chapter needs the best leadership and also those aspiring to eam that recognition. Gundars Osvalds, the Membership Director has been struggling with the neglected INCOSE Intemational membership roles and is slowly trying to answer the important questions that we require to properly manage our membership. His duties include identifying and welcoming new members and following up on expirations. Presently, that is not possible due to issues with the membership data repository. Closely associated with this work is the tracking of SEPs whose certifications are expiring. All ASEPs and CSEPs must renew every three years and have accrued a defined level of, development points to qualify for renewal. We currently have a high level of expirations and do not know if the individuals, in general, have been able to eam the necessary Professional Development Units (PDUs) for renewal. For those that need PDUs, volunteering for Chapter leadership is a path to meeting the requirement given there is no limit on the category. Gundars Osvalds will present a more in-depth discussion how to keep your SEP certification by earning PDUs in this newsletter. | cannot close this month without thanking the ESEPs, shown in figure 3, who organized coordinated and presented our first live streaming video program. Led by Gundars Osvalds, they presented a forum on what they had learned at the International Symposium in July. The August 19, 2015 event is viewable through a ‘YouTube link on the Chapter Webpage. «25 PROTEUS Gisner™ JVIAN BITeEc vencore™Figure 3. L to R James Armstrong, David Fadeley, Gundars Osvaids, David Alldredge, and Elie Gianni In closing, | believe that the Chapter will continue to make history and with everyone's assistance can address the areas that need improvement. [1}Satche! Paige (1906-1982); Baseball Hall of Fame Member to make a plea for more volunteers to help with our activities. Actual volunteer work must go into planning organizing, coordinating and executing the SEP Gala. We would greatly appreciate if all Chapter members who attended would recognize this need and consider donating some time to helping us provide more value next year. George Anderson - INCOSE Chesapeake Chapter President Return to top Postscript: A quick sampling of the pictures from the SEP GALA. We will have the rest available for downloading soon. Nea The Institute for Systems ~ Research ‘A. JAMES CLARK CLEAREDGE Ty SOLUTIONS ELIASSEN SEREPFigure 4. Courtney Wright explains that Chesapeake has more SEPS than most countries Figure 5. Craig Tyler receives his ESEP Recognition Certificate from ‘George Anderson and Courtney Wright serco Bringing service to life = CyberCore TECHNOLOGIES 9 JOHNS HOPKINS App LABORATORYFigure 6. Myra Parsons Gross receives her INCOSE Chesapeake Chapter ESEP Recognition Certificate from George Anderson and Courtney Wright Figure 7. Neal Anderson's ESEP Recognition Certificate is received by his wife and daughter (Neil was unavailable due to company business). Presented by George Anderson and Courtney Wright PROTEUS — Orsnart VIAN BWTeEc VeNCORMFall has Arrived! Ellie Gianni, ESEP, President-Elect Labor Day The final days of summer have arrived. Vacations are over. Internships have ended. We find ourselves sending our college students off to resume their studies and are busy with homework, Back-to-School nights, soccer and football games and PTA meetings, ‘As we enter the month of September, we reflect on the meaning of the upcoming Labor Day holiday on Monday, September 7, 2015. Our family is a family of Italian immigrants who were Teamsters and Boilermakers, and have always celebrated the holiday by displaying the American flag and attending parades and picnics during the to the Department of Labor, *Labor Day... is a creation of the labor movement and is dedicated to the social and economic achievements of American workers. It constitutes a yearly national tribute to the contributions workers have made to the strength, prosperity, and well-being of our country.” Labor Day is also about celebrating the sacrifices working people have made to the shared prosperity of this country. It's about valuing people, regardless of where they ‘were born, for their work and the contributions they make to the economic well-being of our great country (Perrone , Lopez). As we approach the Labor Day holiday let us reflect upon the accomplishments, contributions and sacrifices of the great men and ‘women who helped to shape our nation. Patriot's Day On September 11, 2015, Patriot’s Day, we remember those innocent victims and First Responders that sacrificed their lives in the attacks on the World Trade Center on September 11, 2001. Thank you to those of you who continue to serve, protect and defend our nation. We remain vigilant, as the threats to our country continue to evolve. Congratulations to the New SEPs On a brighter note, on August 26, 2015 the INCOSE Chesapeake Chapter hosted the Sixth Annual Systems Engineering Professional Recognition Gala at the Garrett Jacobs Mansion. Approximately one hundred INCOSE members and their guests attended the event at this home of the Engineers Club in Baltimore, Maryland. ‘Three new ESEPS were recognized: Neal Anderson, Northrop Grumman, Myra Parsons Gross, Jovian Concepts, and Craig Tyler, Vencore. The VIP guests who participated in the ceremonies included: Mr. Robert Gold, Director of Engineering The , Vv Stel for Syst ems Research (A. JAMES CLARK @SLEAREDGE serco Bringing service to lifeEnterprise within the Office of the Deputy Assistant Secretary of Defense for Systems Engineering DASD (SE), Ms. Courtney Wright, CSEP, Program Manager, INCOSE Certification Program; and Mr. Mike McNamee, Chief Systems Engineer, NSA. Upcoming Elections Thanks to you - our members, our chapter continues to grow and thrive. The Board of Directors Elections will be held in October. All members in good standing will be sent a ballot via email. Please consider running for INCOSE Chesapeake Chapter offices or volunteering for an associate position on the Board of Directors. This years vacancies are’ President Elect (Term is 3 years) Secretary (Term is 2 years) Programs Director (Term is 2 Years) Membership Director (Term is 2 years) ESEP Summit A quarterly ESEP Summit meeting will take place on Saturday, 26 September 2015 from 0800-1100 in the Barton Conference room located in the Johns Hopkins University Applied Physics Laboratory Building 1 David Fadeley, ESEP, our first ESEP, is presiding. He may be contacted at: dbfadeley@verizon net. INCOSE Chesapeake Chapter Women in Systems Engineering (WISE) WISE is now supporting the Baltimore-Washington Society for Women Engineers (SWE). They will be co-hosting the “Aspire to Lead” Workshop on Saturday, 19 September 2015. To register, please visit he SWE website, httovAwww.baltwashswe.ora/Aspire-to-Lead. ‘See more at: http://w. incose-co.oraiwise-2/#sthash,DY 1bCv4s.dout In closing, | want to stress that we on the BOD want to hear from you. Please feel free to contact any of our Chapter Presidents with your questions: ‘+ President, George Anderson, ESEP, at xenia52@aol,com ‘President Elect, EleanoraAnn “Ellie” Gianni, ESEP, at EleanoraAnn.Gianni@jhuapl edi + Past President, Erik Devito, CSEP, at erik.t.devito@amail.com Happy Fall! Ellie Gianni, ESEP *% CyberCore TECHNOLOGIES 9 JOHNS HOPKINS APPLIED PHYSICS LABORATORY PROTEUS OptsnartReturn to top. Dinner Meeting on 16 September, 2015 (6:00pm - 8:00pm): Techniques for Conducting Effective Concept Design and Design-to-Cost Trade Studies Presentation: Concept design plays a central role in project success as its product effectively locks the majority of system life cycle cost. Such extraordinary leverage presents a business case for conducting concept design in a credible fashion, particularly for first-of-a-kind systems that advance the state of the art. A key challenge is to know when credible design convergence has been achieved. In this session, we will use a space system example to discuss the level of convergence needed for concept design, the importance of design and cost evaluation learning curves in determining credible convergence, techniques that help expedite ae convergence, and practices for conducting David A. Di Pietro, Senior Engineer for Advanced Concepts and Architectures, NASA Goddard Space Flight | Hamilton Center effective concept design-to-cost studies Go to www.incose-cc.org/registration/ to register Institute for ee a Systems Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD © Map and Directions ‘A. JAMES CLARKReturn to top Tutorial on 19 September, 2015 (9:00am - 1:00pm): Four Areas of Special Importance to the Systems Engineer Presentation: Amidst the various aspects of systems engineering dealt with over many years by the presenter, four areas stand out as being of special importance: (1) The Systems Approach, (2) System Architecting and Design, (3) Computing Detection and False Alarm Probabilities, and (4) a “Top Ten” List for ‘Systems Integration. The systems approach is —_ made specific with a discussion of ten Dr. Howard Eisner, Retired subordinate areas. System architecting is Professor Emeritus, The examined in some detail, resulting in a George Washington definitive procedure that explicitly considers an University analysis of alternatives. Detection and false alarm probability calculations are demonstrated, including tradeoffs between the five key variables. Finally, the complex matter of systems integration is explored. Click here for more details:(www.incose-cc.org) Go to www.incose-cc,org/registration/ to register Kossiakoff Center Classrooms Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD 1 Map and Directions Return to top @CLEAREDGE TP SOWTIONS serco Bringing service to life = CyberCore TECHNOLOGIES 9 JOHNS HOPKINS APPLIED PHYSICS LABORATORYYour SEP Certification will expire unless you act Gundars Osvalds, ESEP, Memberships Director ‘The years pass and you forget the details of your SEP certification and your responsibilities to keep it current. Many members have earned the SEP certification in the last three years and now it’s time for you find out what you need to do to keep your certification. This article provides information you can use to make sure you keep your certification current. As a Systems Engineer Professional certified by INCOSE you have a responsibility to yourself to keep your certification current: ASEP — Requires that you eamed 120 Professional Development Units (PDU) every five years and must maintain INCOSE membership and transition to CSEP within 15 years. A INCOSE Membership fee is required each year. CSEP — Requires you earned 120 Professional Development Units (PDU) every three years. Currently no Membership is required. CSEPs obtaining faiScitor ey BMTec VENCOR ycertificate starting in 2016 will be required to keep their INCOSE Membership current by paying a fee. ESEP — Requires you maintain INCOSE membership by paying a yearly INCOSE membership fee, From “SEP Logo Guidance” Every individual who has eared and kept current (as defined above) an INCOSE SEP credential is entitled to use the appropriate designation immediately after their name on correspondence, Emails, business cards, resumes/CVs, papers/articles, presentations, and other similar items 6 has expired, for individual is no lon: authorized to use the designation. You can find out the deadline for your ASEP or CSEP expiration date by teviewing the INCOSE active SEP list on the INCOSE Certification web site click here: Current SEP’s. As a ASEP or ESEP you also need to check that your membership status is active. If you cannot log into the Members section on INCOSE ora/login/ there is information at the login page on how to verify your membership status and account access. INCOSE support can provide information on how to restore your membership by paying dues to INCOSE. ‘The Chesapeake Chapter does receive part of the dues to support the Chapter activities, In reviewing the Current SEP records from the INCOSE site for the Chesapeake chapter the following list of expirations was compiled. EXPIRED in JUL-AUG 2015 — ASEPs -5; CSEP -1; ESEP - 1 Expiring from SEP-DEC 2015 — ASEPs -2; CSEPs -14 Expiring from JAN-DEC 2016 — ASEPs -0; CSEPs -42 Expiring from JAN-DEC 2017 — ASEPs -4; CSEPs -30 Expiring from JAN-DEC 2018 — ASEPs -9; CSEPs -12 Expiring from JAN-DEC 2019 — ASEPs -6 Expiring from JAN-DEC 2020 — ASEPs -1 The Institute for Systems Research A. JAMES CLARK CLEAREDGE @If you are one of the SEPs that are close to the renewal date you need to complete the forms at: Renewal INCOSE SE Certification ‘The ASEP renewal fee is $100 every 5 years. To keep your membership the fee is $38 for Student and $145 for Regular Individual Members. To obtain New or Renew Membership click on: INCOSE Membership Types and then to Join IN E. The CSEP renewal fee is $100 if you are an INCOSE member, $150 if not a current member, ‘The INCOSE Membership fee is $145 year. Individual members qualify for the Senior category if they are at least 64 years of age at the time of their membership renewal and have maintained their individual membership for the five membership years prior to applying for the Senior category, Senior members also receive a 50% discount on their registration and other program fees for the Intemational Symposium, and a reduced registration fee for the Intemational Workshop. Note: Those members who intend to seek Senior member status and take advantage of the discounted fees at the International Symposium must renew their membership prior to registering for the symposium. Senior member status must be confirmed by the Central Office [mail before individuals can register at the discounted rate. ‘The presentation pages 50-51 (shown below) have a list of Professional Development Activities where one can earn Professional Development Units: there are many ways you can eam them but one way that can you can eam PDUs is to: Perform leadership role in professional technical society at local, national or international level for a Credit of 1 PDU/hour of effort, with No Limit You can eam credit for your ASEP and CSEP recertification by earning PDUs when volunteering to help the Chapter Board of Directors with your services. The instructions and forms for renewal are located on Certification Form page serco Bringing service to life = CyberCore TECHNOLOGIES a JOHNS HOPKINS APPLIED PHYSICS LABORATORYunder the Certification section, Please contact any of the Board members to discuss how you can help the Chapter and help yourself with your certification continuation. Return to top Upcoming Events and Announcements ‘September 16, 2015: Dinner Meeting — Techniques for Conducting Effective Concept Design and Design-to-Cost Trade Studies, by David A. Di Pietro September 19, 2015: Tutorial — Four Areas of Special Importance to the Systems Engineer, by Dr. Howard Eisner October 21, 2015: Dinner Meeting — Human Factors Engineering, by Dr. Amy Bayes and other faculty members from Johns Hopkins University ‘+ November 18, 2015: Dinner Meeting — TBD ‘+ December 9, 2015: Holiday Party «= Interested in Jobs Networking? Contact Mark Kaczmarek at mkaczmarekengr@comcast.net This Newsletter is to serve ourmembers and is open to all for contributions. Do you have an Interesting idea for an article? A review of a new book related to engineering? Let us know. We'd love to hear about it. It may wind up in a future issue of our Newsletter. Return to top Keep up with the latest news and events. Find out about our new Board of Directors. Explore our extensive library of previous lectures from our Monthly Dinner Meetings, Lear ofthe Benefits of Joining INCOSE. Cheek out Systems Engineering education in the lncal area. lth and more awaits you at our |NCOSE Chesapeake Chepier Website, For any comments or suggestions about this newsletter please e-mal our Procdont, Georae Anderson or our Communicalons Diecior Pat E items We vate your etc Board of Director Officers, 2015, Directors at Large = President: Mr. George Anderson Communications: Mr. Pat Wikams «= Past President: Mr. Erk DeVito = Programs: Mr, Glenn Townson - President Elect: Mrs. EleanoraAnn “Ele” Gianni - Membership Committee: Gundars Osvalds Treasurer: Mr. Kent DeJong Secretary: Mr. Mark Kacararek: Please use the Forward email link below so we can invite your friends to join our mailing list. Thanks in advance. INCOSE Chesapeake Chapter © 2015 Forward emal af Safeunsubscrib: ‘This emall was sent to xenia52@a0l.com by incose.ccamal.com | sdate Profile/Emal Address | Rapid removal with SafeLnsubscrbe™ | About cur service provider, [INCOSE Chesapeake Chapter | Chesapeake Chapter INCOSE | PO Box 535 | Laurel | MD | 20725-0535October 2015 President’s Point of View New Beginnings — Attend a Board of Directors (BOD) Meeting ‘As announced last month, the election season has begun with the Chapter’s nominating committee presenting a slate of candidates for ‘the 2016 elections. I chaired the nominating committee and was assisted by President ‘Mr.George Elect, Ellie Gianni and Past President, Erik Anderson DeVito. INCOSE CC President ‘The candidates that have agreed to serve george.anderson provided their biographies and position @incose.org statements. These are currently published on our web site and will later be sent to all members of the chapter via email. The election schedule is also posted and states that the ballots will be distributed via email and must be retuned by November 15, 2015. I will announce the results of the election at the Membership Meeting on November 18, 2015. For those that missed the change, we amended the bylaws several years ago to permit email elections in liew of in person voting at ‘membership meetings and mailing paper ballots to each member. This year’s election committee reached out to many candidates including those who expressed interest in serving via the June membership survey. We appreciate everyone's interest and support and on behalf of the nomination committee, thank you for making our task pleasant and rewarding. While the nominating committee worked, the BOD members began to reach out to many chapter members to support a number of committees that are forming to support immediate and ongoing activities. President Elect, Ellie Gianni, will cover all the committees and their goals in another article. Please review this list even if you cannot serve because it shows the multifaceted functions that enable us to perform our mission. Without our infrastructure, we cannot INCOSE Chesa peake Chapter President's POV. ‘Help Wanted Dinter Mestingon2 October, 2015: The Value of Human ‘Systems Engineering in ‘System Development ‘This is the monthly newsletter for INCOSE Chesapeake, a local chapter of INCOSE International. We are a not- for-profit organization forum for professionals practicing the art and science Of Systems Engineering in the Northern & Central Maryland & Southern Pennsylvania ‘The Chesapeake Chapter is always looking for volunteers to speak at our upcoming ‘meetings! Please contact our Programs Director at programs @incose-cc.org if ‘you would like the ‘opportunity to speak or can recommend someone.continue to meet our goals to support you, the membership, and the systems engineering community in Maryland. 1 am_ especially hoping that some of our members with imagination, enthusiasm and organization skills will embrace the Holiday Party Committee this year. The event is always successful but even more so when we are able to host a large turnout. Hopefully, this committee will build on the suecess of previous years, enjoy the challenge and deliver a very special evening to our members and guests. Dr. Howard Eisner conducted a well-attended tutorial on Saturday, September 19, 2015 at the Kossiakoff Center at the Johns Hopkins University Applied Physics Laboratory. The title of his presentation was: Four Areas of Special Importance to the Systems Engineer. Most welcome were his insightful thoughts on the architectural process and more specifically the DoD Architectural Framework (DoDAF). We are most grateful for his support and look forward to having him provide other programs in the future. INCOSE International encourages us to survey our members to insure that we are meeting their expectations. Last month we conducted a survey that asked how the members viewed the Chapter newsletter. There were only five questions but they told a story. In summary the responders said: + Overall satisfaction with the newsletter was high. + The dominant content selected was Chapter activities followed by coverage of member activities. ‘The Chesapeake Chapter of INCOSE is proud to recognize the following organizations for sponsoring our endeavors to expanding the understanding and appreciation of Systems Engineering in the local The Institute for Syst A. JAMES CLARK @CLEAREDGE (> ELIASSEN — GROUP serco Bringing service to life 5 erCore TECHNOLOGIESLetters to the editor received votes but we don’t currently offer this feature! + YouTube video of our presentations scored high. + Subject areas showed a broad range of interests but the two highest were Professional Employmen/Networking and Training. + Finally, members were asked if the newsletter effort should increase, decrease or be kept the same, The dominant response ‘was to keep it the same. A well-populated survey is a great help in allowing the BOD to focus its programs. Please do your part and participate in our surveys so that our conclusions are not biased by small response rates. Before closing this month, 1 want to inform you all of the progress that we have made on executing the Grant Proposal that we submitted in the spring to the INCOSE Foundation. Basically, we received $1000 to _ procure conference style signage to display the — Chapter’s message throughout our professional community. The first articles have arrived and we are working on designs that will describe both the Chapter and WISE activities and _ services. Some signage will be used to support our meetings and functions such as SEP Honor Rolls and the Chapter Banner that is required for all functions. In closing this month, please consider attending a BOD meeting to show your support for our programs and the new committees that mean so much to our success. George Anderson INCOSE Chesapeake Chapter President Return to op Help Wanted T hope everyone is enjoying the cool October weather and getting ready for the Columbus Day and Halloween holidays. Thank you to all of our members who continue to volunteer to make our Chapter the best in the world. We continue to need additional help in many areas. If you are interested in supporting the chapter and earning additional PDUs while doing so to maintain your certifications, then JOHNS HOPKINS fis 9 J@VIANplease contact the Committee Leadership listed in our Committee List and volunteer today. If you have any questions, I am happy to help answer them. Email me at: eleanoraann.gianni@jhuapl.edu, Ellie Gianni - INCOSE Chesapeake Chapter President Elect urn to to Dinner Meeting on 21 October, 2015 (6:00pm - 8:00pm): ‘The Value of Human Systems Engineering in System Development Presentation: This lecture addresses the three major components of asystem: hardware, software, and humans. A total systems approach that considers all three components and the complex interactions among them has been recognized as essential by government and industry organizations responsible for system development and operation, Human systems engineering is a comprehensive program for considering the requirements and constraints of humans as part of an overall system solution, The Johns Hopkins University Engineering for Professionals (EP) Human Systems Engineering concentration trains students in the human systems integration domains and their interdependencies as well as provides additional material related to general human systems engineering. Students gain a deeper understanding of how the appropriate application of human systems engineering adds value to systems. ‘Amy Bayes, Dr. Kathy Straub, Human Systems Engineer Senior Human Factors JHU APL Scientist, JHU APL Click here for more details:(www.incose-ce.org) Go to www.ineose-cc.org/registration/ to register Johns Hopkins University Applied Physics Laboratory 11101 Johns Hopkins Road, Bldg 200, Laurel, MD fap and Directions Return to top Instiitte sinsttutefor Systems * — Research i mescuane @CLEAREDGE me EN — GROUP serco Bringing service to life CyberCore /recixoLocies JOHNS HOPKINS Ti Ristte g lente «JsBOD 2016 Chapter Elections Sor ae PROTEUS ‘This is your opportunity to cast your electronic vote to elect four of Oosnart ‘our chapter members to the Board of Directors. Your vote must be submitted by 15 November 2015. Together with the incumbents currently on the BOD, these four people will form the new board. The choices that they make differentiate our chapter from all of the J others. A list of primary responsibilities can be found in the 20/5 INCOSE Chesapeake Chapter Operating Plan. The candidates are: President Elect ~ Mike Pafford or Write-in Ell T ec Secretary — Craig Tyler or Write-in Boe Programs Director ~ Gundars Osvalds or Write-in Membership Director — Mark Kaczmarek or Write-in ey. vencor™ Bios are available for review on our web site: www.ineose-cc.org The election schedule follows: Ballots Emailed to INCOSE-CC Membership - 20 October 2015 Ballot Submission Deadline - 15 November 2015 (rors ‘New Officers and Directors Announced ~ 18 November 2015 cant New Officers and Directors Sworn-In and Installed ~ 20 January 2016 George Anderson - INCOSE Chesapeake Chapter President Return to top Upcoming Events and Announcements + October 14,2015: INCOSE Chesapeake Chapter Board of Directors Meeting! + October 21, 2015: Dinner Meeting — Human Factors Engineering, by Amy Bayes and Dr. Kathy Straub ~ Building 200 Cafeteria and Auditorium @ + November 11,2015: INCOSE Chesapeake Chapter Board of Jouns Horians Directors Mecting saeco November 18,2018: Dinner Meeting — TBD > December 9, 2018: Holiday Party Garrett Jacobs Mansion - Engineers Club ~ 5:00-7:00 PM Cocktails, 7:00 ~ 9:00 Dinner and eee inet teen * January 13,2016: INCOSE Chesapeake Chapter Board of Directors nstitute for eatin Syst tems + January 20, 2016: INCOSE Chesapeake Chapter Dinner Meeting ?** Research A. JAMES CLARK January 23, 2016: ESEP Summit * SSibor oF ecwntaninc February 10, 2016: INCOSE Chesapeake Chapter Board of Directors Meeting’ © February 17,2016: INCOSE Chesapeake Chapter Dinner Meeting * 1 Johns Hopkins University (JHU) Applied Physics Lab (APL) Building 1 Barton Conference Room 5:30 ~ 8:30 PM (Free)INCOSE Chesa peake Chapter ternational Council ap. Sy: November 2015 Back Issues ‘ it President’s Point of View A President's POV “It was the best of times, it was the Hepat ie ‘worst of times”™ Reese Radical Rie ‘The awning is down and the acoms are falling |] Identification. moving in droves forecasting that we are in for a heavy i semen it winter. The snow blower is prepared for easy de bet Centar deployment with shear pins, staring fluid, ||) 2g20teChatse required operating tools and conditioned fel | Heit ‘Mr. George inventoried and ready for the first ‘Anderson incapacitating snowstorm. | This is the monthly newsletor INCOSE CC for INCOSE Chesapeake, a President Herds of deer visit my neighborhood moving | !0¢e! chapter of INCOSE georgeanderson in groups of 6 or 8 in daytime and cating every Eoerapeea sn oat @incose.org plant and bush in sight. Lyme disease is | (aleaed w providing a common in our neighborhood and. the | forum for professionals predators, the foxes, owls, Z practicing the ant and seience and hawks have generally fof Systems Engincering in the ‘moved out. Squirrels and ig ocean & Cortal Myon feral cats remain behind in pa small numbers being badly mauled by the foxes, over the summer. We the Chesapeaks — = Jain feat the Chesapeake a . Chapter are busy tallying Leer INCOSE op ta pecans ware Today for this year and see both ‘good and bad, opportunity taken and missed, and misfortune vs seemingly undeserved success. All who see these scores in their final | The Chesapeake Chapter is form are usually amazed that so much has been done and how well | ##Ys looking for volunteers to speak at our upcoming. * Tewas the best of times, it was the worst of times, it was the age of wisdom, it was epoch of belie, it was the epoch of incredulity it was the season of Light, it was the season of Darkness, it was the spring of hope, it was the winter of despair, we had everything before us, we bad nothing before us... Charles Dickens, 4 Tale of Two Cities age of foolishness, it was the