Template T-1 · 1.0 PROPOSAL SIGNATURE PAGE Type or Print the following information. PROSPECTIVE CONTRACTOR’S INFORMATION Company: Chetu, Inc. Address: 10167 W. Sunrise Blvd., Suite

Template T-1

Cover Letter and Executive Summary

Response Template

RFP #: SP-18-0072

Arkansas Agriculture Department Mobile Device Data Collection Solution RFP #: SP-18-0072

Template T-1 – Cover Letter and Executive Summary

2 of 10

Table of Contents

1.0 PROPOSAL SIGNATURE PAGE ........................................................................... 3

2.0 Executive Summary .............................................................................................. 6

3.0 Prospective Contractor Contact Information ...................................................... 7

3.1 Subcontractor Contact Information (Non Applicable) ................................................ 7

4.0 Minimum Mandatory Qualifications ..................................................................... 8

5.0 Addendum 1: Revenue Verification Form…………………………………………..10

1.0 PROPOSAL SIGNATURE PAGE Type or Print the following information.

PROSPECTIVE CONTRACTOR’S INFORMATION

Company: Chetu, Inc.

Address: 10167 W. Sunrise Blvd., Suite 200

City: Plantation State: FL Zip Code: 33322

Business Designation

☐ Individual ☐ Sole Proprietorship ☐ Public Service Corp

☐ Partnership ☒ Corporation ☐ Nonprofit

Minority and Women-Owned Designation*:

☒ Not Applicable

☐ African American

☐ American Indian ☐ Asian American ☐ Service Disabled Veteran

☐ Hispanic American ☐ Pacific Islander American ☐ Women-Owned

AR Certification #: _________________________ * See Minority and Women-Owned Business Policy

PROSPECTIVE CONTRACTOR CONTACT INFORMATION

Provide contact information to be used for bid solicitation related matters.

Contact Person: Thyme Gadson Title: External Relations

Phone: (954) 342-5676 x 816 Alternate Phone:

Email: [email protected]

CONFIRMATION OF REDACTED COPY

☐ YES, a redacted copy of submission documents is enclosed.

☒ NO, a redacted copy of submission documents is not enclosed. I understand a full copy of non-redacted submission

documents will be released if requested.

Note: If a redacted copy of the submission documents is not provided with Prospective Contractor’s response packet, and neither box is checked, a copy of the non-redacted documents, with the exception of financial data (other than pricing), will be released in response to any request made under the Arkansas Freedom of Information Act (FOIA). See Bid Solicitation for additional information.

ILLEGAL IMMIGRANT CONFIRMATION

By signing and submitting a response to this Bid Solicitation, a Prospective Contractor agrees and certifies that they do not employ or contract with illegal immigrants. If selected, the Prospective Contractor certifies that they will not employ or contract with illegal immigrants during the aggregate term of a contract.

ISRAEL BOYCOTT RESTRICTION CONFIRMATION

By checking the box below, a Prospective Contractor agrees and certifies that they do not boycott Israel, and if selected, will not boycott Israel during the aggregate term of the contract.

☒ Prospective Contractor does not and will not boycott Israel.

An official authorized to bind the Prospective Contractor to a resultant contract shall sign below.

The signature below signifies agreement that any exception that conflicts with a Requirement of this Bid Solicitation will cause the Prospective Contractor’s proposal to be disqualified.

Authorized Signature: Title: CIO

Use Ink Only.

Printed/Typed Name: Atal Bansal Date: __5/30/18________



4 of 10

2.0 Executive Summary

Instructions: Provide a brief (three [3] to five [5] page) summary of the key aspects of the Prospective Contractor’s Technical Proposal. The Executive Summary should include an overview of the Prospective Contractor’s qualifications, approach to deliver the services described in the RFP, time frame to deliver the services, proposed team and advantage of this Proposal to AAD.

May 30, 2018

Timothy Smith

Office of State Procurement

1509 West 7th Street, Room 300

Little Rock, AR 72201-4222

On behalf of Chetu Inc., a leader in custom software development solutions, we congratulate you on making the decision to empower Arkansas Agriculture Department (AAD) with the infield, workflow efficiencies that this Mobile Data Collection Solution (MDCS) will deliver. Given the importance of food safety, fiber and forest products to American livelihoods, we are pleased to present the Office of State Procurement with this cost-effective offer to successfully deliver your software solution.

Augmenting current communication and data collecting efforts, AAD’s resulting Mobile Data Collection Solution –stored on local SQL Servers, using Entity Framework 6 to display and edit data in an ASP.NET MVC 5 application (amplified by Power BI), and deployed via iOS/Android technologies –will empower stakeholders (Farmers, Ranchers, Citizens, Staff) by enhancing the clarity and efficiency of AAD’s entire range of active events impacting field data management: gathering, accuracy, input, storage, retrieval, and the reporting of AAD’s invaluable resources.

Beyond this, supervisors will be able to track performance and status in real time. And staff, once equipped with this all-encompassing repository/reporting solution, will be held to a higher standard of (user-friendly) accountability and productivity.

It is my duty to serve as your primary contact for RFP-related communications, including any request for clarification needed. My contact information is as follows:

Thyme Gadson

External Relations P: (954) 342-5676

Chetu, Inc. F: (305) 832-5987

10167 W. Sunrise Blvd. Suite 200 E: [email protected]

Plantation, Florida 33322 W: www.chetu.com

http://www.chetu.com/



5 of 10

Your alternate contact, working at the same address and phone number listed above, is Seth Burger.

His email is: [email protected]. As instructed, we have shipped six (6) hard copies, and one (1)

electronic copy of the Technical Proposal, and one (1) hard copy, and one (1) electronic copy of the

Cost Proposal.

Chetu is incorporated (privately held), and based in Plantation, Florida. Our Federal Employer

Identification Number (FEIN#) is 65-0999101. Chetu makes the following certifications, guarantees,

and compliance regarding this solicitation received on March 28, 2018:

▪ Our offer is made in good faith, without collusion and no attempt has been made to

induce any other person or entity to influence the State of Arkansas.

▪ Chetu affirms that the submitted offer is valid for 120 days and it guarantees the

availability of the services described throughout, fully complying with Section 2 –

Requirements in the RFP.

While Chetu successfully serves roughly 25 industries, with over 1,400 skilled teammates, it is

particularly delightful to have an opportunity to use our software and industry acumen to assist in

the smart development of our nation’s vital resources. For a glimpse of the breadth of our software

solutions, please see: https://www.chetu.com/case-study.php. From robust Geographic Information

Systems (GIS) and Data Analytics / Warehousing, to rich User Interfaces (UI), Reporting and mobile

applications, you will find skillsets and experience in our case studies that pertain to the functionality

of your Mobile Data Collection Solution.

As illustrated herein, our service models are designed to be reliable, transparent and flexible when

accommodating modifications and enhancements by your staff and stakeholders. Specifically, our

‘Best of Both Worlds’ and ‘Right Sourcing’ delivery models create unparalleled value for customers.

Should Chetu earn the business, we will fulfill all contractual responsibilities in a highly professional

manner, a manner that clients ranging from municipalities, universities and global giants, like

Siemens, to SMBs and inspired Start-Ups can attest to having received – over the past 18 years and

counting.

Respectfully Submitted,

Thyme Gadson

External Relations

https://www.chetu.com/case-study.php



6 of 10

Executive Summary

“Price is what you pay. Value is what you get.” In a rapidly changing world, it is imperative that governments embrace contemporary technologies based on new operational methods and practices to improve public services for its constituents. As many know the venerable investor, Warren Buffet is the author of the above adage. It implies that while the price of an asset may fluctuate, “What you get,” has an intrinsic value that is less erratic than “what you pay” in the marketplace…and value is what you seek to maximize.

Collaboration across governmental departments (Arkansas Livestock and Poultry Commission, Arkansas Forestry Commission and the Arkansas Plant Board) and access to useable data from multiple sources are equally important to realizing this value. Chetu’s software solutions have an 18 year history of networking departments, enabling data, and empowering organizations to amplify efficiencies so people and communities can unleash value –be it time saved, quality enhanced, or quantity increased.

Global Strength, Local Reach

At Chetu, our customers come first. It is in our DNA to identify ‘pain points’ and then configure custom software solutions to propel organizational success. While we serve clients from 14 locations around the globe, we proudly help municipalities and universities navigate 21st century technological advances right here at home. Through financial strength (see Revenue Verification), market leadership, and sound business practices, we demonstrate our ability to serve the Public Sector as a vital partner, unearthing value.

Industry Expertise

In particular to Arkansas Agriculture Department current need, Chetu has in-depth knowledge of Livestock and Agricultural Land Management software development https://www.chetu.com/agriculture/land-management.php We have the experience necessary to develop audit management software for maintaining records of all data and documentation related to food safety and quality management, including microbial test results, certifications, process blueprints, and compliance methodologies. We are practiced in designing interfaces for seamlessly retrieving, organizing and submitting information to safety inspectors and for tracking necessary process and environmental changes based on audit conclusions.

Beyond this, Chetu centralizes spatial data through database warehousing platforms with custom business intelligence analytics applications to support query and reporting capabilities for soil samples, weather information, and GIS map storage capabilities across multiple fields and crops. And to ensure these solutions are deployable infield, we are specialists in mobile app development and iOS/Android technologies with over 16,000 apps launched. Major experience renders reliability. When reliable experience comes at a reasonable price, what AAD gets is unparalleled value.

https://www.chetu.com/agriculture/land-management.php



7 of 10

3.0 Prospective Contractor Contact Information

Instructions: Complete the following information regarding the Prospective Contractor’s headquarters and primary contact for any questions pertaining to the responses to this RFP. Do not change any of the completed cells. Any changes to the completed cells could lead to the disqualification of the Proposal.

Table 1. Prospective Contractor Contact Information

COMPANY HEADQUARTERS INFORMATION:

Company Size: (1400+)

Annual Revenue:

$39mm

REGIONAL OR LOCAL OFFICE INFORMATION:

Company Name:

Chetu, Inc.

Region Name:

Address: 2222 West Spring Creek Parkway Suite 110

City, State & Zip Code:

Plano, TX 75023

Primary Contact:

Designated upon Award

Phone: (954) 342-5676 Fax: (305) 832-5987

E-mail: [email protected]

Table 2. Prospective Contractor Profile

PROSPECTIVE CONTRACTOR ORGANIZATION PROFILE

Name of Parent Company Chetu

% of Revenue from State and Local Government Clients in the United States

10%

Number of Years in Business Founded in 2000; 18 years

Number of Years Prospective Contractor has been Providing the Type of Services Specified in the RFP

18 years

Number of Employees Providing the Type of Services Specified in the RFP

Approximately 300

3.1 Subcontractor Contact Information (If applicable)

Instructions: Complete the following information regarding the subcontractor’s contact information. If more than one subcontractor is proposed, add more Tables as necessary. Do



8 of 10

not change any of the completed cells. Any changes to the completed cells could lead to the disqualification of the Proposal.

Table 3. Subcontractor Contact Information

COMPANY INFORMATION:

Company Name:

N/A

Address:


Company Type (Check One):

Private Public

Company Size: (Total Number of Employees)

Annual Revenue:

PRIMARY CONTACT INFORMATION:

Name: N/A Title:

Address:


Phone: Fax:

E-mail:

Table 4. Subcontractor Profile

SUBCONTRACTOR ORGANIZATION PROFILE

Subcontractor Name N/A

Headquarters Location

Date Founded

Services to be Provided

Experience of Subcontractor in Performing the Services to be Provided

Brief Description and Number of Projects that Prospective Contractor has partnered with this Subcontractor on

Locations Where Work is to be Performed

4.0 Minimum Mandatory Qualifications

The Prospective Contractor must provide clear, compelling justification that it meets all of the Minimum Mandatory Qualifications. The Prospective Contractor is encouraged to provide ample references to information contained in the Proposal that supports its attestation.



9 of 10

Prospective Contractor’s that fail to provide clear, sufficient evidence that they meet the Minimum Mandatory Qualifications may be subject to disqualification. OSP and AAD may ask for additional clarifications relating to the Minimum Mandatory Qualifications prior to determination of compliance.

Instructions: Complete the following information regarding the Prospective Contractor’s ability to meet the Minimum Mandatory Qualifications. Provide specific references to Proposal locations that support the Prospective Contractor’s assertions that it meets the Minimum Mandatory Qualifications. Do not change any of the completed cells. Any changes to the completed cells could lead to the disqualification of the Proposal.

Table 5. Minimum Mandatory Qualifications

# QUALIFICATION ITEM

DOES THE PROSPECTIVE CONTRACTOR

MEET QUALIFICATION

ITEM?

REFERENCE TO PROPOSAL

RESPONSE SECTION

1

The Prospective Contractor must have at least three (3) years’ experience with two (2) engagements similar in size, complexity and scope to this procurement that include the delivery of a mobile data capture solution. (See Template T-2)

YES

NO

T-2 Section A.4.

2

The Prospective Contractor’s system must have a customer base that has demonstrated scalability for a single customer instance that meets or exceeds 150 direct users. (Use this Template to provide your response)

YES

NO

T-2 Section A.4.



10 of 10

5.0 Addendum 1: Revenue Verification Form

Template T-2

Prospective Contractor Experience

Response Template

RFP #: SP-18-0072

Arkansas Agriculture Department Mobile Device Data Collection Solution RFP #: SP-18-0072 Template T-2 – Prospective Contractor Experience

2 of 14

Table of Contents

1.0 Prospective Contractor Corporate Background and Experience ..................... 3

1.1 Prospective Contractor’s Corporate Background ...................................................... 3

1.2 Projects Completed in the Last Three Years ............................................................ 8

2.0 Prospective Contractor References .................................................................... 9

2.1 Subcontractor References (If applicable) ................................................................ 12


3 of 14

1.0 Prospective Contractor Corporate Background and Experience

1.1 Prospective Contractor’s Corporate Background

The Prospective Contractor should describe its corporate background to provide context of the organization that will be providing the services in this RFP.

Instructions: Describe the Prospective Contractor’s corporate background as it relates to projects similar in scope and complexity to the project described in this RFP.

Section A - Description of Vendor

Founded on April 1st 2000, Chetu is a custom software development services company with fourteen (14) locations globally. We combine technological expertise, specific domain experience, and a passion for excellence to deliver enterprise-grade solutions. Chetu is a true and seamless, back-end technology partner, helping institutions accelerate the development of desktop, mobile & web-based apps with on-demand programmers focused on ensuring organizations reach their full potential.

A.1. -Client Sample-

Chetu has always followed a "customer comes first" philosophy. Our governance is simple, flexible, and focused on providing effective end results to our clients. Below is a small sample of clients we served:


4 of 14

A.2. -Long-Term Technology Partner-

We value our customer relationships and take extra steps to ensure our customers are always satisfied. Thanks to our employees across the US and abroad, we have grown organically by maintaining a repeat business and referrals rate of 47%.

Driven by two (2) state-of-the-art facilities, totaling 110,000 sq. ft. of development space in Noida, India, Chetu is a long-term, trustworthy partner. Today, we service more than 300 active clients.

A.3. -Standards and Recognition-

As part of our commitment to adhering to best practices in all areas of our operations, every year Chetu successfully completes the SSAE 16 SOC 1 Type 2 audit according to stringent guidelines set by the AICPA. These standards evaluate Chetu in key areas including: company structure, management, risk assessment procedures, information security, data communications, customer implementations, monitoring practices and client controls systems.

Consequently, we are pleased to be recognized by our colleagues and business professionals: https://www.chetu.com/awards-and-recognition.php

https://www.chetu.com/awards-and-recognition.php


5 of 14

A.4. -Industry Specific Experience-

Chetu is organized into industry vertical teams. In order to optimize domain expertise, each group is skilled in the best practices, trends, and regulations specific to that industry. As a result, our Subject Matter Experts are equipped to adapt to changing market conditions and provide insights into initiatives that add value to AAD’s objectives. Chetu’s Mobile App experts specialize in end-to-end iOS/Android app development services, including developing native UI / UX, coding the latest features, and distributing finished apps through the App Store, as well as maintaining compatibility with the store. Additionally, our experts develop database management systems (DBMS) solutions such as hierarchical, network, relational, and object oriented DBMS for data manipulation that reduces downtime, tightens security, and optimizes performance for multi-source organizations, like AAD.

{For reference; many clients have Publicity clauses and NDAs forbidding the sharing of their brand identity.}

Area of Focus Experience / Projects

Agronomy & Livestock Management Software

✓ Built the most advanced seed-to-sale compliance platforms, offering 100% accountability and transparency for govt. reporting.

✓ Designed world-class crop insurance solution improving quotations based on historical assessments and algorithms for a particular grid.

✓ Coded the world’s most sophisticated automatic health system for dairy and beef producers to detect early illness, calving and breeding.


Mapping / GIS

✓ We have integrated with, and processed data from, different GIS data

providers like: ESRI, MapPro, MapBox, Google Maps, and MapDotNet

✓ Used GIS data and/or local Map Server data – Projects: (water resources management, budgeting and forecasting with historic data), (forecasting, budgeting, accounting)

✓ GPS Mapping, overlaying custom layers, drawing over layers w/ real-time moving pointer implementations –

✓ Social analytics based on location and demographics –


Data Warehousing / Analytics

✓ We have implemented: Data Warehouse (DW) for clients, and reported on historic data; developed statistical number crunching processes, forecasts, with aggressive loads in the billions of records with targeted QPS database benchmarks –


6 of 14

✓ Database experience – Hadoop, BigData, Data Sharding setup / Data Farm with Master-Slaves architecture in MS SQL Server and MySQL/mariaDB Server.

✓ We have executed reporting with: drill-down or drill-up on charts or grids; applied specialized analytics tools like: Cognos, Tableau, and Logi Analytics.

✓ We have applied interactive charting on web portals and applications with libraries / controls like: MixPanel Analytics, amcharts, highcharts, Telerik controls, etc.


Mobile Apps

✓ We implemented a timesheet mgmt. system for a preeminent global loss adjusting and claims mgmt. company, wherein: the duration of tasks are tracked; users can view/edit/delete entries and work codes locally before submission to service end; and a service method generates an excel sheet from the mobile device then exports it to an email user.

✓ Plus, executed security features programming, including: Role-Based Access Control (RBAC), user authentication / authorization, Single Sign-On (SSO), compliance tracking, audit trails, permissions / approvals management, alerts / notifications, encryptions, and more


7 of 14

Section B – Engagement Model

Chetu’s approach to provide resources throughout the term of the agreement resulting from this procurement is as follows:

B.1. -Industry Specific Teams-

Chetu’s processes for the identification and qualification of potential teams and resources is based on industry experience and the solution to be implemented. The team assigned to AAD will have decades of combined experience developing multi-tenant web apps to capture, store, visualize, interpret, and analyze data from legacy systems/formats, plus presenting quantitative, actionable reports. In particular, we have in-depth knowledge of Livestock and Agricultural Land Management software development services https://www.chetu.com/agriculture/land-management.php

B.2. -Delivery Model-

Chetu’s proprietary model facilitates real-time communication and collaboration, which seamlessly integrates to meet your needs for the rapid engagement of required resources. Chetu offers two (2) staffing engagement models that AAD can leverage:

Best of Both Worlds (Exhibit A) comprises of dedicated India-based developers working in US time zones (until 2pm EDT). We provide an India-based complimentary Technical Lead who is engaged throughout the project(s) and also serves as a backup. We also assign a complimentary, US-based Technical Project Manager (with a minimum of 8 yrs. of data analytics industry experience), serving in a techno-managerial role.

Right Sourcing (Exhibit B) comprises of the Best of Both Worlds model plus an onsite Project Manager and/or

Developer(s) to work at your location.

https://www.chetu.com/agriculture/land-management.php


8 of 14

1.2 Projects Completed in the Last Three Years

The Prospective Contractor should list all projects similar in size and scope that were completed/finished or were active in the last 3 years.

Instructions: Provide a listing and contact information for all similar contracts in the last three (3) years. Denote any that are pending litigation or have been terminated for cause or convenience. Provide the same information for each subcontractor, associated company, consultant and entity that will be involved in any phase of this engagement. Duplicate the table for each entity in the Proposal. Do not change any of the completed cells. Any changes to the completed cells could lead to the disqualification of the Proposal.

Table 1. Mobile Device Solutions Completed in the Last Five (5) Years

REF #

ENGAGEMENT NAME CUSTOMER

NAME CUSTOMER CONTACT

PROJECT

DURATION

BUSINESS DISPUTE?

1 PAYBOX Corp.

www.gopaybox.com

Steve Reider [email protected]

(954) 849-8589

4/17 to 11/17

YES

NO

2 Incorporate Message

www.incorporatemassage.com

Amelia Wilcox

[email protected]

(800) 556-2950 x 2

5/16 to Present

YES

NO

3 Total Party Planner

www.totalpartyplanner.com

John Cohen [email protected]

866-868-7526 ext 301

12/15 to

Present

YES

NO

2.0 Prospective Contractor References

To realize the objectives stated as part of the RFP, the State of Arkansas is issuing this RFP to contract with a Contractor who has experience similar to the scope provided in this RFP. As such, the State has established mandatory qualifications that must be met in order to submit a proposal to this RFP, see Section 2.5 of the RFP.

To satisfy this requirement, include at least two (2) references (for the Prime Contractor) of projects which are of similar size, complexity and scope to this engagement, that have either completed within the last three (3) years or are active projects. Each reference chosen should clearly demonstrate the Prospective Contractor’s ability to perform the Scope of Work described in the RFP.

Instructions: Provide the information requested in the Tables below. The Tables may be replicated if the Prospective Contractor would like to include more than two (2) references. Do not change any of the completed cells. Any changes to the completed cells could lead to the disqualification of the Proposal.

http://www.gopaybox.com/

mailto:[email protected]

http://www.incorporatemassage.com/


http://www.totalpartyplanner.com/



9 of 14

Table 2. Reference 1

PROSPECTIVE CONTRACTOR INFORMATION

Name: Chetu Contact/Name: Rajat Khatter

Project Dates: 1/15/2015 to 11/16/2016 Contact Phone: 954-342-5676 x 142

CUSTOMER INFORMATION

Customer Organization:

Ride Systems

Customer Contact Name: Justin Rees

Customer Phone: 888-281-2681

Customer Address:

209 N. State St, Suite D

Morgan, UT 84050

Customer Email: [email protected]

Customer Fax: N/A

PROJECT INFORMATION

Total Prospective Contractor Staff:

5

Project Objectives:

• To analyze the existing code and suggest code level improvements or performance tuning actions.

• Develop approved changes (w/ priority) as tasks to fix short-term issues

• Transition into changes that improve performance of website both on desktop and mobile environments.

• Test changes on targeted device default browsers and desktop browsers.

Project Description:

To improve the performance of the mobile device compatibility / performance of the homepage UI for www.uofubus.com

Prospective Contractor’s Involvement (Role and Scope): See Project Objectives

Project Benefits:

• Identified JavaScript files and Google map API taking too long to load and execute.

• Minimized JavaScript and CSS files to reduce loading times.

• Implemented loaders to show with requesting/processing to increase user’s patience.

• Hosted website in external environment to verify modifications

PROSPECTIVE CONTRACTOR KEY PERSONNEL ASSIGNED TO PROJECT

Name: Harish Palaniappan Role: Project Manager

Name: Manvinder Bhatia Role: Director-Operations


http://www.uofubus.com/


10 of 14

PROJECT MEASUREMENTS

Estimated Start & Completion Dates From: 1/15/2015 To: 11/16/2016

Actual Start & Completion Dates From: 1/15/2015 To: 11/16/2016

Reason(s) for Difference Between Estimated and Actual Dates: N/A

If the Prospective Contractor performed the work as a subcontractor, the Prospective Contractor should describe the scope of subcontracted activities: N/A

Table 3. Reference 2

PROSPECTIVE CONTRACTOR INFORMATION

Name: Chetu Contact/Name: Rajat Khatter

Project Dates: 12/15 – 11/17 Contact Phone: 954-342-5676 x 142


Customer Organization:

FreshAir Sensor Customer Contact Name: Anani Sawadogo

Customer Phone: (603) 276-8052

Customer Address:

16 Cavendish Ct. Lebanon, NH 03766

Customer Email:

[email protected]

Customer Fax: N/A

PROJECT INFORMATION

Total Prospective Contractor Staff:

5

Project Objectives:

The objective is to establish the existing codebase & validate the existing API’s and web application to make sure it is up to the standard to include the new features to avoid any issues or hiccups in future.

We worked on the following modules for API verification. When changes were required we modified the existing codebase as per the requirement.

1. User Management 2. User Accounts and Secondary user 3. Devices and Groups



11 of 14


FreshAir Sensor client has developed a novel sensing technology that measures the concentration of airborne organic compounds in real-time. In the first phase, client is using this novel sensing technology to build smart connected devices that detect the presence of nicotine from burnt cigarettes, along with a component from burnt marijuana. Customers are now able to enforce their nonsmoking policies and deter smoking in locations where smoking is prohibited, but people still smoke - such as in hotel rooms or rental properties.

Prospective Contractor’s Involvement (Role and Scope): Project augmentation

Project Benefits:

Developed the following modules.

1. Real-time Sensor and Event Data view 2. Incidents and Real-time notification 3. Dashboard & Header Panels 4. Support 5. Billing

PROSPECTIVE CONTRACTOR KEY PERSONNEL ASSIGNED TO PROJECT

Name: Bhavnath Yadav Role: Project Manager

Name: Sanjeev Kota Role: Director of Operations


Estimated Start & Completion Dates From: 12/15 To: 11/17

Actual Start & Completion Dates From: 12/15 To: 11/17

Reason(s) for Difference Between Estimated and Actual Dates:

If the Prospective Contractor performed the work as a subcontractor, the Prospective Contractor should describe the scope of subcontracted activities:


12 of 14

2.1 Subcontractor References (If applicable)

If the Proposal includes the use of subcontractor(s), include at least two (2) references (for each subcontractor proposed) from scopes of work equivalent to the scope of work proposed of the subcontractor in the Proposal. Each reference chosen should clearly demonstrate the subcontractor’s ability to perform the relevant portion of work requested in the RFP (the State has established mandatory qualifications that must be met to submit a proposal as stated in Section 2.5 of the RFP), and proposed by the Prospective Contractor.

Instructions: Provide the information requested in the Tables below. Replicate the Table if more than two (2) references are desired. Do not change any of the completed cells. Any changes to the completed cells could lead to the disqualification of the Proposal.

Table 4. Subcontractor Reference 1 - N/A

SUBCONTRACTOR INFORMATION

Subcontractor Name: Subcontractor Contact/Name:

Project Dates: Subcontractor Contact Phone:


Customer Organization: Customer Contact Name:

Customer Phone:

Customer Address: Customer Email:

Customer Fax:

PROJECT INFORMATION

Project Objectives:


Subcontractor’s Involvement (Role and Scope):


13 of 14

Project Benefits:

SUBCONTRACTOR KEY PERSONNEL ASSIGNED TO PROJECT

Name: (Add more rows as needed) Role: (Add more rows as needed)



Estimated Start & Completion Dates: From: To:

Actual Start & Completion Dates: From: To:


Table 5. Subcontractor Reference 2 – N/A

SUBCONTRACTOR INFORMATION

Subcontractor Name: Subcontractor Contact/Name:

Project Dates: Subcontractor Contact Phone:


Customer Organization: Customer Contact Name:

Customer Phone:

Customer Address: Customer Email:

Customer Fax:

PROJECT INFORMATION

Project Objectives:



14 of 14

Subcontractor’s Involvement (Role and Scope):

Project Benefits:

SUBCONTRACTOR KEY PERSONNEL ASSIGNED TO PROJECT




Estimated Start & Completion Dates: From: To:

Actual Start & Completion Dates: From: To:


Template T-3

Prospective Contractor Engagement Organization and Staffing

Response Template

RFP #: SP-18-0072

Arkansas Agriculture Department Mobile Device Data Collection Solution RFP #: SP-18-0072 Template T-3 – Prospective Contractor Engagement Organization and Staffing

2 of 24

Table of Contents

1.0 Engagement Organization and Staffing Plan ...................................................... 3

2.0 Prospective Contractor Key Personnel ............................................................... 5

2.1 Subcontractor Key Personnel (if applicable) ............................................................. 8

3.0 Resumes ................................................................................................................ 9

4.0 Roles and Responsibilities ................................................................................. 24


3 of 24

1.0 Engagement Organization and Staffing Plan

The Prospective Contractor should describe an integrated Project Organization and Staffing Plan required to execute the proposed approach for the Engagement. This section should include details of the Prospective Contractor’s team, proposed use of subcontractors, and the Prospective Contractor’s expectations of AAD resources. This section should include a visual representation of the Prospective Contractor engagement including the reporting structure. The Prospective Contractor should also describe the required staffing of business and technical resources AAD will need to provide to support the delivery. The Plan should include the number of resources (both business and technical), anticipated role and responsibilities, level of participation and necessary capabilities/skills for both AAD and Prospective Contractor resources.

Key Project Personnel identified in the Proposal for the engagement are considered to be the core Prospective Contractor resources and are therefore expected to be the major participants in all procurement activities and services delivery activities. If the Prospective Contractor is selected, its Key Project Personnel cannot be replaced without prior AAD approval during the life cycle of the Project.

Instructions: Provide a Staffing Plan and associated organization chart detailing the number of personnel, level, roles and responsibilities, and team reporting relationships between Prospective Contractor staff and AAD staff. Show proposed Prospective Contractor personnel hours by phase, by personnel level, and by role for the entire engagement. Identify all Key Project Personnel for the Prospective Contractor, personnel for AAD and their proposed roles. If the Prospective Contractor’s proposed engagement organization and staffing plan does not align with the guidance provided in the body of the RFP the Prospective Contractor should discuss the justification for recommending an alternative staffing organization.


4 of 24

Below is Chetu’s organizational chart. We have a staff of 1,400 with 90% serving as skilled software engineers. The boxes highlighted in teal are AAD’s project participants. Six (6) engineers will work on the Mobile Device Data Collection Solution (MDDCS): ones (1) Project Manager, one (1) Team Lead, two (1) Xamarin Developer (for iOS & Android platforms), (1) one Web Developer, and (1) one QA engineer (Note: Man Days/Hours are configured into the project plan, the Mobile Developer is interchanged). Each team member will devote an ample percentage of time to complete the project, fulfilling your development needs.


5 of 24

2.0 Prospective Contractor Key Personnel

The Prospective Contractor should identify Key Personnel for the Engagement, as described in the RFP, including:

Name: Rajat Kattar

Position in Prospective Contractor organization: Director of Operations / PM

Proposed role on Engagement: PM

Focus of work effort: Client relations / project management

% of time for that work effort: 10%

Experience in the proposed role: 11+ years with many projects completed successfully

Qualifications for the proposed role: See below

Role in the last two (2) projects: Director of Operations / Project Manager

Instructions: Complete the following Table detailing the Key Personnel identified for this Engagement. Add rows as necessary. Do not change any of the completed cells. Any changes to the completed cells could lead to the disqualification of the Proposal.

2. The Prospective Contractor should identify Key Personnel for the Engagement, as described in the RFP, including:

Name: Jitendra Gupta

Position in Prospective Contractor organization: Xamarin Mobile Developer

Proposed role on Engagement: Xamarin Mobile Developer

Focus of work effort: iOS & Android Development


Experience in the proposed role: 5+ years with many projects completed successfully

Qualifications for the proposed role: Bachelors of Science (Software Engineering) from GNIIT University in 2010

Role in the last two (2) projects: Xamarin Mobile Developer



6 of 24


Name: Anuj Kumar

Position in Prospective Contractor organization: Web Developer

Proposed role on Engagement: Web Development

Focus of work effort: Web Development


Experience in the proposed role: 5 Years with many projects completed successfully

Qualifications for the proposed role: Bachelors of Engineering (Computer Science) from UPTU, Mathura in 2012

Role in the last two (2) projects: Web API Development / Database



Name: Vikash Singh

Position in Prospective Contractor organization: QA Engineer

Proposed role on Engagement: QA Engineer

Focus of work effort: QA


7 of 24


Experience in the proposed role: 4+ with many projects completed successfully

Qualifications for the proposed role: Bachelors of Engineering (Information Technology) from Maharishi Dayanand University, 2013.

Role in the last two (2) projects: Quality Assurance


Table 1. Prospective Contractor Key Personnel

NAME POSITION IN

ORGANIZATION

PROPOSED ROLE ON

ENGAGEMENT

FOCUS OF WORK

EFFORT

% OF TIME FOR THAT WOR

K EFFO

RT

EXPERIENCE IN PROPOSED

ROLE (YEARS)

QUALIFICATIONS FOR PROPOSED

ROLE

ROLE IN LAST 3

PROJECTS

Rajat Kattar Director of Operations

Project Manager

Project Management

10% 11+ (See Resume)

PM

Jitendra Gupta Xamarin Developer

Mobile Developer iOS & Android Development

100% 5+ (See Resume)

Mobile Developer

Anuj Kumar Web Developer Developer Web

Development 100%

5+ (See Resume) Web Developer

Vikash Singh QA Engineer QA Engineer QA 100% 4+ (See Resume) QA Engineer


8 of 24

1.1 Subcontractor Key Personnel (if applicable)

The Prospective Contractor should identify the Subcontractor Key Personnel for the Engagement including: N/A

Name

Position in subcontractor organization

Proposed role on Engagement

Focus of work effort

% of time for that work effort

Experience in the proposed role

Qualifications for the proposed role

Role in the last two (2) projects

This section should also detail the past work each listed person has had with the Prospective Contractor or their staff.

Instructions: Provide a listing of the Subcontractor Key Personnel. This Table should be replicated for each Subcontractor used. Add rows as necessary. Do not change any of the completed cells. Any changes to the completed cells could lead to the disqualification of the Proposal.

Table 2. Subcontractor Key Personnel

NAME POSITION IN

ORGANIZATION PROPOSED ROLE ON ENGAGEMENT

FOCUS OF

WORK EFFORT

% OF TIME FOR THAT WORK

EFFORT

EXPERIENCE IN PROPOSED

ROLE (YEARS)

QUALIFICATIONS FOR PROPOSED ROLE

ROLE IN LAST 3

PROJECTS

N/A


9 of 24

2.0 Resumes

The Prospective Contractor should attach professional resumes of all proposed Key Personnel to this section of the Proposal.

Each resume should demonstrate experience germane to the position proposed. The resume should include work on projects cited under the Prospective Contractor’s corporate experience, and the specific functions performed on such projects.

Instructions: Provide a resume for each proposed Key Personnel.

Rajat Khattar

SUMMARY

● 11 years of experience in software development and management.

● Currently working as a Director of Operations/Sr. Technical Project Manager.

● Expertise in project management of different verticals and domains.

● Good experience in C++/.NET developer/architect.

● Track record of transforming struggling business with: delivery processes, technology

platforms, and cross-functional teams to increase ROI and system stability.

● Expertise in identifying impactful yet cost-effective technical changes to achieve

maximum business value through practices that protect ongoing business operations.

QUALIFICATION

● Bachelor of Engineering in Computer Science, Maharishi Dayanand University, India -

2004

TECHNICAL SKILLS

Programming : C, C++, JAVA, C#.net, VB 6.0, VB .NET.

Scripting : Java Script, J-Query, VBScript, Angular JS, Node JS

Frameworks : .NET All Versions, Entity Framework

IDE : Visual Studio (All versions), Eclipse

Middleware : COM/DCOM, COM+, COM + Interop, ATL

Technologies : ASP.NET, XML, XSLT, UDDI, WSDL, WCF, WPF, WWF, iOS (Objective C & Swift), Android Java, Xamarin, Phonegap.


10 of 24

Web Services : .NET Remoting, SOAP, HTTP, IIS 5.1, IIS 6.0, IIS 7.0

Database : SQL Server 2008/2005/2000, Sybase, Oracle , MS Access, Excel 2007/2003/2002

Operating Systems

: Windows 2000/XP/2003/2008 Server and Unix

Tools : MS Visio (UML), Microsoft Project, VSS, SVN, PVCS, TFS.

Integrations : EMV certifications, First Data, VeriFone (Verix and eVO), Ingenico (RBA and Telium), Magtek, IDTech.

PROJECT DETAILS

Project #1:

Role Director of Operations

Domain Banking & Financial (Payments, Insurance claims, Mortgage Banking,

Lending, Real Estate)

Period June 2013 – Till date

Responsibilities:

● PM Project Dashboard Review, identify any yellow/red flags. Monitor project progress

and process of Project Managers and team for smooth delivery of projects.

● Ensure that the internal calls are productive where communication between: Developers,

Leads and PM should be professional.

● Complete involvement in new projects until architecture is approved and all

documentation is delivered. Review High level Design, Detail design document and

Project plan - approve and ensure delivery.

● Ensure that communication between the customer and team is smooth. Monitor Daily

status reports to identify any issues with projects.

● Conduct Executive Briefing, which covers: objectives of current project,

accomplishments to date, suggestions for additional functionality on industry, project


11 of 24

experience of DOs (e.g. SEO, Mobile platforms), describe Serving Offerings, Referrals

for potential customers, advising BPM and Quotes for current relationship.

● Resourcing: Ramp up or Ramp down based on client needs, co-ordinate with HR for

bench strength, resource assignments and co-ordination with offshore Delivery

Managers.

● Onsite client visits every month and if required conduct executive briefings while onsite.

● Execute technical calls with prospects, presenting the development models, options

before sharing industry expertise and providing a ball park budget for the project.

Project #2:

Role Senior Associate

Domain Banking & Financial (Mortgage Banking)

Period 2009 – May-2013

Responsibilities:

• Managing more than 10 Associates at offshore and 3 onsite, generating revenue of $1 Million.

• Closely working on: Project Management, Resource Management, Estimations, Capacity/Volume Management, Delivery Management, Client Relationship management, Business Development and Account Management.

Project #3:

Role Programmer Analyst

Environment Automobile Manufacturing

Period November 2008 – July 2009

Responsibilities:

• Successfully implemented the Business Object Classes using VC++, VB.NET using OOPS/UML design principles in the core application.

• Involved in designing the Database using RDBMS concepts and wrote Stored Procedures in SQL Server 2005

Project #4 :

Role Senior System Analyst


12 of 24

Environment Hospitality

Period Sept. 2005 - July 2008

Responsibilities:

• Technical Development in C, C++, VC++, ATL COM, VB and VB.NET.

• Using Oracle database procedures to fetch data from Oracle tables, export into XMLs using Meta data, then using the XMLs for providing a local reference database in MS ACCESS using some VB.NET windows services.

Jitendra Kumar Gupta

SUMMARY

• 5 Years of experience in Software Development and Mobile Development using Xamarin

forms.

• Hands on experience in Designing by using Visual Studio, Development of the Client/Server

(Web) applications, APIs and Services using Microsoft Technologies.

• Gained exposure in project management activities including scoping, estimation, planning,

finalisation specifications and quality management of the software application.

• Comprehensive knowledge of end-to-end implementation of the SDLC; including finalisation

of specifications, development, implementation and quality.


13 of 24

• Interaction with team and client and also knowledge scrum call, stand up call using agile

methodology.

QUALIFICATION

GNIIT (Software Engineering) Diploma in 2010

TECHNICAL SKILLS

Programming Languages C#.NET, Xamarin form with MVVM architecture

Web Technologies Asp.Net, MVC, Entity Framework, Web API, WCF, LINQ

Database SQL Server 2005, 2008R2, 2012,2014, SQLite

Server IIS 7, hosting and publishing

Operating System Windows 10

Scripting and UI java script, JQuery

PROJECT DETAILS

Project # 1

Designation Sr. Software Engineer

Duration Mar 2017 to Till Date

Environment Xamarin, Xamarin Forms, visual Studio, Android, iOS



14 of 24

This is the mobile app for their retail customers. It is a car company with software products for retail sector. We are their technology partners for Mobile and cloud platforms. Currently working on a mobile application as a Sr. software engineers to deliver native iOS and Android Apps developed using Xamarin Forms. Responsible for end-to-end delivery of the mobile apps. The app has features such as finding a new and old car with different company for purchasing, modify looks or add accessories in a car, loan management. Worked with mobile features such as get the customer credit score using third party API, send the credit score to another API to store the buyer data in database, design UI, testing of the application in different environments.

Responsibilities:

• Client interaction for requirements, sprint plans, and deliverables.

• Building Common UI with Xamarin.Forms for various platforms.

• Involved in major level tasks like get the customer credit score using third party API, send the data to API, testing of the application in different environments.

Project # 2


Duration Jun 2016 to Feb 2017

Environment Xamarin, Xamarin Forms, visual Studio, Android, iOS, MVVM Cross, Json, Web Services, GIT, VS 2017


This application automates the Dog Daycare. In which dog honor and daycare person can communicate using mobile app. There is push notification option and also user can upload videos and images as well.

Responsibilities:

• Requirement gathering and understanding

• Architecture creation of Xamarin application development.

• Implemented push notification feature using APNS and GCM

• Implemented multiple selection of video and images from gallery


15 of 24

• Implemented camera for capturing images and videos

• Releasing the UAT build and production build

Project # 3


Duration Nov 2014 - May 2016

Environment MVC, C#, Azure, JQuery, data table control, WCF Services, Entity Framework, Dev Extreme controls, VS 2013, Azure Hosting.


This web application is basically for administration purpose. Admin. can register employees to give the permission to assess the mobile app related to construction equipment management. It is a mobile app development company with software products for the construction sector. The web application has features such as: registering the company, registering company employees, purchase the subscription for group of mobile apps accessibility. We have worked on a web application as a Sr. software engineers using MVC 5 and WCF service. Worked with web features such as provide dynamic dashboard responsive design, multiple register user with group of subscription accessibility in single click, old company user convert functionality with implemented group features, database management, implement Dev Extreme grid for reporting and provide change of details in the application.

Responsibilities:

• Building approaches to implement code for business logic.

• Involved in creating the reporting service using Dev extreme grid third party control.

• Involved in integration of third party API and sending SOAP request.

• Resolving the post production issues on priority basis to the client.

Project # 4


16 of 24

Designation Software Engineer

Duration Jul 2013 to Oct 2014

Environment Window service, WCF service C#, VS 2012. Asp.net with c#


• This is the web application for their hotel customers. It is a group of Hotels with software products for hospitality sector. We have worked on WCF service, windows service, web application with c# and database management. The app has features such as finding a lost item and found item status in a hotel, send the message using push notification in android, IOS and send the mail and SMS. Worked with windows service to host the WCF service, UI Design, database handling and implement push notification.

Responsibilities:

• Involved in development and testing of the application in different environments.

• Analyses the Application Requirement.

• Get the information from API and Send the message using pus notification in android, IOS and send the mail and SMS.

Anuj Kumar

SUMMARY

• 5 Years of experience in Software Development and Web Development using .Net Technology, ASP.Net c#, MVC, OOPS, SQL Server and WCF, Angular 5.

• Hands on experience in Designing by using HTML, Development of the Client/Server (Web) applications, APIs and Services using Microsoft Technologies.

• Gained exposure in project management activities including scoping, estimation, planning, finalisation specifications, resource administration and quality management of the software application.


17 of 24

• Comprehensive knowledge of end-to-end implementation of the SDLC; including finalisation of specifications, development, implementation and quality.

• Possess excellent interpersonal, communication and analytical skills with demonstrated abilities in customer relationship management.

QUALIFICATION

B.Tech (CS) from UPTU, Mathura in 2012

TECHNICAL SKILLS

Programming Languages C#, OOPS, SQL Server and WCF, JS.

Web Technologies Asp.Net, MVC, Entity Framework, Web API, WCF, LINQ, Angular 5

Database SQL Server 2012, SQLite

Operating System Windows 10

Scripting and UI JQuery

PROJECT DETAILS

Project # 1


Duration Dec 2016 to Till Date

Environment Visual studio 2012,Sql Server 2012,JS,WebApi


This delivers a full suite of payments solutions. From card issuing to acquiring; from payment gateways to merchant accounts; from fraud and risk to compliance; from digital wallets and mobile to invoicing - we process millions of transactions worldwide and we value our relationships at every point in the process.

Responsibilities:

• Being a single point of contact handled all the environments.

• Complete JIRA task on time.

• Discussed with Customer for new requirements on existing application and Implemented successfully.

• Given Inter Organizational KT.

• Complete ticket on time given by client.

Project # 2



18 of 24

Duration Jul 2016 to Dec 2016



This web application provides the functionality to get device data and send to mobile. In this project we have created a WEB API, this API hit by mobile device and show the data on mobile dashboard. In this project we have fetched the data of device like NIKE, FITBIT, Adidas sports device.

Responsibilities:

• Involved in deploying the application on different environments.

• Resolving the post production issues on priority basis to the client

Project # 3


Duration Mar 2016 to Jul 2016



This web application provides the functionality to Align-fi team to create Audit and perform all process of Audit. This follows a workflow and having a Notification mailing functionality there to intimate the users.

Responsibilities:

• Involved in deploying the application on different environments.

• Understanding the architecture of MVC applications.

• Involving in Design for HTML.

• Analysis, Interface Design & Coding (Front & Back End).

• Resolving the post production issues on priority basis to the client

Project # 4


Duration Jul 2013 to Mar 2016



This MCS web application consist several modules like


19 of 24

• Underwriter.

• Admin.

• Sales Rep.

• Proposal.

• Funding module etc.

Basically MCS is like a financial Bank to provide Loan to customers. This application provides all facilities and functionality to MCS Team like underwriter, admin to create project for particular user project type is Loan and Advance, admin of the organization to keep the all information of all the Users. So it reduces paper work all information are online easier to maintain. Application provides all funding calculation to MCS Team so everything is easy for Team.

Responsibilities:

• Client interaction for requirements, sprint plans, and deliverables.

• Analysis, Interface Design & Coding (Front & Back End).

• Involved in part of API development

Vikash Singh

SUMMARY

• International Software Testing Quality Board certified Software Test Engineer with work experience of 3.7 years in IT.

• Expert in Manual Testing with the strong knowledge of Design of Use Cases and Functional Scenarios, Coverage of Complete Scenarios, Test Data Creation, Test Case Design, Regression Testing, GUI and Usability Testing and Bug Reporting.

• Entering and maintaining bugs into Defect -Tracking System.

• Exposure to all stages of Software Test Life Cycle.


20 of 24

• In-depth experience in Performance testing with Jmeter.

• Experienced user of: Selenium Web Driver, Postman and Jmeter.

• Experienced in IPhone and IPad testing.

• Experienced Android phone and Tablet testing.

• Have sound experience deploying Automation Tools.

• Quick learner and excellent team player, ability to meet tight deadlines and work under pressure.

QUALIFICATION

• Bachelor of Engineering in Information Technology from Maharishi Dayanand University, 2013.

TECHNICAL SKILLS

Operating Systems: Windows XP, Windows 7 & Windows 10

Databases: SQL Server

Bug Tracking Tools: JIRA, VSTS

Performance testing Tool: Jmeter 3.0

Automation Tool: Selenium

PROJECT DETAILS

Project # 1


Duration Jul 2014 to Dec 2014

Environment Windows, JIRA



21 of 24

This project is a patent pending software that instantly converts a pdf to a web form for users to fill out directly.

Client can upload a blank fillable pdf into the application and fill it online .Once filled Users can extract that filled data using excel or csv file. Users can also upload a filled pdf to the application and extract the data using excel or csv file.

Responsibilities:

• Analysed client requirements for the project.

• Prepared test cases & Test conditions for the requirements.

• Performed PDF mapping for the PDF in Application.

• Kept track of the new project requirements.

• Estimated the Project’s future requirements.

Project # 2


Duration Dec 2014 to Oct 2016

Environment JIRA, Selenium Webdriver


This is a Sales Force project in which Corporate User has the power to create Offices and Employees. Corporate user has a residual income tab which calculates residual income for offices and its agents using a calculation wizard.

In the Office Portal: Opportunities, Leads and Clients are created. Users can directly create clients or convert opportunities and leads into clients. Users can add Tasks, Notes, Email, Call for created clients and leads. Under office we can create four types of agents and can calculate residual income for agents.

Office has the power to create, Employee Agent, Sale Agent, Partner Agent and different agent has to the power to create and manage lead opportunities and client etc.

Responsibilities:

• Actively participating in client calls.


22 of 24

• Prepared the Software Test Plan.

• Prepared test cases for the requirements.

• Reviewed the requirements document.

• Created new automation scripts as per client requirements using Selenium Web driver.

• Updated current scripts as per change in requirements.

• Ran the automation Test suite.

• Kept track of the new project requirements.

Project # 3


Duration Oct 2016 to Dec 2017

Environment VSTS


This project is for a background screening company, providing users various background screening services like: county search, MVR, Employer Verification, and Aliases etc.

Project had two logins - super admin and organization admin.

Super Admin: Super admin has various organizations beneath it. It provides screening services to its organizations applicants. It can give users various access permissions.

Organization admin - sends consent letters to applicant on their email id. Once it is submitted organization can process it and provide feedback accordingly to their applicant.

Responsibilities:

• Actively participated in client calls.

• Prepared test cases for the requirements.

• Performed API testing using Postman.

• Performed Device testing for Android and iOS Devices.

• Reviewed the requirement document.

• Kept track of the new requirements from the Project.

• Estimated the Project future requirements.


23 of 24

3.0 Roles and Responsibilities

The Prospective Contractor should describe the roles and responsibilities they feel are needed by each party.

Instructions: Provide a listing of roles and responsibilities for each party.

Project Manager (PM) – is the liaison between the Client and Chetu team. Ensures the team is meeting its milestones and deliverables, according to the agreed upon Project Plan, and communicates status, hurdles and adjustments to the client. Additionally, this PM (a Subject Matter Expert) lends insight and guidance to overcome project challenges.


24 of 24

Team Lead (TL) – is complimentary to the client and not identified until pre-kickoff. The TL is the internal project Team Leader. The TL is responsible for assuring that team members meet their individual milestones and deliverables.

Xamarin Developer (XD) - Develops, enhances and designs mobile applications for the Android and iOS operating systems, using the Xamarin framework which enables the building of native Apps for iOS, Android, and Windows with a shared codebase. XD is responsible for: debugging, choosing libraries and frameworks and working with UI/UX designers to create a secure, seamless mobile experience.

Web Developer (.NET) - Programs our solution to run from the web server to the web and mobile browser. WD is responsible for: designing, building and maintaining the software app; developing content criteria; and coordinating with QA to validate test routines and schedules to ensure that test cases mimic external interfaces, addressing all browser and device types desired by AAD.

Quality Assurance (QA) - Ensures that the app meets the requirements to perform as designed by assessing quality of specifications and our technical documents. The QA Engineer creates detailed, comprehensive test plans/cases for relevant, actionable feedback.

Template T-4

Requirements Approach

Response Template

RFP #: SP-18-0072

Arkansas Agriculture Department Mobile Device Data Collection Solution RFP #: SP-18-0072 Template T-4 –Requirements Approach

2 of 17

Table of Contents

1.0 Technology Approach .......................................................................................... 3

2.0 Software ................................................................................................................. 4

3.0 Users ...................................................................................................................... 5

4.0 Database Design and Management ..................................................................... 6

5.0 Workflow ................................................................................................................ 7

6.0 Initial Form Creation ............................................................................................. 8

7.0 Form Design and Capabilities .............................................................................. 9

8.0 Reporting ............................................................................................................... 9

9.0 Security ................................................................................................................ 10

10.0 Support ................................................................................................................ 11

11.0 Training ................................................................................................................ 15

12.0 Lessons Learned ................................................................................................. 16

13.0 Issues, Challenges and Potential Risks ............................................................ 17


3 of 17

1.0 Technology Approach

Our Mobile Device Data Collection Solution (MDDCS) enables multiple users (150+) to interact with it simultaneously. Multi-tenancy is an architecture in which a single instance of a software application serves multiple customers; each customer is called a tenant. All web based applications provide a session, which is like a thread. So every time a user logs in with a User Id and Password (as seen below) it is their tenancy. Because multiple users will be able to log in concurrently, our solution empowers Arkansas Agriculture Department (AAD) with a multi-tenant environment.

While our response protocol does not afford the creation of a wireframe for an Administrative User Interface (UI), the forthcoming (MDDCS) UI naturally gives the Administrator (Admin): permissions, change configurations, reference data, etc. corresponding to the modules (cited in T1).

All User onboarding will be done by Admin with role based access.

Traditionally, On-Premise installation of SQL server (in the Racks) is done after procuring the license from the vendor. Once installed, we can choose the package- standard, enterprise, etc.; it also encompasses reporting, like SQL Server Reporting Services (SSRS).

The web application (App) is hosted on IIS, Apache or Tomcat based on the technology chosen.

To publish the App we will use a sandbox (like Bitbucket, Github etc.) and live accounts within the App stores (iOS and Android). The User goes to the store and downloads the App onto their

Describe how your solution provides a multi-tenant environment.

Describe the administrative user interface. Please provide information around the features provided including screen shots to visualize the user interface.

Describe how an on-premise installation of your solution is configured. What is the process for installation of the back-end SQL as well as installing the apps on mobile devices.


4 of 17

mobile device (phone/tablet). These applications can be installed manually if AAD does not want to host on external App stores.

All major browsers can be configured…

In particular, (MDDCS) is configured for: IE8/IE9/IE10 - which covers approximately 90% of IE users; configuration for IE7 will require additional efforts; and -

Firefox 15 – 48: covers approx. 90% of Firefox users.

O/S: Windows, MAC (32 bit or 64 bit), Android, iOS. .Net (Visual Studio 2015?), Google Material Design Android Studio 2.2?, Xcode 7.3.1, Swift, Core Java and Android

New OS versions, requires Chetu to employ Configuration/Compatibility Tests to verify the operation of the system or application on different software & hardware configurations. If an update is needed, Chetu will provide a patch. This is supported under the All Purpose and Apportion support plans.

2.0 Software

If AAD does not desire to have the App store or Google Play Store to host the App. Users can use a browser to access (MDDCS) via the website to install the App manually, then navigate its modules

(MDDCS) can be downloaded from the App Store or Google Play, after entering credentials provided to them via email by Admin.

Describe the versions of browsers supported by your solution.

Describe the versions of Operating Systems supported for Android, Windows, and Apple. Additionally, describe the process for testing new OS versions as they are released and how any patches are provided if needed.

Describe what applications and software need to be downloaded to mobile devices for your solution to function properly. Describe where a user will need to go to download the software/applications (i.e. Contractor website, app store, etc.).


5 of 17

No additional software or application is required as this is a web based platform; the only thing a User needs is a web browser. Or, as mentioned above a User can access the App via an App Store, should this be desired by Admin.

3.0 Users

Users are created by the Administrator (Admin) Admin has permission to create/onboard, edit, or soft delete a User. This log is stored in the Database. Admin can also control and create different roles (User types). These different roles (User types) are assigned to Users to control their access. See the Flow Diagram below:

Describe what applications and software need to be downloaded to desktops and servers for your solution to function properly. Describe where a user will need to go to download the software/applications (i.e. Contractor website, etc.).

Describe your system(s) user creation and management process. Please include, at a minimum, how users are added and deleted from the system, a list of user types that are currently available out of the box, and how existing user types can be modified or customized to meet the State's needs.

Describe any flexibility that is available within the system to create additional user types not available out of the box, but required by the State.


6 of 17

To upgrade the licenses with the server, the current application will not be involved, as the App will be upgraded by a system Admin when required.

This is part of the publishing process scripts or MSI. There will need to be some permissions for the virtual directory.

This is an Admin feature, where Admin can create a grouping, via drag and drop.

4.0 Database Design and Management

Describe your solutions ability to upgrade licenses with the server environment.

Describe the process to set up permissions within your solution.

Describe the process to set up groups within your solution

Please provide a brief description of the systems design and how this system is managed once it is determined to be fully functional and live? What type or types of maintenance will AAD be required to perform and how often, daily, weekly, monthly, etc.


7 of 17

The Architecture below displays how the ‘Model, View and Controller’ works with Entity Framework:

We are developing 3 tier architecture for MVC5 applications +Entity framework, keeping layers separate so only the DAL (Dedicated Access Line) knows about entity framework.

AAD will need a System Admin to address infrastructure related issues. A Level 1 support resource who can address calls or incident tickets is also required. A Level 2 developer/Designer who can support the application from a programming

standpoint and fix any production bugs or change requests is required.

5.0 Workflow

The (MDDCS) App will have an Admin to provide access to Users (HQ, Field service Users, etc.).

Initial activity is for the Admin and users to create forms (a % with Chetu in training). o Data types include: TEXT, NUMERIC, LOCIGAL, plus (SQL accessible).

Users drag and drop controls to create forms. Once a form is finalized the same can be converted into a: PDF, CSV, XML or JPEG format - saved against a category.

Users in field can use the form of their assigned project to fill and submit details.

Describe the solutions’ workflow capabilities. Please discuss configurability of various workflows for forms, reporting, basic workflow, etc.


8 of 17

6.0 Initial Form Creation

Aside from the 20 forms that we are tasked to create during training, all other forms will be created dynamically by Admin.

Users will be able to design forms utilizing multiple data types, and export them in multiple formats (listed on pg. 15 of the RFP).

Describe your organization’s approach to providing assistance to organizations when creating

an initial batch of forms.

The discussion should follow all requirements set forth in Section 2.10.


9 of 17

7.0 Form Design and Capabilities

(MDDCS) will have an Admin to provide access to Users and field service users as well. Initial activity is for the Admin and users to create forms (see display for example). They can drag and drop controls to create forms. Once form is finalized the same can be

converted into a PDF form which will be saved against a category. Users in field can use the form of their assigned project and fill and submit details.

8.0 Reporting

Microsoft Power BI is implemented providing a robust range of insightful reporting, including:

Real-time charts with different aggregation types

Data drill down with filtering

Viewing capability available on desktops and mobile devices

Role-based data filtering

Please provide a brief description of the process of creating a form from inception to field inclusion within the SQL database.

Describe your solution’s reporting capabilities and how it meets requirements set forth in RFP Section 2.12.


10 of 17

Role-based access control

Ad-hoc reporting capability

Ability to distribute reports via email

Reports can be emailed in formats citied on page 15 of the RFP. Also, custom reports can be created based on different filters and date selection:

Daily Reports

Weekly reports

Monthly reports

Drilldown reports

Graphs

Pie charts

Etc.

9.0 Security

Security Go-Live onward:

For Data at rest the Device transactions will be through SSL -Secured Socket layer (TLS).

All data is point-to-point encrypted. If required, a base 64 algorithm can be used to encrypt and decrypt. SSL certificate is installed on the server IIS. Database is also connected using entity framework.

Please provide a brief description of the security features available including, data at rest on the device, data in transit, and data storage. Will any additional features be necessary aside from those security features inherent to using a SQL database?


11 of 17

10.0 Support

Product performance and reliability –designed to specs– is a formidable reason why we enjoy a near 47% repeat customer rate. Even so, systems do occasionally present problems / bugs. Upon delivering the application to specifications, we provide two Maintenance and Updating options.

Service Level Agreement (SLA) – Whereby, the client purchases 100 hours (per year) for bug fixes, updates and enhancements. If hours are not used, they do not accrue, or roll over to the next year.

All Purpose Plan (APP) – Whereby, Chetu maintains (fixes bugs) the application for a one-time payment of , good for one year.

Apportion Plan – When the Client selects the All Purpose Plan (APP), the support period is at least three (3) years, Chetu enables the client to spread the total cost of the project and three (3) years of support into a monthly payable amount, for a term of 36 months. After 36 months all licenses and intellectual property will be provided to the client.

2.18 SUPPORT GO-LIVE SUPPORT A. The Contractor shall provide a detailed list of specific activities for go-live in their

Implementation Plan in Template T-5 of their response.

B. Go-live shall be dependent on successful UAT (See Section 2.17)

POST GO-LIVE SUPPORT A. The Contractor shall provide on-going user support beginning at the time of Go Live

and continuing for the life of the contract.

o Understood; and accounted.

B. The Contractor shall:

1. Provide Standard Support to designated State Personnel via telephone, at

minimum, Monday-Friday, 8am-4:30pm CST, excluding State Holidays.


Describe in detail how software maintenance is handled. This should include a discussion regarding the following topics: What is included in your maintenance package? How does your organization’s support services meet all requirements in Section 2.18? Will the state be required to upgrade to the latest version of software as it is released? What type of user support is available during maintenance periods?


12 of 17

2. Provide English speaking Telephone Support Staff.


3. Provide resolution of High Priority Issues within four (4) hours. High Priority must

include at a minimum connectivity issues across the entire system.


4. Provide resolution of Medium Priority Issues within twenty-four (24) hours.

Medium Priority must include issues relating to or symptomatic of affecting a specific department or location.


5. Provide resolution of Low Priority Issues within three (3) days. Low Priority must

include issues relating to a single item such as those which would affect a single user, device, or location.


C. All ongoing user support costs shall be included in Table 5 and 8 of Template C-1 –

Official Bid Price Sheet.


ONGOING SYSTEM MAINTENANCE AND UPDATES A. The Contractor shall provide on-going regular updates and maintenance to the

solution.

o See All Purpose Plan (10. Support)

B. The Contractor shall provide all maintenance and updates to the solution in

accordance with the requirements below:

The Contractor shall furnish to the State, 30 calendar days prior to go-live, Quality Assurance Guidelines for testing new updates, patches or upgrades to the software solution.

o Understood; and agreed.


13 of 17

The Contractor shall ensure that any solution updates or maintenance will not compromise or negatively impact or interrupt any configurations or customizations made by the Contractor or AAD to the solution.

o Understood; and agreed.

The Prospective Contractor’s should address these topics in the applicable sections of Template T-4.

C. All ongoing system maintenance and update costs must be included in maintenance

and support fees included in Table 5 and 8 of Template C-1 – Official Bid Price Sheet.


Embracing a customer-centric approach, we fully realize that software applications are developed to ease and facilitate business processes. We believe that applications must comply with certain basic rules in terms of usability, effectiveness and acceptability. Our experience has helped us identify crucial elements in software applications that bring the highest ROI to our customers.

Analysis and Design | Our staff works extensively with the client, realizing that customer input and interaction is crucial. Through proper analysis and design sessions, we take extra care to thoroughly understand requirements before embarking onto the software design and implementation phase. It ensures that the end-product is exactly what the customer wants and envisions.

Development | Our experience in working through the complete software development lifecycle [SDLC], from the analysis, design, implementation and testing phase, going live, through to maintenance and support, ensures there are no transition or training issues.

Maintenance & Updating | Chetu’s track record, stability and long-term commitment, encourages clients to choose us to do the maintenance and support for the final application. This eliminates many headaches, in terms of training, after going live.

Provide a brief descriptive summary of your software development methodology for product enhancements and include a description of your testing and quality assurance process prior to release.


14 of 17

Intellectual Property and Ownership | Software developed and delivered as part of this project shall be deemed “work made for hire” and Chetu agrees that any and all rights of Chetu to the software shall be assigned to AAD as its sole and exclusive property.

Quality Assurance Consistent user operability for performance is a must. Chetu provides QA/Testing Services to ensure the functionality of the AAD’s solution, including: Unit Testing, Build Verification Test, Business Cycle Test, Regression Testing, Boundary Test, Database Integrity Test, and more. Specific to AAD, we will employ the following tests:

a) Load Tests: Determine whether or not the application or system can handle the projected loads and determine where the application or system fails to handle the load.

b) Volume Tests: Verify that the system successfully functions under the following high volume scenarios:

i. Maximum (actual or physically-capable) number of clients connected, or simulated, all performing the same, worst case (performance) business function for an extended period

ii. Maximum database size has been reached (actual or scaled) and multiple queries or report transactions are executed simultaneously

c) Stress Test: Verify that the system functions properly and without error under the following stress conditions:

i. Little or no memory available on the server (RAM and DASD [Direct Access Storage

Device])

ii. Maximum actual or physically capable number of clients connected or simulated

iii. Multiple users performing the same transactions against the same data or accounts

iv. One user performing the same transaction multiple times

d) Soak Test: Soak testing is running a system at high levels of load for prolonged periods of time. A soak test would normally execute several times more transactions in an entire day (or night) than would be expected in a busy day, to identify any performance problems that appear after a large number of transactions have been executed.


15 of 17

The frequency of upgrades is dependent on AAD’s needs. Chetu will create a scalable solution that can be easily expanded to meet your requirements. There is no downtime required during an upgrade and Chetu will ensure all customizations and configurations are maintained while upgrading. The standard user support will be available during and after major and minor updates.

Chetu will create user manuals for reference post Go Live. Additionally, we can create a configuration and troubleshooting document.

11.0 Training

From the project kickoff Chetu will work collaboratively with AAD to create a solution that integrates seamlessly with your internal workflows to minimize training requirements. Chetu’s objective is to create an intuitive experience that will stay true to current processes for all users. Beyond this, our project managers work closely with AAD’s key personnel to demonstrate functionalities and workflows. These interactions can be recorded and used as training material.

Additionally, Chetu will provide a professionally written training plan or manual for the AAD upon request. If the AAD selects Chetu to write such a manual for this project, we will charge an additional fee of per hour for a Technical Writer to create a User Manual and FAQ list. These will be easily accessible through a URL and can be downloaded via PDF for printing. Before going live, to ensure a full technical and user knowledge transfer to the AAD staff via onsite training.

Provide an overview of your major and minor release cycle process. In your discussion please include the following:

What is the frequency for major and minor upgrades? What is the typical down time required for major and minor upgrades? How are customizations or configurations maintained during an upgrade? What type of user support is available during major and minor upgrades?

Describe how your company will provide on-going user support per the requirements set forth in RFP Section 2.18 Post Go Live Support.

Describe your organization’s approach to training and how it will meet the requirements set forth in Section 2.19.

Describe how your company will ensure all training is completed sufficiently in advance of “go-live”.


16 of 17

Before going live, to ensure a full technical and user knowledge transfer to the AAD staff, Chetu proposes three (3) series of trainings with a duration of five (5) days each to train the following user groups:

1. System Administrators – 5 days 11/22/18 - 11/28/18

2. System Designers – 5 days 11/29/19 – 12/5/18

3. Field Users – 5 days 12/6/18 – 12/12/18

During each of these sessions Chetu will cover the following topics:

• How to Access Technical Support including by phone and electronically

• Troubleshooting Common Problems

• How to utilize the Dashboard

• Report Generation

• System Configuration and Maintenance

• Form Creation

Chetu has Technical Writers who can provide AAD with an owner’s manual or user’s manual upon request. Unfortunately, we cannot provide a sample of a previous client’s owner’s/user’s manual due to it containing the client’s proprietary and confidential information. If your facility selects Chetu to write an owner/user manual for this project, Chetu will charge an additional fee of per hour for a Technical Writer.

12.0 Lessons Learned

Provide sample training material that has been used in past implementations of similar size and scope to AAD’s requirements.

AAD learns from the experiences of others. The Prospective Contractor should describe what it sees as the success factors and primary challenges in implementing the solution. Please describe any “lessons learned” from the Prospective Contractor’s relevant experience and how those lessons learned will impact the Prospective Contractor’s approach to this engagement.


17 of 17

Primary Lesson Learned: The solution may have a problem, however, the problem has a solution. Chetu will plan to make the solution work and when there are bugs, there is a plan for that.

13.0 Issues, Challenges and Potential Risks

Security standards Third party dependencies. Undefined components – e.g. API definitions; API level of availability or completeness. Undefined dependencies.

AAD is interested in any information that may help to identify issues, clarify the requirements, reduce risk of the procurement, and identify issues and challenges of managing and implementing the proposed Solution. Describe the primary concerns, risks, issues and recommendations for AAD as it proceeds with this SOW.

Template T-5

Required Plans

Response Template

RFP #: SP-18-0072


Template T-5 – Required Plans

i

Table of Contents

1.0 Implementation Plan ............................................................................................. 1

2.0 Testing Plan ........................................................................................................... 5

3.0 Training Plan ......................................................................................................... 6



1

1.0 Implementation Plan

The Prospective Contractor should submit a Work Plan regarding the implementation of all services requested under this RFP. This Work Plan will demonstrate that the Prospective Contractor has a thorough understanding of all activities required. AAD requires that the Prospective Contractor provide a schedule with the shortest duration required to implement the services smoothly and without interruption to business operations.

The Work Plan should show all key elements including details with responsibilities, timelines, durations, milestone dates, deliverables, and Prospective Contractor personnel hours by deliverables, State personnel hours, and all critical dependencies for the milestones and deliverables. The Work Plan may be an attachment to the Vendor’s Technical Proposal and tabbed as such in the submission as well as an electronic soft copy (Microsoft Project ® or equivalent and Adobe ® PDF) version in the Prospective Contractor’s electronic submission of the Technical Proposal.

All content should be formatted for effective viewing in hard and soft copy.

Instructions: Provide a Work Plan including at least:

High level Project schedule (Microsoft Project® preferred and Adobe ® PDF) including all deliverables and milestones, and timeline

A listing of what staff is assigned responsibility for each deliverable within the WBS to the level at which control will be exercised (i.e., AAD, Contractor staff)

Major milestones and target date(s) for each milestone

Definition of the review processes for each milestone and deliverable and a description of how the parties will conduct communication and status review

Include or attach associated artifacts such as Gantt charts and flowcharts as appropriate.

▪ Below is our high level Work Plan necessary to address the solution; the table following it displays the man-hours necessary to fulfill the solution:

Task Name Duration Start Finish Predecessors Resource Names

Arkansas Agriculture Dept.

203 days Mon 6/4/18 Wed 3/13/19

Requirements gathering & Analysis

2 days Mon 6/4/18 Tue 6/5/18 .NET Resource, Xamarin Resource

High level and detailed design document

10 days Wed 6/6/18 Tue 6/19/18 2 .NET Resource, Xamarin Resource

Back office application

23 days Wed 6/20/18

Fri 7/20/18



2

Role based access 1 day Wed 6/20/18

Wed 6/20/18

3 .NET Resource

Multi-tenant 2 days Thu 6/21/18 Fri 6/22/18 5 .NET Resource

User onboarding 2 days Mon 6/25/18 Tue 6/26/18 6 .NET Resource

Active directory login authentication.

1 day Wed 6/27/18

Wed 6/27/18

7 .NET Resource

Form Processing 2 days Thu 6/28/18 Fri 6/29/18 8 .NET Resource

Transaction history 2 days Mon 7/2/18 Tue 7/3/18 9 .NET Resource

Email alerts and Scheduling

2 days Wed 7/4/18 Thu 7/5/18 10 .NET Resource

Google, Outlook calendar integration.

2 days Fri 7/6/18 Mon 7/9/18 11 .NET Resource

Reports: Microsoft Power BI

9 days Tue 7/10/18 Fri 7/20/18

Real-time charts with different aggregation types

1 day Tue 7/10/18 Tue 7/10/18 12 .NET Resource

Data drill down with filtering

1 day Wed 7/11/18

Wed 7/11/18

14 .NET Resource

Viewing capability available on desktops and mobile devices

2 days Thu 7/12/18 Fri 7/13/18 15 .NET Resource

Role-based data filtering

1 day Mon 7/16/18 Mon 7/16/18 16 .NET Resource

Role-based access control

1 day Tue 7/17/18 Tue 7/17/18 17 .NET Resource

Ad-hoc reporting capability

1 day Wed 7/18/18

Wed 7/18/18

18 .NET Resource

Ability to distribute reports via email

2 days Thu 7/19/18 Fri 7/20/18 19 .NET Resource

Form Design Tool 31 days Mon 7/23/18

Mon 9/3/18

Drag and drop components

3 days Mon 7/23/18 Wed 7/25/18

20 .NET Resource



3

Workflow based Rules Engine – user rules.

4 days Thu 7/26/18 Tue 7/31/18 22 .NET Resource

Business user workflows ability.

2 days Wed 8/1/18 Thu 8/2/18 23 .NET Resource

Queue based assignments in workflow.

2 days Fri 8/3/18 Mon 8/6/18 24 .NET Resource

Data driven application configurations.

3 days Tue 8/7/18 Thu 8/9/18 25 .NET Resource

User Manual for creating forms

1 day Fri 8/10/18 Fri 8/10/18 26 .NET Resource

Voice based recognition

2 days Mon 8/13/18 Tue 8/14/18 27 .NET Resource

RFID 2 days Wed 8/15/18

Thu 8/16/18 28 .NET Resource

Field validation 3 days Fri 8/17/18 Tue 8/21/18 29 .NET Resource

Test and review forms from the tool.

4 days Wed 8/22/18

Mon 8/27/18 30 .NET Resource

Save draft 2 days Tue 8/28/18 Wed 8/29/18

31 .NET Resource

Prepopulate form fields from reference data.

3 days Thu 8/30/18 Mon 9/3/18 32 .NET Resource

Service layer 12 days Tue 9/4/18 Wed 9/19/18

Import export API 5 days Tue 9/4/18 Mon 9/10/18 33 .NET Resource

Form Processing API

5 days Tue 9/11/18 Mon 9/17/18 35 .NET Resource

TLS encryption 2 days Tue 9/18/18 Wed 9/19/18

36 .NET Resource

Field Services 33 days Wed 6/20/18

Fri 8/3/18

Online/offline feature – geofencing data update.

3 days Wed 6/20/18

Fri 6/22/18 3 Xamarin Resource



4

Geofencing feature – for tracking contractor.

3 days Mon 6/25/18 Wed 6/27/18

39 Xamarin Resource

Location services. 2 days Thu 6/28/18 Fri 6/29/18 40 Xamarin Resource

Docusign integration of forms

4 days Mon 7/2/18 Thu 7/5/18 41 Xamarin Resource

Notifications for new events.

3 days Fri 7/6/18 Tue 7/10/18 42 Xamarin Resource

Form Processing. 2 days Wed 7/11/18

Thu 7/12/18 43 Xamarin Resource

Fillable forms 5 days Fri 7/13/18 Thu 7/19/18 44 Xamarin Resource

TLS encryption 1 day Fri 7/20/18 Fri 7/20/18 45 Xamarin Resource

Unit and testing-Mobile

10 days Mon 7/23/18 Fri 8/3/18 46 Xamarin Resource

SQL implementation as well as during the initial

10 days Thu 9/20/18 Wed 10/3/18

47,37 .NET Resource, Xamarin Resource

utilize data types TEXT, NUMERIC, LOGICAL (and others readily available in SQL and Access) plus image files for input/output.

30 days Thu 10/4/18 Wed 11/14/18

48 .NET Resource, Xamarin Resource

user manuals 3 days Thu 11/15/18

Mon 11/19/18


Configuration and troubleshooting document

2 days Tue 11/20/18

Wed 11/21/18


Training 15 days Thu 11/22/18

Wed 12/12/18


QA 10 days Thu 12/13/18

Wed 12/26/18




5

UAT 12 days Thu 12/27/18

Fri 1/11/19 53 .NET Resource, Xamarin Resource

Production Support 10 days Mon 1/14/19 Fri 1/25/19 54 .NET Resource, Xamarin Resource

Human Resources Man Hours

1 FREE shared Project Manager (US) – 10+ years’ experience

1 FREE shared Team Lead

1 .NET

1 Mobile Developer (Xamarin - Hybrid)

1 QA

= 1,360 hrs.

= 1,096 hrs.

= 80 hrs.

2,536 billable hrs.

2.0 Testing Plan

Chetu will have a two phase approach to Quality Assurance and testing to ensure the viability of AADs custom solution:

1. QA 10 days Tuesday 12/13/18 – Wednesday 12/26/18 2. UAT 12 days Thursday 12/27/18 – Wednesday 1/11/19

QA testing will be a ten (10) day sprint starting 9/25/18 – 10/8/18. During this time Chetu’s QA engineers ensure the functionality of the AAD’s solution by performing Unit Testing, Build Verification Test, Business Cycle Test, Regression Testing, Boundary Test, Database Integrity Test, and more.

When QA is complete we initiate a UAT phase. Members from AAD will interact with the application to identify flaws. If everything is up to AADs standards, we implement the solution into production. If there are errors found the, Chetu will fix them.

3.0 Training Plan

Instructions: Provide a Training Plan.

The Training Plan should demonstrate that the Prospective Contractor has a thorough understanding of all activities required to effectively train staff as specified in the RFP.

The Training Plan should show all key elements including details with responsibilities, timelines, staffing, and durations.



6

From the project kickoff Chetu will work collaboratively with AAD to create a solution that integrates seamlessly with your internal workflows to minimize training requirements. Chetu’s objective is to create an intuitive experience that will stay true to current processes for all users. Beyond this, our project managers work closely with AAD’s key personnel to demonstrate functionalities and workflows. These interactions can be recorded and used as training material.

If this does not suffice, Chetu will provide a professionally written training plan or manual for the AAD upon request. If the AAD selects Chetu to write such a manual for this project, we will charge an additional fee of $20 per hour for a Technical Writer to create a User Manual and FAQ list. These will be easily accessible through a URL and can be downloaded via PDF for printing.

Before going live, to ensure a full technical and user knowledge transfer to the AAD staff, Chetu proposes three (3) series of trainings with a duration of five (5) days each to train the following user groups:

1. System Administrators – 5 days 11/22/18 - 11/28/18 2. System Designers – 5 days 11/29/19 – 12/5/18 3. Field Users – 5 days 12/6/18 – 12/12/18

During each of these sessions Chetu will cover the following topics:

• How to Access Technical Support including by phone and electronically

• Troubleshooting Common Problems

• How to utilize the Dashboard

• Report Generation

• System Configuration and Maintenance

• Form Creation

• Form Usage (data entry)

All content should be formatted for effective viewing.

Include or attach associated artifacts as appropriate.

Template T-6

RFP Response Checklist

RFP #: SP-18-0072


Template T-6 – RFP Response Checklist

i

Table of Contents

1.0 Prospective Contractor Response Checklist ...................................................... 1

2.0 Prospective Contractor Attachments .................................................................. 2

3.0 Exceptions ............................................................................................................. 3

List of Tables

Table 1. Prospective Contractor General Requirements ...................................................... 1

Table 2. Prospective Contractor Package 1 Checklist .......................................................... 1

Table 3. Prospective Contractor Package 2 Checklist .......................................................... 2

Table 4. Prospective Contractor General Requirements ...................................................... 2

Table 5. Prospective Contractor Attachment Checklist ........................................................ 2



1

1.0 Prospective Contractor Response Checklist

The Prospective Contractor should complete the following Tables to verify that all the RFP response requirements have been completed as instructed. The Prospective Contractor should provide specific references to Proposal locations (e.g., section and page numbers) for each Template included. During the evaluation process, OSP will perform an initial review of the Proposals to confirm these are included. If the items identified in this checklist are not included, the Proposal may be disqualified.

Instructions: Complete the following Table. Do not change any of the completed cells. Any changes to the completed cells could lead to the disqualification of the Proposal.

Table 1. Prospective Contractor General Requirements

PROPOSAL RESPONSE ITEM COMPLETED AND

PROVIDED AS INSTRUCTED?

Prospective Contractor’s Proposal’s stamped date meets date and time specified in the RFP

YES X NO

Proposal is sealed YES X NO

Technical Proposal and Cost Proposal are sealed in separate envelopes or boxes within the “Sealed Bid.” Each Proposal should be clearly marked “Technical Proposal” or “Cost Proposal”

YES X NO

Minimum Mandatory Requirements – The Prospective Contractor has documented proof that it meets the minimum mandatory requirements outlined in the RFP.

YES X NO

Table 2. Prospective Contractor Package 1 Checklist

SECTION / TEMPLATE



REFERENCE TO

PROPOSAL RESPONSE

SECTION

T-1 Cover Letter and Executive Summary YES X NO

T-2 Prospective Contractor Experience YES X NO

T-3 Prospective Contractor Engagement Organization and Staffing

YES X NO

T-4 Requirements Approach YES X NO

T-5 Required Plans YES X NO

T-6 RFP Response Checklist YES X NO



2

Table 3. Prospective Contractor Package 2 Checklist

SECTION / TEMPLATE



REFERENCE TO

PROPOSAL RESPONSE

SECTION

C-1 Cost Workbook YES X NO

Table 4. Prospective Contractor General Requirements

Prospective Contractor should provide the following documents with their technical proposal response.



EO 98-04 Disclosure Form. (See Standard Terms and Conditions, #27. Disclosure.)

YES X

NO

Copy of Prospective Contractor’s Equal Opportunity Policy. (See Equal Opportunity Policy.) YES NO X

Voluntary Product Accessibility Template (VPAT). (See Technology Access.) YES NO X

2.0 Prospective Contractor Attachments

The Prospective Contractor should identify all attachments that are part of the Technical or Cost Proposals. The Prospective Contractor should provide specific references to Proposal locations (e.g., section and page numbers) for each attachment included. All attachments must be included in both soft and hard Proposal copies.

Instructions: Complete the following Table with any attachments to the Technical or Cost Proposals. Add rows as necessary. Do not change any of the completed cells. Any changes to the completed cells could lead to the disqualification of the Proposal.

Table 5. Prospective Contractor Attachment Checklist

ATTACHMENT ID

ATTACHMENT NAME ATTACHMENT

PROVIDED?

REFERENCE TO

PROPOSAL RESPONSE

SECTION

NA YES NO

YES NO

YES NO

YES NO

YES NO

YES NO



3

3.0 Exceptions

Any requested exceptions to items in this RFP which are NON-mandatory must be declared below or as an attachment to this page. Prospective Contractor must clearly explain the requested exception, and should label the request to reference the specific solicitation item number to which the exception applies.

Exceptions to Requirements will cause the Prospective Contractor’s proposal to be disqualified.

NA

SP-18-0072 Mobile Device Data Collection Solution Prospective Contractor Name CHETUArkansas Agriculture DepartmentTemplate C-1 - Official Bid Price Sheet

Instructions: Insert your company's name on this tab in the yellow highlighted cell. No further information is necessary to be completed on this tab.

The Total Costs for each category listed on this tab will be automatically inserted once the Vendor fills information on the second tab.

Table 1 Total CostTable 2 - Licensing Fees -$ Table 3 - Implementation Fees 58,328.00$ Table 4 - Training 16,200.00$ Table 5 - Maintenance and Support 17,498.00$ 1 Year Grand Total Cost 92,026.00$

SP-18-0072 Mobile Device Data Collection Solution Prospective Contractor NameCHETU Arkansas Agriculture DepartmentTemplate C-1 - Cost Workbook

Instructions: Insert your company's name on this tab in the yellow highlighted cell. Insert costs in the yellow highlighted cells for each table. Do not fill in any other information on this table.

Table 2Approximate Users

Cost Per User/Per Month Cost Per Month Cost Per Year

Licensing Fees - Initial Contract Period 150 -$ -$ -$ *Provide the cost per user for all licensing fees as required in the RFP. This includes all maintenance and support as required in the RFP.

Table 3 Total CostImplementation Fees $ 58,328.00 *Provide the total, one time cost for all implementation activities necessary to fully implement the system. The cost proposed will be an all-inclusive cost in order for the Contractor to successfully complete all implementation activities in order for the system to Go-Live.

Table 4 Total CostTraining 16,200.00$ *Provide the total cost for all training activities required in the RFP.

Table 5 One Year CostMaintenance and Support 17,498.00$ *Provide the one year cost for all maintenance and support as required in the RFP.

Table 6 - Not EvaluatedCost Per User/Per Month

Licensing Fees - Additional Users -$ *Provide the additional cost per user for all licensing fees as required in the RFP.

Table 7 - Not EvaluatedApproximate Users

Cost Per User/Per Month Cost Per Month Cost Per Year

Licensing Fees - Renewal Period 150 -$ -$ -$ *Provide the cost per user for all licensing fees as required in the RFP.

Table 8 - Not Evaluated Year 2 Year 3 Year 4 Year 5 Year 6 Year 7Renewal - Maintenance and Support 17,498.00$ 17,498.00$ 17,498.00$ 17,498.00$ 17,498.00$ 17,498.00$ *Provide the cost for all maintenance and support as required in the RFP for renewal periods 2 - 7.

Table 9 - Non Evaluated Cost Per UserAdditional Training $25/hr. Remote*Provide the cost per user for any additional training requested by AAD.

Documents

Template T-1 · 1.0 PROPOSAL SIGNATURE PAGE Type or Print the following information. PROSPECTIVE CONTRACTOR’S INFORMATION Company: Chetu, Inc. Address: 10167 W. Sunrise Blvd., Suite