600 likes | 739 Views
A Technical Guide to ERMS. Bill Manago, CRM. What You Need to Plan For. Out of the Box What you should and should not expect. Classification Schema Record series, file plans, folder types. Disposition Rules Creating rules, assigning rules.
E N D
A Technical Guide to ERMS • Bill Manago, CRM
What You Need to Plan For Out of the BoxWhat you should and should not expect Classification SchemaRecord series, file plans, folder types Disposition Rules Creating rules, assigning rules • Implementing an Electronic Records Management System Access ControlsAccess to records, access to system functions End-User Trainer The new records managers
Out of the Box • Do ERMS work out-of-the- box? • Yes ? • No? • Maybe? • Partly?
Out of the Box Boiler plate functions and system interfaces • Database tables • Record repository • Integrations with • business application • Administrator console • System configurations • System parameters • End-User web interface • Record declaration • Search and retrieval
Record Repository For managed records Business Applications • Enterprise-wide dedicated records repository SAP MOSS HR DMS Manage in place
Federated Searching SAP MOSS HR DMS • For managed records Index Index Index Index Email Index Database Metadata Capability for users to select which repository or combination of repositories to search for records.
Database Tables • Relational DBs: • SQL Server • Oracle • IBM DB2 • Others • Tables: • Categories • Folders • Documents • Boxes • Users • Rooms • Rules • Sessions • Others
Corp Database Configuration - 1 LA CHI NYC Corporate HDQS Centrally Managed
Chicago • Repository • Los Angeles • Repository Database Configuration - 2 • New York • Repository Synchronize Corporate HDQS Multi/Distributed
Nomenclature • Label items using your taxonomy One Size Does Not Fit All • Displays • Data Entry, Search and Retrieval, Hit Lists • Functional Features • Available to different classes of users • Menu Displays • Options selectable by end users Configuration vs Customization • Configurable • Things you can change • No costs • Modify out of the box • behavior (limitations) • Standard reports • Standard bar code labels • Customization • You must pay • Changes made to the code • Custom behavior • Database scripts • Custom reports • Custom bar code labels
End-User Web Interface Opening Page
End-User Web Interface Record Search Screen
End-User Web Interface Full Text Search Screen
End-User Web Interface Hit List
End-User Web Interface Document Profile
Record Series • SERIES 0318 – REPORTS • 0318-01 • Record Category Name: AIS Audit Records • Disposition Authority: N1-218-00-4 item 023 • Transfer or Accession to NARA Indicator: No • Vital Record Indicator: Yes • Vital Records Review and Update Cycle Period: Weekly. • Record Category Description: Consisting of AIS Security Officer or Terminal Area Security Officer weekly audit records of audit actions performed on all AIS as required by applicable policy which are maintained by any JS/combatant command activity • Disposition Instructions: Cut off monthly, hold 1 month, then destroy. • Note: One folder created for each month • Expected Behavior: Folder becomes due for cutoff at the end of the month. Cutoff folder is due for destruction 1 month after cutoff. If the RMA automatically calculates cutoff at the record level and does not require the organization to create folders, do not create the "January AIS Audit Records" folder listed below. Instead, provide information to the testers regarding what date the RMA uses to calculate the cutoff eligibility for the records (e.g., Date Filed, Date Published).
Category File Plan Hierarchy Sub-Category Sub-Category File Folders File Folders File Folders
Retention Rules • Record Category Name: Overtime reports and related documents • Disposition Authority: N1-218-00-7 item 28 • Transfer or Accession to NARA Indicator: No • Vital Record Indicator: No • Record Category Description: Overtime reports and related documents which are maintained by JS/combatant command comptroller as the official record copy • Disposition Instructions:Cut off at end of FY, hold 3 years, then destroy • Note: One folder created for each FY • Expected Behavior: Folder becomes due for cutoff at the end • of the Fiscal Year. Cutoff folder is due for destruction 3 years • after cutoff. If the RMA automatically calculates cutoff at the • record level and does not require the organization to create • folders, do not create the "FY08 Overtime Reports" folder listed • below. Instead, provide information to the testers regarding • what date the RMA uses to calculate the cutoff eligibility for • the records (e.g., Date Filed, Date Published)..
Category Retention Rule Assignment Sub-Category Sub-Category File Folders File Folders File Folders Disposition Rule Disposition Rule Record Record Record
Access vs Permissions • What users • can see. What users can do.
Access Controls • Classification Marking • Supplemental Marking • Group Security • Office Security • Location Security • Project Member • Individual Security At least one NO No NOs
Permissions • Copy • Move • Insert/Up Load • Edit/Modify • Download • Create New • View On Hold • Edit on Hold
User Accounts • User ID / number • Name (format) • Login • Office • Role/Permissions • Group/Access • Clearance Level • Supplemental Markings
Record Declaration • Business Applications • EDMS • Shared Drives • Personal Drives • Email Systems • Social Media Providers
Record Declaration Decisions • Delete from source • Allow duplicates • Single instances • Multiple instances • Email stubbing • Official record copy • or • Official record copies
The Role of Metadata • Add business context • Finding aid • Aids authenticity • Extracted by system • Manual data entry
The Issue with Metadata The more the metadata, the easier search and retrieval. The more the metadata, the heavier the burden on users.
Email Records Content Media or Medium Email Archiving. Records Management