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

Author: 
John Sheridan - CIO & CISO

Hi all,

 

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

This is the third Addendum to the EOI, responding to a question received today.

 

Question:

We are finding the Functional Requirements are restrictive when attempting to demonstrate a solution across multiple Functional Requirements.  In some cases we have a capability which will enhance a functional requirement (but not be the core solution to it) out of the box but are restricted in demonstrating it due to the Response Key being absolute.  Would Finance consider:

a.  Adding a fifth “Response Key” to Attachment C – PEMS Solution Requirements.  Something link “NO – but can assist” this will better reflect a solution approach and the narrative to support can be added in the ‘Additional Information’ section. 

b.  A section for a “Solution Overview” or acceptance that this be provided as part of the Executive Summary.  This will allow vendors to describe the proposed solution approach for PEMS.

Response:

a.  An additional option, "No, but I can assist" has been added to the Response Key at Attachment C - PEMS Solution Requirements.  This option can be used where a vendor is attempting to demonstrate a capability which will enhance a functional requirement out of the box but is not the core solution for the requirement.  Note that if this option is used, it is essential that vendors provide an explanation in the Additional Information field for that section. 

b.  Section 1.1 Solution Overview has been added to Attachment C - PEMS Solution Requirements.  Vendors should provide an overview of their PEMS solution in this section. 

This question and response will also be released on Austender.

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

 

John

FIN009171 - PEMS Expression of Interest v2.docx

 

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: 07 September 2017