Attachment_C__FSA_IGSS_TO__0001_PWS.pdf

Task Order 0001, FSA EAPSS

Attachment C

FSA Technology Office

Performance Work Statement (PWS)

Task Order: 0001

Enterprise Architecture Program Support Services

Background

Federal Student Aid (FSA) has a requirement to further develop/mature its Enterprise Architecture

(EA) Program and associated management processes (e.g., EA governance, communications, toolset management, and integration with other FSA functions). The Contractor shall provide support for all layers of the architecture (i.e., performance, business, data, application, infrastructure and security) for all FSA business areas and program management activities in a prioritized manner as described herein or directed by the Contracting Officer's Representative (COR).

FSA's EA capability will be used to enhance mission performance within the FSA business areas, aligning strategic objectives with business needs and information technology (IT) resources to improve IT investment decision making. FSA's EA capability will also be used to identify process, data and technology redundancies that prove inefficient and/or ineffective. FSA's EA will provide services to address business area needs and the needs of FSA stakeholders while leveraging existing department capabilities and optimizing opportunities for sharing. In developing the EA capability and furthering FSA EA goals, the Contractor shall partner with FSA in:

1. Leveraging best practices from industry and from other Federal agencies.

2. Developing a standard methodology for engaging business areas in the planning of business transformation and architecture development.

3. Engaging and extending the use of governance throughout business transformation to gain active participation resulting in review and acceptance of the segment architecture and other

EA processes.

4. Implementing first rate communications practices and training to ensure that business and technology leaders understand tangible benefits and expected outcomes from EA practices to

FSA and FSA programs.

5. Deploying, populating, updating, relating and providing access to the FSA EA repository

6. Providing resources to support communications and outreach.

Objectives

The following objectives shall be supported by this effort:

1. Effective Enterprise Architecture Program Management

2. Results-based Enterprise Architecture Program Development and Execution

3. Advance the Use of Enterprise Architecture

4. Integrate Enterprise Architecture with Related Disciplines

Performance Requirements

The Contractor shall perform the following activities:

Activity 1: Provide EA Program Management Support

The Contractor shall provide EA program management support services to the FSA Technology Office to develop the EA Program and related functions. This includes completion of an EA Program Assessment of existing EA Processes and artifacts. The Contractor shall develop EA program/project plans, including resource and schedule estimates that incorporate all EA-related activities, performance and administrative management responsibilities. The Contractor shall ensure that all deliverables meet the agreed performance standards in regard to quality, technical accuracy, usefulness and timeliness of the deliverables and work products.

Deliverables

Kickoff Meeting – Qualities include:

1. Held within 5 business days of task order award

2. Depicts and describes integrated project team, task order approach, and technical quality control approach

3. Developed in PowerPoint format.

EA Master Program Plan (PgMP) – Qualities include:

1. Delivered 20 business days from task order award

2. Incorporates all EA-related activities including significant activities based on internal and external drivers.

3. Includes a refreshed program charter, goals and objectives that align with the FSA Technology

Office goals and objectives.

4. Describes how scope, cost, schedule, human resources, communications, risk and quality will be managed.

5. Aligns with and supports the Integrated Master Schedule (IMS).

6. Delivered in Word format.

Integrated Master Schedule (IMS) – Qualities include:

1. Delivered 20 business days from task order award

2. Includes detailed tasks, dependencies, resource and schedule estimates, including estimated activity cost information based upon the FSA EA Master Program Plan.

3. Shall be updated monthly based upon impacts and activities identified in previous months' status reports.

4. All activities are included with all predecessor and successors identified such that a logical critical path can be determined.

5. Compliant with FSA’s WBS and schedule standard.

6. Delivered in MS Project format.

EA Program Maturity Assessment and Report – Qualities include:

1. Assesses the capability of the FSA EA Program to guide IT investments and recommendations to improve performance.

2. Assess the Enterprise Architecture maturity framework landscape. Identify pros and cons of each framework. Make a recommendation which Enterprise Architecture maturity framework https://en.wikipedia.org/wiki/Information_technology

FSA should use.

3. Assist with developing an FSA Enterprise Architecture Maturity Assessment based the FSA approved Enterprise Architecture maturity assessment in Excel format.

4. Summarize the Excel FSA EA Maturity Assessment in PowerPoint format.

Responses to information requests, data calls and audits - Reports in response to requests from the

Department of Education, FSA stakeholders, OIG, GAO, etc.

1. Assist with developing, updating, and validating data calls, information requests, and audits.

2. Delivered in format requested by the individual unique information request, data call, or audit.

Meeting Minutes – Qualities include:

1. Due within two days after each meeting on the EA Program site

2. Developed for all scheduled meetings

3. Record date, time and purpose of the meeting as well as attendees, decisions and actions.

4. Delivered in Word format.

Weekly Status Reports – Qualities include:

1. Due Close of Business (COB) each Thursday.

2. Documents activities and progress completed during the previous week, activities planned for the following week and status of project issues / risks.

3. Delivered in Word format.

Monthly Status Reports – Qualities include:

1. Due by the 5th day of each month. If the 5th falls on a weekend or Federal Holiday, the monthly updated plan is due the next business day.

2. Contains an executive level representation of the IMS

3. Identifies progress over last month, planned progress for next month, and costs over the last month and cumulative by activity and deliverable

4. Identifies foreseeable and existing risks and issues that may prevent the successful implementation and accomplishment of the project plan. Identifies impacts with cost, schedule, and performance for each risk/issue.

5. Identifies recommended corrective to address cost, schedule and performance issues.

6. Contains lessons learned and recommendations to improve process or product.

7. Delivered in PowerPoint format.

Activity 2: Document Enterprise Current State Architecture

The enterprise Current State Architecture (CSA) reflects the current state business capabilities, systems, applications, information, and infrastructure for the entire Student Aid Lifecycle that includes Awareness, Application, Acceptance, Disbursement, Renewal, and Repayment. The FSA view of the architecture is based on the Federal EA Framework (FEAF) v2 found in the Common Approach to Federal EA. The

FSA architecture is viewed as the Loans Segment of the Department of Education. The Loans Segment is reported to OMB through the Department of Education’s enterprise-wide modernization roadmap through a standard set of core/elective artifacts and reporting via standard reference model taxonomies.

FSA must maintain a Business Context diagram to provide a high-level view of the overall business and the full range of stakeholders with which it must interact in order to fulfill its mission. This is a non-technical view where FSA stakeholders are grouped together and used throughout the Business, Systems, and Information Architectures to guide planning and reporting. Business Entities include Customers, Partners, Financial Partners, Federal Partner/Oversight, and Loan Servicing.

The Contractor shall collaborate with FSA stakeholders to perform the following:

1) Assist with Current State Architecture Planning

a) Assist with completing a stakeholder analysis

b) Assist with facilitation of stakeholder workshops

2) Assist with updating and validating the Current State Enterprise Business Context

a) Assist with updating and validating the enterprise business context stakeholders and associated definitions. Definitions should explain the nature of each stakeholder’s interactions with FSA, relative to FSA’s mission.

b) Assist with updating and validating the Current State Enterprise Business Context diagram in

Visio format. Upload approved Visio diagram in PNG format as a Site Asset to the CSA site for display.

c) Convert static enterprise business context stakeholder definitions to SharePoint lists/views.

3) Assist with updating and validating the Current State Business Architecture

a) Assist with updating and validating the Business Architecture business functions and definitions to the third level or lower.

b) Assist with updating and validating the Business Architecture Visio graphics. Upload approved Visio diagram in PNG format as a Site Asset to the CSA site for display.

c) Convert static Business Architecture business function to SharePoint lists/views

4) Assist with developing and validating the Current State Business Entity Context Diagrams

a) Assist with facilitation of workshops to identify all FSA Stakeholders

b) Ensure consistency with the Current State Enterprise Business Context Diagram

c) Assist with developing Business Entity Context Diagrams in Visio format with supporting descriptions to reflect the story of major business entities as they flow through the Aid Life

Cycle and through the Systems Architecture.

i) Develop a view of the current state High Level Systems Overview within the center of the diagram

ii) Visually represents business functions as the Business Entity flows through the Aid Life

Cycle

iii) Highlights applicable systems within view of the current state High Level Systems

Overview that apply to the Business Entity as the Business Entity flows through the Aid

Life Cycle

iv) Includes legend that describes use of images and lines within the Business Entity Context

Diagram

v) Can be printed on landscape 11x17 size paper

d) Assist with developing an accompanying MS Word document that describes the FSA

Business Capabilities that apply to the Business Entity as it flows through the Aid Life Cycle

5) Assist with updating and validating the Current State Systems Architecture

a) Assist with updating and validating the Systems Architecture that identifies the systems that

FSA currently has in place in support of the business functions. Systems Architecture must address all systems and system components across the enterprise. Expected to be delivered at the same or greater level or lower than the current CSA.

b) Assist with updating and validating the Systems Architecture Visio graphics. Upload approved Visio diagram in PNG format as a Site Asset to the CSA site for display.

c) Convert static Systems Architecture tables that associate the System Architecture to FSA systems to SharePoint lists/views. This affects the following seven (7) site pages: System

Architecture; Enterprise Portal; Aid; Internal Management; Planning, Analysis & Decision

Support; Enterprise Infrastructure; and Data.

6) Assist with updating and validating the raw data for the Current State Detailed Data Flows

a) Assist with updating and validating the Detailed Data Flow list of raw data that includes the following attributes: Central System, Related System/Stakeholder, Data File Name, Description, Data File Types, Transfer Method, Transfer Frequency, Input/Output, Related

Business Function, Notes. This list is the foundation which the, Information Architecture

High Level Overview, Data Center Context Diagram, System Drill Down Diagrams, and

Data Flow Diagrams are constructed.

b) Assist with updating and validating SharePoint list views that are displayed on underneath each data flow diagram.

c) Assist with developing and validating SharePoint list views to be displayed underneath new data flow diagrams being developed

7) Assist with updating and validating the Current State Information Architecture

a) Assist with updating and validating the High-level Overview Diagrams depicting system interfaces in support of the Federal Student Aid mission. This should include interfaces between all major and minor FSA systems. This should include systems hosted internally and systems hosted externally in support of FSA’s mission.

b) Assist with developing and validating Data Center Context Diagram(s) that depict all FSA major, minor, and GSS operational systems, their data centers (hosting environments), and system interfaces. This should include physical, virtual, and cloud implementations.

c) Assist with updating and validating ten (10) system drill-down diagrams that depict a view of a system and its interfaces based on the detailed data flows, system components, and stakeholders that interact with them. Existing systems drill downs exist for the following systems: Common Origination and Disbursement (COD); Central Processing System (CPS);

Debt Management Collection System (DMCS); e-Campus Based (eCB); eZ-Audit; Financial

Management System (FMS); National Student Load Data System (NSLDS); Ombudsman

Case Tracking System (OCTS); Postsecondary Education Participants System (PEPS); and

Person Authentication Service (PAS).

d) Remove the Direct Loan Consolidation System (DLCS) drill down diagram and site page.

e) Assist with developing and validating (4) new system drill-down diagrams that that depict a view of a system, interfaces based on the detailed data flows, system components, and stakeholders that interact with them. New system drill down diagrams to develop include:

Access Identify Management Solution (AIMS); Enterprise Data Warehouse and Analytics

(EDWA); Participation Management (PM); and Loan Servicing.

f) Assist with updating and validating existing Data Flow Diagram(s) depicting what data is being collected or distributed, how it is being exchanged (file type, transfer method, and frequency) and what type of data stewardship the associated systems have during each data flow. Develop supporting descriptive language in support of the Data Flow Diagrams.

Existing data flow diagrams exist for: Customer Management; Partner Management; Aid

Application; Aid Origination and Disbursement; and Loans Servicing.

g) Assist with developing and validating new data flow diagrams aligned with the Identity and

Access Management business function depicting what data is being collected or distributed, how it is being exchanged (file type, transfer method, and frequency) and what type of data stewardship the associated systems have during each data flow. Develop supporting descriptive language in support of data flow diagrams.

h) Assist with updating and validating the Interface Architecture High Level Overview, Data

Center Context Diagram, System Drill-Down Diagrams (10 existing and 4 new), and Data

Flow Diagrams Visio graphics. Upload approved Visio diagrams in PNG format as a Site

Asset to the CSA site for display.

8) Assist with updating and validating the Current State Systems Inventory

a) Assist with updating and validating the Loans Segment Systems Inventory. Review systems tracked within the Operational Vulnerability Management Solution (OVMS), Cyber Security

Assessment and Management (CSAM), Virtual Data Center (VDC) configuration management database (CMDB) reports, Next Generation Data Center (NGDC) reports, Integrated Technical Architecture current state reports and other materials as input to the validated system inventory.

b) Add additional attributes to the System Inventory list to capture all data elements required in the Office of Management and Budget’s quarterly IT Asset Inventory data call.

c) Assist with developing and validating additional System Inventory views

i) Systems with ATOs – Default View

ii) IT Asset Inventory view

iii) Systems – Systems Components view

iv) Security View that sorts systems by Major Systems, Non-Major Systems, and GSS

Systems

9) Assist with developing, maintaining, enhancing, and validating the Current State SharePoint Site.

a) Ensure tiles are properly linked to existing or new site pages.

b) Assist with developing, maintaining, enhancing, and validating site pages and lists based on the Business Context, Business Architecture, Business Entity, Systems Architecture, Information Architecture, Systems Inventory, and Detailed Data Flow components.

Deliverables:

1) Current State Enterprise Business Context

2) Current State Business Architecture

3) Current State Systems Architecture

4) Current State Information Architecture

5) Customer Business Entity Diagram

6) Partner Business Entity Diagram

7) Financial Partner Business Entity Diagram

8) Federal Partner/Oversight Business Entity Diagram

9) Current State Loan Servicing Business Entity Diagram

10) Current State System Inventory

11) Current State Detailed Data Flows

12) Current State Architecture SharePoint site

Activity 3: Document the FEA Reference Models

The FEAF continues to use standard reference model taxonomies for each sub architecture domain to support reporting requirements. They contain information about what is in an architecture to support consistent reporting as well as supporting planning, decision-making, and analysis activities.

The Contractor shall assist with developing, maintaining, enhancing, and validating the following FEA

Reference Models.

1) Strategy/Performance Reference Model (PRM)

a) Developed in MS Excel format

2) Business/Business Reference Model (BRM)

a) Developed in MS Excel format

3) Data/Data Reference Model (DRM)

a) Developed in MS Excel format

4) Application/Application Reference Model (ARM)

a) Developed in MS Excel format

5) Infrastructure/Infrastructure Reference Model (IRM)

a) Developed in MS Excel format

1) Loans Segment PRM

2) Loans Segment BRM

3) Loans Segment DRM

4) Loans Segment ARM

5) Loans Segment IRM

Activity 4: Document Current Business Architecture

FSA business functions are essential to the performance and support of FSA's mission of providing Title

IV Federal aid to postsecondary students. The business functions serve as a reference starting point to put FSA’s modernization, operations and integration initiatives in context, and ultimately support investment, planning and other decisions surrounding progress required to achieve the desired target state.

The business architecture focuses on what FSA does, which tends to remain more stable over time, versus the more dynamic nature of the applications used to perform the functions which are reflected in the systems architecture. The business architecture will likely to remain fairly consistent over the years, subject to legislative, market and other factors.

FSA’s business architecture is divided into five logical groupings of related functions:

1. Customer Engagement and Management

2. Partner Engagement and Management

3. Oversight

4. Shared Mission Services

5. Enabling / Supporting

The relative consistency over time of the business functions described in the CSA provides a solid foundation and shared understanding on which enterprise investments, projects and other key decisions are based. Key FSA-wide decisions are traceable back to FSA's business architecture, which is why such mapping is required by the investment request and review processes. The Current State business architecture is deliberately focused on defining an enterprise-wide, stable, and single view of the present state of FSA's business functions. The business architecture describes the FSA functions utilized by internal and external FSA stakeholders, such as customers, partners, and other organizations involved in distributing and managing Federal grants and loans.

The Contractor shall assist with developing, maintaining, and enhancing the Loans Segment Business

Architecture for the following six FSA Investments:

1) Application Eligibility Determination System (AEDS) – AEDS supports a large group of front end business functions associated with applying for federal student aid. The primary business function is application processing and eligibility determination.

2) Enterprise Data Warehouse and Analytics (EDWA) – EDWA provides enterprise data and knowledge management for FSA Stakeholders.

3) Integrated Partner Management (IPM) – IPM will provide, in one solution, improved eligibility, enrollment, and oversight processes used to manage partner entities as they administer

Title IV Financial Aid for Students.

4) Common Origination and Disbursement (COD) – COD is a common processing platform for recipients at higher education institutions participating in Title IV aid programs to originate and disburse funds, including Pell Grants & Direct Loans.

5) Enterprise Identity Management Service (EIMS) – EIMS will provide a centralized and consolidated identity management framework for FSA systems.

6) Participation Management (PM) – PM is FSA's central system for managing partner organization enrollment in FSA data exchange services. Virtually all schools, third party servicers, GAs, federal loan servicers, FSA External Partners, State Agencies, and other organizations use PM.

Listed below are the requirements for each Business Architecture deliverable:

1) Assist with developing, maintaining, and enhancing the Loans Segment Business Architecture

2) Assist with completing a stakeholder analysis

3) Assist with facilitation of stakeholder workshops

4) Assist with mapping the FSA Investment and associated systems alignment to the FSA Business

Architecture in Visio, Excel and PowerPoint formats.

5) Assist with developing and validating a high level business concept diagram that represents an operational view in Visio format in Visio and PowerPoint formats.

6) Assist with developing and validating Business Process Modeling Notation (BPMN) business process diagrams that describe business processes in Visio format.

7) The Contractor shall publish the business concept and process diagrams to the FSA CSA

SharePoint Site for viewing and use by stakeholders.

8) Assist with developing and validating an investment context diagram that reflects how systems within the investment operate in relation to other FSA systems in Visio and PowerPoint formats.

Deliverables:

1) Application Eligibility Determination System (AEDS) Business Architecture

2) Enterprise Identity Management Service (EIMS) Business Architecture

3) Participation Management (PM) Business Architecture

4) Ombudsman Case Tracking System (OCTS) Business Architecture

5) Enterprise Data Warehouse and Analytics (EDWA) Business Architecture

6) Integrated Partner Management (IPM) Business Architecture

Activity 5: Document Target State Vision

FSA must update the Target State Vision (TSV) to guide investment and technology prioritization and decision making. The TSV will represent Federal Student Aid’s (FSA) shared understanding regarding where the entire enterprise is going over the next 3-5 years, from both a business and technology point of view. The TSV must support the business needs that will allow FSA to meet strategic goals and objectives in the strategic plan. The TSV will also be designed to be flexible to adapt to changing requirements and business needs. The business needs will drive the technology.

The TSV must also consider modernization of legacy systems. Two of FSA’s core systems — the

National Student Loan Data System (NSLDS) and the Central Processing System (CPS) — are built with mainframe technology and COBOL. FSA systems leveraging COBOL operate on a fully supported, modernized infrastructure that has been hardened and tested. FSA intends to make re-engineering of the

CPS system a requirement during the upcoming contract action, referred to as Digital Delivery and

Application Services (DDAS). FSA has conducted extensive analysis about the requirements to modernize the NSLDS system. A replacement solution was considered that would utilize specialized data load and extraction technologies, migrating COBOL to Java, and decommissioning NSLDS. FSA’s leadership determined the total costs were prohibitive and opted for a much smaller NSLDS re-engineering effort to implement the most critical services needed to support business operations. To that end, FSA embarked on developing an Enterprise Data Warehouse and Analytics (EDWA) for research and analytical purposes which was previously part of the functionality of NSLDS.

The Contractor shall document the FSA Target State Vision (TSV) that is the representation of the future architecture of the entire enterprise aligned with the FSA strategic plan. The Target State Vision represents Federal Student Aid’s (FSA) shared understanding regarding where the entire enterprise is going over the next 3-5 years. The TSV shall consider the impact of all known regulatory, business and technology drivers.

The Contractor shall assist with developing, maintaining, enhancing, and validating the target state vision.

The Contractor shall collaborate with FSA stakeholders to perform the following:

1) Assist with Target State Vision Planning

a) Assist with completing a stakeholder analysis in Excel format.

b) Assist with facilitation of stakeholder workshops

2) Assist with developing, maintaining, enhancing, and validating an Executive Summary.

a) Develop Executive Summary in Word format.

b) Publish approved Executive Summary on SharePoint site page(s).

3) Assist with developing, maintaining, enhancing, and validating a Business Direction

a) Relate the Target State Vision to the Five Year Strategic

b) Summarize Opportunities for Improvement based on stakeholder interviews. Represent

Opportunities for Improvement in Visio format.

c) Develop Business Direction in Word format.

d) Publish approved Business Direction on SharePoint site page(s).

4) Review the Activity 3 Current State Enterprise Business Context. Assist with maintaining, enhancing, enhancing, and validating the stakeholders in the next 3-5 years.

a) Assist with updating and validating the enterprise business context stakeholders and associated definitions. Definitions should explain the nature of each stakeholder’s interactions with FSA, relative to FSA’s mission.

b) Assist with updating and validating the Current State Enterprise Business Context diagram in

Visio format. Upload approved Visio diagram in PNG format as a Site Asset to the CSA site for display.

c) Convert static enterprise business context stakeholder definitions to SharePoint lists/views.

5) Review the Activity 3 Current State Business Architecture. Assist with maintaining, enhancing, and validating business functions that are anticipated to be created, modified, or suspended in the next 3-5 years.

a) Assist with updating and validating the Business Architecture business functions and definitions to the third level or lower.

b) Assist with updating and validating the Business Architecture Visio graphics. Upload approved Visio diagram in PNG format as a Site Asset to the CSA site for display.

c) Convert static Business Architecture business function to SharePoint lists/views

6) Review the Activity 3 Current State Systems Architecture. Assist with maintaining, enhancing, and validating systems or system component descriptions that are anticipated to be developed, updated, or decommissioned in the next 3-5 years.

a) Assist with updating and validating the Systems Architecture that identifies the systems that

FSA currently has in place in support of the business functions. Systems Architecture must address all systems and system components across the enterprise. Expected to be delivered at the same or greater level or lower than the FY13 Target State Vision.

b) Assist with updating and validating the Systems Architecture Visio graphics. Upload approved Visio diagram in PNG format as a Site Asset to the TSV site for display.

c) Convert static Systems Architecture tables that associate the System Architecture to FSA systems to SharePoint lists/views.

7) Assist with developing and validating a System Forecast.

a) Review the Activity 3 Current State System Inventory.

b) Identify Development, Modernization, and Enhancement (DME) efforts in the next 3-5 years based on reviews of FSA Capital Planning and Investment Control (CPIC) information, stakeholder interviews, and other materials.

i) Identify new systems to be developed

ii) Identify development systems that will be deployed to production

iii) Identify production systems that will be decommissioned

iv) Identify system enhancements to be deployed in the next

c) Develop system forecast graphics in Visio format.

d) Develop a system forecast in MS Word

e) Publish approved system forecast on SharePoint site page(s).

8) Assist with updating and validating the Target State Information Architecture

a) Review the Activity 3 Current State High Level Overview diagram. Assist with developing target state high-level overview diagrams depicting new or decommissioned systems and system interfaces in support of the Federal Student Aid mission. This should include interfaces between all major and minor FSA systems. This should include systems hosted internally and systems hosted externally in support of FSA’s mission.

b) Review the Activity 3 Data Center Context Diagram(s). Assist with developing and validating target state data center context diagram(s) depicting new or decommissioned systems and system interfaces in support of the Federal Student Aid mission. This should include interfaces between all major and minor FSA systems. This should include systems hosted internally and systems hosted externally in support of FSA’s mission.

9) Assist with developing, maintaining, enhancing, and validating Target State Vision Governance

a) Assist with developing and validating BPMN business process diagrams in Visio format that integrate the Target State Vision with the FSA Strategic Planning and Investment

Management processes.

b) Describe the governance processes in MS Word format.

c) Publish approved system forecast on SharePoint site page(s).

10) Assist with developing, maintaining, enhancing, and validating the Target State Vision

Communication Plan.

a) Review the FY11 and FY13 Target State Vision Communication plans

b) Assist with enhancing and validating the Target State Vision Communication Plan based on the current FSA environment.

11) Develop and validate a Target State Vision Executive Briefing in PowerPoint format that summarizes the approved deliverable.

12) Assist with developing, maintaining, enhancing, and validating the Target State SharePoint Site.

a) Ensure tiles are properly linked to existing or new site pages.

b) Assist with developing, maintaining, enhancing, and validating site pages and lists based on the Business Context, Business Architecture, Business Entity, Systems Architecture, Information Architecture, Systems Inventory, and Detailed Data Flow components.

1. Target State Business Direction

2. Target State Enterprise Business Context

3. Target State Business Architecture

4. Target State Systems Architecture

5. Target State Information Architecture

6. Target State System Forecast

7. Target State Governance

8. Target State Communication Plan

9. Target State Executive Briefing

10. Target State SharePoint site

Key Personnel

The following positions are considered key personnel for this effort:

SME Level I

System Architect Level I

Business Analyst Level II