Results

Build on what we have.

WCO Data Protocol covers 148 countries and 98% of all global trade.

Customs agencies follow this protocol as part of their regulatory process.

All carriers, NVOCC, Customs Brokers, Terminals, and Bonded Facilities are part of both the regulatory standard and the network.

This is a foundation but we need more

Bryn Heimbeck

CEO at TradeTech

Data Standardization

Next Steps

Standard exchange maps

Need a central accessible repository for next standard data

Known Entities (Importers / Exporters)

Remaining Core Reference Data above and beyond Customs Data Set

Various system contributors can be tied in

​

Bryn Heimbeck

CEO at TradeTech

Data Standardization

Recommendations

We need an on-going active working group

We need to continue this discussion and not wait until next year

We need JOC / S&P’s continued leadership on spreading the word and bringing in others to this discussion and development of a working model we can all share.

Bryn Heimbeck

CEO at TradeTech

Data Standardization

Big Findings

• Right people, Right seats - feel out the expertise, but gauge for competency
• Customer-centricity - No longer an option. Need to understand from their seat, deeply, and with some level of authority/expertise.
• Be the Pilot - Control. Always stay in the “driver seat,” esp with BIG clients & stay true to your own product, and venture too. Control the venture outcome. Leverage change management.
• Growth - comes in all shapes, and sizes, and is ultimately dependent on tons of factors (many of which are out of your control). Lots of luck and market timing involved.
• Product Distribution - Dependent on your own business, tools & tech stack matter. Acquisition channels + sales approach will vary. Think in terms of the client’s commercial experience (i.e. sales process, marketing, etc.)

Miles Varghese

Chief Growth Officer at CargoLogik

Growth Models

Summary

Current situation of the industry:

1. Murky definition on data ownership - Hard for “data consumer” to prove every data owner.
2. Incentive for adoption on data sharing is not clear.
3. Multiple “sources” of truth

Suggestions:

1. Standards should be driven by non-for-profit.
2. Data should be paid for use only.
3. A framework on data ownership for the industry could be a good direction.

Edmund To

CTO at GSBN

Document & Data Ownership

Startup to Growth Stage Overall Theme

Eric Green

COO at Chain.io

Scaling from Startup to Growth Stage

STARTUPS = Solving a Problem

​

GROWTH = Predictably Solving It Over and Over

​

PREDICTABILITY = Product + People + Process

Product Discussion Points

Eric Green

COO at Chain.io

Scaling from Startup to Growth Stage

• Find a common denominator of a problem
• Minimize early "tech debt" save a lot of time and money in the future
• Think through the UX of data
• When building a product focus areas include: (i) agility; (ii) data integrity; (iii) interoperability; and (iv) automation
• Startups say "yes" to every request | growth often requires a "no"
• Product marketing to logistics companies takes specific expertise

People & Process Discussion Points

Eric Green

COO at Chain.io

Scaling from Startup to Growth Stage

• People
• When scaling in new markets, get an expert to supplement the product, i.e. not all markets are the same
• In current capital markets, align the team on a path to profitability and capital efficiency
• Process
• Focus on internal and external change management - See John Kotter link in Resources
• Build internal process and incentives to motivate internal teams to best serve clients

Resources

Dave Kellogg�SaaS Metrics Syllabus

​

Scale Venture Partners

Metrics

​

OpenView Venture Partners

2022 Report�PDF Version

Initialized Capital – Series B Scorecard

Downturn Edition

​

KeyBanc SaaS Survey

Private Companies

​

John Kotter - 8 Steps for Leading Change

Website

Eric Green

COO at Chain.io

Scaling from Startup to Growth Stage

Eric Green

COO at Chain.io

Scaling from Startup to Growth Stage

Eric Green

COO at Chain.io

Scaling from Startup to Growth Stage

System Security Summary

• Cybersecurity should have its own session(s) in the conference agenda
• Best practice resources should be made available for all levels of consumption
• Consider a failfest session broadly and with elements of cybersecurity for learning purposes
• Share how to market the value of your organizations investment in cybersecurity
• Share how to secure API’s. This could be a conference session
• Best practice backup/recovery methods

John Talieri

CTO at NMFTA

System Security

Informational Links

• https://nmfta.org/cybersecurity/
• https://www.cisa.gov/
• https://staysafeonline.org/
• https://resources.infosecinstitute.com/topics/threat-hunting/
• https://attack.mitre.org/
• https://www.nist.gov/cyberframework
• https://www.ncsc.gov.uk/collection/supply-chain-security/supply-chain-attack-examples

John Talieri

CTO at NMFTA

System Security

Quick Product Links (Not endorsed)

• https://delinea.com/products/secret-server (Privileged Access Management)
• https://umbrella.cisco.com/
• https://arcticwolf.com/
• https://www.okta.com/
• https://www.proofpoint.com/us
• https://www.crowdstrike.com/

​

John Talieri

CTO at NMFTA

System Security

Product Development Best Practices

• Build security into the design (Partner with your team, vendors, and partners)
• Password management (MFA)
• Access Control (Role-based and segregation of duties)
• Error Handling and Logging (Tie in SOC)
• System Configuration (Validate & lock down)
• Secure updates/patch management and validate
• End-to-End security testing of code, products, and overall architecture
• Penetration testing
• Integrate with overall security architecture and best practices

​

John Talieri

CTO at NMFTA

System Security

Thank you

More resources available:

https://www.sitetrax.io/devcon2023