diff --git a/tests/BC003_AL01/BC003_AL01_diagram.png b/tests/BC003_AL01/BC003_AL01_diagram.png
new file mode 100644
index 00000000..347e8ad3
Binary files /dev/null and b/tests/BC003_AL01/BC003_AL01_diagram.png differ
diff --git a/tests/BC003_AL01/Dataset/BC003_AL01.ids b/tests/BC003_AL01/Dataset/BC003_AL01.ids
index 95e1e348..464762d1 100644
--- a/tests/BC003_AL01/Dataset/BC003_AL01.ids
+++ b/tests/BC003_AL01/Dataset/BC003_AL01.ids
@@ -1 +1,121 @@
-BC003_PS01This file was produced for aIFC4Rail project.joao.correa@egis-group.com2023-05-31to verify BC003 PS01 test requirementsIFCPROJECTNameBC003: Test plan 1IFCSIUNITUnitType.LENGTHUNIT.Name.METRE.IFCSIUNITUnitType.PLANEANGLEUNIT.Name.RADIAN.IFCPROJECTEDCRSNameEPSG:3944GeodeticDatumRGF93
\ No newline at end of file
+
+
+
+
+ BC003_PS01
+ This file was produced for aIFC4Rail project.
+ joao.correa@egis-group.com
+ 2023-05-31
+ to verify BC003 PS01 test requirements
+
+
+
+
+
+
+ IFCPROJECT
+
+
+
+
+
+
+ Name
+
+
+ BC003: Test plan 1
+
+
+
+
+
+
+
+
+ IFCSIUNIT
+
+
+
+
+ UnitType
+
+
+ .LENGTHUNIT.
+
+
+
+
+
+
+ Name
+
+
+ .METRE.
+
+
+
+
+
+
+
+
+ IFCSIUNIT
+
+
+
+
+ UnitType
+
+
+ .PLANEANGLEUNIT.
+
+
+
+
+
+
+ Name
+
+
+ .RADIAN.
+
+
+
+
+
+
+
+
+ IFCPROJECTEDCRS
+
+
+
+
+
+
+ Name
+
+
+ EPSG:3944
+
+
+
+
+ GeodeticDatum
+
+
+ RGF93
+
+
+
+
+
+
\ No newline at end of file
diff --git a/tests/BC003_AL01/readme.md b/tests/BC003_AL01/readme.md
index fe047447..0aa32a81 100644
--- a/tests/BC003_AL01/readme.md
+++ b/tests/BC003_AL01/readme.md
@@ -22,10 +22,15 @@ The series of tests that belong to this Business Case are listed as follows:
| ALX4 | Stationing tests on cable joints (punctual) |
| NE02 | Cable routing |
+## IFC concepts involved in this test
+
+The following diagram represents the entities involved in this test.
+![AL01 - involved entities](./BC003_AL01_diagram.png)
+
## Prerequisites
-None.
+PS01 as indicated above.
## Test dataset (input)
@@ -120,5 +125,14 @@ After importing the reference file (`BC003_AL01_alignments.xml`):
## Link to requirements
-:zap:
+
+|ID (local) | Name | Description | Requirements for Appointed Party |
+|-|-|-|-|
+| RI 86 | Unique containment | "Each IfcElement shall be either: - contained in one and only one IfcSpatialStructureElement, or - contained in one and only one IfcLinearPositioningElement." | RA-75 |
+| RI 305 | Alignment organization | CableCarrier alignments shall be related to the track alignment with IfcRelPositions relationship | Cable carrier alignments shall be related to the track alignment |
+| RI 311 | Alignement extruded geometry placement | A IfcCableCarrierSement which geometry is a IfcSectionSolidHorizontal shall be using the same IfcObjectPlacement as the IfcAlignment it is positioned along | NIL|
+| RI 312 | Offset alignment placement | An IfcAlignment which geometry is a IfcOffsetCurveByDistances shall use the same IfcLocalPlacement as the IfcAlignment is relates to | NIL|
+| RI 313 | Extruded CableCarrier positioning | A IfcSectionedSolidHorizontal geometry used for a IfcCableCarrierElement positioned relatively from an IfcAlignment shall use its IfcLocalPlacement | NIL |
+| RI 314 | Project structure | The only "container" aggregated to the project shall be either IfcSite, IfcFacility, IfcAlignment. Other non-IfcProducts shall be connected to the project with IfcRelDeclares | NIL |
+| RI 315 | Elements referencing in Spatial structures | If IfcElements are positioned wrt IfcPositioning elements, then they must be also referenced (instead of aggregated) into a IfcSpatialStructure element | NIL |