Keep responsibility clear as the project changes hands.
Delivery is not one event. Requirements, manufacturer decisions, procurement commitments, site interfaces and acceptance each belong to different stages. The architecture matters because responsibility can become ambiguous at every transition.
A handoff is a control point.
This page defines the responsibility logic around a railway project. It does not duplicate the physical deployment sequence, product selection or project-reference record. The objective is to keep technical authority, CBP coordination and customer/project responsibility distinct as the engagement moves forward.
Five transitions that should remain explicit.
Operating need → technical requirement
Define what the railway must accomplish before a manufacturer or product is positioned.Control: customer need + CBP requirement coordination
Requirement → manufacturer solution
The relevant manufacturer confirms technology capability, configuration limits and technical documentation for the application.Authority: manufacturer / design owner
Technical route → procurement commitment
Commercial scope, exclusions, documentation, interfaces and acceptance basis should be explicit before an order is treated as execution-ready.Control: contracting parties + procurement framework
Supply → site deployment
Site readiness, installation responsibility, utilities, civil interfaces, training and commissioning must follow the actual contractual scope rather than assumptions created earlier in the project.Control: project responsibility matrix
Commissioning → operation & lifecycle support
FAT, shipment, installation, SAT, acceptance and current operation are separate states. Support, spares, calibration and warranty follow the state actually reached.Control: documented project stage
Coordination does not transfer technical authority.
CBP coordinates the Indonesian project interface according to the applicable principal and project scope. Manufacturer engineering authority, customer acceptance authority and contractual responsibilities remain where the governing documents place them.
VIEW DEPLOYMENT SEQUENCE