SOURCES SOUGHT
D -- Joint Project Manager Information Systems (JPM IS) - Package #1
- Notice Date
- 8/26/2011
- Notice Type
- Sources Sought
- NAICS
- 541712
— Research and Development in the Physical, Engineering, and Life Sciences (except Biotechnology)
- Contracting Office
- Defense Information Systems Agency, Procurement Directorate, DITCO-Scott, 2300 East Dr., Building 3600, Scott AFB, Illinois, 62225-5406, United States
- ZIP Code
- 62225-5406
- Solicitation Number
- MAC0043
- Archive Date
- 10/4/2011
- Point of Contact
- Rachel Rieger,
- E-Mail Address
-
rachel.rieger@disa.mil
(rachel.rieger@disa.mil)
- Small Business Set-Aside
- N/A
- Description
- Graphics included. Request for Information (RFI) Federal Acquisition Regulation (FAR) Part 10 requires the Government to conduct market research before developing new requirements documents for an acquisition. Results of market research are used to determine whether qualified sources exist and whether commercial items or non-developmental items are available to meet the requirement. One of the ways the Government conducts market research is to issue a Request for Information (RFI). This RFI provides a broad statement of need, briefly describes the Government's intentions regarding program approach, and identifies key organizations. All responsible businesses, including small businesses, are encouraged to respond to this RFI. Additionally, this RFI is issued to assist the agency in determining whether or not there are qualified and capable Small Businesses to provide the type of services described below. Disclaimer THIS RFI IS NOT A REQUEST FOR PROPOSAL (RFP) AND IS NOT TO BE CONSTRUED AS A COMMITMENT BY THE GOVERNMENT TO ISSUE A SOLICIATION OR ULTIMATELY AWARD A CONTRACT. RESPONSES WILL NOT BE CONSIDERED AS PROPOSALS NOR WILL ANY AWARD BE MADE AS A RESULT OF THIS SYNOPSIS. All information contained in the RFI is preliminary as well as subject to modification and is in no way binding on the Government. FAR clause 51.215-3, Request for Information or Solicitation for Planning Purposes is incorporated by reference into this RFI. The government does not intend to pay for information received in response to this RFI. Responders to this invitation are solely responsible for all expenses associated with responding to this RFI. This RFI will be the basis for collecting information on products available. This RFI is issued solely for information and planning purposes only and does not constitute a solicitation. All information received in this RFI that is marked Proprietary will be handled accordingly. Responses to the RFI will not be returned nor will receipt be confirmed. In accordance with FAR 15.201(e), responses to this RFI are not offers and cannot be accepted by the Government to form a binding contract. Background The Joint Project Manager Information Systems (JPM IS) is seeking a prime contractor that can support the systems and software engineering lifecycle of enterprise information technology and information management. Specifically, support is required within the all-hazards domain with a focus on Chemical, Biological, Radiological, and Nuclear (CBRN) capabilities. As part of the Joint Program Executive Office for Chemical Biological Defense (JPEO-CBD), JPM IS is responsible for the development of the IM/IT Enterprise. The IM/IT Enterprise is part of the overall Chemical Biological Defense Program (CBDP) Enterprise, which provides Discoverable Services, Enhanced Situational Awareness, Actionable Intelligence, and Decision Support to achieve Shared Situational Awareness to "provide the right information to the right person at the right time." The evolving IM/IT Enterprise will: •· Achieve the interoperability critical to the CBRN mission by providing a data dissemination, messaging, and routing subsystem (which reuses existing Department of Defense (DoD) capabilities) that integrates existing JPEO-CBD information system outputs into an environment that can detect threats, collect and disseminate appropriate data and make relevant information accessible to those who need it; in essence, facilitate early warning, assessment and reporting to address an incident •· Adapt to changing warfighter Tactics, Techniques, and Procedures (TTPs) and the incorporation of additional capability modules, authoritative data sources, and optimizations within the enterprise •· Provide actionable data presented both within the IM/IT domain and to external stakeholders (system to system communication) •· Improve access to timely mission critical actionable information through fused data products with shorten time to develop and distribute information to key stakeholders •· Enable data from multiple sources to be shared by multiple applications •· Implement rapid acquisition and development practices that allow capability to be specified, designed, developed, tested, certified, and fielded in 3-18 month cycles •· Refine and define common integration standards and processes for capturing requirements, managing software development processes and data validation strategy •· Eliminate redundant capabilities through centralized requirements and configuration management tools •· Provide real/near-real time software component services and data that can be easily integrated as tools and services •· Implement Command and Control (C2) platform independent implementations that follow Joint Defense Information Systems Agency (DISA), Industry, and Open Standards, in addition being granular and modular so that capabilities can to be easily integrated into Army Common Operating Environment (COE), other Armed Service standards, Homeland Defense standards, other frameworks, environments, platforms, and required interfaces •· Include comprehensive training products from a common logistic entity •· Provide a comprehensive "one-stop" system support for warfighters via a unified help desk and software deployment strategy •· Create an expandable and adaptable enduring capability that will continuously leverage emerging technologies •· Evolve a "Capability Lifecycle Integration Platform" (CLIP) which includes a set of development processes and tools, technology standards, and reference and runtime architecture that will support all lifecycle activities to define, develop, and deliver CBD software capabilities In Accordance With (IAW) DISA approved services, a common data model, and standardized development, integration, validation, and product support processes •· Provide a platform which can be utilized by the Science and Technology (S&T) community to support the development, maturation, and technology readiness level evaluation of S&T capabilities that are potential targets for future transition to the IM/IT Enterprise •· Comply with Chairman of the Joint Chiefs of Staff (CJCS) and DoD directives, instructions, and guidance •· Comply with and be supportive of all required Information Assurance controls, directives, instructions, and guidance •· Support multi-level and cross-domain developmental, test, and operational environments from UNCLASS up to Joint Worldwide Intelligence Communications System (JWICS) and StoneGhost JPM IS is committed to supporting the DoD's evolving direction and guidance with respect to streamlined information technology acquisition. JPM IS will employ the key tenants of Fast, In-Expensive, Simple, and Tiny (FIST) with a "build a little, get user feedback, test a little, field a little" continual loop where every completed tiny spiral of new capability can be fielded in 3-18 month cycles and in which updates or patches can be provided within hours or days. Those key tenants include having projects performed by the smallest possible team of talented people, using a short schedule, a small budget and mature technologies to deliver innovative solutions to urgent needs. Short timelines increase agility and stabilize requirements, technology, budgets and people and also force accountability, ownership and learning. To maintain short timelines, JPM IS and the contractor will exercise restraint over budgets, complexity and size, as increases to the project's budget, complexity or size inevitably reduce its speed. Under this model, delivering useful capabilities is the only measure of success. Working software is emphasized first over comprehensive documentation (though ultimately required), customer collaboration over contract negotiation (though still meeting all legal and acquisition requirements, laws, and regulations), responding to change over strict adherence to plan (expect to modify and refine the plan as required in a collaborative environment). JPM IS will continue to migrate and evolve towards a Framework for Software Product Lines to plan, guide, and execute the CBRN IM/IT Enterprise product line development and sustainment. The Software Engineering Institute (SEI) Framework for Software Product Line Practice SM ("the framework") describes the complete foundational product line concepts and identifies the essential activities and practices an organization must master before it can successfully field a product line of software or software intensive systems. The framework is a living document that is evolving as experience with product line practice grows. Version 4.0 is described in the book Software Product Lines: Practices and Patterns [Clements2002], and the latest version is available on the SEI Web site - http://www.sei.cmu.edu/. A software product line is a set of software-intensive systems sharing a common, managed set of features that satisfy the specific needs of a particular mission and that are developed from a common set of core assets in a prescribed way. [1] JPM IS is implementing a fully interoperable and/or integrated electronic cloud based systems engineering lifecycle development environment to support component-based development of services for CBRN IM/IT. The engineering lifecycle development environment will include the evolution of the JPM IS software ecosystem with components tailored to each computing environment that will allow JPM IS to leverage industry best practices, and rapidly develop secure and interoperable applications that satisfy operational requirements. The environment will require that software applications be abstracted from the hardware and software infrastructure supporting them. Components to be developed and/or integrated must be compliant with required DISRonline standards, align to the Army Chief Information Officer (CIO)/G-6 COE, and be modular and abstracted such that integration into Joint and Service-specific command and control platforms (e.g., Global Command and Control System (GCCS)-X, Joint Tactical Common Operational Picture (COP) Workstation (JTCW) JTCW, Unit level Command and Control (UC2)/ Theater Battle Management Core System - Unit Level (TBMCS)-UL, Force XXI Battle Command Brigade and Below (FBCB2)) can be done quickly and inexpensively. IM/IT capabilities may be targeted for one or more combinations of data centers, cloud, command post, platform, or otherwise mounted, mobile/handheld, sensor, and real-time safety critical embedded deployments. JPM IS must be able to acquire the software application products in compliance with federal and DoD regulations and policies. Government ownership of any documentation and software is required as well as the need to be shared among contractors. Evolution of existing capabilities is required, as opposed to revolution or wholesale replacement of existing capabilities. Key Concepts In the IM/IT Enterprise, the core assets required to efficiently define, develop, deploy, and support these yet-to-be-determined CBRN product-specific operational capabilities are the JPM IS Systems Integration Laboratory (SIL) and the CLIP. [1] Software Product Lines: Practices and Patterns, Version 4.0 (Clements 2002). Capability Lifecycle Integration Platform (CLIP ) The CLIP is an evolving set of development processes and tools, technology standards, protocols to include and/or support: •· A fully interoperable and integrated systems engineering development environment including all associated toolsets and processes •· Development, Staging/Integration, Test and Evaluation, and Production/Operational environments and electronic workflow that supports promotion through environments as a function of integrated bug/feature tracking results and approval of promotion based on user roles •· Standard Operating Procedures (SOPs), training material, reference implementations, FAQs, Help Desk and user servicing capabilities •· Utilization of emerging DoD capabilities to provide an "App Store" front-end for approved capabilities •· Utilization of open source, license free capabilities to the extent possible that are still supportive of overall DoD direction (e.g. perhaps leveraging forge.mil; e.g. if we know Army Knowledge Online (AKO) is going to be phased out, don't recommend AKO; if we know SharePoint is a preferred capability don't submit another similar open source solution (i.e. a case where a licensed capability may be necessary, utilize Volume License Agreements (VLAs) which exist in DoD that can reduce the cost)) •· Capability (for authorized users) to download the build environment, source, scripts, required to evaluate, analyze, develop, and test on a particular component or service •· Reference architectures and implementations that utilize common standards and protocols (e.g., Common CBRN Sensor Interface (CCSI), Common CBRN Model Interface (CCMI)) •· Efficient development and deployment of Services and components that can be independently evaluated in a standardized development and integration environment •· Processes that account for all cyber and information assurance requirements to support efficient certification and accreditation •· Modeling and simulation data analysis and capture that is supportive of model accreditation Systems Integration Laboratory (SIL) The SIL is located in San Diego, CA at SPAWAR Systems Center Pacific (SSC-P) and is an evolving capability that will provide facilities, equipment, and networks required to develop, test, and deploy in the operationally relevant Joint and Service specific environment(s), including platforms, networks, host systems, and installations. In particular, the SIL will evolve to provide: •· Provide an environment for Joint Interoperability Test Command (JITC) assessments and certifications, integration, and test and evaluation in the required operationally representative environments, including modular and virtualized environments that would be adaptable to accommodate a wide range of handheld and vehicle platforms, web browser based clients, thick clients, and enterprise services. •· Staging and integration environments that support updates for testing, including capabilities that allow specific hardware to be added to the environment (e.g., sensors, emulators, systems) •· Network and communications test fixtures and sets to analyze and/or design wired and wireless communications gear including a configurable communications test network layer that permits bandwidth and frequency assessment and changes that include wireless components, such as satellite link, digital modular radio, and software wave form radios (e.g., Joint Tactical Radio System (JTRS)) that would be needed to complete spectrum analysis and testing •· Data collection to facilitate analysis, design, score, and validation of capabilities throughout the development and testing •· A suite of automated testing tools to manage tests, validate conformance to standards, and analyze runtime functionality and performance (e.g., Navy sponsored ATRT) •· Versions of deployed infrastructure and services sufficient to support the execution and testing of services or service orchestrations under development and test, as well as mechanisms to determine the testing or certification status of a service or service orchestration (end-to-end thread) •· A mechanism for stubbing out or simulating services that are not yet developed Statement of Need JPM IS requires the evolution of the existing SIL and CLIP to the envisioned end-state of capabilities described herein to ultimately support agile specification, development, deployment, and support of future modular service-oriented CBRN IM/IT capabilities in accordance with existing and evolving DoD direction for streamlined software acquisition and speed to capability. [1] Questions to Be Addressed Interested parties are requested to provide a succinct response addressing: •· Volume I: General Questions (15 page maximum) •· Volume II: Recent and Relevant Experience (5 page maximum) Volume I: General Questions The JPM IS Joint Warning and Reporting Network (JWARN) Increment 1, Joint Effects Model (JEM) Increment 1 and Increment 2 science and technology, development, integration, testing, and product support environments will provide web-based capabilities in a secure cloud environment for [e.g. DISA DECC RACE]. The intent for JPM IS to own and manage the CLIP and the SIL and then have an environment that allows JPM IS to quickly and inexpensively contract for development of capabilities/services in this environment that can be deployed on the order of weeks, vice months, or years. •1. Does your firm have expertise in DoD command and control systems? •2. Does your firm have expertise in the development, integration, and fielding of JWARN, JEM, or other CBRN information systems? •3. If "yes" to Question #1 or #2, how does your firm's expertise position you to execute these capabilities for JPM IS, while minimizing any learning curve and associated cost? •4. Is your firm capable of providing personnel and facilities that are cleared to the TS/SCI level? •5. How would your firm provide a portal that would allow secure network access to the JPM IS SIL and CLIP and what is the rank order (roadmap) of the temporally aligned tasks you would perform to fully implement the SIL and CLIP and why? •6. How would your firm configure the SIL and linkage to the CLIP? •7. What other capabilities would your firm include in the CLIP and SIL that JPM IS has not specified and why? •8. JPM IS is more interested in personnel that are hands-on technical experts in mission critical software product development and fielding than in management and administrative personnel. How can your firm provide JPM IS with the required expertise with minimal management and administrative overhead, while providing a valuable end-product? •9. How does your firm's experience in international partnerships (e.g., Foreign Military Sales (FMS), and International Traffic in Arms Regulations (ITAR)) qualify you to support IM/IT DoD-approved international initiatives? •10. What experience does your firm have in implementing strategies to ensure that the software capabilities/components you develop can be provided (via access to the SIL and CLIP) as a complete GFI package to other CBRN IM/IT developers and integrators that would serve as a complete reference implementation from which they could build additional capabilities? Volume II: Recent and Relevant Experience This portion of the RFI will assist JPM IS to determine whether there are sources available to provide the type of services contemplated within this RFI. In particular, interested small businesses meeting the small business standard of North American Industry Classification System (NAICS) code 541712 are encouraged to submit a response to this RFI. For this volume: •· Provide your company's DUNS number and CAGE code •· Include recent (within the past three years or work that is on-going) and relevant experience (work similar in type and scope), including associated: •o Contract numbers •o Project titles •o Dollar amounts •o Points of contact (telephone number and email) Marketing brochures or generic company literature will not be considered. Not addressing all the requested information may result in the Government determining the responder is not capable of performing the scope of work required. Response Instructions Response Format Responses must be submitted in Microsoft Word format. RFI responses are limited to 20 pages, including cover and administrative pages, and shall be delivered using 10 font or larger. Submission Instructions and Deadline Responses are requested no later than 19 SEP 2011 at 1600 PST. Responses must be submitted via e-mail to: Mr. David Godso JPM IS CHENG / CIO david.godso@jpmis.mil Proprietary Data Proprietary information, if any, must be clearly marked. Proprietary information is not desired; however, if proprietary information is submitted, it should be marked as such and segregated. Please be advised that all submissions become Government property and will not be returned. It should be noted that telephone replies will not be accepted. Failure to respond to this RFI does not preclude participation in any future competition for this requirement, nor will information provided in response to this RFI be used to exclude anyone from responding to any future RFPs. Contractor Support Notice JPM IS intends to utilize contractor support in review of RFI responses: Company: Booz Allen Hamilton POC: Aaron Tuch Telephone: (619) 221-7212 E-Mail: aaron.tuch.ctr@navy.mil Aaron Tuch is a Booz Allen Hamilton (BAH) program/acquisition support contractor. He has an NDA on file and BAH has a no-bid in place for future JPM IS development contracts. Mr. Tuch supports the program office and is assisting the Government's review of RFI responses [1] The current JPM IS SIL and CLIP provide the starting point of baselined mature processes as evaluated by Carnegie Mellon SEI] that must evolve and scale to support IM/IT Enterprise lifecycle engineering [as recommended by Carnegie Mellon SEI].
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/DISA/D4AD/DITCO/MAC0043/listing.html)
- Record
- SN02551611-W 20110828/110826235733-dce20bd71cb323a27c221103e4c5a1c6 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |