Mobile Workforce Pilot

sprocketexponentialΚινητά – Ασύρματες Τεχνολογίες

10 Δεκ 2013 (πριν από 3 χρόνια και 8 μήνες)

203 εμφανίσεις


RESPONSE


To



STATEMENT OF WORK (SOW)


FOR



Mobile Workforce Pilot


By



Contact Details

Vendor Name

Prelude Systems, Inc.

Proposal Submitted by

Craig Oliver

Contact Details

Email :
coliver@preludesys.com

Telephone Number:
512
-
582
-
7507

Facsimile Number:
909
-
801
-
2369

Date of Submission


September 30, 2013











Page |
2

Table of Contents

Table of Contents

................................
................................
................................
.......................

2

Cover Letter

................................
................................
................................
...............................

5

Executive Summary

................................
................................
................................
...................

6

1.

Business
Organization:

................................
................................
................................
.......

7

2.

System Concept and Solution:

................................
................................
............................

9

2.1.

Vision

................................
................................
................................
...........................

9

2.2.

Cultural
-
Change Approach

................................
................................
..........................
10

2.3.

Scope of Work

................................
................................
................................
............
10

2.4.

Solution Definition and Approach

................................
................................
................
14

2.5.

Out of Scope

................................
................................
................................
...............
21

2.6.

Assumptions

................................
................................
................................
...............
21

2.7.

Capabil
ities (functional, technical and process)

................................
...........................
25

2.8.

Communication Plan

................................
................................
................................
...
39

2.9.

Sustainability Plan
................................
................................
................................
.......
40

2.10.

Change Management Process

................................
................................
................
42

2.11.

Knowledge Transfer/Transition

................................
................................
................
42

2.12.

Project Management Plan

................................
................................
.......................
43

2.13.

Infrastructure, Architecture, Integration Design

................................
........................
46

3.

Program:

................................
................................
................................
............................
58

3.1.

Project Plan

................................
................................
................................
................
58

3.2.

Techn
ical factors

................................
................................
................................
.........
59

3.3.

Milestones

................................
................................
................................
..................
61

3.4.

Progress payments

................................
................................
................................
.....
61

3.5.

Deliverables

................................
................................
................................
................
63

3.6.

Service Level

................................
................................
................................
..............
63









Page |
3

3.7.

Period of Performance

................................
................................
................................
63

3.8.

Methodology
-

ongoing consultation, facilitation, and training

................................
......
63

3.9.

Workshop Approach

................................
................................
................................
...
64

4.

Pro
ject Management Structure:

................................
................................
..........................
66

4.1.

Engagement Model

................................
................................
................................
.....
66

4.2.

Organization Chart

................................
................................
................................
......
67

4.3.

Project Organization Plan

................................
................................
...........................
67

5.

Prior Experience:

................................
................................
................................
...............
68

6.

Roles and Responsibilities:

................................
................................
................................
69

6.1.

Qualifications & Resumes of Proposed Key Staff

................................
........................
71

6.1.1

Project Manager
-

Chandilvel Singaravelu

................................
...........................
71

SUMMARY

................................
................................
................................
........................
71

SKILLS

................................
................................
................................
..............................
73

PROFESSIONAL EXPERIE
NCE

................................
................................
.......................
73

EDUCATION & CERTIFIC
ATION

................................
................................
......................
79

6.
1.2

Enterprise Architect


Jayaraman Palaniappan

................................
....................
80

SUMMARY

................................
................................
................................
........................
80

SKILLS

................................
................................
................................
..............................
80

WORK EXPERIENCE

................................
................................
................................
........
81

6.1.3

Utilities, Infor Hansen and esri ArcGIS SME/Analyst
-

Paul McKnight

..................
85

SUMMARY

................................
................................
................................
........................
85

SKILLS

................................
................................
................................
..............................
85

WORK EXPERIENCE

................................
................................
................................
........
85

EDUCATION/CERTIFICAT
IONS

................................
................................
.......................
87

6.1.4

Senior Mobility Developer
-

Srinivasaraju Datla

................................
...................
88

SUMMARY

................................
................................
................................
........................
88









Page |
4

SKILLS

................................
................................
................................
..............................
88

WORK EXPERIENCE

................................
................................
................................
........
89

EDUCATION/CERTIFICAT
IONS

................................
................................
.....................

101

6.1.5

Senior Mobility Developer


Vigneshwer Shanmugasundaram

..........................

102

SUMMARY

................................
................................
................................
......................

102

SKILLS

................................
................................
................................
............................

103

WORK EXPERIENCE

................................
................................
................................
......

103

EDUCATION/CERTIFICATIONS

................................
................................
.....................

113

6.
1.6

Business Analyst / Quality


SriPriya K Padmanabhan

................................
......

114

SUMMARY

................................
................................
................................
......................

114

SKILLS

................................
................................
................................
............................

114

WORK EXPERIENCE

................................
................................
................................
......

114

EDUCATION/CE
RTIFICATIONS

................................
................................
.....................

1
16

7.

Proprietary Information:

................................
................................
................................
....

117

8.

Authorized Negotiator:

................................
................................
................................
.....

117

9.

Cost Proposal:

................................
................................
................................
.................

117

9.1.

Manpower

................................
................................
................................
.................

117

9.2.

Cost of supplies and materials

................................
................................
..................

118

9.3.

Other itemized direct costs

................................
................................
........................

118

9.4.

General and administrative burden (if applicable)

................................
.....................

119

9.5.

Travel expenses

................................
................................
................................
.......

119

9.6.

P
rinting

................................
................................
................................
.....................

119

9.7.

Total cost schedule

................................
................................
................................
...

119

10.

Miscellaneous:

................................
................................
................................
..............

120

10.1.

Cu
stomer/Vendor
-
Furnished Equipment and Work Space

................................
....

120

10.2.

Invoices

................................
................................
................................
.................

120









Page |
5


Cover Letter


September

30,

2013


David Kucko

Corporate Contract Administrator

124 W. 8th
Street

Suite
308

Austin, TX 78701



O
n behalf of Prelude Systems,

thank you for the opportunity to respond to the Statement of
Work (SOW) for Mobile Workforce Pilot from the Austin Water Utility (AWU).

The services described in this documen
t reflect our core competencies and o
ur strengths in the
area
of
Mobile
Application Development
and enterprise integration.

Over the last decade
PreludeSys
has
been a pioneer

in building Windows, Android, Blackberry OS and iOS based
enterprise mobile applications
.

AWU

and PreludeSys share similar corporate values. Among the
se similarities, there are two
which are resoundingly clear:
Reliable

and Service Excellence. As these are the driving forces
within our separate enterprises, they will become unifying forces within our continued strategic
partnership.

We appreciate the op
portunity to submit our response to
AWU

and look forward to a long
lasting, mutually beneficial relationship.



Sincerely,


Craig Oliver

512
-
582
-
7507



Direct

210.708.6371


Mobile

Email:coliver@preludesys.com











Page |
6

Executive Summary


PreludeSys
understands the scope of work (SOW) requested by the
Austin Water Utility
(
AWU
),
for
Mobility Workforce Pilot

project.
PreludeSys

has reviewed the
project SOW and
we are
proposing a
5

month effort to begin on
01/03/2014

and
complete by

05/31/201
4
.


PreludeSys

is pleased to offer
Mobile development and enterprise integration
with INFOR
Hansen, GIS
services. Our experience in delivering
solutions and
projects at Texas Health and
Human Services Commission, Department of Aging and Disability and othe
r State of Texas and
City agencies

will be an asset to making this pilot program a successful one. Our
functional
expertise in
GIS
applications, thorough understanding of
Mobile Application platform
development
,
proven delivery of mobile solutions for Fortune 500 corporations
along with
industry standard best practices

for mobile development and enterprise integration

will make us
a distinguished partner for AWU
.


PreludeSys would like to take this opportunity to list the values and alignment towards
AWU

goals and this project specifically as below,

1.

PreludeSys is well experienced and accustomed to DIR’s Texas Project Delivery
Framework having executed multiple proje
cts under the DBITS model with Texas State
Agencies.

2.

PreludeSys has successfully delivered enterprise mobile solutions for Fortune 500 such
as
General Motors, Twentieth Century Fox, PepsiCo, Universal Music Group among
others.

3.

PreludeSys has successfully m
odernized a critical 3000 + User Case Management
system and a public website that provides Quality Review data on
p
roviders for another
Texas State Agency under HHSC.

4.

PreludeSys has
a structured practice for implementing

SOA
including
Websphere ESB,
Proces
s Server components for State of Texas agencies and also with implementing
one of the largest Oracle SOA implementation

for General Motors
.

5.

PreludeSys has also successfully implemented 508 compliant
a
ccessibility standards on
for several
Texas State
Agencies

projects
.

6.

Our critical success factors for prior engagements with Texas State Agencies were on
-
time delivery, thorough documentation, exhaustive knowledge transfer and transition to
maintenance activities.

7.

The
t
echnologies identified in the
follow
ing section
are
the
core competencies of
PreludeSys.












Page |
7

1.

B
usiness Organization:


a)

Company Name:

Prelude Systems, Inc.


b)

Principal place of business


Address


: 5 Corporate Park, Suite #140

City



: Irvine

State



: California

Zip Code


: 92606


c)

Facility
responsible for servicing the contract

Address




:

12708 Riata Vista Circle
,

Suite A
-
104

City




:

Austin

State




:

Texas

Zip Code


:

787
27


d)

Indicate whether you operate as a partnership, corporation, or individual.

PreludeSys is a “C” co
rporation incorporated in 1999.


e)

Include the State in which you are incorporated or licensed to operate

California


f)

About the company

PreludeSys brings a breadth of unique skills and core competencies in Project Management,
Application Development,
Maintenance and Support, Business Intelligence
-
Analytics, Service
Oriented Architecture (SOA), Legacy Modernization, and emerging technology expertise in
Business Process Management (BPM), Content Management, Mobile, Cloud and Intelligence
solutions.

The t
able below illustrates our core Competencies,

Application Development

ASP.Net, Java, JEE, Cobol, Rules Engine

Emerging Technologies
(BPM, Content
Drupal, Force.com, iOS, Android and other Mobile
development
tools and technologies, Hadoop, Tableau, Big
-








Page |
8

Management, Mobile, Cloud
and Intelligence)

Insights and other Big Data technologies

Databases

Microsoft SQL Server, Oracle, Sybase, DB2, MySQL

SOA

Oracle SOA, IBM Websphere
, ESB, IBM Process Server

Business Intelligence

IBM Cognos, SAP Business
Objects, Microstrategy, Netezza

Legacy

PowerBuilder, Visual Basic, Model204, Sybase

Overall PreludeSys has been providing the following IT services to organizations that include
private and government for over 13 years:



Application Maintenance and Suppor
t (13 Years)



Business Intelligence & Data Warehouse (8 Years)



Service Oriented Architecture (SOA) (9 Years)



Project Management (13 Years)



Technology Migration/Upgrade and Transformation (13 Years)



Application Development (13 Years)



Enterprise Mobility



SharePoint

PreludeSys has been providing deliverable
-
based services to Texas State agencies as a direct
supplier for the past 4 years and 10 months in the following areas:



Application Maintenance and Support



Service Oriented Architecture (SOA)



Project Man
agement





Technology Migration/Upgrade and Transformation



Application Development

PreludeSys has also been providing IT services to Texas State agencies as a
subcontractor
for more than 10 years

in the following areas:



Application Maintenance and Support



Service Oriented Architecture (SOA)



Technology Migration/Upgrade and Transformation



Application Development



Business Intelligence









Page |
9

2.


System Concept and Solution:



2.1.

Vision


PreludeSys has holistically and diligently reviewed AWU’s
SOW and appreciates AWU
’s

vision,
decision and approach to

extend

their
enterprise application
s

to their mobile workforce.

PreludeSys envisions every engagement with its customers and more specifically any
engagement for Enterprise Mobility with the following approach,


PreludeSys

has analyzed AWU requirements exhaustively and has brought together

a wide
range of capabilities to provide a comprehensive Mobility solution encompassing hardware
,

software and services leveraging,




Prelu
deSys core competency expertise



Subject Matter Exp
erts with e
xhaustive Utilities experience



E
xpertise in Infor Hansen and
ESRI

GIS technologies



IBM Worklight Mobile Application Development Platform



Panasonic
Ruggedized Devices










Page |
10

This
above
strategy will
help
address AWU’s requirements and define a comprehensive,
sustainable, and maintainable approach and solution that AWU can
continually leverage to
add
value to its Mobile Workforce.

This
approach will

enable AWU

to,



provide a seamless single
-
entry work order
workflow that can be accessed remotely



increase productivity by

a
n

automated
inventory management



reduc
e

and potentially elimina
te

manual transcription errors

and data loss errors



access to data and solutions remotely


2.2.

Cultural
-
Change Approach


Based on
PreludeSys extensive experience and expertise in Information Technology,
organizations experience cultural change issues when venturing upon legacy modernization and
emerging technology implementations.

In AWU’s case this is related to extending enterprise

appli
cations and solutions to their mobile
work force using Enterprise Mobility

technologies. PreludeSys understands this need thoroughly
and suggests

the following approach for user adaptation of the solutions and
to
address cultural
change needs,



Contin
uous engagement and discussions with business

and users



Prototype/wireframes demonstrations



Iterative approach to solution release and demo



Training

with ea
sy

access to user manual



Helpdesk and exhaustive hand holding support



Last but not the least, get
the user community educated ahead of time


2.3.

Scope of Work


Purpose



Perform single
-
entry work order creation, update, and retrieval



Provide remote capability to lookup work order related Information.



Provide remote capabilities for inventory management



Pr
ovide remote capability to view GIS data, and engineering documents.



Provide remote capability to create, edit, and delete GIS features.



Investigate and implement, where appropriate, other workflow enhancements through
the use of mobile systems
.









Page |
11



Replicat
e application database permissions on mobile device.



Incorporate functionality from the work order system’s advanced modules.

Vendor Responsibilities




Validating the high level requirements previously gathered by AWU and documented.



Defining the project’s detail
-
functional requirements



Developing a mobile solution based on the high level and detailed
-
functional
requirements.



Recommending devices and types for the mobile solution based on role and functional
need.

The pilot is expecte
d to utilize multiple types of devices, PDA’s, laptops, tablets,
smart phones, GPS equipment, etc.



Developing pilot application(s) to demonstrate the recommended mobile solution on a
variety of mobile devices in both the Treatment and Pi
peline Operations
program areas




Integrating with existing AWU applications using the Enterprise Service Bus (ESB) in the
IBM Websphere Process server v7.x as its integration platform. It is mandatory for the
solution being proposed by
the Vendor to use that toolset.



Propos
ing a mobile software development framework for continued development of
mobile solutions. The framework must adhere to open standards and minimize effort to
develop and publish applications on a variety of mobile operating systems and mobile
device types



Proposing and implementing an industry
-
leading, standard
-
based mobile infrastructure
intended to be used in support of COA
-
owned and BYOD mobile devices for
telecommunications, security, hardware, software, and integration.

Project
-
Based Services



Validate

the list of high
-
level requirements generated by the AWU Project Team.



Prepare a detailed functional
-
requirement document for the Pilot Project.



Develop a pilot solution based on the high
-
level (See Appendix A) and the to
-
be
-
defined
detailed
-
functional
requirements.

a.

Demonstrate the recommended mobile solution with a minimum of 15 mobile
users for each program area for a total of 30 devices used during the pilot, using
a variety of mobile devices (i.e., ¼ VGA), Tablets, Laptops, Convertibles, Smart
Device
s, GPS etc.).

b.

Integrate with the INFOR EAM system.

c.

Integrate with the INFOR Hansen system.

d.

Integrate with the
esri

GIS system.









Page |
12



Investigate and propose a mobile software development framework for use within AWU
for the mobile pilot and all future mobile

projects. At a minimum the framework should
include:

a.

Support for variety of mobile device platforms, to include iOS, Android, and
Windows

b.

Software development kit that adheres to nationally recognized open standards

c.

Integration capabilities must be executed using the AWU platform of IBM
Websphere Process Server Enterprise Service Bus

d.

Customizable templates specific to utility industry and maintenance functionality

e.

Ability to render solutions to a variety of mobile d
evice types

f.

Remote software deployment and management capabilities

g.

Compatibility with virtual environments. Any server class software components to
be virtualized within the AWU network must be compatible with
VMware
.

h.

Expected Compatibility with existin
g AWU and COA systems



Investigate and propose mobile devices for use within AWU for the mobile pilot and all
future mobile projects. At a minimum the devices should include:

a.

Devices to be based on need and role of the user

b.

Voice and data communications.
Consideration should be made for wireless,
cellular, pager, and radio communications.

c.

Ruggedized

d.

Sunlight readable display

e.

Able to render GIS Map’s to device being used

f.

Camera (front and back)

g.

Barcode

h.

QR Code

i.

Voice annotation

j.

GPS Capability


sub
-
m
eter accuracy desired.

k.

RFID

l.

Touch screen

m.

Print capability in field

n.

Memory expansion

o.

Store and forward capabilities

p.

Dock and sync capabilities









Page |
13

q.

Device network auto sync

r.

Split
-
screen functionality



Investigate and propose a standard mobile infrastructure environment for use within
AWU for the mobile pilot and future mobile projects to securely manage mobile devices
and applications. At a minimum this should include:

a.

Secure end
-
to
-
end data transport
with encryption capabilities

b.

Integrate with existing enterprise security and identity management
infrastructure.

c.

Integrate with existing datacenter and network infrastructure.

d.

Demonstrate the recommended solution with 20 employee owned devices.

e.

Compati
bility with existing AWU and COA network devices and server
infrastructures, which may include Netmotion
, Citrix, or vSphere 5 or later. This
includes
TCP/IP version 4
,

VPN
,
Smart devices
,
Active Directory 2008 and later
and
Tivoli Access Manager
.


f.

Device
security

-

Remote
-
device monitoring and management
,
On device data
encryption and wipe
,
Remote
-
application management
,
Device tracking and
locating
,
Device lockdown
and
Time to live (delete data automatically based on
pre
-
established rules)

g.

Offline synching (real time when connected to the network, store and forward
when not)

h.

VMware

capable

i.

Internet access control

j.

Open Standards Architecture



Manage the development and architecture of solutions to support the deployment of a
pilot applicat
ion. The resulting pilot environment is expected to be production ready and
scalable to at least 2000 devices.

a.

Define and manage scope of work for the Mobile Project.

b.

Identify and communicate project risks, assumptions, and constraints.

c.

Define project co
mpletion criteria.

d.

Prepare project schedules to be achieved by the vendor.

e.

Establish relevant quality processes that will apply, such as change, acceptance,
risk, and issue management.

f.

Manage Cultural Change

g.

Evaluate the effectiveness of the pilot.









Page |
14

2.4.

Sol
ution Definition

and
Approach


Solution


Technical Definition

PreludeSys recommends AWU to consider following mobile
Operating Systems

for their Mobile
Workforce pilot and for future mobile projects.


1. iOS 5.0 and above


2. Android 2.2 and above


3.
Windows Phone 8 and above

We have made above recommendations based on their current market share and expected
growth in the future.

http://en.wikipedia.org/wiki/Mobile_operating_system

http://www.idc.com/getdoc.jsp?containerId=prUS24302813

We recommend AWU to consider IBM's
W
orklight 6.x platform to build the mobile workforce
pilot and for their future mobile projects.



IBM Worklight 6.x supports developing mobile applications for iOS, Android, BlackBerry,
and Windows Phone.



IBM Worklight uses following industry standards in its platform

1.

IBM Worklight Studio is built on top of Open Source Eclipse Integrated Development
P
latform. Eclipse IDE is the most widely used development platform for building Java
and related technologies
.

2.

IBM Worklight Studio allows mobile applications to be built using standard based
technologies like HTML5, CSS3, Javascript, XML, and JSON to bui
ld user interfaces.

3.

IBM Worklight integrates with Apache's Open Source Cordova Mobile Platform to
write and deploy hybrid mobile applications for multiple mobile operating systems
with single code base.

4.

IBM Worklight Server supports Java, JEE, PL/SQL, Java
script, Ajax, XML, REST
and SOAP Web Service, and other popular standard based technologies to write
server side programming.



IBM Worklight Server 6.x is built on top of IBM WebSphere Application Server, which
has following built in adapters, that allows i
t be integrated with variety of standard based
applications and servers including IBM's WebSphere Process Server.



1. JMS Adapter for Queue based integration.



2. SQL Adapter for Relational Database integration.




3. HTTP Adapter for REST and SOAP based

Web Service integration.









Page |
15



IBM Worklight Studio allows developers to build a single code base for mobile
applications and deploy it mobile operating systems with relative ease.



IBM Worklight Server 6.0 can be integrated with IBM Endpoint Manager or any othe
r
mobile device management platform like Airwatch to enable remote deployment and
management of mobile applications on variety of platforms like iOS, Android, Windows
Phone.



IBM Worklight Server 6.0 is certified to work with
various

platforms.



IBM Worklight will be integrated with INFOR, GIS, OMMS, Oracle, Microsoft SQL
Server
, and Other Systems via IBM Process server workflows, rules, and queues. IBM
Worklight provides a first class support in the way of integration adapters to interface
with I
BM Process Server.





IBM Worklight Platform provides following encryption support



1. Data Transport
-

HTTP over SSL (HTTPS)



2. Data at rest on mobile device
-

Encryption AES 256 and PCKS #5



IBM Worklight Platform supports following security and identit
y management integration



1. IBM Security Access Manager



2. IBM Federated Tivoli Identity Manager



3. LDAP Integration



4. Database Authentication



5. OAuth



IBM Worklight Server and the mobile solution will use Standard based technologies and
commun
ication protocols to ensure proper integration with existing infrastructure,
systems and applications



IBM Worklight Server 6.0 can run on Linux, Unix, AIX, Windows operating
systems.



Applications
that run on IBM Worklight Server 6.0 can use TCP/IP, HTTP,
H
TTPS SOAP protocols to communicate with external servers and applications.



IBM Worklight Server can run on virtualized operating systems.







The Server Platform and Solution will work seamlessly in Netmotion, Citrix, or vSphere 5
or later as we use only

TCP/IP, HTTP, HTTPS, and SOAP to communicate.











Page |
16

Infrastructure Component

IBM Worklight Platform

Mobile Application

TCP/IP

Yes

Yes

VPN

Yes

Yes

Smart Devices

Yes*

Yes

AD 2008

Yes

Yes


Tivoli IM

Yes

Yes




Remote
-
device monitoring and management


Remote

device monitoring support is
provided via IBM Endpoint Manager or via integration through 3rd part MDM solutions.



On device data encryption and wipe
-

Device encryption can be achieved via IBM
Worklight's Mobile application runtime encryption API. Remote wipe can be achieved via
integrating with Mobile Device Management solution.



Remote
-
application management
-

Yes,

Mobile Applications can be monitored,
versioned, and retired via IBM's Worklight Server administration console.



Device tracking and locating
-

Can be achieved via integrating with Mobile Device
Management solution.



Device lockdown
-

Can be achieved via in
tegrating with Mobile Device Management
solution.



T
ime to live (delete data automatically based on pre
-

established rules
)
-

Can be
achieved via integrating with Mobile Device Management solution.



Offline synching
-

IBM Worklight provides data service APIs

and networking APIs that
will allow us to write custom functions for offline synching.



VMware

capable
-

Yes, IBM Worklight Server 6.0 is certified to run on virtual
environments.



This can be achieved by controlling the device via Mobile Device Management
software’s

like IBM Endpoint Manager, Airwatch, etc.



IBM Worklight Server and Mobile Platform are built on top of following Open Standards
Architecture



IBM Worklight Server




1. Java / JEE Application Server




2. XML, JSON, REST, MQ, JMS




3. TCP/IP,

HTTP, HTTPS









Page |
17



Mobile Platform




1. Eclipse IDE (Studio)




2. HTL5, CSS3, Javascript (User Interface)




3. HTTP, HTTPS, SOAP, REST (Communication)




4. LDAP, OAuth, RBA (Authentication and Authorization)




5. AES 256 PCKS #5 (Encryption)

Solution
-

Approach

PreludeSys is careful in choosing the right project management methodology depending upon
the client environment to achieve its project objectives, execute and deliver successfully. The
methodology is proven to be planned, controlled and result
-
driven. Pre
ludeSys proposes to
manage this project based on such a methodology that has been refined based on its past
experiences to suit every life cycle stage of a project as shown in the diagram
at the same time

has considered the
AWU lean practice
.

As the firs
t step in making this project successful, PreludeSys has assembled a team that has
key personnel

who have in
-
depth experience and extensive knowledge about Texas Project
Delivery Framework and with
technical staff

who are experts in the technologies
and so
lutions
proposed for this solution.

PreludeSys will initiate the project by conducting a kick
-
off meeting to engage with
AWU
’s IT
staff and customer area business sponsors, stakeholders and users. PreludeSys will plan the
detailed activities to validate any additional/new risks or issues that need to be addressed
during the project. PreludeSys will work with the agency Project

Manager to update the project
plan with updated milestones and deliverable dates based on the actual project initiation for
Requirements Validation
,
Detailed Functional Requirements Definition,
Development, Testing,
and Demo

related
tasks
.

Based on
previo
us experience with similar projects
PreludeSys has identified to deliver the
solution in multiple stages
/gates

and has critically t
aken into account that this is a Pilot
implementation that will prove out the solution and technology which will be rolled ou
t to the
enterprise in future.









Page |
18



Discovery/Validation

Phase

The
Discovery

stage
with respect to AWU comprises of a validation phase of the requirements
identified by AWU and documented in the SOW,

PreludeSys will approach the
Validation

Phase with the following key steps:

1.

Multiple workgroup sessions to understand and
validate

with business and technical
subject matters for each
of the Use cases identified under Section 16. Exhibit A for Pilot
and understand the Additional Requirements un
der Section 17
. The following steps and
artifacts will be used during the sessions:



Templates will be used to gather information



Meeting minutes will be captured and circulated for each session



Action items log will be maintained for each session



Change o
rder log will be maintained through the sessions

2.

Multiple Joint Application Development (JAD) Sessions with the necessary experts to
validate use cases and requirements identified from the workgroup sessions.

3.

Hands on analysis of the systems and applicatio
ns by
PreludeSys Subject Matter
Experts
.

4.

Clarification Sessions based on the finding of the hands on analysis.

5.

Documentation of SRS
.

6.

SRS Signoff sessions with
AWU
subject matter experts.

Scoping
Phase

As PreludeSys response to the SOW only comprises of est
imation of the scope of work based








Page |
19

on the Use Cases identified in the SOW for the Pilot SOW, in this phase any adjustment to the
scope and estimates based on the Validation phase will be agreed upon between AWU and
PreludeSys based on a Change Management P
rocess that will be identified during the initiation
phase after project award.

PreludeSys will approach the Scoping phase with the following key steps:

1.

Joint review session of the SRS.

2.

Identify items to be discussed in the Change Management Process.

3.

Provide cost estimates for the changes agreed upon if applicable.

4.

Signoff on the Cost estimates and/or updated cost and deliverable schedule proposal.

Design
Phase

PreludeSys will approach the
detailed Functional Design p
hase with the following key steps:

1.

Technical Architecture validation meetings with
AWU
.

2.

Document SDD and SAA
.

3.

Update SRS
.

4.

SDD, SAA signoff sessions with
AWU Technical subject

matter experts.

Development

Phase

During the
Development

Phase

of the project, PreludeSys will utilize its proven solution
development methodology that
will include

development, testing and
demo

phases
:

o

The vendor will plan the detailed activities to validate any additional/new risks or issues that
need to be address
ed during the project based on the Analysis stage.

o

The vendor will work with the agency project manager to update the project plan with
updated milestones and dates for completion of Development, Testing, Deployment and Go
Live tasks.

o

Adopt an iterativ
e process to develop the solution and integrate. Currently
3

iterations have
been planned for development

Quality Assurance

Phase

During the
Quality Assurance

Phase of the project

or prior to doing a demonstration of the
solution and rollout for Users
, t
he application would go through the following testing phases
.

Unit Testing

During the development phase t
he code goes
through
Unit Testing for achieving the design
goal.

The unit testing will be done by PreludeSys developers.

Development Integration
Testing

After a particular unit of work or module has been developed and unit test
ed
, PreludeSys








Page |
20

Quality Assurance team will perform testing to make sure the application is ready for QA Test/
System Integration Test (SIT).

QA Test / System Integration Test
ing (SIT)

System Testing is a verification that checks if the build (units integrated into modules and finally
into the
solution
) meets the system specifications approved by
AWU
. This is done by
AWU

QA
Testers
who use system test cases. These system test c
ases are designed to check if the
application meets the requirement specifications in SRS. These system test cases are reviewed
by the PM/SME to check if all functionality has adequate test cases for normal and abnormal
scenarios.

User Acceptance Testing (
UAT) / Customer Acceptance Test

During acceptance testing, UAT test cases are used which are designed to test the final product
in the intended environment to check if the application meets
AWU

business requirements.
These are reviewed by the Project Manag
er (PM) /SME/Customer to ensure that all business
scenarios are covered by the test cases
.

The user interface to be developed will be
strictly adhering to the Agency Standards and will be
tested by
AWU

Quality Assurance team if it meets the same.

Assessment/Lessons Learnt

As part of the project kickoff, PreludeSys will define functional and technical requirements and
critical success factors that are key to the success of this project. PreludeSys as part of its
project delivery methodology will per
form assessments at the end of each phase. Using
assessment reports and requirements traceability PreludeSys will continuously monitor the
project progress to ensure that there is continuous progress to not only meeting the
requirements but also satisfyin
g the critical success factors of the project. The assessment
reports will document the issues and lessons learnt through the phase and iteration so that the
subsequent phases can avoid running into those issues either during the next phase or during
the
project implementation after the pilot phase.

The assessment reports will document
ed

but is not limited just to detailed project issues, risks,
technical challenges, integration patterns, detailed device usage by staff, usage pattern,
potential devices r
equired, resource utilization, potential resource availability issues, training
required for customers, technical staff and business areas. PreludeSys will also prepare
a pilot
evaluation report that analyzes
the cost/benefit, effectiveness and efficien
cie
s achieved during
the pilot.

PreludeSys will utilize these assessment reports and publish a unified assessment report with
all of the details detailed above to AWU staff.

Demonstration/Rollout Phase

During this phase as per AWU requirements the solution wi
ll be deployed to a total of 30
devices, 15 each for the Operations and Pipeline programs and another 15 bring your

own
devices used by AWU staff.









Page |
21

2.5.

Out of Scope


1.

Functionality that is not identified as part of Statement of Work will be considered a
change
request or new proposal.

2.

Changes to any external applications or systems not identified as part of Statement of
Work is considered out of scope

3.

Preparations of User Acceptance Criteria and User Acceptance Test Plans or data are
not covered under this propo
sal.

4.

Maintenance and support of
solution after the demonstration is not automatically
included and will be dependent on further engagement model approval and processes
associated with it.

5.

Setting up testing or production
environment

is not
included

in the proposal.
The SOW
required a demonstration of the mobile solution only and not a production deployment.

We assume that the
AWU infrastructure

team will be setting these up

if required by AWU
to further continue with a rollout
.

6.

Conversion or
data
,
i
ncluding

load and transformation is not included.


2.6.

Assumptions


Scope



PreludeSys has made the following assumptions based on the statement below in the SOW
(Section 3.2)
. Also Appendix A has been clarified as referring to Section 17. Additional
Requirement
s as per the RFQ


Q&A
-

Mobile Workforce Pilot

document.


The goal of the mobile pilot project is to demonstrate the requirements in Appendix A
can be achieved. It is expected that, after the detailed
-
functional requirements are fully
defined by the vendo
r, the scope of the pilot will be agreed upon by both the Vendor and
AWU. However, at a minimum AWU desires to provide our mobile and inventory
workforce the ability to remotely add, edit, view and complete Service Requests, Work
Orders, conduct basic inve
ntory operations, reference equipment and asset histories,
GIS data, and documents in real
-
time from the field. The vendor shall identify in their
response to this SOW which of the requirements listed in Appendix A they initially plan to
implement during t
he pilot.”

a.

The proposed approach,

solution,

project plan, resources and cost estimates
are
limited to
the
Mobile Function Specifications identified in Section 16. Exhibit A of
AWU SOW.









Page |
22

b.

The Pilot will not address all of the Section 17.
Additional
Requirements

(PreludeSys
has identified the list of requirements that will be addressed as part of the Pilot in
separately below
)
.

c.

The validation and definition of detailed requirements
of Section 16. Exhibit A is
expected to be within a
reasonable
set of
clarifications of the Mobile Specification
Realization, Pilot Use Case Scope and Interface Descriptions as PreludeSys cost
estimates are based on these details provided in the SOW.

d.

If the actual requirements vary a lot i.e., beyond a reasonable level of co
m
fort,
PreludeSys expects this to be addressed through a Change Management Process
that will be agreed upon award.



PreludeSys assumes that AWU will procure devices, software, hardware if required to be
deployed on a Production Server or Development Server
within AWU for the purposes of the
Pilot. PreludeSys will only provide an estimate of the cost for the same.



There are no changes anticipated to the Enterprise systems.

Change M
anagement Process



Considering this is a Pilot project with a lot of technology
that will be proved out using the
Pilot project, PreludeSys expects AWU to consider a reasonable approach to situation when
the course of direction deviates in a large scale with respect to technology, hardware etc.



Any changes in our assumptions, modifica
tion to requirements, scope or fun
ctionality may
impact the timelines, resources and hence the

cost of the project and
is expected to
go
through a change request process.



PreludeSys will meet with
AWU

within a week of the project award and will mutually
es
tablish an agreed upon Project Change Request (PCR) process and a communication
and escalation plan.



Delays impacting the execution dates of critical path activities will go through a mutually
agreed upon impact analysis and subsequent change request proce
ss.

R
esources



PreludeSys

Project Manager

will be the
sole point of contact to
AWU

Project Manager and
will be responsible to refer to other PreludeSys staff as required
for meetings and
interactions with
AWU

staff, stakeholders and users.



This
SOW

will require time from
AWU

staff
(business SME’s and information resources)
and
will be requested
through a
single point of contact

which will be
AWU

Project Manager who
may
direct to other resources if required
for the life of

the project
for

analysis, r
equirements
gathering, design, development, testing, deployment and post implementation support
activities.



AWU

will coordinate requirements meetings with business Users.









Page |
23



AWU will make available any Technical SME’s required for Infor Hansen, EAM,
esri

ArcG
IS,
OMMS and other systems impacted.



PreludeSys staff will report to PreludeSys Project Manager all activities and tasks to
PreludeSys staff will be assigned by PreludeSys Project Manager.



PreludeSys shall be solely responsible to onboard and offload resou
rces as per the various
requirements of the SOW deliverables throughout the duration of the project.



PreludeSys resources will be performing their tasks spread across AWU facilities,
PreludeSys Austin Development Center and Irvine Development Center.

Proje
ct Initiation

and Approach



The project is scheduled to begin on a mutually agreed upon date. Any delays in project
initiation will delay the respective delivery dates.



PreludeSys assumes it will be a few days between project award and kick
-
off to assemble
team and logistics.



PreludeSys will leverage its
project management and
software development life cycle
methodology

as defined in the Section “Project Management and Software Development
Methodology”

which

has been successfully suited and
adapted to meet
A
WU’s request to
consider Lean practices
.



Existing documentation
and access to c
urrent In
-
House applications

(Infor Hansen, EAM,
ESRI

and OMMS)

and
the
database
s

will be made available to
PreludeSys

upon award
.



Technical standards will be provided to the
PreludeSys staff during on
-
boarding process.

Requirements



The requirements identified further during the validation phase will be
evaluated
after the
requirements phase and will be a separate estimate of costing will be provided.




PreludeSys understands ba
sed on the clarifications from the RFQ
-

Q&A document that
certain requirements related to technology are not mandatory and only preferable. This will
be further refined during the validation and detailed specification definition phase
.

Execution



Build and

Configuration Management support will be provided by
AWU
.



AWU

will provide infrastructure information relevant to the applications being developed for
PreludeSys to prepare Deployment plan.

Testing



All the necessary test data for UAT and System test will
be provided by the
AWU
.

Go Live









Page |
24



PreludeSys assumes that
AWU requires a demonstration of the Pilot functionality on 50
devices (15 each from the business units and 15 BYOD) as part of the completion of the
deliverables.



A production rollout / Go Live of the

solution
are

not part of this Pilot project
.

Infrastructure



AWU

will provide access to PreludeSys staff to
AWU

facilities, infrastructure both remote
and onsite in a timely manner.



AWU

will provide the development environment, equipment and work space necessary for
PreludeSys

staff to successfully complete
the SOW deliverables.



AWU

will procure infrastructure as required for development, test and production.

Data



The current data
model/
structure will be made available to the
PreludeSys

upon award
.



There are not much Data Definitions or Manipulation activities anticipated from this Pilot
SOW

Deliverables



Deliverables will be spread through the life of the project and will have correspondi
ng review
periods respectively.



Once
AWU

has reviewed a deliverable and has been returned back to PreludeSys for
comments and/or correction, PreludeSys will mutually determine the timeline (typically 5


15 business days) for returning back the corrected deliverable and expects
AWU

to
revalidate

and approve within a reasonable timeframe typically 3
-
5 business days which can
be mutually agreed upon SOW award.



If a deliverable approval is delayed due to unforeseen circumstances not within the control
of Vendor due to delays with environment, infras
tructure, availability of resources to validate
and approve due to holidays etc, PreludeSys expects
AWU

to perform due diligence and
reasonable judgment and provide direction regarding the deliverable approval and invoicing.

Additional Requirements


A.
Remotely access and manage personal e
-
mails and documents with Microsoft Office


N
o, we have not addressed this requirement as part of the SOW response scope.

B. Access to existing field lookups and hyperlinks

If required, t
his can be achieved by exposing
the field lookups and hyperlinks via the
mobile and web apps.

C. Duplicate role based permissions of current database on remote devices.

Yes, the

solution we propose will be able to interface with existing authentication and
authorization systems that may
include Identity Management Systems, Federated Single
Sign On services, Active Directory, Database, etc.









Page |
25

D.

Adhere to current database workflows and routing rules.

Yes, we will build service components and service adapters that will interface with
workflow
s and routing rules via ESB

E. Remotely access the
Internet

and AWU intranet.

The mobile devices and mobile operating systems we recommend are capable of
accessing
Internet

and be able to connect to AWU VPN.

F. Capture and store GPS information for field e
quipment.

Yes
, mobile

devices and mobile operating systems we recommend are capable of
capturing GPS information. We will write additional functionalities in our solution to
store

transmit and associate the captured GPS information with relevant business d
ata.

G.

Remotely access the AWU Central Stores Inventory System

Yes,
w
e will build web services and message queue based interfaces within the scope of
the pilot to access AWU Central Stores Inventory System and retrieve or update
inventory related
information.

H. Attach and view associated documents for parts, equipment and work orders.

This will depend on the mobile device used by the end user. Certain version of iOS,
Android and Windows Phone devices comes with built in
capability to

view standard

document and image formats like MS Word, MS Excel, MS
PowerPoint
, PDF, TIFF, GIF,
JPEG and PNG, etc.

If the mobile workforce application is accessed
via web

browsers, the corresponding
device may need additional software to view the documents.

I. Electron
ic data capture of field images and attach to work orders.

The IBM Worklight Device Runtime software comes with capabilities to interface with
device cameras and relevant software APIs to capture, transmit and store pictures.

J. Voice activation of work o
rder & data entry comments


N
o
,
this is not included as part of the SOW response scope
.

K. Capability to add verbal and on
-
screen annotation.


N
o
,
this is not included as part of the SOW response scope
.


2.7.

Capabilities (functional, technical and process)


As a company with a global footprint, PreludeSys’

strength lies in helping
customers

achieve
their business goals by bridging the gap between a business vision and real
-
world technology
implementation. W
e take the time to understand our client’s business s
trategies and focus on
total customer and end
-
user satisfaction by providing solutions that enable companies to








Page |
26

address their changing business needs.

Process Driven Project Management

PreludeSys has experience in handling projects of varying sizes and com
plexities employing
diverse technologies and platforms, involving process driven defect free delivery models.
PreludeSys also provides a complete range of services by leveraging our domain and business
expertise having strategic alliances with leading tech
nology providers.

PreludeSys is an ISO 9001:2008 certified organization. As part of our continuous process
improvement initiatives, we are pursuing our CMMI L3 journey and will be assessed by
December 2011
.

People Competence

The core strength of Prelude
Sys is its highly motivated and empowered employees, their
expertise and experience to support all software
-
engineering activities. The highly qualified,
trained and experienced team of more than 450 members at PreludeSys brings this perspective
to practi
ce
-
assimilating relevant skills at every level of the organization. PreludeSys has
a

cumulative experience of more than
3

Million man hours of experience across different
technology areas and business domains.


PreludeSys have repeatedly delighted its
clients around the world and across industry segments
through their cutting edge IT services, Consulting services and Business Process Outsourcing
services, they strive constantly to deliver greater tangible business benefits to its clients. In
addition to

strategic consulting, their own internal technology and operational processes have
matured to a level where they are able to pass on the time, effort and cost and benefits to their
clients.

Technology

PreludeSys' capability to deliver high quality, cost
-
e
ffective IT solutions rests heavily on the
knowledge, experience and technical skills of our staff.

Technologies we work on:



Java & Open Source Framework

Java, JSP, JDBC, EJB, JINI, JAAS, Web Sphere, Web logic, CVS, MySQL, Oracle,
Apache, Struts, Spring,
JMS, Eclipse, Xdoclet.



Microsoft

.Net , C# , VB.NET, ASP.NET, ASP, SQL Server, Visual Basic, Visual C++, IIS, MTS,
MSMQ, Index Server, Visual Source Safe, BizTalk Server, Exchange & SharePoint
Portal Server, Ajax.net.



Legacy

PowerBuilder, IBM Mainframe, Mo
del 204 DBMS and IDE, Sybase



Tools

InfoPath, Team Foundation Server, Visual Studio Team
System, SharePoint Server








Page |
27

2003 and
BizTalk Server 2006.



Framework and Components

Single Sign On (SSO), Re
-
usable Web user interface, Validation block



Patterns and best

practices

Model View Controller, Front controller, Filters and cache, Data Transfer Objects, User
Interface Process Application Blocks (UIPAB)



Enterprise Application

SAP, Oracle SOA, Microsoft Dynamics, Microsoft SharePoint, ILOG, BPMN/BPEL.



Others

C++,
Oracle, CGI / Perl, XML / XSL, Networking, Design, PHP, SOA, Web Services,
Linux, Graphics/Flash, Internet Security, Mobile & Wireless, CRM, Portal Development.



E
nterprise mobility capability includes:



Expertise in creating new applications on iPhone, Blac
kberry, Android and
Windows Mobile devices



Proficiency in porting existing applications (e.g. Windows Mobile to Blackberry or
iPhone/iPad)



Capability to extend Line
-
of
-
Business applications and enhance the value of
existing systems



Augment mobile
enterprise framework development



Proficiency in growing practice like Mobile
Application Development Platform

(M
AD
P)



Partner with Sybase iAnywhere



Broad expertise in mobile development technologies such as:



IBM Worklight



.NET Compact Framework/Windows M
obile



J2ME



iPhone Enterprise SDK



Sybase Unwired Platform



Data Sync techniques along with the working knowledge of device
-
resident
databases like SQLite, Ultralite, and SQL CE



Enterprise Mobility
-

Benefits

o

Enterprise grade mobile solutions

o

Secured integrat
ion with back
-
end systems









Page |
28

o

Solutions work in connected and disconnected modes

o

Ease of deployment without interrupting the IT landscape

o

Multiple devices support

o

Makes your organization more responsive and competitive

o

Shorten decision cycles by providing
access to information from anywhere

PreludeSys Experience with Enterprise Mobility

The capabilities of Prelude
S
ys from the three dimensions of functional, technical and process
ha
ve been provided in the form of a snapshot of
a few
projects
executed
.

1.

Client

Name

General Motors

Project Description

The client is one of the world's leading auto
-
maker who faced
material shortages that led to line stoppages of premium
shipments impacting the net contribution margin. There was
limited/no secured access to critical data like sales, supply KPI
metrics anyw
here and anytime. Customer communication was
not satisfactory without real time data updates.


PreludeSys developed a custom Cognos Dashboard for iPad
with lean
web
-
services. The reporting system was built using
our mobile solution and COGNOS connector. Interactive chart
features were developed using HTML5 components to provide
real time reports. The security functionality was handled with
single sign on feature
for authentication. Data was analyzed
with predictive analytics to notify material run
-
out situations,
tool to refresh data daily from the dump provided by customer
.The application allows sales and supply chain executives to
plan and mitigate risks in rea
l
-
time. The technologies used in
this solution were Oracle SOA, SAP ECC6, SAP SRM,
COGNOS, IBM Mainframe, iOS/Blackberry OS.

Project Duration

4 weeks

Team Composition

4
member team


2.

Client Name

Pepsi Co.

Project Description

The client was one among
top 3 consumer food products
companies. Approval of procurement requests and sales
requests were delayed .The need for timely delivery aroused.

Timely decisions became essential for customized work
-
flows to








Page |
29

reduce inventory cycle. Executives across the glo
be had to take
critical decisions when off
-
site, during travel and vacations.

Travelling had

the risk of their laptops/mobiles
with corporate
sensitive data
being stolen.

PreludeSys

implemented
an enterprise mobile solution

with pre
-
built business extender
s, technology stack and integrated with
existing enterprise applications.

Blackberry,

iPhone and iPad
devices were chosen for use by managers/executives. Secured
access to content and instant, on
-
time approvals were also
facilitated. The technologies used
in this project were SAP ECC,
SAP SRM, iPhone, iPad, Blackberry devices, iOS/Blackberry
OS.


Project Duration

12 weeks

Team Composition

5 member

team


3.

Client

Name

Universal Music Group

Project Description

One of the world’s leading music records label company
w慮t敤
t漠 扵il搠 愠 r潢畳琠 慮搠 獣慬慢l攠 Cl潵搠 扡獥s Bf o数潲oi湧
p潬畴楯渠for im慤Lim桯湥 摥vi捥c

f潲oit猠畳ur猠t漠p
r潶i摥 慣捥獳s
t漠iq畮敳e a慩ly o数潲os 潶敲e im桯湥 慮搠im慤 摥vi捥c

w桩ch
桡搠t漠扥 獣慬
慢l攠慮搠i湣n畤攠愠
w敢 慰灬i捡瑩cn t漠pr潶i摥 畳ur
灲潶i獩潮i湧
.

mr敬畤敓y猠
im灬敭敮e




敮ter灲楳p m潢ilit礠獯s畴楯渠畳u湧
AqCq 敮t敲eri獥s捬潵搠灬慴f潲m.

q桥 捬潵搠灬慴form 桥l灥搠in
灲潶i摩湧 愠 lig桴h敩g桴 m潢il攠 湡tiv攠 慰灬i捡瑩c渠 t桡t 捡c 扥
摯wnlo
慤敤 慮搠i湳瑡nl敤 t漠t桥 A灰l攠im桯湥 a湤 im慤 m潢ile
摥vi捥c

q桥 慰灬i捡瑩c渠 敮獵牥搠 t桡t t桥 a捣敳獥猠
w敲e

灲潶i摥搠潮ly t漠摥vi捥猠of 敮ter灲楳p 畳urs. q桥 摥vi捥猠桡搠t漠
扥 regi獴er敤 慮d 灲潶i獩潮敤 t桲潵gh t桥 Ap灬攠 敮t敲eri獥
J
灲潶i獩潮i湧 灯rt慬

j潢il攠 w敢 獥svi捥猠 w敲攠 扵ilt 畳u湧 t桥
Az畲支Atp Cl潵搠 infra獴r畣t畲攠 f潲 獣慬慢ility
. q桥 獯suti潮
敮獵牥s

m潢il攠 摥vi捥 畳ur猠 捯cl搠 g敮er慴a
r数潲o
s

from
慮祷桥r攬e慮ytim攠畳u湧 t桥 捬潵搠infr慳tr畣t畲e
. ft pr潶i摥搠

t潯l t漠oefr敳e t桥 摡t愠a渠愠摡il
y 扡獩猠from t桥 d慩ly 摡t愠摵a瀠
灲潶i摥搠批 t桥 捵獴潭er

ey灥ri潮I iq畮敳⁗eb p敲ei捥猬cim慤
C im桯湥 a敶i捥猠
w敲攠t桥 t散e湯logi敳⁵e敤 批 潵r

t敡m.


mr潪散t a畲慴楯n

㠠U敥ks









Page |
30

Team Composition

5

member team




4.

Client

Name

Santec
h

Inc.

Project
Description

The client
, a g
lobal leader in provi
ding web and mobile
healthcare
solutions
,
wanted to foray into the mobile space with
an iPhone application for its end user
s

to track and maintain
their

routine food consumption & physical activity and the
en
ergy spent in
their

activities to remain fit.

The end
users could
either select

from a standard list or create

and add a new item to
the existing list of standard database.
Because of its volume, it
was

difficult to provide
the list
along with the applicat
ion
. The
d
ata
had to be u
pdat
ed with
the activities, on a daily basis,

which the end user
entered in the application
.
End user level of
document viewing experience was an issue
.

PreludeSys delivered a solution workable on the iPhone and the
iPad

for the cl
ient. The application allowed

the end user to enter,
update, track and store all details with respect to
their
food
consumption, physical activities, pre
-
defined goals or also
customize all the said functions
.
The
solution allowed

access to
the standard da
tabase only on demand by the c
lient
, thereby
managing the application size & available memory space
efficiently
. It provides

o
ff
-
line connectivity of the ap
plication, on
the mobile device
,

by being able to sync data from both web and
mobile databases
.
Sinc
e the Software Development Kit was
limited in providing options for viewing documents, charting and
calendar controls, third party frameworks were used to achieve
a rich user experience
. The solution used
Objective C, SQLite,
MS SQL Server 2008, Rest Web S
ervice (WCF), Macintosh OS,
Windows Server 2008, Core Plot, QL Preview

for it to take
shape.

Project Duration

It’s a 1 Year Contract and Automatically extends thereafter year
J

J
y敡r.

m敲楯搠df m敲form慮捥c a散em扥r ㈰〹

J

lng潩湧

q敡m Com灯獩ti潮


mem扥r t敡m










Page |
31

5.

Client

Name

Moxian

Project Description

The client is a
unique multi channel social media platform

which
integrates
digital contents and experiences
, who needed a chat
application to increase the consumers using the client’s social
platform.
The application had to be developed for mobile
devices and desktops following different data models. It had to
be compatible with multiple devices with all latest technological
features like QR code scanner, comments, Geochat feature etc.

PreludeSys develo
ped the Chat Application using MySql
Database, PHP and JavaScript stack. The application was
packaged as four applications for Android tablets, Android
Phones, Apple iPad and Apple iPhone. In addition an internet
based web application was developed using t
he same PHP
-
MySql
-
JavaScript stack that can be used in Laptop and
Desktop. The QR scanner was integrated from the API provided
by the client and all the other requested features were included
in the application mobile device and web compatibilities.
Report
s and graphs were provided to study the usage patterns
of the application. Security of the application was provided with
profile registration with role based rights to access information.
Javascript, Sencha, PHP and My SQL were the technologies
used in dev
eloping the application.

Project Duration

9 weeks

Team Composition

7 member team


Project Management and Software Development Process

PreludeSys will leverage its custom project management life cycle, application analysis and
design
processes

that comply with
DIR Delivery Framework and AWU
Project Management
Methodology. PreludeSys proposes to manage this project based on such a methodology that
has been refined based on its past experiences as shown in the diagram below.

From the project management perspective, the SOW determines the list of deliverables and the
required dates of delivery for those deliverables. This is further developed into Software Project
Plan (SPP) which is an end
-
to
-
end plan for the execution of the
entire project













Page |
32

PROCEDURES

Project Initiation:


Once the SOW is accepted, project initiation starts. As a first step the Project Manager (PM) is
identified. The PM studies the SOW and conducts a project kick
-
off meeting in which the
stakeholders are
informed about the scope and other details of the project. The resources and
infrastructure needs, communication plan, deliverables and delivery schedules, commitments
and expectations from various stakeholders are all discussed at the project kick
-
off mee
ting.

Project Planning:


The PM prepares Software Project Plan (SPP) which covers all aspects
of P
roject
M
anagement
like resource plan, infrastructure plan, communication plan, inspection plan (
r
eviews), test plan
(verification and validation), QA plan, c
onfiguration management plan, risk management plan.










Page |
33


The Software Quality Assurance (SQA) reviews the SPP to verify if it is in agreement with the
contents of SOW in regards to deliverables, delivery schedule and the verification and validation
requirem
ents. These are also included in the Microsoft (MS) Project for tracking purposes.

Project Monitoring and Control:

The weekly status of the project is reviewed by the senior management with reference to the
status of commitments mentioned in the SOW and
Pr
eludeSys

quality goals.



During these weekly status meetings, we review weekly achievements with respect to
completion of deliverables, plans for the following week, status of risks and effectiveness of any
risk mitigation. We also review the status of i
ssue resolution, progress to date compared to
budget, potential scope changes, etc.



Monthly progress reviews are conducted with the project steering committee which includes key
stakeholders. This reviews the progress with respect to the deliverables, s
tatus of stakeholder
commitments, and issues.

At each phase
-
end, metrics are obtained to check the project performance from project








Page |
34

management perspective (Schedule, Effort and Cost) and software engineering perspective
(Review Effectiveness, Test
Effectiveness and Defect Density). Corrective actions are identified
and implemented if needed.

POLICY

The PreludeSys Quality Policy states


PreludeSys delivers high quality deliverables and services by following proven methodologies,
effective testing a
nd a rigorous quality control process.

STANDARDS:

The list of deliverables, delivery schedule, verification and validation requirements are the
references against which the project is monitored for its compliance to the PreludeSys Quality
Policy. To this e
nd the PreludeSys Quality Management System (QMS) has defined guidelines,
checklists, and templates that standardize all project management activities. Risk Management
Guidelines, Configuration Audit Checklists, and Metrics Templates are all examples of
gu
idelines and controls to ensure high standards from PreludeSys.

METHODS:

The Review Methods defined in the QMS include the following:

Technical Reviews:

The purpose of Technical Reviews is to check for the completeness,
correctness, feasibility and compli
ance to standards. These are conducted by Peers, Project
Managers, and Subject Matter Experts etc.

Some examples are Design Review, Code Review, and Test Case Review.

Verification:

Verification is to check if the work product has been prepared according t
o the
design/ specifications. These are normally conducted by developers, test engineers and
Software Quality Assurance (SQA).

Some examples of verification are Unit Testing and System Testing.

Validation:

Validation is done to check if the deliverable me
ets customer requirements. It is
carried out by the customer, a representative of the customer or in the presence of the
customer. Usually, validation is followed by a sign
-
off.









Page |
35

Examples of validation are SRS review, Prototype review and User Acceptance Te
sting (UAT).

All reviews use the standard Review Form Template to record the findings in each review. This
is a tool that captures the source, type, cause, severity, status and corrective action taken for
each finding.

Findings from all review forms are c
onsolidated and analyzed at each phase
-
end using a Defect
Summary tool. The results from this summarization tool are used to identify correction and
improvement needs.

MEASURING DELIVERABLES

Each deliverable goes through a cycle of Preparation, Inspection
and (optionally) Testing. The
phase
-
wise work products / deliverables and the corresponding preparation, inspection and
testing are detailed as follows:

REQUIREMENTS

System Requirements Specification (SRS
)

Preparation: The template is picked up from the Qu
ality Management System. All header
information/ metadata are completed. Requirements stated at a high level in the SOW are
elaborated into a comprehensive set of functional and non
-
functional requirements through one
or more methods of requirement elicita
tion. These requirements are analyzed, organized into
components, prioritized and then documented as a system requirement specifications

document.


Inspection:

The SRS goes through a technical review by the Subject Matter Expert (SME) to
check for correctness, completeness, feasibility and testability etc. It is also used to identify and
resolve any requirement conflicts, etc.

Testing (Validation):

SRS is vali
dated by the customer and signed
-
off

DESIGN

Design Document

Preparation:

The template is taken from the QMS. All header information/ metadata are
completed. The details of solution architecture, database design, UI design, component reuse,
navigation, pseu
do code etc are included.

Inspection:

A Technical Review of the design documents is carried out to ascertain that the
details are necessary and sufficient to implement the system as defined in the SRS.









Page |
36

User Interface (UI) Design

Preparation:

The Design Team prepares the UI design appropriate to the technology chosen
for the solution based on the UI details provided in the design document.


Inspection:

A Technical Review of the UI design documents is carried out by the PM to ensure
that it me
ets the design specifications.

Testing:

The UI Design is validated by the customer

Database Design


Preparation:

The Database (DB) Design is developed using a Design Tool that supports the
chosen database and that provides traceability to meet the Design
Document specifications.

Inspection:

A Technical Review of the DB design documents is carried out by the (Database
Architect (DBA)) to ensure that it meets the design specifications. The review covers the
completeness (vis
-
à
-
vis the classes, transactions
etc), adherence to DB Design Best Practices.
The best practices include right level of normalization, indexing, stored procedures, and scripts
and so on).

Testing:

The DB Design is
validated

by the customer and the development leads.














Page |
37

System Test Cases


Preparation: