SOURCES SOUGHT
D -- The Marine Corps Systems Command is requesting information concerning the governance, development, and operation of Service Oriented Architectures (SOA.)
- Notice Date
- 4/2/2008
- Notice Type
- Sources Sought
- Contracting Office
- M67854 MARINE CORPS SYSTEMS COMMAND Quantico, VA
- ZIP Code
- 22134
- Solicitation Number
- M6785408I2078
- Response Due
- 4/30/2008
- Archive Date
- 6/30/2008
- Point of Contact
- Sharon Ward703-432-4129Sharon.ward@usmc.mil
- Small Business Set-Aside
- N/A
- Description
- This is a Request for Information (RFI) as defined in FAR 15.201(e). The Marine Corps Systems Command is requesting information concerning the governance, development, and operation of Service Oriented Architectures (SOA) within the United States Marine Corps at the tactical and enterprise levels. This RFI provides an opportunity for respondents to submit their ideas, initiatives, and/or processes related to this request. This RFI is issued solely for information and planning purposes and does not constitute a Request for Proposal (RFP). Any procurement resulting from this announcement will be published separately in the Federal Business Opportunities (FBO). Furthermore, the Government does not intend to pay for any information/items, or otherwise reimburse responders for any costs associated with their respective submissions in response to this RFI. Responders are solely responsible for all costs and expenses associated with responding to this RFI. All infor! mation received in response to this RFI will be treated as business confidential information, however, any proprietary information MUST be marked as such, on a page-by-page basis. Moreover, in accordance with FAR 15.201(e), responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. Background The Department of Defense has directed the migration of the military services legacy network architectures to implement service oriented architectures within the enterprise and to the greatest extent possible down through the tactical level. The Marine Corps considers the tactical level as everything within the Marine Air Ground Task Force (MAGTF) and the enterprise as everything external to the MAGTF. Multiple programs within Marine Corps Systems Command are endeavoring to implement SOA in order to align with DoD and USMC requirements. Additionally, the MAGTF C2 Systems and Applications program was created to focus disparate USMC C2 program efforts towards a common goal and delivery in order to dramatically improve the Marine Corps｡ｦ ability to respond to change, reduce costs, and accelerate the delivery of new systems and applications to the operating forces. However, if not implemented correctly, the transition to a SOA will greatly disrupt operations at the tactical ! and enterprise level, increase costs, and adversely effect combat efficiency.Because SOA is a relatively new concept to the Marine Corps, MCSC personnel do not have depth of knowledge and experience that is available in the commercial sector concerning the governance, development, and operations of a SOA. The focus of this RFI is to identify potential opportunities in partnering that will assist MCSC personnel in implementing SOA. This RFI invites information, ideas, initiatives, and/or processes from all interested entities regarding: Assistance and support is needed in, but not limited to the following:━ The development and implementation of governance standards for a SOA.━ Configuration management of services and data within a SOA.━ Information assurance accreditation of services.━ Identification, development, and quality of services.━ Discoverability and accessibility of services.━ Migration of legacy applications to a SOA.━ Run-time policy and service level management of a SOA.━ Dealing with change and problems unique to implementing a SOA.━ Implementing a SOA in a fluid and disconnected environment typically found at the tactical level.━ Using SOA to span the gap between the enterprise and tactical levels.━ How to transition to a SOA while maintaining the Marine Corps operational uniqueness and without disrupting operations.━ Manpower and training implications of SOA.━ Contracting strategies beyond the traditional prime/sub suppler relationships to minimize barriers to entry to promote innovation. ━ Entrance criteria for SOA-based Technology Insertion/adoption and the SOA-germane definitions of Technology Readiness Levels. ━ Defining services for general purpose application and extensions to satisfy a niche such as for a specific domain. ━ Identification of infrastructure and governance required to implement SOA (what are the prerequisite technologies, data management strategy, and governance).━ Identification of how technology aligns with NCES and NESI.━ The governance of a services oriented architecture within the Marine Corps unique environment.━ The development of a services oriented architecture without disrupting current operations.━ The operations of services oriented architecture within the Marine Corps structure/organization.All information, ideas, initiatives, and/or processes should try to meet to following criteria. ━ Will the information assist the Marine Corps transition to a SOA in a timely and effective manner by 2015?━ Is the information based upon actual experiences within the public and private sectors?━ Is the information focused on process rather than product?━ Will the information give the Marine Corps flexibility to adapt to changing SOA implementations, requirements, and policies within DoD?Please submit responses via email to the Contracting Officer and please limit submissions to less than 3MB. NOTE: THIS NOTICE WAS NOT POSTED TO FEDBIZOPPS ON THE DATE INDICATED IN THE NOTICE ITSELF (02-APR-2008); HOWEVER, IT DID APPEAR IN THE FEDBIZOPPS FTP FEED ON THIS DATE. PLEASE CONTACT fbo.support@gsa.gov REGARDING THIS ISSUE.
- Web Link
-
Link To Document
(https://www.fbo.gov/spg/DON/USMC/M67854/M6785408I2078/listing.html)
- Record
- SN01546289-F 20080404/080403042622 (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 |