SOLICITATION NOTICE
D -- AIR FORCE GLOBAL FORCE MANAGEMENT DATA INITIATIVE
- Notice Date
- 10/16/2009
- Notice Type
- Presolicitation
- Contracting Office
- 201 East Moore Drive,MAFB-Gunter Annex, AL 36114Montgomery, AL
- ZIP Code
- 00000
- Solicitation Number
- R2271
- Point of Contact
- Bobby Perry bobby.perry@gunter.af.mil
- E-Mail Address
-
E-mail the POC
(bobby.perry@gunter.af.mil)
- Small Business Set-Aside
- N/A
- Description
- REQUEST for INFORMATION (RFI)Air Force Global Force ManagementData Initiative (AF GFM-DI) The government is seeking small business contractors that have the ability to provide maintenance and sustainment to support the Air Force GFM DI SIPRNET and NIPRNET organization requirements of Global Force Management Information Exchange Data Model (GFMEIDM) version 3.5, available within the Global Combat Support System (GCSS-AF) infrastructure, and fielded through Defense Information systems Agency (DISA) that is fully developed, fielded, and deployed. This request for information (RFI) is for planning purposes only and shall not be considered as an invitation for bid, request for quote, request for proposal, or as an obligation on the part of the Government to acquire any products or services. Your response t this RFI will be treated as information only. No entitlement to payment of direct or indirect cost or charges by the Government will arise as a result of contractor submission of responses to this announcement or the Government use of such information. This reque! st does not constitute a solicitation for proposal or the authority to enter into negotiations to award a contract. No funds have been authorized, appropriated, or received for this effort. The information may be used by the 554th ELSG/FCR in developing an acquisition strategy and statement of work/statement of objectives and performance specifications. Interested parties are responsible for adequately marking proprietary or competition sensitive information contained in their response. The Government does not intend to award a contract on the basis to this RFI or to pay for the information submitted in response to this RFI. Interested parties should submit a white paper and limit their comments to the areas identified in the "Description of Capabilities" section of this request. Responses to this RFI are not to exceed 10 pages in length. All material submitted in response to this RFI must be unclassified. Responses are to be submitted via email to bobby.perry@gunter!.af.mil by 1600 CST on 02 Nov 2009. This is an information gathering effort only and if further procurement is taken, additional publications will be accomplished as required. Respondents will NOT be notified of any review results. This RFI is only seeking to establish the existence of small business with capabilities and interest in providing support. 1. Background In summary, this includes a through description of the Unclassified Organizational Server that makes force structure data available for integration and use by other programs of record that use force structure data, and all the Architectural Views of GFM. Procedurally speaking, the Unclassified Org Server data is passed to the Classified Organizational Servers and augments the classified force structure data that includes the Combatant Commander (COCOM) command relationships used to document the force assignment process. The force structure data includes specifications and authorizations for personnel and equipment as well as unit identification data. Additional pertinent background information for this task is provided at the Joint URL https://www.intelink.gov/wiki/Global_Force_Management_Data_Initiative/CCB#Operational_Baseline_v1.1. GFM Capability Development Document, Technical Specifications, Operational Baselines, Overviews, CONOPS, and Implementation Plans can be fou! nd there. 2. System Overview The Air Force Global Force Management Data Initiative (GFM DI), enables Defense Readiness Reporting System/Global Visibility Capability, Adaptive Planning, Defense Integrated Military Human Resource System, and Standard Financial Information Structure to integrate organizational and force structure data across the Department of Defense. The end goal of the GFM DI is to integrate the three force management processes (assignment, allocation and apportionment), and ensure the data is available to meet the needs of all users, systems and functions. This task is the sustainment, maintenance and modification of the current classified and unclassified AF GFM DI that includes implementation of the Global Force Management Information Exchange Data Model, (GFMIEDM), 3.5 changes. The Global Force Management Information Exchange Data Model (GFMIEDM) is the information exchange specification that supports data integration within and among the Services' Organizational Servers (each branc! h of the Service has an Organizational Server), and provides information to external systems. Further, to enable data integration and de-confliction across the Org Servers, and provide utility for applications outside the Org Servers, the tagging of all authorized force structure data with unambiguous, unique identifiers is a necessity. Force Management Identifiers (FMIDS), serve this function for all data within the GFMIEDM, and thus all data within the Org Servers (including organizations, materiel authorizations, personnel authorizations, and relationships and associations between these entities). The GFMIEDM version 3.5 contains 46 different entities that cover the minimum essential force structure data understood as necessary to fulfill Global Force Management. The inter-relational generalized hierarchy of the data specification provides for the unique identification of all GFMIEDM data with a set of FMIDS comprising twelve attributes. Note: GFMIEDM found at the URL h! ttps://www.intelink.gov/wiki/Global_Force_Management_Data_Initiative/CCB#Operational_Baseline_v1.1. 2.1 A major deficiency in data sharing across the enterprise is the lack of a common reference standard across information technology domains and business processes. A basic premise of GFM DI is that force structure is the common element between almost all DOD warfighting and business systems and that the development of a methodology to create an authoritative data source for authorized force structure will provide the means to accomplish GFM objectives. The Department established GFM DI to fill gaps in the capability to provide visibility of the entire force structure as a function of time: past, present, and future. The three components of the GFM Data Strategy include documenting the authorized force structure for all organizations, uniquely identifying force structure data elements, and disseminating the force structure data for use throughout the Department. Key elements in implementing GFM DI include identifying authorization data, establishing an organizational hierarchy to build a single force structure, developing an information exchange model to provide standard formats, and establishing requirements for GFM Organization Servers that will become the authoritative data sources for force structure authorization data. The mission of the AF GFM-DI is to support the warfighter by providing timely, reliable, and authoritative force management data in a net-centric environment. This data may be used to enhance the situat! ional awareness of decision-makers and other authorized users and to facilitate a more rapid and accurate means of assessing risks, planning courses of action, and executing objectives. 2.2 Joint Programming Guidance VII, dated 9 June 2006, directed the GFM DI to proceed in two phases - defined by the General Officer Steering Committee as Task One and Task Two. The impetus for implementing a comprehensive GFM Data Strategy (GFM DS) is that currently the assignment, allocation, and apportionment processes are not integrated; the data necessary to support such integration is not visible, accessible, or usable; and there is no single, authoritative data source (ADS) for force structure data that meets the needs of all users, systems, or functions. The force structure data created by the GFM DI lays the foundation for integrating these three force management processes. 2.3 The objective of GFM DI is to integrate information from disparate applications and present it as though it came from a single source. The JOpsC family of future capabilities, especially the joint functional and integrating areas of Force Management, Command and Control, Net-Centric, and Focused Logistics, are reliant upon the success of GFM DI to resolve much of what the Joint Operation Planning and Execution System effort identifies as the friction and inefficiency of the Department's force management capability. GFM DI implementation is also a requirement for achieving Total Force Visibility. 2.4 There were three principal and integrated actions required to transform the effectiveness of GFM DI that have been completed in Task One work in Fiscal Years 2007 - 2009. First, the development of an Organizational Force Structure Construct (OFSC): a hierarchical framework of universal rules expressed in mathematical terms by which force structure data may be organized, electronically documented, and exploited by software programs. Second, the Global Force Management Information Exchange Data Model, (GFMIEDM), is based on a Joint standard that was developed to capture force structure data in a common persistent format. It captures the minimum essential data elements required for the electronic documentation of authorized force structure while permitting future linkages to a distributed network of databases where personnel, materiel, readiness, deployed location, and other data may be linked with the force structure authorizations and then integrated in a classified en! vironment. Finally, the tagging of force structure data across the DOD with standardized, unambiguous identifiers, (known as Force Management Identifiers (FMIDS), and marking each data asset with metadata tags in Extensible Markup Language (XML), promotes the efficacy of discovery services. 3. Description of Capabilities 3.1 The contractor shall perform all system administrator duties necessary to sustain and maintain both the unclassified and classified GFM DI. Database maintenance and upkeep is required for both TeraData and Oracle. The contractor will provide content management, Tivoli Access Management, and error resolution for the currently deployed SIPR version of GFM DI. This includes maintaining the GFM COCOM/Forces For GUI link on the GCSS AF Portal, however the PMO will retain authority to approve/disapprove use based upon individual's need to know and security clearances. The contractor shall provide technical analysis and plans for any GCSS-AF Service upgrades necessary for GFM DI to remain functional and satisfy feeder ADS logistics systems and communications requirements. The contractor shall submit Engineering Change Proposals (ECPs) for this requirement as the documentation by which the change is described and suggested. 3.2 The contractor shall perform maintenance to include minor bug fixes within the scope of GCSS Data Services, and those normally performed on an annual basis for logistics systems within the same suite of GCSS Data Services. 3.3. The contractor shall implement a GFM application robust data management capability to include automated metadata management, data quality metrics and changed data capture using the AF IDQM solution structure. 3.4 The contractor shall ensure data consistency between NIPRNET and SIPRNET environments by verifying the transfer of data files from existing authorized data sources, transfer between unclassified and classified databases and success of transfer to the Joint Organizational server on a daily basis Monday - Friday, and as requested after normal duty hours and on weekends. 3.5 The contractor shall maintain the latest version of iChart and provide liaison with the Joint Staff (J8) to conduct tests and provide data verification at least bi-monthly. The contractor shall attend via telcon and VTC monthly Organizational Server and Planning Working Group Meetings and produce weekly meeting status reports that include any action items for the Air Force from these meetings. The contractor shall use both iChart and the upgraded Tree Viewer tool to conduct testing and validation of AF GFM. 3.6 The contractor shall deliver to the GFM PMO (via email) a weekly program management status report to include issues, successes, risks and mitigation plans. The contractor shall participate in program management meetings every week via telecon to ensure cost, schedule and performance targets are met. At a minimum, in this meeting the contractor shall provide updates to the weekly status report and include metrics and any substantial schedule changes. The contractor shall use a standard risk tool, compatible with RISK RADAR, to monitor risk and provide risk reports to the PMO, with the first report being due 30 days after contract award. 3.7 The contractor shall participate via telecon in the monthly Force Management Integration Project and GFM Policy Integration and Planning (PIPWG) meetings for the purpose of providing technical information relating to GFM DI and the potential interchange of data. 3.8 The contractor shall update the registration of services, WSDLs, and related data in the DoD MetaData Registry and the NCES Service Registry at least quarterly as required for GFM DI. This includes the updating of both the classified and unclassified WSDLs as directed by the SAF/XC customer to maintain the interface with the Joint Organizational Server. 3.9 The contractor shall provide security accreditation support to maintain the current accreditation. The contractor shall provide security accreditation support for new work added under this task order. This includes updated DoDAF views, and providing data for answering all appropriate questions in the Enterprise Information Technology Data Repository (EITDR) related to design, security, interfaces, and controls. 3.10 The contractor shall maintain a development sandbox within GCSS Data services for the purpose of conducting testing as required for system maintenance, bug fixes, and any enhancements added to the system by task orders. This environment must emulate both the unclassified and classified actual system environment. The contractor shall be responsible for the update and maintenance of the environment. GCSS-AF Data Services shall be responsible for providing environment infrastructure components and support. 3.11. The contractor shall fully participate with the Capabilities Integration Environment, following all procedures outlined in the 554th ELSW System Engineering Process for testing GFM DI and test according to the test practices of the Wing Test Office (WTO) and in conjunction with the WTO. The contractor shall fully comply with the GFM Test Plan. This includes conducting a full Component Validation and Integration test in the Capabilities Integration Environment, Development Zone. The contractor shall provide a test client application that will completely support all test cases and will also deliver the latest version of IChart, both for use in verifying data in the testing environments and for Joint Staff Peer Reviews. 3.12 The contractor shall provide an Integrated Master Schedule (IMS) that is fully resource loaded and is in complete compliance with the 554th ELSW System Engineering Process. This IMS shall be updated and provided to the PMO monthly to track progress on all tasks both contractor and government. Labor hours shall be documented and earned value shall be calculated. Within 30 days of task award, the contractor shall provide the first delivery of the entire updated Project IMS. 554 ELSW guidelines for producing a schedule are available in the Wing SEP. The URL is http://public.gunter.af.mil/applications/sep/menus/Main.aspx. Further, the contractor shall deliver a schedule documenting all planned activities as part of their proposal and including all "System Gates" outlined in the Wing Enterprise Schedule. Examples of "System Gates" include; Preliminary Design Review, Critical Design Review, Test Readiness Reviews, and Field Readiness Reviews. The contractor shall notify t! he GFM PMO in the event of changes to their development schedule. 3.13 The contractor shall produce all documentation necessary to communicate that the requirements are satisfied, the allocation to component elements in the solution design, and a method for verifying and validating requirements satisfaction. At a minimum, the contractor shall develop the following systems engineering documentation: a Software Development Plan, Requirements Specification, Design Specification, Requirements Traceability Matrix (RTM), and Test Plan. 554 ELSW guidelines for producing such documents are available in the Wing SEP. 3.14 The contractor shall participate in all Integrated Test Team meetings and provide technical advice and analysis. The contractor shall prepare all required briefing slides for the following reviews; Preliminary Design Review, Critical Design Review, Component Validation and Integration Review, Test Readiness Reviews, and Field Readiness Reviews. 3.15 The contactor shall participate in all GCSS-AF Outreach meetings and provide artifacts, and technical advice as necessary to move GFM DI though the Inception, Development, and Deployment phases and into full production. This includes providing updates to all required GCSS-AF Work Plans. 3.16 The contractor shall participate in all GFM Outreach meetings and provide artifacts, and technical advice as necessary to support the GFM goals of increased adoption in the greater Air Force community. 3.17 The contractor shall provide technical analysis and plans for any GCSS-AF Service upgrades necessary for GFM DI to remain functional and satisfy feeder ADS logistics systems and communications requirements. The contractor shall submit Engineering Change Proposals (ECPs) for this requirement as the documentation by which the change is described and suggested. 3.18 The contractor shall maintain the standard Java 2 Platform Enterprise Edition (J2EE) web application GUI utilized to support user interaction with the COCOM links and provide two updates, modifications for testing screens and demonstration purposes. The contractor shall provide a recommended approach for improving the COCOM GUI interface leveraging existing enterprise components (such as the RIA framework). 3.19 The contractor shall provide a Quality Control Plan that satisfied the standards of ISO (International Organization for Standardization) 9126: Information Technology/Software Evaluation - Quality Characteristics and Guidelines for their Use, 1991 and the 554 ELSG Wing SEP. 3.20 The contractor shall propose a standard set of metrics within 30 days of contract award to be delivered monthly to the Government. 3.21 The contractor shall provide a Software Development Plan within 30 days of contract award. MIL-STD-498 requires the developer to define and apply software management indicators and provide a set of candidate management indicators to serve as a starting point. It is left up to the developer to propose in the Software Development Plan (SDP) the indicators to be used, the data to be collected, and the approach to interpreting the data, and the reporting approach. 3.22 The contractor shall provide complete test cases, test scripts, and all documentation necessary for all phases of testing according to the Wing SEP and Wing Test Procedures. 3.23 The contractor shall enter all required test data into the Wing Test Tool, Quality Center. 3.24 The contractor shall modify the current GFMIEDM to comply with the specifications of the GFMIEDM 3.5. See the GFM URL referenced in the above paragraphs for the web link. 3.25 The contractor shall modify the current GFM to use the current Enterprise Data Quality Management Service (EDQMS) framework for GFM 3.26 The contractor shall provide analysis and modify the current GFM to implement an MPES long-term automated feed solution 3.27 The contractor shall modify the current GFM to implement automated data synchronization, see paragraph 5.4 requirement definition. 3.28 The contractor shall modify the current GFM Informatica BTEQ conversion to GCSS-AF Data Services Informatica standards 3.29 The contractor shall modify the current GFM to COCOM GUI/Forces For conversion to Rich Internet Application (RIA). The contractor shall conform to current standards for the Chief of Staff Dashboard, including the use of Adobe Flex as the tool for RIA. 3.30 The contractor shall present as a separately priced option for the "Dashboarding of GFM". This contract option could be exercised in either the first or second year of the contract. Currently only machine to machine interfaces (web services) are planned for GFM, which means the AF GFM Organization Server lacks the capability to be easily human readable and useable. The option is to add a user interface through an upgrade. The current GFM Data Viewer Graphical User Interface that is in use for demonstrations shall be enhanced and formatted to deploy and run on the SIPR Air Force Portal, as a Rich Internet Application. This would give any MAJCOM or authorized user the capabilities to access information in GFM for war planning, war gaming, or OPLAN development. The technical effort consists of executing the following tasks: modify the GFM Data Viewer to display all Force Structure, add user defined searches to the data viewer, build service layer for retrieving authorize! d, on-hand, and readiness data, extract on-hand weapons data from LIMS data mart, extend GFM extract process to include new on-hand weapons data, modify current GFM SIPR import process to include new on-hand weapons data, create additional data structures on SIPR to contain new on-hand data, build the GFM Dashboard Leadership View for deployable material. In general the "touch and feel" of the GFM Dashboard should mirror the Chief of Staff Dashboard which utilizes the tool Adobe Flex. 3.31 The contractor shall deliver a general set of deliverables, e.g. Progress reports, Funding reports, schedules, documents, and documented research, IAW the CDRLs outlined. The contractor shall make delivery of the required software as specified in the IMS. 4. Special Requirements: 4.1 Data Rights. The government shall have unlimited rights to all deliverables developed under this contract. 5. Government Furnished Material 5.1 The government will furnish office space and computing equipment for contractor personnel on-site at WPAFB AFB or Maxwell AFB Gunter Annex for personnel on this project. Computing equipment will have network access to the GCSS-AF Data Services production environment. 5.2 The government will furnish access to the GCSS-AF Data Services production environment for use in maintenance of the contractor development environment. 5.3 The government will furnish access to the GCSS-AF CIE Development Zone for the contractor. Limited support from CIE engineers will be available for system administration type activities. Access to CIE capabilities will be available via secure connection from the web. 5.4 The Government will furnish all documentation associated with the last previous development activities (e.g. maintenance releases). Such documentation shall consist of GCSS-AF work plans, Requirements Specifications, Design Specifications, Test Specifications, and Deployment Artifacts applicable to the in-process development activity and will be available from the GFM CoP web site. 6. Security 6.1 Contractor personnel using unclassified automated information systems, including e-mail, must have at a minimum, a completed favorable National Agency Check (NAC)/Entrance National Agency Check in accordance with DOD 5200.2-R Personnel Security Program, January 1987. The contractor is required to complete the application and apply for a NAC, for any employee not currently having a NAC, upon receipt of a task order where the employee will have access to automated information systems. The contractor shall diligently pursue obtaining NACs for its employees. No contractor personnel will be permitted access to any Government computer system, including E-mail, until the NAC forms have been completed and furnished to the appropriate Government Security Officer. Contractor personnel performing content management and work on the SIPR environment must have a Secret Security Clearance. 6.2 Due to the nature of the work, work may only be performed by US citizens. The contractor is responsible for ensuring protection of government information it handles.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/USAF/AFMC/ESC/R2271/listing.html)
- Record
- SN01986812-W 20091018/091016234739-22ce08c488315122c9d1eacab104cf08 (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 |