{"id":109,"date":"2026-01-13T16:18:27","date_gmt":"2026-01-13T15:18:27","guid":{"rendered":"https:\/\/essentos.com\/en\/news\/?p=109"},"modified":"2026-01-13T16:18:27","modified_gmt":"2026-01-13T15:18:27","slug":"news-essentos-tos-container-centric-c-core","status":"publish","type":"post","link":"https:\/\/essentos.com\/en\/news\/news-essentos-tos-container-centric-c-core\/","title":{"rendered":"Essentos puts the container at the center of operations and accelerates efficiency"},"content":{"rendered":"\n

In many facilities, operations run one way and software runs another. Essentos is a TOS<\/strong> that closes that gap with a simple, demanding idea: The container is the center<\/strong> and everything else organizes around it. That approach is not an add-on or a separate bundle. It\u2019s a design philosophy<\/strong> we call C-CORE<\/strong> (Container-Centric Orchestration, Rules & Evidence<\/em>), the invisible foundation we used to build Essentos so day-to-day work becomes predictable, traceable, and measurable.<\/p>\n\n\n\n

Result:<\/strong> Less dwell, fewer reattempts, fewer penalties, and fewer minutes in line, without swapping hardware and while leveraging what you already have.
<\/p>\n\n\n\n

What does it mean to put the container at the center?<\/strong><\/h2>\n\n\n\n

It means people, processes, and data<\/strong> treat the container as the unit of truth<\/strong>, and the physical<\/strong> and documentary<\/strong> states move forward together. When that happens, noise drops and available capacity per shift rises.<\/p>\n\n\n\n

    \n
  • Dwell:<\/strong> The time a container remains idle between two relevant milestones inside the facility. Reducing dwell frees space and lowers demurrage\/detention risk.<\/li>\n\n\n\n
  • Truck Turn Time (TTT):<\/strong> Minutes from truck gate-in<\/strong> to gate-out<\/strong>. Lower TTT prevents congestion and improves the driver experience.<\/li>\n\n\n\n
  • Orchestration:<\/strong> Processes turned into clear tasks<\/strong> with prerequisites<\/strong>, defined ownership, and closure with evidence.<\/li>\n\n\n\n
  • Evidence:<\/strong> Photos, reads, weights, signatures, license plates, and user\/device\/time\/location stamps per event. Without evidence, there\u2019s no traceability.
    <\/li>\n<\/ul>\n\n\n\n

    What is C-CORE and why does it matter if it\u2019s \u201cinvisible\u201d?<\/strong><\/h2>\n\n\n\n

    C-CORE<\/strong> is the operating philosophy<\/strong> that guides how we design and configure Essentos TOS<\/strong>:<\/p>\n\n\n\n

    Container-Centric Orchestration, Rules & Evidence<\/strong> = Container, Orchestration, Rules, and Evidence.<\/strong><\/p>\n\n\n\n

      \n
    • It is not a product<\/strong> and not a \u201cspecial mode.\u201d<\/li>\n\n\n\n
    • It is not a separate process<\/strong> you \u201cswitch on.\u201d<\/li>\n\n\n\n
    • It is the way we think and build<\/strong> Essentos so every decision starts from the container, executes with simple rules<\/strong>, and leaves minimum required evidence<\/strong>.<\/li>\n<\/ul>\n\n\n\n

      That \u201cinvisible software\u201d creates real advantage: Less friction<\/strong>, Self-validating data<\/strong>, and KPIs<\/strong> that reflect what actually changes the shift. Other systems can copy screens; copying a design philosophy<\/strong> is a different league.
      <\/p>\n\n\n\n

      C-CORE Principles<\/strong><\/p>\n\n\n\n

        \n
      1. Container first:<\/strong> Every decision starts from its real status.<\/li>\n\n\n\n
      2. Simple orchestration:<\/strong> Short checklists, clear prerequisites, visible ownership.<\/li>\n\n\n\n
      3. Exit-oriented rules:<\/strong> Placement, pre-staging, and sequencing look to the next milestone.<\/li>\n\n\n\n
      4. Minimum required evidence:<\/strong> Just what adds value, no bureaucracy.<\/li>\n\n\n\n
      5. Continuous measurement:<\/strong> KPIs that matter for ops and customers, not vanity metrics.
        <\/li>\n<\/ol>\n\n\n\n

        Essentos functionalities aligned with C-CORE<\/strong><\/h2>\n\n\n\n
          \n
        • Role-based orchestration<\/strong> with prerequisites:<\/strong> Valid documents, verified identity, available location, active time window.<\/li>\n\n\n\n
        • Pre-validations<\/strong> before gate and before handoff to avoid in-yard rejections and recirculation.<\/li>\n\n\n\n
        • Evidence capture (automatic and manual):<\/strong> License plate and container reads, weights, condition photos, signatures, and geo-stamps.<\/li>\n\n\n\n
        • API\/EDI integrations<\/strong> with your TOS\/WMS\/ERP\/PCS, scales, and readers already in place.<\/li>\n\n\n\n
        • Exception handling<\/strong> with assignment, guided action, and traceable closure.<\/li>\n\n\n\n
        • Weekly improvement loop:<\/strong> Adjust rules based on incidents and KPIs.
          <\/li>\n<\/ul>\n\n\n\n

          What if you\u2019re running another TOS today?<\/strong><\/h2>\n\n\n\n

          We don\u2019t force cold cuts. Essentos coexists and integrates<\/strong> with your current TOS to test, measure, and de-risk<\/strong>. Once the team sees improvements and ROI, migrating to Essentos<\/strong> stops being a leap of faith and becomes a financial and operational decision<\/strong>.<\/p>\n\n\n\n

          Low-risk migration path<\/strong><\/p>\n\n\n\n

            \n
          1. Discovery:<\/strong> Mapping of critical flows.<\/li>\n\n\n\n
          2. Light integration:<\/strong> States, events, and evidence.<\/li>\n\n\n\n
          3. Controlled parallel:<\/strong> Two flows with shared KPIs.<\/li>\n\n\n\n
          4. Phased cutover:<\/strong> By process families on low-load days.<\/li>\n\n\n\n
          5. Adoption:<\/strong> In-field training and rule review.<\/li>\n<\/ol>\n\n\n\n

            Typical outcome:<\/strong> Fewer redundant licenses, Lower<\/strong> support cost, Faster<\/strong> change velocity, and an operation that doesn\u2019t break<\/strong> when rules need adjusting.
            <\/p>\n\n\n\n

            Measurable examples your team can verify<\/strong><\/h2>\n\n\n\n

            1) Urban depot with high rotation<\/strong><\/p>\n\n\n\n

            Context:<\/strong> Capacity 1,200 TEU; 80% average occupancy; 3.2 days dwell.<\/p>\n\n\n\n

            Action with Essentos:<\/strong> Exit-oriented placement rules, prerequisites before release, evidence at handoff.<\/p>\n\n\n\n

            Result:<\/strong> Dwell 2.6 days<\/strong> after 45 days.<\/p>\n\n\n\n

            Calculation:<\/strong> 0.6 days \u00d7 960 TEU average occupancy = 576 TEU-days<\/strong> returned to the cycle per week.<\/p>\n\n\n\n

            Translation:<\/strong> More usable slots without expanding the yard<\/strong> and lower penalty exposure.<\/p>\n\n\n\n

            2) Intermodal ramp with uneven queues<\/strong><\/p>\n\n\n\n

            Context:<\/strong> TTT avg 62 min; 90th percentile<\/strong> 94 min; first-attempt success 71%.<\/p>\n\n\n\n

            Action:<\/strong> Gate prerequisites, 30-minute appointments, document checklist before opening the work order.<\/p>\n\n\n\n

            Result:<\/strong> TTT avg \u201318%<\/strong> (51 min), p90 \u201322%<\/strong> (73 min), first-attempt success +12 pp<\/strong>.<\/p>\n\n\n\n

            Impact:<\/strong> 300 trucks\/day \u00d7 11 minutes saved = 55 hours<\/strong> of waiting removed per day.<\/p>\n\n\n\n

            3) Yard with high rehandles<\/strong><\/p>\n\n\n\n

            Context:<\/strong> 0.7 rehandles per useful move; 400 moves\/shift.<\/p>\n\n\n\n

            Action:<\/strong> Exit-oriented rules and pre-staging by train or pickup window.<\/p>\n\n\n\n

            Result:<\/strong> 0.7 \u2192 0.4<\/strong> rehandles.<\/p>\n\n\n\n

            Impact:<\/strong> 0.3 \u00d7 400 = 120 rehandles avoided<\/strong> per shift. At 2.5 min each, that\u2019s 300 minutes<\/strong> freed per shift.<\/p>\n\n\n\n

            4) Disputes on condition and timing<\/strong><\/p>\n\n\n\n

            Context:<\/strong> 28 disputes\/month; 9-day resolution; 42% favorable.<\/p>\n\n\n\n

            Action:<\/strong> Mandatory evidence by incident category and a disputes board with internal SLA.<\/p>\n\n\n\n

            Result:<\/strong> 28 \u2192 14<\/strong> disputes; 4-day<\/strong> resolution; favorable closures +20 pp<\/strong>.<\/p>\n\n\n\n

            5) Export with early train arrival<\/strong><\/p>\n\n\n\n

            Context:<\/strong> Train arrives 45 minutes early; last-minute maneuvers and gate queues.<\/p>\n\n\n\n

            Action:<\/strong> Pre-staging by train window, protected critical lanes, and time-slot alerts.<\/p>\n\n\n\n

            Result:<\/strong> \u201335%<\/strong> last-minute moves; on-time train +8 pp<\/strong>.<\/p>\n\n\n\n

            Every site has its unique reality and adaptation. The data above reflects some of our customers<\/strong> and how Essentos impacted their facilities.<\/p>\n\n\n\n

            How do we deploy Essentos under the C-CORE philosophy without stopping operations?<\/strong><\/h2>\n\n\n\n

            Week 1:<\/strong> Field discovery, baseline for dwell, TTT, reattempts, and disputes.<\/p>\n\n\n\n

            Week 2:<\/strong> Minimum viable rules and 5\u20137 step checklists. Light integration and live boards.<\/p>\n\n\n\n

            Week 3:<\/strong> Rule tuning by root cause. Mandatory evidence on key events. Time-window alerts.<\/p>\n\n\n\n

            Week 4:<\/strong> Consolidation and impact report: Dwell, TTT, reattempts, disputes, and penalties.<\/p>\n\n\n\n

            Data governance that makes improvement possible<\/strong><\/h2>\n\n\n\n
              \n
            • Controlled catalogs:<\/strong> Container types, incident categories, zones, and rejection reasons.<\/li>\n\n\n\n
            • No free text on critical fields:<\/strong> Customer, flow, milestone, status, exception reason.<\/li>\n\n\n\n
            • Trustworthy stamps:<\/strong> User, device, time, and location per event.<\/li>\n\n\n\n
            • Useful retention:<\/strong> Keep evidence long enough for audits and customer care.<\/li>\n\n\n\n
            • One visible state:<\/strong> Documentary and physical in the same view to avoid contradictions.<\/li>\n<\/ul>\n\n\n\n

              How do we design exit-oriented rules?<\/strong><\/h2>\n\n\n\n
                \n
              1. Identify the next dominant milestone<\/strong> per flow: Train, pickup, inspection, transshipment.<\/li>\n\n\n\n
              2. Define preferred locations<\/strong> and alternatives by compatibility, height, and safety.<\/li>\n\n\n\n
              3. Protect critical zones<\/strong> to avoid last-minute rehandles.<\/li>\n\n\n\n
              4. Set max stack heights<\/strong> by equipment and safety.<\/li>\n\n\n\n
              5. Measure the effect on rehandles and TTT<\/strong> by time band.<\/li>\n\n\n\n
              6. Adjust weekly by root cause<\/strong>, not intuition.<\/li>\n<\/ol>\n\n\n\n

                Exceptions: From signal to action<\/strong><\/h2>\n\n\n\n

                Practical taxonomy<\/strong><\/p>\n\n\n\n

                  \n
                • Documents:<\/strong> Releases, VGM, permits, restrictions.<\/li>\n\n\n\n
                • Identity:<\/strong> Invalid driver or license plate.<\/li>\n\n\n\n
                • Location:<\/strong> Safety, height, or rack incompatibility.<\/li>\n\n\n\n
                • Time window:<\/strong> Out-of-range appointment or early train.<\/li>\n\n\n\n
                • Inspection:<\/strong> Hold or condition detected.<\/li>\n<\/ul>\n\n\n\n

                  Standard response<\/strong><\/p>\n\n\n\n

                    \n
                  • Assign to a role, short checklist, and minimum evidence.<\/li>\n\n\n\n
                  • Time limit and block the next milestone.<\/li>\n\n\n\n
                  • Close with root cause and learning to prevent recurrence.<\/li>\n<\/ul>\n\n\n\n

                    KPIs Essentos watches from day one<\/strong><\/h2>\n\n\n\n
                      \n
                    • Dwell<\/strong> by flow family and zone.<\/li>\n\n\n\n
                    • TTT<\/strong> average and 90th percentile.<\/li>\n\n\n\n
                    • First-attempt success<\/strong> at gate.<\/li>\n\n\n\n
                    • Rehandles per useful move.<\/strong><\/li>\n\n\n\n
                    • Open disputes<\/strong>, days to resolution, and favorable closure rate.<\/li>\n\n\n\n
                    • Demurrage\/Detention<\/strong> by customer and root cause.<\/li>\n\n\n\n
                    • Effective occupancy<\/strong> and zone utilization<\/strong>.<\/li>\n\n\n\n
                    • On-time alert handling<\/strong> and SLA compliance<\/strong>.<\/li>\n<\/ul>\n\n\n\n

                      Frequently asked questions<\/strong><\/h2>\n\n\n\n

                      Does Essentos replace my current TOS on day one?<\/strong><\/p>\n\n\n\n

                      Not required. We can coexist<\/strong> with your current TOS, integrate states and evidence, measure impact<\/strong>, and migrate when it makes economic and operational sense.<\/p>\n\n\n\n

                      Do I need to change hardware?<\/strong><\/p>\n\n\n\n

                      No. We leverage your existing scales, readers, and equipment wherever possible.<\/p>\n\n\n\n

                      Who defines rules and checklists?<\/strong><\/p>\n\n\n\n

                      Your team and ours, together<\/strong>, in the field. We prefer six rules everyone follows to twenty nobody remembers.<\/p>\n\n\n\n

                      When will I see results?<\/strong><\/p>\n\n\n\n

                      Within 4 weeks<\/strong> you\u2019ll see reattempts and TTT trending down. Dwell reduction typically consolidates in 8 to 10 weeks<\/strong>.<\/p>\n\n\n\n

                      Ready to validate Essentos in your facility?<\/strong><\/h2>\n\n\n\n

                      We propose a 30-day Impact Trial<\/strong> on two operational flows. We walk the yard with your team, implement rules and evidence, and measure dwell, TTT, reattempts, disputes, and penalties<\/strong>.<\/p>\n\n\n\n

                      Essentos<\/strong> is the TOS. C-CORE<\/strong> is the philosophy that makes it perform.<\/p>\n\n\n\n

                      Everything around the container.<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"

                      Essentos is a TOS built on the C-CORE philosophy: Container-Centric Orchestration, Rules & Evidence. It aligns physical and documentary states to cut dwell, reduce rehandles, and shorten Truck Turn Time while leveraging your existing hardware and integrations.<\/p>\n","protected":false},"author":1,"featured_media":111,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[38,40,42,39,41],"class_list":["post-109","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-sin-categoria","tag-container-centric","tag-dwell","tag-evidence","tag-terminal-operating-system-2","tag-truck-turn-time"],"_links":{"self":[{"href":"https:\/\/essentos.com\/en\/news\/wp-json\/wp\/v2\/posts\/109","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/essentos.com\/en\/news\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/essentos.com\/en\/news\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/essentos.com\/en\/news\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/essentos.com\/en\/news\/wp-json\/wp\/v2\/comments?post=109"}],"version-history":[{"count":2,"href":"https:\/\/essentos.com\/en\/news\/wp-json\/wp\/v2\/posts\/109\/revisions"}],"predecessor-version":[{"id":112,"href":"https:\/\/essentos.com\/en\/news\/wp-json\/wp\/v2\/posts\/109\/revisions\/112"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/essentos.com\/en\/news\/wp-json\/wp\/v2\/media\/111"}],"wp:attachment":[{"href":"https:\/\/essentos.com\/en\/news\/wp-json\/wp\/v2\/media?parent=109"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/essentos.com\/en\/news\/wp-json\/wp\/v2\/categories?post=109"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/essentos.com\/en\/news\/wp-json\/wp\/v2\/tags?post=109"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}