COMMENTARY
authoritative digital repository establishes a common baseline for various solutions under development. Mapping solutions to the common baseline provides the justification for analyses of expected performance of alternative solutions. Analysts will be able to clearly point to how their work supports the acquisition decision-making process. In the same way, the common baseline simplifies future integration of additional components as technol- ogies mature. Common baselines enable “plug and play” solutions to be developed, instead of designing a system from the bottom up whenever a new function needs to be added.
Using data from the architecture model, context- and decision- specific views, outside of the standard set of DOD Architecture Framework views, could be customized for specific discussions and decisions. Creating unique views from the same underly- ing data ensures consistency across the enterprise. Trough this data repository, enterprise knowledge can captured efficiently and made available for reuse. Reuse may include new collabora- tive communications between portfolios, or new and innovative analyses.
HORIZONTAL INTEGRATION STUDY As a recent example, the Army Futures Command implemented a horizontal integration “tiger team” to document first-order expected interdependencies—systems or functions that rely on other systems to work properly—between the cross-functional teams’ systems. Te team developed an architecture methodology to capture these interdependencies from both an operational and system perspective. Recognized interdependencies for this effort included communications; networking position, navigation and timing; synthetic training; power distribution and generation; sustainment; interoperability; autonomy; and commonality of sensors and subsystems.
Te team used the architecture methodology developed during the study to inform subsequent analyses, modeling and simu- lation, course-of-action development and near-term resourcing decisions for senior acquisition leaders. Tis architecture meth- odology was recognized by Army Futures Command leadership as valuable—so much so that it was approved for inclusion in their Future Force Modernization Enterprise requirements docu- mentation.
CONCLUSION In a January 2018 interview with Defense News, Army Secre- tary Dr. Mark T. Esper summed up the role of architecture by noting that “the key, or part of the key going forward, has to be to understand the architecture and to map it out so we have
the plan. … It’s like building a house—you have to have a blue- print. Having a blueprint doesn’t necessarily mean deciding who will supply the fixtures or materials or what will be used, but it defines what is needed.”
Architecture supports the identification and documentation of system interdependencies with technical rigor; frames and quantifies opportunities for resolution; and enables informed decision-making. As a living product, architecture supports timely requirements development and updates in the face of new systems and emerging threats. Architecture ensures the end- to-end traceability of requirements to solution as a system goes through concept, requirement generation and deployment. Te architecture confirms that a Soldier’s equipment aligns to an initial need for that equipment. Finally, architectures support comprehensive analyses to refine operational concepts and system solutions, and can serve as blueprints for force modernization.
For more information, contact Fred Buchanan in ASA(ALT)’s Office of the Chief Systems Engineer at
fred.b.buchanan.civ@
mail.mil.
NICKEE ABBOTT is director of the Architecture and Analysis Directorate in the ASA(ALT) Office of the Chief Systems Engineer. She holds an M.S. in strategic planning from the U.S. Army War College, an M.S. in electrical engineering from the New Jersey Insti- tute of Technology and a B.S. in electrical engineering from Drexel University. Her organization focuses on modernizing Army materiel systems to deliver engineered, integrated and validated solutions for the Soldier at all echelons. She leads the organization in production of a synchronized ASA(ALT)-integrated master schedule, capability set architectures and Army network analyses that follow a disciplined system-of-systems engineering process. As a key figure in the coordi- nation and collaboration with stakeholders, she works to ensure that the Army’s modernization initiative is engineered and validated to meet the needs of the Soldier. She is Level III certified in program management and in engineering.
RICHARD HABERLIN, Ph.D., Cmdr., U.S. Navy (Ret.), is senior technical adviser in the Modeling, Simulation, Experimentation and Analysis Division at MITRE Corp. He leverages 20 years of Navy operational and staff experience to produce tailored, relevant and defensible analyses informing executive-level decisions across DOD and the broader government. He earned his doctorate in systems engineering and operations research at George Mason University, and holds an M.S. in operations research from the Naval Postgrad- uate School and a B.S. in ocean engineering from the United States Naval Academy.
https://asc.ar my.mil 133
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72 |
Page 73 |
Page 74 |
Page 75 |
Page 76 |
Page 77 |
Page 78 |
Page 79 |
Page 80 |
Page 81 |
Page 82 |
Page 83 |
Page 84 |
Page 85 |
Page 86 |
Page 87 |
Page 88 |
Page 89 |
Page 90 |
Page 91 |
Page 92 |
Page 93 |
Page 94 |
Page 95 |
Page 96 |
Page 97 |
Page 98 |
Page 99 |
Page 100 |
Page 101 |
Page 102 |
Page 103 |
Page 104 |
Page 105 |
Page 106 |
Page 107 |
Page 108 |
Page 109 |
Page 110 |
Page 111 |
Page 112 |
Page 113 |
Page 114 |
Page 115 |
Page 116 |
Page 117 |
Page 118 |
Page 119 |
Page 120 |
Page 121 |
Page 122 |
Page 123 |
Page 124 |
Page 125 |
Page 126 |
Page 127 |
Page 128 |
Page 129 |
Page 130 |
Page 131 |
Page 132 |
Page 133 |
Page 134 |
Page 135 |
Page 136 |
Page 137 |
Page 138 |
Page 139 |
Page 140 |
Page 141 |
Page 142 |
Page 143 |
Page 144 |
Page 145 |
Page 146 |
Page 147 |
Page 148 |
Page 149 |
Page 150 |
Page 151 |
Page 152 |
Page 153 |
Page 154 |
Page 155 |
Page 156
