Vital Planning and Analysis (VIPA) Software Utilities - Engines and Services

Provision of services for developing and maintaining software utilities (engines and services for the Vital Planning and Analysis (VIPA) Version 2.0 joint logistic planning tool and Aid Memoire Web Services.

Note: To request RFT Documentation (Must be by Email as below

Addenda 1 Date 18/11/2009

Questions and Answers

Question 1 - SOW clause 7.4.1 lists as an ‘Essential’ requirement that all named staff to be located in Adelaide. Are you able to provide additional information concerning the drivers for this requirement.

Answer 1 - The drivers for this requirement are that the contract is for the provision of services and an ability to interact directly with staff involved at DSTO Edinburgh. For example the explanation of concepts, peer review, gain direct feedback and participate in design decisions, product behaviours, testing approaches, scheduling and project re-planning. There is also the requirement at clause 6 for regular on-site progress meetings.

Addenda 2 Dated 04 Dec 09

QUESTION & ANSWERS (Continued)

Question 2. - [Relates to DSLD 01 & 02 RFT] - When do you anticipate starting the projects? The letter at the start of each RFT indicates a negotiation process that will finish on the 5 February 2010 and the resource requests (generally) indicate Jan 2010 – Jun 2011.Should we assume that it’s an 18 month project (plus 6 months) commencing in February 2010? E.g. Feb 2010 – Jul 2011.

Answer 2. - The VIPA Version 2.0 Project Plan (in Part 2 of the AUSDEFCON (Services) documentation) - specifically paragraphs 5.1 (for DSLD 01/2009) and paragraph 6.1 (for DSLD 02/2009) reflects a Contract Commencement Date of "Late January 2010".For consistency and allowing for negotiation, however, would intend contract start on week commencing 8 February 2010.For DSLD 01/2009, the “Specified Personnel” section - Section 7, Paragraphs 7.4.2 (Engine and Calculator Software Developers) and 7.4.3 (Data Model and Web Service Developer) - the indicative staff requirements and tenure timeframes are provided.For DSLD 02/2009, the “Specified Personnel” Section 8, Paragraphs 8.4.2 to 8.4.7 the various indicative staff requirements and tenure timeframes are provided.

Question 3. - [Relates to DSLD 02 RFT / Refers to DSLD 01 RFT] - Would you consider implementing the client applications [02] in an online framework rather than as a desktop app?We notice that you’re using a web-services architecture in [DSLD 01] that would lend itself to consumption in an online application.

Answer 3. - We are only considering a desktop application at this time.

Question 4. - [Refers to DSLD 02 RFT] - There is a requirement for improving the user interface of the client application in the RFT [02] but there doesn’t seem to be a resource request that aligns with this requirement. E.g. a user interface designer or a user experience designer. Should we include a designer as an option in our response to [02]?

Answer 4. - A user experience designer is not considered essential; however, a tendered response could submit options such as a user experience designer as part of their solution should they wish.Software developers with substantial user interface development experience (in Java) are required.

Question 5. - [Refers to DSLD 01 & 02] - There isn’t a project manager listed in the engines RFT [01]. Are you expecting that the Project Manager from the client applications RFT [02] would manage both streams? Or would the developers in [01] be working directly for a Project Manager from Defence?

Answer 5. – The project is to be technically directed by DSTO, with Defence providing an overarching Project Manager.The Project Manager for DSLD 02/2009 shall support the Defence Project Manager.

Question 6. - [Refers to DSLD 01 & 02] - How are the dependencies between the development of the web-services in [DSLD 01] being managed for their consumption by the applications in [DSLD 02].Should the applications stream [02] have a delayed start to minimise the management of dependencies?

Answer 6. – The program schedules will require both applications and development streams simultaneously.The applications stream [02] can utilise VIPA 1.1 web-services and architecture for initial development/consumption.