FIELDING THE FUTURE
of a system have a larger effect on surviv- ability in combat, perhaps? Currently, experts provide input on the importance of things such as speed and weight to the utility of a system. In the near future, we will use expert opinion less and the results from combat models more.
Rather than looking at what improve- ments to a particular system to buy, it is now possible to use OneSAF to consider whether improvements in one functional area, such as detection, provide more benefit than improvements in another functional area, such as protection. For instance, is it preferable to have CBRN suits with better thermal comfort or to have a detector with faster response time?
The NBCRV wi ll be the first JPEO-CBRND system to use OneSAF to examine these types of cross-commodity trades.
FUTURE WORK With the success achieved so far with the creation of the analytical framework, JPEO-CBRND is taking additional steps to fully embrace the shift toward a digi- tal engineering environment through improved data management tech- niques and more reliance on models and simulation.
Previously, CBRN data lived in dispa- rate, isolated sources that were not readily available to those who may have needed
In the near future, we will use expert opinion less and the results from combat models more.
it. Tis led to duplication of effort to produce needed data or use of data that was not necessarily the latest and best to support decision-making. To correct this, JPEO-CBRND has initiated an effort to create a centralized CBRN data reposi- tory to ensure everyone has access to the same validated data sets and to make sure knowledge is preserved.
Te repository will hold all data pertain- ing to CBRN capabilities, including programmatic data such as cost, sched- ule and performance as well as modeling and simulation inputs and outputs, test data and any other data generated over the course of a program’s life cycle. Sources for the data will be listed, as well as a point of contact who can be reached for more information. Tat point of contact will have the responsibility for making sure the data is up to date. Storing data in a centralized repository will allow it to be updated one time and then made available to all, reducing errors and ensuring that the same, consistent data is being used at all times. As we adopt more digital engi- neering principles, we hope to develop the digital thread that will connect all phases of the program’s life cycle, so that when data is updated, it will automatically disseminate out to each place it is being used, such as component-level models, engineering drawings, inputs for combat models and test plans. As a simple exam- ple, if the name of a system component were to change, the ideal process would be that the point of contact for that compo- nent would log into the centralized data repository and update the name, which would then be automatically updated everywhere else that the component name is used.
JPEO-CBRND is also embracing the use of models and simulations at each stage of the program life cycle, from item-level engineering models that inform system
designs,
to trade-space models
that
examine ways to reduce cost and improve performance, to combat simulations that demonstrate the mission impact of new capabilities.
CONCLUSION Te JPEO-CBRND end goal is to put into place the architecture and necessary processes to create a digital environment that will remove the manual processes in existence today in favor of automated ones, creating a continuum across all phases of a program’s life cycle, from concept to disposal. Tis will help create a more efficient acquisition process by reduc- ing manual work, ensuring an audit trail throughout a program’s life cycle and creating a shared understanding among all program stakeholders of the issues impact- ing their programs.
For more information, contact Lori Remeto, director of analytical framework for JPEO- CBRND, at
lori.c.remeto.civ@
mail.mil.
GAIL CAYCE-ADAMS is an operations research analyst and serves as the lead for combat analytics for the JPEO-CBRND analytical
framework team. She holds
an M.S. in systems management and operations research from the Florida Institute of Technology and a B.S. in computer science
from the University of
Maryland, Baltimore County. She is Level III certified in engineering and Level I certified in program management.
KEVIN JOUBERT has worked in every part of the acquisition life cycle during his 20 years of government experience in the chemical and biological protection area. He is a Level III certified engineer, with a B.S. in chemical engineering from McNeese State University and a B.S. in biology from the University of Louisiana at Lafayette.
https://asc.ar my.mil
47
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 |
Page 157 |
Page 158 |
Page 159 |
Page 160 |
Page 161 |
Page 162 |
Page 163 |
Page 164 |
Page 165 |
Page 166 |
Page 167 |
Page 168 |
Page 169 |
Page 170 |
Page 171 |
Page 172
