83,308
edits
Business Structure: Difference between revisions
→Documentation
Amwelladmin (talk | contribs) |
Amwelladmin (talk | contribs) |
||
| Line 3: | Line 3: | ||
===[[Business Structure/Business Lines/Documentation|Documentation]]=== | ===[[Business Structure/Business Lines/Documentation|Documentation]]=== | ||
====Business Description==== | |||
Engaging in repapering projects - where large quantities of documentation need to be updated or changed in a homogenous way. Here there is a premium to configuring the documentation and process up front, using workflow and document automation to make the process is simplistic as possible. | Engaging in repapering projects - where large quantities of documentation need to be updated or changed in a homogenous way. Here there is a premium to configuring the documentation and process up front, using workflow and document automation to make the process is simplistic as possible. | ||
The Pitch: There will be a huge amount of repapering required as a result of [[Mandatory Clearing]] and [[ESMA]] initiatives. Inhouse can't do it - it will require overflow. Getting a business which understands not only the market practice and legal subtleties, but also how to project manage, scale and apply technology to solve the volume problem, should be well placed. | |||
====Examples==== | ====Examples==== | ||
*Mandatory clearing | |||
====Necessary Resources==== | ====Necessary Resources==== | ||
''Personnel'':<br> | ''Personnel'':<br> | ||
*Expert in Clearing and Regulatory issues. Suggest: Peter Loo. | |||
*TBD re technical expertise. | |||
''Time''<br> | ''Time''<br> | ||