The Defence stream includes a number of workshops featuring systems practitioners from defence, defence industry and academia discussing current challenges. The program also features a number of interesting tutorials.
The working sessions allow practitioners to explore the state of Sys Eng maturity and identify areas to target for enhancement. The “First Principles Review – Where now in SE?” session will explore a number of topics around the FPR and encourage participants interaction. Sessions are open to all interested parties; systems practitioners with application experience in other domains particularly welcome.
Modelling across the Contractual Boundary
Facilitator: Jon Hallett
At the 2012 DSTO MBSE symposium, a workshop was conducted to help understand the boundaries and issues preventing the passing of descriptive models generated by Defence projects to Industry. The results of this workshop informed research work conducted by Dr Quoc Do and Professor Stephen Cook at the University of South Australia. Findings of this research were presented at the 2013 DSTO MBSE symposium and SETE 2014. This workshop looks to see if anything has changed over the last 5 years and to brainstorm the advantages to projects to share models produced on either side of the contractual boundary, what the problems are in doing so and what could be done to improve the situation.
- Determine the benefits
- Define and understand the problem
a. Determine the current barriers to Defence passing descriptive models (used to generate CDD sets) across the contractual boundary
b. Determine the Industry-side issues in receiving Descriptive models from Defence
c. Determine the Industry-side issue of passing solution models back to Defence
d. Determine the Defence-side issues of receiving and assessing solution models provided by Industry
- Propose potential solution
a. Defence-side solutions and initiatives
b. Industry-side solutions and practices
Effective Systems Engineering and Project Management Integration
Presenter: Angela Tuffley, RedBay Consulting
Within every project, two distinct disciplines, engineering and project management, are required to deliver a successful outcome. Yet often these two disciplines operate as two separate entities; focussing on their own accountabilities rather than collaborating as a team. An example of effective systems engineering and project management integration was highlighted in a case study on the Electronic Support Upgrade for the Royal Australian Navy’s Anzac Class Frigate published in the Integrating Program Management and Systems Engineering book sponsored by the Project Management Institute (PMI) and the International Council on Systems Engineers (INCOSE). The source for the case study was a Schedule Compliance Risk Assessment Methodology (SCRAM) Review. SCRAM is an independent review to identify issues and risks to schedule compliance and embodies best practices from project management, schedule development, systems engineering and software engineering.
This one hour workshop will briefly introduce SCRAM, the Root Cause Analysis of Schedule Slippage (RCASS) model and explore the key elements of systems engineering and project management integration detailed in the SCRAM Review case study. Active participation by attendees is encouraged.
Decision making in complex systems
Facilitators: Mal Tutty, Keith Joiner and Luke Brown
Over the last three decades, defence communication and information systems have been increasing the complexity and interconnectedness of systems that has pervaded society more broadly throughout the Information Age. Even more than society in the broad, Western Departments of Defence (DoDs) have sought to attain information dominance. The result has been a large number of complex systems, system-of-systems and families-of-system-of-systems. This workshop examines the Australian implications of the big four challenges facing decision making in complex systems and the six key assurance initiatives pursued systematically by the US DoD initiatives to effect these more integrated, interoperable and information-assured (I3A) capabilities, while also ensuring these capabilities remain resilient to the new cyber threats.