INCENTIVES CODE RFP Answers to Proponents Questions€¦ · identified in the Incentives Code. (...

Answers to Proponents Questions

Request for Proposals to Implement Incentive Code into Single Business Portal RFP #2019-2020-001

1

INCENTIVES CODE RFP

Answers to Proponents Questions NOTE: The questions are presented exactly as submitted by each vendor; no changes or corrections were made. Orientation Meeting:

1. What version of CRM is being used? Microsoft Dynamics CRM 2013. It is hosted in DEDC's datacenter.

2. Where the historical data that will be uploaded to the system come from?

The sources include DEDC's CRM system and custom developments from any agency identified in the Incentives Code.

3. What system is being used to handle payments?

'Colecturía Virtual' from the Department of Treasury. 4. What is DDECs ERP system to issue payments?

'Colecturía Virtual' from the Department of Treasury. 5. Is the date (12/31/2019) the official launch date?

DEDC is expected to launch and comply on January 1, 2020. However, each proponent should present their timeline in order to meet the requirements stated in the RFP.

Fusionworks:

1. Will the company responsible for incorporating new Act 60-2019 flows into the system, be the same company that provides support and maintenance to the current system? Not necessarily.

2. Is DDEC looking to replace the company who’s providing these services under contract today? No.

3. Are the requirements included under section 4 of the RFP need to be quoted for all existing permits, incentives and other flows? No, requirements must be met for the transactions identified in the Incentives Code. Current permit flows must not be altered. (Reference in RFP - Section 4)



2

4. Will new process flows be able at project start? No, the business rules for each workflow are not established other than the process established by the Incentives Code; nonetheless, the exact requirements for each transaction will be addressed by the regulation to be issued.

5. Section 2 of the RFP talks about proponents submitting “financing options”, what do you mean/expect about that? The term 'financing options' refers to the cost associated to the design, development and implementation of the project. (Reference in RFP - Section 2)

6. Is DECC expecting on having all Act 6—2019 flows in production (MVP) by January 1, 2019? Would DDEC consider an alternate day as it is uncertain wether DDEC could formalize a contract by year’s end. DEDC is expected to launch and comply on January 1, 2020. However, each proponent should present their timeline in order to meet the requirements stated in the RFP.

7. Could you confirm the name and version of the CRM application that DDEC currently uses? Microsoft Dynamics CRM 2013. It is hosted in DEDC's datacenter.

Softek:

1. Can DDEC provide copy of the documents used in the actuall process for the transactions identify in the RFP? Yes.

2. How many forms will be implementend in the new solution for each transaction? As referred in Section 2.5, a minimum of 43 forms (or workflows) will be included.

3. Can you provide workflow of each transaction? No, each workflow will be defined by the proposed regulation for Act 60-2019.

4. Can you provide the manual of the actual solution? Yes.

5. Can you provide the actual regulation for each to the transactions? Regulations that exists before the Incentives Code can be provided, otherwise refer to Act 60-2019 Incentives Code.

6. Can you confirm the expected dates for the new solution go life? DEDC is expected to launch and comply on January 1, 2020. However, each proponent should present their timeline in order to meet the requirements stated in the RFP.



3

7. Can you indicate the number of transactions that will be being developed on the platform? As referred in Section 2.5, a minimum of 43 forms (or workflows) will be included.

8. Can you tell us which agencies, if any, information that the platform used are collected? Example: Agricultura, Comercio y Exportation, CRIM, OSIF, others. Any and all agencies that are included in the Incentives Code.

9. Can you provide us with the current design documentation of the existing platform? Yes, current design documentation exists. Yet a new design process is within the scope of this RFP.

10. Will the data that will be migrated be clean or should be clean as part of the proposal? Yes, data scrubbing will be necessary. It is possible that some data should be cleaned for migration purposes.

Evertec:

1. Are there any user registration requirements? Yes, including but not limited to: company information, representative information, among others.

2. Is the user universe segmented by category? (Individuals, corporations, promoters) Yes.

3. Will the application process be segmented by corresponding government? Agency or by economic sector? No.

4. Will the application approving agents be segmented by government agency? No, each transaction will have a defined internal workflow that may lead to an inter-agency process.

5. Which document attachments formats are accepted? No restrictions for format.

6. Will the application approval/denial process be online? Yes.

7. Does the application attached documentation have a retention policy? Yes. Minimum of 10 years retention.



4

8. Is the application review and approval process one and the same for all sectors? (Timelines and agents) No.

9. Will the users be notified of any denial/approval by electronic means?

Yes.

10. Are the users required to be notified of application status? (I.e. in progress) Yes.

11. Can users have or be part of more than one sector? (I.e. Manufacturing, Agriculture) Yes.

12. Will users be capable of printing and/or downloading reports? Yes.

13. Does this application require ADA act compliance? Yes.

14. Is this application required to have a 24/7 availability? Yes.

15. Is the application required to be developed in both English and Spanish languages? Yes.

16. Can a user apply for a grant or business opportunity once denied? Is there a waiting period? Yes; there is no waiting period.

17. Are the application documentation and instructions available for download? No.

18. Are there any geographical restrictions to access this application? No.

19. Do user sub accounts have predetermined roles? No; sub-accounts should be defined.

20. Is there a data retention policy? Minimum of 10 years retention.

21. Does the applicant require a notification or application status update after each step of the workflow is completed? Yes.



5

22. Will the application process workflow require to upload additional documentation?

Yes, additional documentation will vary from each transaction.

23. Will agency endorsements, recommendations be added electronically during the workflow by approving agents? Yes.

24. Are there any expected user concurrency metrics for user session management? Currently there is a limitation of 511 concurrent sessions. The expectation is to increase this requirement.

25. Are load and stress test required for implementation? Yes.

26. Can you elaborate more in Phase 1? Would it be to create a new one? or Modified the existing one? We intend to modify the existing one, however, DEDC is open to receive other proposals.

27. When you talk about Integration! Who will provide the Integration? What are the Requirements? etc. All transactions will be generated exclusively through SBP, and therefore, SBP's unique profile will be its main driver. In other words, any information in the unique profile should be available to be pre-populated in any SBP transaction.

28. Does the current system run in CRM? No, the current system does not run in CRM.

29. Does the migration from all data is contemplate? And what system are? Yes, the current CRM and other agency's custom developments.

30. Migration requires data transformation? Yes.

31. The RFP mention this Bellow, what phase is this for? Is this already in place? Can you elaborate more on this? These capabilities, to some degree, are currently in place in the SBP. DEDC expects to maintain or expand on some of the functional capabilities. (Reference in RFP - Other current functional capabilities in the SBP-Incentive section include: • State-of-the Art Security and Administration • Status history and tracking • Help Desk System with Live Chat



6

• Geographic Integration System (“GIS”) integration • Mobile friendly and responsive • Automated remoted inspection requests, such as by website and/or integrated voice response (“IVR”) • Electronic Plan Review Integration, with inspections and approvals capability • Ability to integrate with financial software (commercial or custom) • Ability to integrate with existing records management database (Oracle/SQL) • Integrated Cashiering/Automated Payment System (“APS”) tools and add-ins with online and in-person components • System-calculated fees and charges with manual adjustments • Robust and flexible search and display capabilities • Ability for users to create custom reporting and data extraction, including external dashboard reporting • Ability to automate generation of customized forms, letters, permits and licenses, among others • Digital connectivity and add-ons to allow interlink with external agencies that require inputs to the process).

32. HelpDesk? Full time or part time? DEDC will evaluate each proponent's services.

C2S Consulting:

1. Which other partner websites does DEDC anticipate will need to be consulted to implement this required functionality? Are there documented and available interfaces to access the data from these partner websites, for example, web services or direct database access? Is connectivity in place to access them? All transactions will be generated exclusively through SBP, and therefore, SBP's unique profile will be its main driver. In other words, any information in the unique profile should be available to be pre-populated in any SBP transaction. (Reference in RFP - Section 2.5.1 User Profiles – The third bullet states: These profiles can be created by the user or pre-populated in the system if the user has made transactions previously in other partner websites.)

2. Which data sources are anticipated that SBP will need to pull historical data from? Are these sources hosted within DEDC or externally? Are all of these electronic sources, such as databases, web services, electronic documents, The sources include DEDC's CRM system and custom developments from any agency identified in the Incentives Code. (Reference in RFP - Section 2.5.1 User Profiles – The fourth bullet states: The SBP should migrate the historical data (current decrees, amendments, etc.) to the Unique Profile. This data is available from various sources.)



7

3. What type of integration does this refer to, query data from the PRITS TIM Data Platform to show to the user, send data processed in the SBP back to the PRITS TIM Data Platform for storage, or other type of integration? Are there documented and available interfaces to interact with the PRITS Data Platform? PRITS will determine the functional requirements for this notification engine. (Reference in RFP - Section 2.5.2 User Dashboard – The second bullet states: Should be integrated with PRITS TIM Data Platform.)

4. What type of integration is required, for instance, should the SBP send notifications using PRITS Notification Engine facilities? Are there documented and available interfaces to interact with the PRITS Notification Engine? Is connectivity in place to accomplish this? PRITS will determine the functional requirements for this notification engine. (Reference in RFP - Section 2.5.3 System Notifications and Communication – The third bullet states: Should be integrated with PRITS Notification Engine.)

5. How many other additional workflows does DEDC estimate or anticipate may be identified after consulting with and gathering information from these other agencies? As a result of the initial assessment, there were 43 workflows or transactions identified; nevertheless, the final number of workflows will depend on the designs agreed upon. Three main workflows are mentioned (Reference in RFP - Section 2.5.5 Transaction Types – The second paragraph after the first three bullets states: As part of the initial assessment of Act 60-2019, we identified 43 transaction workflows. However, other transactions might be identified in the design process. Also, the last line after the workflow breakdown by sector table states: This list might be subject to change as information is gathered from other agencies.)

6. Which CRM system is being used? Where is it hosted? Microsoft Dynamics CRM 2013. It is hosted in DEDC's datacenter. (Reference in RFP - Section 2.6 Functional Requirements – Back End – The CRM Software Reports bullet states: The SBP should be able to access the data in the current CRM system used to manage Act 73-2008, Act 83-2010 and Act 273 applications.)

7. Which ERP, CRM and Treasury systems are anticipated that the SBP should interface with? Are there documented and available interfaces to interact with these systems? Where are they hosted? Is connectivity in place to accomplish this? DEDC's and any other agencies' ERP that is used to process the corresponding payments. The interfaces do not exist. (Reference in RFP - Section 2.6 Functional Requirements – Back End – The Interfaces bullet states: The SBP shall be able to interface with software of the other entities (ERP, CRM and Treasury))



8

8. Is DEDC’s expectation that the selected proponent must design, implement, test and document a disaster recovery and backup solution above and beyond what may currently be in place for the current SBP platform hosted in the Azure Cloud? Or does this refer to updating the current disaster recovery and backup plan and procedures to include the newly developed components? Yes. (Reference in RFP - Section 4.5.3.5 Training & Installation Support – the last bullet indicates (i) Disaster Recovery and Backup configuration)

9. Detail types of Clients (Users) access the system and what are their profiles? Number of current users and their roles? How security and access of external users is currently managed if there are any? Currently, the system does not have a segregation of users. However, this should be considered as part of the design phase. (Reference in RFP - Users of Systems and Security)

10. Is there a functional team already established by the Agency to start the project? Are the business rules that apply during the Workflow work established - (Currently the Times are fulfilled) What is the level of integration with other Internal/ External applications (Banks, Finance, GIS Services, Government Agencies, etc)? Participants and/ or Applicants can submit (submit) documents digitally. No, there is no functional team; there is a steering committee established by the agency. However, there is an expert identified in DEDC's team for each transaction type. No, the business rules for each workflow are not established other than the process established by the Incentives Code; nonetheless, the exact requirements for each transaction will be addressed by the regulation to be issued. SBP is currently integrated with 'Colecturía Virtual' from the Department of Treasury for the transaction payments. Yes, participants and/or applicants can submit documents digitally. (Reference in RFP - Functionals Aspects)

11. What is the current volume of the data? - (Cases) • Current data quality (part of this scope) • Data Migration (part of this scope) Special Digitized Forms already established? What services of notifications and / or Alerts and which? There is a repository of digital documents and images and what capabilities do you currently have? What volume of reports currently exists? Current volumes of data can be provided for the existing transactions in SBP, CRM and internal DEDC systems. Forms for each current transaction are available. Notifications and alerts will vary from each transaction and will be defined in the design process, which is part of this scope. Yes, there is a repository of digital documents and images; technical capabilities are available in the RFP document. Currently, there are no administrative reports available in SBP except for a Dashboard designed to inform PRITS. (Reference in RFP - Volume and data capabilities)



9

E3 Consulting:

1. What is meant by financing options? Financing? Fee per transaction? The term 'financing options' refers to the cost associated to the design, development and implementation of the project. (Reference in RFP - 2.0 Scope of Services Financing Options)

2. Does the law allow fee per transaction? Yes. (Reference in RFP - 2.0 Scope of Services Financing Options)

3. What if these changes alter the scope and timeline of the project? Each modification in scope or timeline will be subject to the change request process established by DEDC's PMO office and subject to the Committee's evaluation and recommendation. (Reference in RFP - 2.0 Scope of Services The DEDC reserves the right to adjust the conceptual design as needed to ensure compliance with Act 60-2019. Given that the rules and regulations for Act 60-2019 are under development, the transactions and processes outlined in the RFP might be subject to change and impact the design process.)

4. Will all sections require the same information? No, each transaction's required information and/or additional documents will vary. (Reference in RFP - 2.3Act 60-2019 – New Incentive Code Moreover, it creates nine (9) strategic economic segments: Individuals, Exports, Financial and Insurance Services and investments, Visitors Economy, Infrastructure, Creative Industries, Manufacturing, Agriculture, and Entrepreneurship.)

5. Are these segments front end or back end workflows? Both, each transaction will need a front-end and back-end process. (Reference in RFP - 2.3Act 60-2019 – New Incentive Code Moreover, it creates nine (9) strategic economic segments: Individuals, Exports, Financial and Insurance Services and investments, Visitors Economy, Infrastructure, Creative Industries, Manufacturing, Agriculture, and Entrepreneurship.)

6. Three main workflows are mentioned yet it is not clarified how this will be divided into products. Please clarify As a general rule, each transaction identified in the Incentives Code will need to include at least one of these three workflows. On these main workflows we have identified the following: 20 Preferential Tax Decrees, 3 Tax Credits and 7 Cash Grants. (Reference in RFP - 2.3Act 60-2019 – New Incentive Code A primary analysis was performed, and we have concluded that there are three main workflows that can be optimized: Preferential Tax Decrees., Tax Credits, and Cash Grants)



10

7. What is the main product? These 3 or the 9 segments?

The main product is defined by everything contained in the Incentives Code. (Reference in RFP - 2.3Act 60-2019 – New Incentive Code A primary analysis was performed, and we have concluded that there are three main workflows that can be optimized: Preferential Tax Decrees., Tax Credits, and Cash Grants)

8. Will there be a product for each combination of for example a Tax Decree and Economic segment? Or Will they all be conglomerated into segments or main workflows? As a general rule, each transaction identified in the Incentives Code will need to include at least one of these three workflows. (Reference in RFP - 2.3Act 60-2019 – New Incentive Code A primary analysis was performed, and we have concluded that there are three main workflows that can be optimized: Preferential Tax Decrees., Tax Credits, and Cash Grants)

9. When you say workflows do you mean front end or back end? Both, each transaction will need a front-end and back-end process. (Reference in RFP - 2.3Act 60-2019 – New Incentive Code A primary analysis was performed, and we have concluded that there are three main workflows that can be optimized: Preferential Tax Decrees., Tax Credits, and Cash Grants)

10. What are the requirements? All the requirements established in the RFP document will help comply with the client centric vision and principles that are to be implemented that will be discussed and confirmed during the design phase. (Reference in RFP - 2.4 Implementation Stages The SBP needs to be adjusted to the client centric vision and principles. Adjustments will have to be implemented in the Front and Back End of the SBP.)

11. Do you want companies to be able to create their own profiles to be shared by their employees with one username and password? No, each user should have their own user and password. (Reference in RFP - 2.5.1 User Profiles The SBP should have Unique Profile for every user whether the user is: (a) Applicant, (b) Business (ie. corporations, Small businesses, etc.), (c) Promoters or (d) Authorized Professionals.)

12. Would these profiles be created using EIN? Yes, in the case of legal entities. (Reference in RFP - 2.5.1 User Profiles The SBP should have Unique Profile for every user whether the user is: (a) Applicant, (b) Business (ie. corporations, Small businesses, etc.), (c) Promoters or (d) Authorized Professionals.)



11

13. Who is authorized to give access to whom?

Administrative roles will be defined in the design process. (Reference in RFP - 2.5.1 User Profiles The user should have the capability to grant access to its Unique Profile to other users in the platform as further described and agreed upon in the design while following security protocols.)

14. Does the person that you give access have their own user profile with social security

number? Administrative roles will be defined in the design process. (Reference in RFP - 2.5.1 User Profiles The user should have the capability to grant access to its Unique Profile to other users in the platform as further described and agreed upon in the design while following security protocols.)

15. What is the interface?

All transactions will be generated exclusively through SBP, and therefore, SBP's unique profile will be its main driver. In other words, any information in the unique profile should be available to be pre-populated in any SBP transaction. (Reference in RFP - 2.5.1 User Profiles These profiles can be created by the user or pre-populated in the system if the user has made transactions previously in other partner websites. The Incentive Interface needs to be able to identify the existing fields in the user profile in order to pre-populate the application forms)

16. What are the other websites? To clarify Section 2.5.1 of the RFP, SBP will be the only website that will generate transactions, therefore, SBP should have the ability to prepopulate fields from the unique profile to any SBP transaction. (Reference in RFP - 2.5.1 User Profiles These profiles can be created by the user or pre-populated in the system if the user has made transactions previously in other partner websites. The Incentive Interface needs to be able to identify the existing fields in the user profile in order to pre-populate the application forms)

17. Do these other systems have a way for us to request data already setup? To clarify Section 2.5.1 of the RFP, SBP will be the only website that will generate transactions, therefore, SBP should have the ability to prepopulate fields from the unique profile to any SBP transaction. (Reference in RFP - 2.5.1 User Profiles These profiles can be created by the user or pre-populated in the system if the user has made transactions previously in other partner websites. The Incentive Interface needs to be able to identify the existing fields in the user profile in order to pre-populate the application forms)



12

18. Which are the various sources of data?

The sources include DEDC's CRM system and custom developments from any agency identified in the Incentives Code. (Reference in RFP - 2.5.1 User Profiles The SBP should migrate the historical data (current decrees, amendments, etc) to the Unique Profile. This data is available from various sources.)

19. Would this require data scrubbing? Data back until when? Who has the data? Does this

include paper data? Yes, data scrubbing will be necessary. Historical data will be needed varying on the transaction type; it can be from 10-20 years from the current date. Data will be migrated from the CRM system and custom developments from any agency identified in the Incentives Code. If the only source of information or any data that is required and is not included in the CRM system or in any other custom developments, then paper data might be needed for migration. (Reference in RFP - 2.5.1 User Profiles The SBP should migrate the historical data (current decrees, amendments, etc) to the Unique Profile. This data is available from various sources.)

20. Do these other systems have a way for us to request data already setup? To clarify Section 2.5.1 of the RFP, SBP will be the only website that will generate transactions, therefore, SBP should have the ability to prepopulate fields from the unique profile to any SBP transaction. (Reference in RFP - 2.5.1 User Profiles The SBP should migrate the historical data (current decrees, amendments, etc) to the Unique Profile. This data is available from various sources.)

21. Do you want to save documents to the user’s/company’s profile? Yes, this is a strict requirement. (Reference in RFP - 2.5.1 User Profiles When the user applies for a type of decree, amendment or any service the SBP should be able to: a) identify all the transaction requirements; b) assess what requirements are readily available in the system and current; c) ask the user only for the documents and information that are missing in the application. This functionality is essential to improve user experience.)



13

22. What documents are required?

The documents required will vary with each transaction, although, some of these documents will be strictly required for each company's/ individual's unique profile. For example, Negative Debt Certificate or Filling of Income Tax Returns issued by the Department of Treasury. (Reference in RFP - 2.5.1 User Profiles When the user applies for a type of decree, amendment or any service the SBP should be able to: a) identify all the transaction requirements; b) assess what requirements are readily available in the system and current; c) ask the user only for the documents and information that are missing in the application. This functionality is essential to improve user experience.)

23. What will be each document’s expiration date?

Each document's expiration date will vary, depending on the certification. (Reference in RFP - 2.5.1 User Profiles When the user applies for a type of decree, amendment or any service the SBP should be able to: a) identify all the transaction requirements; b) assess what requirements are readily available in the system and current; c) ask the user only for the documents and information that are missing in the application. This functionality is essential to improve user experience.)

24. What is the matrix for required documents per product? The matrix will be defined by the regulation and internal assessments. (Reference in RFP - 2.5.1 User Profiles When the user applies for a type of decree, amendment or any service the SBP should be able to: a) identify all the transaction requirements; b) assess what requirements are readily available in the system and current; c) ask the user only for the documents and information that are missing in the application. This functionality is essential to improve user experience.)

25. Will you save ALL documents required for all transactions? Yes. (Reference in RFP - 2.5.1 User Profiles When the user applies for a type of decree, amendment or any service the SBP should be able to: a) identify all the transaction requirements; b) assess what requirements are readily available in the system and current; c) ask the user only for the documents and information that are missing in the application. This functionality is essential to improve user experience.)

26. What certifications? All certifications required as part of the application process. That includes, but is not limited to, all governmental certifications (Treasury, Municipal Revenue Collection Center, Municipality, among others) and all internal (DEDC) certifications needed to complete the transactions. These documents/ certifications will be confirmed during the design phase.



14

(Reference in RFP - 2.5.3 System Notification and Communication The SBP should be able to have all notifications and communications related to the user applications easily accessible. All stakeholders in the approval process should have visibility of the stage where the application or request is at. The SBP should also be to notify the user when: (a) certification is about to expire; (b) annual reports are due; (c) changes in the terms, rules or regulations take place; and (d) there is a non- compliance with the terms of decree.)

27. What is the notification engine? PRITS will determine the functional requirements for this notification engine. (Reference in RFP - 2.5.3 System Notification and Communication Should be integrated with PRITS Notification Engine)

28. Do you have 9 products with a total of 43 front-end workflows, and 3 backend workflows per product or 43 products with 43 front end workflows and 3 backend workflows? The main product is defined by everything contained in the Incentives Code. There are 9 economic sectors for which we have identified 43 transactions or workflows. These workflows can be for tax decrees, tax credits, cash grants, certifications, etc. (Reference in RFP - 2.5.4 Workflows All of the incentive transactions shall be digitalized and optimized as much as possible. This includes and is not limited to the following: (a) all fields in the application forms should be completed online; (b) capability to upload attachments; and (c) capability for online payment.)

29. Where will negotiation take place - in platform or outside? In the platform. (Reference in RFP - 2.5.5 Transaction Types Extraordinary transactions - These transactions are applications that do not adhere to the standard forms and require additional information, special negotiations with the Secretary, and/or a negotiation, evaluation or consultation processes with an external agency. External agencies must submit responses through the SBP adhering to the times specified in the code. Extraordinary transactions can result in special concessions after a negotiation process.)

30. Which transactions fall under this category? Which products? As a general rule, all transactions will include an ordinary, extraordinary and expedited process in the back-end workflow. (Reference in RFP - 2.5.5 Transaction Types Extraordinary transactions - These transactions are applications that do not adhere to the standard forms and require additional information, special negotiations with the Secretary, and/or a negotiation, evaluation or consultation processes with an external agency. External agencies must submit responses through the SBP adhering to the times specified in the code. Extraordinary transactions can result in special concessions after a negotiation process.)



15

31. Do you have 9 products with a total of 43 front-end workflows, and 3 backend workflows per product or 43 products with 43 front end workflows and 3 backend workflows? As a general rule, all transactions will include an ordinary, extraordinary and expedited process in the back-end workflow. (Reference in RFP - 2.5.5 Transaction Types As part of the initial assessment of Act 60-2019, we identified 43 transaction workflows. And The code transactions can be processed as: (a) Ordinary, (b) Extraordinary and (c) Expedited.E98)

32. What do you mean by 6 transactions? Create a product of Tax credit with 6 different front-end versions? As stated in section 2.5 of the RFP, there are 6 Tax Credits transactions identified. (Reference in RFP - 2.5.5 Transaction Types Tax Credit Applications – These applications are completed manually today and require constant communication between the client and the DEDC. This transaction should be an automated workflow. (Transactions: 6))

33. What do you mean by 7 transactions? Create a product of Cash grants with 7 different front-end versions? What about the economic segments? Where do they fit here? As stated in section 2.5 of the RFP, there are 7 Cash Grants transactions identified. (Reference in RFP - 2.5.5 Transaction Types Cash Grants - These transactions currently require the user to submit the forms as attachments, the client could benefit from having blank fields that they can fill out and submit non-standard documents. (Transactions: 7))

34. What do you mean by 4 transactions? Create a product of Cash grants with 4 different front-end versions? What about the economic segments? Where do they fit here? As stated in section 2.5 of the RFP, there are 4 programs transactions identified. (Reference in RFP - 2.5.5 Transaction Types Programs – These include subsidies, marketing incentives and sponsorships (Transactions: 4).)

35. Does it travel to external agencies? Yes. (Reference in RFP - 2.5.5 Transaction Types Certifications – These transactions are required for Difficult-To-Recruit Professional and Scientist/Researchers (Transactions: 4))

36. What is the hierarchy of sectors and which transactions fall under which category, subcategory, segment or transaction type? Refer to Section 2.5.6 of the RFP. (Reference in RFP - 2.5.6 Navigation structure by sector Navigation)

37. What fields are we to use for this ROI calculation? ROI calculation formula will vary for each transaction. Some fields may include, but not limited to: number of jobs generated, expected sales, total project investments, etc. Specific fields will be given as part of the design phase.



16

(Reference in RFP - 2.6 Functional Requirements - Back End Return-On-Investment (ROI) – The SBP should be able to calculate the ROI based on the information provided by the applicant. This ROI calculation will be used by the Administrative Officer and/or Legal counsel during the decree evaluation.)

38. Is there a defined formula to calculate the ROI? ROI calculation formula will vary for each transaction. Some fields may include, but not limited to: number of jobs generated, expected sales, total project investments, etc. Specific fields will be given as part of the design phase. (Reference in RFP - 2.6 Functional Requirements - Back End Return-On-Investment (ROI) – The SBP should be able to calculate the ROI based on the information provided by the applicant. This ROI calculation will be used by the Administrative Officer and/or Legal counsel during the decree evaluation.)

39. Will all transactions use the same data/formula? No. (Reference in RFP - 2.6 Functional Requirements - Back End Return-On-Investment (ROI) – The SBP should be able to calculate the ROI based on the information provided by the applicant. This ROI calculation will be used by the Administrative Officer and/or Legal counsel during the decree evaluation.)

40. Are external workflows defined? Yes. (Reference in RFP - 2.6 Functional Requirements - Back End Inter-Agency and Municipal Consideration– In the case of Ordinary Transactions, the SBP should transfer the case automatically to the next agency or process owner. In the case of Extraordinary Transactions, the case manager will channel the request to the respective process owner in the agency or municipality. The agencies or owners involved in the process include but are not limited to: Treasury, Municipalities, Health Department, Agriculture, PR Tourism Company and CRIM.)

41. Are these back-end workflows products? Or just internal cases per different product or segment? If so, are all these processes identical regardless of type of product applied for? Each transaction will have its own set of business rules that will cover the entire process. (Reference in RFP - 2.6 Functional Requirements - Back End Inter-Agency and Municipal Consideration– In the case of Ordinary Transactions, the SBP should transfer the case automatically to the next agency or process owner. In the case of Extraordinary Transactions, the case manager will channel the request to the respective process owner in the agency or municipality. The agencies or owners involved in the process include but are not limited to: Treasury, Municipalities, Health Department, Agriculture, PR Tourism Company and CRIM.)



17

42. Will these priorities be defined manually by the Secretary or base on automated rules? Both. (Reference in RFP - 2.6 Functional Requirements - Back End Selection of Project Priority – Section 3000.01 provides for the Secretary of DEDC to establish priorities of processing applications. This capability should be incorporated in the system.)

43. Would this be an additional interface with Hacienda? When? After final approval? Yes, as part of the workflow process. (Reference in RFP - 2.6 Functional Requirements - Back End Credit Certifications – In this process the DDEC issues a certificate of compliance to the Treasury department in order to issue the Tax Credit to the business or individual. The SBP needs to be capable of issuing and sending the certification automatically.)

44. What are the other systems to be integrated?

DEDC's and any other agencies' ERP that is used to process the corresponding payments. (Reference in RFP - 2.6 Functional Requirements - Back End Payment Transmittal through SBP or Finance ERP – Some incentives require the DEDC or agencies to process payments. The SBP should be able to identify how the payments would be processed and integrate with such systems. Act 60-2019 states that the Incentive Office will generate two types of annual reports: legislative report and general public report.)

45. Are merchant accounts setup for this? Yes. (Reference in RFP - 2.6 Functional Requirements - Back End Payment Transmittal through SBP or Finance ERP – Some incentives require the DEDC or agencies to process payments. The SBP should be able to identify how the payments would be processed and integrate with such systems. Act 60-2019 states that the Incentive Office will generate two types of annual reports: legislative report and general public report.)

46. What are split payments? Split payments will depend on the transaction, which means, a percentage of the payments will be credited to different accounts. (Reference in RFP - 2.6 Functional Requirements - Back End Payment Transmittal through SBP or Finance ERP – Some incentives require the DEDC or agencies to process payments. The SBP should be able to identify how the payments would be processed and integrate with such systems. Act 60-2019 states that the Incentive Office will generate two types of annual reports: legislative report and general public report.)



18

47. What are legislative reports & general public reports? What data is utilized? How are they different? Refer to the Act 60-2019 Incentives Code for the specific requirement. (Reference in RFP - 2.6 Functional Requirements - Back End Payment Transmittal through SBP or Finance ERP – Some incentives require the DEDC or agencies to process payments. The SBP should be able to identify how the payments would be processed and integrate with such systems. Act 60-2019 states that the Incentive Office will generate two types of annual reports: legislative report and general public report.)

48. How many systems? SBP, CRM and other agency's custom developments. (Reference in RFP - 2.6 Functional Requirements - Back End Reporting and Analysis – The system needs to be capable to collect confidential and public Information from the user profiles. This data will be used to generate reports and business intelligence as required. Although the data comes from different sources and agencies, the system should have the capability to interface with those systems.)

49. Which systems? SBP, CRM and other agency's custom developments. (Reference in RFP - 2.6 Functional Requirements - Back End Reporting and Analysis – The system needs to be capable to collect confidential and public Information from the user profiles. This data will be used to generate reports and business intelligence as required. Although the data comes from different sources and agencies, the system should have the capability to interface with those systems.)

50. Which data is needed? All data included within in the scope of the application. (Reference in RFP - 2.6 Functional Requirements - Back End Reporting and Analysis – The system needs to be capable to collect confidential and public Information from the user profiles. This data will be used to generate reports and business intelligence as required. Although the data comes from different sources and agencies, the system should have the capability to interface with those systems.)

51. Is this referencing interface? Data should be migrated from the current CRM system to SBP. (Reference in RFP - 2.6 Functional Requirements - Back End CRM Software Reports – The SBP should be able to access the data in the current CRM system use to manage Act 73-2008, Act 83-2010 and Act 273 applications.)



19

52. Since this requires data migration, what type of access will be utilized: read, extract, other? As necessary in order to comply with the data migration process. (Reference in RFP - 2.6 Functional Requirements - Back End CRM Software Reports – The SBP should be able to access the data in the current CRM system use to manage Act 73-2008, Act 83-2010 and Act 273 applications.)

53. What does CRM have, which data are we migrating? All data from existing grants should be migrated. (Reference in RFP - 2.6 Functional Requirements - Back End CRM Software Reports – The SBP should be able to access the data in the current CRM system use to manage Act 73-2008, Act 83-2010 and Act 273 applications.)

54. Would the information need to be entered manually? As last resource in the data migration process, if some information is missing, there is a possibility of manually registering the data. (Reference in RFP - 2.6 Functional Requirements - Back End CRM Software Reports – The SBP should be able to access the data in the current CRM system use to manage Act 73-2008, Act 83-2010 and Act 273 applications.)

55. Will the products also be in SBP? Yes, all the transactions in the Incentives Codes will be added in SBP. (Reference in RFP - 2.6 Functional Requirements - Back End CRM Software Reports – The SBP should be able to access the data in the current CRM system use to manage Act 73-2008, Act 83-2010 and Act 273 applications.)

56. Is CRM shutting down? Yes, CRM should only exist as historical data source. (Reference in RFP - 2.6 Functional Requirements - Back End CRM Software Reports – The SBP should be able to access the data in the current CRM system use to manage Act 73-2008, Act 83-2010 and Act 273 applications.)

57. Where does this payment request go - the ERP? To the corresponding internal office that processes the payments. (Reference in RFP - 2.6 Functional Requirements - Back End Cash Grants Evidence – In order to receive a cash-grant payment the business or individual needs to provide evidence of their expenses, disbursements, etc. The SBP has to be able to receive the evidence and generate a payment request.)

58. SBP should receive expense reports and automatically generate payment request? Based

on what parameters? Yes, based on the parameters established by the regulation.



20

(Reference in RFP - 2.6 Functional Requirements - Back End Cash Grants Evidence – In order to receive a cash-grant payment the business or individual needs to provide evidence of their expenses, disbursements, etc. The SBP has to be able to receive the evidence and generate a payment request.)

59. SBP should receive expense reports and automatically generate payment request? Based on what parameters? No. (Reference in RFP - 2.6 Functional Requirements - Back End Help Desk – The system must have a Help Desk to be able to troubleshoot system malfunctions, security breach and user incidents (logins, user provisioning, etc.).)

60. Must it be inside SBP or can it be a separate system that interfaces with SBP? DEDC is open to recommendations based on each proposal. (Reference in RFP - 2.6 Functional Requirements - Back End Help Desk – The system must have a Help Desk to be able to troubleshoot system malfunctions, security breach and user incidents (logins, user provisioning, etc.).)

61. How would we approach a change of scope, timeline and price due to the lack of design?

Each modification in scope or timeline will be subject to the change request process established by DEDC's PMO office and subject to the Committee's evaluation and recommendation. (Reference in RFP - 4.5.3.1 Design & Development The DEDC reserves the right to adjust the conceptual design as needed to ensure compliance with Act 60- 2019. Given that the rules and regulations for Act 60-2019 are under development, the transactions and processes outlined in the RFP might be subject to change and impact the design process.)

62. Please clarify if only documents 8, 12 and 13 are required to be submitted for the RFP. Refer to Section 4.6 item #15 in the RFP document. (Reference in RFP - 4.6 Additional Certifications and Representations Without excluding other certifications pertinent to this specific RFP, and except as specified below, the Selected Proponent shall obtain, before execution of a contract, and deliver DEDC the following: (refer to pages 23-24))

63. The remaining documents are to be submitted if RFP is approved? As indicated in Section 4.6 of the RFP, only the selected proponent shall obtain the additional documentation. (Reference in RFP - 4.6 Additional Certifications and Representations Without excluding other certifications pertinent to this specific RFP, and except as specified below, the Selected Proponent shall obtain, before execution of a contract, and deliver DEDC the following: (refer to pages 23-24))



21

Truenorth Corporation:

1. Does DEDC expects to maintain and update the existing SBP application, or create a new solution for the general public? DEDC expects to maintain and update the current SBP application.

2. Besides Azure, is there any specific technology or tools required by the DEDC for the solution (Development, reporting, virtualization, etc.)? Refer to the Section 2.2 Current SBP - Technical Infrastructure.

3. Who is the provider that initially developed SBP? Fusionworks initially developed the system.

4. Who is the current provider maintaining SBP? Will the current provider be available for

technical knowledge transfer? E3 Consulting is the current maintenance provider. If the process of this RFP results in a change of provider, DEDC, as owner of the current SBP system, will have available all the technical information regarding the system; if any additional information might be needed, DEDC will address the issue as presented.

5. How many and what are the data sources for reporting and analysis? The only data source should be the SBP database. (Reference in RFP - Section 2.6)

6. How many and what are the data sources of historical data that needs to be migrated? The sources include DEDC's CRM system and custom developments from any agency identified in the Incentives Code. (Reference in RFP - Section 2.5.1)

7. Are integration with third party defined and/or functional? Yes, the integrations are defined and identified. No, these integrations are not yet functional.

8. What integration is expected to PRITS TIM Data Platform? PRITS will determine the functional requirements for this notification engine. (Reference in RFP - Section 2.5.2)

9. What integration is expected to PRITS Notification Engine? PRITS will determine the functional requirements for this notification engine. (Reference in RFP - Section 2.5.3)

10. Are the 43 transaction workflows and their corresponding forms already documented? No, only some of the transactions are documented.



22

(Reference in RFP - Section 2.5.5)

11. Are the parameters to be used to calculate ROI already documented? Yes, specifics can be found in the Incentives Code. (Reference in RFP - Section 2.6)

12. What integration is expected to the Treasury Department to send Credit Certifications? There will be an interface with the Department of Treasury via the back-end workflow process. (Reference in RFP - Section 2.6)

13. What integration is expected for payment transmittal? With which systems? DEDC's and any other agencies' ERP that is used to process the corresponding payments. (Reference in RFP - Section 2.6)

14. What integration is expected to the current CRM system? All data from existing grants should be migrated. (Reference in RFP - Section 2.6)

15. What integration is expected to systems of other entities (ERP, CRM, and Treasury)?

Systems of other entities will be considered to be integrated as part of the back-end workflow processes. Each transaction may vary in the level of integration with other systems. (Reference in RFP - Section 2.6)

16. What types of electronic payments are expected to be handled? 'Colecturía Virtual' from the Department of Treasury currently accepts Visa, Mastercard and ACH transactions (subject to change by the Department of Treasury). (Reference in RFP - Section 2.6)

17. Does DEDC expects Help desk services as part of the contract? What days and times must the Help Desk be available? DEDC will evaluate each proponent's services. (Reference in RFP - Section 2.6)

18. Do the financial statements need to be audited? No. (Reference in RFP - Section 4.2)

19. Are insurance requirements required for all proponents or just for the selected proponent? Just for the selected proponent. (Reference in RFP - Section 4.4)

Date post:	25-Jul-2020
Category:	Documents
Upload:	others
View:	0 times
Download:	0 times

INCENTIVES CODE RFP Answers to Proponents Questions€¦ · identified in the Incentives Code. (...

Documents