Contractor & Site Interface Documentation

Contractor governance and the operational interface between parties sharing a work area

This section covers the Contractor and Site-Interface Management application specifically. For how the interface works in general (lists, forms, navigation, deletion), see the Framework Guides above.

In This Section

• Application Overview — what the app models and why
• Quick Reference — menu map, demo codes and statuses
• System Diagram — the data model mapped, with an interactive pan/zoom viewer

The Application in One Paragraph

CSIM governs what happens when more than one organisation works the same ground. A contractor is prequalified into a ContractorProfile, engaged through a Contract, and does bounded work under a WorkPackage with a place, a period, a site representative and a contractor supervisor. Subcontractors are disclosed rather than hidden. Where two packages overlap — in area, in time, in energy, or in a load path — an InterfaceRegister entry records the interaction, its InterfaceHazards and the InterfaceControls that manage them, each with an owner, a performance requirement and a verification frequency. People are mobilised only once competency, induction and access line up; contractor plant is separately approved for the site. FieldAssuranceEvents then test in the field whether those controls actually hold, producing AssuranceFindings that may escalate to a StopWorkEvent, sit alongside an Incident, and resolve through CorrectiveActions — which also flow from a periodic ContractorPerformanceReview. The package ends with a Demobilisation handover.

Design boundary. This app supports contractor-interface governance and evidence. It does not replace procurement/ERP, HR/payroll, physical access control, statutory appointments, permit systems, the CMMS or the mine safety management system — those stay authoritative, and the *_reference fields throughout carry their handles.