Discover

This is a Sample Heading (size 3, custom color #174AB6 from the UI guide)

This is the text. (paragraph 2) in black

The section color scheme is Light 2

This is a Sample Heading (size 3, custom color #174AB6 from the UI guide)

This is the text. (paragraph 2) in black

The section color scheme is Light 2

Divider added to bottom, bright blue, size M - use this style if above the footer

This is a Sample Heading (size 3, custom color #FFE00D from the UI guide)

This is the text. (paragraph 2) in white

Note: the section color scheme is Dark1

This is a Sample Heading (size 3, custom color #FFE00D from the UI guide)

This is the text. (paragraph 2) in white

Note: the section color scheme is Dark1

Divider added to bottom, bright blue, size M - use this above the footer

Learning and Awareness: (heading size 3)

  • Intelligent Autonomy 101 seminar/workshop:

    • What is an Autonomous System and what makes something autonomous

    • How AI and Machine Learning make It more capable and resilient

    • Explore existing candidate applications and Use Cases that may shed light on what your organization could do

  • We will be learning about your organization and its vision, goals, processes, workers, customers, suppliers, etc.

    • Conduct knowledge exchange sessions and/or interviews

    • Review documents and other materials that you provide

  • Evaluate your IAS readiness

  • Play the “Pain Game” (aka “What keeps you up at night?”)

  • Brainstorm Company-specific Use Cases

  • Assess your competition’s use of IAS

  • Explore and evaluate IAS products that might supply some or all of your needs

Explore touchpoints and Interactions with people and other systems: (heading size 4)

  • Who are the users and maintainers?

  • Who will be operating the intelligent autonomous system?

  • Who provides and receives its information and data?

  • What are the outside influencers, such as Regulators (especially for autonomous aircraft), Standards bodies, Insurers, and Unions?

  • What are the relevant software applications and cloud or local data repositories that potentially produce or provide information needed by the IAS and/or that potentially consume or store information produced by the IAS?

  • What are the physical systems, such as machinery, cameras and other sensors, that similarly need to interact with the IAS?

Scope out a notional (or “rough”) solution (heading size 4):

  • Lay out a recommended conceptual design of the AIS solution that captures the:

    • Desired features, capabilities, tasks, and behaviors

    • Desired human and system interfaces

    • Desired performance, precision, and safety goals

    • Desired degree of human oversight/involvement/interaction

    • Desired degree of interaction with other physical infrastructure, systems and machinery (e.g, is it acceptable to introduce markings on the floor/road or walls to help the IAS confirm its position and orientation?)

    • Applicable high-level restrictions or constraints

    • Applicable policies or organization-specific regulations that must be followed

  • Assess AIS applicability and its potential cost-benefit-risk and ROI

  • Assess Buy-Build-Blend solution options

  • Flesh out the Design and Deployment strategy (Most clients prefer a crawl-walk-run approach):

    • Do we need a Proof-of-Concept Prototype?

    • Do we need a Demonstration Prototype?

    • Do we need a Pilot Prototype?

    • Do we go straight to the full solution?

  • Document our results and recommendations in a Scoping Study document for client review and distribution