Six types of objects appear to be needed in order to load and save a state in DITOPS.

Due to dependencies on other objects, the types will be loaded in the following order:

1. Demands
Field Name Description
ULN tpfdd record id
POE geoloc
POD geoloc
ALD real (C dates starting from 0)
EAD real (C dates starting from 0)
LAD real (C dates starting from 0)
mode 'air or 'sea
bulk-stons number in STONS of bulk cargo
oversize-stons number in STONS of oversize cargo
outsize-stons number in STONS of outsize cargo
pax number of pax
bulk-mtons number in MTONS of breakbulk cargo (sea transport)
pol number in Cbarrels of pol cargo
commodity-type e.g., 'resupply
description e.g., "CES PRIME BEEF COMBAT SUPPORT"
mode, bulk-mtons, pol, and commodity-type are not strictly necessary in the jfacc model, unless sea operations are going to be used. Commodity-type is usually derivable from the type of cargo, and the other three are not used when dealing with air data.

2. Operations
Field Name Description
name internal name, not entirely necessary but useful
est real (C dates starting from 0)
eft real (C dates starting from 0)
lst real (C dates starting from 0)
lft real (C dates starting from 0)
demand name of the demand that this operation helps to satisfy
status status of the operation, e.g., :SCHEDULED, :UNSCHEDULED
bulk-stons number in STONS of bulk cargo
oversize-stons number in STONS of oversize cargo
outsize-stons number in STONS of outsize cargo
pax number of pax
parents parents of the operation (always nil so far)
resources the resource used during this operation, e.g., 'C5-0001
alternative-resources a list of resource types that can carry this
origin geoloc
destination geoloc
ULN tpfdd record ID (not used by DITOPS)

3. Geolocs
Field Name Description
name 4 letter abbreviation that becomes a symbol name
latitude real
longitude real
description e.g., "ANDREWS AFB/NAF"

4. Resource Types
Field Name Description
type Air-Fleet, Pol-Fleet, or Cargo-Fleet (stored as A,C,P)
class Air-craft or Sea-craft
name symbol name, e.g., 'C5, 'C141B
speed number, Nautical Miles per hour
load-duration number,  Hours
capacity currently a list. Could be broken up like cargo in demand This field should probably be a separate relation (resource-type capacity amount) called 
resource-type-capacity.
cargo-type-capability similar to capacity, but different fields I would leave this off. It is completely determinable from the capacity. The actual types of capacity are the important feature.
maintenance rate The percentage of planes of this type that are always considered in maintenance and therefore unavailable.

5. Resource Instances
Field Name Description
type type of resource, e.g., 'C5
name description of the fleet, e.g., 'C5-0001
initial-availability-day integer (C dates starting from 0)
initial-port geoloc

6. Resource Breakdowns
Field Name Description
object name of the object that is changing
type type of the object that is changing
start date real (C dates starting from 0)
end date real (C dates starting from 0)
capacity new capacity of the resource
 
7. Dataset Constants
Field Name Description
Start Date Either a date in standard form (Y M D H M S) or 
the keyword NOW
 
I would change all the C dates to be dates in the standard form. I am just suggesting
(Y M D H M S) it might be easier to use Y/M/D H:M:S

Were there other Dataset constants mentioned last week? Model-name? Ticks/per/hour?