The Data and Analytics Branch of Data Division operates and manages the use of the One Defence Data Platform. The Branch is seeking suitable qualified and experienced personnel to support the branch in the development/refinement of the financial cost model for use in managing platform and data operations on the One Defence Data Platform.

The One Defence Data platform includes a number of technologies, applications hosted on an Azure Protected Cloud. The method of operation is the realisation of a multi tenancy approach across Defence aligned to the principles of a data mesh ‘on a platform’.

Key applications that reside within the platform include:

• MS Azure
• Cloudera
• Neo4J
• Teradata
• MS SQL
• Alation
• Erwin

A number of subscription-based applications.

Key components that are considered in scope that support the Cloud Platform include:

Components and patterns involving underlying gateway between Defence Protected Environment and Defence Protected Cloud.

This is a deliverables-based contract with an expected duration of three months post commencement. Requests for additional time will be considered and must be included in submissions.

The proposed structure of the deliverable is broken down into two key phases:

1. Phase 1. Establishing Cost Visibility and initial risk reduction. This phase includes a technical review of platform configuration and support to initial cost estimation. In doing so, there following should be addressed:

• Developing documentation pertaining to platform configuration and cost drivers across environments to develop a common view that will be referenced in subsequent phases.
• Identifying existing applications, tools processes to support ongoing FINOPS management already within the platform environment.
• A simplified cost estimator based on predicted data storage; usage based on identified configuration.

2. Phase 2. Foundational FINOPS model. This phase delivers a suitable cost model aligned to the platform cost creation and alignment of existing tools, applications on platform to support ongoing operation. In doing so, the following should be addressed:

• Suitable documentation that recommends changes to platform configuration to match predicted needs and realise cost efficiencies.
• Develop a cost model, basic processes and using existing reporting solutions that support operations and maturation of a foundational FINOPS model across the platform. The cost model is expected to accept variables and inputs to predict potential platform costs e.g. users, data prior to realisation.

Across all phases, the intended approach is to ensure that platform configuration, operating model enables visibility, planning, billing, benchmarking, and optimization of investments and aligned to outcomes across the target operating model.

In delivering this work package it is expected that the successful provider has a working knowledge aligned methodologies such as Technology Business Management (TBM).

The preferred cost structure of submission is a total cost inclusive of all phases and deliverables. In doing so, the supplier accepts:

• Phase 1: A fixed, agreed price that forms the core agreement under the work order.
• Phase 2: Estimated Cost. Suppliers are encouraged to propose solutions to meet the phase 2 deliverables. Informed by Phase 1, the parties will review potential solutions (deliverables) to be delivered under phase 2. This will be assessed on the basis of feasibility (implementation), cost, schedule. It is expected that these factors will drive changes to the cost of Phase 2 which will need to be agreed between both parties before commencement.

In the event Phase 2 deliverables cannot be agreed between the parties before commencement, the agreement will be concluded.