# Start with the Mobile-ID ecosystem

Turn a business requirement into a reading path, component selection and a test plan.

Conceptual and implementation-planning guidance

## Start with a specific outcome

Describe one case from creation to completion. What does each participant do, which system owns the data and where is the outcome checked? A specific request such as moving a contract from a CRM to a signer and returning the completed file is more useful than a product name alone.

Separate the business application from digital infrastructure. The customer system may continue to own the case while relevant Mobile-ID components are considered for identity, signing or payment tasks. Discovery establishes the actual scope.



## Read according to your role

Managers need outcomes and responsibilities. Architects need system boundaries and dependencies. Developers need the applicable specification. Operations needs traceability and incident procedures. The same workflow therefore calls for different documentation layers.

A brochure describes capabilities, a datasheet describes a model, an operating guide explains actions and an API specification defines data exchange. Choose the right resource type before discussing implementation.

- Business: objectives, users and a representative case.
- Engineering: systems, environments and versions.
- Operations: roles, updates, logs and support.

## Prepare discovery inputs

A concise discovery pack includes the current workflow, a sample without sensitive data, participating systems and technical contacts. Identify the developer of each system and its available integration interfaces.

Separate mandatory requirements from options. Environment, retention, access and processing-time requirements need confirmation with the implementation team; examples in overview material are not commitments for every project.



## Define a testable pilot

Select a small journey that can be tested end to end. Agree inputs, outcomes, failure cases and who validates each step. A complete pilot is more informative than disconnected successful actions.

Discovery should produce a scope, participating components, applicable documentation, responsibilities and a test plan. Keep these decisions alongside system versions so changes remain traceable.



Source document:
- TSA timestamping component overview: https://docs.mobile-id.vn/trustedhub/Trusted%20Hub%20TSA%20Appliance%20Brochure.pdf
- GoPaperless workflow overview: https://docs.mobile-id.vn/GoPaperless/Brochure_Datasheet/Brochure_GoPaperless_20250819.pdf

https://knowledge.mobile-id.vn/en/knowledge/getting-started/