diff --git a/related_papers_books/00OCT2013/Failure_Modes_Effect_and_Criticality_Analysis-INDENTURE_CONCEPT_3.1.pdf b/related_papers_books/00OCT2013/Failure_Modes_Effect_and_Criticality_Analysis-INDENTURE_CONCEPT_3.1.pdf
new file mode 100644
index 0000000..7ba6c89
Binary files /dev/null and b/related_papers_books/00OCT2013/Failure_Modes_Effect_and_Criticality_Analysis-INDENTURE_CONCEPT_3.1.pdf differ
diff --git a/related_papers_books/00OCT2013/Failure_Modes_Effect_and_Criticality_Analysis-INDENTURE_CONCEPT_3.1.txt b/related_papers_books/00OCT2013/Failure_Modes_Effect_and_Criticality_Analysis-INDENTURE_CONCEPT_3.1.txt
new file mode 100644
index 0000000..654dd13
--- /dev/null
+++ b/related_papers_books/00OCT2013/Failure_Modes_Effect_and_Criticality_Analysis-INDENTURE_CONCEPT_3.1.txt
@@ -0,0 +1,20 @@
+
+
+Indenture.
+
+
+Can start at any level, so it can be based on FTA.
+
+Therefore not a strict modular bottom-up process.
+
+Does not ensure failure modes tracable by DAGS.
+
+Does not ensure all component failure modes must be traced to
+top level symptoms.
+
+Still does not support software.
+
+Indentures are functional---but also can be seen as 
+breaking up chunnks of work for the FMECA team.
+
+