MODIFICATION
D -- F-16 Electronic Technical Order Viewer / Content Management Solution for USAF, EPAF, and FMS Air Forces
- Notice Date
- 5/25/2010
- Notice Type
- Modification/Amendment
- NAICS
- 541511
— Custom Computer Programming Services
- Contracting Office
- Department of the Air Force, Air Force Materiel Command, Hill AFB OO-ALC, OO-ALC/PKXB, 6038 Aspen Ave (Bldg 1289), Hill AFB, Utah, 84056
- ZIP Code
- 84056
- Solicitation Number
- FA8232-10-R-0022
- Archive Date
- 6/19/2010
- Point of Contact
- Dawn A. Schmidt, Phone: 8015863442
- E-Mail Address
-
dawn.schmidt@hill.af.mil
(dawn.schmidt@hill.af.mil)
- Small Business Set-Aside
- N/A
- Description
- This announcement constitutes a 3-fold purpose: 1) Obtain Sources Sought/Request for Information (RFI) feedback from potential vendors for market research, 2) Rough Order of Magnitude (ROM) with basis of estimates (BOEs) to use for planning purposes for cost and schedule estimates, and 3) Announcement of Informal Capabilities Briefing / Demonstration to be held 14-15 July 2010 at Hill AFB UT for interested vendors to demonstrate their viewer / content management solutions. This is not a Request for Proposal (RFP) or an Invitation for Bid (IFB), nor is it to be construed as a commitment by the Government. The following information is provided to identify potential contractors who have the skills, experience and knowledge required to successfully provide the described capability. The 508th Aircraft Sustainment Group, Hill AFB UT, intends to award a 1-year basic period contract with four 1-year option periods to support the F-16 Electronic Technical Order (ETO) Viewing Solution Project necessary to support the effort required for the analysis, design, engineering development, testing, training, help desk support, deployment planning, and sustainment of the F-16 ETO Viewing Solution. It includes the associated program management and logistic support requirements. 1. The F-16 ETO Viewing Solution project is being initiated to field a capability for viewing F-16 Technical Orders for United States Air Force (USAF), European Participating Air Forces (EPAF) and Foreign Military Sales (FMS) using Air Force SGML Technical Orders (TOs) in USAF approved formats using a standard web browser (e.g. Internet Explorer) while utilizing connected and non connected mode network environments. The F-16 ETO Viewing Solution effort includes the following: • Implement requirements identified in this notice • Establish training programs and conduct training • Perform sustainment, deployment, and implementation support • Provide F-16 ETO Viewing Solution COTS Software maintenance and sustainment (if required) 2. Applicable Documents 2.1. Department of Defense Specifications • MIL-STD-38784 App B General Style & Format (Tri-Service) • MIL-PRF-38807 Illustrated Parts Breakdown (IPB) • MIL-PRF-83495 App A General Equipment • MIL-PRF-83495 App B General Systems • MIL-PRF-83495 App C Job Guide • MIL-PRF-83495 App D Fault Reporting • MIL-PRF-83495 App E Fault Isolation • MIL-PRF-5096 App A Inspection Manual • MIL-PRF-5096 App B Functional CF Manual • MIL-PRF-5096 App C Functional CF Checklist • MIL-PRF -5096 App D Work Cards • MIL-PRF-8031 LOAPS • MIL-PRF-87929 App E Corrosion Control • MIL-PRF-87929 App F Non-Destructive Inspection • MIL-PRF-87929 App G Aircraft Structural Integrity Program • MIL-PRF-5096 App F Checklists • MIL-PRF-5920 App A Sample Basic Weight Checklists • MIL-PRF-5920 App B Loading Data Manual • MIL-PRF-9854 Structural Repair • MIL-PRF-9977 App C Nonnuclear Munitions Basic Information (Standard Volume) • MIL-PRF-9977 App D Nonnuclear Munitions Loading Procedures Manual • MIL-PRF-9977 App E Integrated Combat Turnaround Procedures Manual • MIL-PRF-9977 App G Loading Procedure Checklists • MIL-PRF-9977 App H Integrated Combat Turnaround Procedures Checklists • MIL-PRF-38384 App A Nonnuclear Weapon Delivery Manual • MIL-PRF-38769 WUC • MIL-PRF-83495 App E Fault Isolation • MIL-PRF -7700 App A Flight Manuals • MIL-PRF-7700 App B Supplemental Flight Manuals MIL-PRF-7700 App C Abbreviated Flight Crew Checklist 2.2 Department of Defense Standards MIL-STD- 38784 General Style & Format 38784 General Style & Format 2.3 Availability of DoD Documents unless otherwise indicated, copies of specifications, standards, and handbooks listed above are available upon request. 2.4 Government Documents • AFI 33-202, Network and Computer Security • AFMAN 33-223, Identification and Authentication • AFRIMS, Records Disposition Schedule • AFI 33-201, Communications Security FIPS 140-2, Security Requirements for Cryptographic Modules 3 REQUIREMENTS. 3.1 General • Once contract is awarded, the work required shall be performed in accordance with applicable Performance Work Statement (PWS). • The contractor shall analyze requirements, design, develop, code, and test the software to support requirements listed and in accordance with the detailed requirements in paragraph 3.2.1 below. • The contractor shall provide program management, and logistic support in accordance with the detailed requirements in paragraph 3.2.3 below. • The contractor shall provide planning and support for the 501st ACSS/GFLC deployment of the F-16 ETO Viewing Solution to various operational locations in accordance with the detailed requirements in paragraph 3.2.4 below. 3.2 Detail Tasks. In the following paragraphs, references to the F-16 ETO viewing solution will refer to all of the components of the F-16 ETO Viewing Solution software (Publisher, Administrative Tool, Viewing Services, and the Connected & Non Connected Mode Viewing Client) that are developed for 501ST ACSS/GFLC under this project. Exceptions to this statement will be noted explicitly. 3.2.1 Requirements Analysis 3.2.1.1 Requirements Identification The contractor shall evaluate the requirements identified for consistency, testability, and feasibility. The contractor shall provide minimum hardware and software requirements to support F-16 ETO Administrative Tools, Publishing, Viewing solutions. 3.2.2 Design, develop, code, and test. Beta Testing shall include EPAF and FMS. 3.2.2.1. Design, develop and code. 3.2.2.1.1 Additional Functionality: The contractor shall design, develop, and code the functionality identified in Appendix A. The contractor shall ensure the functionality and performance provided in Appendix A supports the addition of future functionality that may be identified at a later date. 3.2.2.1.2 F•16 ETO Software Compliance The contractor shall design, develop and code the F-16 ETO Viewing Solution software to be compliant and provide future compatibility with the following operating system: 1. Microsoft Windows XP 2. Microsoft Windows Server 2003 3. Microsoft Windows 7.0 4. Microsoft Windows Vista 5. Internet Explorer 6 and higher 6. All Air Force approved operating system patches and updates 7. All Air Force current/approved versions of desktop applications including Microsoft Office 2003, Norton Antivirus, PKI software, security database, Winzip, Adobe Acrobat. 8. Internet Protocol v6 (and emerging) protocols when used in the residing operating system 9. Supporting Network protocols used in a Local Area Network (LAN) and Wide Area Network (WAN) environment. The desired protocol is TCP/IP. 3.2.2.1.3 TRAINING Training methodology will be "Train the Trainer". The contractor will develop a training program if selected by customers. The training program will include End User (Flightline) training curriculum for using all viewer navigation, viewing annotation and help functionality. The training program will also include T.O. management training focused on Tech Order Distribution Office utilizing help functions and an introduction to importing or updating tech data using integrated software packages or alternate processes. 3.2.2.1.4 F-16 ETO Corrections The contractor shall, by direction of the F-16 Digital Data Configuration Control Board (CCB), incorporate any corrections to deficiencies as identified throughout the period of performance of this delivery order. This shall include any updates/revisions to the COTS/GOTS products incorporated for the F -16 ETO Viewing solution. 3.2.2.1.5 F-16 ETO Executable Formats The viewing solution (to include the capability to publish, manage, update, and view ETO data) shall be in an executable format accompanied by documented installation instructions and applicable configuration instructions. 501ST ACSS/GFLC will have the right to reproduce or distribute, within the limitations of the COTS licenses. 3.2.2.1.6 Style Sheets The contractor shall provide style sheets to support each of the listed TO types identified in the Technical Manual Specifications and Standards (TMSS) list provided in Section 2.1 and 2.2 of this SOW. As a minimum, Version 6.n of all document type definitions (DTDs) to be supported by the F-16 ETO Viewing Solution shall be considered the baseline, with backward compatibility through Version 6. Any style sheet changes made to support changes/updates/patches made to subsequent to the delivery and acceptance shall be included in the F -16 ETO Viewing solution. 3.2.2.2 CDRL documentation The contractor shall provide all documentation in contractor format. 3.2.2.3 Tagging guidelines The contractor shall determine and document guidelines for the tagging of SGML TO instances to ensure appropriate rendering of the TO instance within the F -16 ETO. Guidelines shall include recommended tagging of SGML for proper display on all device sizes, excluding devices with a screen size less than 3 inches in length or width, for systems running the operating systems identified in 3.2.2.1.2. The contractor shall update tagging guidelines delivered for the duration of this delivery order. 3.2.2.4 Training and on-line documentation The contractor shall develop and update training guide/training curricula and supporting materials suitable for training Air Force users in the use of the F-16 ETO for installation, publishing, administering, updating, and viewing. Training shall cover all aspects of the F-16 ETO Viewing Solution publishing necessary for the successful translation of an SGML instance into XML and how to use the viewing/navigation features of the Viewer and administrative features of the Administrative Tool. The contractor shall produce on-line help files from the training guide/training curricula and perform a post-conversion clean-up of the on¬line help files. The contractor shall provide detailed installation guides which comprehensively describe the steps necessary to install and manage the F-16 ETO Viewing Solution. 3.2.2.5 Test and evaluation The contractor shall conduct testing of the F-16 ETO Viewing Solution to ensure it complies with all requirements as set forth in this SOW. Testing shall be performed to ensure the F-16 ETO Viewing Solution is stable and no mission-critical deficiencies exist. The tests shall be conducted in accordance with the developmental test plan developed by the contractor and approved by 00¬ALCIYPVP. The Contractor shall document the results of the tests in a development test report to be delivered to 501ST ACSS/GFLC. 501ST ACSS/GFLC participation/witnessing of the Contractor testing will be at 501ST ACSS/GFLC's discretion. All defects found during contractor testing shall be repaired prior to release. 3.2.2.6 System Administration The contractor shall provide a system administration guide which will provide comprehensive instructions for: Repair, reinstall, troubleshoot, and manage user permissions; Installation, configuration and maintenance of the software; Import, Export and Maintenance of the TO repository 3.2.2.7 F-16 ETO Viewing Solution Delivery The contractor shall deliver the F-16 ETO viewing solution on CD storage media to 501ST ACSS/GFLC for testing purposes prior to acceptance. Upon delivery of the F¬16 ETO Viewing Solution, 501ST ACSS/GFLC and EPAF/FMS representatives will validate/test all requirements, and process instances through the F -16 ETO publisher and viewer in a connected & non connected mode to determine F-16 ETO Viewing Solution's compliance with all the F -16 ETO Viewing Solution requirements. Deficiencies observed during testing shall be corrected within 30 days and the modified F -16 ETO Viewing Solution CD storage media shall be provided to 501ST ACSS/GFLC. Contractor shall support 501ST ACSS/GFLC testing/evaluation of the F-16 ETO at LM Aero Technical Publications facility in Fort Worth, TX or at Hill AFB, UT. 3.2.3 Program Management and Logistic Support 3.2.3.1 Program Management The contractor shall provide all necessary management controls and oversight to ensure the successful development and fielding of the viewing solution (to include both client and server installations). The Contractor shall develop an Integrated Master Schedule for the F-16 ETO Viewing Solution project. The Contractor shall provide bi-weekly status reports on each task identified in the Integrated Master Schedule. The Contractor shall provide on a monthly basis a funds and expenditure man-hour report. The Contractor shall provide a preliminary version of the schedule at the kickoff meeting and an Integrated Master Schedule 45 days after contract award. The contractor shall provide technical and management support (as requested by 501ST ACSS/GFLC, to include attendance at technical interchange meetings with various EPAF/FMS customers in conferences where the F-16 ETO Viewing Solution will be briefed or demonstrated, meeting with and resolving problems/concerns relative to the F-16 ETO Viewing Solution, and performing testing in the support of problem resolution. The contractor shall record the deliberations and actions resulting from the conference. The recorded minutes shall be subject to Government approval. The selected vendor will comply with all ITARS requirements via Technical Assistance Agreement or ITARS exemptions to participate in technical discussions associated with the viewer. 3.2.3.2 Kickoff Meeting The contractor shall conduct a Kickoff Meeting 14 days after award of the contract. The following items will be discussed at the Kickoff Meeting. • Statement of Work • Software Development Process • Quality Assurance Process • Traceability matrix tie-in of requirements to SOW tasks • Preliminary design of each requirement not supported in current solution. • Schedule • Deliverables • Status Meetings and Reporting • The contractor shall record the deliberations and actions resulting from the conference. The recorded minutes shall be subject to Government approval. Reviews shall be conducted at the contractor facility. Kickoff Meeting will be scheduled for I day. 3.2.3.3 Technical Interchange Meetings The contractor and the ITOD IPT shall participate in TIM's with 501ST ACSS/GFLC. TIM's will be combined with other reviews whenever possible. TIM's can be convened upon either LM Aero or Government request. Advance notice and topics for each TIM shall be given prior to each meeting. This advance notice can be waived by mutual agreement between LM Aero and the Government. The contractor shall document in the meeting minutes significant events, results, and action items. 3.2.3.4 Quality Assurance The contractor shall implement a quality assurance process to ensure the project adheres to the contractor's internal quality procedures and standards. The contractor shall conduct reviews and audits to ensure the accuracy, completeness, and timeliness of all project deliverables. 3.2.3.5 Configuration Management The contractor shall develop a configuration management plan to track and control the configuration of the F-16 ETO Viewing Solution software as it is developed and deployed. 3.2.3.6 Help Desk support The contractor shall provide Level II-III help desk support for resolving and tracking technical issues and problems for one year after delivery. Contractor shall identify the cause of problems encountered by users, develop solutions, and guide the user through final resolution of the problem. The FMS and EPAF customers will identify problems to 501ST ACSS/GFLC who will in-turn forward the problems to the contractors help desk. The contractor will reply to 501ST ACSS/GFLC who will in turn reply to the customer. 3.2.4 Deployment 3.2.4.1 Deployment planning The contractor shall develop a generic approach for deploying F-16 ETO Viewing Solution to any FMS and EPAF Air Force location. Deployment approach shall consider all elements bearing upon the deployment and use of the F-16 ETO Viewing Solution to include client-server configuration and location, hardware and software recommended requirements, and support needed. 3.2.4.2.1. Deployment support The contractor shall upon successful government acceptance of the F-16 ETO Viewing Solution software, assist, as required, the deployment F-16 ETO Viewing Solution via telephone standby. 3.2.5 F-16 ETO Sustainment The contractor shall provide sustainment of all the F-16 ETO Viewing Solution software, style sheets, scripts and translation software throughout the period of performance of this delivery order. The F-16 Digital Data Configuration Control Board (CCB) will be the final approval authority for all F-16 ETO Viewing Solution sustainment actions. The CCB will be chaired by USAF personnel and supported by EPAF and FMS representatives. 3.2.5.1 Viewer Style Sheets (VSS). The contractor shall sustain the VSS to support the listed TO types identified in the Technical Manual Specifications and Standards list provided in Section 2.1 and 2.2 of this SOW based on Software Problem Reports (SPRs) generated by the user and categorized by the F-16 Digital Data CCB. The VSS will support Version 6.n of the Document Type Definitions (DTDs) listed above and shall be backwards compatible through DTD V6. The style sheets shall be sustained according to the document type definition (DID) provided for each document type and shall be in compliance with each specification identified. The VSS shall be updated to the latest version of F-16 ETO Viewing Solution fielded as a Block Cycle Update. 3.2.5.2 Deficiency SPR: The contractor shall sustain the F-16 ETO Viewing Solution software based on SPRs generated by the user and categorized by the F-16 Digital Data CCB. The support shall include debugging any problems with functionality or style sheets discovered in the viewing solution. Software patches as a result of an approved SPR shall be updated to the existing version of F-16 ETO Viewing Solution fielded as a Block Cycle Update. 3.2.5.3 Enhancement SPR: The contractor shall sustain the F-16 ETO Viewing Solution software based on SPRs generated by the user and categorized by the F-16 ITOD CCB. Any SPR's identified by the contractor as enhancements shall be categorized and approved by the CCB as enhancements. 501ST ACSS/GFLC may request the contractor to provide a ROM on the enhancement( s) and to implement a solution for each enhancement approved by the CCB. 3.2.5.4 F-16 ETO COTS software upgrades: F-16 ETO Viewing Solution software shall be evaluated against new COTS patches and updates, if required, to ensure F-16 ETO Viewing Solution continues to meet functional and performance requirements without degradation. All COTS patches and upgrades will be evaluated by the CCB prior to incorporation. 3.2.5.5 On line Help: The contractor shall sustain the On-line Help for the Publisher, Viewing Client, Viewer Services and Administrative Tool based on SPRs generated by the user and categorized by the F -16 ITOD CCB. On line help files shall be updated to the existing version ofF-16 ETO Viewing Solution fielded as a Block Cycle Update. The contractor shall repair any discrepancies found in the online help files after the conversion of the word documents into the online help files. 3.2.6 Performance: The contractor shall ensure the F-16 ETO Viewing Solution supports 500 concurrent users with simultaneous access to no less than 1000 T.O.s. 3.2.7 COTS Software maintenance/ licenses The contractor shall recommend software support plan for the continuation of development and deployment efforts for any Commercial Off the Shelf software required to operate the F-16 ETO Viewing Solution. 4. GOVERNMENT ACCEPTANCE 4.1. Viewing Solution All components of the viewing solution shall comply with the requirements contained herein and shall contain at a minimum, the functionality and look and feel requirements defined in the F-16 ETO Viewing Solution Requirements specification. The viewing solution shall have been thoroughly tested by the contractor and demonstrated to be stable during operation, free of defects, and suitable for operational use by the USAF/EPAF/FMS Air Forces prior to release. 4.2. Style Sheets The criteria for acceptance shall be based upon successful completion of the style sheets in accordance with the Technical Manual Specifications and Standards (TMSS) identified in paragraph 2.1 of this SOW. The style sheets shall comply with the Document Type Definition (DTD) associated with each TMSS contained herein. 4.3. Acceptance and Correction The government will review all deliverable documentation within 5 business days of delivery and retain the option to accept or reject the deliverables and notify the contractor of such. In the event of rejection of any deliverable, the contractor shall be notified in writing of the specific reason why the deliverable is being rejected. The contractor shall have 15 working days to correct the rejected deliverable and return it to the government. If additional time is required by the contractor to correct deficiencies, the contractor shall request an extension in writing. 5.0 TRAVEL The contractor shall provide a ROM for travel on a cost reimbursable basis. Below is an estimate of the travel required. Destination Nr Trips Nr Days Nr Travelers Ft Worth, TX (IPT MTG) 4 2 2 Various CONUS Sites (Deploy) 2 5 2 Various sites for conferences 2 5 2 6.0 PERIOD OF PERFORMANCE The period of performance for will be a base period of 12 months after contract award followed by 4, twelve-month option periods. 7.0 Deliverables CDRL Deliverable Title SOW Task # Desired Delivery Date A002 F-16 ETO System Admin Guide 3.2.2.6 3 months after exercise of option A003 F-16 ETO Install Disks 3.2.2.7 Contract award A004 F-16 ETO Tagging Guidelines 3.2.2.3 Contract award A005 F-16 ETO Training Curricula 3.2.2.4 3 months after exercise of option A006 F-16 ETO Installation & Training Guide 3.2.2.4 3 months after exercise of option A007 F-16 ETO Development Test Plan 3.2.2.5 30 days prior test A008 F-16 ETO Development Test Report 3.2.2.5 30 days after test A009 F-16 ETO Integrated Master Schedule 3.2.3.1 Draft - 14 days after contract award. Final - 45 days after contract award A010 F-16 ETO Monthly Status Report 3.2.3.1 Monthly A011 F-16 ETO Deployment Plan 3.2.4.1 Draft - 45 days after contract award. Final - 75 days after contract award A012 Funds Expenditure Report 3.2.3.1 Monthly A013 Meeting Minutes 3.2.3 Within 5 business days after each review A014 F-16 ETO Quality Assurance Plan 3.2.3.4 30 days after contract award A015 F-16 ETO Configuration Management Plan 3.2.3.5 30 days after contract award A016 F-16 ETO Software Configuration Evaluation 3.2.3.5 30 days prior to end of contract option 8. Capability: For each of the following elements listed in paragraph 8.1. - 8.9., provide comments to address the following: - Standard Capability - Customization Required - Unable to Provide Capability - Date Available 8.1. NAVIGATION 8.1.1. History of Traversed Links: Ability to view previously identified navigation path in a session with the ability to hyperlink back to any of those previous paths 8.1.2. Logical Next and Back: Ability to navigate through logical next and back functionality. i.e. next page, next task, functions like turning pages in a book 8.1.3. System/Subsystem Navigation: Ability to drill down through table of contents from a top level breakdown to lowest level individual tasks from a single pane. Table of contents is compressed when initially opens, +/-or other type icons indicate more data available if desired 8.1.4. User Creation of Bookmarks: Ability to bookmark system or subsystem tasks within a data set with user ability to define as temporary or permanent bookmarks 8.1.5. Viewer Navigation Pane: As a minimum, the navigation pane shall include tabs to rapidly access the following data, Emergency Procedures, Table of Contents (TOC), List of Tables (LOT), List of Figures (LOF) and will include Foldout ordering, List of Changes (LOC) (when required by AF TMSS). 8.1.6. Search Across Multiple T.O.'s: Non-Connected Mode -For data search across T.O.'s only and includes Boolean searches on the client device. 8.1.7. Search Across Multiple T.O.'s: Connected Mode -when connected to a server search multiple T.O's on the client and the server device with a single search. 8.2. LINKING 8.2.1. Internal Cross References: Support internal links within a T.O. as defined by the AFTMSS 8.2.2. Launching External Processes: Provide the ability to launch external processes while viewing ETM data. 8.2.3. External Referencing Capability: Support external links between T.O.'s as defined by the AF TMSS 8.2.4 Hotspots hyperlinks must show with name that refers to content or as thumbnail. When the cursor is rolled over a Hotspot a description of the link is displayed, or a graphical representation of the graphic will display the content. 8.3. UPDATES 8.3.1. Full Revision: Support ability to identify updated or changed data with the use of icons or colored text and ability to link from list of changes to the changed data. 8.3.2. Tech Data Updates: Provide capability to add, delete and replace tech data on connected and non-connected mode clients 8.3.3. Data Configuration Management: Provide capability to configuration manage updates when importing or updating T.O.'s 8.3.4. User Account Management: Provide capability for T.O. manager to limit access to tech data based on User login information in connected and non-connected modes. 8.4. USER DEFINED COMMENTS 8.4.1. Redlining: Provide the ability to create annotations within a graphic instance (free-hand type) and save this data to a separate file. Annotations will NOT be saved into the T.O. Redlines should be active for current session only. Redlined graphic may be copied to a separate software package i.e. MS Paint for archiving. 8.4.2. Annotations: Provide the ability to create public and private notes within a text instance. Annotations will not be saved into the T.O. Annotations will be available for multiple sessions. Public annotations will be established and by a functional administrator. Public annotations will be distributed to all non¬-connected mode clients. Private annotations will be available to a single user and managed. Private annotation may be imported and exported for use on various non-connected mode clients. 8.4.3. Checklist Data: Provides capability to accomplish "Pen to Paper Check-off' upon completing checklist items. Checks will remain resident for a single session. 8.4.4. Annotation Management: Users need the additional F-16 ETM functionality to manage local supplements inserted in digital tech data via the F -16 ETM Annotator Tool. USAF and FMS customers will insert links to local maintenance procedures. Each country has a varying number of local documents. The greater the number of local documents the greater the management burden of the following problem and the greater the need for the modification. Several F-16 customers have greater than 1000 local documents to manage and USAF F-16 bases manage ~25-75 local documents. • F-16 ETM shall: provide the ability for the annotator to allow users to insert links to local maintenance or inspection requirements. • These local requirements are sometimes dependant and leverage off text in the existing tech data. If the existing tech data changes users may be required to modify their local requirements. • F-16 ETM Admin Tools provides functionality to indicate if the existing data change "Orphaned" the user established link. 8.5 GRAPHICS 8.5.1. Pan, Zoom, Expand, Magnify: Ability to perform pan, zoom, expand and magnify on graphic elements 8.5.2. Simultaneous Text/Graphics Display: When required by the instance the viewer shall provide the capability to display text and graphics in Job Guides in the same window with a split pane. 85.3. Hotspots: Provide the ability to navigate (within the same document (internally) and between documents (externally) from text to graphics, graphics to graphics, and graphics to text within the ETM data. 8.5.4. Icons: Icons shall be used to indicate the presence of in-line graphics. When the cursor is paused over the icon, a thumbnail view of the graphic shall appear. Upon double c1icking the icon, a full graphic view shall be launched. 8.5.5. Full Screen Graphics: Ability 10 show graphics full screen. Full screen viewing provides the capability to Pan, Zoom, Expand and, Magnify. 8.6. PRINTING 8.6.1. Print Screen (Connected Mode) 8.6.2. Time/Date Stamp with administrator defined destruction notice (For all Printing) 8.6.3. Print Task Data: Print complete task 8.7. PUBLISHING 8.7.1. Batch Processing: I) Batch processing shall provide the ability to perform batch process conversion of 30 SGML instances to include text and graphics into XML for viewing in F-16 ETM, 2) Publisher and Admin Tool shall have a command line interface in order to wrap in an OEM Vendor authoring system. 3) Batch processing shall need to support several options when called by the command line: (a) Specifying target server, T.O. and output directory. (b) Rule base to use (e.g. general-maintenance by sections vs. general maintenance by chapters) (c) Batch processing shall support the ability to convert graphics, capture and create thumbnails. 4) Batch processing shall provide report capability and notification of tech data instances of text and graphics that did not properly publish. 8.7.2. Multi-DocBase Capability: a. Publishing: Provide the capability to separate multiple blocks or versions of data during the publishing phase. b. Updating: Provide the capability to select a specific block or version of data and update with new data without replacing entire TO set(s) c. Viewing: Provide the capability to separate multiple blocks or versions of data on the viewing tool (CMC and NCMC) and allow the user to select a desired set of T.O.'s 8.7.3. Auto-Numbering (1): Auto numbering capability shall support batch process capability. Auto numbering s hall be automatically generated based on the specification and elements used in the tagged SGML. 8.7.4. Auto-Numbering (2): Must provide the same auto text generation capabilities as the corresponding FOSI i.e. Chapter, Section and Title 8.7.5. Tag Mapping: All auto generated text shall be sensible and readable (i.e. don't display tag names in the final viewing TO) 8.7.6. Viewable data format: Viewable data when transitioned from publisher to viewer must meet mil spec format and not lose any data when authored correctly 8.7.7. More Data Follows Indication: F-16 ETM shall provide an indicator that reflects more data is to follow the current screen. 8.7.8. Performance: Display times between screens shall be consistent with operator effectiveness (5 second objective). This may be achieved by partitioning the data or other means supportable by the viewing tool 8.7.9. Graphic Thumbnail Management: F-16 ETM shall support the publishing of the thumbnails to identity where the user is in the document so that only the graphics in the document that need a thumbnail get one in order to make the viewer smart enough to make that determination based on the location. 8.8. OTHER 8.8.1. Training: User Training 8.8.2. Deficiency Reporting: Capability to capture data that is in need of correction or update and forward it electronically for evaluation and correction along with comments. Shall include all management data currently required for recommended change process in accordance with TO 00-5-1. 8.8.3. Help Desk Support from 0600 -0500 Mountain Standard Time (MST): 8.9. SECURITY 8.9.1. Access Controls. Control access to TO.'s, software, data content, and devices so only authorized users can use or change them. 8.9.2. System Admin-this administrator is responsible for the hardware and operating system portions of the F-16 ETM system. Normally, this function is provided by the Base's Network Computing Center or the enclave level that maintains the server. 8.9.3. Functional Administrators (TODO) -Responsible for functional administrative activities. The functionally administrator primarily performs the following activities through the F-16 ETM software or designed COTS package: Use the Admin tool to set up and perform manual maintenance of data on Non-Connected Mode Client NCMC and base level server. Reviews Audit logs. Creation and maintenance of location specific public annotations Create Maintain Delete the user/admin passwords and accounts in F-16 ETM Maintain currency of content releases via imports and updates Coordinate with the NCC (System Admin) for OS system changes 8.9.4. Basic User-Read/Print access only 8.9.5. Administrator controls-Administrators configurable base-level server or NCMC to enforce user discretionary access controls (primarily for NCMC). When the controls are enabled, F-16 ETM shall provide the capability for the administrator to control (create, update, delete) a user's access to designated T.O. (s) when multiple docbases are used. 8.9.6. Login requirements- Require all users and administrators to login into F-16 ETM (not just OS login) to access F -16 ETM features. To enforce individual accountability, shall uniquely identify each user and administrator within a system. a. Eighteen characters maximum length of the username. b. F -16 ETM shall not require a system administrator account labeled "root" or "administrator" as a requirement to log in to the system, or for an application to run. c. F-16 ETM shall not allow "anonymous" or "guest" log-ins. d. Following a successful log-in procedure, inform the user/administrator of the last successful access to the account and of any unsuccessful intervening access attempts 8.9.7. Logoff function-Provide the administrator when using remote capability; automatically log the user or administrator off if the session is inactive for a period of 4 hours. This forces the user/administrator to re-authenticate after being logged off a system due to inactivity. This requirement is not applicable if an administrator is performing administrative activities directly on the server console of the E-tool 8.9.8. Disable/Delete User Account function-Provide the ability to disable (threshold) and delete (goal) an administrator or user account (internal to F-16 ETM) whenever the user/administrator is permanently transferred to another location or terminates employment 8.9.9. SECURITY AUDITING Provide basic auditing features to capture and log the following: User and administrator login -user/administrator name (account), date, time, and the origin (e.g., terminal ID, host Internet Protocol address). Creation, update (change), deletion of account information -administrator name (account) performing action, date, time, message of action providing information about the action (what action was performed on what account) Content load, change (update), or deletion -administrator name (account) performing action, date, time, message of action providing information about the action (what action was performed on what content) Failed login attempts -user/administrator name (account), date, time, and the origin (e.g., terminal ID, host Internet Protocol address). Report of locked account (excessive number of failed logon attempts) -user/administrator name (account), date, time Restrict access to audit logs to authorized administrators (audit trails shall be protected against unauthorized access, modification or deletion.) If the ability to toggle auditing is provided, it shall default "on" for the auditing items noted above. 8.9.10. Encryption of Transmission Communications -All information transmitted by F-16 ETM across network communication lines shall be encrypted. 8.9.11. Passwords Base-level servers shall support, when GFS is available, run password enforcement software to conform to password requirements established in AFMAN 33-223. To prevent unauthorized disclosure of passwords while they are stored, password authentication files shall not contain clear text authentication data. Shall enforce password construction rules. Each password must contain a minimum of eight characters comprised of at least one uppercase character, one lowercase character, one number, and one special character (@&+, etc.) Generic password assignment is prohibited (e.g., a system having "welcome" as the password for all newly created accounts) unless the user is required to change the password upon initial login. In this case, disable user accounts until the user is immediately ready to log in for the first time. Shall enforce password change rules. Prompt the user to enter the old password and authenticate as part of the password change procedure. Require password to be changed at a minimum of every 90 days. The default minimum before a password can be changed is 5 days. (Unless it is a initial password to be changed by the user/administrator at first login.) If given a generic password (e.g., "Pa$wOrd"), the system must prompt the user to immediately change to a new password. Must support at least four characters must be changed when a new password is created. Deployed/tactical systems with limited data input capabilities implement the password to the extent possible 8.9.12. Account Lock-Shall provide account-locking mechanisms to automatically lock an account when a maximum of three failed sequential attempts occur. The user/administrator will be notified of lockout whenever the account has exceeded the three attempts at time of next login attempt. RESPONSE FORMAT: When responding, potential offerors are requested to not to exceed 20 (20) single-sided pages and include an executive summary, relevant history and evidence of past performance or capability to perform the tasking with responses to the following: 1. Company Name 2. Company Cage Code 3. Company Point of Contact Name, email address and phone number 4. Executive Summary, relevant history of past performance or capability to perform the tasking, please describe. Explanation by requirement of the ability of the potential offeror's ability to meet each requirement. If the viewer/content management solution does not currently meet a requirement, the potential offeror must provide a detailed explanation of what modifications would be required to meet the requirements and a cost associated with each modification. This information will in turn be used to determine ROM quantity and cost required to meet F-16 customer needs. 5. Suggested NAICS Code 6. Business Size Classification for NAICS and qualifications, if any, as any sub-category (i.e., 8(a), HUBZone, SDVOSB) 7. Would you be a prime or subcontractor? 8. Lead Time for Task Performance 9. What type of contract would you be able to provide? 10. Do you possess a facility clearance, please describe? 2) ROM FORMAT: When responding, potential offerors are requested to submit a Rough Order of Magnitude (ROM) cost/schedule estimates in a Work Breakdown Structure (WBS) format compatible with inquiry paragraphs/requirements and include basis of estimates. The ROM does not have a page limit but needs to be submitted in single-sided page format and be resubmitted with response listed above. 3) ANNOUNCEMENT OF INFORMAL CAPABILITIES BRIEFING/DEMONSTRATION: In addition to the response and ROM, potential offerors are requested to provide informal capability briefing to take place at Hill AFB UT on 14 or 15 July 2010. Potential offerors' demonstrations to the F-16 customer need to demonstrate the available viewing solution / content management functionality to meet requirements or capable of meeting requirements with minimal amount of updating or enhancements. Scheduling of demonstrations will be accomplished by 501st Aircraft Sustainment Squadron. To be considered for briefing/demonstration, the potential offerors viewer solution / content management solution must be in such a status as to be demonstrated the on 14 or 15 July 2010; if not, there is no need to respond to this request. The Government does not intend to award a contract on the basis of this inquiry or to otherwise pay for the information solicited. The information provided is considered market research and may be utilized by the USAF in developing its acquisition strategy, Performance-Based Work Statement (PWS) and Performance Specifications. Responses to the inquiry will not be returned. IAW FAR 15.202(e), a response to this notice is not an offer and cannot be accepted by the government to form a binding contract. Responders are solely responsible for all expenses associated with responding to this notice include ROM and participation in the informal capabilities briefing/demonstration. Any proprietary information that is submitted may be used as a general concept but specific information will be safeguarded as proprietary, if so marked. Interested potential offerors should email a response to the inquiry and include answers to the questions listed above and the ROM to the Contract Negotiator. Copies of your submitted information will be distributed to the USAF Program Manager, USAF Engineer, and Contracting Officer for review. Responses should be emailed by 2:00 pm MST on Friday, 04 June 2010 to the Contract Negotiator listed below: Dawn Schmidt 508 ASCG/PK 6072 Fir Ave, Bldg 1233 Hill AFB UT 84056-5816 Email address: dawn.schmidt@hill.af.mil Technical Questions related to this notice should be referred to Cynthia Warr at email address: Cynthia.warr@hill.af.mil
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/USAF/AFMC/OOALC/FA8232-10-R-0022/listing.html)
- Place of Performance
- Address: 501 ACSS, Ft Worth TX and various CONUS user sites, Ft Worth, Texas, United States
- Record
- SN02159456-W 20100527/100525235032-0c9edbe102631866279d9567848c94a9 (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 |