Attachment 6 - Enterprise Architecture Sample Task Order.doc

Defense Information Systems Agency

Chief Information Officer

DISA Information Technology Enterprise Support Services (DESS)

ENTERPRISE ARCHITECTURE SUPPORT

HC1047-12-D-XXXX

Task Order 0006 (Version 1.0)

31 January 2012 Table of Contents

1Chief Information Officer

1DISA Information Technology Enterprise Support Services (DESS)

11.

Task Order Contracting Officer Representatives (TO CORs)

11.1 Primary TO COR.

11.2 Alternate TO COR

12.

Task Order Title:

23.

Background

34.

Enterprise Architecture Objectives

45.

Scope

55.1 IT Service Management and Support.

55.2 Information and Mission Assurance Support.

55.3 Enterprise Architecture Support:

216.

Place of Performance

216.1 Primary Place of Performance

216.2 Alternate Place of Performance

227.

Travel Requirements

228.

Period of Performance

229.

Delivery Schedule

2410.

Service Level Agreements and Performance Metrics

2411.

Security Requirements

2411.1 The VAR/VAL

2712.

Government-Furnished Equipment (GFE)/Government-Furnished Information (GFI)

2713.

Other Pertinent Information or Special Considerations

2713.1 Identification of Potential Conflicts of Interest (COI).

2713.2 Identification of Non-Disclosure Requirements.

2713.3 Inspection and Acceptance Criteria.

2814.

Section 508 Accessibility Standards

2915.

DoD Enterprise Architecture Directives, Policies and Instructions

1. Task Order Contracting Officer Representatives (TO CORs)

Primary TO COR

Department of Defense Activity

Address Code (DODAAC):

HC1047

DISA HQ Complex (Command Bldg)

6910 Cooper Ave

Fort Meade, MD 20755

Alternate TO COR

Department of Defense Activity

Address Code (DODAAC):

HC1047

DISA HQ Complex (Command Bldg)

6910 Cooper Ave

Fort Meade, MD 20755

2. Task Order Title:

Defense Information Systems Agency’s (DISA’s) Information Technology (IT) Enterprise Architecture (EA) Support Services

3. Background The Defense Information Systems Agency is a Combat Support Agency responsible for connecting US Forces and their coalition partners to the DoD’s Global Information Technology (IT) Enterprise. DISA provides IT networks, computing infrastructure, and enterprise services in direct support of US Warfighters to facilitate the seamless exchange of information on a global scale.

The mission of DISA’s Chief Information Officer (CIO) is to, “Lead and govern the delivery and operation of secure world-wide enterprise IT services enabling the efficient and effective execution of DISA’s global combat support missions.” In order to accomplish this mission, the DISA CIO must:

· Provide an efficient and effective IT infrastructure and services to support the Agency’s warfighting mission.

· Achieve a Mission Assurance posture that ensures the security and continuity of the Agency’s internal IT Enterprise’s infrastructure and services against an ever evolving spectrum of threats.

· Maintain compliance with all DOD information governance policies and legislation.

· Govern a common architecture and service delivery framework to drive efficiencies in business system investments and portfolio and knowledge management capabilities.

The Office of the Chief Information Officer (OCIO) working with the Director for Strategic Planning and Information (SPI) is responsible for promoting and facilitating the use of architecture products to support IT investment planning; IT requirements definition, planning, and programming; technology standardization; and other decision processes related to the management of IT. The CIO keeps the DISA Chief of Staff (COS) apprised of all new and existing Congressional and statutory requirements that may affect the Agency Enterprise Architecture. The DISA COS serves as the Agency implementation authority for DISA EA governance framework. The Chief, Enterprise Architecture Branch (CI4), is assigned under the operational control of the COS to provide this EA support.

The office of the technical director, CI4, leads all DISA CIO Enterprise Architecture (EA) initiatives and supports the design and development of the agency’s strategic enterprise architecture in accordance with DoD EA directives (See Appendix A – DoD EA Directives). CIO CI4 EA establishes and supports agency-wide architectural product compliance in accordance with DoD legislative and statutory compliance. Maintains the enterprise architecture for the DISA CIO, including associated governance and policy for service and delivery of internal DISA systems and services. The effects of this enterprise architecture are to promote interoperability, secure information sharing, collaboration, and economies of scale. The EA function of this division provides support to the CIO’s role as one of the agency’s Senior Decision Authority (SDA) and Designated Approval Authority (DAA) which addresses acquisition oversight, portfolio management practices for all internal DISA systems, and information assurance (IA) for all systems that link to DISA’s enterprise network.

CI4 investigates both new and emerging technologies; validating these technologies to DISA mission requirements and responsibilities of the CIO. Develops process improvement standards and practices, provides senior technical direction on business decisions in the execution of specific agency projects. Provides senior IT leadership and serves as a consultant and advisor to DISA executive leaders and mission support staff ensuring technical results of the highest quality and effectiveness. CI4 guides the CIO in his internally-oriented position focused on technology needed for running the agency and solving problems through acquiring and adapting existing technologies. This task order outlines requirements for the contractor to provide Enterprise Architecture (EA) services necessary to support the DISA Chief Information Office. The DISA CIO is responsible for ensuring that all Department IT investments align to the agency’s business missions in accordance with a controlled enterprise architecture that provides an effective, efficient and secure information infrastructure for the agency. To accomplish this, DISA CIO as the chief architect supports a set of forums (boards, working groups and integrated product teams) to support the research and development, staffing, approval and publication of enterprise level information technology and information management guidance, including but not limited to, architectures, standards, plans, processes and policies.

4. Enterprise Architecture Objectives The CIO and the enterprise architecture team must advise program project leaders on business case/solution development. The EA team contributes to the development of investment proposals and work to facilitate progress through DISA’s capital planning and strategic investment process by aligning projects and tracking projects to DISA’s Campaign Plan, Strategic Plan and GIG Convergence Master Plan (GCMP). The CIO EA team has a specific interest in ensuring that projects identified in these strategic plans are supported, and may also introduce new projects and or solutions. For other projects, CIO EA team must support project leaders in initiating and developing proposals to align the Project to the DISA EA. To support these objectives the CIO’s EA team must perform proposal and program assessments. In the initial phase capital planning, the emphasis of these EA assessments is on the business alignment, business case solution, strategic plan, and technical compliance.

One goal of the DISA CIO is to maintain an Enterprise Architecture (EA) as the primary authoritative resource for Program, Planning, Budget, and Execution (PPBE) in the development of DISA’s Investment Portfolio. The Office of the CIO (OCIO) must be positioned with these responsibilities and authorities to improve the operating efficiency of DISA. In addition to statutory responsibilities through the Clinger-Cohen Act and related laws, under the IT Reform Plan there are four main areas in which CIO shall have a lead role:

1. Governance: DISA CIO must drive the investment review process for DISA’s IT investments and have responsibility over the IT portfolio for the Agency.

2. Commodity IT: DISA CIO must focus on eliminating duplication and rationalize DISA's IT investments. DISA’s commodity services include services such as: IT infrastructure (data centers, networks, desktop computers and mobile devices); enterprise IT systems (e-mail, collaboration tools, identity and access management, security, and web infrastructure); and business systems (finance, human resources, and other administrative functions

3. Program Management: CIO must improve the overall management of large Federal IT projects by identifying, recruiting, and hiring top IT program management talent.

4. Information Security. As the DISA Designated Approval Authority (DAA) the CIO is the appointed management official tasked to authorize the operation of an information system within an established set of security parameters and with an acceptable risk level.

In support of this reform plan DISA CIO enforces the use of the EA precepts as outlined and directed by the Department of Defense (DoD) Information Enterprise Architecture (IEA) 2.0. The DoD IEA provides a common foundation to support the accelerated transformation to net-centric operations and establishes priorities to address critical barriers. The DoD IEA highlights the key principles, rules, constraints and best practices drawn from collective policy to which applicable DoD programs, regardless of Component or portfolio, must adhere in order to enable agile, collaborative net-centric operations. DoD IEA core principles and rules are organized around five key priorities where increased attention and investment will bring the most immediate progress towards realizing net-centric goals:

1. Data and Services Deployment (DSD)

2. Secured Availability (SA)

3. Computing Infrastructure Readiness (CIR)

4. Communications Readiness (CR)

5. NetOps Agility (NOA)

DoD IEA’s core principles and rules support decision-makers across all tiers and portfolios (including Investment Review Boards and Capability Portfolio Managers) in managing the overall DISA Information Technology (IT) portfolio while also ensuring strategic alignment of programs and architectures to DISA’s enterprise vision.

5. Scope The scope of this Task Order includes DESS PWS task areas X, X, and X. In support of DISA CIO’s EA strategic plan requires application of the necessary technology management activities to institutionalize mandated processes for ensuring the synchronized development, approval, publication, and compliance of enterprise-wide agency IT. The mandated guidance includes standards and policies in fulfillment of the DOD CIO’s Title X, Title 40, Title 44, National Defense Authorization Act, Clinger-Cohen Act responsibilities, and DoD Directive 8210.xx (Enterprise Architecture (EA) in DoD).

The contractor shall provide continuing Project management support as requested by the Customer. Prepare Briefings, Status Reports, and Coordinate efforts among DISA teams, Coordination of DISA SMEs, Risk Management, Consolidation of DISA Implementation Plans, and liaison with other Defense Agencies, Review and Consolidate Responses for DISA.

IT Service Management and Support.

The contractor shall provide technical analysis and services to facilitate the implementation of a Managed Service approach on DISA internal IT enterprise while defining and establishing standardized enterprise-wide service delivery policies, procedures, and associated governance practices for managing, monitoring, coordinating, integrating, prioritizing, and performance reporting. The IT Service Management support will augment the DISA CIO’s existing Management Team and establish enterprise-wide service management and delivery standards that enable the DISA CIO to translate DISA’s strategic IT mission objectives into executable operational actions.

5.1 Information and Mission Assurance Support.

Contractor support shall provide technical security expertise in planning, preparing, oversight and executing DISA’s Information Assurance program. Also, to ensure DISA’s information infrastructure and systems are compliant with all mandated DoD, National Institute of Standards and Technology (NIST), Office of Management and Budget (OMB), Chairman of the Joint Chiefs of Staff (CJCS), U.S. Strategic Command (USSTRATCOM), U.S. Cyber Command (USCYBERCOM) and DISA tasking orders, directives, instructions, standards, and requirements.

Enterprise Architecture Support:

6. Enterprise Architecture Assessment Compliance

The objective of EA assessments is to enable the DISA CIO to determine if the proposed project aligns with agency strategic plans, goals, objectives, and meets requirements under the auspices of DoD IEA, Clinger Cohen Act (CCA), and Business Enterprise Architecture (BEA) and Agency IA requirements. The Business Enterprise Architecture (BEA) is the enterprise architecture for the DoD Business Mission Area (BMA) and reflects the DoD business transformation priorities; the Business Capabilities required to support those priorities; and the combinations of Enterprise Systems and Initiatives that enable those capabilities. BEA 8.0 aligns with DoD Architecture Framework (DoDAF) 2.0 name conventions and comprises a set of integrated products including the All Viewpoint (AV), Capability Viewpoint (CV), Operational Viewpoint (OV), System Viewpoint (SV), Services Viewpoint (SvcV), Standards Viewpoint (StdV), and Data & Information Viewpoint (DIV). Together, the aforementioned Viewpoints display capabilities, activities, processes, data, information exchanges, business rules, system functions, services, system data exchanges, technical standards, terms, and linkages to Laws, Regulations, and Policies (LRP). The purpose of the BEA is to provide a blueprint for DoD business transformation that helps to ensure that the right capabilities, resources and materiel are rapidly delivered to our warfighters: What they need, where they need it, when they need it, anywhere in the world. The BEA guides and constrains implementation of interoperable defense business system solutions as required by the National Defense Authorization Act (NDAA) and guides information technology (IT) investments to align with strategic Business Capabilities as required by NDAA, Clinger-Cohen and supporting Office of Management and Budget (OMB) and Government Accountability Office (GAO) policy. In support of DoD’s BEA requirements DISA CIO must review all investments. The goals and objectives of the review (see Table 1 below) are to ensure that the expected business outcomes of the project are aligned to concept and high-level project requirements.

Table 1 – EA Goals and Objectives

7. Enterprise Architecture Maturity Framework (EAMMF) Assessment

To ensure the DISA builds a strong EA competency agency wide the contractor will provide Enterprise Architecture Maturity Framework (EAMMF) Assessment to DISA current EA activities and planning. Application of the EAMMF to DISA will assist in sharpening the focus of EA being applied and also broaden its application across the entire DISA agency. At present DISA’s EA lacks formal institutional acceptance across the agency and unable to foster change and efficiency as it might once more EA maturity is established. Founded on Carnegie-Mellon’s Software Engineering Institute’s Capability Maturity Model for Software the GAO EAMMF methodology is organized into 7 levels. Each level represents an increased ability to control and manage the Enterprise Architecture (EA) for a component, service or agency (C/S/A). Contractor shall perform annual assessments, results, and recommendations to correct and or develop necessary maturity in the following 7 areas to support more effective agency wide EA.

Table 2 - DISA EA EAMMF Deliverable Requirements Matrix

8. Implement an IT Enterprise Portfolio Management Information Environment As directed by the Government the contractor will:

Develop a DISA Enterprise Architecture IT Portfolio Management (IT PfM) Requirements document based on DoD, DISA policy, laws and guidance. Conduct review and analysis to baseline existing DISA IT PfM. Sumarize these two activites in an IT PfM Finding and Recomendations white paper. The objective of this task is to identify alignments in IT PfM that need to be made in support of DISA’s goals and objectives outlined in DISA’s EA Governance Framework.

Develop a data and services strategy model and approach to support DISA EA by leveraging existing DoD EA resources (e.g. DITPR, DARS, EMASS, and GTG). Contractor will work with the owners of these systems/services for application to CIO use, consumption, and or support. This data and services strategy must leverage DISA IT PfM as this portfolio will be foundational to tracking and management of EA assessment and compliance.

Implement and Support an Enterprise Architecture repository to support a DISA IT Enterprise document library of artifacts. The repository must support reasonable number of different multiple architecture artifact formats as determined practical by the government. The EA repository must be made available to agency wide DISA EA community. The contractor must provide and demonstrate a comprehensive requirements analysis has been performed. The design and implementation of the DISA EA Repository must leverage the DISA EA data and services strategy (task 4.3.3.2). Essential to this work is that existing DoD resources are leveraged. DISA CIO EA requires significant EA visibility across the agency while implementing a repeatable assessment process through a single, secure, and unified information environment.

Conduct technical analysis DISA IT PfM to identify and propose logical sequential breakdown of detailed transition plans required to accomplish the goals of the DISA IT enterprise IAW with the DISA Campaign Plan, GIG Convergence Master Plan (GCMP), and applicable data and service planning.

Provide technical risk analysis and assessment of DISA’s IT portfolio. The contractor will focus on eliminating duplication and rationalize DISA's IT investments by leveraging DISA’s IT portfolio management IT (PfM). DISA’s commodity services include services such as: IT infrastructure (data centers, networks, desktop computers and mobile devices); enterprise IT systems (e-mail, collaboration tools, identity and access management, security, and web infrastructure); and business systems (finance, human resources, and other administrative functions).

The contractor will support DISA CIO with alignment of IT resources, to consolidate duplicative investments and applications. The CIO EA must show a preference for using shared services as a provider or consumer instead of continuing to standing up separate independent services.

In support of driving a leading edge shared services environment the contractor will leverage DISA IT PfM activities to support forward thinking approach to meet DoD’s anticipated IT service needs.

9. DISA EA Governance Framework The contractor will support the DISA CIO EA review process for DISA’s IT investments. In addition, the contractor will work with Chief Financial Officers and Chief Acquisition Officers to ensure IT portfolio analysis is an integral part of the yearly budget process for DISA. Contractor may be asked to support Integrated Project Teams (IPTs) in compliance review sessions which are designed to improve line-of-sight between project teams and DISA’s senior executives.

The contractor will update and or write supporting DISA EA governance instructions, directives, and or policy as directed by the government.

The contractor will provide DoD EA thought leadership to support technical EA disciplines, DoD EA domain knowledge, and EA policy, laws, and governance (PLG). The contractor will participate with government in both industry and government EA plenary sessions and conferences.

10. DISA EA Community of Practice and Communications Plan In support of DISA EA Community of Practice the contractor will develop DISA EA CoP Plan and EA Communications Plan. These plans shall make use of DISA investments in MS SharePoint services. The contractor shall provide share point development support to develop these plans as on-line DISA EA resources. Together these plans must:

Socialize stakeholders and seniors about the establishment of the EA CoP

Provide a formal process for DISA EA SME identification within each applicable directorate Communicate education and certification opportunities to agency Enterprise Architects in accordance to standards set by DoD EA governance structures, Architecture Standards Working Group (ASRG), Federal Enterprise Architecture Council (FEAC) requirements and accredited University educators (e.g. National Defense University, University Of Pennsylvania, etc) Develop a schedule to introduce, educate and provide access to the agency’s EA tool Educate Directorates on the benefits of a mature agency EA Program

Support facilitation of compliance with OMB and DoD prescribed mandates and policies

Facilitate EA knowledge sharing and internal needs of the DISA Directorates customer community to make Enterprise Architecture usable.

11. DISA EA Repository and Architecture Management Contractor shall design and implement an internal agency EA repository. An EA Repository shall be designed to scale to provide decision support for all levels of management throughout the agency. The EA Repository will become the hub for storing architecture variants, viewpoints, views / models and architecture elements that comprise these objects. The architecture elements to be stored in the repository must have pre-defined and well maintained definitions from authoritative sources. The EA Repository will integrate and display enterprise information that supports the DISA Command Group, Senior Decision Authorities (SDA), Senior Management, and the agency communities of interest (COI), and leverages Commercial off the Shelf (COTS) and EA development tools.

The repository must capture architecture, functional, operational, and service capabilities that exist within the DISA enterprise to facilitate total accountability of agency capabilities. It must enable transparency to senior leadership and component managers to have an agency-wide visibility of their information technology and functional resources. The repository must capture architecture, functional, operational, and service capabilities that exist within the DISA enterprise to facilitate total accountability of agency capabilities.

This EA repository must enable transparency to senior leadership and component managers to have an agency-wide visibility of their information technology and functional resources.

The contractor will provide an EA repository Program Management Plan that addresses all life cycle requirements to include but not limited to repository Hosting, EA Configuration Management (CM), Standard Operating Procedure (SOP), and alignment to DISA and DoD’s EA community of practice.

12. DISA EA Security Risk Management Architecture Acting as the Designated Approval Authority for DISA the DISA CIO is the DISA Chief Architect and his/her signature authority must be supported by clear defined framework from which DISA will manage and mature the IT infrastructure and capabilities. This framework shall encompass all systems, services, process and capabilities from the most basic internal DISA business system to the most distributed command and control (C2) system receiving DISA support. As DISA must respond to support both joint and service unique requirements it’s imperative that the agency leverage an enterprise architecture approach to facilitate standards to both operate and govern.

In support of establishing risk assessments the contractor will develop a Security Risk Management Architecture (SRMA) framework that will support DISA’s enterprise wide strategic security risk and technology architecture planning as it aligns to DISA policy, laws, and governance in support of EA compliance.

In support of program alignments to the SRMA the contractor will develop EA Information Assurance (IA) risk assessment metrics to be applied to appropriate DODAF artifacts. These artifacts can then be required to support acquisition milestone decisions while also being mandated in support of IA risk assessment.

13. DISA/DESS/ Network Program Management Documentation

As directed by the Government the contractor will conduct technical analysis to develop and maintain the DISA IT Enterprise DoD Architecture Framework (DODAF) views, (e.g., to include but not limited to OVs, TVs and SVs), and other network architecture documents as requested. Documenting DISA’s network and services architecture using DODAF shall support alignments identified in DISA’s IT Enterprise Five Year IT Strategic Plan. The contractor shall assemble and develop Enterprise Architecture requirements documents based on DoD, DISA and DISA CIO goals.

Implement and Support an Enterprise Architecture repository to support a DISA IT Enterprise document library diagrams and views

Conduct technical analysis to identify/propose a logical and sequential breakdown of projects required to accomplish the goals of the DISA IT Enterprise IAW with the DISA Campaign Plan and GIG Convergence Master Plan (GCMP).

Provide technical analysis and documenting the design and implementation efforts required to achieve the goals identified in the DISA CIO’s Enterprise Architecture plan and the DISA Campaign Plan and GIG Convergence Master Plan (GCMP).

Develop and maintain supporting Laws, Policy, and instructions as required to support EA Governance structure.

DISA Enterprise supports DISA’s five key strategies: Speed, Power to the Edge, Operational Effectiveness, Sharing & Defense of Information, and Best Value. The DISA Enterprise Architecture will facilitate technological improvements in these areas by providing information that will be useful to the communities described above in “Architecture Viewpoints.”

The contractor shall develop and maintain a comprehensive set of DESS network DODAF architecture products that can support network management, documentation, and testing. Documentation will adhere to the DoD Architecture Framework (DoDAF) 2.0 formats for all work products. Network drawings and plans will be provided in a timely fashion (e.g., documentation related to DISA Enterprise and Develop Net). The level of detail for the network diagram and security architecture goes down to the resource level (i.e. firewall, router, software package, etc.) and extends throughout DISA Enterprise to the Service Delivery Points of the DISA Enterprise locations and/or the last DISA Enterprise asset prior to the DISN. Network diagrams will be communicated using Microsoft Visio, but data will be input into Telelogic’s System Architect for analysis and transition planning purposes. CI4 EA team will work with contractor to develop a SharePoint site to publish the DISA Enterprise architecture.

1. Long term EA goals include: Capturing long-term objectives and plans to adopt additional capabilities as DoD budgets shrink

2. Capture the ‘requirements’ necessary to develop long-range network growth plans and adoption of concepts like Cloud Computing.

3. Develop Continuity of Operations Plan (COOP)

4. Leverage documentation and lessons learned from Base Realignment and Closure (BRAC) activities.

5. Support simulation and what-if scenarios (e.g., how can we determine the number of users affected when a specific component, building floor, or site experiences an outage).

The following is an overview of the products and activities in which the required DODAF artifacts will support:

· As-Is Network Architecture - The data gathered will be used to create a network architecture diagram illustrating the connectivity, both internally and externally, provided by the DISA Enterprise network. At the highest level, the Network Diagram will resemble a CONOps, Operational Views, Systems Views, Technical Views, and more detailed decompositions will drill down to specific sites, buildings, floors of buildings, and possibly to the level of specific components, if the data is available (e.g., from up-to-date as-built and/or a network discovery exercise). All levels will be documented to resemble tailored DoDAF views (i. e., OV-1, OV-2, SV-2, etc.) The deliverables will include descriptions of the diagrams.

· To-Be Network Architecture - Through facilitation with DISA leadership, the operational purpose and strategy for the infrastructure will be established to provide clear direction for the continual evolution of DISA Enterprise and GiG compliant, Net-Centric DISA Network Architecture (e.g., “as-is” and future OV1/SV1).

· Network Security Architecture – The security architecture will provide details on the alignment of DISA Enterprise with Defense-In-Depth principles. The following will be considered: Hardware resources such as firewalls, Intrusion Detection System (IDS) and Common Access Card (CAC) readers, as well as software assets such as Single Sign On (SSO) and Lightweight Directory Access Protocol (LDAP). Security standards that dictate the configuration of security assets will also be included.

· Technical Standards Profile - The architecture will include a profile of standards that will be applied to various segments of DISA’s network to ensure compliance with governing authorities. This will address the current and future standards (tailored TV-1/TV-2).

· Configuration Management (CM) Plan – a formal change process necessary to keep the data quality of DISA’s architecture at the highest level possible. The CM Plan will spell out the processes for maintaining the infrastructure segment of the EA. This will include understanding new system introduction processes, break/fix, and release management.

· Transition Plan– A DISA Enterprise Transition Plan will be created to align current initiatives affecting DISA Enterprise to provide a single picture of how the infrastructure is changing and emerging technologies can be introduced. This information will feed analysis and recommendations for DISA’s target architecture. The high-level DISA Enterprise transition plan will address how to incorporate GIG 2.0, Joint Task Force-Global Network Operations (JTF-GNO) and Defense Enterprise Computing Centers (DECCs).

The proper accurate completion of this architecture documentation will provide useful, accessible, navigable information that will:

1. Serve as a tool for DISC planners and designers involved in future DISA Enterprise improvements

2. Facilitate network trouble-shooting, e.g., determining effects of specific network or server component outages, and what-if planning

3. Provide useful information to other functional or network systems (e.g., a network that plans to connect to DISA Enterprise) to promote development of standards

4. Support investment planning, purchasing analysis, and decision support, with regards to upgrades and maintenance

5. Support configuration management of changes that relate between the network and applications.

6. Understand the network topology to assess impacts of change on DISA programs; enabling program managers (and the enterprise) to plan for future changes to DISA Enterprise.

7. Capture the Transition Plan based on ‘enterprise’ requirements necessary to meet DISA’s strategic direction

8. Serve as a tool for DISC planners and designers involved in future DISA Enterprise improvements

9. Facilitate network trouble-shooting, e.g., determining effects of specific network or server component outages, and what-if planning

10. Provide useful information to other functional or network systems (e.g., a network that plans to connect to DISA Enterprise) to promote development of standards

11. Support investment planning, purchasing analysis, and decision support, with regards to upgrades and maintenance

12. Support configuration management of changes that relate between the network and applications.

13. Provide understanding the network topology to assess impacts of change on DISA programs; enabling program managers (and the enterprise) to plan for future changes to DISA Enterprise.

14. Capture the Transition Plan based on ‘enterprise’ requirements necessary to meet DISA’s strategic direction.

The DISA/DESS Enterprise architecture viewpoints shall be developed focusing on using GIG 2.0 plans, DISA’s 2011-2012 Campaign Plan, key DISA and relevant DoD enterprise-level initiatives, processes and information. The enterprise level defines network capabilities that are required per statute, policy, best practice, or longstanding practice. The architecture will be developed to support several viewpoints and stakeholders with differing, but related needs as follows:

· Investment decision making – e.g., DISA Components can examine programmatic considerations for initiatives such as consolidations, proposed systems, and new IT in context with interoperability needs, integration or leveraging opportunities, and expected impact on mission effectiveness.

· Capability and interoperability analysis – e.g., DISA can analyze architectures in terms of their support to joint concepts, identification of capability needs, and determine the operational and support-related performance attributes of a system(s) that provide the capabilities required by the users.

· Component system development – e.g., DISA developing systems can use architectures to determine system concepts related to operational concepts and ensure interoperability.

· Operational planning – e.g., DISA enterprise planners can examine how various mission participants, systems, and information work together, what problems may be encountered, and what quick fixes may be available.

· Compliance with DoD Business Enterprise Architecture (BEA) – DISA Enterprise architecture will help to ensure compliance with the DoD BEA.

· Compliance with Global Information Grid (GIG) Enterprise Services (ES) – DISA will ensure compliance with the DoD GIG-ES. The goal of GIG-ES is to improve the speed and quality of DoD decision making by connecting information producers and consumers more effectively through information technology and Net-Centricity.

· Transition planning - DISA can use the architecture to make transition plans, establish schedules, and to retire legacy systems, reengineer and/or integrate systems and applications.

The following Table (Table 3) provides detailed descriptions and requirements for DISA Network architecture documentation.

Table 3 - Required DODAF Network Deliverables

For “To Be” system: serves as a planning guide of the purpose, scope, context, and tools.

One dictionary with entry requirements noted for “As Is” and “To Be” architectures.

14. Place of Performance

14.1 Primary Place of Performance

The Contractor shall perform work in Government provided office space located in the DISA Headquarters campus located on Fort Meade, MD.

14.2 Alternate Place of Performance

Contractor employees may be required to work at home, another approved DISA activity within the local travel area or at the contractor's facility in cases of unforeseen conditions or contingencies (e.g., pandemic conditions, exercises, etc.). Any equipment such as laptops or phones provided to Contractor personnel shall be returned at the termination of the engagement or at another time mutually agreeable to both parties. Contracting Officer Representative (COR)/Task Order COR (TO COR) approval is required. Contractor shall prepare all deliverables and other contract documentation utilizing contractor resources. The contractor shall continue to provide the same level of support as stated in the PWS. In the event the services are impacted, reduced, compromised, etc., the Contracting Officer may request an equitable adjustment.

15. Travel Requirements

Contractor travel is anticipated to support the requirements named in this document. The Contractor shall project anticipated travel in the quote, and obtain approval from the Customer prior to actual travel. The Contractor shall submit invoices for direct costs related to travel no later than 30 days following the end of travel. Travel, per diem, and other direct costs will be reimbursed in accordance with the US Government Joint Travel Regulations (JTR).

16. Period of Performance The period of performance for this Task Order is twelve (12) months from date of award.

17. Delivery Schedule Due dates for all deliverables associated with this Task Order are identified in the table below.

DELIVERABLES

18. Service Level Agreements and Performance Metrics

INCLUDE ANY PERFORMANCE MEASURES OR REFERENCE THE APPENDIX FOR SERVICE LEVEL AGREEMENTS

19. Security Requirements The work to be performed under this contract is up to and including the Secret level and positions are IT-II for systems access.