Level 1 — Candidate Brief: Pinnacle Marine Ltd¶
About this exercise¶
This is your Level 1 configuration exercise. You will set up a complete, working configuration for a fictional client — Pinnacle Marine Ltd — in your local Send PDE environment. You will build everything from scratch using the base repository as your starting point, following the configuration standards you have been taught.
By the end of this exercise you must be able to demonstrate a full submission flowing from creation through to bind in your PDE.
What you need before you start¶
- [ ] Access to the base repository (raise a request with your trainer if not already set up)
- [ ] Your Send PDE running locally
- [ ] Access to the Send Workbench at
http://localhost(or your configured local port) - [ ] The Configuration Standards page open for reference
- [ ] The New Client Setup Guide open for reference
Standards apply
Your completed configuration will be assessed against the configuration standards. Any Critical-severity violations will result in an automatic fail regardless of whether the PDE demonstration works.
Client Profile¶
| Field | Value |
|---|---|
| Client name | Pinnacle Marine Ltd |
| Client code | pinnacle |
| D&B DUNS number | urn:duns:724891035 |
| Country of operation | United Kingdom |
| Primary currency | USD |
| Business type | Open Market only |
| Placement type | Direct broker submissions |
Line of Business¶
Pinnacle write a single class of business at this stage:
| Field | Value |
|---|---|
| Class name | Marine Cargo |
| Type code | MC |
| Sub-classes | CARGO, STOCK_THROUGHPUT |
The Underwriter's Workflow¶
Pinnacle's workflow is intentionally straightforward for this exercise. There is no referral step and no rating integration — premium is entered manually by the underwriter.
The steps in order are:
- Sanctions check — automatically run against the insured name when a new submission is created
- Structured quote — the underwriter reviews the risk, enters a premium manually, and marks the submission as quoted
- Bind — the underwriter confirms the risk is bound
There is no appetite check, no referral, and no external integrations at this stage.
Submission Form Fields¶
The following fields must appear on the submission form. All fields are mandatory unless marked optional.
| Field Label | Field Type | Notes |
|---|---|---|
| Insured Name | Text | Mandatory |
| Broker Name | Text | Mandatory |
| Inception Date | Date | Mandatory |
| Expiry Date | Date | Mandatory — must be after inception date |
| Sub-class | Dropdown | Options: Cargo, Stock Throughput |
| Country of Origin | Text | Mandatory |
| Country of Destination | Text | Mandatory |
| Sum Insured | Currency (USD) | Mandatory |
| Description of Cargo | Text area | Mandatory |
| Conveyance Type | Dropdown | Options: Air, Sea, Road, Rail |
| Open Cover Reference | Text | Optional |
| Underwriter Notes | Text area | Optional |
Roles and Authority¶
Three roles must be configured. All roles can view any submission. Bind authority is enforced by the platform.
| Role Name | Can Create | Can Quote | Bind Authority |
|---|---|---|---|
| Underwriting Assistant | Yes | No | None — cannot bind |
| Underwriter | Yes | Yes | Up to USD 250,000 sum insured |
| Senior Underwriter | Yes | Yes | Up to USD 2,000,000 sum insured |
Documents¶
Two documents must be generated at the following points in the workflow:
| Document | Trigger Point | Recipient |
|---|---|---|
| Quote Slip | When the submission status moves to Quoted | Internal only (stored on submission) |
| Policy Schedule | When the submission is bound | Internal only (stored on submission) |
For this exercise, the document templates do not need to be fully designed. They must include at minimum:
- Client name and logo placeholder
- Insured name (from submission data)
- Inception and expiry dates (from submission data)
- Sum insured (from submission data)
- A placeholder clause section
Environments¶
For this exercise you are configuring local / PDE only. You do not need to produce a DynamoDB specification for DevOps.
Your local PDE configuration (pde.dev.json, which stands in for be_config.json in the Docker stack) should be configured for local use with the DUNS number provided above.
Deliverables¶
When you are ready to be assessed, you must be able to demonstrate the following in your PDE:
- Create a new Marine Cargo submission as an Underwriting Assistant user — confirm the sanctions check runs automatically
- Log in as an Underwriter and quote the submission with a sum insured of USD 150,000 — confirm the Quote Slip is generated
- Attempt to bind the submission as an Underwriting Assistant — confirm the platform prevents this
- Bind the submission as an Underwriter at USD 150,000 — confirm the Policy Schedule is generated and the submission reaches bound status
- Create a second submission with a sum insured of USD 1,500,000 — confirm an Underwriter cannot bind it but a Senior Underwriter can
You must also provide your configuration files for review.
Assessment Criteria¶
Your configuration will be reviewed against the following. Each item maps to a standard in the Configuration Standards.
| Area | What will be checked |
|---|---|
| Repository structure | All base repository files not applicable to Open Market have been removed |
| be_config.json | DUNS number correct, no credentials present, at least one role defined |
| Business class | MC type code, correct sub-classes, coverages match the brief |
| Action file naming | Follows mc-open-market-actions.json convention |
| Pipeline order | Sanctions check is first or second step |
| Lifecycle coverage | Quote and bind pipelines both defined |
| Authority limits | Enforced at bind for each role in USD |
| Document generation | Both documents triggered from pipeline steps |
| Config domain | No environment-specific values hardcoded in any S3 file |
Good luck.