1. Licenses, Authorizations & Standards
20th Tuna Data Working Group
28th April 2017
Noumea, New Caledonia
Licenses, Authorizations & Standards

2. Overview Where are we now? Why are we doing what we’re doing?
How is this being done?
What does this mean?

3. Where are We Now?
We are in the process of developing open standards for all our future systems

4. Why? Carpenter Story Why is this?
Imagine you’re a carpenter. Trying to build a house. While your building the house, the plans keep changing for the house.
Added to that instead of just1 house, your building another 100 houses. All their plans are changing and each change is different for each house.
This is what the implementation of the IMS looks like
Why is this?
Strategy was customise to members needs.
Fine at the start when the IMS small. Not so good once you start growing.
Why? Members have their own Biases engrained in procedures, policies, legislation
Differences from member to member
Made more complicated as we transition to ER / EM. New technology requires new ways of doing things
Uncertainty > Complexity > Size & Scope
We need to change the way we do things

5. How is this being done?
Identify where this Uncertainty is coming from (Done)
Fix it (Doing) – Open Standards
Check to see if our fix is working (To Do)
Tweak it if necessary (To Do)

6. ROOT CAUSE
Bias – Ingrained ways of doing things i.e. different solutions solving the same problem.
Ambiguity – Unfamiliar with Electronic ways of doing things i.e. Difficult to define in enough detail upfront to build

7. Open Standards
We create an open standards for our system

8. Methodology Guess make an educated guess of an electronic system
Map out current reality (data, processes and checklists) visiting a sample set of members
Analyze map eliminate or consolidate any Duplication / Bias
Validate Bring all members together to check to make sure we got it right
Tweak if necessary
Endorse ask for Endorsement (MCSWG20)
Approval Seek approval (FFC OR DCC) <– We are here for Authorizations
Create Open Standard Build electronic system according to standards

9. What We’ve Found
Create very specific electronic standards (data, processes, checklists)
Reusable like Lego blocks
Standardized like Lego blocks
Stackable like Lego blocks
Scalability and Flexibility
in design (to manage complexity)

10. IMS Lego Blocks
Entities need valid Authorizations to conduct Activities within Jurisdictions
Manages data for

11. Unpacking This
Entity – Individual, Organization, Port, Vessel, Sensor etc. (Done)
Authorization – Registration, License, Permit, Agreements, Conditions etc. (Done)
Activity - Fishing, Monitoring & Surveillance, Enforcement etc. (Doing)
Fishing Activities - Trip, Sets, Unloading, Transshipment etc.
Monitoring & Surveillance Activities - Boarding, Inspection, Contacts etc.
Enforcement Activities - Infringement, Violation, Case etc.
Jurisdiction – Geo shape file with ISO Country Code and / or High Seas Code in properties etc. (Done)
Each of the above uniquely identified by a GUID

12. Standardized Authorization Process
Apply
Validate
Due Diligence
Approved
Payment
Issue

19. Expected Outcomes Create certainty > Reduce complexity
Reduce Costs (required time, money and expertise) to develop and maintain systems
Improve interoperability and data sharing among current (TUFMAN, iFIMS etc…)and future systems and technologies
Scale implementation across multiple use cases using reusable standards
Flexible enough to handle future changes

20. What Does this Mean? Short term Long term
Not much is changing in old modules
Currently migration to RIMF2.0 (address technical debt)
No New Modules / Features will be added (feature freeze)
Driving standards for RIMF3.0
Long term
Our system interoperable with new and existing system
Ability to scale out solutions very quickly without too much complexity
Ability to react to new requirements

21. Sources
Standards -
Data Dictionary -

22. Ano Tisam TVM Systems Analyst
Thank You
Ano Tisam
TVM Systems Analyst