*Hi Friends,*

*Need DSI EDW Architecture Foundation Effort*

*Please respond to [email protected]*



Project Name: DSI EDW Architecture Foundation Effort

Project Location: Parsippany, NJ

Position Needed:

*Information Delivery Architect/lead developer.  ***

*o**        **Profile: Seeking Information Delivery Architect/Lead Developer
to support an EDW Architecture Foundation effort.  Position requires strong
query skills and intimate knowledge of the Business Objects tool, including
universe design, server suite of components, Webi, deski, and portal
access.  Person must be hands on and be comfortable configuring the various
server components, setting up user access and controls, developing universes
as well as shared design components (e.g., interfaces to LDAP server,
reporting templates).  This is not a “report developer” role, but rather is
an architect role that lays all components in place to enable report
development and distribution, as well as ad hoc access.***

*Project Description:*

*1**         **EDW Architecture Foundation Project *

         running concurrently with Reverse Engineering Project:.  Overall
Task: Create a proof of concept for the EDW architecture that

-          Eliminates or mitigates architectural risks for the EDW effort.

-          Provides a strong architecture foundation for accelerated
application release development.

Given Architecture Components:

1.       Modeling Tool: Erwin: ETL: Informatica 8.x, running on Windows
Server

2.       Information Delivery: Business Objects running on Windows Server

3.       DW Appliance (combination of DBMS/OS/hardware/storage)

a.       POC Option 1 for evaluation: Teradata

b.      POC Option 2 for evaluation: Netezza NPS

Tasks:

1.       POC Technology setup:  Setup an informatica and business objects
development environment, Erwin access to databases, hookup for appliance
boxes, access to existing development databases (CDMA repository),
CDMA/repository.

2.       POC data set/rule definition:  Define a set of data and business
rules to exercise the POC from sourcing through execution.  Focus is on
simple but effective data set definition that exercises all needs of the
POC,

3.       POC Tool Alternative Evaluation Strategy and execution: Define a
strategy for Vendors to come in and execute a POC.  Scope includes:

a.       Using competing DW appliances to support ETL processing and
population of the IDS and EDW, both for an initial and update run.

b.      Using competing DW appliainces to support BO query processing

4.       ABC POC.  Architecture POC will develop shared ETL components and
use these components to demonstrate the use of an ABC layer

5.       CM POC.  Architecture POC will develop shared ETL, Data and
Information Delivery components, and use these components to demonstrate
moving an application from the sandbox development environment to the
development integration environment

6.       Design Templating POC.  Architecture POC will demonstrate the use
of design templates, with example documentation.

7.       Workflow POC.  Architecture POC will develop a workflow framework
and demonstrate the workflow of ETL and Information delivery components.  At
a minimum, this will demonstrate workflow between unit development, unit
testing, integration testing.

8.       Extract and Collection Layer POC.  Architecture POC will
demonstrate the methods of extracting and collecting data at DSI.  At a
minimum: the POC will demonstrate:

a.       accessing files FTPed to an FTP server

b.      Accessing data from SAP

c.       Accessing user-defined files from a directory

d.      Accessing Oracle and MS SQL Server tables from a source

e.       Landing files in the collection area, and then moving them to a
collection table

f.        Naming conventions for collection files and tables that allow
multiple collection cycles to reside in the collection area.

g.      Example DQ process and the reporting of DQ issue in the Collection
Area

                                                   i.      One process to
validate file integrity and report exceptions

                                                 ii.      One process to
validate minimum field information requirements, and to report exceptions

                                                iii.      One process to
validate record count in an acceptable range and report exceptions

h.       Example Archiving of Collection data after a run

9.       Operational POC including:

a.       Example backout of a run, and rerun

b.      Example recovery of collection data from archive and rerun

c.       Example initialization of environment

10.   Informatica – Data Interface POC.  Set up and use of the one or more
interface methods between Informatica and the DW Appliance (for both
Teradata and Neteeza):

a.       Load utility

b.      Other

11.   Round Trip Codes Management POC.  Design shared components to access
master codes in CDMA, and update code tables within the EDW, capture codes
in source data that are not validated in CDMA, upload these invalid Codes to
CDMA, validate the codes, and then download the code updates the IDS
environment.

12.   Master Data Management CDI POC.  Design shared components to interact
with the customer master data integration tool.


-- 
Thanks & Regards
James
Astoline Inc
Phone : 732-658-9252
E-mail : [email protected]
www.astoline.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Mainframe1952" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/mainframe1952?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to