diff --git a/fmmd_concept/System_safety_2011/submission.tex b/fmmd_concept/System_safety_2011/submission.tex
index ebea2e6..9051d6b 100644
--- a/fmmd_concept/System_safety_2011/submission.tex
+++ b/fmmd_concept/System_safety_2011/submission.tex
@@ -1269,6 +1269,13 @@ Furthermore the reasoning path is traceable. By being able to trace a
 top level event down through derived components, to base component
 failure modes, with each step annotated as {\fcs}, the model is easier to maintain.
 
+The example used here is deliberately small for the purpose
+of being presented in a six page paper. FMMD has been applied
+to larger systems encompassing mechanical, electrical and software
+elements. FMMD represents a new technique in that it
+can address all the criteria in table 3, whereas the other methodologies
+can only cover some.
+
 \paragraph{Future work}
 \begin{itemize}
 \item To provide bounds on the size of the state space for the application of the methodology to certain classes of systems.