AllPduAssessmentTemplate.md



IEEE Distributed Interactive Simulation (DIS) version 7 PDU Assessment


PDU type and PDUs
ID
    Assess

IEEE Standard 1278.1-2012


EntityInformationInteractionFamilyPduType
1


Javadoc  Schemadoc

Section 5.3.3. Common superclass for EntityState, Collision, collision-elastic, and entity state update PDUs.


1. EntityStatePdu
1
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

7.2.2. Represents the position and state of one entity in the world. See 5.3.2. (length of list found in field numberOfVariableParameters)


2. CollisionPdu
4
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

7.2.3 Collisions between entities shall be communicated by issuing a Collision PDU. See 5.3.3.


3. CollisionElasticPdu
66
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

7.2.4 Information about elastic collisions in a DIS exercise shall be communicated using a Collision-Elastic PDU. See 5.3.4.


4. EntityStateUpdatePdu
67
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

7.2.5. Nonstatic information about a particular entity may be communicated by issuing an Entity State Update PDU. 5.3.5. (length of list found in field numberOfVariableParameters)


5. AttributePdu
72
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

7.2.6. Information about individual attributes for a particular entity, other object, or event may be communicated using an Attribute PDU. The Attribute PDU shall not be used to exchange data available in any other PDU except where explicitly mentioned in the PDU issuance instructions within this standard. See 5.3.6. (length of list found in field numberAttributeRecordSet)


PDU type and PDUs
ID
    Assess

IEEE Standard 1278.1-2012


WarfareFamilyPduType
2


Javadoc  Schemadoc

Abstract superclass for fire and detonation pdus that have shared information. Section 7.3


1. FirePdu
2
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

7.3.2 Used to communicate the firing of a weapon or expendable.


2. DetonationPdu
3
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

7.3.3 Used to communicate the detonation or impact of munitions, as well as non-munition explosions, the burst or initial bloom of chaff, and the ignition of a flare. (length of list found in field numberOfVariableParameters)


3. DirectedEnergyFirePdu
68
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

7.3.4 Used to communicate the firing of a directed energy weapon. (length of list found in field numberOfDERecords)


4. EntityDamageStatusPdu
69
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

7.3.5 Used to communicate detailed damage information sustained by an entity regardless of the source of the damage. (length of list found in field numberOfDamageDescription)


PDU type and PDUs
ID
    Assess

IEEE Standard 1278.1-2012


LogisticsFamilyPduType
3


Javadoc  Schemadoc

Abstract superclass for logistics PDUs. Section 7.4


1. ServiceRequestPdu
5
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.5.5 Communicate information associated with one entity requesting a service from another. (length of list found in field numberOfSupplyTypes)


2. ResupplyOfferPdu
6
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.5.6 Communicate the offer of supplies by a supplying entity to a receiving entity. (length of list found in field numberOfSupplyTypes)


3. ResupplyReceivedPdu
7
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.5.7 Used to acknowledge the receipt of supplies by the receiving entity. (length of list found in field numberOfSupplyTypes)


4. ResupplyCancelPdu
8
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.5.8 Used to communicate the canceling of a resupply service provided through logistics support.


5. RepairCompletePdu
9
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.5.10 Used by the repairing entity to communicate the repair that has been performed for the entity that requested repair service.


6. RepairResponsePdu
10
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.5.11 used by the receiving entity to acknowledge the receipt of a Repair Complete PDU


PDU type and PDUs
ID
    Assess

IEEE Standard 1278.1-2012


RadioCommunicationsFamilyPduType
4


Javadoc  Schemadoc

Abstract superclass for radio communications PDUs. Section 7.7


1. TransmitterPdu
25
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.8.3 Communicates the state of a particular radio transmitter or simple intercom. (length of list found in field modulationParameterCount antennaPatternCount)


2. SignalPdu
26
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.8.4 Conveys the audio or digital data carried by the simulated radio or intercom transmission.


3. ReceiverPdu
27
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.8.5 Communicates the state of a particular radio receiver. Its primary application is in communicating state information to radio network monitors, data loggers, and similar applications for use in debugging, supervision, and after-action review.


4. IntercomSignalPdu
31
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.8.6 Conveys the audio or digital data that is used to communicate between simulated intercom devices (length of list found in field dataLength)


5. IntercomControlPdu
32
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.8.7 Communicates the state of a particular intercom device, request an action of another intercom device, or respond to an action request. (length of list found in field intercomParametersLength)


PDU type and PDUs
ID
    Assess

IEEE Standard 1278.1-2012


SimulationManagementFamilyPduType
5


Javadoc  Schemadoc

First part of a simulation management (SIMAN) PDU and SIMAN-Reliability (SIMAN-R) PDU. Sectionn 6.2.81


1. CreateEntityPdu
11
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

Section 7.5.2. Create a new entity. See 5.6.5.2.


2. RemoveEntityPdu
12
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

Section 7.5.3 The removal of an entity from an exercise shall be communicated with a Remove Entity PDU. See 5.6.5.3.


3. StartResumePdu
13
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

Section 7.5.4. Start or resume an entity or exercise. See 5.6.5.4.


4. StopFreezePdu
14
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

Section 7.5.5. Stop or freeze an enity or exercise. See 5.6.5.5


5. AcknowledgePdu
15
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

7.5.6 Acknowledges the receipt of a Start/Resume PDU, Stop/Freeze PDU, Create Entity PDU, or Remove Entity PDU. See 5.6.5.6.


6. ActionRequestPdu
16
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

7.5.7 A request from an SM to a managed entity to perform a specified action. See 5.6.5.7 (length of list found in field numberOfFixedDatumRecords numberOfVariableDatumRecords)


7. ActionResponsePdu
17
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

Section 7.5.8. When an entity receives an Action Request PDU, that entity shall acknowledge the receipt of the Action Request PDU with an Action Response PDU. See 5.6.5.8. (length of list found in field numberOfFixedDatumRecords numberOfVariableDatumRecords)


8. DataQueryPdu
18
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

Section 7.5.9. Request for data from an entity. See 5.6.5.9 (length of list found in field numberOfFixedDatumRecords numberOfVariableDatumRecords)


9. SetDataPdu
19
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

Section 7.5.10. Initializing or changing internal state information shall be communicated using a Set Data PDU. See 5.6.5.10 (length of list found in field numberOfFixedDatumRecords numberOfVariableDatumRecords)


10. DataPdu
20
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

7.5.11 Information issued in response to a Data Query PDU or Set Data PDU. Section 5.6.5.11 (length of list found in field numberOfFixedDatumRecords numberOfVariableDatumRecords)


11. EventReportPdu
21
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

7.5.12 Reports occurance of a significant event to the simulation manager. See 5.6.5.12. (length of list found in field numberOfFixedDatumRecords numberOfVariableDatumRecords)


12. CommentPdu
22
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

7.5.13 Used to enter arbitrary messages (character strings, for example). See 5.6.5.13 (length of list found in field numberOfVariableDatumRecords)


PDU type and PDUs
ID
    Assess

IEEE Standard 1278.1-2012


DistributedEmissionsRegenerationFamilyPduType
6


Javadoc  Schemadoc

Section 5.3.7. Electronic Emissions. Abstract superclass for distributed emissions PDU


1. ElectromagneticEmissionPdu
23
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

7.6.2 Communicate active electromagnetic emissions, including radar and radar-related electronic warfare (e.g., jamming). Exceptions include IFF interrogations and replies, navigation aids, voice, beacon and data radio communications, directed energy weapons, and laser ranging and designation systems, which are handled by other PDUs. Section 5.3.7.1. (length of list found in field numberOfSystems)


2. DesignatorPdu
24
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

7.6.3 Handles designating operations. See 5.3.7.2.


3. IFFLayer2Pdu
28
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

Section 5.3.7.4.2 When present, layer 2 should follow layer 1 and have the following fields. This requires manual cleanup. the beamData attribute semantics are used in multiple ways. UNFINSISHED (length of list found in field numberOfParameters)


4. IFFPdu 
 IdentificationFriendOrFoePdu
28
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

7.6.5.1 Information about military and civilian interrogators, transponders, and specific other electronic systems. See 5.7.6


5. UnderwaterAcousticPdu
29
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

7.6.4 Information about underwater acoustic emmissions. See 5.7.5. (length of list found in field numberOfShafts numberOfAPAs numberOfUAEmitterSystems)


6. SEESPdu 
 SupplementalEmissionEntityStatePdu
30
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

7.6.6 Certain supplemental information on an entity’s physical state and emissions. See 5.7.7 (length of list found in field numberOfPropulsionSystems numberOfVectoringNozzleSystems)


PDU type and PDUs
ID
    Assess

IEEE Standard 1278.1-2012


EntityManagementFamilyPduType
7


Javadoc  Schemadoc

Managment of grouping of PDUs, and more. Section 7.8


1. AggregateStatePdu
33
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.9.2.2 The Aggregate State PDU shall be used to communicate the state and other pertinent information about an aggregated unit. (length of list found in field numberOfDisAggregates numberOfDisEntities numberOfSilentAggregateTypes numberOfSilentEntityTypes numberOfVariableDatumRecords)


2. IsGroupOfPdu
34
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.9.3.1 The IsGroupOf PDU shall communicate information about the individual states of a group of entities, including state information that is necessary for the receiving simulation applications to represent the issuing group of entities in the simulation applications’ own simulation. (length of list found in field numberOfGroupedEntities)


3. TransferOwnershipPdu
35
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

Information initiating the dyanic allocation and control of simulation entities between two simulation applications.


4. IsPartOfPdu
36
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.9.5 Used to request hierarchical linkage of separately hosted simulation entities


PDU type and PDUs
ID
    Assess

IEEE Standard 1278.1-2012


MinefieldFamilyPduType
8


Javadoc  Schemadoc

Abstract superclass for PDUs relating to minefields. Section 7.9


1. MinefieldStatePdu
37
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.10.2 Communicate information about the minefield, including the location, perimeter, and types of mines contained within it. (length of list found in field numberOfPerimeterPoints numberOfMineTypes)


2. MinefieldQueryPdu
38
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.10.3 Contains information about the requesting entity and the region and mine types of interest to the requesting entity. (length of list found in field numberOfPerimeterPoints numberOfSensorTypes)


3. MinefieldDataPdu
39
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.10.4 Information about the location and status of a collection of mines in a minefield is conveyed through the Minefield Data PDU on an individual mine basis. (length of list found in field numberOfSensorTypes numberOfMinesInThisPdu numberOfMinesInThisPdu numberOfMinesInThisPdu numberOfMinesInThisPdu numberOfMinesInThisPdu numberOfMinesInThisPdu numberOfMinesInThisPdu numberOfMinesInThisPdu numberOfMinesInThisPdu numberOfMinesInThisPdu numberOfMinesInThisPdu numberOfMinesInThisPdu numberOfMinesInThisPdu numberOfMinesInThisPdu)


4. MinefieldResponseNACKPdu
40
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.10.5 Contains information about the requesting entity and the PDU(s) that were not received in response to a query. NACK = Negative Acknowledgment. (length of list found in field numberOfMissingPdus)


PDU type and PDUs
ID
    Assess

IEEE Standard 1278.1-2012


SyntheticEnvironmentFamilyPduType
9


Javadoc  Schemadoc

Section 5.3.11: Abstract superclass for synthetic environment PDUs


1. EnvironmentalProcessPdu
41
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

7.10.2 Used to communicate information about environmental effects and processes. (length of list found in field numberOfEnvironmentRecords)


2. GriddedDataPdu
42
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

7.10.3 Used to communicate information about global, spatially varying environmental effects. (length of list found in field numberOfGridAxes numberOfGridAxes)


3. PointObjectStatePdu
43
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

7.10.4 Used to communicate detailed information about the addition/modification of a synthetic environment object that is geometrically anchored to the terrain with a single point.


4. LinearObjectStatePdu
44
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

7.10.5 Used to communicate detailed information about the addition/modification of a synthetic environment object that is geometrically anchored to the terrain with one point and has size and orientation. (length of list found in field numberOfLinearSegments)


5. ArealObjectStatePdu
45
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

7.10.6 Used to communicate detailed information about the addition/modification of a synthetic environment object that is geometrically anchored to the terrain with a set of three or more points that come to a closure. (length of list found in field numberOfPoints)


PDU type and PDUs
ID
    Assess

IEEE Standard 1278.1-2012


SimulationManagementWithReliabilityFamilyPduType
10


Javadoc  Schemadoc

Simulation Management with Reliability PDUs with reliability service levels in a DIS exercise are an alternative to the Simulation Management PDUs, and may or may not be required for participation in an DIS exercise,


1. CreateEntityRPdu 
 CreateEntityReliablePdu
51
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.12.4.2 Serves the same function as the Create Entity PDU but with the addition of reliability service levels.


2. RemoveEntityRPdu 
 RemoveEntityReliablePdu
52
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.12.4.3 Contains the same information as found in the Remove Entity PDU with the addition of the level of reliability service to be used for the removal action being requested.


3. StartResumeRPdu 
 StartResumeReliablePdu
53
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.12.4.4 Serves the same function as the Start/Resume PDU but with the addition of reliability service levels


4. StopFreezeRPdu 
 StopFreezeReliablePdu
54
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.12.4.5 Serves the same function as the Stop/Freeze PDU (see 5.6.5.5.1) but with the addition of reliability service levels.


5. AcknowledgeRPdu 
 AcknowledgeReliablePdu
55
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.12.4.6 Serves the same function as the Acknowledge PDU but is used to acknowledge the receipt of a Create Entity-R PDU, a Remove Entity-R PDU, a Start/Resume-R PDU, or a Stop/Freeze-R PDU.


6. ActionRequestRPdu 
 ActionRequestReliablePdu
56
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.12.4.7 Serves the same function as the Action Request PDU but with the addition of reliability service levels. (length of list found in field numberOfFixedDatumRecords numberOfVariableDatumRecords)


7. ActionResponseRPdu 
 ActionResponseReliablePdu
57
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.12.4.8 Serves the same function as the Action Response PDU (see 5.6.5.8.1) but is used to acknowledge the receipt of an Action Request-R PDU. (length of list found in field numberOfFixedDatumRecords numberOfVariableDatumRecords)


8. DataQueryRPdu 
 DataQueryReliablePdu
58
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.12.4.9 Serves the same function as the Data Query PDU but with the addition of reliability service levels (length of list found in field numberOfFixedDatumRecords numberOfVariableDatumRecords)


9. SetDataRPdu 
 SetDataReliablePdu
59
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.12.4.10 Serves the same function as the Set Data PDU but with the addition of reliability service levels. (length of list found in field numberOfFixedDatumRecords numberOfVariableDatumRecords)


10. DataRPdu 
 DataReliablePdu
60
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.12.4.11 Serves the same function as the Data PDU but with the addition of reliability service levels and is used in response to a Data Query-R PDU, a Data-R PDU, or a Set Data-R PDU. (length of list found in field numberOfFixedDatumRecords numberOfVariableDatumRecords)


11. EventReportRPdu 
 EventReportReliablePdu
61
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.12.4.12 Contains the same information as found in the Event Report PDU. (length of list found in field numberOfFixedDatumRecords numberOfVariableDatumRecords)


12. CommentRPdu 
 CommentReliablePdu
62
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.12.4.13 Serves the same function as the Comment PDU. (length of list found in field numberOfVariableDatumRecords)


13. RecordRPdu 
 RecordReliablePdu
63
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.12.4.16 Used to respond to a Record Query-R PDU or a Set Record-R PDU. It is used to provide information requested in a Record Query-R PDU, to confirm the information received in a Set Record-R PDU, and to confirm the receipt of a periodic or unsolicited Record-R PDU when the acknowledged service level is used. (length of list found in field numberOfRecordSets)


14. SetRecordRPdu 
 SetRecordReliablePdu
64
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.12.4.15 Used to set or change certain parameter values. These parameter values are contained within a record format as compared to the datum format used in the Set Data-R PDU. (length of list found in field numberOfRecordSets)


15. RecordQueryRPdu 
 RecordQueryReliablePdu
65
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.12.4.14 Used to communicate a request for data in record format. (length of list found in field numberOfRecords)


PDU type and PDUs
ID
    Assess

IEEE Standard 1278.1-2012


LiveEntityFamilyPduType
11


Javadoc  Schemadoc

Does not inherit from PduBase. See section 9.


1. TSPIPdu 
 TimeSpacePositionInformationPdu
46
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

9.4.2 The Time Space Position Information (TSPI) PDU shall communicate information about the LE’s state vector. (length of list found in field systemSpecificDataLength)


2. AppearancePdu
47
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

9.4.3 Communicate information about the appearance of a live entity.


3. ArticulatedPartsPdu
48
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

9.4.4 Communicate information about an entity’s articulated and attached parts. (length of list found in field numberOfParameterRecords)


4. LEFirePdu 
 LiveEntityFirePdu
49
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

9.4.5 Representation of weapons fire in a DIS exercise involving LEs.


5. LEDetonationPdu 
 LiveEntityDetonationPdu
50
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

9.4.6 Communicate information associated with the impact or detonation of a munition.


PDU type and PDUs
ID
    Assess

IEEE Standard 1278.1-2012


LiveEntityPduType
11


Javadoc  Schemadoc

The live entity PDUs have a slightly different header


PDU type and PDUs
ID
    Assess

IEEE Standard 1278.1-2012


InformationOperationsFamilyPduType
13


Javadoc  Schemadoc

Information operations (IO) are the integrated employment of electronic warfare (EW), computer network operations (CNO), psychological operations (PSYOP), military deception (MILDEC), and operations security (OPSEC), along with specific supporting capabilities, to influence, disrupt, corrupt, or otherwise affect enemy information and decision making while protecting friendly information operations.


1. InformationOperationsActionPdu
70
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.13.3.1 Used to communicate an IO attack or the effects of an IO attack on one or more target entities. (length of list found in field numberOfIORecords)


2. InformationOperationsReportPdu
71
 
 relevant? 
 
 in use? 
 

Javadoc  Schemadoc

5.13.4.1 Used to communicate the effects of an IO attack on one or more target entities. (length of list found in field numberOfIORecords)