EST 337120 Sterling Portal Interface

STATEMENT OF WORK CHANGE REQUEST ESTIMATE

Client	PART	Project	DEV	Site	PART
Client Reference	PL-STERLING PORTAL	Aptean Reference	337120	Estimate Version	1.0
Prepared By	A N Walker			Estimate Date	13/09/16
'Invoice Reference	'			Priority	3
Customer	ALL			System Version	3.3.X

Client Request

From Stirling - Phil Hall on Tuesday, 26 July, 2016 4:28 PM, cc John Davidson. We have now got the import working for AKW, we would also like to get it working for all delivery partners in Partnerlink, with this in mind would it be possible for you to give us a single login with all of the signatures for Partnerlink partners? This way we could import them all and they would just match to the relevant job. Also configure the firewall to give Stirling access from the Partnerlink server IP address 81.138.72.158

Aptean Solution

Note: The export of data from C-ePOD has been extended for multiple additional systems (i.e. the pallet network tracking exports) far beyond it's initial design. As such, the export process has at times reached its maximum capacity in the current form. As part of this change, the export process must have many efficiency changes put into it to handle: batching of FTP file sends, to reduce the overhead of connecting to FTP sites multiple times. reducing the number of times that the process builds export files, if the file is to be replicated to multiple destinations. distribute the decision as to whether files will be sent to the point of completing the jobs, rather than at the point of export. A new export configuration will be added to each site, to control the sending of the Job Completion export file to Sterling's Portal. The rule allowing only one configuration per type to be added to a configuration will be relaxed, so that this export configuration may be added. The configuration will set the destination FTP directory and file naming specification and connectivity parameters to be the same for each of the sites. The database will be modified to create an Export Control record for each job that requires it, at the point that a job is set to Completed or Cancelled status. This will be triggered by the database at the point of completion and will be largely sourced from the existing package that decides which configuration requires an export. These changes will reduce development costs and increase the speed of the export process. The process will be modified slightly to obey the configuration against the site, rather than requiring the configuration to be the same name as the site code - this is required to allow the control records to be written. As the control records are being written based off the configuration against the site and job group, the new configuration added will result in a new control file being created for the new export to Stirling's Portal system. The Export process for jobs will be changed to retrieve the control records rather than attempt to find each job that requires updating. The job associated to the control record will be retrieved at the same time. This will ensure a far more efficient export process. The process will 'batch' similar export files together, and produce the XML once only, replicating this to several files. The process will produce the files in a temporary area, and will send all FTP files for the same destination at the same time. Only then will a file be marked as successfully sent. The files will be named based on the Export configuration, expected to be: EPOD_STIRLING_<SITE>_<DATE>__<SEQ>.XML For example: EPOD_STIRLING_L01_20160805_093427_80.XML EPOD_STIRLING_L01_20160805_093427_81.XML EPOD_STIRLING_L03_20160805_093427_80.XML Note that the sequence may only be unique for the site file being sent, rather than for all messages sent in that batch. Any issues with creating or sending the export file will result in the Error or Reprocess status being set against the control record, as normal. The changes above will result in a faster processing export process, as well as improving the capability and efficiency of the re-sending process should an individual record fail to process. Access will be provided to Stirling to the Partnerlink server for the purposes of this change.

Warning:

Unknown costs for client/year (PART/2016)

Cost Details
Activity	Hours	Rate per hour (£)	Cost (£ Exc. VAT)
Requirements	0.00	0.00	£0.00
Change Request Evaluation	0.75	0.00	£0.00
Functional Specification	2.50	0.00	£0.00
Technical Specification	0.00	0.00	£0.00
Development	10.50	0.00	£0.00
Testing and Release	2.50	0.00	£0.00
Implementation	0.25	0.00	£0.00
Project Management	0.75	0.00	£0.00
TOTAL	17.25		£0.00

Estimate excludes training, release to live and go live support.

Copyright © Aptean 2016. This estimate has an expiry date of 30 days from the specified Estimate Date. The information contained herein is supplied without liability for errors or omissions.