elecsense.← Back to ElecsenseChoose your starting point.
Exploring the product? Start with the interactive allocation example. Select a dataset and compare the longest-first arrangement with the coordinated reassignment of cuts. The stock and cable demand stay the same. This website example uses illustrative data and makes no changes to a project.
Already invited? Log in to enter your assigned project or select among the projects available to you. Contact your Organization administrator if an expected project is missing.
Ready when: you know whether you are exploring sample data or working inside an assigned project.
Prepare the inputs for your stage.
Inside Cable Optimizer, choose the relevant stage and download the current Template. The product upload uses its supplied Excel workbook. Copy data into that workbook while retaining its structure and required fields.
- Cable demand: stable cable tags, matching specifications, required lengths, and relevant source, destination and route information.
- Pre-order planning: cable data, minimum and maximum drum lengths by cable type, and the applicable allocation rules. The drum sheet is ignored in this mode.
- Post-order allocation: cable data plus identified drums and trustworthy declared available lengths. Distinguish an original manufactured length from the length available today.
Check units, duplicate tags, cable specifications and outstanding commitments before running a calculation. Do not describe stock already promised to outside work as freely available.
Ready when: each cable and drum can be identified, lengths are in the intended units, and availability reflects the project's actual commitments.
Calculate, then inspect the result.
Complete the stage's inputs and settings, then run the calculation. A pre-order run explores drum requirements. A project post-order upload first opens execution preparation so that existing resources and proposed changes can be reviewed.
Follow the run's status. When the result is available, inspect its statistics, drum allocations and unresolved demand. Keep the retained inputs and downloadable Excel report with your review record; the history allows you to return to the same run.
For the nine-cable example, confirm that every required length is allocated exactly once. Four 1,000 m drums provide 4,000 m of stock. Meeting 2,960 m of demand leaves 1,040 m in total. The longest-first baseline checks every opened drum before opening another, yet uses all four. Reassigning several runs together uses three drums, leaving 40 m across those opened drums and one full 1,000 m drum unopened. Read the worked allocation comparison to reconcile every cut.
Ready when: you can explain the input assumptions, account for all required cable lengths and distinguish remaining stock from waste.
Prepare a revision with the work in view.
Review matches with existing cable and drum records before proposing a change. A deliberate revision needs a reason and confirmation. Issued, cut and progressed work stays protected; available capacity reflects physical stock, reservations and commitments outside the change.
Review shortages, holds and any stale-result message. A later field change can make a calculation unsuitable for release while its report remains useful review evidence. Follow the project's approval and release process before issuing work.
Ready when: the proposed change is clear, existing commitments are respected and the responsible engineer can explain the next authorized step.
Record the cut, then the progress.
Where operational PullCards have been issued, the field workflow connects the cable, assigned drum and authorized work. In Process PullCards, an authorized user accepts the work and records the measured actual cut when that action is available.
A valid confirmed cut updates the recorded drum balance. Record laying progress and notes separately: cutting and installation are different events. The card's history retains the sequence of work and updates.
If an entry exceeds the recorded physical balance, or a hold or reconciliation issue blocks the next action, contact the responsible engineer. A discrepancy should be corrected through the authorized record, rather than concealed in a different cut length. Additional cutting also requires the appropriate recorded authority.
Ready when: actual cuts, recorded stock and installation progress tell a consistent story.
Who does what?
Assign the people responsible for each part of the workflow. Access follows Organization membership, assigned projects and explicit permissions. Subcontractor users work with their own subcontractor's PullCards.
| Responsibility | What the team needs to establish |
|---|---|
| Plan and review | Who prepares cable data, runs calculations, reviews changes and approves the next step. |
| Direct field work | Who issues authorized PullCards and coordinates the assigned subcontractors. |
| Record cuts and progress | Which field users have the explicit permissions for their assigned work. |
| Reconcile stock | Who checks measurements and resolves corrections or disputed balances. |
| Manage team access | Who assigns permitted users and project roles within the agreed Organization and seat limits. |
A title alone does not grant a permission. The controls in your assigned workspace also depend on the current state of the work.
Prepare for a useful pilot discussion.
Bring these starting points:
- Your project's stage, a representative cable schedule and available drum stock.
- The allocation and jointing rules, and the way your team records drum locations.
- The people responsible for calculations, instructions, cuts and reconciliation.
- Required browsers, site connectivity, data-hosting expectations and any system integrations.
For an ongoing project, start with remaining unallocated cables and available stock. Exclude lengths already committed to outside work until those commitments are cleared. You do not need to recreate the project's entire field history to discuss this starting point.
Cable jointing and GPS-based drum location are part of the first customer release. The wider engineering suite and native mobile applications remain future capabilities.
Before sharing operational data, agree the pilot scope, access roles, onboarding steps, hosting arrangements and written data terms. Setup timing depends on data readiness and scope.