www.nps.navy.mil/meyerinstitute Email:MeyerInst@nps.navy.mil Phone:(831) 656-7847 Fax:(831) 656-2336 Naval Postgraduate School, 777 Dyer Rd., Mail Code 97, Monterey, CA; Articles including: Maritime Domain Protection Task Force Hard at Work, Project Brief Summary - MSSE Port Hueneme, and Systems Engineering and Analysis (SEA).

www.nps.navy.mil/meyerinstitute Email:MeyerInst@nps.navy.mil Phone:(831) 656-7847 Fax:(831) 656-2336 Naval Postgraduate School, 777 Dyer Rd., Mail Code 97, Monterey, CA; Articles including: "Opportunistic Arrays" Antennas Designed to Fit the Available Space, Systems Engineering Management - Product Development for the 21st Centry (SEM-PD21) Program Update.

www.nps.navy.mil/meyerinstitute Email:MeyerInst@nps.navy.mil Phone:(831) 656-7847 Fax:(831) 656-2336 Naval Postgraduate School, 777 Dyer Rd., Mail Code 97, Monterey, CA; Articles including: Systems Analysis Certificate Program Takes Off! etc.

www.nps.navy.mil/meyerinstitute Email:MeyerInst@nps.navy.mil Phone:(831) 656-7847 Fax:(831) 656-2336 Naval Postgraduate School, 777 Dyer Rd., Mail Code 97, Monterey, CA; Articles include: Meyer Institute Hosts NPS Maritime Domain Task Force, Certificates in Systems Analysis and Systems Engineering

www.nps.navy.mil/meyerinstitute Email:MeyerInst@nps.navy.mil Phone:(831) 656-7847 Fax:(831) 656-2336 Naval Postgraduate School, 777 Dyer Rd., Mail Code 97, Monterey, CA; Articles include: USAF Center for Systems Engineering and Meyer Institute Research Project Aids Joint Intelligence System Interoperability

www.nps.navy.mil/meyerinstitute Email:MeyerInst@nps.navy.mil Phone:(831) 656-7847 Fax:(831) 656-2336 Naval Postgraduate School, 777 Dyer Rd., Mail Code 97, Monterey, CA; Articles include: Turnover Time, Joint Executive Systems Engineering and Management Program (SEM-PD21), and Integrated Campus Projects and the Meyer Institute.

Attached is a paper as well as a presentation - - Note that this presentation came from this conference: 15th ANNUAL SYSTEMS ENGINEERING CONFERENCE, OCTOBER 22 - 25, 2012, SAN DIEGO, CA More information is here: http://www.dtic.mil/ndia/2012system/; This paper explores the potential benefits and disadvantages associated with providing a course (or part of a course) in complex systems as part of a systems engineering graduate degree program. An overview of systems engineering education programs and a history of SE curricular design provides context for this exploration. Curriculums other than systems engineering that include courses in complexity, nonlinear dynamics, emergence, chaos, decentralized synchronization through stigmergy, scale-free networks and related topics are also examined. The application of these concepts to design problems is assessed, particularly for engineers in the defense domain. Complex systems learning objectives tailored for systems engineers are proposed. Finally, a framework on which to base a trade-off analysis to determine if such topics should be included in an existing or developing graduate degree program is recommended.

Naval Postgraduate School Graduate School of Engineering & Applied Sciences, Total Ownership Cost Modeling presented by Raymond J. Madachy, Associate Professor of Systems Engineering at the Naval Postgraduate School.; Total Ownership Cost (TOC) is the sum cost of system acquisition, development, and operations including direct and indirect costs. In the DoD, cost modeling is needed to enable tradespace analysis of affordability with other system ilities. Parametric cost models will be overviewed that enable affordability tradeoffs with integrated costing of systems, software, hardware and human factors across full lifecycle operations. Examples will be shown for software-intensive systems. Research and development of Product Line TOC modeling to support investment decisions will also be covered.

Naval Postgraduate School, Graduate School of Engineering and Applied Sciences, Defining a System of Systems Engineering & Integration Approach from a Lifecycle Perspective, December 18, 2014. Presented by Warren K. Vaneman, Ph.D.

Systems engineering processes using pull scheduling methods (kanban) are being evaluated with hybrid modeling and simulation. We are assessing integrated systems and software engineering at the enterprise level, where rapid response software development projects incrementally evolve capabilities of existing systems and/or systems of systems. A kanban-based scheduling system was defined and implemented with connected discrete, continuous and agent-based models. We are simulating the process performance vs. traditional methods of sharing systems engineering services across projects, and whether the overall value of the systems of systems over time is increased.; This material is based upon work supported, in whole or in part, by the U.S. Department of Defense through the Systems Engineering Research Center (SERC) under Contract H98230-08-D-0171. SERC is a federally funded University Affiliated Research Center managed by Stevens Institute of Technology.

Proceedings of the 3rd Asia-Pacific Conference on Systems Engineering (APCOSE), Singapore, 2009; This paper documents (1) the early phases of using systems engineering to develop a conceptual system – the system being developed is a systems engineering body of knowledge (SEBoK) and (2) the findings and opportunities generated in those early phases. The approach was based on identifying activities specific to systems engineering, as opposed to the broad raft of activities that systems engineers might undertake, according to their role. An activity-based definition of systems engineering vs. non-systems engineering role-based definition was developed. The second part of the paper identifies five types of systems engineers, discusses the evolution of systems engineering in terms of those five types, and hypothesizes that a major cause of the failure of systems engineering is the allocation of inappropriate types of systems engineers to early lifecycle phase systems engineering activities. The paper concludes with some insights and recommendations for further study.

Version 1.0; This guide has been prepared for Systems Engineering (SE) students to assist them in completing the Master’s thesis. The guide focuses on the preparation, the proposal and the research element of the project, describes the roles and responsibilities for those involved in the project, and provides an outline for the major sections of a thesis.

Version 1.1; This guide is intended to provide the basis for learning to communicate effectively in writing. The guide is useful not just for your engineering project reports or thesis but for all the writing you will do as an engineering graduate student.

Approved for public release; distribution is unlimited; This study uses core elements of the system-of-systems (SoS) engineering process to obtain lessons learned, which are then used to recommend process and organizational changes to facilitate an SoS approach to current and future U.S. Army acquisitions. The study finds that an SoS approach is necessary to accommodate the capability-based process that drives the Army acquisition system. Recommendations include incorporating SoS engineers in the Joint Capabilities Integration Development System process to build and standardize SoS architectures; using a chief integration officer throughout the SoS life cycle to provide expertise on integration and interoperability; and establishing guidelines for integrated product teams and lead system integrators. The SoS acquisition approach will also benefit from capability portfolio managers using consolidated funding as opposed to the current stove-piped funding. The SoS wave model can be incorporated in the operation and support phase to support iterative SoS evolution. The Army acknowledges that many current systems are, or have the potential to be, part of an SoS environment; however, the current acquisition processes and organizational structure are based on stand-alone system acquisitions. The recommendations of this study describe how the Army can support SoS acquisition.; ; Major...

Approved for public release; distribution is unlimited; According to a 2010 Government Accountability Office (GAO) report, major system acquisitions within the Department of Defense (DOD) tend to be behind schedule, over budget, and often fail to deliver at least some of the planned capabilities. One area that can significantly contribute to successful implementation of systems engineering is the regular usage of management software tools and their continued evolution to better meet systems engineering needs. This thesis provides a detailed exploration of four categories of available system engineering management tools: Model-Based Systems Engineering (MBSE), Product Life Cycle Management (PLM), Systems Engineering Environment (SEE), and Project Management software. Each tool has numerous features that support successful systems engineering. However, there does not seem to be a consolidated commercially available tool or system that allows for seamless management of systems engineering projects across all of the process areas. Drawing upon these existing tools and the International Council on Systems Engineering (INCOSE) processes, this thesis derives a set of requirements for such a consolidated systems engineering management tool. This research can serve as the starting point for a follow-on effort to develop such a tool.; ; Space and Naval Warfare Systems Center Pacific

Approved for public release; distribution is unlimited; The Naval Postgraduate School's first CubeSat, the NPS Solar Cell Array Tester (NPS-SCAT), demonstrates the capability of the CubeSat form factor as a technology test bed by implementing a single experiment--a solar cell tester. The need to validate solar cell performance on orbit, in the harsh space environment, is recurring with the continued development of advanced, untested solar cells. By using a relatively inexpensive platform, the CubeSat, such solar cells can be tested and the risk for larger satellites mitigated with this experiment. This thesis discusses the design and construction process of the solar cell array tester payload along with its integration with the remaining satellite subsystems (command and data handling subsystem, communications subsystem, and electrical power subsystem) including the problems encountered along the way and the chosen solutions. In addition, the systems engineering and testing procedures developed for and conducted on the satellite engineering design unit will be described in detail.; US Navy (USN) author

Presentation made by Dr. Warren K. Vaneman, Naval Postgraduate School & Richard Budka, Customer Inspired Solutions, LLC. Provided to: NDIA 15th Annual Systems Engineering Conference Net Centric Operations / Interoperability Track & System of Systems Track.

This research addresses interagency coordination from an architectural perspective utilizing a systems engineering process. Interagency coordination is not fully understood and has proven difficult for various U.S. government agencies to replicate. Two examples of successful interagency coordination are used in this analysis: the Joint Interagancy Task Force-South (JIATF-South) and Special Operations Forces (SOF) high-value target teams. These organizations are decomposed into their top-level functions and organized by their major physical components. These results are applied in the creation of a notional top-level functional and physical architecture for the U.S. European Command's new Joint Interagency Counter-Trafficking Center (JICTC).

Approved for public release, distribution unlimited; This thesis presents a new systems engineering based approach to naval ship concept design for the Republic of Korea (R.O.K.) Navy. The R.O.K. Navy currently uses a traditional naval architecture approach in concept design. Naval architects focus only on naval architecture issues such as speed, range, and displacement; combat systems engineers focus on the performance of combat systems, weapons, and sensors. This design process creates some integration problems in the late design stage and during construction. For this reason, there is a growing interest in the systems engineering approach design concept in the R.O.K. Navy. Naval ship design is an aggregate of engineering, computer science, management, and even strategy and policy. Naval ship engineers should consider not only naval architecture issues such as hull form, stability, structure, maneuverability and propulsion, but also mission needs, effectiveness, cost/risk benefits, and integration with all combat systems. Naval architecture and combat systems engineering are a part of the design process, and they must be considered simultaneously a systems engineering approach to combatant ship design. To properly design a naval ship...

Approved for public release; distribution is unlimited; The purpose of this thesis is to study the manning and maintainability requirements of a submarine unmanned undersea vehicle (UUV) program. This case study reviews current commercial and military applications of UUVs and applies their principles to the missions of the Navy's submarine force. Past and current UUV efforts are lacking requirements documents and the formal systems engineering process necessary to produce a successful program of record. Therefore, they are not being funded for use by the war-fighter. The Navy must develop formal concepts of operations (CONOPS) for the missions and systems that it wants to produce and allow industry to begin development for a formal future UUV program. Furthermore, the military has developed countless unmanned systems that have been developed for use in the water, on the ground and in the air, from which the Navy can apply important lessons learned. Lastly, analysis suggests that the Navy should continue to support the use of a submarine detachment for operation and maintainability of future vehicle programs.; US Navy (USN) author