82,964
edits
Business Structure: Difference between revisions
m
Text replace - "can't" to "can’t"
Amwelladmin (talk | contribs) |
Amwelladmin (talk | contribs) m (Text replace - "can't" to "can’t") |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
__NOTOC__ | |||
== {{subpage|Infrastructure}}== | == {{subpage|Infrastructure}}== | ||
== {{subpage|Business Lines}}== | == {{subpage|Business Lines}}== | ||
| Line 6: | Line 7: | ||
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 | 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==== | ||