Software Developer Technical Working GroupUnclassified

Minutes

/ File ref: N/A
Title: / Software Developer Technical Working Group(SwD TWG)
Issue date: / 22 February 2017
Venue: / N3.13 Phone Conference call: 1800 888 453 #571942905
Event date: / 15 February2017 / Start: 14:00AESST / Finish:15:00
Co-Chairs: / Brian Hughes
Andrew D Smith / Secretary: / Samantha Chudzinski
Publications: /
Email: / SwD TWG
Contact / SIPO / Contact phone: / 1300 139 052
Attendees: / STP SwD Community
Apologies: / N/A
Next meeting / 23/02/2017
Agenda item: 1 – Action Items & Issues / Brian H
Welcome and run through of action items and issues raised for STP
Agenda item: 2 - Revised Payroll Event Specs / Mick F
  • Interface we are providing won’t be the end state solution. The reason being for a non-end state solution is us understand the developers need to begin their development cycles. The timelines are pressing and rather than wait until we have the end-state (which will take longer to release into EVTE) we thought we would go through with the current position and going with the non-end state solution. The document circled with this meeting outlines this. The desire behind this is to give you a known state of what EVTE will look like when we go in there on the 23rd February. This lets each developer decide if they want to start building a product now or whether you want to wait for subsequent releases to get further quality into the closer position of the end-state interface. Please read the PCN – this will contain this information. There’s a chat going on determining whether we will be able to get everything into the March release for EVTE or whether some of that will go into April. There is a push to have this released ASAP. We will keep you updated on the progress of this.
  • An issue was raised by Graham (AEP) on how a payroll event should be declared when an intermediary was involved. Michael K will take than on to get that resolved as an action item (STPA0023).

Agenda item: 3 - STP Implementation Planning / Mick F
  • STP implementation document will be made available along with the end state validation on the 23rd February. To ensure DEVS who haven’t been in this space before have enough time to deliver their implementation. This allows you to decide if your concern is around building in eBMS implementation with SBR and getting the product up and running. Some developers that have been through PLS and earlier SBR implementation won’t have as much difficulty with it and may choose to wait for a higher quality product but what we have is a baseline interface and for the developers new to the market being able to get in and work with SBR etc. being able to get access to our external test environment and to verify you can make a connection and send a message and receive responses from the ATO is an important part of your delivery and this will be the base structure of the Payroll event. Document will be made available on the SBR site with the EVTE environment opening from then forward.

Agenda item: 4– Other Items / Brian H
  • Matt from SAP raised 2 questions – can employers send data directly to the ATO? (final state) will it go directly to the ATO or will it need to go through a third party? i.e a gateway community? We are looking at what the market is going to demand. The ATO’s preference is to minimise this as much as possible but through STP we are not driving the super gateway process. Payroll information won’t use the same message exchange patterns (MEPs). There is currently no specific drive on which way this will go. Our preference is the less number of clients we have the easier it is to maintain. We don’t expect to do full load performance testing in EVTE. And encryption –we don’t want to be sending unencrypted data across the networks. What is being done about this? This is still being looked into. This is an action item for the ATO to be addressed in the next TWG (STPA0022).There is concerns about the 1st July delivery timeframes if encryption is unavailable. SwD’s are voicing that this delivery is off the table if this is unavailable.The suggestion of creating a sub-group to go through options and suitability for this. Further conversations will definitely occur.
  • Remember that all times are run in Canberra/Sydney AESST time
  • Next regular SwD TWG on the 09/02/2017
    Action for all – Next meeting items to be sent to the TWG mailbox.
  • Please ensure you email through your attendance at the TWG sessions to the TWG inbox
  • Contact SwD TWG for any feedback or issues and please copy SIPO into all communication with the SwD TWG inbox.
Technical Working Groups are regularly held every 2nd Thursday of each month – please see SIPO site for future dates (except for the STP out of sessions as well as the January and February TWG’s)
Registration for the TWG is open to everyone – please contact SIPO to register your interest to attend. Your interest to attend won’t result in calendar invites being sent out to Software Developers.

ExternalPage 1 of 2