The Multidev system is largely undocumented, if not, practically speaking, completely undocumented.
Documents that do exist may not have been updated in the last 7 to 10 years.
Documents that do exist may address modifications/enhancements to a process, but not the underlying process itself.
As the project has proceeded, Multidev has provided a lot of training that they believe is adequate knowledge transfer to allow us to support ourselves both in terms of function and usage as well as configuration and customer-directed/customer-enabled modification of the Multidev ERP/POS system.
This training has been received by Art but has been used by Art mostly to allow for the exploration of system/solution functionality to drive and/or validate modifications to the system and NOT necessarily for the purposes of developing end user training or system configuration training.
Recordings of most sessions are available, but most are driven by Art’s goal of learning the system well enough to drive and/or validate modifications to the system and the recording may not represent the best/most usable training resource.
CSS
The CSS system has a good deal of documentation available.
See: (user logins are set-up by CSS).
The documentation that is available provides good step by step process information but does not provide a lot of context, especially within our operating premise, i.e., first party, revolving credit.
Because of the work that was done in starting in 2016 to migrate from CCS to CSS for collection support, Art has a strong knowledge of the CSS system including knowledge for some customer-directed/customer-enabled modification of the CSS system.
Business Process Knowledge
A key gap that will be present when Art’s time is further diminished/eliminated is regarding the application of Multidev and CSS processes to SMC business processes.
Due to the development and modification done to MAGIX, Universe and CSS by Art over the last 35+ years, the business processes that drive automation and automation that drives business processes are understood by Art, but few others.
David Sherwood has a strong understanding of many, if not all, business processes, but is not fully knowledgeable about implemetation of the automation that addresses those business processes.
Within each key area there are business processes “subject matter experts”, but linkage to automation is mostly at the keystroke level and not the process and methods level.
David and/or Inez can provide the names/roles of those involved in various departments.
SMC IT Support
Inez is the best resource for understanding the current state of the SMC IT department’s knowledge of and ability to support existing and new systems.
From my perspective, the following areas need to be discussed to allow for the proper allocation of resources and prioritization of additional training for the support of the new systems.
Multidev
Security (configuration of security issues)
Access to usages/usage groups.
Control of add/delete record rights (versus read only rights).
Field level security.
Usage group creation and modification.
Usage group layout modification/
Field list creation and manipulation.
Server filter creation and manipulation.
Screen layout updates
Field level controls:
List mode headings
Form mode headings
Required and default values.
Background processes and services
Multidev MDDT Service
Multidev MS Web Sync – SHOPIFY interface
Client-User Applications (administration)
Within Accounting – database and user account security
Within SmartForms – user security
Console Applications
POSPRGenerator
STGLQUEUE
Server Applications
Configurator (POS)
MDDT_Config
Multiservices (console control/configuration of Multidev MS Web Sync service
CSS
Manipulation of accounts through result codes and result code SODs (processes of the CSS system) need to be fully communicated.
The overall processing cycle for customer accounts (which is moving from MAGIX to CSS) needs to be fully communicated.
FTP data transfer/exchange processes
Multidev to CSS – full customer purchasing detail to support additional work done at write-off.