Site stores, issues and the phone app
You will be able to: Explain the guards on issues to a breakdown item; Describe returns, transfers, damage and local purchases; State how phones are enrolled, trusted and synchronised.
- Read not done yet
- Self-check: not taken not done yet
- Lesson complete not done yet
Every issue, return, transfer and write-off on site is an ordinary stock document with its project and breakdown item. The Project stores screens only make the project work quick to enter. Choose the project first.
| Movement | Rule |
|---|---|
| Issue to an item | Issues from the store to the item at the stock value. Above the BOQ quantity it needs a reason and an approver. The store cannot go negative when the stock policy blocks it. |
| Return to store | Brings material back at the cost it left at, never above what was issued |
| Transfer between stores | May go through a transit store; the receiver cannot confirm more than was sent |
| Damage | A damage report posts the wastage and can raise a back-charge |
| Local purchase | One-step purchase invoice; the payer is petty cash, cash advance, card or supplier credit; a voucher over the limit needs an approver |
A reservation for another project can block an issue: if the quantity on hand less the quantity needed would go below what is reserved for others, the issue is refused for the part reserved.
The phone app
A phone enrols itself the first time its user opens the mobile app. It then waits. Nothing it holds is accepted until an administrator approves it, choosing a trust level, the roles it may open and the projects it receives. The roles are site engineer, gate, inspection, storekeeper, HSE, assets, procurement and project manager.
- Basic trust sends site records only. Standard adds approvals. Full adds the records that post to stock and the ledger.
- A record made on a phone shows a temporary number until the office accepts it. The real number then replaces it.
- If a phone and the office both changed a record, it appears under Sync conflicts. Quantities are never merged automatically.
- A lost phone is marked lost and ordered to erase its data at its next contact. Records still on the phone that were never sent are lost.
Walk it through
- Compute how much of an issue is above the BOQ for an item of your own.
- List who on your site needs which phone role.
- In the demo, open Project stores and see the Issue and Return to store buttons.
Public demo company, sign in as admin / demoAdmin123. Data refreshes nightly.
- Issues above BOQ need a reason and an approver.
- Returns come back at the cost they left at, never above what was issued.
- A phone is trusted only after an administrator approves it.
Check yourself
4 questions on this lesson. Not timed, not the exam, and you can try again. Score 60% or more, and read the lesson, to complete it.
1. An issue above the BOQ quantity of an item needs:
2. A new phone can send records as soon as its user opens the mobile app, before anyone approves it.
3. BOQ 1,000 bags, 960 already issued, 60 requested. By how much is the issue above BOQ?
4. Which are true about returns, transfers and phone sync?
Select all that apply.