Recommendations for Managing Frequently Changing DFIDUIs

1
Recommendations for Managing Frequently Changing
DFI/DUIs

• David Couturier
• April 6, 2005

2
Problem

• Some DFI/DUI Types Change Frequently
• Supplies
• Munitions
• Symbology
• This Causes Problems for Systems needing to
  Maintain Interoperability

3
MINIMP Requirement on Data Items

• VMF 6017 - Paragraph 5.4.7.c
• When a system implements either a mandatory
  or an optional DUI, it shall implement all data
  items for that DUI.
• This is an onerous requirement for two reasons
• The cost to implement data items your system
  wont use
• Changes in data items frequently are identified
  well into the development phase of the Block,
  imposing schedule and cost issues

4
Considerations Regarding Mandatory Use of All
Data Items

• Original Intent was to ensure that a system would
  be able to recognize any data item which might be
  sent to them
• Many systems are not implementing this way
• Cost to implement all data items can be
  substantial, with no added benefit

5
Recommendation on Mandatory Use of All Data Items

• Revise wording in paragraph 5.4.7.c to
• When a system implements either a mandatory or
  an optional DUI, it shall be able to receive all
  data items for that DUI, however, it may group
  some, but not all, of the data items into generic
  groups having the same bit code.

6
Approaches to Late DI Changes

• Prohibit Them
• Not Realistic If theyre needed, they are
  needed
• Provide Blocks of Reserved Data Items to
  specific Organizations
• Better solution, but still needs to have
  guidelines to ensure Reserved Data Items Get Into
  Next Version of Standard
• Essential Changes may still need to be made, but
  Developers should make every effort to identify
  new data items without having to resort to
  Essential Change.

7
Reserved Blocks of Data Items

• In SWB, tens of systems are now being required to
  maintain interoperability
• Blocks of Data Items Could be Allocated to
• Systems
• PEOs
• Software Blocking
• Army CCB
• Joint CCB
• Other?

8
Recommendations on Frequently-Changing Data Items

• Have Systems Identify Candidate
  Frequently-Changing DIs
• Have Army CCB Approve List
• Army CCB Allocate Some Data Items as Reserved
• System needing to Use Reserved Data Item submits
  an ICP which ONLY addresses the needed Data
  Items no other changes on a Reserved Data Item
  ICP
• Software Blocking Notify Systems of the New
  Process for Frequently-Changing Data Items
• ACCB Monitor this process to ensure it is not
  used to get around the standard process
• ACCB Approach JCCB for adopting the Process