SIS Release Management Breakout Session

Transcription

1 SIS Release Management Breakout Session Paula FEINBERG Test Manager, SIS Operations Thierry CERPOLET Product Manager, Web Access Services 1 11 October

2 Agenda SIS Release Management Strategy SIS Evolution Q&A 2

3 SIS Release Management Strategy 3

4 Type of Releases and Strategy Major Releases Aim > Changes to application / infrastructure functionality Periodicity > Twice a year in P1 Nov and P1 May Changes to record structures is scheduled in P1 May, so once a year Managed > as projects between Service Provider / IATA 4

5 Type of Releases and Strategy (2) Maintenance Releases Aim > To fix software problems/bugs reported by SIS users or IATA Periodicity > usually twice a month For urgent cases put as hot fixes in SIS prod immediately Managed > Weekly Release Management meetings with Service Provider as to prioritize next Help Desk incidents fixes to be deployed 5

6 Release Management Process Summary Issues / Change Requests raised by industry / SIS Ops / SIS General Mtg Faults are included in Maintenance Releases Enhancements are included in Major Releases 6

7 How to raise a Change request SIS Help Desk Web Form /Pages/sis-help-desk.aspx to SIS Operations [email protected] Requests bringing value for the entire industry will be considered for CMP implementation 7

8 CMP Prioritization Process 8

9 Timelines for CMP selected vs deployment 9

10 Open CMPs for Future Releases: where? List of CMPs available from IATA / SIS / Technical Documentation 10

11 Release Management Flow Development by vendor Release is tested and certified by vendor Sandbox Staging envt changes related to validations Release is tested and verified by IATA Release deployed on production Staging environment for CMPs / issues 11

12 Releases Communication Release Notes Communication Major Releases: via SIS Bulletin +/- 3 months prior deployment Maintenance Releases: directly in SIS web site at time of deployment Downtime Cover fixes when they concern an existing validation that was not working or a bug that was affecting a large group of carriers always published via SIS Bulletins (for Major releases) always confirmed in advance via SIS Ops Downtime s 12

13 Maintenance Releases Calendar Advise community of upcoming downtimes Plan is for two Maintenance Releases a month One just after a Closure Day and prior Offline Archive Maintenance Releases implementation window July 9 th July 10 th July 15 th July 17 th Jul P1 Submission opens Jun P4 Output generation Jul P1 Submission deadline Jul P1 Output generation One coordinated with possible IT maintenance need on a Saturday Calendar communicated via SIS Bulletins 13

14 SIS Evolution 14

15 SIS History : Major Steps Project Operations Oct 2011 Rel. 1.0 SIS went live with PAX and MISC Billings May 2012 Rel CGO and UATP Billings (*) go live (*) UATP not activated at start) Since Nov 2012 Enhancements deployed every 6 months in May and Nov 15

16 History Major Releases since IS-week 1 Rel. 1.2 (Nov 2012) Enhancements covered deployed by 8 Nov 2012 Rel. 1.3 (May 2013) Enhancements covered deployed by 8 May 2013 Rel. 1.4 (Nov 2013) Enhancements covered deployed by 8 Nov 2013 Next Rel. 1.5 (May 2014) 16

17 Release 1.2 contents - P1 Nov 2012 Enhancements deployed by 8 Nov 2012 Key CMPs Validation of Flight Date in Passenger Prime Billings (PAX) Invoice PDF changes (MISC/UATP) Size of Tax/VAT percentage changed from 2 to 3 decimals for IS-XML / IS- WEB capture (MISC/UATP) Report on IS-WEB User s Permissions Clearance Currency & Amount in IS- Processing Dashboard Audit Trail to maintain log of invoices deleted by carriers on IS-WEB 17

18 Release 1.3 contents P1 May 2013 Enhancements deployed by 8 May 2013 Key CMPs Validation of Original Billing Amounts in SIS Rejection Memos (PAX/CGO) Query on Billing History Using only Ticket Number Field (PAX/CGO) 11 digit ticket / FIM numbers being captured (PAX) Re-rejection of a RM that has no Coupon Breakdown (PAX) Increase of VAT Description Field (MISC/UATP) Field Part Number for Engineering to be Extended to 40 Characters (MISC) Location Code to be made Mandatory for All Invoices (MISC) RAM A13 New Validations and New Charge Code (MISC) Validation of reference data against the member profile (ALL Billings) 18

19 Release 1.4 contents P1 Nov 2013 Enhancements deployed by 8 Nov 2013 Key CMPs Source code in PAX Receivables / Payables RM/BM/CM Summary Report Preview invoice / Credit Note captured on IS-WEB prior to submission (MISC) Tax Invoice Number to be included in Invoice PDF (MISC) Daily Output generation for Bilateral invoices (MISC) Correspondence ref. Number to be displayed on correspond. invoice PDF (MISC) Addition of a column for Charge Code Type in Invoice PDF (UATP) Correspondence download with supporting documents (ALL Billings) Correspondence Screen Option to Close/Accept (ALL Billings) Add submission method columns to the Processing Dashboard 19

20 Release 1.5 contents P1 May 2014 Enhancements in scope for deployment by 8 May 2014 Key CMPs prioritized by the SIS SG PDF invoice does not contain information about scaling factor (MISC) SIS to accept Cyrillic characters (MISC) User to be able to reply to a correspondence upon clicking hyperlink in correspondence alert (ALL Billings) SIS to generate weekly reference data update in CSV report (ALL Billings) Updates to Master / Member Profile data in production automatically take effect in Sandbox environment 20

21 SIS History: # of Maintenance Releases After Rel. 1.2 After Rel Maint Hot Fixes - 32% 21

22 SIS Maintenance Fixes Deployed 1.2/ After Rel. 1.3 After Rel After Rel Showstopper Major After Rel % - 19% 22

23 SIS architecture / solution improvements File loading optimization Review insertion mechanism in database Purging activities Transactions Oracle alignment New Oracle Server version (to be deployed in Jan 2014) 23

24 Q & A 24

25 Thank you. SIS Website: 25