search.noResults

search.searching

dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
ARCHITECTURE FOR ARMY MODERNIZATION


FIGURE 1 Operational views


Multidomain operations doctrine


Mission threads System-of-systems architecture


AFC cross- functional teams


Informed by cross- functional teams & PEO efforts


ASA(ALT) program executive


offices (PEOs)


Concept of operations Directed requirements Initial capability documents Joint urgent operational needs statement Operational needs statement Requirements development packages Technical data packages Threat assessment Program manager systems engineering products Project schedules Reports


Technical standards


Integrated master schedule


ARCHITECTURE METHODOLOGY


A modernized approach to Army architecture begins with system requirements from the cross- functional teams. Then, cross-portfolio and enterprise requirements are identified by stakeholders in ASA(ALT) and the Army Futures Command. The final architecture must include data storage that is accessible across the enterprise. (SOURCE: ASA(ALT) Office of the Chief Systems Engineer)


of alternate solutions. Te availability of an architecture model would accelerate expected system performance analyses, increas- ing the chances that they would be completed in time to inform acquisition decisions, often not the case in acquisition today.


With a single, authoritative architecture model, analysis can be better managed to support acquisition decision-making. Model fidelity and scenario development will take precedence over data gathering and corroboration. With a clearer under- standing of the architecture, decision-makers will be better able to direct analysis efforts to be more refined and better answer difficult questions before making a potentially irre- versible acquisition decision. Analysts will be able to use the architecture to further improve model and scenario fidelity as they can quickly and efficiently communicate in a common language with both operational requirements owners and mate- riel developers. With clear, relevant, high-fidelity model data


132 Army AL&T Magazine Summer 2019


in hand, decision-makers will have the justification to defend their acquisition decisions.


ARCHITECTURE IN A DIGITAL WORLD For an architecture to be successful in a highly connected, digital enterprise, it must include all stakeholders, be readily acces- sible and be easy to navigate from concept to deployment. A digital architecture model has the additional role of being the authoritative repository for all data pertaining to solutions under development and their integration with other systems. Tis repos- itory becomes the single launch point for analyses performed on the system, providing a consistent data source for modeling and simulation tools to link directly into.


In this way, the repository serves as a mechanism to manage configuration of the current state of the enterprise and an enabler for analyses of future designs. Reusing system data stored in an


Analysis (research papers, modeling and simulation) Gaps


System-of-systems use cases


Challenges Opportunities


Architecture Development Process


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