Attachment A - Revision 2.pdf

Response Requirements Attachment:

Subject:

A

Response Requirements

Attachment A - Response Requirements Revision 2 Page 1 of 45

1. Response to SCDMV Requirements

The table below identifies the topics which the Offeror shall address in its Technical Proposal. Each topic in the response shall be identified with a heading corresponding to the table below. Responses should not be placed in the table.

The Offeror shall refer to the referenced appendix number and appendix section to fully understand the SCDMV’s requirements and expectations when preparing the response.

The Offeror should provide a detailed description of the proposed solution but does not need to address every item or sentence in a particular section. The Offeror shall address the topics/questions identified in the table but is expected to elaborate or add additional information as appropriate to fully understand the Offeror’s solution and approach. Highlight the following in your responses:

1. Is the proposed functionality for that topic fully configurable, partially configurable, or not at all configurable and who is able to do the configuring?

2. Is the functionality for that topic part of the proposed system’s core functionality, an add-on module, or provided through an interface or other mechanism?

3. Will any features be especially useful to SCDMV in its goals to improve processes, improve service delivery, and achieve a 360-degree view of the customer?

The Offeror should adhere to any page limit for the topic. Page limits are provided only to indicate expected response length but an offeror’s adherence to this limitation is not evaluated.

In some topics below, the SCDMV has requested a sample of work from a previous project or a draft version of an artifact for this project. These items are identified below and shall be included but not inserted into the narrative. Such items are not included in page limits. If requested items are not available, briefly describe.

TECHNICAL RESPONSE REQUIREMENTS

Num Appdx Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit

1. 1 2.1 Contractor’s SDLC Methodology

1. Describe your proposed system development life cycle methodology, demonstrating how it is iterative and incremental, use case driven, architecture centric, and risk focused. Specifically discuss your organization’s and your proposed team’s experience using that methodology in a project of similar size and scope to this project.

Attachment A - Response Requirements Revision 2 Page 2 of 45

Num Appdx Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit

2. 1 2.1.1 SDLC Requirements 1. Provide a copy of the current SDLC methodology the Contractor intends to follow for the modernization project.

2. The Contractor’s SDLC methodology is subject to periodic review and approval by the SCDMV. Describe your approach to addressing any gaps identified in your

SDLC.

3. It is not uncommon for an SDLC to be tailored to a particular project. Describe your approach to tailoring the Contractor’s SDLC methodology when necessary.

4. Describe how the Contractor’s SDLC methodology addresses software change management, including all proposed changes/enhancements:

a. Evaluating and approving/rejecting proposed changes

b. Testing a change

c. Implementing a change/enhancement

d. Confirming a change has successfully been implemented and closing out the change proposal/request

3. 1 2.1.2 Contractor's SDLC Documentation

1. Provide a list of the typical artifacts created for each stage of the Contractor’s SDLC methodology. Describe the deliverables you plan to create and organize them according to the proposed SDLC phases.

2. Describe how the Contractor’s SDLC methodology ensures documentation is kept up to date at all times.

3. Describe how you ensure the end-user documentation (e.g., help text) and training materials match the code released into the production environment.

Attachment A - Response Requirements Revision 2 Page 3 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit

4. 1 2.1.3 SDLC Training 1. Describe the training and documentation you will provide the SCDMV on the Contractor’s SDLC methodology.

2. Describe the frequency of the Contractor’s SDLC methodology training that will be provided to the SCDMV.

3. Describe the training and documentation you will provide the SCDMV’s partners, contractors, counties and courts on the Contractor’s SDLC methodology.

5. 1 2.2 Software Development Plan & High-level Roadmap

Describe the overall approach proposed for this project to build the Modernized System consistent with the requirements in 2.2.

6. 1 2.3 SDLC

Documentation Tools

1. Describe tools and frameworks you propose to use in supporting the SDLC.

Describe your proposed approach to change/configuration management.

2. Describe the tools you plan to use to manage, track, and version SDLC artifacts and requirements documentation, and to manage, track, and version source code.

Describe how the tools are used during the engagement. Describe how traceability between all items is preserved.

3. List the artifact templates you plan to provide; provide samples of some artifact templates.

4. Describe your proposed coding standards.

5. Describe your approach to developing a Performance Engineering Plan.

6. Provide a sample Performance Engineering Plan from a similar project.

7. 1 2.4 Version Control Tools

Describe how your version control tools address changes to the SCDMV modernized system.

Attachment A - Response Requirements Revision 2 Page 4 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit

8. 1 2.5 Architecture and System Environments

1. Describe the architecture you propose for the SCDMV modernized system.

2. Describe architectural differences in the environments for the SCDMV modernized system.

3. Describe your approach to sizing each of the environments.

4. Describe the sizing for each of the environments in terms of processors, memory, storage, bandwidth, and other factors.

5. Describe how the environments and which environments support external testing. (Also see related questions in Appendix 14 System Interface Requirements.)

6. Describe the tools you recommend for automating environment setup, replication, and management.

9. 1 2.6 Requirements Traceability Matrix

1. Describe the approach for meeting the requirements in 2.6.

2. Describe the tools you recommend for automating the Requirements Traceability Matrix (RTM).

10. 1 2.7 Capacity Analysis Plan

Describe the approach for meeting the requirements in 2.7.

11. 1 3.0 Initial Use Case Analysis and Gap Analysis

1. Describe your approach for developing a set of initial use cases as described in 3.0.

2. Describe the use cases and other artifacts that exist for the proposed solution and your anticipated approach for conducting Gap Analysis between the SCDMV requirements and the proposed solution.

12. 1 4.0 Release Planning 1. Describe your approach to developing the Release Plan for this project.

13. 1 5.0 Iterative Requirements Analysis and Design Activities

1. Describe your expected approach for planning and conducting the iterative requirements analysis and design activities. Include the activities

Attachment A - Response Requirements Revision 2 Page 5 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit performed, resources involved and artifacts that are generated.

2. Describe your expected approach for planning and conducting analysis and design sessions.

3. Describe your approach to developing security requirements including identity management requirements, authentication requirements and roles.

14. 1 6.0 Iterative Development Activities

1. Describe your expected approach for planning and conducting the development activities. Include the activities performed, resources involved, standards applied and artifacts that are generated.

15. 1 7.2 Required Testing Activities

1. Describe your tools and approach to regression testing in all environments.

2. Describe the tools you recommend for automating regression testing.

3. Describe your experience with tools for automated regression testing.

4. Describe your tools and approach to compatibility testing in all environments

16. 1 7.3.2 System and Integration Testing

1. Describe your approach to meeting the regression testing requirement in this section.

2. Describe your approach to manual and automated Regression testing, which is the repetitive testing of an application’s major features to ensure that changes have not introduced new defects into the system.

3. Describe your approach to testing each of the items in the bulleted list in this section.

17. 1 7.4 UAT Test Requirements

1. Describe your planned approach to User Acceptance Testing.

2. Describe how the SCDMV and the Contractor can work together in the UAT environment.

Attachment A - Response Requirements Revision 2 Page 6 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit

3. Describe how the SCDMV users can participate in UAT and introduce test scripts and scenarios.

4. Describe how you address test data that ages over time. For example, birth dates in test data are integral to testing drivers under 21 years or over 65 years.

18. 1 7.5 Testing Environments

1. Describe your approach to testing in each environment, including documentation, tools, and reporting.

2. Describe how you are sure the code transferred into the production environment is properly operational.

19. 1 7.7 Use Automated Testing Tools

1. Describe your approach to meeting the requirements for the test activities.

2. Describe your approach for performing automated testing and the tools that are used for automated testing.

20. 1 8.0 Data Conversion and Migration

1. Describe the approach, activities performed, resources involved, and artifacts that are generated to address the data conversion, migration, and synchronization requirements for this project.

2. Describe your approach to managing risk associated with data synchronization.

21. 1 9.0 Implementation Activities

1. Describe your expected approach for planning and conducting the Implementation activities. Include the activities performed, resources involved and artifacts that are generated.

22. 1 10.0 Contractor Logistics The Offeror shall describe any logistical requirements or solutions it has related to Section 10.

23. 1 All Project Schedule

Gantt Chart & Narrative Approach

1. Provide a draft of a high-level SDLC schedule, if not already included in the overall Project Plan, including a Gantt Chart with sufficient detail to present the Offeror’s understanding of the complexity of the project and the necessary work

Attachment A - Response Requirements Revision 2 Page 7 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit effort. Also provide a narrative description as necessary to explain the schedule.

2. In preparing the proposed schedule, the Offeror shall consider the following:

a. The SCDMV has described the scope of the project in terms of business functions such as, Driver Services and Vehicle Services, but the Offeror shall propose an approach for partitioning, constructing, and deploying system functionality as it sees fit based on its experience.

b. The SCDMV has described execution requirements by referencing the South Carolina SDLC but Offerors are expected to propose its preferred SDLC based on its experience.

c. The Offeror shall propose a schedule that it believes is realistic and cost-effective based on its experience.

3. The Offeror shall provide the following to describe its proposed schedule and approach:

a. A detailed narrative description of the schedule and proposed candidate releases for the project. Offeror shall provide any additional information necessary to explain the proposed schedule, its benefits and risks, and other considerations.

b. A detailed list of milestones for the project. This shall include, at a minimum, the releases of system functionality, milestones related to activities such as training, data conversion, and operations and support. It shall also describe planned progress through phases of the SDLC for each release and

Attachment A - Response Requirements Revision 2 Page 8 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit significant project management activities.

24. 1 11.2 SDLC Design Documentation

Describe your techniques and processes for preparing SDLC documentation. Describe the level of detail. Describe how you ensure consistency across all artifacts.

25. 1 11.3 Source Code Documentation

1. Describe your techniques and processes for documenting source code. Describe how you ensure consistent documentation across all code.

2. Include a sample of code where the source code is annotated that demonstrates the extent to which you intend to document source code.

26. 1 11.4 System Operations Manual

1. Describe how you build a system operations manual over the course of the contract.

2. Include a sample of a process from a system operations manual.

27. 1 11.6 System User Guide 1. Describe how you build a system user guide over the course of the contract.

2. Include a sample of a transaction from a system user guide.

28. 1 11.7 System Integrated Help

1. Describe system integrated help functions in your solution. Describe what level of detail you will include in the system integrated help.

2. Describe any other electronic help features that may exist in your solution to support end users.

3. If using a third-party solution to manage the integrated help, identify the tool and describe how you will transition the use of this tool to SCDMV resources during the project.

4. Include a screenshot of any features described.

29. 1 11.8 Documentation Tools

Identify any tools you will use to create, edit, and maintain documentation. Describe how

Attachment A - Response Requirements Revision 2 Page 9 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit you keep all documentation in sync throughout the life of the project.

30. 1 11 General Describe how all types of documentation will be turned over to the SCDMV after the warranty period.

31. 1 11 General 1. Describe the methodology including processes, templates, and tools that will be used to manage all documentation on the project. Describe the implementation, execution, and management of all documentation processes. Describe how this methodology will be integrated into the project plan to guide the project to a successful conclusion.

2. Include a summary documentation plan for this project.

3. Describe the approach for meeting the requirements for the Documentation Plan.

32. 1 N/A Requirements not Met

By submitting an offer, Contractor agrees to meet all requirements of the solicitation, including all appendices. Confirm you meet all requirements of Appendix 1. Identify and explain any areas that cannot be met.

33. 2 4.0 Project Startup The Offeror shall describe its general approach to project startup.

34. 2 5.0

Project Management Requirements

1. The Offeror shall present its project management methodology as proposed for this innovative project. This description should include all proposed deliverables necessary to meet the requirements in the RFP and others that the Offeror proposes to include as part of its approach.

2. The Offeror should submit a proposed draft PMP for this project.

35. 2 5.4 Quality Management

The Offeror should provide a detailed description of the Quality Management approach it proposes to use for this project.

Attachment A - Response Requirements Revision 2 Page 10 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit

Include a sample Quality Management Plan from a similar project.

36. 2 5.7 Risk and Issue Management

The Offeror shall describe its approach to Risk and Issue management and specifically describe risks related to this project, to include any perceived mitigation or remediation considerations.

37. 2 5.8 Escalation Process The Offeror shall describe its escalation process for issue and risks identified during the project.

38. 2 6.0 Project Management Document Repository

The Offeror shall describe its approach and recommended toolset for addressing Configuration and Document Management. If there is a cost or licensing for these tools then include line-item pricing on the price sheet for them as directed, including licensing model, hardware and software.

39. 2 7.0 Project Management Tools

Offerors should describe any project management tools and software proposed as part of their solution. If there is a cost or licensing for these tools then include line-item pricing on the price sheet for them as directed, including licensing model, hardware and software.

40. 2 N/A Requirements not Met

By submitting an offer, Contractor agrees to meet all requirements of the solicitation, including all appendices. Confirm you meet all requirements of Appendix 2. Identify and explain any areas that cannot be met.

41. 3 2.1.2 Support Levels

1. Describe your approach to the requirements in 2.1.2 Support Levels.

2. Describe the two-way handoff between the SCDMV-provided support tool and Vendor-provided tools.

42. 3 2.2 Warranty Period Confirm that the Warranty covers all aspects of the modernized system (e.g., base software, SCDMV-specific customization, configuration, training, and other materials.

Attachment A - Response Requirements Revision 2 Page 11 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit

43. 3 2.3.1.1 Staffing Needs Analysis

Provide an example of the Staffing Needs Analysis used on a prior project that included both Vehicle and Driver examples. Prior customer names and PII may be redacted.

44. 3 2.3.3 O&M Services Describe your approach to the requirements in 2.3.3 O&M Services, items k. Technical Knowledge Transfer and I. O&M Training.

45. 3 2.3.5 Support Duration and Hour Requirements

1. Indicate the number of hours and resources typically required to provide annual, non-warranty support for legislative enhancements and other support activities typically required by States.

2. What are your best practices for knowledge transfer to allow the SCDMV to support the system?

3. After the SCDMV support staff is fully trained and has experience supporting the modernized system, how many Contractor resources are recommended to be available, and what activities would these resources perform?

46. 3 2.3.6 Impact Assessment Requirements

1. Describe the Contractor-provided support activities typically requested by States.

2. Describe how you can include the SCDMV’s IT resources in executing change orders.

3. In the event the Total Support Hours for a given year are insufficient to address the approved change orders, how quickly can you bring on additional resources to meet the SCDMV’s needs for support?

4. What are the most overlooked areas where the Contractor can support the

SCDMV?

47. 3 2.3.7 Turnaround Times for Change Orders

Although every support request is unique, describe the typical turnaround times for the most common support requests. For example, fee changes, the addition of plates, the addition of reports, emergency defect repairs, deploying an update to the base

Attachment A - Response Requirements Revision 2 Page 12 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit software, and other common support requests.

48. 3 2.4.5 Service Level Requirements

Describe your approach to the requirements in 2.4.5.

49. 3 N/A Requirements not Met

By submitting an offer, Contractor agrees to meet all requirements of the solicitation, including all appendices. Confirm you meet all requirements of Appendix 3. Identify and explain any areas that cannot be met.

50. 4 2

Training Approach/Planning

1. Describe the methodology and general approach to training. Describe how this methodology will be integrated into the project plan to ensure all personnel are properly trained.

2. Include sample training and knowledge transfer plans.

51. 4 2.5 Training Environments

1. Describe the types of training environments the Contractor will setup to support training delivery.

2. Describe how training data is created, loaded, and refreshed in the training environments.

3. Describe how the environments will be maintained and supported during the entire project.

52. 4 2.8 and 2.9

Training Curriculum

1. Describe the various types of curriculum and training materials created to support the System and the type of delivery (WBT, instructor led, other methods).

2. Describe how these materials support a blended learning approach and various user groups around the state.

3. Describe what tools will be used to develop training materials and web-based training.

4. Describe the format used to deliver electronically editable training materials to SCDMV.

Attachment A - Response Requirements Revision 2 Page 13 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit

5. Describe the solution for web-based training.

6. If recommending an alternative learning management system, explain the benefits to the SCDMV provide associated pricing within the pricing spreadsheet on the “Deliverables” worksheet under the “Optional Deliverables” section.

53. 4 3.1 Train-the-Trainer 1. Describe the methodology used for a train-the-trainer approach.

2. Explain how the SCDMV trainers will be supported while they deliver training.

54. 4 3.3 UAT Training 1. Describe the approach for training the UAT testers.

2. Describe the level of training materials and details it deems appropriate to support UAT training.

55. 4 3.5

Proficiency Test and Reports

Describe the tools the Contractor will develop or use for proficiency testing and reporting

56. 4 6 Knowledge Transfer

1. Describe the approach for continuous knowledge transfer throughout the project lifecycle.

2. Submit a sample Knowledge Transfer Plan

57. 4 N/A Requirements not Met

By submitting an offer, Contractor agrees to meet all requirements of the solicitation, including all appendices. Confirm you meet all requirements of Appendix 4. Identify and explain any areas that cannot be met.

58. 5 1.0 Blueprint Overview Describe your overall solution for a seamless integration of all depicted systems in the Blueprint diagram. Include all hardware and software. Include both logical and physical descriptions of the proposed System. Include peripherals and other related components.

Describe how your solution will meet the goals of the SCDMV. Also describe:

Attachment A - Response Requirements Revision 2 Page 14 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit

1. How flexible is the proposed solution and its ability to support the issuance of other licenses?

2. How capable is the proposed solution’s ability to support transactions online? Is configuration necessary for every transaction?

3. How would you approach the SCDMV’s goal of making all transactions available online and what challenges do you foresee?

4. How would your proposed solution be used to support external or supplementary systems that leverage the data in your proposed System solution?

For example, what if the SCDMV wanted to create a specialized application server to support smartphone applications.

How would that external system write to and access data in your proposed solution?

5. Describe the features of your solution that will integrate future technologies to meet future, changing business needs.

6. Describe how the components of your solution can be leveraged across the Enterprise.

7. Describe your solution’s suggested implementation method, as well as future upgrades methods.

59. 5 4.0 Foundation Systems

1. Describe the implementation tools to be used and how they will be brought together to work as a comprehensive solution for this project.

2. Include a diagram from another project of similar size and scope that brings together multiple foundation systems as described in the Blueprint diagram

3. Describe best practices your team has developed for designing solutions that

Attachment A - Response Requirements Revision 2 Page 15 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit bring together similar types of foundation systems on other projects.

4. Describe the software and solution that will be implemented to support the functions described in the following sections:

a. 4.1 Electronic Correspondence

Exchange

b. 4.2 Electronic Forms (E-Forms)

c. 4.3 Electronic Signature

d. 4.4 Document Composition

e. 4.5 Reporting and Analysis

f. 4.6 Interface Management

g. 4.7 Workflow Management

h. 4.8 Business Rules Manager

i. 4.9 Access Control

j. 4.10 Scanning and Imaging

k. 4.11 Data Quality

l. 4.12 Operational Database

m. 4.13 Data Warehouse

n. 4.14 Document and Image Repository

60. 5 5.0 Base Systems 1. Describe how the Base Systems will be designed to deliver functionality across multiple departments, locations, and businesses.

2. Describe the software and solution that will be implemented to support the functions described in the following sections:

a. 5.1 Customer Management

b. 5.2 Identity Management

c. 5.3 Case Management

d. 5.4 Web-Based Portal – Describe how the initial releases will support the existing list of functionality and how later releases can be expanded to accommodate all transactions.

e. 5.6 Self-Service Terminal

Attachment A - Response Requirements Revision 2 Page 16 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit

f. 5.11 Knowledge and Skill Test platform

g. 5.12 Vehicle Management

h. 5.13 Insurance Compliance

i. 5.14 Business Inspection

Management

j. 5.15 Inventory Management

k. 5.16 Plate Management

l. 5.17 Licensing Management

m. 5.18 Suspension and Restoration

n. 5.19 Knowledge Management

o. 5.20 Financial Management

p. 5.21 Point of Sale

q. 5.22 Fraud and Investigation

Management

r. 5.23 Audit Management

3. Describe how the software and solution will integrate with the current systems to support the functions described in the following sections:

a. 5.5 Customer Information Center

(website)

b. 5.7 Call Center Management

c. 5.24 Contract Management

d. 5.25 Learning Management platform

61. 5 5.8 Digital Access 1. Describe the software and solution that will be implemented to support the functions described in 5.8 Digital Access.

2. Describe how the solution will work with the various formats used by various mobile devices.

62. 5 5.9 and 5.10

Appointment Management, Queuing and Scheduling Management

Describe the software and solution that will be implemented to support the functions described in 5.9 Appointment Management and Queuing 5.10 Scheduling Management.

Attachment A - Response Requirements Revision 2 Page 17 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit

63. 5 6.0 Business Systems Describe how your approach creates configurable functionality across all the business applications.

64. 5 N/A Requirements Not Met

By submitting an offer, Contractor agrees to meet all requirements of the solicitation, including all appendices. Confirm you meet all requirements of Appendix 5. Identify and explain any areas that cannot be met.

65. 6 2 Introduction Describe how your solution and system design process will deliver a standard transaction-based system that meets the SCDMV Standard Transaction Model goals.

Describe how your system can provide a capability for the customer to review and approve the transaction.

66. 6 3 Standard Transaction

Describe your solution’s ability to support multiple transaction models as defined in a standardized way across SCDMV to support the business functionality.

67. 6 4 Customer Initiated Model

1. Describe your approach to meeting the requirements for the Customer Initiated model.

2. Describe your approach for meeting the requirements for pending transactions.

68. 6 5 SCDMV Employee/ Authorized Agent Assisted Model

Describe your approach to meeting the requirements for SCDMV Employee/Authorized Agent Assisted model.

69. 6 6 Central Office Model

Describe your approach to meeting the requirements for Central Office model.

70. 6 7.1 Batch Processing Describe your approach to meeting the requirements for Batch Processing support.

71. 6 7.2 Web Services Interface

Describe your approach to meeting the requirements for Web Services Interface support.

72. 6 N/A Requirements not Met

By submitting an offer, Contractor agrees to meet all requirements of the solicitation, including all appendices. Confirm you meet

Attachment A - Response Requirements Revision 2 Page 18 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit all requirements of Appendix 6. Identify and explain any areas that cannot be met.

73. 7 2 Customer Relationship Management (CRM) – DMV View

(“SCDMV 360”)

1. Describe how your solution and system design process will deliver a complete 360-degree view of the customer, and customer relationship management capabilities.

2. Demonstrate with screenshots how the customer’s 360-degree view will be visible to the SCDMV employees and how they will be able to manage this view.

74. 7 3 Customer Portal Account Access / Management – Customer View (“My DRIVE”)

1. Describe how your solution and system design process will deliver a complete 360-degree view of the customer, managing various customer profiles.

2. Describe how the business customers will differ from individual customers.

75. 7 4 Identity Verification and Access Management

Describe how your solution will meet the requirements for identity verification and access management.

76. 7 5 Customer Communication and Correspondence

1. Describe how your solution will track and manage contacts for customers.

2. Describe how your solution will track and manage communication between the customer and the SCDMV across all channels.

3. Describe how your solution will handle all undelivered notifications.

4. Describe your solution’s capability to assign a tracking mechanism to allow status updates of incoming mail and attach them to the customer’s record.

77. 7 6 Appointment, Scheduling and Queuing Management

Describe how your solution will track and manage the appointment and scheduling needs of SCDMV and their customers.

78. 7 7 Inventory Management of Customer Products

Describe how your solution will track and manage inventory requirements of the

Attachment A - Response Requirements Revision 2 Page 19 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit

SCDMV and how it will interface with external systems and partners.

79. 7 8 Insurance Verification & Reporting

1. Describe how your solution will support insurance related functionality for individual customers and their vehicles or integrate with the existing SCDMV solution.

2. Describe how your solution will meet the needs of SCDMV for Business Customer’s Insurance.

80. 7 9 Quality Assurance Describe how your solution will support SCDMV Quality Assurance Requirements.

81. 7 10 Auditing Describe how your solution will support the auditing requirements of the SCDMV and help the auditors to schedule, perform and manage the entire audit process.

82. 7 11 Investigation Describe how your solution will support the investigation requirements of the SCDMV.

83. 7 12 Fraud Detection & Remediation

Describe how your solution will help identify fraud and help with the remediation process and case management as it relates to fraud detection and its remediation.

84. 7 13 Customer Product Request (Customer Records)

1. Describe how your solution will help meet the needs for various record requests received and processed at the

SCDMV.

2. Describe how the various types of customer products will be categorized and identified in the system and trigger a workflow to the appropriate SCDMV employees.

85. 7 14 Covert, Confidential, & Undercover

Describe your approach to meeting the requirements in this section.

86. 7 15 Renewal Notification

1. Describe how your solution will handle the renewal notification generation.

2. Describe how your solution will work with the County offices to handle their tax notice requirement.

Attachment A - Response Requirements Revision 2 Page 20 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit

3. Describe your solution’s capability to send email and SMS text message notifications to the customers and how it will be sent via the customer account portal.

4. Describe how the returned/undelivered notification is reflected on customer’s profile.

87. 7 16 Payment Processing

Describe how your solution will handle the payment processing requirements for

SCDMV.

88. 7 17 Document/Image Capture, Storage, & Retrieval

1. Describe how your solution will handle document / image capture, storage and retrieval requirements for SCDMV.

2. Describe your solution’s capability to work with third-party Enterprise Content Management (EMS) software / solution.

3. Describe how your solution will manage access to specific items held within the document repository dependent on the authorized SCDMV employee or authorized agent’s role (RBAC).

89. 7 17 Workflow Processing

Describe how your solution will handle the workflow processing requirements for

SCDMV.

90. 7 19 Reporting Requirements

Describe how your solution will handle the standard and ad-hoc reporting to meet SCDMV’s needs.

91. 7 20 Correspondence Requirements

1. Describe how your solution will meet the needs of SCDMV as outlined in the overview.

2. Describe how your solution will handle letters and templates to meet SCDMV’s needs.

92. 7 N/A Requirements not Met

By submitting an offer, Contractor agrees to meet all requirements of the solicitation, including all appendices. Confirm you meet all requirements of Appendix 7. Identify and explain any areas that cannot be met.

Attachment A - Response Requirements Revision 2 Page 21 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit

93. 8 All Driving Privilege Management

Describe how your solution will manage the driving privileges, endorsements, and restrictions required in the system and how it is expandable. Include a screenshot(s) demonstrating this functionality.

94. 8 3 General Features 1. Describe how your system will meet each of the topics in this section.

2. When appropriate, include screenshots demonstrating functionality.

95. 8 4 Driver's license 1. Describe how your solution will manage the overall process of issuing, exchanging, and regulating non-commercial driver’s licenses to customers, including functions that can be completed through Self- Service Transactions.

2. Describe how your solution will manage the overall process of issuing, exchanging, and regulating commercial driver’s licenses.

3. Describe how your system will process the graduated license program.

96. 8 5 Identification Card Describe how your solution will manage the overall process of issuing, exchanging, and regulating identification cards to customers, including functions that can be completed online and other channels.

97. 8 6 Permits 1. Describe how your solution supports the process of issuing, exchanging, and regulating beginner’s permits.

2. Describe how your solution supports the process of issuing, exchanging, and regulating commercial learner’s permit.

98. 8 7 Motorcycle License Describe how your solution will manage the overall process of issuing, exchanging, and regulating motorcycle licenses to customers, including functions that can be completed through self-service transactions.

99. 8 8 Moped License Describe how your solution will manage the overall process of issuing, exchanging, and regulating moped licenses to customers, Attachment A - Response Requirements Revision 2 Page 22 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit including functions that can be completed through self-services transactions.

100. 8 9 Testing 1. Describe how your solution will monitor knowledge & skill testing as required in the System and the approach to interfacing with such systems during the licensing process.

2. Describe how your system will interface with the existing testing system to receive and use the test results.

3. Include a screenshot demonstrating this functionality.

101. 8 11 Driver Photos 1. Describe your solution’s ability to store and display the captured photos and signatures from the third-party system as part of the licensing process.

2. Describe your solution’s ability to manage the photo database and initiate transactions which are sent to a central issuance facility.

102. 8 N/A Requirements not Met

By submitting an offer, Contractor agrees to meet all requirements of the solicitation, including all appendices. Confirm you meet all requirements of Appendix 8. Identify and explain any areas that cannot be met.

103. 9 2 System Enhancements and Improvements

1. Describe the driver enforcement and compliance-related functionality of your products and how it will support the system enhancement and improvement sought by the SCDMV.

2. Describe how your solution will provide the SCDMV employee/authorized agent or customer with guidance in clearing multiple suspensions on a customer’s record.

3. Describe how your solution will automate the dispersal of suspension and reinstatement notifications, medical packets, and notifications for skills tests.

Attachment A - Response Requirements Revision 2 Page 23 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit

104. 9 3 Violations Describe how your solution shall support the processing of violations and citations received from external agencies and update the customer’s record accordingly (as described in the Violations section).

105. 9 4 Ticket Processing 1. Describe how your solution will interface with the appropriate third-party system to implement an automated electronic ticket process as well as a manual ticket process.

2. Describe how your solution will monitor the ticket process to provide statistics on factors impacting the process. These statistics must be fully configurable by

SCDMV.

106. 9 5 Event Processing Describe how your solution will receive, and process events as described in the Event Processing section as well as update a customer’s record accordingly.

107. 9 5.3 Points Assessment Describe your solution's capability to manage the addition and removal of points to a record as well as maintaining points thresholds on a record.

108. 9 6 Suspension Processing

1. Describe how your solution will meet the suspension processing requirements including offense escalations.

2. Describe how your solution will process and maintain accident suspensions based on the driver at-fault, driver/primary owner identity, and the verification of insurance of all parties.

109. 9 7 Hearing and Appeals

Describe your solution’s capability to receive and process both the requests and results of hearings and appeals while notifying the appropriate parties throughout the process.

110. 9 8 Medical Condition Processing

1. Describe your solution’s ability to verify medical packets received and prepare them for the review process.

Attachment A - Response Requirements Revision 2 Page 24 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit

2. Describe how your solution will issue medical packets to customers dependent on the channel the packet was requested.

111. 9 9 Ignition Interlock Processing

1. Describe how your solution will provide the capability to add, record, and remove an ignition interlock installation requirement to a customer’s record.

2. Describe how your solution will interface with authorized vendors to add ignition interlock installations electronically.

112. 9 10 Compliance Processing

Describe how your solution will display when a customer is eligible for a temporary alcohol license, a provisional license, and/or a route restricted license as well as what requirements must be met before the customer becomes eligible.

113. 9 11 Reinstatement Processing

1. Describe how your solution will process reinstating driving privileges and automatically generate notification of reinstatement to the customer.

2. Describe how your solution will provide a correspondence letter for instances when a customer has multiple events affecting their record.

3. Describe how your solution will support the eligibility tracking, setup and management, and resolution of a payment plan to provide the reinstatement of driving privileges for a customer’s record.

4. Describe how your solution will automate and monitor the reinstatement of driving privileges for Driver Suspension Eligibility Week (DSEW). Demonstrate a solution that is fully configurable by SCDMV.

114. 9 12 Accident Reporting and Processing

1. Describe how your solution will implement an automated electronic accident entry process as well as a manual process while capturing the defined details from the Accident Reporting and Processing section.

Attachment A - Response Requirements Revision 2 Page 25 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit

2. Describe how your solution will monitor the accident entry process to provide statistics on factors impacting the process. These statistics must be configurable by SCDMV.

115. 9 13 CDL / Driver Compliance

1. Describe how your solution will verify the accuracy of CDL medical certifications against FMCSA’s database to ensure accurate and complete information.

2. Describe how your solution will receive submitted self-certifications from CDL drivers electronically and manually, process the self-certification, and maintain the customer’s record accordingly.

116. 9 14 Inventory - Citation Describe how your solution will manage and monitor serialized inventory items to authorized law enforcement agencies as well as manage missing or damaged inventory as described in the Inventory section.

117. 9 15 Financial Responsibility

1. Describe how your solution will manage the tracking and validation of insurance coverage through the insurance verification system and process alerts on a customer’s record when coverage cannot be validated.

2. Describe how your solution will facilitate the suspending and reinstatement of uninsured motorists.

3. Describe how your solution will oversee the reception, maintenance, and return of surety bond while processing beneficiary claims and surety bond return requests.

118. 9 N/A Requirements not Met

By submitting an offer, Contractor agrees to meet all requirements of the solicitation, including all appendices. Confirm you meet all requirements of Appendix 9. Identify and

Attachment A - Response Requirements Revision 2 Page 26 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit

119. 10 2.0 General Vehicle Management

1. Describe how your system supports tracking each vehicle as a unique entity from initial acquisition for final disposition.

2. Display how your system performs VIN validation, decoding, and duplicate checks with screenshots or diagrams.

3. Demonstrate the capability to create South Carolina-specific VINs and link vehicles to related data (titles, registrations, etc.).

4. Describe how your system categorizes and manages vehicles by type.

120. 10 3.0 Vehicle Inquiry 1. Describe an innovative solution that supports the inquiry of vehicle, vehicle history, and customer data.

2. Display the results of vehicle and customer data inquiries, highlighting access restrictions based on user roles.

3. Demonstrate the system’s ability to integrate with third party vendors for real-time inquiry and data exchange.

4. Describe/display how your system displays a customer’s complete listing of all titled and registered vehicles.

121. 10 4.0 Title Management 1. Describe how your system completes a request to title a vehicle and what innovative and efficient solutions your system offers.

2. Demonstrate the system’s ability to support in-state and out-of-state title transfers seamlessly.

3. Demonstrate how your system manages the VINs for multi-stage vehicles and mobile homes.

4. Describe how your solution ensures compliance with AAMVA standards for title branding.

Attachment A - Response Requirements Revision 2 Page 27 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit

5. Display examples of title branding workflows, title creation, title edits, and customer.

6. Describe the innovative capabilities of your system for managing electronic and digital titles.

122. 10 5.0 Registration 1. Describe your system’s ability to issue new registration types and plates.

2. Display the process for handling registration renewals and verification of county property tax payment.

3. Demonstrate how the system supports specialty and personalized plate requests, including offensive word list verification.

4. Describe how your system issues and manages permits and decal issuance for vehicle subsets excluded from a normal registration (e.g. Golf Carts, UTV’s ATV’s).

5. Describe how your system issues, assigns, and manages temporary vehicle registrations and plates.

6. Demonstrate how your system processes and manages vehicle registration suspensions and reinstatements.

123. 10 6.0 Lien Management 1. Describe how your system supports the addition of a single and multiple liens, lien release, and lien updates including utilizing both an Electronic Lien and Title (ELT) process and non-electronic lien format.

2. Demonstrate intuitive workflows for lienholder management, ensuring ease of use for SCDMV Employees, ELT Service Providers/Lenders, and vehicle owners.

3. Demonstrate automated notifications to vehicle owners and lienholders on relevant updates to the lien or vehicle that could impact the lien status.

Attachment A - Response Requirements Revision 2 Page 28 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit

124. 10 7.0 Placard Management

1. Describe innovative capabilities for issuing, renewing, and tracking disability and hearing-impaired placards.

2. Demonstrate how the system enables intuitive submission of medical certifications and online renewals for customers.

3. Demonstrate automated fraud detection and the ability to manage placards issued to businesses versus individuals efficiently.

4. Demonstrate the issuance of an Interim Placard (one issued to a customer while the regular Placard is being produced and shipped) either produced by an SCDMV Employee/Authorized Agent or through a self-service portal transaction.

125. 10 8.0 International Registration Plan

(IRP)

1. Describe how your solution supports the creation and management of IRP accounts.

2. Demonstrate efficient workflows for issuing apportioned plates, managing mileage reporting, and processing renewals.

3. Describe how your system facilitates compliance checks and intuitive customer service through the self-service portal.

4. Describe how your solution supports suspension of the account and vehicles for out-of-service compliance violations.

126. 10 9.0 International Fuel Tax Agreement

(IFTA)

1. Describe how your solution supports IFTA account management, including quarterly tax reporting, and issuance and monitoring of the decals.

2. Demonstrate how the system ensures efficiency in linking IRP and IFTA accounts and managing customer updates.

3. Demonstrate intuitive methods for customers to file tax returns and update fleet information through a self-service portal.

Attachment A - Response Requirements Revision 2 Page 29 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit

4. Demonstrate how the SCDMV employee will be able to view the tax returns and other relevant information on an IFTA account.

127. 10 10.0 Fleets, Leasing, Manufacturer, Rental, and Intrastate Commercial Vehicles

1. Describe your solution’s capabilities to manage fleets, including intuitive tools for adding, updating, and tracking vehicles.

2. Demonstrate innovative methods for customers to manage fleet data via an intuitive portal.

3. Demonstrate how your system manages the titling and registration of leased vehicles.

4. Demonstrate how your system will differentiate between interstate and intrastate fleets and how vehicles in these fleets will be visible on a fleet dashboard.

128. 10 11.0 Plate Management 1. Describe how your system manages a wide variety of plate types, including issuance, cyclic replacement, tracking, and renewal.

2. Demonstrate intuitive features for configuring plate designs, tracking inventory, and maintaining plate design history.

3. Demonstrate efficient real-time validation for personalized and specialty plate requests.

129. 10 12.0 Unified Carrier Registration (UCR)

1. Describe how your system tracks payments and compliance for Unified Carrier Registration (UCR).

2. Demonstrate an intuitive interface for managing UCR customer accounts and payment tracking.

130. 10 13.0 IRP and IFTA Audits 1. Describe your system’s capabilities to support efficient audits of IRP and IFTA accounts.

Attachment A - Response Requirements Revision 2 Page 30 of 45

Num

Appdx Sect Ref

Appdx Topic Title Response Requirements Page Limit

2. Demonstrate how your system provides intuitive access to audit data and simplifies handling of discrepancies.

131. 10 14.0 IRP and IFTA Permits

1. Describe how your system supports intuitive issuance of IRP and IFTA permits.

2. Demonstrate how the system efficiently processes temporary permits and integrates with IRP and IFTA account data.

132. 10 15.0 Transmittals 1. Describe your system’s capabilities for processing transmittals in an automated and manual manner.

2. Demonstrate how the system ensures efficient data updates, receipt, and processing of IRP and IFTA transmittals.

3. Demonstrate intuitive user tools for managing transmittal workflows and generating notifications.

133. 10 16.0 Certificate of Compliance

1. Describe how your system ensures efficient generation of Certificates of Compliance.

2. Describe how the Certificate of Compliance status is updated when an insurance update is received from the insurance verification vendor.

3. Demonstrate how the system simplifies compliance checks and enables intuitive customer self-service.

134. 10 17.0 Dealer Assignment Describe how your solution will capture and track dealer assignments and trigger an alert when a dealer assignment is missing when being exchanged between multiple dealers.

135. 10 N/A Requirements not Met

By submitting an offer, Contractor agrees to meet all requirements of the solicitation, including all appendices. Confirm you meet all requirements of Appendix 10. Identify and explain any areas that cannot be met.

136. 11 N/A Functional Requirements

Describe how your solution and…