Flight Operators can provide preliminary flight planning data to TFMS via tfmRequestReply FDBLOCK earlyIntent requests. To submit a valid tfmRequestReply earlyIntent request message to TFMS there are certain JMS properties and message elements / attributes that are required, see Required Elements in all TFMData Requests.The following example illustrates an Early Intent message as entered today by flight operators in current CDM message format as compared to how that same message may be entered in NEMS Request/Reply TFMData format.
EI DAL0819182538.01
FP DAL1529 A320 0450 MSP P1910 370 MSP..GRB..ECK..ALB..BOS/0210
****************Response************
//////////////////////Fri Aug 19 18:25:41 UTC//////////////////////
EI DAL0819182538.01 PROCESSED. 1 OK, 0 ERRORS, 0 WARNINGS
<?xml version="1.0" encoding="UTF-8"?>
<tx:tfmDataService xmlns="urn:us:gov:dot:faa:atm:tfm:tfmrequestreplytypes" xmlns:ax="http://www.fixm.aero/tfm/3.1" xmlns:fdm="urn:us:gov:dot:faa:atm:tfm:flightdata" xmlns:frt="urn:us:gov:dot:faa:atm:tfm:rapttimeline" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tx="urn:us:gov:dot:faa:atm:tfm:tfmdataservice" xmlns:fim="urn:us:gov:dot:faa:atm:tfm:flowinformation" xmlns:fcm="urn:us:gov:dot:faa:atm:tfm:ficommonmessages" xmlns:fce="urn:us:gov:dot:faa:atm:tfm:ficommondatatypes" xmlns:fm2="urn:us:gov:dot:faa:atm:tfm:ficommonmessages2" xmlns:nxce="urn:us:gov:dot:faa:atm:tfm:tfmdatacoreelements" xmlns:nxcm="urn:us:gov:dot:faa:atm:tfm:flightdatacommonmessages">
<tx:tfmRequestReply>
<tx:request serviceCode="FDBLOCK">
<requestId>
<requestor>
<fm2:center>DAL</fm2:center>
<fm2:requestorId>20.13.196.90</fm2:requestorId>
</requestor>
<uniqueMsgId>4f55856f-8d75-4509-9af4-111111111112</uniqueMsgId>
<replyOption>SUCC_OR_ERR_OR_WARN</replyOption>
</requestId>
<flightBlockReqData>
<earlyIntent>
<aircraftIdentification>DAL1529</aircraftIdentification>
<aircraftSpecification>A320</aircraftSpecification>
<airSpeed>
<nxce:filedTrueAirSpeed>450</nxce:filedTrueAirSpeed>
</airSpeed>
<coordinationPoint>
<fm2:fixName>MSP</fm2:fixName>
</coordinationPoint>
<coordinationTime type="PROPOSED">2016-08-19T19:10:47Z</coordinationTime>
<requestedAltitude>
<fm2:baseAltitude>370</fm2:baseAltitude>
</requestedAltitude>
<filedRoute>MSP..GRB..ECK..ALB..BOS/0210</filedRoute>
</earlyIntent>
</flightBlockReqData>
</tx:request>
</tx:tfmRequestReply>
</tx:tfmDataService>
****************Response Received **************
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns4:tfmDataService xmlns:ns16="http://www.fixm.aero/flight/3.0" xmlns:ns14="http://www.fixm.aero/base/3.0" xmlns:ns15="http://www.fixm.aero/foundation/3.0" xmlns:ns9="urn:us:gov:dot:faa:atm:tfm:tfmrequestreplytypes" xmlns:ns5="http://www.fixm.aero/tfm/3.1" xmlns:ns12="urn:us:gov:dot:faa:atm:tfm:flowinformation" xmlns:ns6="urn:us:gov:dot:faa:atm:tfm:tfmdatacoreelements" xmlns:ns13="urn:us:gov:dot:faa:atm:tfm:rapttimeline" xmlns:ns7="http://www.faa.aero/nas/3.1" xmlns:ns10="urn:us:gov:dot:faa:atm:tfm:ficommonmessages" xmlns:ns8="urn:us:gov:dot:faa:atm:tfm:ficommonmessages2" xmlns:ns11="urn:us:gov:dot:faa:atm:tfm:ficommondatatypes" xmlns:ns2="urn:us:gov:dot:faa:atm:tfm:flightdatacommonmessages" xmlns:ns4="urn:us:gov:dot:faa:atm:tfm:tfmdataservice" xmlns:ns3="urn:us:gov:dot:faa:atm:tfm:flightdata">
<ns4:tfmRequestReply>
<ns4:reply serviceCode="FDBLOCK">
<ns9:requestId>
<ns9:requestor>
<ns8:center>DAL</ns8:center>
<ns8:requestorId>20_13_196_90</ns8:requestorId>
</ns9:requestor>
<ns9:uniqueMsgId>4f55856f-8d75-4509-9af4-111111111112</ns9:uniqueMsgId>
</ns9:requestId>
<ns9:status>SUCCESS</ns9:status>
</ns4:reply>
</ns4:tfmRequestReply>
</ns4:tfmDataService>