Careers – SwiftAnt

Request Case Study

Administrative Assistant
(U.S. Location only)

Job Description

He/she is responsible for day to day management of routine tasks, managing time sheets and non-supervisory duties of the business.
Proactively ensure that Executive and Managerial personnel of the business are freed from the burden of managing routine tasks of the business.

Salary Levels – per the prevailing labor laws & competitive market conditions.

Reporting Hierarchy
Administrative Assistant reports to Chief Enterprise Architect.

Educational qualifications
Preferably Undergraduate degree, but not a must.

Skills

Microsoft Word and Excel.
General Communications.

Business Systems Analyst

Job Description
Solves organizational information problems and requirements by analyzing requirements; designing computer programs; recommending system controls and protocols. Business Systems analysts generally need to have a 2-4 years’ hands on programming experience.

Salary Levels – per the prevailing labor laws & competitive market conditions.

Experience – Minimum of 2 years in I.T. programming (any programming language); preferably about 2-4 years of industry experience, which can overlap with programming experience.

Reporting Hierarchy
Business Systems Analysts reports to and receive general directions from Chief Enterprise Architect.

Educational qualifications
University Degree, 4 years Engineering Degree (10+2+4) with Computer Science and Mathematics is preferable. Candidates with Masters in Computer Science also suitable for this position.

Skills

Software Design
Software Documentation
Software Development Process
Software Requirements
Analyzing Information
Teamwork
Software Maintenance
Written Communication
Promoting process improvement

Project Manager

Job Description / Job Duties

The Project Manager oversees the planning, implementation, and tracking of a specific short-term project which has a beginning, an end and specified deliverables.
His or her responsibilities include, planning, staffing, implementing and controlling the progress of the project throughout the lifecycle of the project.
Project Manager must be able to follow the guidelines of the Enterprise Architecture.

Salary Levels – per the prevailing labor laws & competitive market conditions.

Experience – Minimum of 3 years in I.T. Project Management; preferably about 7-10 years of industry experience, but not a must.

Reporting Hierarchy
Project Manager reports to and receive general directions from Chief Enterprise Architect.

Educational qualifications

University Degree, 4 years Engineering Degree (10+2+4) with Computer Science and Mathematics is preferable. Candidates with Masters in Computer Science also suitable for this position.
Project Management Professional (PMP) from Project Management Institute (PMI) will be a huge plus.

Skills

Business – I.T. Requirements Management
Project Lifecycle Management
Communications Management
Risk Forecasting, Quantitative and Qualitative analysis, Risk Rating and mitigation plans
Financial Management
Proven track record in:
- Leading: Positively influence others to achieve results that are in the best interest of the organization.
- Planning: Determine strategies to move the organization forward, set goals, create and implement actions plans, and evaluate the process and results.
- Decision making: Assess situations to determine the importance, urgency and risks, and make clear decisions which are timely and in the best interests of the organization.
- Organizing: Set priorities, develop a work schedule, monitor progress towards goals, and track details/data/information/activities.
- Solving Problems: Assess problem situations to identify causes, gather and process relevant information, generate possible solutions, and make recommendations and/or resolve the problem.

EDI Practice Head

Job Description / Job Duties
As part of Logistics Solution delivery, EDI (Electronic Data Interchange) is a very important building block. EDI Practice Head must understand the Logistics business and how the data is exchanged between trading partners in Client specific business scenarios, analyze the As-Is processes, recommend best practices in the context of Enterprise Architecture. EDI Practice Head must also be leading configuration driven EDI implementations.

Salary Levels – per the prevailing labor laws & competitive market conditions. Ramakrishnan Sankaran is being offered $70,000 per annum at this time.

Experience – Total I.T. experience of 5+ years with a minimum of 3 years in EDI Technologies.

Reporting Hierarchy
EDI Practice Head reports to and works very closely with C.T.O to design the Technical solutions and practices.

Educational qualifications
4 years Engineering Degree (10+2+4) with Computer Science and Mathematics as the primary specializations is a must. Alternatively, candidates with Masters in Computer Science are also eligible.

Technical skills

EDI Integration and mapping skills, knowledge of Transportation Domain will enable better adaptability to the client processes.
Strong Experience on messaging and mapping tools like IBM Sterling B2B v5.2, Gentran Integration Suite (GIS) v4.2, communication protocols like AS2, SFTP, FTP, MFT (Large File Mailbox Services).
Experience on EDI standards like ANSI X12, EDIFACT& XML is a must.
Expertise in RIEDA implementation framework for Sterling B2B is a must.
Good understanding of SQL, primarily SQL Server 2008R2 and 2012 versions.
Advanced knowledge & working experience of Business Process Modelling Language (BPML) on creation of BP’s, integrate with Web services, Enterprise applications like SAP, JD Edwards and Travel & Transportation systems.
Liaison with client business personnel (Transportation domain) to understand the business needs and accordingly customize / implement the EDI technology platform.
Resource should have understanding of messaging and message flows, landscaping and architecture.
Support both EDI and Non EDI Integration.

Detailed Model Capture

Activity

Purpose

Deliverables

Responsible

Focus on gaps in As-Is and To-Be

Focus on gaps between what is in the legacy system and what is desired (include every aspect, functional, performance, scalability etc)

To-Be business scenarios and gaps

SwiftAnt Project Manager

Keep it Simple

Plan an adequate, but simple solution (in line with Client vision of on premise) to a potentially more general, but complex solution.

High Level To-Be Solution design

SwiftAnt Project Manager

UML Models for To-Be

Deliver the documentation in use cases, and UML models

Business rules

Use cases

Class diagrams

Data Class models

SwiftAnt Project Manager

UI / UX Prototypes

Develop a prototype of the new concept and evaluate it with respect to the new, emerging requirements & making sure that current requirements are met.

UX Prototype preferably in Axure (or any preferred tool of Client)

SwiftAnt Project Manager

Interface specifications

External / Internal system interfaces by applying Industry best practices to deliver integrations via Integration Platforms (as well as any other middleware preferred by Client)

Interface specifications

SwiftAnt Project Manager

Knowledge Transfer & Sign Offs

Conduct workshops with all stakeholders and deliver the documentation and also get the required sign-offs

Final signed documentation

SwiftAnt Project Manager

Document & Discuss

Activity

Purpose

Deliverables

Responsible

Record Business Rules

Document the information as per Client documentation standards and also by applying UML and PMI best practices.

Initial versions of

Business rules

Use cases

Class diagrams

Data Class models

SwiftAnt Project Manager

Record potential Risks (aligned with most valuable requirements first)

Document the potential risks, with probability & impact and Risk Mitigation strategies.

Risk register with potential impact (possibly in Client SharePoint)

SwiftAnt Project Manager

Meet and Present

Showcase to the stakeholders the smallest results that can demonstrate real value.

Meeting minutes

SwiftAnt Project Manager

Refine the Documentation

SwiftAnt Project Manager

Knowledge Transfer & Sign Offs

Final versions of

Business rules

Use cases

Class diagrams

Data Class models

SwiftAnt Project Manager

Analyze

Activity

Purpose

Deliverables

Responsible

Read the Code & Documentation

Understand the code and available documentation

Input deliverable: as-is code in Client servers and documentation

Client Project Manager

Chat with Maintainers

Professionally working with maintainers like “Brothers in arms”, understand the system history and the people-related issues that influenced history.

SwiftAnt Project Manager

Involve the (Business / Operations) Users

Understand the business users perspective of the system

SwiftAnt Project Manager

Re-read the Code

Based on inputs from Maintainers and Users, re-read the code and focus on most valuable aspects

SwiftAnt Project Manager

Step through the execution for most valuable aspects

Gain total command on details for most valuable aspects

SwiftAnt Project Manager

UML and Data Model for As-Is

Deliver the documentation in use cases, and UML models

Business rules

Use cases

Class diagrams

Data models

SwiftAnt Project Manager

Set the direction

Activity	Purpose	Deliverables	Responsible
Agree on Maxims	Establish the key priorities for the project and identify guiding principles that will help the team to stay on track.	Mini Charter for every functional module	SwiftAnt and Client Project Managers
Identify the Personas	Understand who is using the system and why is it important for them and what aspects are most important for them.	User personas (internal and external)	SwiftAnt and Client Project Managers
Appoint a Navigator (Business & Technical)	Appoint a specific person whose responsibility in role of navigator is to ensure that the business architectural vision is maintained throughout the project duration (minimal changes are acceptable).		Client Project Manager
Speak to the Roundtable	Hold brief, regular round table meetings.		SwiftAnt Project Manager
Identify the most valuable first	Start working on the aspects which are most valuable to the project first.		SwiftAnt and Client Project Managers
Identify what can be left as-is	Which aspects of the system should be left in their current state (such that time and resources aren’t wasted where not necessary)		SwiftAnt and Client Project Managers