Parliamentary Expenses Management System (PEMS) - EOI - Addenda 02

Author: 
John Sheridan - CIO & CISO

Hi all,

 

On Monday 21 August I released the PEMS EOI for your response by Friday 15 September 2017.

A response to a clarification question was provided in Addenda 01 to the EOI on Wednesday 30 August.  This week, we’ve received the following further requests for clarification:   

 

Question 1:

  • Can you please provide breakdown of estimated 3000 users for each of groups identified (Users, Administrators, Industry)?

  • Can you please provide estimated number of expenses processed per year?

a.  And/Or number of enquires for explaining/applying expense policy (ie eligibility )

  • Can you please provide estimated number of unique daily visitors and/or hits for the Web Portal and Content Management?

  • Can you please provide estimated number of emails to be generated and sent by the CRM and/or Web Portal/CMS component (ie internal or external marketing campaigns )

  • Can you please provide estimated number of Contacts + Accounts/Organisations (ie Suppliers, App Builders, SME, partners etc) to be managed by the CRM component.

  • Can you please provide estimated number of API calls to the system?

Response 1: 

  • A breakdown of the 3,000 users is estimated as: 

a.  Users:  2,700

b.  Administrators: 170

c.  Industry:  130

Note that not all users will use all components of the solution.  Concurrent user numbers are estimated at approximately 20% of the maximum.

  • The approximate average number of expenses processed annually is:

a.  340,000 expense transactions

b.  170,000 advice and support transactions

  • The number of unique daily visitors and/or hits for the Web Portal and Content Management is estimated at 600, being 20% of the total number of users. 

  • The estimated number of emails to be generated and sent will be determined by the proposed solution.  The expectation is that communication will be customised in accordance with the users preferred channel, leading to a reduction in the volume of emails generated. 

  • The minimum estimated number of Contacts and Accounts / Organisations to be managed by the CRM is 30,000.  This estimate increases at times of changing business activities. 

  • The estimated number of API calls will be determined by the solution and architecture proposed by vendors. 

 

Question 2:

  • Attachment C - Since we are only responding to two of the core capability requirements, should we mark the questions related to other core capabilities in Attachment C as "N" - "No does not demonstrate" or should we leave them blank or should we remove them from the list?

  • Attachment I - The pricing tables provided require prices to be provided on a "Per user" basis for both Establishment and Annual ongoing costs. However our pricing model is not dependent on the number of users but rather on the number of trips performed (per trip model) or Number of vehicles in use (per vehicle per month model).   Please advise as to how we could best fill out this section.

Response 2: 

  • Questions which are not being responded to should be marked as "N" - "No does not demonstrate".

  • Where a vendor responds with any variation to the Per User cost breakdown model, an explanation on the reason for the variation should be provided.  Refer to Attachment G – Assessment Criteria where assessment of the pricing response will take into consideration the ‘Extent to which the respondents proposed indicative pricing is transparent and predicable and enables Finance to gauge total cost of ownership (TCO) for the solution.’

 

These questions and responses will also be released on Austender.

If you have any further questions, please contact AusPEMS@finance.gov.au

 

John

Add new comment

Commenting

  • Allowed HTML tags: <a> <strong> <em>
  • Lines and paragraphs break automatically.
  • Web page addresses and e-mail addresses turn into links automatically.

Filtered HTML

  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.

Last updated: 05 September 2017