Scope

Specific Requirements

CALS Implementation Plan (CALSIP)

CALS Approach

Database Architecture/System Tradeoffs

CALS Standards Conformance Test

Security

Programme Assessment and Control

Post Award CALS Program Orientation Conference

Government Furnished Information (GFI)

Contractor Integrated Technical Information Services (CITIS)

Data Element Dictionary [If CITIS is required.]

Engineering Data (Graphic and Text Files)

Automation & Functional Integration

Reliability and Maintainability (R&M) Automation

R&M-Logistic Support Analysis Record (LSAR) Integration

LSAR Data Automation

Reliability Centered Maintenance (RCM) and Age Exploration Automation

Level of Repair Analysis (LORA)

Diagnostics

Management Information Tools

Technical Manuals

Supply Support

Facilities Data

Training

Scope

Specific Requirements

The contractor shall implement a CALS Programme that will achieve the following objectives:

• Integrate contractor technical information systems and processes;
• Authorize NATO/NATO nations access to the contractor database(s);
• Deliver technical information in digital forms."

CALS Implementation Plan (CALSIP).

The contractor shall develop and maintain a current, comprehensive and detailed CALS Implementation Plan (CALSIP) outlining the procedures to be used to accomplish the CALS requirements defined in [Section X.X] of this Statement Of Work (SOW). The CALSIP shall address capabilities for automating the access and retrieval of technical data, and provide for digital exchange and integration between the engineering, manufacturing, logistics and other functional areas as appropriate to this acquisition phase of the Programme.

The CALSIP shall address, as a minimum, the following:

• CALS support hardware and software architecture, reference documents, points of contact.
• Contractor's approach and experience in creation, management, use, and exchange of digital information.
• Contractor's capabilities for integrating applications and databases.
• Procedures to improve product quality and eliminate data redundancy.
• Proposed CITIS on-line access capabilities.
• Information system and relationships with NATO/NATO nations receiving systems.
• Outline of proposed actions and capabilities to be pursued in subsequent life cycle phases.
• Telecommunications data protection and integrity, including system security."

CALS Approach

The contractor shall define a specific CALS implementation objective and strategy, taking into consideration technical constraints, quality and cost guidelines and the NATO/Government CALS Concept of Operations (NCoO) established by the service acquisition manager. This strategy shall be supported by necessary trade studies, and shall describe the framework for CALS implementation activities to be accomplished during each phase of [Programme name] system development. The strategy shall define how the principles of Concurrent Engineering (CE) will be applied, identify the critical enablers for CE (i.e., integrated database), and provide details on how Programme risk and costs will be reduced and product quality improved through CE and CALS initiatives. The implementation strategy shall serve as a guide in developing contractual requirements for later Programme acquisition phases. The CALSIP shall be updated every [days] throughout the life of the contract. The CALSIP updates shall define implementation plans for the upcoming period in greater detail, resolve outstanding strategy issues, respond to strategic and technology changes, and recommend specific alternative approaches for continuation of CALS in the next phase.

Database Architecture/System Tradeoffs

The contractor plan shall provide a cost effective method of managing the utilization of the contractor set of automated data processing systems and applications which support specific weapon system technical database(s) such that appropriate configuration and version control of technical information is maintained, while providing current data for design, engineering analysis, manufacturing, and product support planning. The contractor shall conduct appropriate tradeoffs/studies/analyses to support determination of the CALS implementation strategy. The status of these studies shall be reviewed at appropriate Programme management, design, and ILS reviews, and the results documented as part of the CALSIP. Candidates for such studies include:[Examples only; final determination is Programme specific]

• improved alternate data generation and delivery modes.
• >digital data delivery vs. on-line access.
• identification and elimination of unnecessary CDRL items.
• identification of CDRL items for interactive, on-line review.
• analysis of telecommunication alternatives.
• functional integration cost/benefit studies.
• cost effectiveness of contractor interim.
• CALS support [particularly in areas where infrastructure capability limitations can be overcome through use of hardware/software leased from the contractor]."

CALS Standards Conformance Test

The contractor shall include in the CALSIP plans to demonstrate the exchange of digital deliverables using the CALS standard formats, in accordance with the requirements of [ xxx ] and references [ xxx ]. This shall be accomplished through testing provided by the NATO/NATO nations or an industrial organization(s) chartered to perform such conformance test. Deliverables should pass a first article test on all formats to ensure conformance to the CALS specifications."

Security

The contractor shall establish a security system and enforce data protection and integrity standards. System security engineering principles as outlined in [ xxx ] shall be used. Controls to prevent unauthorized access shall be established and detailed in the CALSIP. The plan shall be based on the results of documented data protection and integrity, threat and vulnerability analysis, risk assessments, and tradeoff analyses. Vulnerabilities that remain after security system design shall be identified. The plan shall include disaster recovery provisions. Security requirements that must be complied with by NATO/NATO nations personnel will be identified to the NATO/NATO nations in the security section of the CALSIP. Any peculiar software that must be resident on NATO/NATO nations access terminals will be provided and maintained by the contractor. Information requiring special security provisions such as classified data, critical technology and sensitive data, such as proprietary, competition or liability sensitive data, will be partitioned to minimize the volume of information requiring specialized handling, to provide classification at the lowest classification level, and to control access. Sensitive data, in this context, includes but is not limited to, CDRL data items marked with one or more of the following: an export control warning notice, restrictive distribution statement, and/or a proprietary legend. Encryption of classified data or sensitive military data shall be stipulated by the CDRL and on an as-required basis in accordance with procedures established by the [ xxx ]. Such information shall be identified to prevent inadvertent disclosure and retention of security identification for printouts of accessed information. The contractor shall pay particular attention to unclassified items of information, which, taken together, can infer classified information. The contractor shall maintain configuration control of the security system and trusted system components. The contractor shall conduct a test and evaluation of the system and periodic inspections to ensure compliance. The NATO/NATO nations shall retain the right to conduct announced and unannounced inspections by security specialists at any time to review, audit, and account for classified materials.

Programme Assessment and Control

The CALSIP shall describe the procedures and controls by which the contractor and the NATO/NATO nations will evaluate the status and effectiveness of CALS. The implementation of CALS will be a subject of review at program, design, and ILS reviews.

Post Award CALS Program Orientation Conference

The prime contractor shall host a post award CALS program orientation conference to be scheduled no later than [number] of days after contract award. A representative from the [programme name] program office shall chair this conference. Major prime contractor teaming partners/subcontractors shall attend. The agenda for this conference shall be approved by the [programme name] program office. The purpose of this CALS meeting is to clarify the NCoO and have the contractor present to the NATO/NATO nations their plans for on-line access, if required, exchange, and delivery of digital data."

Government Furnished Information (GFI)

The contractor CALSIP shall describe the GFI the contractor expects to receive from the NATO/NATO nations. The list of GFI the NATO/NATO nations plans to provide is included in attachment/exhibit [number]. GFI shall be provided in both digital and hard copy formats. The GCO will define infrastructure capabilities to receive and use various types of digital data and technical information. The contractor shall use this GFI with contractor generated data."

Contractor Integrated Technical Information Services (CITIS)

The contractor shall propose ["develop" if CITIS is required] a program composed of procedures, processes, specifications and software applications for the integration, storage, exchange, and/or on-line sharing of data with the NATO/NATO nations. These technical data and database(s) and functional application capabilities provided within the contractor's system shall be referred to as the CITIS. This CITIS shall be developed in accordance with [ xxx ], and the following. The contractor shall propose ["develop" if CITIS is required] a Technical Information (TI) and programmanagement architecture, with a functional and hierarchical indexing system to:

• Manage configuration of the entire TI and planning databases.
• Integrate planning information into its respective TI source database.
• Trace configuration changes from design to logistics products and vice versa.

The contractor shall propose how he will ["is required to" if CITIS is required ] establish a link among logistics, design, engineering, and manufacturing data and functional processes to:

• facilitate the interchange and exchange of technical information.
• integrate technical data and database(s) to support the design, manufacturing and support processes and allow for timely access by authorized NATO/NATO nations activities.
• provide an integrated, shared data environment, consisting of integrated databases, analysis tools, and engineering processes designed to utilize digital TI.
• provide for the generation, storage, indexing, distribution, and delivery of integrated acquisition and logistics information products.

In the selection of analytical tools, the contractor shall maximize the use of previously developed or off-the-shelf software. These software tools shall be compatible with NATO/NATO nations hardware/software systems stated in the NCoO, unless contractor developed, unique software solutions are demonstrated to be more cost effective. The contractor's telecommunications solution for CITIS shall comply with NATO/NATO nations Interconnect Profile.

Data Element Dictionary [If CITIS is required.]

A general data element dictionary shall be developed so that identical data elements are addressable by the computer as the same data element. Changes to any duplicate data element shall be effected throughout all databases. A similar methodology shall be developed for graphics and large textual entities to ensure that changes to the source graphic correctly flags the necessity for change to all dependent graphic/textual entities derived from the source graphic. The contractor shall use existing data dictionaries as guidance in constructing the [Programme] data dictionary.

Engineering Data (Graphic and Text Files)

Any data, either NATO/NATO nations, contractor, or vendor, that contains engineering definition or guidance on material items (components), equipment system practices, methods, and/or processes relating to the design, manufacture, acquisition, test, inspection shall be submitted in digital form in accordance with [ XXX ] and compatible with the NATO/NATO nations data repository and receiving systems stated in the NCoO.

Automation & Functional Integration

The contractor should use computer-aided design, engineering, and manufacturing methods (CAD/CAE/CAM) to support design integration with manufacturing planning and logistic support system development. These software tools shall be compatible with the NATO/NATO nations hardware/software systems stated in the NCoO, unless contractor developed, unique software solutions are demonstrated to be more cost effective. An integrated set of ADP systems and applications will be used by the contractor team to enter, update, manage, and retrieve data from specific [Programme] technical database(s)."

Reliability and Maintainability (R&M) Automation

The contractor shall employ automated tools for performing R&M tasks. The contractor shall integrate these R&M tools with other CAE tools. These tools may stand alone with no direct access to the CAE database; reside in the CAE system and interface with the evolving design; or, reside on the CAE system and be automatically invoked to support design decisions. The R&M methods and tools used by the contractor shall, as a minimum, include:

• Automated R&M analysis procedures coupled to parts libraries and to material characteristics databases.
• Automated R&M synthesis based on design rules and lessons learned from prior design experience and field use.
• Fully characterized (tested and validated) component part performance and R&M characteristics databases.
• Design decision traceability.

R&M-Logistic Support Analysis Record (LSAR) Integration

The contractor shall establish an automated link to satisfy (LSAR) documentation requirements for initial and updated reliability and maintainability (R&M) information. Algorithms or transformations that must be applied to R&M source data elements to conform to LSAR documentation requirements shall be documented. Traceability between the LSAR and individual R&M data sources, and the preservation of appropriate data flows while maintaining established LSAR data element relationships and interdependencies, shall be clearly demonstrated.

LSAR Data Automation

The contractor shall establish and maintain a validated LSAR automated data processing system capable of input, storage, and retrieval of LSAR data in accordance with [xxx]. The contractor may use an internally developed and NATO/NATO nations validated LSAR automated data processing system, or independently developed and NATO/NATO nations validated LSAR automated data processing system. The contractor shall partition LSAR working data for in-process reviews and maintain these files separate from NATO/NATO nations approved LSAR data. The LSAR version containing the submitted data shall be the LSAR that has been subjected to internal contractor review procedures and is pending NATO/NATO nations review and approval. The LSAR working data shall be updated in accordance with the schedule in the LSA plan regardless of the approval status of the working data's content since the last update. Upon NATO/NATO nations approval, LSAR working data shall be transferred to the NATO/NATO nations approved LSAR. All NATO/NATO nations directed changes resulting from the LSAR data shall be cumulative of all approved LSAR data. Delivery of LSAR data shall be in accordance with the CDRL.

Reliability Centered Maintenance (RCM) and Age Exploration Automation

The contractor shall develop an automated system to maintain a complete RCM audit trail throughout the [Programme name] life cycle. This audit trail will permit traceability of preventive maintenance tasks back to specific engineering failure modes listed in the LSAR. The automated RCM analysis process must have the capability of delivering results digitally and through an interactive electronic interface with the LSAR database. The contractor shall utilize the RCM automated worksheet process or a contractor developed RCM automated process with the capability of automatically transferring compatible data to the NATO/NATO nations RCM software. The automated RCM analysis data/work-sheets must be delivered to the NATO/NATO nations in accordance with the CDRL.

The contractor will develop an Age Exploration (AE) database for the storage and analysis of in-service/operational age-reliability data which shall be used to support the RCM analysis process. The AE database shall be integrated digitally and have an interactive electronic interface with the RCM automated process.

Level of Repair Analysis (LORA)

The contractor shall employ an automated system to perform LORA in accordance with the requirements specified in [xxx]. The contractor shall establish a database as a repository for LORA input data and LORA output report files generated by execution of the LORA model software. The LORA database will be integrated with the automated LSAR database to maintain traceability of LSA data used as input to the LORA. The output results of the LORA shall be documented in the LSAR for development of the LSA-024 maintenance plan report. Approved LORA input data files and output reports shall be delivered in accordance with CDRL specified delivery mode (i.e., deliverable digital media or on-line access/retrieval).

Diagnostics

The source of diagnostic information will reside in logistics engineering databases offering data exchange in neutral formats. Software shall be developed to provide for automated interface with in-service performance and maintenance data collection processes and to provide feedback concerning successes and failures in the fault isolation process to the [Programme] system designer. Diagnostic systems that learn from experience and which have the capability to update a knowledge-based diagnostic database to optimize the fault isolation process or to improve system design are to be used to the fullest extent possible.

Management Information Tools

The contractor shall establish an on-line direct access capability for recording, planning, scheduling, and reporting status of program requirements. This shall provide visibility of the contractor's performance, highlight potential problems, and provide schedule compatibility checks to ensure integration of functional activities. This on-line capability shall identify change impacts on related areas of logistic support, design and manufacturing, and provide the status of program deliverables.

Technical Manuals

The contractor shall provide for computer assisted generation of technical manuals. This data is to be derived, to the maximum extent possible, from integrated digital data files, e.g., CAD/Engineering DataBase/LSAR. This data shall be provided in accordance with (Service-unique specifications and TM development guidance or other TM SOW requirements).

Supply Support

The contractor shall maintain spare parts identification consistent with the approved configuration baseline and allow for on-line assessment of the impact to spare parts requirements during analysis of design alternatives. The contractor shall provide provisioning technical documentation in accordance with [ xxx ] to facilitate automated ordering, supply management, and distribution, and should provide on-line identification of spares, repair parts, and source/maintenance/recoverability coding. This data shall be provided IAW (Service-unique specifications and TM/TO development guidance or other TM/TO SOW requirement).

Facilities Data

The contractor shall provide facilities data in digital form in accordance with [ xxx ] consistent with data derived from the LSAR database. Engineering drawings and specifications shall be provided in accordance with [ xxx ].

Training

Training data should be developed in accordance with [xxx]. The LSAR database shall provide source data to program software for producing output reports and instructional materials. Authorized system software shall be in accordance with NCoO specified requirements.