FCC/readMe.txt

This Fdc server implementation was copied and modified at Dec, 2017, and based from EMEA\DotNet\Production\SHG EMSG OPT PRODUCTION\SSF\SSF.Dev\SSF.FC.Solution\
it was refered as Old FC and have not aligned with latest Global FC, and the latest Global FC have very limited message schema changed, refer this email to know the changes(may have later email to have more details):
			From: Loewy, Bradford 
			Sent: Thursday, October 26, 2017 5:57 PM
			To: Alonso, Gabriel <gabriel.alonso@doverfs.com>; Tirinzoni, Michele <michele.tirinzoni@doverfs.com>; Molina, Rodrigo <rodrigo.possemolina@doverfs.com>; Yin, Li <li.yin@doverfs.com>; He, Jackie <jackie.he@doverfs.com>; Holmqvist, Henrik <henrik.holmqvist@doverfs.com>; Von Lochow, Peter (Contractor) <peter.vonlochow@doverfs.com>
			Subject: RE: MsgRouter security with global FCC

			All,

			Please review the attached functional specification and updated schemas for this enhancement.  Let me know if there are any comments/questions/concerns.

			As my local schema copies may not match exactly what is checked in on the mainline, here are the changes listed out.
			Schema Changes:
			FDC_Basic_Types.xsd
			•	Added FPDeviceState complex type that extends DeviceState to add the Stopped optional attribute
			o	Stopped attribute is of type “True”, which forces a value of “true” if present
			•	RequestType – Added enumerated values “StopFuelPoint” and “StartFuelPoint”

			FDC_GetFPState_Respone.xsd
			•	Changed DeviceState from DeviceState type to FPDeviceState type

			FDC_FPStateChange_Unsolicted.xsd
			•	Changed DeviceState from DeviceState type to FPDeviceState type

			FDC_StopFuelPoint_Request and FDC_StopFuelPoint_Response – New
			FDC_StartFuelPoint_Request and FDC_StartFuelPoint_Response - New



we may need to merge this new Fdc server in sometime, but not now since the Fdc client side (android POS) need align with it as well.