Closed arlentees closed 4 months ago
@saragunnarsson @LizGovier Need to create a user flow showing how the Security Act types would work. Example: You can have a Preservation order attached/added/as part of a Notice of Lien. Notice of Lien > Register > Amend > Add Preservation order.
Need more requirements and information on that the 3 Security Act Types.
@arlentees I added this design ticket for the Security Act Notices. There are 3 design tickets in this epic, but depending on how we treat the three categories, it may be combined into one.
We're going to meet with Scott on Monday/Tuesday to brainstorm a few options, would you be able to post a description of why we would need to combine Notice of Lien, Preservation Order, and Notice of Proceeding. You mentioned that Kevin had stated a reason why we might want to do that (I think when amending a Notice of Lien you can also add a Preservation order, or something like that)
@LizGovier we need to do a deeper dive into these filing types for sure - the hope coming out of the requirements was that the Security Act Notice would be one single registration type, and the single registration could have for example a notice of lien and a preservation order at the same time. Whether or not a preservation order could be part of the initial filing or only made via amendments is something I'm not sure of.
It will be worth another call with Kevin and Derek to drill into some more specifics, my understanding of the act is limited.
Questions:
Can we get an example of a court order, commission order.
Note: Security's Act Notice does not actually need to be filed
cc @arlentees
Hey @arlentees I believe all the designs have been completed for this ticket. Do you mind if I close it?
Mural Board
Summary of requirements: Per action 1, a DRAFT summary of requirements follows. (Note: When we met 12 Dec I fully expected to document our agreed actions and the following summary before breaking for the holidays. Given the unintended delay, please review with extra care. There is increased likelihood that I have misreported what we agreed.)
Subject to final decisions in legislative drafting, the new Securities Act (SA) notice(s) will be defined as a “claim” in the Miscellaneous Registration Regulation (MRR), e.g. s. 1(1)). See the MRR s. 1(1) definition of “proceeds of crime notice” for an example of how a claim as defined in MRR may pertain to more than one type of interest as defined in the statute. We expect that the new SA notices will be described as a single claim in the MRR, but we will not know with certainty until MRR changes are drafted.
The minimum PPR registration capability to support the new SA notice is a new PPR registration type that is functionally equivalent to the “Lien for Unpaid Wages” (registration type “WL”). This includes the following registration type features which are available as existing configurable features for registrations under the MRR: a. The registration type will have a name identifying it, including distinguishing it from other interests. For example, “Securities Act notice”. b. Access to register, amend or discharge a registration of this type will be restricted to a short-list of authorized users managed by BCROS staff. c. At least one secured party code will be created to aid in definition of the secured party as being the securities commissioner or another person appointed to act on behalf of the securities commissioner d. The collateral must include a General Collateral Description. The collateral may include one or more serial numbered (aka “vehicle”) collateral items.
Note: The optional entry of Court Order and Detailed Description fields in an original (base) registration may be desirable improvements for other registration types as well, in particular: • A number of other MRA crown charges and claims originate from court orders. Registration of the court order information may be beneficial to searchers. • All PPR registrations might benefit from the Detailed Description field being available with the original (base) registration. It provides an alternative to the General Collateral text field for entry of other information related to the registration.
@mstanton to update Reg/Leg ticket 1686 when sizing is complete.
Update master requirements spreadsheet when requirements complete: https://docs.google.com/spreadsheets/d/18eTumnf5H6TG2qWXwXJ_iAA-Gc7iNMpnm0ly7ctceTI/edit#gid=0