Job Description :
Role: Senior Solutions Architect Location: (Plymouth Meeting PA/ West point PA) Duration: 6 Months Contract likely extension. Remote during Covid-19, onsite 2-3 days/week post Covid-19 Plymouth Meeting, PA/WestPoint, PA Pharma client in PA has split, they are cloning most of everything in their Sales & Marketing section, though some will shift to a different solution Our role is to create a master program plan and end to end solution architecture (high level - timing and dependencies are key), and have the solution architecture inform the program plan The architect must be able to see what is not explicitly indicated. Example: Project 1 integrates to project 2 using informatica. There is a "seen" integration and dependency between the two. Unseen: because this is a new company, there is a dependency on the informatica environment actually being available (has to be installed in the New Company Managers for project 1 and 2 are not thinking about that, they assume it is there. * Client will provide services for some capabilities. The architect must be able to distinguish and categorize applications. (are they Part of the New Company, part of the end Client, third party hosted) * There are timing dependencies for dev, test and prod environments. Though the manager does not need three diagrams, understanding and identifying the dependency that app 1 testing can't start until app 2 is also in test is primarily the responsibility of our PM, but some of this stuff is unseen, and the architect needs to "see" and raise those. Example: Are both environments ready on time. This is one level deeper than "when does each plan to start testing", and may not be apparent to the PM * All applications and connections need to be tagged, and the manager needs the architect to know what tags, categories and values should be defined. This is used in our visualization tool (see next section Applications and connections can have multiple tags. Example * Application Owner: Pharma End Client/New Company * Connection Technology: ETL/TIBCO * Data Entity (applies to both connections and apps): Customer/Product * Host: On Prem/Cloud/Third-Party * Whatever. this is a short example list, but the manager needs someone to think about how this will be shown in the visualization tool and be able to create the tag categories and values, not be fed a set list. The key is "the ability to define" and "know why it should be defined" * Architect needs to decipher various project diagrams and combine them correctly Example: Diagram for project 1 shows a link to project X, diagram for project 2 shows a link to project X. Master diagram should show 1->x->2. (there will be multiple source diagrams Understanding direction of integrations and (high level) data entities in the connections is important KEY: The architect will NOT be creating a master Visio. The master diagram will be in our visualization tool, and the architect needs to understand how to get that in there. What is important is to understand the basic concept below, and know HOW to structure the information for success Visualization Tool, SharpCloud Basically allows drill down to show views that are more focused (click on one app in the master architecture and you get a diagram with only that app and its dependencies The tool is SharpCloud, BUT, the architect does not need to know the tool or how to use it, we have folks for that. The architect needs to understand HOW SharpCloud is going to be used, and how to get the information into a spreadsheet correctly, for import into SharpCloud. The architect should also think outside the box to imagine new relevant architecture views and help define those to our sharp cloud guru Example: How about a view that shows me everything using ETL? Hmmm, let me tag everything with ETL and tell the sharp cloud Guru this is needed, roughly how it should look, and why * Importing Data to SharpCloud: * Two spreadsheets * 1 - List of items (Item ID and any number of attributes on the sheet (columns * 2 - Connections between items (Source, Destination, Direction, Tags) * Tricky Part, we want to show not only the architecture dependencies, but also the project task dependencies. This means that each "task" from a project plan is an "item" in sharp cloud, and each application is an "item" in sharp cloud. Tasks are interdependent to each other, but a task also "refers" to 1 or more applications. This "reference" or "dependency" is another connection that needs to be created for sheet 2 above. Any "item" can be connected to any "item" for any reason. Could be a time dependency, could be an integration, could be a platform dependency, etc. Many to many * Though this sounds like a spreadsheet exercise, the value of a solution architect is to be able to understand the co-dependencies of applications, infrastructure, environments, platforms (such as informatica as the integration mechanism), tasks and timelines to achieve success. Basically be able to identify risks to the programs if ANY ONE of these items are going to be out of sync * Given the above, the architect needs to define a system to uniquely identify items across these two spreadsheets and in sync with MS project. The manager has a unique identifier in place which may need to be enhanced, but they key is to understand how it is used. If spreadsheet 1 used Project Name as the UID, and spreadsheet 2 connects by project numbers, that won't work. Understanding how the information needs to be structured in the two spreadsheets to get them in correctly. Ability to create excel formulas to transform exported data from MS Project or create new attributes for items is a plus, but not required. Aptitude: * Understand data loading. Example 1: An env Data load has to be done 10 days in advance in order for a system to be configured. The architect isn't doing the data load, but needs to know and raise up that there is a 10 day buffer needed here (this may or may not be seen by the PM, or the PM does not know that this needs to be asked Example 2: The DB team inherently knows that after the data load there is a 3 day indexing time needed (making this up They know it, but never communicate it. That type of information needs to be discovered and raised so that the project plan reflects it, in order to ensure success. A solution architect should be able to Client this where a PM may not be tech enough to Client this. * If there are roadblocks or hurdles due to timing of the above, the architect should think outside the box for ways to correct, and make recommendations. Someone that is very good at seeing how all of the pieces of the puzzle fit together, and also in finding the pieces of the puzzle that fell under the table. Note: Momento USA is an Equal Opportunity/Affirmative Action Employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, pregnancy, sexual orientation, gender identity, national origin, age, protected veteran status, or disability status. Thanks, Adam Walsh. Momento USA | Exceeding Customer Expectations 440 Benigno Blvd, Unit#A 2nd Floor. Bellmawr, NJ 08031 Interstate Business Park Direct Number; Tel Ext 1003; Fax Email: Web: Note: Momento USA is an Equal Opportunity/Affirmative Action Employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, pregnancy, sexual orientation, gender identity, national origin, age, protected veteran status, or disability status.