1. Vulnerability Requirements in the
RAN
Goal setting and testing via computer models
Kurt Pudniks
Vulnerability Technology Manager
Total Ship Survivability
DNPS – NAVSYSCOM – RAN
27/03/09

2. Technical Standard
 CNE sponsors the DEF AUST 5000 documents
 Materiel Requirements Set (MRS)
 Defines the following areas:
- Scope
- Definitions
- Background
- Functional Performance Requirements
- Constraints
- Deliverables

3. Technical Standard
 Vol 2 Pt 3 is the Platform Vulnerability
MRS
 Defines the vulnerability goals in terms of
retained capabilities
 Mandates the modeling approach
- Note this is not prescriptive to a particular software
package, but tries to talk in general modeling terms
- Could it be done by hand?

4. Goal Framework
 The vulnerability goals rely on a modeling framework
 The framework is meant to be general
 Makes use of general ideas such as:
1. Nodes
2. Links
3. Fault trees
4. Coarse and specific volume based damage scenarios
(damage templates)
5. Capabilities vs. functions
6. Data mapping and lists (spreadsheets or databases)
7. Percentages and colour coded thresholds
(communication of results)

5. Nodes and Links [1 & 2]

6. Fault Tree [3]

7. Coarse Damage Scenarios [4]

8. Specific Damage Scenarios [4]

9. Capabilities vs. Functions [5]
 A capability is defined as:
- Capability is the power to achieve a desired operational effect in a
nominated environment, within a specified time, and to sustain
that effect for a designated period.
- Capability is generated by Fundamental Inputs to Capability
comprising organisation, personnel, collective training, major
systems, supplies, facilities, support, command and management.
an action the ship can do
- Track targets
- Fire weapons
- Sustain
- Mobility
- Emergency Evacuation
- Specialist capabilities

10. Capabilities vs. Functions [5]
 A function is defined as:
- An action that occurs within the ship or an action that the
ship performs on the external environment.
- A function is a conceptual idea, with no tangible physical
equivalent
- Propulsion
- Steering
- Buoyancy
- Internal Communications
- External Communications
- Sensors (if any)
- Weapons (if any)
- Combat System (if any)

11. Data Mapping [6]
 Functions are mapped onto nodes
 Capabilities are mapped onto functions
 In total there are only three levels of data, and
two interfaces between the three levels
- NODE
- NODE / FUNCTION INTERFACE (MAP)
- FUNCTION
- FUNCTION / CAPABILITY INTERFACE (MAP)
- CAPABILITY

12. Retained Capability % Levels [7]
 Damage is binary
 However multiple nodes can have one function
 Therefore a function value can be between 0 and 1
in n steps (n = number of functions)
- Green shall indicate x = 100%
- Yellow shall indicate 50% < x < 100%.
- Orange shall indicate 0% < x <= 50%.
- Red shall indicate 0%
 The capability will adopt the most conservative
colour (least or most red!)

13. Retained Capability % Levels [7]

14. Vulnerability Study - A to Z
 Build ship model with nodes and links
- Assign functions to nodes
- Assign capabilities to functions
 Create threat volumes
- coarse zones
- specific volumes
 “Intersect” the threat with the ship
 Run fault tree analysis to find cascading
disablement due to damaged systems
 Summarise results in a retained capability list

15. Minimum Retained Capabilities