Posted: Nov. 18, 2011, 11:21 a.m. EST
Purpose: DISA's Global Information Grid (GIG) EWSE Branch (EE21) will host an Industry Day to establish a dialogue with interested potential vendors and to answer questions on the background of EWSE and upcoming technical issues requiring resolution. On Industry Day, DISA EWSE will open the session by sharing the EWSE process for resolving GIG technical issues and answer questions related to the objectives of the larger EWSE work effort. DISA EWSE will also discuss the strategy for the task support requirements and the desire to understand the capabilities of small businesses in addition to those of larger companies.
When: The EWSE Industry Day will occur on Wednesday, 26 October 2011 from 9:00 am to 12:00 pm at MITRE-Annapolis Junction (Meade). The address is 300 Sentinel Drive, Suite 600, Annapolis Junction, Maryland 20701 (http://mitre.org/about/locations/md_annapolis_junction.html). Parking (deck) is available adjacent to the facility. The available space can accommodate 50 seats so we request contractors limit company attendance to a single representative. The first 50 respondents are guaranteed seats. Additional requests will be placed on a wait-list. Attendance is restricted to pre-registered applicants possessing photo identification on arrival. This meeting is UNCLASSIFIED; no visit request is required. The meeting will begin promptly at 9:00 am. We recommend that you plan to arrive not later than 8:30 am to accommodate for check-in delays. If the attendee is a U.S. citizen, please provide the following information to EWSE_WG@DISA.MIL not later than 12:00 pm on Friday, 21 October: full name, company name, e-mail address, contact phone number, and mailing address. If the attendees is a foreign national, you will need to provide your passport and the following contact information to the MITRE Security Office at least five business days prior to the meeting (by 12:00 pm Tuesday, 18 October): name, address, phone number, e-mail address, company they represent, company address, company phone number and company website. Please send your information to Ms. Jacquetta Burton via fax, 301-617-3370, or via secure email to jburton@mitre.org.
Background: DISA EWSE intends to issue RFPs (Request for Proposal) in the first quarter of FY 2012 in support of the FY 2012 EWSE initiative. In FY 2011, DISA EWSE issued four competitive task orders. The average value of the task orders was $870,000; individual values depended largely upon the complexity of the technical task. Each task is performed by a team with typical contractor staffing of 3 to 4 Full Time Equivalents.
DISA EWSE hosted the EWSE Working Group Meeting with DoD stakeholders on September 1, 2011 to review candidate topics for the FY 2012 EWSE issue cycle. The DISA EWSE approach is based upon identifying solutions that require DoD, Intelligence and Industry community involvement and expertise to capture the best ideas and approaches. Existing working groups and on-going initiatives within the communities are leveraged to the maximum degree possible when resolving technical issues. DISA EWSE requires Industry experts to complement the Government participants on each task by providing subject matter engineering expertise to the core team tasked with refining, analyzing, and proposing solutions to the technical issues. The task outputs are various technical products to include GIG Technical Profiles (GTP) and GIG technical architecture artifacts.
Current & Future Status: After the 2011 EWSE Working Group Meeting, candidate issues were consolidated and further refined. The following topics are currently considered for competitive acquisition in FY 2012 and will be discussed at the Industry Day. Additionally, more details could follow as amendment to this RFI:
1. GIG IPv6 Service and Network Architecture
DoD has worked IPv6 transition strategy and plan in the past and determined IPv4/IPv6 dual-stack model to be the baseline architecture for transitioning to IPv6. With most recent federal OMB and DoD IPv6 mandate and directives, there is an urgent and practical need to analyze the current IPv6 technical requirements and high-level transition plan, and develop detailed DoD IPv6 network architecture, engineering design and implementation guidance required for incremental implementation and transition across both strategic and tactical networks. During the transition, IPv4 only, IPv6 only and dual stack network islands will co-exist within GIG and complex permutation of interconnection among those network types need to be analyzed and addressed. So detailed transition approach and implementation guidance based on industry best practice need to be developed.
The objectives of this task are to develop: 1) DoD GIG IPv4/IPv6 dual-stack incremental network architecture and Implementation guidance for near/mid/far-term; 2) GIG IPv6 inter-domain routing architecture and networking service solution architecture (DNS, HAIPE GDS etc.); 3) Technical framework and approach to GIG IPv6 network management and IA requirements; 4) GIG IPv6 transition techniques and implementation guidelines based on industry best practice.
2. Service Level Interoperability for Tactical Edge and Core
The interoperability of services across different tactical edge & core domains is an essential requirement to support joint missions. For some infrastructure and core services (e.g. Service Discovery, Content Discovery, Collaboration) joint interoperability specifications/profiles are only partially complete, and those do not sufficiently address tactical edge technical constraints (e.g. DIL). As well, adoption by PORs of completed service interoperability specifications/profiles has been minimal. Leveraging the products from previous EWSE IPTs (e.g. the Joint Tactical Edge Services Framework), EWSE will continue its efforts in FY12 to support development and use of the joint interoperability specifications/profiles.
The objectives of the Service Level Interoperability for the Tactical Edge & Core (SLI-TEC) multi-year task will be to 1) complete development of the joint interoperability specifications/profiles for all infrastructure and core services in coordination with major programs and their existing service interface implementations, 2) provide support and guidance to related IPTs (e.g. Content Discovery & Retrieval IPT), PORs, and PEOs in order to aid in the adoption of the specs/profiles, 3) continue to improve the Joint Tactical Edge Services Framework and support its incorporation within relevant COI Architectures (e.g. JC2 Objective Architecture), and, 4) to research alternative architectural models to improve the performance and enhance the capabilities needed to support joint interoperability (e.g. Semantic Service Bus, Tactical Edge Bus).
3. GIG Cloud Computing Services Guidance
US CIO has issued a cloud first' policy in February 2011 to improve the efficiency and reduce the cost of federal IT infrastructure and services. DoD is also going through an IT consolidation effort to save cost. Cloud computing has been explored by many DoD organizations, such as DISA CSD, Army, Navy, USAF, USMC, and USTRANSCOM, as an efficient and cost effective way to host GIG services. There is an urgent need to develop a coherent enterprise level DoD cloud computing technical framework, architecture, and implementation guidance supporting all cloud services for DoD to ensure the interoperability of DoD clouds (e.g., private and community). Technical framework and architecture here intends to provide technical solution architecture to solve the issue of "What is the recommended interoperable DoD architecture to design, develop, and deploy cloud services (IaaS, PaaS and SaaS) from the DoD cloud service provider perspective". The technical guidance for cloud computing services at the enterprise level is critical to ensure the interoperability of cloud services and improve performance of cloud services. The guidance will cover how to build interoperable private cloud services from the DoD cloud service provider perspective. The interoperable resource pooling and data synchronization across clouds are basic capability required to support SaaS, Paas, and IaaS between cloud service providers. DoD Cloud Computing Strategy and Implementation Plan are business drivers for the enterprise level DoD cloud computing technical framework and architecture.
The objectives of this task are to develop:1) DoD Cloud computing technical framework including taxonomy of cloud computing terminologies based on NIST definitions tailored to DoD environment, use cases and requirements of functional capabilities to be provided by clouds, and DoD cloud service definition and criteria checklist to qualify for each type of DoD cloud service; 2) an overarching DoD cloud computing interoperability reference architecture to show how different clouds interface and interact with each other for resource pooling and data synchronization; 3) the near-term, mid-term, and long-term DoD cloud computing solution architectures for realizing the DoD cloud computing interoperability reference architecture to include design of system components of multiple layers (IaaS, PaaS, and SaaS) from the cloud service provider perspective; 4) DoD cloud computing implementation guidance including minimum essential engineering guidance and design patterns for new cloud services development and legacy services migration to cloud services; 5) Initial GTP Input for GIG Cloud Computing Services Guidance including framework, architecture, and implementation guidance with key components in SysML (Requirements Diagram, Sequence Diagram, Activity Diagram, Block Definition Diagram); 6) DoD Cloud Services Management and security capabilities with key components in SysML (Optional);7) DoD Cloud Computing Architecture and Implementation Guidance for Tactical DIL Environment with key components in SysML (Optional).
4. Dynamic Access Control Framework
DoD CIO identified the IdAM as the foundation for accessing future information services. The need for a consistent real time dynamic access control capability for DoD is identified as one of the DoD top IT priorities. Multiple IdAM frameworks exist within Federal government and DoD with fragmented lexicon and interface definition. There is a need for a synchronized framework in order to facilitate the development and implementation of a DoD wide dynamic access control capability with possibility to be able to interface with each other in the future. EWSE FY10 GIG Authentication and Access Control (GAAC) IPT started addressing the issue with a Dynamic Access Control Framework GTP/White Paper with recommended lexicon and ontology definition attempting to provide a platform to address the fragmented framework issue. The objective of this task is to leverage the GAAC work and further develop technical architecture and implementation guidance between the service provided by Enterprise and Community of Interest (COI) to facilitate such future program development of the dynamic access control capability.
The outputs needed are 1) Attribute Service architecture and interoperability guidance between Enterprise (Enterprise Identity and Attribute Service a.k.a EIAS run by DMDC) and COI attribute service. This architecture/guidance development will address the interoperability between EIAS and COI provided attribute services; 2) Access Control Policy Store/Service architecture and interoperability guidance between Enterprise and COI policy store/service. This architecture/guidance development will address the distribution of and interoperability between the enterprise and COI distributed policy service ; 3) Metadata attribute schema and discovery architecture between all Enterprise and COI information; 4) Environmental Attribute Service architecture and interoperability guidance between Enterprise and COI Environmental attribute service; 5) Transitional plan/architecture from "as-is" to "to-be" state on how to make the current COI Identity/Role Based Access Control (IBAC/RBAC) to an Enterprise-wide Attribute-Based Access Control (ABAC) ; 6) Non-Person Entity (NPE) related identity and access management reference architecture if the development in this area is mature enough to create a interoperability guidance during the course of the task.
In order to have a productive Industry Day, each company planning to attend should send a representative well versed on the above topics so that a meaningful dialogue can be conducted. Part of the discussion will clarify the technical problem statement as well as define some of the constraints placed on the potential problem solutions.
DISA will not address contractual questions during this Industry Day. The sole function of the meeting will be to provide industry a firm understanding of technical requirements, identify required expertise, and gain an understanding of the technical capabilities of the companies present. The Government is particularly interested in identifying small businesses that are capable of doing this type of work. For market research purposes, we request both large and small businesses provide the following company capability information NLT than 12:00 pm Friday, 21 October to EWSE_WG@DISA.MIL : 1) representative full name, 2) company name, 3) your NAICS codes and the associated business size standard, 4) e-mail address, 5) contact phone number, 6) capability statement limited to 10 pages organized by four technical topics described above in this section, 7) listing of contract numbers where you are the prime (e.g. GSA schedules, multiple award contracts, etc.).
Responses: Please submit attendance requests and company capability information by e-mail to EWSE_WG@DISA.MIL not later than 12:00 pm on Friday, 21 October. Responses must be single spaced, Times New Roman, 12-point font, with one inch margins & compatible with MS Office Word 2003. Proprietary information and trade secrets, if any, must be clearly marked on all materials. All information received that is marked "Proprietary" will be handled accordingly. Be advised that all submissions become Government property and will not be returned. All personnel reviewing responses will have signed non-disclosure agreements and understand their responsibility for proper use and protection from unauthorized disclosure of proprietary information as described 41 USC 423. The Government is not liable for any damages incurred if proprietary information is not properly identified.
Point of Contact:
EWSE Team, DISA EE21 ewse_wg@disa.mil
