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
REUSABLE AND REFRESH-ABLE


for sharing available information in GCIA, give the vehicle crew increased situational awareness while reducing redundant hard- ware solutions.


Delivering reliable and alternative mech- anisms for resources to operate and communicate effectively with each other in GCIA provides for a robust solu- tion that enables the vehicle systems to continue to operate properly during soft- ware failures.


systems, such as fire control or remote weapon systems, on GCIA.


CONCLUSION Future efforts will evolve GCIA incre- mentally to allow multiple open-systems frameworks, such as the Future Airborne Capability Environment, modular open radio frequency architecture, sensor open systems architecture and open mission systems to work together without any disruptions to the operation of the vehi- cles. Planned enhancements in the next


GCSCIS/PEO+GCS+Common+Infrast ructure+Architecture+Home.


The nature of warfare is changing, and combat vehicles must support new technologies quickly, with the promise that they’ll perform reliably and interoperate with related warfighter capabilities.


INTEGRATING CAPABILITIES The GCIA platform provides all the required computing and display resources, network, infrastructure-related common capability services software, commonly used shared data services software, a library for assisting the development of VICTORY-compliant interfaces and an infrastructure for managing the network using open-standard specif ications. Capability developers have to develop the drivers, devices and their system-specific software to interface with GCIA. Te platform allows any VICTORY-compli- ant systems, such as digital radios, to interoperate with other VICTORY systems, such as computing resources, electronic warfare sensors or Ethernet switches, and non-VICTORY-compliant


68 Army AL&T Magazine


12 to 16 months will improve GCIA’s technical maturity in the areas of security, performance and software configuration.


Te opportunities for reuse of this prod- uct go well beyond PEO GCS platforms or programs; it could also be used in High Mobility Multipurpose Wheeled or Mine Resistant Ambush Protected vehicles. With GCIA aboard vehicles on the battlefield, Soldiers will not only have multiple capabilities at their finger- tips, but also a distinct advantage over the adversary.


For more information, email macam.s.dattathreya.civ@mail.mil or visit the website (registration is required): https://conf luence.di2e.net/display/


DR. MACAM S. DATTATHREYA is the chief architect and a scientist for PEO GCS and the U.S. Army Tank Automotive Research, Development and Engineering Center. He holds a Ph.D. in electrical and computer engineering from Wayne State University. He has 24 years of experience in multiple engineering fields in both the commercial and government sectors. He is a senior member of the Institute of Electri- cal and Electronics Engineers and is Level III certified in systems engineering. He has published several technical research papers in journals and holds nine U.S. patents.


MAJ. GEN. BRIAN P. CUMMINGS is the program executive officer for GCS and responsible for the life cycle management of the U.S. Army’s main battle tank, Brad- ley fighting vehicles, self-propelled howitzers, the Stryker family of vehicles, combat vehicle recovery systems, the Armored Multi-Purpose Vehicle and the Mobile Protected Firepower Program. He was previously the program executive officer for Soldier programs at Fort Belvoir, Virginia. He holds an M.S. in science and technology commercialization from the University of Texas, an M.S. from the Indus- trial College of the Armed Forces of National Defense University and a B.S. in biology from Old Dominion University.


MR. FASI SHARAFI is the assistant program executive officer for Systems Engineering and Integration within PEO GCS. He has more than 29 years of Army acquisition experi- ence across multiple system-level efforts that includes serving in the position of chief engi- neer for 10 years. He holds a B.S. and an M.S. in electrical engineering from Rutgers Univer- sity and New York University, respectively. He is Level III certified in systems engineering and a graduate of Defense Systems Manage- ment College.


October-December 2018


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