Exhibit_3_-_Complexity_Guidelines.xlsx
XLSX spreadsheet 14 KB Posted
- Attached to
- Enterprise Asset Management - Software & Implementation State and local contract opportunity
- Solicitation number
- RFP 26-0007
- Issued by
- Maricopa County, Phoenix City, Arizona
About this file
Exhibit 3 from the City of Phoenix outlines Complexity Guidelines for an Enterprise Asset Management (EAM) software implementation, detailing evaluation criteria across six key technical domains: Configurations, User Defined Fields, Reports, Interfaces, Extensions/Enhancements, Workflows, Forms, and Conversions. Each domain is categorized into four complexity levels - Simple, Moderate, Complex, and Very Complex - providing a comprehensive matrix for assessing technical intricacy and implementation requirements. The guidelines serve as a detailed assessment framework to evaluate the proposed EAM solution's technical sophistication, system integration capabilities, and potential implementation challenges.
The complexity matrix provides granular insights into technical requirements, with each complexity level offering specific characteristics related to configuration dependencies, data processing logic, reporting capabilities, transaction handling, error management, and system integration. The guidelines suggest the City of Phoenix anticipates a sophisticated EAM solution requiring flexible, robust technical capabilities that can handle complex multi-departmental configurations, intricate data translations, advanced reporting needs, and extensive system interfaces. By establishing these detailed complexity guidelines, the city ensures a comprehensive evaluation process that can objectively assess vendor capabilities across technical, functional, and integration dimensions of the proposed enterprise asset management solution.
View the file
Other files for this state and local contract opportunity
Show all 50
Enterprise Asset Management - Software & Implementation has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Exhibit 3 Exhibit 3. COMPLEXITY GUIDELINES
| Simple | Moderate | Complex | Very Complex | ||
| Configurations | · Simple configuration table that stands-alone. | · Multiple configuration tables with table inter-dependencies. | • | Multiple configuration tables with complex table inter-dependencies. | |
| • | Table dependencies that drive EAM and/or FSM processing logic. | • | Multiple configuration tables with complex table inter-dependencies. | ||
| • | Table dependencies that drive external application processing or logic. |
| Simple | Moderate | Complex | Very Complex | ||
| User Defined Fields | • | Used for simple displaying and/or reporting. | |||
| • | Simple formatting (e.g., date). | ||||
| • | Little to no entry validation required. | • | Used for driving a moderate level of processing logic. | ||
| • | Entry validation required. | • | Used for driving a complex level of processing logic in EAM and/or FSM. | ||
| • | Complex entry validation required that may include logical data combinations. | • | Used for driving a complex level of processing logic in EAM and/or FSM. | ||
| • | Complex entry validation required. | ||||
| • | Includes use in external application processing or logic. |
| Simple | Moderate | Complex | Very Complex | ||
| Reports | • | Minimal modifications to an existing report. | |||
| • | Simple custom new report. | • | Modifications to an existing report with new additional fields and alignment or formatting changes. | ||
| • | Stand-alone report that requires joins of multiple tables. | • | Custom report with multiple trigger events. | ||
| • | Report that requires complex joins of multiple tables. | ||||
| • | Complex data selection, detail levels, and sorting options. | · Combination of external application and EAM data for report generation. |
| Simple | Moderate | Complex | Very Complex | ||
| Interfaces | • | Single transaction to be posted in EAM. | |||
| • | Simple error reporting. | ||||
| • | No restart functionality required. | ||||
| • | One output file created. | ||||
| • | Little or no translations. | ||||
| • | Data read from a few tables. | ||||
| • | Simple batch processing. | ||||
| • | One file to one EAM transaction. | • | A few EAM transactions with minimal flow decisions. | ||
| • | Moderate level of error reporting. | ||||
| • | Moderate restart functionality. | ||||
| • | Moderate number of tables accessed. | ||||
| • | One or more output files created. | ||||
| • | Multiple field/table translations. | ||||
| • | Multiple files and/or formats to one or more EAM transactions. | • | Many EAM transactions and/or complex data conditions. | ||
| • | Complex error, control, and audit reporting required. | ||||
| • | Significant restart functionality. | ||||
| • | Several output files are created. | ||||
| • | Complex processing. | ||||
| • | Requires user exits. | ||||
| • | Significant data translation required. | ||||
| • | Interfaces multiple files to one or more EAM transactions. | • | Significant business logic and decision points. | ||
| • | Complex data translation required. | ||||
| • | End-to-end restart functionality. | ||||
| • | Interface will include updates in multiple systems. | ||||
| • | Cross-transactional data dependencies. |
| Simple | Moderate | Complex | Very Complex | ||
| Extensions / Enhancements | • | User exit is available and is frequently used on similar implementations. | |||
| • | Requires simple effort to understand functionality. | • | User exit is available, but not frequently used. | ||
| • | Requires moderate effort to understand functionality. | ||||
| • | Moderate code changes required. | • | New user exit(s) required. | ||
| • | Significant research is required to design the enhancement. | ||||
| • | Significant code changes required. | • | Requires existing base code to be modified. | ||
| • | Involves complex programming with multiple screens and sub-screens. | ||||
| • | Composed of multiple complex objects. |
| Simple | Moderate | Complex | Very Complex | ||
| Workflows | • | Few changes to an existing business object. | |||
| • | Simple business object code. | ||||
| • | Simple attributes. | ||||
| • | Standard tasks available in workflow template. | • | Moderate number of steps to be created. | ||
| • | Moderate number of attributes to implement. | ||||
| • | Uses standard available module calls. | ||||
| • | Requires creation of minimal roles with custom functions. | ||||
| • | Minor event triggering for workflow handling. | • | Requires functionality like charts, maps, wizards, etc. | ||
| • | Built some simple Custom Controls to accommodate client’s requirements. | ||||
| • | Includes dynamic editing of table data and updates the system of record. | ||||
| • | Includes display of some popup dialog on select or hover on a chart or map. | ||||
| • | Includes navigation between the pages with multiple parameters. | ||||
| • | Requires use of a third-party APIs to achieve certain type of charts and controls. | ||||
| • | Requires new windows with complex formatting. | ||||
| • | New functionality/ business logic or multiple subroutines. | • | Converts a table/chart to PDF and downloads. | ||
| • | Usage of cookies or variants for session/data storage and its usage across the pages. | ||||
| • | Accesses data from some external sources. | ||||
| • | New functionality/ business logic or multiple subroutines. | ||||
| • | Composed of multiple objects. |
| Simple | Moderate | Complex | Very Complex | ||
| Forms | • | Uses simple controls (e.g., lists, tables, grid, etc.). | |||
| • | Navigation between pages with minimal parameters. | ||||
| • | Simple binding to the UI controls. | ||||
| • | Simple layout or layout changes. | ||||
| • | One main window with only a few elements. | ||||
| • | Minor changes to an existing program. | • | Uses a few dialogs and popups to display additional information. | ||
| • | Requires functionality like search, sort, filters, validations for input fields, etc. | ||||
| • | Requires a formatter to convert data in the user readable format. | ||||
| • | Complex layout with multiple windows. | ||||
| • | May require new windows with some format changes. | • | Requires functionality like charts, maps, wizards, etc. | ||
| • | Built some simple Custom Controls to accommodate client’s requirements. | ||||
| • | Includes dynamic editing of table data and updates the system of record. | ||||
| • | Includes display of some popup dialog on select or hover on a chart or map. | ||||
| • | Includes navigation between the pages with multiple parameters. | ||||
| • | Requires use of a third-party APIs to achieve certain type of charts and controls. | ||||
| • | Requires new windows with complex formatting. | ||||
| • | New functionality/ business logic or multiple subroutines. | • | Converts a table/chart to PDF and downloads. | ||
| • | Usage of cookies or variants for session/data storage and its usage across the pages. | ||||
| • | Accesses data from some external sources. | ||||
| • | New functionality/ business logic or multiple subroutines. | ||||
| • | Composed of multiple objects. |
| Simple | Moderate | Complex | Very Complex | ||
| Conversions | • | One one-to-one data with limited data variations. | |||
| • | Limited field/data translations. | ||||
| • | Basic validation and error processing. | ||||
| • | Simple record counts for balancing. | ||||
| • | Requires no data clean-up. | ||||
| • | Small data volume. | ||||
| • | Restart mechanism needs minimal effort. | ||||
| • | None to simple dependencies on other converted data. | • | Limited variations of data formatting. | ||
| • | Limited conditional constructs. | ||||
| • | Some table/field translations. | ||||
| • | Summary control reports required for balancing. | ||||
| • | Requires some data clean-up. | ||||
| • | Moderate number of records to be converted. | ||||
| • | Minimal dependencies on other converted data. | • | Many files to one or more transactions. | ||
| • | Sequencing based on data conditions. | ||||
| • | Complex validations and error processing. | ||||
| • | Requires detailed control calculations and reports for balancing. | ||||
| • | Requires extensive data clean-up. | ||||
| • | Requires error logs. | ||||
| • | Significant number of records to be converted. | ||||
| • | Complex restart mechanism required. | ||||
| • | Multiple dependencies on other converted data. | • | Complex file structures. | ||
| • | Composed of multiple objects. | ||||
| • | High number of records to be converted. | ||||
| • | Significant performance requirements during conversion cut over. | ||||
| • | Complex dependencies on other converted data. |
Forms
File details come from the government source that posted it. Updated .