Friday, July 7, y

Tracksafe
TechM Proposal notes
Summary items:
• Nice proposal in short turn around. TM has solid team responding to requests.  
• Excellent level of detail for architecture, specifically, the solution architecture diagram is
solid start for this early in the process.
• Requirements:  Details need to be vetted by the TS team.  Not much detail here.  
◦ Concern: Geo Fence feature out

TechM Response-Pls detail out the specific requirement related to Geofencing

• Milestones: This approach does not deliver in time for the conference demo or the early
customer adoption. 
◦ This is business decision for Jim and Susan.  
◦ Or work to massage to proposal to meet these objectives.

TechM- Already covered in previous query

• Is this a fixed price proposal.  The answer to this will dictate further questions.  
◦ Frankly, we want fixed price if possible. In this scenario will need to nail down
requirements extremely solid as any deviation will invoke a change that will result
in increased cost.
◦ If this is not fixed price, we will need details of the resources, experience and rate
card
◦ No T&C’s included.  Needs to be addressed 

TechM: This is a fixed price proposal.  

•Engagement: this looks like a waterfall, black box engagement. Define requirements,
they go away and build it, and then we test it.  This is a bad approach.  
◦ They did not explicitly call this out, so we need to implement an operational
cadence during the development phase that provides visibility to the burndown of
epics and associated stories.  Use jira for this.
◦ Recommend 2 week sprints with demos. 
◦ Twice weekly scrums with TS team to clarify requirements
◦ ongoing email and instant messaging for team questions
◦ Weekly project review.  Please provide project review template 
◦ Monthly Sponsor review. 
TechM Response: Covered in the previous queries.

• Biggest overall concern with the proposal is controlling quality and predictability of
delivery (as addressed above)

1
 Friday, July 7, y
◦ Beware of statements regarding company experience that applies to this project.
We need to assure we get resources assigned who actually delivered on IoT
projects and specifically using Telit to solve similar problems. 
◦ Talent assigned to our project team: 
▪ experience level for their area of expertise
▪ Explicit Telit experience (need 1-2 seniors with this)
▪ Attrition - plan to proactively and reactively address team attrition, along
with clear visibility to team attrition as it occurs.  (India has 30 day notice
period, so they will usually know 30 days in advance when someone is
leaving).  If attrition occurs and impacts project date or quality, they need
to remediate this.  

TechM Response: We are formalizing this and it will take more to respond.
◦ Code quality
▪ Implement thin layer of Engineering best practice measures. 
▪ I have these and can select top items to address, like static code analysis
reports integrated into build, and external architecture and a handful
of external code reviews along with internal collaborative code review
▪ Performance guarantee to certain number of devices, etc
▪ Security guarantee - explicitly describe how product is being build
securely.  Consider 3rd party pentest. If fails, then they must remediate.  

TechM-Static code analysis had already been factored. Others like performance & security items
may take a bit time to respond. We may cover in the revised proposal.

◦ Deliverables:
▪ Need build/deploy automation as a deliverable in source repository
▪ Automated unit tests as deliverable

TechM-Will be updated in revised proposal.

◦ Warranty - 6 months due to slower customer adoption cycle requiring 

TechM-Will be updated in revised proposal.

Other details:

IoT experience:
• describe and provide details regarding each IoT project where Telit platform was used
• How many people and who specifically has attended Telit training?  Will they be
assigned to our project? 
• describe any IoT project with similar characteristics tracking items, notifications,
alerting, and other key features
• who from these projects will be assigned to this project.  Get names and track team
member names, attendance, attrition, and potentially time by team member as part of
weekly or monthly review.

2
 Friday, July 7, y
• Did any of your Table 2 TechM IoT Engagements leverage Telit? (Generally none were
very similar to our product)
• Would you recommend another IoT platform instead of Telit?  Is there another that
would reduce dev or operational cost significantly?  Maybe ask these, depending on
where you are regarding Telit as an A player in the market. or to gain insight into future
direction and options)
TechM Response: We are formalizing and we will share all above details in revised proposal
4.2 Out of Scope
• Any items related to platform enhancements / customization - I assume this is in regards
to Telit platform.  Do you anticipate needing any enhancements or customizations?
(more later as they don’t detail how they intend to leverage Telit in much detail)
TechM Response: Not at this point of time
• Geo Fencing out - same concern addressed above
• IoT Platform is out of scope - what do you mean by this?
TechM Response: Proposing the IoT Platform and their commercial are considered out of
scope.Here it is assumed that Telit Iot plarform will be provided to techmahindra on
which solution will be developed.
• License costs for 3rd party API - do you anticipate any costs related to this item?
TechM Response: -Google map API/ services etc,will be updated in the revised proposal
• Code changes to 3rd party library or module - do you anticipate needing any?
TechM Response: - Not at this point of time.

5 Solution and Approach

• As show in diagram above paragraph - Describe what you will build versus what you will
use in Telit for rules, data model, event config, business logic, user & role mgmt, and
device mgmt.
TechM Response: -
1) Use-
 Device management
 Application development-Enterprise integration
 Administration & security
 event config using triggers which may in turn invoke business logic
 Data management
o Current timeseries Device data 6 month
o Low cost external storage- TS need to detail out the data retention and analytics req.
 Device management
 Connectivity management

2) Build-
Business Logic Module will leverage Telit Iot platform capabilities as much as possible
to implement
 Business logic
 Rules
 user & role mgmt.

3
 Friday, July 7, y
 event config

• Describe how the variants of the Telit Platform will be used

TechM Response: Different modules/ variants will be used through exposed API also
using appropriate agents.Details will be covered in the revised proposal.

•overall more clarity on what they build versus what they will use in Telit.  any risks or
concerns around these assumptions?   This is where the estimate will grow substantially if
their assumptions are not correct. 
• No perf testing - need perf guarantee.  Estimate for perf test scripts.  This will be more
important down the road as we want to assure we stay ahead of customer load
TechM Response: Already cover in previous queries.
• Mobile Apps - Guarantee App Store acceptance

6.1 Tech Stack

• Any other frameworks that will used? 
TechM Response: -Java along with Spring and Hibernate framework will be used for application
development
• No Data Analytics tech stack mentioned - is this excluded? 
TechM Response: -Pls detail out the analytics requirement. Currently it is not included in scope.

7 Testing
• Won’t you implement automated unit tests?  
TechM Response: -Junit is considered.
• Test case documentation and repository?
• Test cases should be part of deliverables – 
TechM Response: -SIT test cases will be provided.
• Test coverage metrics - how do we know you actually tested all code, branches and
paths? 
TechM Response: -What is the percentage of code coverage is being expected.
• Duration of acceptance testing - if no automation, then more time will be needed to retest
new builds

8 Deliverables 
• Add Test cases
• Add Unit Test code 
• Add Build/Deploy automation
TechM Response: -SIT test cases will be shared. We may use the existing build/deploy tool used
any,else We may propose the automated tool, Commercials may impact.

• All stored in a shared repo we can see and inspect during the project
• Requirements - Functional requirements document will be created and iteratively
reviewed throughout the project. It will include all Epics and then story level, stored in
Jira that we retain post project

4
 Friday, July 7, y
•Defects tracked in Jira (Note:  we will need to pay for jira and any other Atlasssian
products we use.  This is a great low cost set of tools and will pay for itself.  Bitbucket is
good code repot with good code review capability built in, Confluence for docs, hip chat
for communication, etc.  We can pick and chose what we want to use.)
• Add Detailed Architecture documentation (including transaction sequence diagrams, etc) 
TechM Response: -Architecture document will be shared

9 Warranty
• 6 months is industry standard for software needing slower adoption.  If we retain TM for
maintenance and further enhancements, they should do this.  If we do not commit to this,
they will not.  We should get 3 months in this case.
TechM Response: We will provide updated commercials in revised proposal based on 6 month
warranty support.
• Ask - what would ongoing support and maintenance cost?  Get them to cost this now as
an option we can select at end of project.  

10 Project governance etc - addressed in summary section

10.3 Project plan

• Add dates 
• What is delivered on milestone 1? 
• Can we get milestone deliveries to meet our business needs? 
TechM Response: We will add in updated proposal

11 Assumption and dependencies

• TS will provide dev test and UAT prod / hosting - this means TS has AWS account 
• TS will provide all req’d devices - Describe how you will build and test with these
products in India
• All required s/w licenses will be provided by TS - what is anticipated?  Provide list and
costs
Iot Platform
Google map API/Services
Jira

• Change request procedure - if this is fixed price, we need to nail requirements explicitly.
So expect more time up front. The risk is things will change. The other risk is that the
requirements are not explicit and interpretation will be out of sync between TM and TS.
In this case, we must have excellent detailed requirements document.  We need to
provide structure to how requirements are written and accepted.  Generally, this takes
more time, so will be a challenging topic.
• No perf or security testing.  Need perf and scale guarantee so that if we have issues in
prod, this is a defect.  We can also write requirements on this to insure quality we need is
acceptable. 
• Native - No offline support - Jeff and I discussed.  Is this a concern? 

5
 Friday, July 7, y

TechM Response: We are working on it and a few clarification is required from your side. Post
that we will update in revised proposal.