Migrate MRAS messaging from COLIN to ENTITIES

[lmcclung]

Description:

MRAS messaging is currently going through the COLIN Oracle database. As part of modernization project this messaging should be moved off COLIN oracle and over the the Entities database.

• What are the most critical features being built as part of this Epic
• Expected Outcome – Justification why this Feature must be built, what is expected value and justification for priority.

https://docs.google.com/spreadsheets/d/1oFG5dMBsOQ_FIrjbdOPmtTOVnklKYnafJsBEPe9urvo/edit?ts=6065f958#gid=368952238

• Start date when team will start to work on: This is visible in ZenHub under "Roadmap" - After critical filings built

• End date Epic will be delivered: This is visible in ZenHub under "Roadmap"

• T-shirt size: X (S, M, L, or XL) (S=1-2 Sprints, M=2-3 Sprints, L=4-5 Sprints, XL=not sure, probably more than 5 Sprints). Story points needs to be updated in Epic. This can be decided by team. Rough estimate from Thor would be 53 developer days if high performing dev (20-50% more if less experienced). Plus should add 30% for overhead and QA testing.

• Process Flow (if applicable) - see google doc

• CM considerations? May need to do testing with MRAS partners

• Possible dependencies or blockers forseen right now? - Please create a story and block this epic by the dependency story.

---

Enabler Epics:

• action
• result
• object

[lmcclung]

@Kaineatthelab FYI, created this epic so I don't lose track of Thor's estimate for MRAS migration. Looks to be about 3 sprints worth of work