Collaboration measurement worksheets

Use these five blank templates to prepare a discussion. They contain headers only, no customer data. Keep customer identifiers, addresses and evidence files in the approved private system; use internal references in working copies.

Event records

collaboration-event-log.csv separates occurrence, source recording and partner receipt times. Store an explicit UTC offset in each timestamp. local_event_offset describes the event location and must not override an already unambiguous timestamp. A missing time produces an unresolved interval, not zero minutes. recordTime in EPCIS has a specific repository meaning; the worksheet's fields are proposed study fields, not an EPCIS capture payload.

collaboration-event-mapping.csv records the meaning and object level of an original status. Physical receipt, inventory posting and permission to sell may require different events. Agree a version and evidence basis. Do not substitute a warehouse status for USPS acceptance without the relevant postal evidence.

Stock differences

collaboration-count-review.csv requires one stock boundary and consistent units. If the snapshot and count refer to the same population, expected_at_comparison equals recorded_quantity plus evidenced boundary receipts minus evidenced boundary departures. Internal moves within that boundary and allocation-only reservations do not change its physical total. Prevent double counting of movements. Reconcile posting differences before using the formula; a stock state that excludes quarantine has a different boundary.

signed_difference equals first_count_quantity minus expected_at_comparison. absolute_difference equals its absolute value. Sum absolute quantities only within a comparable unit group. Keep the initial count, recount and approved adjustment separate. Do not average item-level percentages without identifying the intended weighting and zero expected quantities.

Trial measures and decisions

collaboration-pilot-measures.csv records the selection rule, grouping factors and mutually exclusive outcomes. State whether eligible_count is before or after exclusions. Recommended convention here: eligible_count is after documented exclusions; successful, unsuccessful, unknown and not-yet-due counts sum to eligible_count. A completed-only proportion describes its own denominator; it cannot silently replace the all-eligible view.

collaboration-pilot-decision.csv connects observed work with charges, unresolved exceptions and a proposed next action. decision_proposed and decision_confirmed are separate fields. Targets, sample size, authority and changes of scope require the actual project agreement. These templates do not certify a service result or execute stock adjustments.