Optical payload removal and refit with a connector discrepancy

ESV-S01-SOP-01   Payload satellite   Simulation procedure



Remove and refit the optical payload during an unpowered ground-integration rehearsal. Resolve a conflicting connector instruction before releasing the harness and mount, then prove that the final configuration matches the approved starting state.

Use this procedure to author and assess a controlled simulation with the Payload satellite model, version 5. This is a concept-model training exercise. It does not authorise real hardware work or establish flight qualification.

Before the exercise

Load the saved version 5 scene. The scenario owner supplies the harness map, isolated-power evidence, ESD condition, supported and parked poses, removal path and assessment tolerances. Keep a separate fixture root. No real hardware is energised.

Identity and provenance: ESV-S01-SOP-01 · S01 · model v5 · 25 October 2026

Explore the model and related procedures: https://eonspaceventures.com/models/#s01

1 Establish the task configuration

Model labels: bus, base, optics

Match the spacecraft, fixture and optical payload to the saved version 5 starting configuration. Select the three correct objects and save the baseline pose.

Check: Proceed only when all three identities and the task revision agree.

2 Secure the ground support

Model labels: base, foot_rf, foot_lf, foot_rr, foot_lr

Confirm all four support locations and put the simulated work package into the secured-fixture state. Keep the fixture independent of the spacecraft.

Check: A missing or misidentified support prevents the removal sequence.

3 Establish the unpowered work state

Model labels: conn_ru, conn_rl, conn_lu, conn_ll

Identify all four connector positions and acknowledge the scenario's power-isolated and ESD-ready condition before disconnecting anything.

Check: Power state is supplied by the scenario or an instrument record; the mesh does not prove it.

4 Trace the intended harness

Model labels: conn_ru, cable_r, cable_r_sleeve

Follow the training-defined right harness from its connector to the optical payload. Compare the actual connector identity with the task card.

Check: This fictional exercise maps the harness to conn_ru; an actual programme supplies its own mapping.

5 Catch the planted discrepancy

Model labels: conn_ru, conn_rl, cable_r_head_clip

Present a task card calling for the lower connector while the approved training configuration calls for the upper one. Learner must place a hold, capture both identities and request the reviewed correction.

Check: Continuing with the lower connector is a critical error. The approved branch corrects the task card and resumes from this checkpoint.

6 Open the access area

Model labels: optic_hatch_r, optics, cable_r_head_clip

Select the right optical access cover, expose the cable retention area and identify the retaining clip. Use a declared detachable-cover animation if hinge travel has not been established.

Check: Do not infer an engineered hinge axis or open the opposite-side cover.

7 Release the harness in sequence

Model labels: cable_r_head_clip, cable_r_sleeve, cable_r, conn_ru

Release the simulated retention, disconnect the reviewed connector and move the right harness into the defined stowed position.

Check: Record the selected parts and sequence; prevent pulling the payload while the harness remains connected.

8 Support and remove the optical payload

Model labels: optics, S01-PMI, bus

Set the supported-payload hold point, release the payload mount interface and withdraw the optical assembly along the authored removal path into its parked pose.

Check: The mount cannot be released before the support acknowledgement. Fastener-level actions require separately addressable fasteners; do not invent them.

9 Refit to the correct interface

Model labels: S01-PMI, optics, bus

Return the optical assembly to its saved baseline pose and align its mount interface with the bus. Reject a reversed or incomplete seating state.

Check: Assess against declared simulation pose tolerances, not unsupported flight alignment claims.

10 Restore the harness and retention

Model labels: conn_ru, cable_r, cable_r_sleeve, cable_r_head_clip

Reconnect the correct connector, restore the harness route and sleeve position, and re-engage retention in the reviewed order.

Check: The lower connector remains a decoy. Missing retention or the wrong route prevents completion.

11 Close and verify clearance

Model labels: optic_hatch_r, solar_r, solar_l, objective

Restore the access cover. Check the harness/cover against both folded arrays and keep the objective in the no-contact zone.

Check: Use reviewed geometric envelopes where available; visual appearance alone is not a clearance measurement.

12 Demonstrate completion and hand over

Model labels: S01-PMI, optics, conn_ru, cable_r_head_clip, base

Compare final and baseline configuration, review the discrepancy/recovery record and submit the evidence package for the next engineer.

Check: Record identity, order, positions, hold resolution and required external test records. Do not infer torque, electrical continuity or powered performance from video alone.

Assessment and completion

Score component identification 25, sequence 20, discrepancy handling 20, restored configuration 20 and evidence handover 15. Wrong-connector continuation, unsupported payload release or work before power-state confirmation prevents completion. Preserve both the original discrepancy and the accepted recovery.

Authoring and headless handoff

Bind the optics assembly, its cover, harness and mount to their actual component IDs. Configure supported, disconnected, parked, seated and retained states. Use declared detachable-cover and removal transforms; do not infer hinge travel or fastener-level actions from the mesh. Instrument results remain explicit scenario evidence.

Reuse the exact GLB and component identifiers above. Verify the supported Genesis import and binding path; the current Creator scene driver can generate a different model. This document and its JSON describe authoring intent, not completed interactions. Preserve one model revision and record actual lesson, job and review identifiers during execution.
