Title: CM - Facility Designation User Requirements Correction

PDR Reference:				98090005
Originator Reference: 
SARPs Document Reference: 		CM SARPs, Sections 2.1.7.1.1.1 - 
						2.1.7.1.1.7, 2.1.7.1.2, 2.1.7.1.3.4, 
						2.1.7.2.2.6 - 2.1.7.2.2.7, 2.1.7.2.3.1, 
						2.1.7.2.6.5
Status: 					RESOLVED
Impact :					D (Minor)
PDR Revision Date: 			28/09/98 (PROPOSED -> RESOLVED)
						22/09/98 (SUBMITTED -> ACCEPTED -> PROPOSED)
						18/09/98 (PDR renumbered from 98090003 to 
						98090005, note 2 added in item 4)
PDR Submission Date:  			17/09/98
Submitting State/Organization: 	ATNP WG3/SG2
Submitting Author Name: 		Saccone, G
Submitting Author E-mail Address: 	gsaccone@west.raytheon.com
Submitting Author Supplemental 
Contact Information:
						ph 1 604 821-5182, fx 1 604 279-5795
SARPs Date:  				IV2.3 (Doc 9705)
SARPs Language: 				English

Summary of Defect: 

This PDR supersedes PDR 98050020. 

This PDR addresses operational concerns over the use of the optional facility designation field of the CMLogonRequest (cf. the detailed description of the problem in PDR 98050020).  In order to ensure that the facility designation field is used and interpreted in a consistent manner, changes to the user requirements of CM must be made.

Assigned SME: 				Sub-Volume II SME

Proposed SARPs amendments:

1/ In 2.1.7.1.1.1, change (deleted text) {new text}:
	2)	for applications that can be ground initiated: application name, version number, and address for all versions that can be supported,( and)

d)	{the facility designation of the facility with which the CM-air-user wishes to exchange application information (if required), and
e)}	flight information data as required by the ground system.

2/ Add note to 2.1.7.1.1.1 <text in italics>:
<Note.- The> facility designation <is only used if the CM-air-user wants to explicitly identify a facility other than the one contained in the> Facility Designation <parameter of the CM-logon service for which it requires application information.>

Renumber 2.1.7.1.1.2 through 2.1.7.1.1.6 to 2.1.7.1.1.3 through 2.1.7.1.1.7.

3/ Add 2.1.7.1.1.2 <text in italics>, [text bold]:
2.1.7.1.1.2	[Recommendation.] - <The CM-air-user should only use the> facilityDesignation <field of the> CMLogonRequest <if requesting information for a facility other than the one specified in the> Facility Designation <parameter of the CM-logon service.>

4/ Add notes to 2.1.7.1.1.7 <text in italics>:
<Note 1.- If the> facilityDesignation <field of the> CMLogonRequest <was provided, then the information contained in the> Logon Response <parameter corresponds to that facility designation.  If the> facilityDesignation <field of the> CMLogonRequest <was not provided, then the information contained in the> Logon Response <parameter corresponds to the> Facility Designation <parameter of the CM-logon service.>
<Note 2.- If the> facilityDesignation <field of the> LogonRequest <was provided and no application information is returned in the> Logon Response <parameter, this means that the CM-ground-user does not have access to the information for the requested facility or that the requested facility does not support any of the proposed applications.
5/ Add note to 2.1.7.1.2 <text in italics>:
<Note.- If a CM-update service indication is received, then the information contained in the> Update Information <parameter corresponds to the facility designation contained in the> Facility Designation <parameter, or, if a dialogue exists, the facility with which the dialogue is in place.>

6/ Add the following to the note of 2.1.7.1.3.4 <text in italics>:
<  However, the facility designation will not be provided as part of the> CMLogonRequest <in this case.>

Renumber 2.1.7.2.2.6 and 2.1.7.2.2.7 to 2.1.7.2.2.8 and 2.1.7.2.2.9

7/ Add 2.1.7.2.2.6 <text in italics>:

2.1.7.2.2.6  If the facility designation is present in the> Logon Request <parameter, then the application information contained in the> CMLogonResponse <shall correspond to that facility designation.>

8/ Add note to 2.1.7.2.2.6 <text in italics>:

<Note.-  If a CM-ground-user does not have access to the information for the requested facility, no application information is returned.>

9/ Add 2.1.7.2.2.7 <text in italics>:

2.1.7.2.2.7  If the facility designation is not present in the <Logon Request> parameter, then the application information contained in the <LogonResponse> shall correspond to the responding CM-ground-user's facility designation.

10/ Add note to 2.1.7.2.3.1 <text in italics>:

<Note.- The CM-update service only corresponds to a ground facility's local applications.>

11/ Change 2.1.7.2.6.5 <text in italics> [text bold] (deleted text) {new text}:

2.1.7.2.6.5  {[Recommendation.] -} <Upon the receipt of a> Forward Request <from a CM-forward service indication, the receiving CM-ground-user (shall){should} invoke a CM-update service request with the indicated aircraft{ if the update service is supported}.>

SME Recommendation to CCB: 			-

CCB Decision:					atnp_ccb_chair: ACCEPTED (22/09/98) 
							CCB-7 (Bordeaux): RESOLVED (28/09/98)