There are two common approaches to shared drives. One is considered day forward with people, processes, and technology that align with a company’s content strategy. The second, is a backfile, or the approach we take to cleaning up issues seen in our content management.
As the largest collection of documents in your organization, removing shared drives suggests massive change management and expense. However, if approached correctly, it doesn’t have to be complex, expensive, or disruptive—and you can continue to provide a file system. Through proper methodologies, content is not duplicated and an alternative user interface is applied to the DMS. User adoption is also increased by leveraging the simple shared drive, and efficiency is increased by offering tools that automate common tasks.
We will review the methods for classifying information, what you are able to accomplish with policy evolution, and the technologies and methods available to limit the sprawl of content.
5. WIIFM?
What problems are we
solving?
Workplace Efficiency,
System Complexity, Risk &
Cost Avoidance
ECM
AVOIDANCE
(FOR COLLABORATION))
ECM SHELFWARE
• Shared Drives
• Email
• Cloud Sites: Dropbox,
Box.Net
USING ANYTHING BUT…
COST &
COMPLEXITY
(OF SECURING DOCUMENTS)
HIGH COST, HIGH
RISK
• Manage
• Synchronize
• Secure
page
05
6. Security.
Risk is greatly reduced by
better managing content,
reducing duplication of
content, managing access
and lifecycle.
Shrink the vectors of attack.
Efficiency is a result!
People Spend Two Hours a Day
Looking For Information.
page
06
8. Serious
Message
page
08
Lock it down now. Stop
adding to the problem.
Provide an integrated solution,
similar to the shared drive UI,
for maximum user adoption.
Any content, any type of content related to the enterprise shall be managed!
Mention SAP.
Duplicztaion of content is the enemy. Data entry, multiple screens & swivel chair are not acceptable today.
Context and Automation Start at 1 and 2
Deliverying Content, when you need it, where you need it starts at 2 and 3
Integration is done seamlessly
Migration is
Lowering costs of records storage;
Assuring continuity of business functions in the event of a disaster;
Protecting against privacy violations resulting from inappropriate access to data or disclosure of data,
Avoiding substantial fines and penalties for discovery failures (in civil or administrative cases) or criminal sanctions for obstruction of justice (in government investigations).
Reduce access to dumping grounds. Shrink the attack vector.
Context and Automation Start at 1 and 2
Delivering Content, when you need it, where you need it starts at 2 and 3
Integration is done seamlessly
Migration is
Stop adding to the problem.
Easy fix – lock down the top 2 levels and allow super-users to administer the creation of additional top level folder structure.
galina
Autoclassification technologies WITH ETL features
Both day-forward and back….extracting meaning means knowing what to do next and knowing where this belongs. Take out the human element and humans will be happier.
Auto-declaration, collab site cleanup, content locking & synchronization.
Intralinks, Geolang/Ascema, StoredIQ, Valora
Option for day forward if your DMS doesn’t support open standards…lock down the backfile
Don’t just move the problem such as moving content from a shared drive to SP or Gdrive.
Add Encryption at Rest – Alfresco functionality with 5.0
Add outside of repository
Mike
Mike
1 - A significant amount of information stored on file shares simply has no business relevance whatsoever, such as employees’ collections of MP3 music files, or pictures from your amazing vacation, or flyers for the company potluck from last year. This type of non-business-related information should be discarded on a regular basis – or not allowed in the first place.
2 - This is clearly business information because the organization relies on it to conduct its day-to-day activities. For example, invoices are used to document what a client or the organization owes or is owed; even after the payment has been made, the invoices and payment information need to be kept for some period of time to satisfy customer inquiries (including internal customers). This should be retained until no longer needed and then discarded subject to the next two considerations.
3 - Every organization has to comply with certain legal or regulatory requirements. Some of these apply to almost every organization, such as tax and personnel; others may be specific to an industry, such as government, energy, or financial services. These often take the form of needing to retain specific types of information for specific minimum periods of time; in some cases, they may also require that certain types of information be destroyed after some period of time.
Scalable - Scales to support large volumes of users and content Billion documents on AWS etc.
Or just get your job done faster and better. Help a colleague do better next time.