Loren Data's SAM Daily™

FBO DAILY - FEDBIZOPPS ISSUE OF SEPTEMBER 18, 2016 FBO #5413
SOURCES SOUGHT

R -- F100 Type II Interactive Electronic Technical Manuals IETMS

Notice Date

9/16/2016
 

Notice Type

Sources Sought
 

NAICS

541519 — Other Computer Related Services
 

Contracting Office

Department of the Air Force, Air Force Materiel Command, PK/PZ Tinker AFB, 3001 Staff Drive, Ste 1AG76A, Tinker AFB, Oklahoma, 73145-3015, United States
 

ZIP Code

73145-3015
 

Solicitation Number

FA812416R0007
 

Point of Contact

Melanie K. Easom, Phone: 405-734-6376
 

E-Mail Address

melanie.easom@tinker.af.mil
(melanie.easom@tinker.af.mil)
 

Small Business Set-Aside

N/A
 

Description

*Notice: This is a Sources Sought announcement. No proposals are being requested or accepted with this request. This is not a solicitation for proposals and no contract shall be awarded from this synopsis.* 1. Background 1.1 NOTICE: This is not a solicitation but rather a Sources Sought Synopsis to determine potential sources for information and planning purposes only. 1.2 The purpose of this Sources Sought is to conduct market research to determine if responsible sources exist, to assist in determining if this effort can be competitive and/or a total Small Business Set-Aside. The Government will use this information to determine the best acquisition strategy for this procurement. The government requests interested parties respond to this notice if applicable and identify your small business status to the identified NAICS code. Additionally, please provide any anticipated teaming arrangements, along with a description of similar services offered to the Government and to commercial customers for the past three years. Any responses involving teaming agreements should delineate between the work that will be accomplished by the prime and the work accomplished by the teaming partners. 1.3 Both large and small businesses are encouraged to participate in this Market Research. Joint ventures or teaming arrangements are encouraged. 1.4 Contractors/Institutions responding to this market research are placed on notice that participation in this survey may not ensure participation in future solicitations or contract awards. The government will not reimburse participants for any expenses associated with their participation in this survey.   REQUIREMENTS DESCRIPTION F100 IETMS PURPOSE/DESCRIPTION We are conducting market research to identify potential sources that may possess the expertise, capabilities, and experience to meet the requirements for the development and sustainment of an F100 Type II IETMS for the F100-PW-220 and F100-PW-229 Intermediate Level (I-Level) Technical Orders. Deliveries shall comply with applicable military specifications and technical manual requirements for Intermediate Level maintenance Interactive Type II Electronic Technical Manuals (IETMS). The tasks include sustainment support for applicable TOs; preparation and construction of IETM-compatible Rapid Action Change (RAC) electronic files, incorporation of Time Compliance Technical Orders, and AFTO Form 252s into the SGML, and delivery of Federal Desktop Core Configuration compliant TYPE II IETM to support distribution of scheduled IETM Revision Block Cycle Updates (BCU). The IETMS shall include an Engine Automated Work Package (EAWP) for field support. EAWP shall produce analyses and reports enabling maintainers, technical support personnel, and management to evaluate and analyze the difference between desired builds, most cost effective builds, and achieved builds, and to accomplish fleet reliability analysis. Additionally, the EAWP shall enable work center supervisors, depot, and MAJCOM Headquarters personnel to review and analyze maintenance being performed at the unit level. The IETMS shall include an integrated installation program capable of providing a complete installation on the user's computer without the requirement for network access. Our acquisition strategy is a four-year contract (basic plus 3 option years) and will continue through FY22. The projected delivery quantities will be an estimated 4 BCUs per year per engine for a total of 8 BCUs per year. It is estimated each BCU will be 300 change pages or less. • Detailed IETMS and EAWP requirements are included in APPENDIX A TM-86-01P. • The source data for the current IETMS is proprietary and cannot be provided by the government.   CONTRACTOR CAPABILITY SURVEY F100-PW-220 and F100-PW-229 Type II Interactive Electronic Technical Manuals Part I. Business Information Please provide the following business information for your company/institution and for any teaming or joint venture partners: • Company/Institute Name: • Address: • Point of Contact: • CAGE Code: • Phone Number: • E-mail Address: • Web Page URL: • Size of business pursuant to North American Industry Classification System (NAICS) Code: Leave this blank BC will provide Based on the above NAICS Code, state whether your company is: • Small Business (Yes / No) • Woman Owned Small Business (Yes / No) • Small Disadvantaged Business (Yes / No) • 8(a) Certified (Yes / No) • HUBZone Certified (Yes / No) • Veteran Owned Small Business (Yes / No) • Service Disabled Veteran Small Business (Yes / No) • Central Contractor Registration. (Yes / No) • A statement as to whether your company is domestically or foreign owned (if foreign, please indicate the country of ownership). Written responses, no facsimiles or e-mails please, must be received no later than close of business XX XXX 2016. Please mail two (2) copies of your response to: Questions relative to this market research should be addressed to the following:. Kevin Miller Post 2AA2108B 3001 Staff Drive Tinker AFB OK, 73145 Phone: 405-736-9558 Email: Kevin.miller.7@us.af.mil Cherry Caffey Post 2AA2108B 3001 Staff Drive Tinker AFB OK, 73145 Phone: 405-739-7907 Email: cherry.caffey.1@us.af.mil Part II. Capability Survey Questions General Capability Questions: Describe briefly the capabilities of your facility and the nature of the goods and/or services you provide. Include a description of your staff composition and management structure. Describe your company's past experience on previous projects similar in complexity to this requirement. Include contract numbers, a brief description of the work performed, period of performance, agency/organization supported, and individual point of contact (Contracting Officer or Program Manager). Describe your experience with Air Force Data Type Documents and TMSS compliant SGML. Are there specific requirements in the documentation that we provide that would currently preclude your product from being a viable solution to our requirement? Hardware Production Questions: What quality assurance processes and test qualification practices does your company employ? Please provide a description of your quality program (ISO 9000, QS-9000, EIA-599, or otherwise)? Engineering Services and Software Development Questions: Describe your capabilities and experience in managing software development projects, including subcontractor involvement. Include any experience in project planning, work breakdown structures, resource allocations, schedule tracking, risk analysis and cost management. Commerciality Questions: Are there established catalog or market prices for our requirement? If you offer this product and/or service to both U.S. Government and commercial sources, is the same workforce used for both the U.S. Government and general public? Is our requirement offered to both under similar terms and conditions? Briefly describe any differences. Acquisition Questions: What Rough Order of Magnitude estimate would you provide to undertake this effort? What period of performance estimate would you provide in undertaking this effort? Are you able to provide unlimited government rights to all software and source data? APPENDIX A Air Force Technical Manual Contract Requirements (TMCR) for F100 Engine Interactive Type II Electronic Technical Manuals (IETM) ATTACHMENT, TO CDRL SEQUENCE NUMBER, EXHIBIT REQUEST FOR PROPOSAL/CONTRACT: Date: Section 1. Technical Order (TO) Program Requirements 1. TMCR Tailoring. This TMCR has been tailored by the program office, including the associated tables, matrices and Specification/Standard Interface Records (SIRs). The Contractor may propose and submit, in writing additional tailoring to the TO Manager Agency/Agent (TOMA) and Procuring Contracting Officer (PCO) for consideration. The tailored TMCR shall be attached to the CDRL for TO delivery, and shall be included in the proposal as a separate exhibit, referenced in the proposal Performance Work Statement (PWS). Proposals shall be compatible with the F100 IETM Technical Order Concept of Operations. Air Force TO Acquisition procedures, including procedures for tailoring this document, are found in TO 00-5-3, AF Technical Order Life Cycle Management, located on the Internet at http://www.tinker.af.mil/technicalorders/index.asp. A copy may also be obtained from the Program TO Manager. Any terms or procedures found in this document may be researched there. 2. TO Program Scope. Sustainment of F100-PW-220, and F100-PW-229 Turbofan Engines, Intermediate Level (I-Level) Technical Orders. The standardized digital data shall include an integrated installation program capable of providing a complete installation on stand-alone DOD user's computer without the requirement for network access or installation on local DOD networks. All digital technical data shall be accurate and complete, and is critical for the end-user to maintain, and overhaul engines to continue Operational Safety, Suitability, and Effectiveness (OSS&E) for each engine TMS. Standardized digital data shall include an integrated installation program capable of providing a complete installation on a stand-alone Department of Defense (DoD) user's computer without a network access requirement, or installation on local DoD networks. The Air Force plan and intent is to have the contractor deliver a Type II IETMS update package at a minimum of every 90 days, up to 180 days. An Engine Automated Work Package (EAWP) to document maintenance of the engine during Jet Engine Intermediate Maintenance (JEIM) in accordance with AFI 21-101 will be included. 3. Technical Manual Specifications and Standards (TMSS) Tailoring. TMSS are tailored by selecting between tailoring options offered in each TMSS. The tailoring is recorded in SIRs and added to Section 3 of this document for each TMSS required. NOTE: Tailoring must not change or delete mandatory requirements which are part of the Document Type Definition (DTD) structure or XML schema structure located in Section 2 Table 1. 3.1. AF options in some Joint-Service TMSS have been documented in preliminary SIRs included in Section 3. These preliminary SIRs provide the starting point for further tailoring. Contractors may recommend additional tailoring of the Joint-Service TMSS SIRs and provide recommended SIRs for other TMSS as applicable. NOTE: TMSS requirements marked "(F)" are specifically for Air Force use; "(A)" is for Army, "(M)" is Marine Corps and "(N)" is Navy. Comply with all unmarked and "(F)" TMSS requirements as modified by the tailoring options in each TMSS. 3.2. Questions concerning TMSS requirements may be resolved by written request and justified suggestions for resolution submitted through the Procuring Contracting Officer (PCO). Deficiencies and suggested improvements shall be submitted to the TMSS Preparing Activity (PA). Approved recommendations, corrections and clarifications will be maintained with contract documentation. 4. TO Development. TOs shall be written to a scope and depth of coverage sufficient to support the F100 IETMs operations and maintenance concepts. 4.1. SGML-tagged TO files shall include required illustration (graphics) files in an approved graphics exchange format. Illustration files developed and delivered for other purposes shall be used in lieu of developing special TM illustration files whenever possible. All delivered graphics shall conform to the approved graphic creation and format guidelines listed in attachment 1. For assistance with illustration requirements contact AFLCMC/HIAM via (e-mail: SGMLSupport@us.af.mil). 4.2. Page-oriented Military Specification (MILSPEC) TOs shall be formatted with text, graphics and delivered according to the TMSS specified in Section 2. The contractor shall develop TO files (tagged instances) using Standard Generalized Markup Language (SGML) according to the DTDs referenced in the appendix to MIL-STD-38784, and each applicable military detail specification (MIL-DTL). Multiple SGML file instances for a single T.O. document are not authorized. 4.3. The contractor shall contact the PCO in writing for approval before modifying or developing any new DTD. If permission is granted, the Offeror must submit and proposed DTDs through the PCO for validation of TMSS compatibility with approved electronic TO viewing solution. New DTDs shall not be developed in lieu of existing DTDs, including those for legacy TMSS. DTD and rule sets submitted and approved in execution of the contract shall become the property of the Government. 5. Data Rights. Contractors shall provide Unlimited Government Rights for all source data and TOs prepared specifically for the contract. Government rights in data are specified in the Defense Federal Acquisition Regulation Supplement (DFARS), 252.227-7013, Rights in Technical Data, Noncommercial Items, 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation, and 252.227-7015, Technical Data-Commercial Items. The government shall be given unlimited rights for all business rules (tailoring and application methods and procedures) and documented business processes developed for use in TO development. Government data rights shall extend to the common source database, transformation style sheets, and other tools or products used to author or display technical data. The Contractor, at the request of the PCO, shall deliver the latest SGML and graphics files for all engines within 10 calendar days upon the completion of the contract. The Contractor shall deliver 3 CD/DVD's containing SGML files (1 original, and 2 copies), and 3 CD/DVD's containing graphics files (1 original, and 2 copies). 6. Classification, Distribution, Destruction, Disclosure, and Export Control Notices. Offerors shall place the below statements (ref. DODM 5200.01, DODI 5230.24, AFI 61-204, and MIL-STD-38784) on the title page of each new technical manual, and CD/DVD. DISTRIBUTION STATEMENT D - Distribution authorized to the Department of Defense and U.S. DoD contractors only, Critical Technology, 1 June 1987. Refer other requests for this document to AFLCMC/LPSLB, OK 73145-3031. WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec. 2751, et. seq.) or the Export Administration Act of 1979 (Title 50, U.S.C., App. 2401 et. seq.), as amended. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25. DESTRUCTION NOTICE -Destroy by any method that will prevent disclosure of contents or reconstruction of the document. 7. TO Quality. The Contractor shall develop and maintain quality control program to ensure services are performed in accordance with this PWS. This quality plan shall include software testing procedures if modifications/upgrades are required to either the IETMS/EAWP or to the third part software required to run IETMS/EAWP. The Contractor shall provide a Quality Control Plan (QCP) within 10 calendar days ARO. The Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The Government reserves the right to perform inspections on services provided to the extent deemed necessary to protect the Government's interests. The Contractor must control the quality of the services and deliverables provided in support of this task and maintain substantiating evidence that services conform to contract quality requirements and furnish such information to the Government if requested. The Contractor's quality control program is the means by which they assure themselves their work complies with the requirement of the contract. After acceptance of the QCP, the Contractor shall receive the CO's acceptance in writing of any proposed change to the QCP. (DIQCIC-881379, CDRL A003) 7.1. Guidance Conference. The Guidance Conference shall be coordinated and cohosted between the contractor, PCO, and Contracting Officer's Representative (COR). Working through the TOMA, the Contractor and/or Subcontractor shall attend an initial Post Award Conference either via teleconference or on site at Tinker AFB to be scheduled by the PCO and coordinated with the COR within 10 calendar days ARO. The Post Award Conference shall be scheduled to (1) achieve a clear and mutual understanding of all contract requirements, and (2) identify and resolve potential problems in the performance of these services. The Contactor shall submit a proposed Agenda at least 5 calendar days prior to the conference, and provide Conference Minutes for PCO review and approval within 5 calendar days after the meeting. Post Award Conference topics shall include: PWS Overview, Contractor Quality Control Plan, Government Quality Assurance Surveillance Plan, Conversion of SGML to TMSS complaint SGML, Delivery Schedule, Deliverables, Roles and Responsibilities, Government Inspection and Acceptance, Recommended Metrics (Milestone Chart), Status Meeting and Reporting Schedule and Contractor Invoice procedures. The PCO, COR, Administering Contracting Officer (ACO), and other Government personnel, as appropriate, may meet periodically via teleconference for review of Contractor's performance. 8.2. In-Process Reviews. The contractor shall support In-Process Reviews of the data developed for this effort. In-Process Reviews are required for those TOs converted to TMSS compliant SGML The contractor shall support IPRs with the technical writers, engineers and QA personnel as required or needed. IPRs will be held in accordance with TO 00-5-3 or as defined by the program office. 8.3. TO Delivery Requirements for In-Process Reviews. IPR TO data shall be technically edited and reviewed according to the Quality Control Plan before delivery to the government. 8.4. TO Prepublication Reviews (PPR). PPRs, and Record of Incorporated Data (RID) reviews are examinations of TOs to ensure incorporation of changes from IPRs and Technical Data Change Forms (AFTO Form 252s). The Contractor shall prepare and deliver copies of TOs and TO updates in MIL-SPEC compliance for the PPR as shown in the delivery matrix. The TOs for PPR shall have been approved by contractor QA, be in compliance with the MIL-SPECs/standards, and incorporate all verification comments and corrections approved by the TOMA or program management office representative. 8.5. Technical Data Assessment (TDA). TDA's will be accomplished using the assistance of AFLCMC/HIAM. The TO Manager, will determine the TDA requirements for each TO type. 8.5.1. SGML TO Data. The contractor shall submit an SGML tagged TO file, associated graphics files, a PDF rendition of the SGML tagged TO file composed by the contractor and any associated companion files necessary for PDF composition. During assessment, the SGML tagged TO file will be parsed against the appropriate TMSS DTD (and optionally run through the Tagging Utilization Tool (TUT)) to determine DTD compliance and correct tag usage. The SGML tagged TO file and associated graphics will be composed by the program office and the rendered PDF will be compared with the submitted PDF to check for completeness, indexing, and MIL-SPEC/STD compliant formatting. 8.5.2. Error Resolution. Errors found during the TDA shall be addressed and completed prior to each IPR. Additional TDAs may be necessary based on the amount of errors found during the initial TDA. Successful TDAs in no way relieves the contractor from fixing errors found during future reviews. 9. TO Delivery. TO file delivery requirements are located in Section 2 Table 3 of this document. 9.1. SGML Tagged Files. The contractor shall parse and compose SGML tagged TO document files prior to delivery to the government, and verify that content tagging has been accomplished in compliance with the appropriate DTD. 9.2. Interactive Electronic Technical Manuals (IETM). IETM delivery shall be according to the Section 2 of this document. 10. Source Data Maintenance. Contractors shall maintain accuracy, currency and configuration of TO source data, to include GFI, throughout the contract period of performance. Maintenance includes preparation of source data updates to incorporate corrections, equipment configuration changes, and maintenance and operational concept changes. 11. Schedules. Contractor will deliver Block Cycle Updates 90 days after receipt of order and change requests. 16. Program Specific Requirements: See Appendix's A and B SECTION 2. TM TYPE AND DELIVERY REQUIREMENTS NOTES: • Mark the TM Type Selection Tables indicating the applicable TO types and related specifications. PART A - (NEW DEVELOPMENT) TM TYPE SELECTION TABLES. TABLE 1 TMSS REQUIREMENTS FOR THE TYPE II F100 Program IETMS Title or Type of Manuals Specification Required 1. Inspection TOs MIL-DTL-5096 N/A 2. Cargo Aircraft Loading and Offloading TOs MIL-DTL-5288 N/A 3. Weight and Balance (Aircraft) MIL-DTL-5920 N/A 4. Flight Manuals MIL-DTL-7700 N/A 5. List of Applicable Publications MIL-DTL-8031 N/A 6. Structural Repair Manuals (for Aircraft) MIL-DTL-9854 N/A 7. Munitions/Weapons Loading Procedures, Non- nuclear and Nuclear TOs MIL-DTL-9977 N/A 8. Space Operations and Support Documentation TOs -- MILSPEC (Intercontinental Ballistic Missiles) -- MILSPEC (Space) MIL-PRF-38311 0 MIL-PRF-38314 N/A 9. Nuclear and Non-nuclear Weapon Delivery and Aircrew Procedures Manuals and Checklists MIL-DTL-38384 N/A 10. Work Unit Code Manual MIL-DTL-38769 11. Calibration Procedures MIL-DTL-38793 N/A 12. Time Compliance Technical Orders (TCTOs) MIL-DTL-38804 N/A 13. Aircraft Battle Damage Assessment and Repair TOs MIL-DTL-87158 N/A 14. Illustrated Parts Breakdown MIL-DTL-38807 1 15. On-Equipment Organizational Maintenance Manual Set MIL-DTL-83495 N/A 16. Operation and Maintenance Instructions in Work Package Format MIL-DTL-87929 a. Maintenance Manuals (1) Intermediate Maintenance 1 (2) Depot Maintenance 0 (3) Combined (I&D) Maintenance 1 (4) On Condition Maintenance 1 b. Operation & Maintenance Instruction Manuals 1 c. Special Manuals (1) Aircraft Engine Testing and Trending Procedures 1 (2) Aircraft Power Package Testing Procedures 0 (3) Static Firing of Missile Motors 0 (4) System Peculiar Corrosion Control 0 (5) Nondestructive Inspection (NDI) 1 (6) Aircraft Structural Integrity Program (ASIP) 0 (7) ATE Operator Test Procedures 0 (8) Special Requirements for Storage and Maintenance Procedures; AUR Munitions/Launchers and Associated Support Equipment, Conventional Components and CMBR Agents 0 (9) Parachute Packing Procedures 0 (10) Operators Instructions (Hand Held Flight Computers) 0 (11) Installation Engineering Facility (Ground C-E Equipment) 0 d. Checklists (IAW MIL-DTL-5096) 0 e. With Illustrated Parts Breakdown 0 17. Commercial Manuals (Evaluate according to MIL-PRF-32216) N/A0 18. Aircraft Cross-servicing Guide MIL-DTL-22202 N/A0 19. Technical Publications Utilizing Common Source Database (CSDB) ASD-S1000D - International Specification for Technical Publications Utilizing a CSDB MIL-STD-3048 N/A0 TABLE 2 SUSTAINMENT/MODIFICATION UPDATES TM TYPE SELECTIONS NOTES: • Check all applicable boxes. • For existing manuals not being updated to latest specification requirements, enter "Same style and format" under the specification heading. TO Number, Title, or Type of Manual Specification Change Revision Supple-ment Supple-mental TM Source Data 1. 2J-F100-1-CD-6 See Appendix D for included TOs Mil-DTL-87269 MIL-DTL-87268MIL 0 1 0 0 0 2. 2J-F100-1-CD-7 See Appendix C for included TOs Mil-DTL-87269 MIL-DTL-87268 0 1 0 0 0 3. 2-1-111 MIL-DTL-87929 0 1 0 0 0 4. 2J-F100-9 MIL-DTL-87929 0 1 0 0 0 5. 2J-F100-94 MIL-DTL-87929 0 0 0 0 0 6. 00-25-113-F100 MIL-DTL-87929 0 0 0 0 0 TABLE 3 - TM DELIVERY REQUIREMENTS FOR F100 TYPE 2 IETMS (System/Item) NOTES: • For Paper media delivery indicate required quantity • For all other media types indicate (Y)es or (N)o • TCTO requirements are specified in the contract vehicle approving the TCTO. If "Other" is selected, define media type and quantities: Type II IETMS 3ea DELIVERY SCHEDULE Event Number of days data required prior to event  In Process Review(s) (10 Days) Final TO Distribution IETMS Enter physical mailing address, electronic delivery location or web access point  ATTN: Cherry Caffey AFLCMC/LPSLB 3001 Staff Drive Post 2AA2108B Tinker AFB OK 73145 Other/ IETMS Other/ IETMS DELIVERY SCHEDULE Event Number of days data required prior to event  In Process Review(s) (10 Days) Final TO Distribution IETMs Enter physical mailing address, electronic delivery location or web access point  ATTN: Cherry Caffey AFLCMC/LPSLB 3001 Staff Drive Post 2AA2108B Tinker AFB OK 73145 Other/ IETMS Other/ IETMS DELIVERY SCHEDULE Event Number of days data required prior to event  In Process Review(s) (15 Days) Final TO Distribution IPDF Enter physical mailing address, electronic delivery location or web access point  ATTN: Cherry Caffey AFLCMC/LPSLB 3001 Staff Drive Post 2AA2108B Tinker AFB OK 73145 Other/ IPDF Other/ IPDF   ATTACHMENT 1 Graphics Format Recommendations GENERAL GUIDELINES • Single column graphics should not exceed 51 Picas High by 18 Picas Wide. (Paper only) • Full page graphics should not exceed 51 Picas High by 42 picas Wide. (Paper only) • Fold Out graphics should not exceed 51 Picas High (width on foldouts is not important). (Paper only) EPS: • Raster based images will not be saved as EPS. • EPS files shall not be a mix of vector and raster images. Vector only. • Any source data (photos used for tracing etc.); used in aiding of creation of EPS (templates, etc.) will be deleted from illustration prior to saving/exporting. • If multiple layers are used, then image is to be flattened into 1 single layer before exporting to minimize file size and reduce possible printing issues. TIFF: • B&W raster images should only be saved as Bitmap and not Grayscale, RGB or CMYK. • Grayscale or Color images (screenshots, etc.) will be saved as such (Grayscale, RGB or CMYK) and will not be bitmap converted using a halftone screen. • To further aid in file size reduction for storage purposes, images should be compressed using Group 4 compression when saving/exporting. CGM: • Raster based images will not be saved as CGM. • Any source data used in aiding of creation of CGM (templates, etc.) will be deleted from illustration prior to saving/exporting. • CGM files shall not be a mix of vector and raster images. Vector only. • If multiple layers are used, then image is to be flattened into 1 single layer before exporting to minimize file size and reduce possible printing issues. • Unless Version 4 is specifically required for hotspots and/or hyper linking, CGMs should be exported as version 3 to increase cross platform compatibility. DWG: • Raster based images will not be saved as DWG. • DWG files shall not be a mix of vector and raster images. Vector only. • Any source data used in aiding of creation of DWG (templates, etc.) will be deleted from illustration prior to saving/exporting. • If multiple layers are used, then image is to be flattened into 1 single layer before exporting to minimize file size and reduce possible printing issues. JPEG: • JPEG File format should be used as last resort. Color screenshots/photos should be saved as TIFFs due possible system compatibility issues. • B&W Bitmaps should not be saved as JPEGs.   APPENDEX A IETMS REQUIRMENTS The following is a list of minimum IETMS functional requirements. NOTE: The IETMS structure shall not include or require the use of a Web Server software application on individual end user computers, including computers used as host servers within a local network installation. However, the IETMS structure shall be capable of operating within a Government-owned server environment. For security reasons, Java Applets shall not be utilized in and delivered in IETMS. a. IETMS structure shall support stand-alone installation on an independent computer (i.e., non-networked notebook/desktop computer). b. IETMS structure shall support installation database format capable of supporting multiple connections to client computer systems. The network clients shall be capable of utilizing the TO data stored in a database. c. IETMS structure shall provide Global Search capability within engine models as well as search within a single manual. d. IETMS shall support Integrated Rapid Action Change (RAC) incorporation. RAC issued data shall integrate with existing IETMS TOs text upon installation. RACs shall be distributed with an IETMS installation Program. e. IETMS shall support active change marking with automatic highlighting of change data within the TOs, and provide summary of change data since last Bulk Change Update (BCU). f. IETMS shall provide bookmark and memo capabilities allowing the user to stop a session and mark where they left off for later return. g. IETMS shall support internal referencing (linking). h. IETMS shall be capable of supporting External Media Object referencing (i.e., PDF documents, videos, Excel spreadsheets, Word documents, and photos, etc.) i. IETMS shall be capable of allowing the user to embed or add supplements, IPIs, country peculiar supplements, digital pictures, videos, and other attachments to a specific location or procedure. This function will allow the administrator to select a location and add the attachment. The system must prevent the maintainer/mechanic from proceeding past supplements, IPIs, and country peculiar supplements to the next step until the procedure has been completed. j. Locally required inspections, steps, or notes shall be capable of being added to IETMS using the IPI feature. IETMS shall provide a method for allowing the work completed in accordance with the IPI to be approved by the mechanic, and a digital signature for approval by a qualified inspector. k. IETMS shall provide the capability to create a printable Source Data Representation (SDR) file for WP or IPB assemblies, with references to graphics and tables. IETMS shall provide the capability to print individual figures and tables. Any printed SDR file shall require the TO and WP number in addition to a time and date stamp displayed on the printed output. l. IETMS installation program shall automatically provide an IETMS icon on the desktop. m. IETMS display shall include a readily viewable indication of IETMS Title and Revision number. n. IETMS shall provide a navigation pane to include a Table of Contents and a List of Changes for each manual. o. Graphic Presentation Display Minimum Requirements (Typical): View: These are the graphics viewing options (magnify, zoom-in, zoom-out, fit, Pan, Full Screen Graphics (FSG)) Window. p. Print: This option prints the graphics display area. Split-Screen capability to view text on the left and graphics on the right. q. IETMS shall have alerts which consist of: Warnings, Cautions, and Notes, as per MIL-STD-38784A. Warnings are displayed in Red, Cautions displayed in Yellow, and Notes displayed in Blue. r. IETMS shall have a help selection link to a help file. s. Synchronization: This function is for synchronization of RACs, IPIs, supplements, memos, bookmarks, activity trace, and users. t. Synchronization shall include capability to synchronize Engine Automated Work Package (EAWP) data between server and shop client computers. u. IETMS shall include direct hot links to "Emergency Procedures" and "Engine shutdown procedures" anytime the engine test TO is displayed to the test cell engine operator. v. IPB Hotspots -The IPB illustrations shall be populated with hotspot information to support linking from the index number to the part location in the parts list. The link shall take you back to the original spot. w. IETMS shall be capable of use in a Browse, Admin or Maintenance Mode. x. When performing maintenance in the maintenance mode, use of the IETMS will require the user to sign on and enter the serial number and job control number (JCN) which represents the asset the user is inspecting or repairing. y. Activity Trace capability in the Maintenance Mode: This feature traces a user's maintenance history in a particular session including User Id, Name, Engine/Module/Component S/N, or P/N if non-tracked item and JCN, which represents the asset the user is inspecting or repairing. A date will be stored for each session in which the user signs on. This data is stored in a read-only file. Review of this data is controlled by a password. z. IETMS shall be capable of using admin mode to make administrative changes as required without signing into maintenance mode. aa. Multiple Sessions and Users: the user should be able to have multiple sessions: WP and multiple users on one computer. bb. Exit: Stops the maintenance session and concludes the activity trace. dd. Security Function will enforce user ID for log-on in Maintenance/Admin Mode only. ee. When performing maintenance in maintenance mode, the use of the IETMS will require the user to sign on with a user ID and password, and allow an administrator to assign the user roles to each individual who is authorized to access the IETMS. ff. IETMS will provide capability for an administrator to assign a user as an IPI certifier. This will be accomplished by allowing a person with the user role of "Certified Signoff Authority" to enter his/her logon ID and password for IPI completions. gg. Dialogs are used to context filter the TO data. This feature is primarily used for configuration management and decision making. Dialog statements to give maintainer choice of procedures to view within the IETMS or specific WP. This feature may not be applicable to all WP's. hh. A Distribution Statement shall be included on the DVD-ROM covers of all unclassified TOs, including DVD or TO revision number, individual TO change number, and supplement numbers. An Export Control Notice and Destruction Notice will be placed on the media jacket and on the database splash screen as required by T.O. 00-5-1. ii. Each WP contains pull down menus to provide access to internal reference data (supplemental information, locator graphics, system/part descriptive information, and theory of operation, where applicable) as well as external links to other IETMS WP's and other IETMS built support manuals that are currently in IPDF format. APPENDIX B ENGINE AUTOMATED WORK PACKAGE (EAWP) MINIMUM REQUIREMENTS a. The contractor shall develop the EAWP to function with the F100 IETM operating system. The EAWP will be non-proprietary. b. The EAWP will allow maintenance documentation for the engine during JEIM in accordance with AFI 21-101. c. The EAWP will incorporate a standard engine maintenance Work Package to be furnished by the USAF. d. The use of the EAWP in maintenance mode will require a user to sign on to the IETM with a user ID and password, and enter the serial number and job control number (JCN), which represents the asset the user is inspecting or repairing. e. EAWP Roles will be assigned through the IETM. The IETM will allow an administrator to assign user roles to each individual who is authorized access to the IETM (e.g. Administrator, Certified IPI signoff authority, and Standard Users), and shall include capability to assign user special skills certifications and task signoff restrictions for associated tasks as defined by the USAF. f. The EAWP will provide a means to identify tasks that have been completed, not completed, in-work, and not required. g. Capability to print individual worksheets or the entire work package will be provided. h. The EAWP shall provide capability to reconcile data input to a "Component Verification Worksheet" for tracked components to CEMS historical data and identify any discrepancies or incomplete data. i. The EAWP will provide for automated processes to the maximum extent possible. j. The EAWP shall permit import of engine and component configuration and times, and TCTO data. The EAWP will be designed to provide capability to export to other maintenance systems by exporting files in extensible markup language (XML). k. The capability to either manually input entries into a Daily Summary Worksheet or to auto-populate it following task completions will be proposed for USAF approval. The Daily Summary Worksheet auto-populate functionality will be incorporated into the EAWP following USAF review and approval. l. The capability to save the final work package in a single Read-Only document will be provided. m. The EAWP shall not increase IETM system security requirements; i.e. Certification and Accreditation requirements. n. All requirements applicable to style, format, and process flow as identified during user In-Process Reviews and TO Verifications will be incorporated. Incorporation of any increased functionality requirements identified will be as agreed upon by the contractor and Government. o. Automated processes will be developed and used to the maximum extent possible. These include import of engine and component configuration and times and TCTO data. These processes will provide the capability to export data to required maintenance systems. p. The EAWP shall be able to be transferred to the EHM+ DRC at completion of the engine maintenance. q. The EAWP shall have the capability to capture inspection data from the inspection tables. r. The EAWP shall provide the capability to provide an executive summary status of each engine in work.   APPENDIX C Technical Orders residing on T.O. 2J-F100-1-CD-7: TO TITLE 2J-F100-41-01 ENGINE PRETEST AND POSTTEST PROCEDURES 2J-F100-41-02 ENGINE TEST 2J-F100-41-03 ENGINE TROUBLESHOOTING 2J-F100-24 ILLUSTRATED PARTS BREAKDOWN - INTRODUCTION AND GENERAL INFORMATION 2J-F100-46-1 INTRODUCTION AND GENERAL INFORMATION 2J-F100-46-2 ON CONDITION MAINTENANCE 2J-F100-46-3 SUPPORT EQUIPMENT AND NUMERICAL TOOL LIST 2J-F100-46-4 ENGINE ACCESSORIES AND RIGGING PROCEDURES 2J-F100-46-5 ENGINE 2J-F100-46-6 INLET/FAN MODUEL 2J-F100-46-7 CORE ENGINE MODULE 2J-F100-46-8 REAR COMPRESSOR DRIVE MODULE 2J-F100-46-9 FAN DRIVE TURBINE MODULE 2J-F100-46-10 AUGMENTOR DUCT AND NOZZLE MODULE 2J-F100-46-11 GEARBOX MODULE 2J-F100-46-12 ENGINE AUTOMATED WORK PACKAGE   APPENDIX D Technical Orders residing on T.O. 2J-F100-1-CD-6: T.O. TITLE 2J-F100-51-01 ENGINE PRETEST AND POSTTEST PROCEDURES 2J-F100-51-02 ENGINE TEST 2J-F100-51-03 ENGINE TROUBLESHOOTING 2J-F100-54 ILLUSTRATED PARTS BREAKDOWN - INTRODUCTION AND GENERAL INFORMATION 2J-F100-56-1 INTRODUCTION AND GENERAL INFORMATION 2J-F100-56-2 ON CONDITION MAINTENANCE 2J-F100-56-3 SUPPORT EQUIPMENT AND NUMERICAL TOOL LIST 2J-F100-56-4 ENGINE ACCESSORIES AND RIGGING PROCEDURES 2J-F100-56-5 ENGINE 2J-F100-56-6 INLET/FAN MODUEL 2J-F100-56-7 CORE ENGINE MODULE 2J-F100-56-8 REAR COMPRESSOR DRIVE MODULE 2J-F100-56-9 FAN DRIVE TURBINE MODULE 2J-F100-56-10 AUGMENTOR DUCT AND MODULE NOZZLE 2J-F100-56-11 GEARBOX MODULE 2J-F100-56-12 ENGINE AUTOMATED WORK PACKAGE
 

Web Link

FBO.gov Permalink
(https://www.fbo.gov/spg/USAF/AFMC/OCALCCC/FA812416R0007/listing.html)
 

Record

SN04276303-W 20160918/160916235818-e1f5c775be0b21c4914d3e18c1985d67 (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 |